cXML PunchOut Vs. OCI PunchOut


As we all know, PunchOut is a protocol that has been designed to simplify the B2B ordering process. It establishes a direction connection between the procurement application and the supplier’s website. PunchOut provides plenty of benefits including direct access to Contract catalog without entering any login credentials. Although this functionality is popular, many users are still unaware about the difference between cXML PunchOut and OCI PunchOut.
cXML is an XML language created by Ariba to exchange business documents between Ariba procurement system and ecommerce platform. Even other procurement systems like SciQuest and Coupa use cXML messages to do business transactions with B2B ecommerce sites. No wonder in cXML PunchOut, standard business transactions are sent/received in cXML format.
When a customer clicks the PunchOut link to access his Contract catalog from the supplier’s site, a PunchOut request is sent in standard cXML format. Also, upon adding products into the shopping cart, it returns back to the procurement application in cXML format with the cXML header containing <To> and <From> elements.
On the other hand, OCI PunchOut is typically used by SAP systems while cXML PunchOut is typically for non-SAP users. So if you are using a SAP procurement system, then you will have no option but to use OCI format for communication with ecommerce site. This format defines the field mapping between the supplier’s catalog and SAP system. With OCI format, you really don’t have to worry about incorrect data transmission between the source and the receiver.
With cXML PunchOut, it is possible to give a customized error message to the user when server connection fails. There is no such provision in OCI PunchOut, hence the user will receive the typical HTTP 404 error, which indicates that the web page cannot be found.

On the whole, PunchOut catalog simplifies B2B business transactions using cXML and OCI connectivity. Depending upon your requirements, decide in what format, you want to conduct business transactions.

No comments

Theme images by Maliketh. Powered by Blogger.