Lapasar

Buyer Guide

How to Add a PunchOut Supplier in SAP Ariba

A buyer-admin walkthrough of enabling a punchout supplier in SAP Ariba — from trading relationship to a tested, published catalogue.

WhatsApp us rfqme@lapasar.com
How to Add a PunchOut Supplier in SAP Ariba
Buyer Guide

To add a punchout supplier in SAP Ariba, the buyer organisation establishes a trading relationship with the supplier on the Ariba Network (formerly SAP Business Network), exchanges cXML credentials — the From/To identities, shared secret and the supplier's PunchOutSetupRequest URL — then loads the supplier's punchout index catalogue file, validates and tests the session in the test realm, and publishes the catalogue so requisitioners can shop it from Guided Buying. Suppliers like Lapasar handle their side of the configuration and support testing end to end.

What you need before you start

Punchout enablement in Ariba is mostly an exchange of identities and URLs, so most of the elapsed time is coordination rather than configuration. Before starting, have your Ariba Network ID (ANID) to hand, know which realm you are working in (test vs production), and confirm who on the supplier side owns punchout configuration.

With Lapasar, the supplier side is handled by a dedicated integration team: credentials, the punchout index file, organisation-specific catalogue views and contract pricing are prepared for you, and testing is supported end to end until carts return cleanly.

  • Your Ariba Network ID and realm details
  • cXML identities and shared secret agreed with the supplier
  • The supplier's punchout index catalogue file (CIF or cXML)
  • A test user with requisitioning rights in the test realm

Common issues and how to avoid them

Most failed punchout sessions trace back to credential mismatches — the From/To identities or shared secret differ between the buyer and supplier configuration. Validate these first when a PunchOutSetupRequest is rejected. The second most common issue is catalogue file validation errors, usually a malformed field in the CIF or cXML index file. Finally, confirm the cart's unit-of-measure and currency mappings early: mismatches surface as requisition line errors after checkout, which are slower to debug.

Adding a punchout supplier in SAP Ariba, step by step

The typical buyer-admin sequence for enabling a punchout catalogue in SAP Ariba. Exact screens vary by Ariba release and configuration, but the flow is consistent.

  1. 1Establish the trading relationshipInvite the supplier to connect with your buyer account on the Ariba Network (SAP Business Network), or accept the supplier's existing relationship request. Punchout enablement runs on top of this relationship.
  2. 2Exchange cXML credentials with the supplierAgree the cXML From/To/Sender identities, the shared secret and the supplier's punchout endpoint (the URL that receives the PunchOutSetupRequest). The supplier configures the same values on their side.
  3. 3Obtain the supplier's punchout catalogue fileFor a Level 1 catalogue this is a small index file (typically CIF or cXML format) containing a single punchout item that points at the supplier's storefront; Level 2 catalogues include item-level index entries.
  4. 4Load and validate the catalogue in AribaIn your buyer account's catalogue administration, create or update the catalogue subscription, upload the file, and let Ariba validate it — syntax errors and credential mismatches surface here.
  5. 5Test the punchout session in the test realmFrom a test requisition, click into the catalogue: confirm the session opens, contract pricing displays, and the cart returns to Ariba as requisition lines with correct prices, units and classification codes.
  6. 6Verify order transmissionApprove a test requisition and confirm the purchase order transmits to the supplier (typically as a cXML OrderRequest) and that the supplier acknowledges it.
  7. 7Publish to production and assign visibilityPromote the catalogue to your production realm, assign it to the right purchasing units or Guided Buying views, and communicate the new supplier to requisitioners.

Common questions

How do I add a punchout catalogue in SAP Ariba?
Establish a trading relationship with the supplier on the Ariba Network, exchange cXML credentials (identities, shared secret and punchout URL), load the supplier's punchout index catalogue file into your catalogue administration, test the session and cart return in your test realm, then publish the catalogue to production and assign it to the right purchasing views.
What is the difference between a CIF catalogue and a punchout catalogue in Ariba?
A CIF (Catalog Interchange Format) file is a static list of items and prices loaded into Ariba. A punchout catalogue uses a small index file — often in CIF or cXML format — containing a punchout item that links out to the supplier's live store instead of holding items statically. Punchout keeps pricing and stock live; static CIF files need re-uploading whenever they change.
How long does punchout enablement in Ariba take?
With a punchout-ready supplier, enablement is typically measured in weeks. The main variables are credential coordination and testing availability — the supplier-side setup, index file and catalogue views are usually prepared within days.
Is Lapasar punchout-ready for SAP Ariba?
Yes. Lapasar supports Level 1 and Level 2 cXML PunchOut with SAP Ariba, provides the punchout index file and credentials for your realm, and its integration team supports validation and testing end to end.

Didn't find your answer?

Ask us directly — WhatsApp or email, whichever suits you.

WhatsApp us rfqme@lapasar.com

Enable a punchout-ready supplier

Lapasar arrives punchout-ready for SAP Ariba — credentials, index file and testing handled by our integration team.

Prefer to talk to a real person?

Our team replies fast on WhatsApp and email — no forms, no waiting.

WhatsApp us rfqme@lapasar.com

Related

IntegrationSAP Ariba PunchOut SupplierHow-toAdd a PunchOut Supplier in CoupaGuidecXML & OCI PunchOut Integration ExplainedIntegrationPunchout & ERP Integration in Malaysia

Written by Lapasar Procurement Technology · Procurement Technology & Integration (https://lapasar.com/team/lapasar-procurement-technology)