Häufig gestellte Fragen
What is a punchout catalogue, explained simply?
A punchout catalogue is an online catalogue hosted by the supplier, into which buyers "punch out" directly from their own procurement or ERP system instead of importing the catalogue into their own system. In the supplier's shop they assemble a basket with daily updated prices and availability and hand it back to the internal system in structured form. This does not create a finished purchase order but a purchase requisition, which then passes through the regular approval workflow in the buyer's own system. The approach thus combines the always up-to-date catalogue maintenance on the supplier side with the approval, budget and posting rules of the purchasing organisation.
What is the difference between OCI and cXML in punchout?
OCI (Open Catalog Interface) and cXML (commerce eXtensible Markup Language) are the two most widespread protocol families for punchout, and at their core they fulfil the same task: establishing a secure session and returning the basket in a standardised way. OCI was developed by SAP, frequently transfers data via simple HTTP parameters and is considered lean and quick to implement, whereas cXML originates from the Ariba environment, uses structured XML messages and can map further documents beyond the mere basket return, such as order confirmations or invoices. In practice, OCI is found above all in SAP landscapes, while cXML dominates in cloud-based procurement platforms such as SAP Ariba or Coupa. Which protocol is suitable depends on the existing system landscape and the standards supported by the suppliers involved.
Which OCI versions exist and how do they differ?
The most important OCI versions are OCI 4.0, introduced around 2004 in the context of SAP Supplier Relationship Management (SRM) 4.0, and OCI 5.0, which followed about ten years later. OCI 4.0 established the basic mechanism of transferring item data and prices from a supplier catalogue into the SAP shopping basket via HTTP hand-over. OCI 5.0 extended the concept with, among other things, options for catalogue replication and JSON support, and is regarded more as a fundamental redesign than a mere evolution. Both versions can be operated side by side, which is why both variants are often in parallel use in grown system landscapes.
What is the difference between Level 1 and Level 2 punchout?
With a Level 1 punchout, users leave their procurement system and are redirected to the supplier's standalone online shop, where they search and assemble the basket before it is handed back. With a Level 2 punchout, by contrast, parts of the supplier's product range are made searchable directly within the procurement system via an index file (such as a CIF file with SAP Ariba), so that requisitioners can research items from several suppliers together without opening each shop individually. Level 2 thus offers a more integrated search experience and more control over the presentation, but the connection is usually more involved because structured catalogue data has to be maintained in addition. The choice of level depends on the product range, the desired search depth and the acceptable integration effort.
How secure is a punchout catalogue and how are sessions authenticated?
Punchout connections run over encrypted HTTPS sessions in which the procurement system authenticates itself to the supplier shop before item data is exchanged. Depending on the protocol and provider, authentication uses shared secrets, certificates or token-based methods; clean session management is intended to prevent unauthorised access and the takeover of other users' sessions. Because the supplier recognises the requesting organisation, customer-specific prices and terms can be displayed at the same time, without these having to be maintained in the buyer's own system. Since approval, budget checking and posting remain entirely within the buyer's own system, the purchasing organisation retains control over the ordering process despite the external session.
When is punchout worthwhile compared with a static catalogue?
A punchout catalogue plays to its strengths above all with large, dynamic product ranges with frequent price and availability changes — for instance C-parts, office supplies or IT hardware — because updating remains with the supplier and no extensive catalogue has to be imported and versioned internally. A static catalogue, on the other hand, can be the simpler choice for stable ranges with infrequent updates, since no live connection has to be operated. The integration effort should be taken into account: in practice, punchout connections are set up per supplier and frequently require several weeks of project time, depending on the protocol, platform and data mapping. As a general rule, pure licence or subscription costs usually account for only a smaller share of the total costs of ERP and procurement projects, while the larger share goes on implementation, adaptation, training and data maintenance.