Punchout

How a punchout runs

A punchout has three steps. First, the procurement system logs the buyer in at the shop: with cXML through a PunchOutSetupRequest, which the shop answers with a start URL; with SAP OCI through a call that carries login data and the HOOK_URL. Then the buyer shops, with their range and their prices. Finally, the shop returns the cart through the browser: with cXML as a PunchOutOrderMessage, with SAP OCI as a form with NEW_ITEM fields.

In the procurement system the cart becomes a purchase requisition. After approval, the supplier receives the order by a route of its own, for example as a cXML OrderRequest, an IDoc ORDERS05, an openTRANS ORDER or by email.

Level 1 and Level 2

With Level 1, the procurement system's catalog holds a single entry for the supplier; the punchout leads to the shop's home page, and the buyer searches there. With Level 2, the supplier's items or categories are already stored in the procurement system's catalog and can be searched there; a click opens the matching product or category page in the shop directly. With cXML, the PunchOutSetupRequest passes the chosen item for this (SelectedItem). The division into levels is common mainly with SAP Ariba.

Punchout catalog and static catalog

A static catalog is a file the supplier loads into the procurement system, for example in BMEcat or CIF format; prices and range are as current as the last delivery of the file. With a punchout catalog, by contrast, the buyer sees the shop itself, with the current range, their prices and availability. The punchout ends with the cart; the purchase only becomes binding with the order after approval.

Punchout with orcamultimedia and punchout.dev

punchout.dev turns any shop into a punchout supplier for cXML and SAP OCI through a single script tag. orcamultimedia also offers plugins for SAP OCI, SAP Ariba PunchOut and cXML Punchout Transaction, and the punchout catalog as a complete package based on an open-source shop system.