Open Catalog Interface

This article has multiple issues. Please help or discuss these issues on the . (Learn how and when to remove these template messages) This article needs additional citations for verification. Please help by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources:  –  ·  ·  · scholar · JSTOR (June 2021) (Learn how and when to remove this template message) The topic of this article may not meet Wikipedia's general notability guideline. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted. Find sources:  –  ·  ·  · scholar · JSTOR (January 2014) (Learn how and when to remove this template message) (Learn how and when to remove this template message)

Open Catalog Interface (OCI) is a standard protocol developed by SAP for punch-out catalogs that connect buyers' procurement systems with suppliers' eCommerce systems.^[1] OCI is an alternative to cXML.

It is used by SAP Supplier Relationship Management, ORDIGES Purchase-to-Pay, Microsoft Dynamics AX and other ERP/Purchasing Systems when connecting to external punch-out catalogs. In the open catalogue project Open Icecat, a separate OCI is defined for the exchange of multimedia data between multilingual product catalogs.

The OCI format is used to define the field mapping between the supplier's catalog and the SAP SRM shopping cart, to ensure that the data is transferred accurately and completely between source and receiver.

See also[]

• cXML

References[]