Setting up PunchOut in SAP Ariba® | PunchCommerce                       ![](//analytics.punchcommerce.de/matomo.php?idsite=1&rec=1)

  [Skip to content](#main-content)

Setting up PunchOut in SAP Ariba®
=================================

In a PunchOut Level 1, the supplier does not provide individual items in SAP Ariba®, but only a single catalogue entry (index file in CIF format). This entry appears as a tile to the buyer, e.g. in Guided Buying. Clicking on it launches the PunchOut to your online shop. Items, prices and the shopping basket continue to be retrieved in real time from the shop via PunchCommerce.

> **Note**: A static CIF catalogue (all items as a file) is not a PunchOut. When your customer requests a PunchOut catalogue, they are referring to the direct interface between their Ariba and your shop via cXML (or OCI). For a direct link to product detail pages (Level 2), see CIF catalogue generation for gateway customers (Level 2).

The basic technical setup (PunchOut configuration, template for the Level 1 index file, testing in the Ariba test account) is described in the article ‘Setting up PunchOut in SAP Ariba®’. This article covers the production deployment at the buyer’s end.

Prerequisites
-------------

- An SAP Business Network account (supplier account) at [supplier.ariba.com](https://service.ariba.com/). A standard account licence is sufficient.
- A trading relationship with the buyer on the Ariba Network. Usually, the buyer sends an invitation. Once this has been accepted, your account is linked to the buyer’s account.
- Your ANID (Ariba Network ID, format AN…) and the buyer’s Buyer Identity. Both values are required for configuration in PunchCommerce.
- A customer set up in PunchCommerce with the cXML protocol and the Gateway module. For Shopware 6, the PunchCommerce plugin is also required.

Step 1: Obtain buyer-specific requirements
------------------------------------------

Many buyers, particularly public sector clients and large corporations, have their own specifications for supplier catalogues. Before setting up, clarify the following:

RequirementExampleNaming convention for the catalogueSupplier name\_Country\_Product group DE – Product group FRClassification system including versionUNSPSC 13.5Permitted units of measureEA, PK, CT, LTR, KGM …Testing optionsIs there a connected test environment at the buyer’s site?You can maintain the product group and unit of measure mappings in PunchCommerce via the [Field Mappings](https://www.punchcommerce.de/de/documentation/feldzuordnungen). For information on the codes, see [ISO units of measurement](https://www.punchcommerce.de/de/documentation/iso-masseinheiten-uncefact) (UN/CEFACT) and [classification systems](https://www.punchcommerce.de/de/documentation/klassifizierungssysteme).

Step 2: Distinguish between test and production accounts
--------------------------------------------------------

Ariba strictly separates test and production accounts. This applies to both suppliers and buyers:

- A catalogue published in a test account is only visible if the buyer is also using a test environment linked to your test account.
- If this is not the case, the buyer will only see the catalogue if it is published in the production account.

> **Recommendation**: Agree with the buyer at an early stage which environment will be used for testing. This will prevent a successful test in the test account from having no effect on the buyer.

Step 3: Creating a PunchOut configuration in Ariba®
---------------------------------------------------

Go to the ‘Catalogues’ menu item and then to the ‘PunchOut Configuration’ menu item in the Ariba interface. Configure the “Level 1 Index File Template” and the default PunchOut configuration in accordance with our guidelines in the two screenshots below.

Placeholder values are often sufficient in the test account. However, for live publication, Ariba checks the index file against validation rules. Furthermore, its contents determine how the catalogue is displayed to the buyer. You should therefore ensure the following in the Level 1 Index File Template in particular:

- Supplier name: Must be filled in. If this value is missing, publication will fail with a validation error (see Troubleshooting).
- Catalogue or item name / short description: This text is displayed to the user in Guided Buying. Use the buyer’s naming convention.
- Image: A publicly accessible URL via HTTPS to your logo. This image appears on the catalogue tile.
- Commodity code in accordance with the buyer’s classification.

> **Important**: The company logo in your Ariba company profile is not automatically used for the catalogue tile. The details in the index file or the buyer’s display settings take precedence.

**Note on the index template:** You can leave the “Image” and “Overview” fields blank.

**Note on PunchOut configuration**

![SAP Ariba® PunchOut Configuration Overview](https://www.punchcommerce.de/storage/media/support-articles/ariba-einrichtung-als-lieferant/1.png)

![SAP Ariba® PunchOut Configuration – Editing](https://www.punchcommerce.de/storage/media/support-articles/ariba-einrichtung-als-lieferant/2.png)

Step 4: Create a catalogue for cXML PunchOut in Ariba®
------------------------------------------------------

1. In the production account, under Catalogues, create a PunchOut catalogue with PunchOut Level 1.
2. Apply the configuration that has been successfully tested in the test environment.
3. Select ‘Private’ mode and the buyer for whom the catalogue is to be published.
4. Publish the catalogue and check the validation status.

![Create an SAP Ariba® PunchOut catalogue](https://www.punchcommerce.de/storage/media/support-articles/ariba-einrichtung-als-lieferant/3.png)

![Publish an SAP Ariba® PunchOut catalogue for customers](https://www.punchcommerce.de/storage/media/support-articles/ariba-einrichtung-als-lieferant/4.png)

Buyer approval
--------------

Every published catalogue version must be approved by the buyer before it is visible to end users. This also applies to corrections, such as a changed name or logo. You should therefore actively inform the buyer when you have uploaded a new version.

The buyer will then integrate the catalogue into their procurement system, e.g. Guided Buying.

Step 6: Test access to the PunchOut catalogue from Ariba®
---------------------------------------------------------

Carry out a full test run together with the buyer:

1. Access the catalogue from the buyer’s procurement system (PunchOut login via PunchCommerce)
2. Fill the shopping basket in the online shop
3. Transfer the shopping basket back to Ariba (check product groups and units of measure)
4. Optional: Test order; see Processing cXML Orders

![Testing the SAP Ariba® PunchOut catalogue](https://www.punchcommerce.de/storage/media/support-articles/ariba-einrichtung-als-lieferant/5.png)

![SAP Ariba® access to PunchCommerce®](https://www.punchcommerce.de/storage/media/support-articles/ariba-einrichtung-als-lieferant/6.png)

![Transferring the shopping basket from PunchCommerce® to SAP Ariba®](https://www.punchcommerce.de/storage/media/support-articles/ariba-einrichtung-als-lieferant/7.png)

Bug fixes
---------

SymptomCauseSolutionPublication fails: “Items in the catalogue file have failed some validation rules”, Supplier Name field \[Unknown\]Supplier name is missing from the index file or is invalidMaintain the supplier name in the Level 1 template, republish the catalogueThe buyer cannot see the catalogue in the test systemCatalogue published only in the test or production account; the buyer is using the other environmentCoordinate the environment with the buyer (see Step 2)Catalogue appears in Guided Buying with the wrong name, e.g. the buyer’s nameName not maintained or incorrectly maintained in the index fileSet the name in accordance with the naming convention, publish a new version, obtain approval from the buyerCatalogue appears without a logoNo image stored in the index file (logo in the company profile is not sufficient)Maintain the logo URL in the index file, publish a new version, and obtain approval from the buyer. If necessary, the buyer can also adjust the display in Guided BuyingCorrection is not visible to the buyerNew catalogue version not yet approvedAsk the buyer for approvalNotes on collaboration
----------------------

- Do not send access details (e.g. shop logins for the PunchOut user) by email. With the PunchCommerce gateway, the buyer generally does not need their own shop access details, as login takes place automatically via PunchOut.
- Arrange a joint meeting with the buyer or their implementation partner for the live launch. This allows the launch, approval and final testing to be completed in a single step.

If you have any questions or encounter any problems, please contact our [Support](https://www.punchcommerce.de/de/documentation/kontakt).

 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
