Prerequisites for a supplier to participate in OCI 5.0 import for Catalog Items

[KeLaw]

Hello,

we are aiming to set up the Import of Catalog Items to use during Self-Service Procurement, according to these blogs:

Configuration for OCI 5.0 and OCI 4.0 in the S/4HANA Cloud Essentials - SAP Community

Setup of Punch-out Catalogs in S/4 HANA Cloud Essentials - SAP Community

We are still at the very beginning and are wondering: Are there any prerequisites that our suppliers need to fulfill?

Best regards,

Kerisha

[Daisy_Zhang]

We helped you to accept the answer, since there were no updates after 7 days. You can unaccept it anytime if you have further questions.

[Chris1973 · Accepted solution]

Good day @KeLaw 

Thank you for your question

Yes, there are supplier side prerequisites that you should consider. When you look at the blogs you attached, you can recognise various defined sections in ensuring you can successfully implement your project. In summary, they fall into three buckets that can be defined as: technical capability of OCI, Authentication and access, Parameter handling and data protection, content quality and data completeness, Images and attachments.

In public cloud, OCI 4.0 will support your classic catalog punch out for Self Service Procurement. You user are then able to open the supplier catalog, fill their cars and return items into the purchase requisition. See, Settings for Web Services & OCI for more insights.

For OCI 5.0, this is relevant if you want to import catalog items and cross catalog searches are possible. It uses JSON over HTTP or file upload to support catalog data replication

In reference to the buckets mentioned earlier, you may consider this as a checklist for your supplier.

Technical capability:

For OCI 4.0 punch out, your supplier must provide a HTTPS catalog entry URL that your users can reach. They must also support the OCI roundtrip and return the cart back to SAP. See Settings for Web Services.

For OCI 5.0, your supplier must provide catalog content that matches the designed format as mentioned above.

Authentication and access:  

The Schedule Import of Catalog Data and Settings for Web Services provides details/prerequisites on how SAP stores the authentication parameters. So, you will need to agree with your supplier on how the catalog session is authenticated.

Parameter handling and data protection:

SAP sends certain parameters such as language, currency, return URL, etc and your supplier must accept those. You can use certain BAdI to control OCI parameters in the outbound call if you want to restrict what user data is sent. This Blog has some good insights: Employee Self Service Procurement in S4 HANA with Catalogs hosted in External System.

Content quality and data completeness:

Make sure you align with your suppliers on their ability to provide quality data such as Product ID, UoM, price, currency, tax logic, attachments, etc.

Images and attachments:

Considering you will be carrying out cross catalog searches and will need attachments and images, you will need to use a Content Management Service endpoint.

To summarise:

• Your supplier must support OCI 4.0 for classic punch out.
• Same for OCI 5.0 and must provide catalog data as JSON over HTTP or file.
• Make sure you set up the supplier catalog in Settings for Web Service
• Ensure to schedule catalog import and delivered contents are sent through accessible endpoint.

Best regards

Chris