cXML for SAP Business Network: 7 proven steps to avoid broken supplier integrations

cXML is the language SAP Business Network, formerly Ariba Network, uses to move purchase orders, order confirmations, ship notices and invoices between buyers and suppliers without anyone retyping them. If your company supplies a large buyer that runs SAP Ariba, your ERP or middleware may already use it, and a single quarterly release can quietly break it. This guide explains how it works, what SAP Business Network releases change, and seven proven steps to keep your integration running.

Key takeaways:

• SAP Business Network ships quarterly releases named by year and month, for example 2611 for November 2026.
• The 2611 release, planned for 13 November 2026, adds support for cXML DTD version 1.2.072 and needs no system downtime.
• New DTD versions are usually supported first and made mandatory later: version 1.2.071 was supported from the 2605 release and became required with 2608.
• Suppliers working only in the web portal see little change. Suppliers with a direct integration or punchout connection should test every release.

What is cXML?

cXML (commerce eXtensible Markup Language) is an open, XML-based protocol for business-to-business e-commerce. Ariba introduced it in 1999, and the specification and DTD files are published at the official cXML site. Every cXML document follows a Document Type Definition (DTD), a formal description of which elements and attributes a document may contain and in what order. When a buyer’s procurement system sends an order, the supplier’s system reads the XML, checks it against the DTD and turns it into a sales order in its own ERP.

The documents suppliers meet most often on SAP Business Network are:

• PunchOutSetupRequest: opens a punchout catalog session from the buyer’s procurement system.
• OrderRequest: the purchase order.
• ConfirmationRequest: the supplier’s order confirmation.
• ShipNoticeRequest: the advance ship notice.
• InvoiceDetailRequest: the invoice.

Each document starts with a DOCTYPE line that points to a specific DTD version, such as http://xml.cxml.org/schemas/cXML/1.2.072/cXML.dtd, and a header with the sender’s and receiver’s credentials. That version number is what matters when SAP announces a new release.

How suppliers connect to SAP Business Network: portal, cXML or EDI

A supplier can work with SAP Business Network in three ways. The choice depends on order volume, the number of buyers on the network and the systems the supplier already runs.

Option	How it works	Best for
Ariba supplier portal	Staff log in and process orders and invoices by hand in the browser.	Low volumes and one or two buyers.
cXML integration	The ERP or middleware exchanges cXML documents automatically over HTTPS.	Medium to high volumes, punchout catalogs, several buyers.
EDI	ANSI X12 or EDIFACT messages are exchanged through SAP Business Network’s EDI support.	Suppliers already running EDI with other customers.

Most suppliers start in the Ariba supplier portal. Once a buyer sends dozens of orders a week, manual entry becomes slow and error-prone, and the supplier moves to an automated integration. From that moment, SAP’s release calendar becomes part of the supplier’s IT calendar too.

What SAP Business Network quarterly releases mean for cXML

SAP Business Network releases are named after the year and month: 2602, 2605, 2608 and 2611 for 2026. The 2611 release is planned for Friday, 13 November 2026, starting at 5:00 pm Pacific Time, and SAP says it requires no downtime. With it, SAP Business Network will support DTD version 1.2.072, and a pre-release version of the DTD is available in advance for organisations that cache the DTD locally. Release materials are collected in the SAP Business Network Supplier Readiness Portal.

The previous cycle shows the pattern to expect. DTD 1.2.071 was supported from the 2605 release, and the pre-release notes for cXML 1.2.071 state that it became required for SAP Business Network for Procurement, Supply Chain and Trading Partners at the 2608 release. If SAP follows the same pattern, version 1.2.072 will become required in a later release. Check the readiness portal for the actual date rather than assuming it.

“Required” matters because buyers and the network may start sending documents that use elements or attribute values introduced in the new DTD. A supplier system that validates strictly against an older DTD stored on its own server can then reject documents that are perfectly valid.

Why cXML integrations break after a release

In our experience with inherited integrations, failures after a release rarely come from SAP itself. They come from assumptions built into the supplier’s side of the connection:

• A locally cached DTD. The XML parser validates against an old file and rejects documents with new elements.
• A hard-coded DTD version in outgoing documents, which stays frozen for years until the network stops accepting it.
• Rigid mappings in middleware. New optional fields or extrinsic values break the mapping or are silently dropped.
• Changed credentials or certificates that nobody updated in the integration configuration.
• Punchout changes on the buyer side, so the shopping cart no longer returns to the buyer’s system.
• No monitoring. Failed documents sit in an outbox, and nobody notices until a buyer asks why an invoice never arrived.

The last one is usually the most expensive. An invoice that never reaches SAP Business Network is an invoice that does not get paid on time.

7 proven steps to keep your cXML integration working

1. Map what you exchange. List every document type you send and receive, for which buyers, and through which system or middleware. Many suppliers discover document types nobody documented.
2. Find where the DTD lives. Check whether your parser loads the DTD from the cXML site or from a local copy, and which version your outgoing documents declare.
3. Read the release notes early. Each quarter, review the readiness portal and the DTD pre-release notes for new or changed elements that affect your documents.
4. Test with real samples. Run your most common orders, confirmations, ship notices and invoices through a test account before the release date, using the new DTD.
5. Check punchout end to end. Open a punchout session from the buyer side, add items, return the cart and confirm the order arrives correctly.
6. Monitor after go-live. For the first days after a release, watch error queues and document status in SAP Business Network, and compare document counts with a normal week.
7. Own the calendar. Name one person responsible for each release, with a deputy, and keep a short log of what was tested and what changed.

None of these steps is complex. The integrations that fail are usually the ones where nobody owns them anymore: the developer who built them has left, the middleware vendor has changed and the documentation lives in someone’s old inbox.

cXML vs EDI: which should a supplier choose?

cXML and EDI solve the same problem with different tools. cXML is XML over HTTPS, readable by developers and native to SAP Business Network, which makes it the natural choice for punchout catalogs and for suppliers whose first big buyer is on SAP Ariba. EDI standards such as ANSI X12 and EDIFACT are older, very widespread in retail, automotive and logistics, and usually run through an EDI provider.

If you already exchange EDI with most of your customers, adding SAP Business Network through EDI keeps one set of tools. If SAP Business Network is your main channel, or buyers want punchout, cXML is usually simpler to build and maintain. In both cases the same rule applies: someone has to own the integration and test it when the network changes.

Punchout catalogs: the cXML feature buyers ask for

A punchout catalog lets a buyer’s employee leave their procurement system, shop in the supplier’s own web catalog with negotiated prices, and return the cart to the procurement system for approval. Behind the scenes, this runs on cXML: a PunchOutSetupRequest opens the session and a PunchOutOrderMessage sends the cart back.

For suppliers, punchout is often what wins or keeps a large account, because buyers prefer catalogs that are always up to date. It is also the most fragile part of the integration, since it touches the supplier’s web shop, pricing and the buyer’s configuration at once. Test it first after every release.

How Sanddev helps suppliers with cXML integrations

Sanddev builds and maintains integrations between ERP systems, web shops and platforms such as SAP Business Network. We map existing document flows, update DTD handling, build punchout catalogs and set up monitoring, so a quarterly release becomes a checklist instead of an incident. See how our integration and advisory work is organised. If the integration was built by a vendor who is no longer around, we can also take over an integration nobody fully understands and document it before the next release.

Frequently asked questions about cXML and SAP Business Network