Skip to Content
SAP Open Catalog Interface is simple http POST interface between SAP application and internal/external catalogs. Employee can select items from catalogs and transfer items to Shopping Cart via OCI. Suppliers can enhance existing their catalog to support OCI. *1. Specification*  {code:html}SAP Supplier Relationship Management – SAP SRM Open Catalog Interface (B2B-OCI){code} You can ask suppliers to support OCI and pass this specification to their developers. If they want “SAP Certified Integration” logo, please contact ICC Integration Certification Center. There are HTML form transfer and XML transfer but HTML transfer is widely used because of low investment in supplier side. *2.* *How does it work ? *    1. Employee selects catalog link     2. SAP application calls supplier catalog URL with username, password and return URL     3. Supplier catalog authenticates the user and show catalog search screen     4. Employee searches items in supplier catalog and add items in supplier side Shopping Cart     5. Employee selects transfer button     6. Supplier catalog generates transfer page with HTML form and transfer     7. SAP application receives POST data and add items in SAP application OCI specification has parameter name agreement both SAP and Supplier catalog side. For Example, *NEW-ITEM_DESCRIPTION* (1) = Standard A4 note PC with 2G memory *3.* *Additional functions* Buyers can request suppliers to support following 2 additional functions *    FUNCTION=DETAIL *After items are transferred, detail icon is available in Shopping Cart. When user select detail icon, catalog shows item detail window.
*    FUNCTION=VALIDATE *When user copy items from old shopping cart, item is validated and the latest information is transferred to new shopping cart. If you buy some items monthly, new shopping cart gets the latest price. There is no catalog UI interface for validate function.

*4. OCI enabled SAP Application*
SRM – all release
PM – Plant Maintenance since R/3 4.7
PS – Project System since R/3 4.7
MM – Material Management since ERP 6.0

*5.  OCI enabled Catalog*
SAP CCM – Catalog Contents Management
ISV Catalogs and Supplier Catalogs
[ |]
Search by B2B-OCI*. These are only certified vendors but there are many OCI enabled supplier catalogs in the market. Please ask your supplier to support OCI in their catalog. It is not big development for them. *6. Customizing* Example for SRM and SRM-MDM Catalog. Go to SPRO transaction. Supplier Relationship Management -> SRM Server -> Master Data -> Define External Web Services  (Catalogs, Supplier Lists, and so on) You can pass required parameters to catalog. If SRM is ITS based UI under SRM5.0, please define 3 additional parameters. If your Portal Session Management is 2.0, add returntarget parameters. *7. Trouble Shooting
*Please set “Use error log” in Catalog definition. Please check general troubleshoot note. ( Common error is UOM mismatch. Supplier should send ISO UOM. *SLG1 log:* [ |] Please implement the BADI. You can see the OCI return parameter value in SLG1. *HttpWatch:* If you face issue in http level, please use http log tool like HttpWatch.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member
    Hi Masa,
    Very useful Information.
    Can I know a sample punchout catalog to test my connectity and checking the functionality?


  2. Former Member

    Thank you

    Can you tell me if there is a browser version control within the OCI configuration or if it will use the users installed IE version.



  3. Former Member

    When configuring the web services catalog from ECC 6.0 using the below call parameters.  I continue to get a white screen when punching out to the Ariba Procurement Content catalog.   All the necessary call parameters to call the catalog and open a session appear correct.   Has anyone seen this issue… or have any suggestions on how to resolve the issue.



Leave a Reply