PunchOut for SAP S/4HANA: OCI catalog or cXML for your customer | PunchCommerce                       ![](//analytics.punchcommerce.de/matomo.php?idsite=1&rec=1)

  [Skip to content](#main-content)

   Procurement system · SAP S/4HANA    Live in production

 PunchOut for SAP S/4HANA. Your customer buys through SAP S/4HANA and requires a PunchOut catalog. You deliver via OCI or, with SAP Ariba in front, via cXML.
==============================================================================================================================================================

 Your customer runs purchasing through SAP S/4HANA, the ERP system from SAP, the central business software that also covers purchasing. SAP S/4HANA connects supplier catalogs via OCI, the Open Catalog Interface from SAP, in the standard version 4.0; your customer expects cXML, the Ariba standard, if they have put SAP Ariba in front of it. With PunchCommerce you provide this catalog, from your online shop or, without a shop, from the Hosted Catalog. This page shows how to clarify the protocol, what S/4HANA expects from you, where connections typically fail and what the connection costs.

 [ Start free trial ](https://www.punchcommerce.de/register) [ See the setup ](#setup)

30 days free · no credit card · cancel anytime

  SAP S/4HANA protocols OCI · cXML

 Setup without an IT project &lt; 1 h

 per customer per month, plus VAT €49

 Requirements

What your customer on SAP S/4HANA expects from you
--------------------------------------------------

 If your customer buys directly in SAP S/4HANA, you deliver an [OCI PunchOut](https://www.punchcommerce.de/en/oci-punchout). If they have put SAP Ariba in front of it, the [cXML PunchOut](https://www.punchcommerce.de/en/cxml-punchout) applies, set up as described under [PunchOut for SAP Ariba](https://www.punchcommerce.de/en/punchout-sap-ariba). What follows concerns the OCI case. Which protocol other systems speak is shown in the overview of [procurement systems](https://www.punchcommerce.de/en/procurement-systems).

### You need a catalog entry in S/4HANA

Your customer creates your catalog in SAP Fiori with “Manage External Catalogs” and assigns it to their buyers with “Assign Catalogs to Users”, or in Customizing (transaction SPRO) under “Materials Management → Purchasing → Sources of Supply → Define External Catalogs”. They store the catalog ID, target URL, call type and OCI version.

### You need the PunchOut URL, OCI version and credentials

Your customer receives from you the PunchOut URL as the target URL, the OCI version, usually 4.0, and the username and password. For each item, the cart returns the short text, price, unit of measure, material group and manufacturer part number, mapped via the field mapping per customer.

### You need the material group and ISO unit of measure

The material group has to match the assignment your customer has stored in S/4HANA; otherwise S/4HANA assigns the item to the wrong account. S/4HANA expects the unit of measure as an ISO code, such as PCE for piece or KGM for kilogram; an abbreviation such as “ST” fails. You set both in the field mapping.

### You need the deployment: public cloud or on-premise

In the public cloud, your customer sets up catalogs only via Fiori apps and self-service configuration; your data therefore has to arrive from the catalog in the right form. On-premise or in the private cloud, customers often enrich the OCI data with their own code.

### You need answers to VALIDATE and DETAIL

Some customers have S/4HANA check with the OCI function VALIDATE whether price, availability and the item are still current. Occasionally, the buyer uses DETAIL to reopen an item from a document line in your catalog. PunchCommerce answers both without any extra setup.

 How VALIDATE and DETAIL work in detail is shown on the page [PunchOut for SAP SRM](https://www.punchcommerce.de/en/punchout-sap-srm). Where connections typically fail is covered in the frequently asked questions.

 Setup

Five steps to the first purchase from SAP S/4HANA
-------------------------------------------------

You complete three steps yourself, your customer takes over the fourth in SAP S/4HANA, and in the last one you both test. You usually set up your side of the connection in under an hour.

1. 1 You · your customer### Ask for the protocol

    Ask your customer whether they have put SAP Ariba in front of S/4HANA: if so, cXML applies, otherwise OCI. At the same time, clarify the OCI version, material group keys, units of measure and whether they work in the public cloud or on-premise.
2. 2 You · PunchCommerce### Choose the catalog source and create the customer

    Install the plugin for your shop system or provide your items in the Hosted Catalog. Then create your customer with the matching protocol and define product range, prices and field mapping, including material group and ISO unit of measure.
3. 3 You · your customer### Hand over the PunchOut URL and credentials

    For OCI, you send your customer the PunchOut URL, the OCI version and the username and password. You do not need to ask for the HOOK\_URL: S/4HANA sends it along with every call.
4. 4 Your customer · S/4HANA### Register the catalog in SAP S/4HANA

    Your customer registers your catalog with the Fiori app “Manage External Catalogs” or in Customizing and assigns it to their buyers with “Assign Catalogs to Users”.
5. 5 You · your customer### Test and release

    With the simulator you check the cart before the first real purchase. Your customer then tests from S/4HANA whether the material group and unit of measure arrive correctly and releases the catalog for their buyers.

###   What you need from your customer

- The protocol: OCI directly from S/4HANA, or cXML because SAP Ariba sits in front of it
- The OCI version, usually 4.0
- Their material group keys
- The units of measure as ISO codes, such as `PCE` for piece
- Whether they work in the public cloud or on-premise

###   What you send your customer

- The PunchOut URL as the target URL of the catalog
- The OCI version you deliver
- Username and password for the catalog

 Catalog source

With your own shop or without: SAP S/4HANA receives the same cart
-----------------------------------------------------------------

 For SAP S/4HANA, it makes no difference where your items come from. In both cases the buyer opens a catalog and transfers the cart back via OCI or cXML. In both cases you set the material group and the unit of measure via the same field mapping per customer. Hosting is GDPR-compliant in Germany.

 With your own online shop### Your shop becomes the S/4HANA catalog

 Ready-made plugins are available for nine shop systems, including [PunchOut for Spryker](https://www.punchcommerce.de/en/spryker), [PunchOut for Shopware](https://www.punchcommerce.de/en/punchout-shopware), [PunchOut for Magento](https://www.punchcommerce.de/en/punchout-magento), [PunchOut for Vendure](https://www.punchcommerce.de/en/punchout-vendure), [PunchOut for JTL-Shop](https://www.punchcommerce.de/en/punchout-jtl) and [PunchOut for Medusa](https://www.punchcommerce.de/en/punchout-medusa). The buyer jumps from S/4HANA straight into your shop and sees their prices and the product range you release for them.

 [See the plugins for your shop system](https://www.punchcommerce.de/en/integrations)

 Without your own online shop### Provide items in the Hosted Catalog

 You upload your items to the Hosted Catalog as a list or transfer them via API. The buyer jumps from S/4HANA into this catalog. You define product range and prices per customer.

 [See the Hosted Catalog](https://www.punchcommerce.de/en/hosted-catalog)

 Pricing

What PunchOut for SAP S/4HANA costs
-----------------------------------

You pay per customer you connect in PunchCommerce. Whether your customer expects OCI or cXML does not change the price. Hosting is GDPR-compliant in Germany.

 For your case Supplier · self-service setup### PunchCommerce Business

Connection to SAP S/4HANA via OCI or cXML, set up by you, without an agency. Three connected customers cost €147 per month, plus VAT.

 €49 per customer per month, plus VAT

Without your own shop: plus the Hosted Catalog add-on, €50 per customer per month, plus VAT.

 [ Start free trial ](https://www.punchcommerce.de/register)30 days free · no credit card · cancel anytime

 [Compare plans and pricing](https://www.punchcommerce.de/en/features-and-pricing)

 With SLA &amp; operational responsibility### PunchCommerce Enterprise

For suppliers who need availability with an uptime guarantee, defined escalation paths and someone responsible for operating their PunchOut connections.

 Custom based on SLA level and number of connections

 [ Schedule a consultation (opens in a new window) ](https://account.netzdirektion.de/appointments/punchcommerce)30 min · remote · with the founder

 [See PunchCommerce Enterprise](https://www.punchcommerce.de/en/enterprise)

 FAQ

Frequently asked questions about PunchOut for SAP S/4HANA
---------------------------------------------------------

What suppliers want to know before the first S/4HANA catalog: protocol, OCI version, unit of measure, public cloud, typical errors and costs.

 ###   My customer uses SAP S/4HANA – do I need OCI or cXML? +

 That depends on whether your customer has put SAP Ariba in front of S/4HANA. If they buy directly in S/4HANA, S/4HANA connects your catalog via OCI, the Open Catalog Interface from SAP; you can recognize this by the HOOK_URL, the return address for the cart. If purchasing and orders run through SAP Ariba, for example via SAP Ariba Buying or Guided Buying, cXML, the Ariba standard, applies to the PunchOut and to the orders. Also ask about a group policy: some corporations require cXML from all suppliers. How the two protocols differ for you is shown in the comparison [OCI vs. cXML](https://www.punchcommerce.de/en/oci-vs-cxml); for the Ariba case, read [PunchOut for SAP Ariba](https://www.punchcommerce.de/en/punchout-sap-ariba).

###   Which OCI version does SAP S/4HANA expect? +

 Usually OCI 4.0, the standard version of the Open Catalog Interface through which S/4HANA connects external catalogs. It is often backward compatible with OCI 3.0. Your customer enters the version in the catalog definition in S/4HANA and can tell you which one applies. PunchCommerce supports OCI 4.0 and OCI 5.0.

###   Why does SAP S/4HANA not accept my item with the unit of measure ST? +

 Because S/4HANA expects the unit of measure as an ISO code, as SAP has stored it for the unit, such as PCE for piece or KGM for kilogram. “ST”, the German-language SAP abbreviation for piece, is an internal code that S/4HANA does not accept in this field. In the field mapping, with which you define per customer which item data goes into which OCI field, you assign the matching ISO code to your units. The default field mapping of PunchCommerce already sets spellings such as “Stück”, “Stck.” or “St.” to PCE.

###   My customer is on the SAP S/4HANA public cloud – what does that change for me? +

 Your customer has less room for customization there. In the public cloud, the variant operated by SAP, they set up catalogs only via Fiori apps, meaning the user interface of S/4HANA, and self-service configuration (SSCUI or SAP Central Business Configuration); custom programs that rewrite transferred catalog data are only possible to a limited extent. The material group, unit of measure and texts therefore have to come from your catalog exactly as S/4HANA needs them. You set this up in PunchCommerce via the field mapping per customer. On-premise, meaning in their own data center, or in the private cloud, customers by contrast often compensate for deviations with their own code, for example via an exit or a BAPI, meaning enhancement and programming interfaces provided by SAP.

###   My customer’s HOOK\_URL cannot be reached – what should I do? +

 S/4HANA sends the HOOK_URL, the return address for the cart, along with every call; you do not enter it anywhere. If it cannot be reached, the cause is usually in your customer’s network: with on-premise systems, which your customer runs in their own data center, it often points into the intranet, and the firewall or DNS, the name resolution in the network, blocks access. An invalid SSL certificate, the certificate for the encrypted connection, also aborts the return. The third typical error is garbled umlauts: they occur if UTF-8, the usual encoding for umlauts and special characters, is not used throughout. In all three cases, first check with the PunchCommerce simulator whether your cart is created correctly, then pass the error message on to your customer’s IT.

###   Is PunchCommerce part of SAP S/4HANA? +

 No. PunchCommerce is an independent solution for suppliers and not a component of SAP S/4HANA. The connection runs via OCI, the Open Catalog Interface through which S/4HANA connects supplier catalogs, or via cXML, the Ariba standard, if your customer has put SAP Ariba in front of it.

###   What does PunchOut for SAP S/4HANA cost? +

 PunchCommerce Business costs €49 per connected customer per month, with OCI and cXML; there is no surcharge per protocol. Without your own shop, the Hosted Catalog add-on comes on top at €50 per customer per month, plus VAT in each case. You test the first 30 days free of charge and without a credit card. If you need an SLA and operational responsibility, PunchCommerce Enterprise is the right plan.

  Get started

 Your customer is waiting for the S/4HANA catalog. Deliver it today.
---------------------------------------------------------------------

 €49 per customer per month; without your own shop, plus the Hosted Catalog add-on at €50 per customer per month, plus VAT in each case. Ask for the protocol, create the customer, send the credentials to your customer, have the catalog registered in S/4HANA, done.

 [ Start free trial ](https://www.punchcommerce.de/register)30 days free · no credit card · cancel anytime

 ![Patrick Dornbusch, founder of PunchCommerce](https://www.punchcommerce.de/static/patrick-dornbusch.webp)Patrick Dornbusch

Founder of PunchCommerce

Prefer to talk first? In 30 minutes we’ll work out which option suits your shop, your ERP and your customers’ procurement systems.

 [ Schedule a consultation  (opens in a new window) ](https://account.netzdirektion.de/appointments/punchcommerce)30 min · remote · with the founder

 PunchCommerce® is a product of [ ![netzdirektion | Gesellschaft für digitale Wertarbeit mbH](https://www.punchcommerce.de/static/netzdirektion-logo.png) (opens in a new window) ](https://netzdirektion.de) ![DEKRA seal: quality management according to ISO 9001](https://www.punchcommerce.de/static/dekra-netzdirektion-iso-9001.png) **ISO 9001:2015**
certified quality management

 netzdirektion | Gesellschaft für digitale Wertarbeit mbH · © 2020 - 2026
