The OCI interface is an open standard for exchanging catalogue data records. The Open Catalog Interface (OCI) is a standardised catalogue data interface. SAP developed the technology for electronic purchasing in the 1990s. It connects an ERP system directly with a B2B e-commerce online shop, and the data exchange works as a PunchOut.
Primus Catalog: software for catalogue management
The e-catalogue software Primus Catalog manages and distributes your product catalogues centrally. The system serves OCI and PunchOut scenarios for e-procurement, letting you automate the exchange of your catalogue data completely.
Arrange a free demo appointment or read more about the system:
How an OCI PunchOut links the ERP system to the online shop
For the user this purchasing process starts inside their e-procurement system. From there the buyer accesses the supplier’s product catalogue. The platform authenticates the user automatically in the background during that access, so no separate login is required.
The buyer then researches inside the external online shop. The system displays all item data and prices in real time. This immediate data synchronisation prevents errors during product selection.
After choosing, users add the desired items to the cart. In the final step the software transfers the order data back to the purchasing system, using standardised URL parameters such as the HOOK_URL for the handover.
What the OCI interface delivers for procurement
The technology optimises a company’s procurement processes.
- Efficiency: direct system integration eliminates manual data entry.
- Time saved: this data alignment saves roughly two to four minutes per order.
- Fewer errors: standardised transfer avoids transmission mistakes.
- Lower costs: automation reduces total procurement costs by around eight to twelve per cent.
- Compliance: keeping internal ordering processes intact prevents maverick buying during research.
- Less training: removing external logins cuts the training requirement for users by around 80 per cent.
- Real-time data: buyers check same-day prices right inside their product selection.
- Supplier variety: the protocol accelerates onboarding for new supplier catalogues.
- Risk reduction: multiple sources of supply strengthen the resilience of customers’ supply chains.
Integrating the OCI interface seamlessly
Pro3Con supports you in planning and implementing a well-performing OCI connection. We adapt the technology precisely to your system landscape, and our specialists advise you in a free initial conversation.
Arrange a free initial conversation
OCI 4.0 and OCI 5.0 modernise the standard
OCI 4.0 supports extended data structures
OCI 4.0 uses HTTP requests for the transfer within the system landscape. Each product receives detailed product information such as images or specifications. SAP developers use the structure CI_OCI_CUSTOMER_EXTENSION for additional customer fields, which software vendors treat as the basis for individual tax indicators.
For detailed information on the specifications and advantages of this version, see our dedicated page:
OCI 5.0 establishes the JSON mass upload
This upload replicates catalogue data into the ERP system in bulk over an HTTP connection. An integrated catalogue search gives the user a direct overview of the replicated data, and federated search provides an uninterrupted view of the range.
The updated protocol transfers item hierarchies into the ordering software through the PARENT_ID field. Advanced attributes now support highly configurable products, with deeply nested JSON structures handling the transfer.
As a new feature, Secure OCI hides sensitive credentials from the browser. Communicating servers exchange those credentials through a direct backend call.
Implementing the OCI interface requires preparation
Integration into a merchandise management system starts with defining the catalogue URL.
- Parameters: engineers store the address of the CGI script for the network connection.
- Call enrichment: the SAP enhancement BBP_CAT_CALL_ENRICH adds dynamic parameters to the catalogue call.
- Field mapping: developers configure the settings for correct data assignment.
- Materials management: the BAdI IF_ME_CATALOG_INTERFACE controls the field mapping for the MM module through the MAP_CAT_VALUES method.
- Classification mapping: the module BBP_CATALOG_TRANSFER assigns external UNSPSC classifications to internal material groups.
- Customer fields: the same transfer module also processes the parameters CUST_FIELD1 to CUST_FIELD5.
- Session data: transferring catalogue data into enterprise resource planning strictly requires the SessionTransmissionId parameter.
- Data enrichment: the add-in /SRMNXP/CATALOG_TRANSFER_DATA enriches catalogue data before it is written into the staging tables.
- Validation: the system rejects faulty data records when values are missing.
Primus PunchOut
The software Primus PunchOut takes the complex IT configuration off your hands entirely. Our standardised cloud solution lets you skip the manual development effort.
Check your BMEcat catalogue for free
How Pro3Con automates the connection for suppliers
As a technology specialist, Pro3Con optimises your digital B2B procurement. Primus PunchOut generates your universal interface fully automatically in 30 seconds. As a supplier you need no IT resources of your own. The technology synchronises your catalogue and product data in real time.
The system transfers this data to e-commerce and procurement platforms and serves the OCI 4.0, OCI 5.0 and cXML standards.
Seamless integration into common e-commerce platforms
The connector integrates your range into platforms such as SAP, Coupa or Unite Mercateo.
Check your BMEcat catalogue for free
A dedicated customer care team accompanies you through implementation up to a successful go-live. Error-free catalogue records contribute directly to lower costs, and automation makes your e-commerce visibility future-proof.
OCI interface: frequently asked questions
What does OCI stand for?
OCI stands for Open Catalog Interface.
What is the OCI?
The OCI is a standardised catalogue data interface developed by SAP for B2B e-commerce. The technology enables the electronic exchange of catalogue data between business partners.
How does OCI work?
OCI works through HTTP requests to exchange shopping carts between a merchandise management system and supplier catalogues. The user controls the process from their own e-procurement system.
What is an OCI PunchOut?
An OCI PunchOut is direct access from a procurement system to a supplier’s external product catalogue. The technology integrates external product catalogues seamlessly into the buyer’s own ERP system.
What is a PunchOut?
A PunchOut is the technical connection between an e-procurement system and an external online shop for automated cart handover. The setup automates a company’s internal purchasing processes.
What are PunchOut connections?
PunchOut connections are the configured interface links between the buyer’s ERP system and the supplier’s e-commerce software.
What does “OCI-capable” mean?
“OCI-capable” describes a system’s technical compatibility with this protocol: the software supports direct PunchOut into external catalogues.
What is the difference between OCI and Oracle?
The difference lies in the formats used for data exchange. OCI primarily serves the SAP environment, while the Oracle platform often uses the cXML standard for procurement processes.