OAGXML - Open Applications Group XML is a typical Oracle standard in that it is Open and the only user is Oracle. The xml format is extremely complicated and normally can be implemented via @UK PLC in a few days for punchout and purchase order.
It can take a long time to find an Oracle consultant that knows how to configure the Oracle end, but it usually works first time once Oracle is configured.
OAGXML DOES NOT WORK FOR INVOICES AND IS NOT SUPPORTED BY @UK PLC FOR INVOICES. THERE ARE OTHER ORACLE FORMATS THAT WORK AND ARE SUPPORTED BY @UK PLC FOR INVOICES.
OAGXML works well for Punchout and purchase order and any other message sent from Oracle. However because each oracle system sends a different purchase order format depending on the detailed configuration of the oracle system. It is not a good format for returning invoices to Oracle since the inbound format needs to match the Oracle configuration, because of this we use other methods to load electronic invoices into Oracle that are quick and easy to configure at the Oracle end.
OAGXML is available in two variants Standard Punchout (the same as all other versions of punchout) and Transparent punchout (a distributed search). Transparent punchout is only suitable for ordering goods that do not have complex pricing, configuration or delivery options since the protocol does not support multilevel/volume price breaks, configuration or carriage charges. @UK PLC has extended the protocol to provide this information to Oracle users, however this is not automatically imported into the requisition and purchase orders end up with incorrect pricing and no carriage charges. This is why there are a number of advantages to using standard punchout. The main advantage of transparent punchout is if you have a large oracle user base that have been trained in Oracle, since their is no change in process with transparent punchout.
@UK PLC can connect in any suppliers ecommerce site using sbxp which provides an standard way of connecting from @UK PLC to any ecommerce site and simplifies the process.
@UK PLC normally only accepts OAGXML on the buyside of the system and connects to suppliers using either sbxp or cxml punchout, for suppliers as soon as they are connected to @UK PLC via either sbxp or cxml punchout then your system is connected to all major buyside platforms.
@UK PLC offers a quick route for suppliers that require OAGXML punchout by using the @UK PLC hub and sbxp punchout/orderXchange. This allows suppliers to leverage @UK PLC's working integration with all the variations of OCI and to connect using the sbxp toolkit which provides a punchout in all the various web development languages.
By providing proven multi development language functionality, it is much easier for developers to connect using the language of their choice.