Open Catalog Interface
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Open Catalog Interface" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Open Catalog Interface|concern=data format article of unclear notability, lacking independent references, tagged for refs and notability since 2014}} ~~~~ Timestamp: 20200605160730 16:07, 5 June 2020 (UTC) Administrators: delete |
![]() | The topic of this article may not meet Wikipedia's general notability guideline. (January 2014) |
Open Catalog Interface (OCI) is one of the standard formats 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. This standard is used instead of XML or cXML.