PUBLIC

Document Version: 2502 – 2025-02

EDI Configuration Guide

© 2025 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

EDI Configuration Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Introduction to EDI on SAP Business Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

EDI Document Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
VAN Transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
About Incoming Document Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
About Outgoing Document Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
About Inovis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
EDIINT AS2 Transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Incoming Document Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Outgoing Document Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Document Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Single Data Map for Each Document Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Data Preservation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
EDI Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Implementation Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
SEF Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
SAP Business Network Account Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuration Tasks for EDI Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
SAP Ariba EDI Integration Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Supported EDI Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Document Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Functional Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Order Confirmations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Ship Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Remittance Advice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Quality Inspection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Requirements for Functional Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Allotted Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Transaction-Level Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Acknowledging Failed Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Other Ways to Acknowledge Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

EDI VAN Configuration and Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Subscriptions That Provide Unlimited EDI Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

EDI Configuration Guide

2 PUBLIC Content
 About Configuring Your SAP Business Network Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Identifying Your EDI Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Configuring Your EDI Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Using Multiple Routing Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
EDI Interconnect from Your VAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
EDI Interconnect from SAP Ariba. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Requesting an EDI Interconnect from Ariba. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configure Your EDI Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configure Your Data Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Specify the SAP Business Network’s Interchange IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Identify Your Customers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Looking Up Customer Ariba Network IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Detect Test/Production Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Test on Your Own. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Send Functional Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Check Order-Routing Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Testing ANSI X12 EDI Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Test with Customers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Request Test Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Checking Basic Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Viewing cXML Source Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Recognize and Use Extrinsic Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Extrinsic Data Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Default Extrinsic Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Send Functional Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Send Order Confirmations, Ship Notices, and Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Switch to Production Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Switching to Production Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

EDIINT AS2 Routing Configuration and Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

EDIINT AS2 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Digital Certificate Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
EDIINT AS2 Information to Send to SAP Product Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Configuring Your EDIINT AS2 Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Test and Deploy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Troubleshooting EDI Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

If Orders Do Not Appear in Your SAP Business Network Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Check for Received Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Check Buyer Integration with SAP Business Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Check Your ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
If Orders Do Not Appear in Your EDI System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

EDI Configuration Guide

Content PUBLIC 3
 Check Order History on SAP Business Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Verify Your EDI Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Check for Other Common Order-Routing Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Interconnect Not Set Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Missing Required Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Non-Compliant Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Functional Acknowledgement Overdue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
If Your EDI System Issues Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Verify the EDI Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Check for Extrinsic Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Check Your Customers’ IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Check Test/Production Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
If Functional Acknowledgement Does Not Update Order Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Check Test/Production Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Check the ID of Buying Organizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Check Reference to Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Obtain Additional Help with Functional Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
If Invoices Do Not Appear in Your SAP Business Network Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Check for Translation Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Check for cXML Validation Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Check Your Customers’ Invoice Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Check References to Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Example Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

cXML OrderRequest Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
X12 850. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
X12 997. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
EDIFACT ORDERS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
EDIFACT CONTRL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Support for X12 and EDIFACT Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Purchase Order Contact Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
cXML Source Data for Contact Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
ANSI X12 850 Example Contact Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
EDIFACT ORDERS Example Contact Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Purchase Order Extrinsics to REF Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Additional References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Invoice REF/RFF Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
ANSI X12 REF Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
EDIFACT RFF Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Unsupported Segments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Unsupported ANSI UOMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

EDI Configuration Guide

4 PUBLIC Content
 Additional References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

EDI Configuration Guide

Content PUBLIC 5
EDI Configuration Guide

This guide describes how to configure your SAP Business Network account for EDI document routing.

This guide applies to:

• SAP Business Network

• SAP Business Network for Supply Chain

Related Guides

Configuring Document Routing

EDI Configuration Guide

6 PUBLIC EDI Configuration Guide
Introduction to EDI on SAP Business Network

The SAP Business Network supports Electronic Data Interchange (EDI) document routing along with other routing
methods, such as fax, email, and cXML.

EDI Document Flow [page 7]

Document Mapping [page 12]

SAP Business Network Account Prerequisites [page 14]

Configuration Tasks for EDI Routing [page 14]

SAP Ariba EDI Integration Resources [page 15]

EDI Document Flow

The EDI routing method enables you to automate order processing and connect your order management, shipping,
and invoicing systems with your customers through SAP Business Network.

To integrate your EDI order receiving system successfully with SAP Business Network, you need to know:

• How documents flow through SAP Business Network. Document flow is bidirectional (incoming and outgoing).
• About transport methods: Value Added Network (VAN), and routing over the Internet (EDIINT AS2).

Buying organizations (your customers) generate electronic purchase orders and payment remittance in their
procurement solution, which transmits them to SAP Business Network as Commerce Extensible Markup Language
(cXML) documents.

You send outgoing documents such as order confirmations, ship notices, invoices, and functional
acknowledgments back to your customers. SAP Business Network converts those EDI documents to cXML as
it routes them.

SAP Business Network supports two transports for EDI documents: VAN (Value Added Network) and EDIINT AS2
(EDI over the Internet). You decide which transport to use when you configure your SAP Business Network account.

EDI Configuration Guide

Introduction to EDI on SAP Business Network PUBLIC 7
VAN Transport

You can configure your SAP Business Network account to use VAN-to-VAN interconnects to route EDI documents.
SAP Business Network uses an EDI mailbox on the Inovis VAN.

About Incoming Document Flow

SAP Business Network supports routing of incoming purchase orders (POs) and payment remittances in cXML
from your customer’s procurement solution to your EDI system using VAN-to-VAN.

The following procedure describes the flow of PO from your customer’s procurement solution to your EDI system:

Figure 1: Incoming Purchase Order From Buyer To Supplier

1. Your customer (buyer) generates a cXML PO OrderRequest using his procurement solution and sends it
securely over the Internet to SAP Business Network.
2. SAP Business Network receives the cXML PO and stores a copy of it in your customer’s SAP Business Network
Outbox and in your SAP Business Network Inbox.
3. SAP Business Network translates the cXML PO into an X12 850 or EDIFACT ORDERS document, depending on
your order-routing settings.
4. SAP Business Network sends the EDI document securely over the Internet to your inbox on Ariba Network's
VAN (INOVIS).
5. Ariba Network's VAN (INOVIS) receives the EDI document and sends it to the inbox on your VAN.
6. Your VAN stores the EDI document for manual or automatic retrieval.
You retrieve EDI documents using the medium your VAN supports (private telephone lines). You use EDI
retrieval and translation software to read your EDI mailboxes and translate orders for your order-fulfillment
system.

About Outgoing Document Flow

SAP Business Network supports routing of outgoing order confirmations, ship notices, invoices, and functional
acknowledgments from your EDI system to your customer’s procurement solution using VAN-to-VAN.

The following procedure describes the flow of invoice from your EDI system to your customer’s procurement
solution:

EDI Configuration Guide

8 PUBLIC Introduction to EDI on SAP Business Network
 Figure 2: Outgoing Invoice From Supplier To Buyer

1. You generate an X12 810 or EDIFACT INVOIC document using your EDI system and send it to the outbox on
your VAN.
2. Your VAN forwards the document to your outbox on Ariba Network's VAN (INOVIS).
3. Ariba Network's VAN (INOVIS) directs the EDI document securely over the Internet to SAP Business Network.
4. SAP Business Network receives the EDI document and translates it into a cXML invoice.
5. SAP Business Network stores a copy of the cXML invoice in your SAP Business Network Outbox and your
customer’s SAP Business Network Inbox.
6. SAP Business Network sends the cXML invoice to a download queue for your customer (buyer).
7. Your customer’s procurement solution periodically queries SAP Business Network for new documents and
downloads them securely over the Internet if any are waiting.

About Inovis

SAP Business Network uses the Inovis, Inc. VAN for EDI document routing. Inovis (subsidiary of OpenText) has
provided B2B solutions to the world's most successful companies since 1984. The Inovisworks network provides
mission critical and flexible connectivity to electronic B2B trading communities.

EDIINT AS2 Transport

You can configure your SAP Business Network account to route EDI over the Internet (EDIINT AS2). SAP Business
Network uses Secure Hypertext Transfer Protocol (HTTPS) on the Internet to communicate directly to your EDIINT
AS2 server and it encrypts the transport so that only their intended recipient can read them.

EDIINT AS2 transport offer the following advantages:

• Transmit EDI documents securely and seamlessly using its own communication protocols
• Improve business processes and reduce transaction turnaround time
• Enhance efficient communication with customers
• Reduce manual data entry which in turn eliminates errors
• Leverage the Internet and help reduce the high cost of installation and maintenance

EDI Configuration Guide

Introduction to EDI on SAP Business Network PUBLIC 9
Related Information

EDI VAN Configuration and Testing [page 21]

Incoming Document Flow

When you use EDIINT AS2 to route incoming EDI purchase order and remittance advice from your customers, they
generate their documents and send them to Ariba Network for translation (into an ANSI X12 850 or UN EDIFACT
ORDERS document) and routing to your AS2 server.

Figure 3: EDIINT AS2 Incoming Document Flow

The following steps describe the incoming document flow in more detail:

1. Your customer generates a purchase order as a cXML OrderRequest using his procurement solution and
sends it securely over the Internet to SAP Business Network.
2. SAP Business Network receives the document and stores a copy of it in your customer’s SAP Business
Network Outbox and in your SAP Business Network Inbox.
3. SAP Business Network translates the OrderRequest into an ANSI X12 850 document or a UN EDIFACT
ORDERS document, depending on your order-routing settings.
4. SAP Business Network sends the EDI document securely through the Internet to your EDIINT AS2 server.

EDI Configuration Guide

10 PUBLIC Introduction to EDI on SAP Business Network
Outgoing Document Flow
When you route outgoing EDI documents such as functional acknowledgements, order confirmations, ship notices,
and invoices to your customers, you generate an EDI document on your system, send it securely over the Internet
to SAP Business Network for translation into a cXML document, and put it into the customer’s download queue.

Figure 4: EDIINT AS2 Outgoing Document Flow

The following steps describe the outgoing document flow in more detail:

1. You generate an EDI invoice using your EDI system and send it to SAP Business Network securely over the
Internet.
2. SAP Business Network receives it and translates it to a cXML invoice.
3. SAP Business Network applies any order status information to the purchase order and its line items displayed
online. It stores a copy of the invoice in your SAP Business Network Outbox and your customer’s SAP Business
Network Inbox.
4. SAP Business Network sends the cXML invoice to a download queue for your customer.
5. Your customer's procurement solution periodically queries SAP Business Network for new documents and
downloads them if any are waiting.

EDI Configuration Guide

Introduction to EDI on SAP Business Network PUBLIC 11
Document Mapping
When SAP Business Network routes documents between you and your customers, it translates them between
cXML and EDI and then maps data between these formats. You must understand outbound document
requirements because your customers’ procurement systems must process them without human intervention.

Single Data Map for Each Document Type

SAP Business Network uses a single data map for each EDI document type. For example, there is a single data map
for translating cXML purchase orders to X12 purchase orders. You must adhere to these data maps when receiving
or transmitting EDI documents.

SAP Business Network does not support custom implementations, custom mappings, or per-supplier mappings.
By requiring you to use a single set of data maps, SAP Business Network makes it easy for you to integrate with
additional customers after your initial configuration.

Data Preservation

SAP Business Network maps EDI documents to or from cXML. This mapping dictates a set of required fields and
segments that you must interpret and populate.

When Ariba Network maps data between cXML and EDI documents, it passes as much of the original data as
possible. For example, an EDI purchase order is as complete a rendering of a cXML OrderRequest that can be
produced within the confines of the X12 or EDIFACT languages. EDI documents derived from cXML documents
might contain other content, such as currency declarations, redundant postal addresses, or text comments, if that
data is present in the original document.

EDI Documentation

EDI documentation consists of PDF guides that provide specific EDIFACT and ANSI X12 implementation resources
that describe the fields and segments you need to interpret and populate for your EDI documents. You should also
become familiar with Standard Exchange Form (SEF) files.

This documentation describes the cXML/EDI mapping performed by SAP Business Network and data
requirements. It is available to both buying organizations and suppliers.

EDI Configuration Guide

12 PUBLIC Introduction to EDI on SAP Business Network
Implementation Guides

SAP Business Network provides separate implementation guides for each EDI document type. Use these guides
to understand how to interpret incoming documents and generate valid outgoing documents. These guides are
required reading for suppliers who want to implement EDI.

EDI implementation guides are updated when there is a change to the existing EDI mapping. When changed, the
revision date for each document is also updated. You can find the revision date in the footer of the document.

 Note

Most EDI routing problems occur when suppliers fail to comply with the requirements described in these
guides.

Additional References

To access the EDI documentation, go to the Product Documentation For Administrators EDI Integration
section of the Learning Center.

SEF Files

SEF is an open, machine-readable standard for defining specific implementations of EDI transaction sets. Many EDI
applications can use SEF files to validate incoming and outgoing documents. You can use them to ensure you are
generating documents that meet SAP Business Network EDI guidelines.

Additional References

If you are implementing EDI using EDIFACT, go to the Product Documentation For Administrators EDI
Integration EDIFACT Implementation Resources ARIBA D98A DESADV SEF/D98A SEF sections of the
Learning Center.

If you are implementing EDI using ANSI X12, go to the Product Documentation For Administrators EDI
Integration ANSI X12 Implementation Resources ARIBA 4010 SEF/820 SEF sections of the Learning
Center.

EDI Configuration Guide

Introduction to EDI on SAP Business Network PUBLIC 13
SAP Business Network Account Prerequisites
Before you can configure your SAP Business Network account for EDI document routing you must have a fully
enabled account with sufficient permissions.

A fully enabled account on SAP Business Network is one that has at least one trading relationship with a buying
organization. After a trading partner confirms your account, SAP Business Network sends you a notification
indicating that your account is fully enabled and you can begin transacting.

SAP Business Network account administrators have all available permissions for configuring EDI document
routing. Other users must have the following permissions:

This permission… Allows users to…

Contact Administration Maintain information about contact personnel

Transaction Configuration Configure electronic transactions

Catalog Management Upload and test customer catalogs

Outbox Access View and search documents in the Outbox tab and take action
based on your role

Inbox Access View and search documents in the Inbox tab and take action
based on your role

 Note

If you don't already have an SAP Business Network subscription that lets you automate the submission and
receipt of orders and invoices, upgrade your subscription before you implement EDI document routing.

Configuration Tasks for EDI Routing

Configuring your SAP Business Network account for EDI document routing involves setting up a test environment
to ensure proper document flow, and then moving your tested implementation to your production environment.

EDI document routing configuration steps are:

1. Configure your SAP Business Network test account

Set parameters for EDI routing in your test account.
2. Request an interconnect from your VAN
Ask your VAN provider to enable communication with SAP Business Network’s VAN, INOVIS. (This is not
applicable for EDIINT AS2 customers.)
3. Request an interconnect from SAP Business Network
Ask Ariba to enable communication with your VAN. (This is not applicable for EDIINT AS2 customers.)
4. Configure your EDI application
Enable your EDI system to map incoming data and send functional acknowledgements.

EDI Configuration Guide

14 PUBLIC Introduction to EDI on SAP Business Network
5. Test on your own
Use SAP Business Network’s catalog tester to check basic communication between SAP Business Network
and your EDI system and verify that your system can process orders.
6. Test with customers
Verify that your EDI system can process test orders from your customers forwarded by SAP Business Network.
7. Switch to production
Propagate your test configuration to your production SAP Business Network account and inform your
customers you can receive production orders through EDI.

Allow adequate time to implement and test EDI integration with SAP Business Network and your customers before
switching to production. A reasonable estimate for implementation and testing is two to three weeks, depending on
the business complexity of the documents you receive and transmit.

Related Information

EDI VAN Configuration and Testing [page 21]

SAP Ariba EDI Integration Resources

When you implement EDI, there are different resources available to you for information about configuration and
troubleshooting, and optionally you can engage SAP Ariba Supplier Services for consultation and integration work
at all levels of EDI implementation.

Available resources include:

Information Type Resource Link

Configuration and testing steps • EDI VAN Configuration and Testing [page 21]
• EDIINT AS2 Routing Configuration and Testing [page 37]

Troubleshooting guidelines Troubleshooting EDI Problems [page 41]

EDI document implementation guides Implementation Guides [page 13]

EDI applications that recognize SEF files SEF Files [page 13]

EDI Configuration Guide

Introduction to EDI on SAP Business Network PUBLIC 15
Supported EDI Documents

SAP Business Network supports two major EDI document formats: ANSI ASC x12 version 004010, and UN
EDIFACT version D98A with syntax version 3.

EDI Languages

SAP Business Network supports EDI document types required for commerce between you and your customers.
You select the EDI language to use for your implementation.

Ariba Network supports the following EDI languages:

• ANSI ASC X12 version 004010

American National Standards Institute Accredited Standards Committee X12
• UN EDIFACT version D98A with syntax version 3
United Nations Electronic Data Interchange For Administration Commerce And Transport

Ensure that your EDI system is configured for the exact version listed above.

Maximum Interchange Size

EDI interchanges must be smaller than 60 MB. Ariba Network rejects interchanges that exceed this limit. If you
have more than 60 MB of data to transmit to Ariba Network, break it into multiple interchanges.

Related Information

Document Types [page 16]

Requirements for Functional Acknowledgments [page 20]

Document Types
Ariba Network supports the EDI documents that correspond to purchase orders, functional acknowledgements,
order confirmations, ship notices, invoices, and remittance advice.

Some of these documents are optional. The business rules you establish with your customers determine which
documents you receive and send.

EDI Configuration Guide

16 PUBLIC Supported EDI Documents
Purchase Orders

Procurement applications send purchase orders to SAP Business Network as cXML OrderRequest documents.
SAP Business Network translates them into the corresponding EDI document depending on the EDI language you
use.

Purchase orders are one of the following types, depending on the EDI language you implement:

ANSI X12 850 (Purchase Order)

EDIFACT ORDERS (Purchase Order)

Purchase orders describe a request for goods and services. They are also used for change and cancel orders,
that replace the original purchase order. After receiving a change or cancel order, you must send a functional
acknowledgment.

SAP Business Network keeps purchase order attachments in your online Inbox, because it cannot send them
through EDI. It adds an extrinsic element in the purchase orders to inform you that attachments reside in your
Inbox. Sign in to your account to view them.

Functional Acknowledgments

After you receive any document, you must send a functional acknowledgment in response. The acknowledgement
indicates that the document you received is functionally and syntactically correct.

Functional acknowledgements are one of the following types, depending on the EDI language you implement.

ANSI X12 997 (Functional Acknowledgment)

EDIFACT CONTRL (Syntax and Service Report Message)

These documents change the status of purchase orders on Ariba Network from “Sent” to “Acknowledged,” but they
are not confirmations of quantities or dates.

Related Information

Requirements for Functional Acknowledgments [page 20]

Order Confirmations

If you implement EDI with ANSI X12, then after you examine the contents of a purchase order, you can optionally
send an ANSI X12 855 (Purchase Order Acknowledgement) document to Ariba Network.

The order confirmation document sets the line item status in the purchase order on Ariba Network to “Accepted,”
“Rejected,” or “Backordered.” It can also specify estimated delivery dates. Buying organizations can configure Ariba
Network to convert order confirmations to cXML ConfirmationRequest documents and route them to their
procurement applications for display.

EDI Configuration Guide

Supported EDI Documents PUBLIC 17
Ship Notices

After you ship ordered items, you can optionally send a ship notice document to Ariba Network.

Ship notices are one of the following types, depending on the EDI language you implement.

ANSI X12 856 (Ship Notice/Manifest)

EDIFACT DESADV (Despatch Advice)

A ship notice document sets the line item status in the purchase order on Ariba Network to “Shipped.” It can also
specify carrier information. Buying organizations can configure Ariba Network to convert ship notices to cXML
ShipNoticeRequest documents and route them to their procurement applications for display.

Invoices

After you ship items or perform services, you can optionally send an invoice document to SAP Business Network.

Invoices are one of the following types, depending on the EDI language you implement:

• ANSI X12 810 (Invoice)

• EDIFACT INVOIC (Invoice)

Invoice documents create an invoice associated with one or more purchase orders or master agreements.
Buying organizations can configure SAP Business Network to convert invoices to cXML InvoiceDetailRequest
documents and route them to their procurement applications for reconciliation and payment.

You can send invoices only to customers that have enabled their SAP Business Network accounts to accept
invoices. To see a customer’s invoicing settings, go to the Customer Relationships page in the Administration tab
and click the customer’s name.

 Note

When generating invoices, do not use any of the units of measure codes listed in the Unsupported ANSI UOMs.

Related Information

Unsupported ANSI UOMs [page 63]

Additional References

You can send invoices to trigger Ariba Processing Plus (AP Plus) payment. If you are implementing
EDI using EDIFACT, go to the Product Documentation For Administrators EDI Integration EDIFACT
Implementation Resources INVOIC Implementation Guide in the Learning Center.

EDI Configuration Guide

18 PUBLIC Supported EDI Documents
If you are implementing EDI using ANSI X12, go to the Product Documentation For Administrators EDI
Integration ANSI X12 Implementation Resources 810 Invoice Implementation Guidelines in the Learning
Center.

Remittance Advice
If you implement EDI with ANSI X12, then buying organizations or Ariba Network can generate remittance advice
documents after sending payment to you.

Ariba Network translates a remittance advice into the ANSI X12 820 (Payment Order/Remittance Advice) EDI
document.

A remittance advice document describes payments, payment schedules, payment method, and financial
institution information. After you receive a remittance advice, you must respond with a functional
acknowledgment.

Quality Inspection

Suppliers on SAP Business Network can send and receive quality inspection documents through the Electronic
Data Interchange (EDI) routing method in the ASCX12 EDI863 document format.

Buyers integrated with SAP Business Network, SAP Business Network for Supply Chain for Buyers solution,
and SAP Integration Suite, managed gateway for spend management and SAP Business Network can
send suppliers a request to inspect the quality of goods (QualityInspectionRequest) sent by them. On
receiving the request, suppliers inspect the quality of goods and send the results of the quality inspection
(QualityInspectionResultRequest) to the buyer.

Along with cXML, another document format, ASCX12 EDI863, is supported to exchange the quality inspection
documents through the EDI routing method as well. The following cXML document types are supported:

EDI863 Inbound: QualityInspectionResultRequest

EDI863 Outbound: QualityInspectionRequest

EDI Configuration Guide

Supported EDI Documents PUBLIC 19
Requirements for Functional Acknowledgments
Functional acknowledgments (ANSI X12 997 or EDIFACT CONTRL documents) confirm the acceptance of
documents. Functional acknowledgements must be sent within 72 hours of document receipt, and must be sent at
a transactional level.

Allotted Time

Ariba Network must receive a functional acknowledgment within 72 hours after it sends a document. Otherwise it
considers the document to have failed to route and sets its status to “Failed.”

For your customers’ convenience, it is recommended that you send acknowledgments within 24 hours. If it has not
received a functional acknowledgement within 24 hours, SAP Business Network sends a warning message to the
email address for the EDI administrator you specified in the EDI Configuration page.

Transaction-Level Acknowledgments

You must generate transaction-level, not group-level functional acknowledgments. A transaction-level

acknowledgement references an individual document rather than a group of documents.

ANSI X12 997 functional acknowledgments must contain an AK2/AK5 segment for each document in the
functional group.

Similarly, EDIFACT CONTRL functional acknowledgments must contain a UCM segment for each document in the
interchange.

Acknowledging Failed Orders

After a document has failed, sending a functional acknowledgment does not set it to “Acknowledged.” You can
“manually” acknowledge a failed document.

To acknowledge a failed document, sign in to your SAP Business Network account, resend the failed document to
yourself, and return an acknowledgement. Make sure the resent document does not create a duplicate document in
your system.

Other Ways to Acknowledge Purchase Orders

You can acknowledge “Sent” or “Failed” purchase orders by sending invoices against them. You can use any
invoicing method: online, cXML, or EDI. SAP Business Network considers invoices to be acknowledgments and sets
purchase order status to “Acknowledged.”

EDI Configuration Guide

20 PUBLIC Supported EDI Documents
EDI VAN Configuration and Testing

Configuring EDI VAN on SAP Business Network is a multi-step process that involves setting up a test account to
make sure you and your customers can use the configuration before you deploy it for actual use.

To configure EDI VAN, perform the following procedures in this section.

Subscriptions That Provide Unlimited EDI Usage [page 21]

About Configuring Your SAP Business Network Account [page 21]

EDI Interconnect from Your VAN [page 25]

EDI Interconnect from SAP Ariba [page 26]

Configure Your EDI Application [page 26]

Test on Your Own [page 28]

Test with Customers [page 31]

Switch to Production Mode [page 35]

Subscriptions That Provide Unlimited EDI Usage

If you don't already have an SAP Business Network subscription that lets you automate the submission and receipt
of orders and invoices, sign up before configuring EDI VAN. Some subscriptions offer an enhanced level of support,
such as direct access to EDI support specialists, extended support hours, and guaranteed response times.

To sign up for an SAP Business Network subscription that includes EDI, click Company Account Settings at the
top of the home page and choose Service Subscriptions.

About Configuring Your SAP Business Network

Account
Configuring your account involves specifying an EDI administrator and configuring EDI (switching to a test account,
indicating your VAN, and choosing your EDI language).

After resolving any problems you encounter during testing, you configure your production account. Settings in your
test and production accounts are completely separate.

 Note

During testing you can receive production purchase orders through other routing methods, such as fax or
email.

EDI Configuration Guide

EDI VAN Configuration and Testing PUBLIC 21
Optionally, you can use different routing methods for incoming and outgoing communications.

Identifying Your EDI Administrator

You must identify an EDI Administrator who is responsible for setting up and maintaining your EDI processing
system and interacting with SAP Business Network should there be EDI configuration issues or processing
changes.

Context

SAP Business Network might need to contact your EDI administrator if there is a configuration problem or if EDI
processing changes in the future. Your customers might need to contact your EDI administrator if they change the
content of purchase orders, such as adding new extrinsic data.

Procedure

1. On the Home dashboard, click the Administration tab to display the User page.
2. Click Customer Contacts.
3. Click Create and enter the name, email address, and phone number of your EDI administrator.
4. Click Companywide Assignments. “EDI Administrator” is listed as a predefined category.
5. Click Edit for “EDI Administrator” and select the contact person you just entered.

Configuring Your EDI Settings

Configure EDI settings in your test account to resolve any issues before switching your production account to use
EDI routing.

Context

You can use EDI routing in your test account, but continue to receive actual customer orders in your production
account through another method, such as fax or email. When you finish testing and you are ready to use EDI in
production, change the order routing method in your production account to EDI.

EDI Configuration Guide

22 PUBLIC EDI VAN Configuration and Testing
Procedure

1. Sign in to your SAP Business Network account.

2. Go to your test account by clicking Switch to Test Account in the masthead.

This link is available only to account administrators. The first time you click the link, SAP Business Network
creates your test account and prompts you to assign a user name and password.
3. Click Manage Profile in the upper left corner of the home dashboard. The Configuration page opens.
4. Click Electronic Order Routing on the Company Profile page.
5. For “New Orders,” select EDI from the Routing Method list.
6. Click the Click here for Configuration link to display the EDI Routing Configuration page.
7. Fill out all the fields in the EDI Routing Configuration page.

Field Description Example

Value Added Network (VAN) The name of your EDI VAN. Sterling

Interchange Control Number Interchange sequence start number. The default is 100. 123

8. Select an EDI language: ANSI X12 or EDIFACT.

9. Fill in the configuration fields for the EDI standard you selected. Do not leave a field blank unless it is optional.

ANSI X12:

Field Description Example

Application (GS) ID The ID of your relationship. Used in GS03 (application re- 942888710
ceiver ID).

Functional Group Control Number Functional group sequence start number. The default is 456
100.

Interchange (ISA) Qualifier The domain of the ISA Identifier. 01 -DUNS

Interchange (ISA) Identifier The ID your VAN uses for your mailbox. 942888710

UN EDIFACT:

Field Description Example

Syntax Identifier The character encoding required for your locale and cus- UNOC-ISO
tomer catalogs. 8859-1:
Latin alphabet

Interchange ID The ID your VAN uses for your mailbox. 942888710

EDI Configuration Guide

EDI VAN Configuration and Testing PUBLIC 23
 Field Description Example

Interchange Qualifier The domain of the Interchange ID. 1 -DUNS

Routing Address (Optional) Your destination application. ORDERENTRY

 Note

Most suppliers use different Interchange IDs for test and production configurations. You can enter up to two
Interchange IDs, one in your test account and one in your production account. If your VAN provider later
changes your Interchange IDs, you must update the EDI Configuration page in both your test account and
production account with the new values. Although uses only ARIBAEDI to identify itself both in test and
production accounts, you can use separate IDs for yourself in your test and production accounts.

10. Send notification if outgoing documents are undeliverable or FAs are overdue to enable these notifications.
11. To receive additional tax information in purchase orders, click Map purchase order tax details to EDI. SAP
Business Network then maps cXML purchase order TaxDetail elements (in cXML 1.2.005 or later) to EDI
purchase orders. cXML Enter an email address for receiving warning and failed routing notifications. Enter only
one email address. Click TaxDetail elements specify taxable amount, tax amount, tax location, tax purpose,
tax category, and tax rate. If this box is not checked, SAP Business Network ignores TaxDetail elements
during cXML-to-EDI translation.
12. To map payment terms from cXML-to-EDI purchase orders, click Map paymentEnter an email address for
receiving warning and failed routing notifications. Enter only one email address. Click terms. By default, this
box is deselected, so the mapping behavior is unchanged.
13. To map the complete purchase order date that includes the time and timezone from cXML to EDI X12 purchase
orders, click Map order date with complete date, time, and zone for X12 850 documents. By default, this
box is deselected, so the mapping behavior is unchanged.
14. Click Submit.

 Note

Whenever you make changes to the EDI Configuration page, you must send an EDI interconnect request to
Ariba Customer Support.

15. Select EDI routing for the other types of documents you want to route, such as change/cancel orders,
non-catalog orders, and invoices. You do not need to fill out the EDI Configuration page for these additional
documents.

Next Steps

After configuring EDI routing, you cannot actually route documents until Ariba creates a VAN interconnect for you.

EDI Configuration Guide

24 PUBLIC EDI VAN Configuration and Testing
Related Information

Request an EDI Interconnect from Ariba [page 26]

Using Multiple Routing Methods

You can use different routing methods for inbound and outbound communication simultaneously. For example, you
can choose to receive purchase orders through fax and send invoices through EDI.

Incoming document (purchase order and remittance advice) routing is determined by your SAP Business Network
account settings. However, outbound document (functional acknowledgment, order confirmation, ship notice, and
invoice) routing is not restricted by your SAP Business Network account settings. For example, you can generate
invoices online even if you configured your account for EDI ANSI X12 invoicing.

 Note

If you set the order confirmation status through cXML or EDI, you cannot later update the order confirmation
status manually using the Create Confirmation button in the Inbox tab of your SAP Business Network account.
Instead, you can manually update the shipping status using the Create Ship Notice button for that order.
Ensure that you keep the source system up-to-date when you change your order shipping status manually.

Use the same routing method for functional acknowledgments that you use to receive purchase orders. For
example, if you receive an EDI ANSI X12 purchase order, send an X12 functional acknowledgment.

EDI Interconnect from Your VAN

Contact your Value Added Network (VAN) provider to request EDI interconnects between your VAN and SAP
Business Network’s VAN, INOVIS. EDI interconnects allow your documents to travel from VAN to VAN to reach their
intended destination. You need two bidirectional interconnects: one for test transactions and one for production
transactions.

When you request interconnects, send the following information about SAP Business Network to your VAN
provider:

Interconnect Direction Bidirectional

Company Name Ariba

VAN Name INOVIS

Interchange IDs ARIBAEDI

Interchange ID Qualifier ZZ (ANSI X12)

ZZZ (EDIFACT)

EDI Configuration Guide

EDI VAN Configuration and Testing PUBLIC 25
EDI Interconnect from SAP Ariba
You need an EDI interconnect from SAP Ariba to establish a connection between your VAN and INOVIS (the SAP
Business Network VAN). Request the EDI interconnect from SAP Ariba Support.

Requesting an EDI Interconnect from Ariba

You initiate an EDI interconnect request from Ariba through your SAP Business Network account.

Procedure

1. Sign in to your SAP Business Network account.

2. In the masthead, click Help and choose Help Center to display the User Community Home page.
3. Click Support Center to contact Ariba Customer Support and request an EDI interconnect for you.

Next Steps

Ariba Customer Support creates EDI interconnects within a few hours and sends you an email notification. While
you wait for your EDI interconnect, configure your EDI application.

Configure Your EDI Application

Your EDI application must be configured to map data, recognize SAP Business Network’s interchange IDs, send
functional acknowledgments, and identify your customers.

Configure Your Data Maps

Configure your EDI application to map data in incoming and outgoing documents according to SAP Business
Network’s requirements.

To learn about data and format requirements, see the Related Information section.

EDI Configuration Guide

26 PUBLIC EDI VAN Configuration and Testing
Related Information

Implementation Guides [page 13]

SEF Files [page 13]
Example Documents [page 50]

Specify the SAP Business Network’s Interchange IDs

Your EDI application must be configured to recognize the SAP Business Network Interchange ID. In most EDI
applications, you add a new Interchange ID by adding a new partner relationship. Use the following parameters
when specifying the Ariba Interchange ID:

Parameter Value

Interchange ID ARIBAEDI

ID Qualifier ZZ (ANSI X12)

ZZZ (EDIFACT)

Configure your EDI application to send functional acknowledgment documents to this Interchange ID ((997 or
CONTRL depending on your EDI implementation language).

Identify Your Customers

You need to specify each of your customers using that customer’s SAP Business Network (ANID) when using
EDI. The ISA element in EDI documents from SAP Business Network identifies SAP Business Network, not your
customers.

SAP Business Network specifies your customers’ ANID (Ariba Network ID) in the following EDI language elements:

Standard Element Name Example

ANSI X12 Application Sender ID (GS02) AN0100000001234

EDIFACT Reverse Routing ID (UNB0203) AN0100000001234

Looking Up Customer Ariba Network IDs

Context

You can look up your customers’ Network IDs in your SAP Business Network account.

 Note

Ensure that you do not use the Test Indicator element (‘-T’).

EDI Configuration Guide

EDI VAN Configuration and Testing PUBLIC 27
Procedure

1. Sign in to your SAP Business Network test account.

Be sure to use the correct test or production account. Account administrators can switch between the two
types of accounts from the Home page.
2. On the Administration tab, click Customer Relationships. to view a list of all your customers.
3. Click a customer entry to view information about that customer, including the customer ANID.

Detect Test/Production Mode

Suppliers keep test and production orders separate either by using two different mailboxes on their VANs. Even so,
some supplier order-processing systems might need to detect the production mode of purchase orders.

Use the Test Indicator element to detect the production mode of purchase orders:

Standard Element Name Value

ANSI X12 Test Indicator (ISA15) T (test)

P (production)

EDIFACT Test Indicator (UNB11) 1 (test)

(UNB11 is absent for production)

Test on Your Own

Send test EDI purchase orders to yourself to check basic communication from SAP Business Network to your EDI
processing system. This testing also checks that your EDI system can accept, interpret, and process orders from
SAP Business Network and generate a correct functional acknowledgment.

To perform testing on your own, you must have the following:

• An SAP Business Network test account. The catalog tester is available only in supplier test accounts. Create
your test account by clicking Switch to Test Account in the masthead. The first time you click this link, SAP
Business Network prompts for a user name and password.
The catalog tester’s Network ID is AN01000002779-T, which appears in the GS02 (ANSI X12) or UNB0203
(EDIFACT) segment.
• Your test account configured for EDI order routing. The document-routing settings in your test account are
separate from the ones in your production account.
• A test catalog. Upload a product catalog to your test account and use the catalog tester to generate simple
test purchase orders. Customer catalogs in your production account are not available in your test account. For
complete instructions on generating orders with the catalog tester, go to Customer Catalog Testing.

After you accumulate test purchase orders in your SAP Business Network account, you can resend them. Go to
your online Inbox, select a purchase order, and click Resend.

SAP Business Network transmits test purchase orders within 10 minutes of generating them. When you receive
test purchase orders, verify that your system can process them. You may need to repeat this process to debug

EDI Configuration Guide

28 PUBLIC EDI VAN Configuration and Testing
your configuration. To send another purchase order, sign in to your SAP Business Network test account and either
generate a new order with the catalog tester or resend an existing order. You cannot delete purchase orders from
your SAP Business Network account.

Send Functional Acknowledgments

After receiving a purchase order you must send an EDI functional acknowledgment document (997 or CONTRL,
depending on your EDI language) to ensure you can generate them correctly.

When you compose acknowledgments, reverse the sender/receiver IDs from purchase orders. You can check
whether you successfully acknowledged orders by logging in to your SAP Business Network account and
viewing them in your online Inbox. Successful functional acknowledgments change order status from “Sent” to
“Acknowledged.”

As with all documents you send, start with the minimum required information and confirm that SAP Business
Network accepts the basic document, then add any additional data you want to send.

Related Information

Requirements for Functional Acknowledgments [page 20]

Check Order-Routing Status

You can view order-routing status in your SAP Business Network account. During testing this can helpful to debug
routing problems.

To view order-routing status, go to your online Inbox tab, select a purchase order, and click the Order History tab.
Purchase orders go through the following status levels on SAP Business Network:

Status Explanation

Accepted SAP Business Network accepted the purchase order from your customer or from the catalog
tester.

Order Queued SAP Business Network queued the purchase order for cXML processing.

Sent SAP Business Network successfully converted the purchase order from cXML to EDI and has
forwarded it to you in an interchange.

Acknowledged SAP Business Network received a positive functional acknowledgment from you.

Failed SAP Business Network could not route the purchase order and lists the reason for the failure.
Failure can occur if you do not send a functional acknowledgment within the allotted time.

EDI Configuration Guide

EDI VAN Configuration and Testing PUBLIC 29
Related Information

Requirements for Functional Acknowledgments [page 20]

Testing ANSI X12 EDI Documents

Test your ANSI X12 EDI order confirmations, invoices, and ship notices using the EDI Tester function.

Prerequisites

The EDI Tester function is available only to account administrators and in the test account. To use it you must have
configured your SAP Business Network test account to use the EDI routing method.

Context

You can test your inbound ANSI X12 EDI documents (order confirmations, invoices, and ship notices) using the EDI
Tester. This tool uploads your implemented EDI document and validates them against SAP Business Network EDI
implementation guidelines to ensure that your documents are error-free when sending them to your customers.

Procedure

1. Sign in to your SAP Business Network account.

2. On the Home dashboard, click the Home tab.

SAP Business Network displays the Home page.

3. Click Switch to Test Account in the masthead.

The first time you click this button, SAP Business Network creates your test account and prompts you to
assign a user name and password.
4. Click EDI Tester in the Quick Links panel on the Home dashboard. This link is available only if you have
configured your EDI settings.
5. Click Browse.
6. In the Choose File dialog box, navigate to the EDI file to test.
7. Click Open. SAP Business Network returns to the EDI Tester page.
8. Click Upload. SAP Business Network displays the contents of the uploaded EDI document in the text box.
9. Click Validate Document. If your EDI document contains errors, SAP Business Network displays the error
details in the Validation Result section.

EDI Configuration Guide

30 PUBLIC EDI VAN Configuration and Testing
  Note

The file size of your EDI document cannot exceed 500 KB.

The EDI tester does not validate against your customer’s invoice validation rules. It only confirms that the
EDI X12 documents are error-free and translate successfully.

You must ensure that each inbound transaction to SAP Business Network must have a unique ISA control
number. This is also applicable when the previous transaction failed during translation.

You cannot send subsequent outbound documents (order confirmations, ship notices, or invoices) against
purchase orders generated by the catalog tester. To test these subsequent documents, you must test
against purchase orders generated by your customers.

Next Steps

Correct any errors and upload, and validate the file again.

Related Information

Configuring Your EDI Settings [page 22]

Test with Customers

After testing on your own, the next step is to test with purchase orders generated by your customers. This requires
coordination with your customers.

Buying organizations each have an SAP Business Network test account, similar to your test account, and they
can configure their procurement solution to connect to that account. Test accounts cannot communicate with
production accounts, which ensures that test orders are not mixed with production orders.

Request Test Orders

Inform your customers that you have performed basic EDI configuration and testing and are ready to test with
them. Ask them to use their own test accounts to create relationships with your SAP Business Network test
account and to send several test purchase orders to you.

Your customers must perform the same supplier-relationship activation process for supplier test accounts as they
do for supplier production accounts.

Your customers might want to create purchase orders that contain items from your customer catalogs. In this case,
upload customer catalogs to your test account and publish them to your customers.

EDI Configuration Guide

EDI VAN Configuration and Testing PUBLIC 31
Checking Basic Routing
After your customers create relationships with your test account and send purchase orders to it, look for the orders
in your online SAP Business Network Inbox and your EDI order receiving system.

Procedure

1. Sign in to your SAP Business Network account and click the Inbox tab on the Home Dashboard. SAP Business
Network stores a copy of each received purchase order in your online Inbox, regardless of your order routing
method.
2. If test orders routed successfully, they also appear in your EDI application.

Results

The following table lists symptoms and suggested actions for order routing problems:

Symptom Suggested Action

Orders do not appear in your SAP Busi- Ask your customers to check their SAP Business Network online Outboxes. SAP Busi-
ness Network online Inbox ness Network creates copies all customers’ orders in their Outboxes. If test orders do
not appear there, the buying organizations have not successfully integrated with SAP
Business Network.

You must wait for at least one of your customers to finish integrating their procure-
ment applications with SAP Business Network before you can continue testing.

Orders do not appear in your EDI sys- There was a problem during cXML-to-EDI translation or during routing. Log in to your
tem SAP Business Network account, go to your online Inbox, find a failed order, and click
Order History to see more information about it.

Related Information

Troubleshooting EDI Problems [page 41]

EDI Configuration Guide

32 PUBLIC EDI VAN Configuration and Testing
Viewing cXML Source Data

It can be helpful to look at the cXML source generated by your customers to understand the data they send,
including extrinsic data.

Procedure

1. Sign in to your SAP Business Network test account

2. On the Home dashboard, click the Inbox tab to display the Purchase order page.
3. Select a purchase order. SAP Business Network displays the purchase order details.
4. Click Export cXML. Your web browser prompts you to save the file or open it. You can view cXML documents in
your web browser or any text editor.

Recognize and Use Extrinsic Data

Your customers might include extrinsic data in their purchase orders. When SAP Business Network maps data
from cXML to ANSI X12 or EDIFACT, it attempts to preserve data from Extrinsic elements. You might need to
configure your order receiving system to recognize and use extrinsic data.

For example, SAP Business Network maps the following cXML Extrinsic element:

<Extrinsic name="UniqueName">Andrew Jackson</Extrinsic>

to the following EDI elements:

Standard Data

ANSI X12S
N9*ZZ**UniqueName~
MSG*Andrew Jackson~

EDIFACT
FTX+ZZZ+UniqueName:ZZZ:ZZZ+Andrew Jackson'

Extrinsic Data Mapping

Due to the nature of extrinsic data, SAP Business Network can map it only to general purpose message segments,
not to data-specific segments. SAP Business Network does not know the specific purpose of extrinsic data used by
trading partners.

Extrinsic data mapping is bidirectional. SAP Business Network maps extrinsic data for both purchase orders and
invoices. For purchase orders, it maps all extrinsic data. For invoices, it maps buying organizations’ part numbers. It
also maps extrinsic data from invoice REF/RFF segments.

EDI Configuration Guide

EDI VAN Configuration and Testing PUBLIC 33
SAP Business Network does not map extrinsic data you include in functional acknowledgments, order
confirmations, or ship notices.

Related Information

Support for X12 and EDIFACT Features [page 59]

Default Extrinsic Data

By default, SAP Ariba Buying include extrinsic data named UniqueName, UserEmail, and CostCenter in cXML
purchase orders, but your customers can modify SAP Ariba Buying to include any extrinsic data they want.

Send Functional Acknowledgments

After receiving a purchase order you must send an EDI functional acknowledgment document (997 or CONTRL,
depending on your EDI language) to ensure you can generate them correctly.

When you compose acknowledgments, reverse the sender/receiver IDs from purchase orders. You can check
whether you successfully acknowledged orders by logging in to your SAP Business Network account and
viewing them in your online Inbox. Successful functional acknowledgments change order status from “Sent” to
“Acknowledged.”

As with all documents you send, start with the minimum required information and confirm that SAP Business
Network accepts the basic document, then add any additional data you want to send.

Send Order Confirmations, Ship Notices, and Invoices

When testing with your customers, you can also send outbound documents (ANSI X12 855, 856, and 810, or
EDIFACT DESADV and INVOIC, depending on your selected EDI language). You can send invoices only if your
customers have configured their SAP Business Network accounts to accept them.

Related Information

Implementation Guides [page 13]

EDI Configuration Guide

34 PUBLIC EDI VAN Configuration and Testing
Switch to Production Mode
After testing EDI routing and fixing any problems in test mode, you can switch to production mode. You might
make this change at an idle time, such as during the evening, so your EDI processing system can send functional
acknowledgments to the correct account.

Switching to Production Mode

When testing of EDI routing is complete, you are ready to propagate your tested settings to your production
environment and turn on EDI electronic order routing.

Prerequisites

Do not select EDI on the Electronic Order Routing Configuration page before beginning this procedure.

Procedure

1. Propagate any configuration changes you made during testing to your SAP Business Network production
account. Be sure to use your production EDI values. Do not select EDI in the Electronic Order Routing
Configuration page yet.
2. If you do not yet have EDI interconnects for your production account, perform the steps in Request an
Interconnect from Your VAN and Request an EDI Interconnect from Ariba section for your production account.
3. After receiving notification that the VAN interconnect has been created, activate EDI routing by clicking EDI in
the Electronic Order Routing configuration page and submitting the page.
4. Inform your customers to start sending you transactions through their production SAP Business Network
accounts.

Next Steps

After switching to production mode, monitor the initial transactions closely to make sure SAP Business Network
and your system processes documents as expected.

Related Information

EDI Interconnect from Your VAN [page 25]

EDI Configuration Guide

EDI VAN Configuration and Testing PUBLIC 35
EDI Interconnect from SAP Ariba [page 26]

EDI Configuration Guide

36 PUBLIC EDI VAN Configuration and Testing
EDIINT AS2 Routing Configuration and Testing

You can route EDI documents over the Internet (EDIINT AS2) using your own servers instead of through a Value
Added Network (VAN). Configuration is a multi-step process.

To configure EDIINT AS2 routing, perform the following procedures in this section.

EDIINT AS2 Requirements

Using EDIINT AS2 for routing requires that you use HTTPS for Internet communications, that you create a digital
certificate, and that your software supports the IETF AS2.

SAP Business Network encloses AS2 documents within Secure/Multipurpose Internet Mail Extensions (S/MIME)
envelopes and secures them by routing them over Hypertext Transfer Protocol Secure (HTTPS).

SAP Business Network authenticates AS2 documents using the National Institute of Standards and Technology
(NIST) Secure Hash Algorithm 1 (SHA-1) with your digital certificate. After it transmits or receives AS2 documents,
it uses IETF Message Disposition Notification (MDN) protocol to generate and receive message confirmations. The
MDN protocol is mandatory. SAP Business Network only supports synchronous MDN protocol.

The EDIINT AS2 routing method supports both the ANSI X12 and UN EDIFACT languages.

Digital Certificate Creation

You need to create a digital certificate to use for both a client certificate for authentication, and a server certificate
for SSL.

Create a ITU X.509 V3 Class 3 signed digital certificate for document authentication and security. This certificate
acts as both a client certificate (for authentication) and a server certificate (for SSL). It enables SAP Business
Network to authenticate messages from you. It also enables your web server to establish an HTTPS connection,
which is required by SAP Business Network.

This certificate can be self-signed; it does not need to refer to a trusted Certificate Authority (CA). It can be in
binary Distinguished Encoding Rules (DER) format or base64-encoded Privacy-Enhanced Mail (PEM) format.

You use this certificate when sending EDIINT AS2 information to SAP Business Network and when configuring your
EDIINT AS2 server.

 Note

You can also use an existing digital certificate for your EDIINT AS2 server.

EDI Configuration Guide

EDIINT AS2 Routing Configuration and Testing PUBLIC 37
EDIINT AS2 Information to Send to SAP Product
Support
SAP Product Support needs certain information from you to configure SAP Business Network to support your
EDIINT AS2 environment.

Gather the following information about your EDIINT AS2 environment:

Value Description Example

Your Ariba Network ID A unique number SAP Business Network

(ANID) assigns to your organization. Your ANID AN02-000-123-456 (production)
AN02-000-123-456-T (test)
appears on the Home page of your AN ac-
count. Test accounts have a “-T” suffix.

Your EDIINT AS2 server The externally accessible address of your

URL EDIINT AS2 web server. This URL must be- [Link]
ediint
gin with https so the HTTP connection is
encrypted.

Your EDIINT AS2 ID An identifier for your relationship with SAP

Business Network. SAP Business Network ZZMYCOMPANY
embeds this ID in the header of EDIINT
AS2 messages it sends to you.

Your certificate An ITU X.509 V3 Class 3 digital certificate

that SAP Business Network uses authenti- -----BEGIN CERTIFICATE-----
2767CCAvagAwIBAgIQAREDumEudPn39jEB
cate your messages. You created this cer-
zY2Y4DANBgkqhkiG9w0BAQUFAD276
tificate in step Create a Digital Certificate. MQswCQYDVQQGEwJVUzEgMB4GA1UEChMXUl
NBIERhdGEgU2VjdXJpdHksIElu532
LjAsBgNVBAsTJVNlY3VyZSBTZXJ2ZXIgQ2
VydGlmaWNhdGlvbiBBdXRob3Jp765
HhcNMDMwNDExMDAwMDAwWhcNMDUwNTA5Mj
M1OTU5WjCBljELMAkGA1UEBhMC65434
…
-----END CERTIFICATE-----

(The above example is a PEM file. You can also send a

DER file.)

Contact SAP Product Support to request that your account be enabled for EDIINT AS2, and provide the information
you gathered. Then wait to receive a confirmation email indicating that your account has been enabled for EDIINT
AS2 routing before continuing configuration, testing, and deployment.

EDI Configuration Guide

38 PUBLIC EDIINT AS2 Routing Configuration and Testing
Configuring Your EDIINT AS2 Server
You must configure your EDIINT AS2 server to accept documents from Ariba Network. Ariba Network requires
specific transmission, authentication, and message-receipt protocols.

Context

Configuring your EDIINT AS2 server involves installing your digital certificate, setting up your server to use the SAP
Business Network URL and protocols, and configuring your firewall.

Procedure

1. Install the certificate you created in Create a Digital Certificate to enable SSL. Consult your web server
instructions for installing the certificate and enabling HTTPS communication. All communication with SAP
Business Network must go through HTTPS.
2. Configure your EDIINT AS2 server to use the SAP Business Network URL and its protocols:

Parameter Setting

SAP Business Network’s [Link]

EDIINT AS2 URL ediInt

SAP Business Network’s ZZARIBAEDI

EDIINT AS2 ID

Transmission HTTPS with encryption

Protocol

Document S/MIME without encryption

Envelope

Authentication SHA-1 without encryption

Protocol

Message receipt Synchronized and signed MDN

protocol

3. Configure your firewall to support two-way communication over Transmission Control Protocol (TCP) port 443,
the default port used by HTTPS. You can restrict your firewall to allow incoming connections only from SAP
Business Network.

Related Information

Digital Certificate Creation [page 37]

EDI Configuration Guide

EDIINT AS2 Routing Configuration and Testing PUBLIC 39
Test and Deploy
Once your server is configured, use your test account to send yourself purchase orders and functional
acknowledgements, and then do the same with customers. When everything works as expected, propagate your
configuration to your production account.

Suppliers keep test and production orders separate either by using two different EDIINT AS2 URLs. To test your
account, follow the instructions in Test on Your Own and Test with Customers section.

 Note

Be sure your EDIINT AS2 server is available 24/7. If it is down, SAP Business Network resends documents
every half hour for ten hours (20 times). SAP Business Network requires both an MDN receipt and a functional
acknowledgment document to confirm success. If, at the end of ten hours, SAP Business Network cannot send
the document successfully, it marks the document as “Failed.”

After testing and debugging any document routing problems, copy your test account settings to your production
account.

Related Information

Test on Your Own [page 28]

Test with Customers [page 31]
Switch to Production Mode [page 35]

EDI Configuration Guide

40 PUBLIC EDIINT AS2 Routing Configuration and Testing
Troubleshooting EDI Problems

During testing of your EDI routing configuration, you may encounter some common configuration problems.

If Orders Do Not Appear in Your SAP Business Network Account [page 41]

If Orders Do Not Appear in Your EDI System [page 43]

If Your EDI System Issues Errors [page 45]

If Functional Acknowledgement Does Not Update Order Status [page 47]

If Invoices Do Not Appear in Your SAP Business Network Account [page 48]

If Orders Do Not Appear in Your SAP Business

Network Account
The first step in troubleshooting order-routing problems is to verify whether your SAP Business Network account
received purchase orders.

Check for Received Purchase Orders

The first place to check for received purchase orders is the Purchase Orders or Orders and Releases page .

Procedure

1. Sign in to your test or production account as appropriate. Account administrators can switch between the two
types of accounts from the Home page.
2. Do one of the following:

• For suppliers without SAP Business Network for Supply Chain, choose Orders Purchase Orders
• For suppliers with SAP Business Network for Supply Chain, choose Orders Orders and Releases
3. Locate the purchase order in the list.

Results

If no purchase orders from your customers are listed, your customers have not properly integrated with SAP
Business Network or they are addressing documents incorrectly.

EDI Configuration Guide

Troubleshooting EDI Problems PUBLIC 41
Check Buyer Integration with SAP Business Network
Your customers must properly integrate their applications with SAP Business Network before they can successfully
send purchase orders to you.

If purchase orders do not appear in your online Inbox, ask your customers to check their online Outboxes. SAP
Business Network creates copies of all orders in buying organizations’ Outboxes. If purchase orders do not appear
there, your customers have not successfully integrated their applications with SAP Business Network.

Ensure that your customers send test orders to their SAP Business Network test accounts and production orders
to their SAP Business Network production accounts.

Check Your ID
Your customers must properly address purchase orders to you. If orders do not appear in your online Inbox, ask
them for the exact organization ID and ID domain they are using for you.

SAP Business Network recognizes the following organization ID domains in cXML documents:

ID Domain Example Description

NetworkId AN01000000123 A unique alphanumeric value assigned to each organization registered on

SAP Business Network. Also called ANID. You can see your NetworkId by
logging on to SAP Business Network

duns 942888711 A unique number assigned to organizations by Dun & Bradstreet; for
example. To request a Dun & Bradstreet D-U-N-S® number or to see if
your organization already has one, go to Dun & Bradstreet website (http://
[Link] ).

AribaNetworkUser judy@workchairs.c The user name of an SAP Business Network account administrator. These
Id om names typically have the format of an email address. This ID domain is
not preferred, because if users change their user names, cXML documents
might fail to route.

EDI Configuration Guide

42 PUBLIC Troubleshooting EDI Problems
If Orders Do Not Appear in Your EDI System
If purchase orders appear in your SAP Business Network account but not in your EDI order receiving system, there
is a problem either during cXML-to-EDI translation or during document routing.

Check Order History on SAP Business Network

If there are cXML to EDI translation or transmission errors, that information appears in your order history. SAP
Business Network transmits orders within ten minutes of receiving them.

Sign in to your SAP Business Network account, go to your online Inbox, select an order, and examine the order
history for warnings.

Verify Your EDI Configuration Settings

If the Interchange ID you specified in your SAP Business Network account does not match the one used by your
VAN, orders will not appear in your EDI system.

Go to the EDI Configuration page in your SAP Business Network account and check the values entered there. Your
Interchange ID must match the one used by your VAN.

If your VAN changes your Interchange IDs, you must update the EDI Configuration page in both your test and
production accounts with the new values. Then you must request a new EDI interconnect from SAP Business
Network Technical Support.

Related Information

Request an EDI Interconnect from Ariba [page 26]

EDI Configuration Guide

Troubleshooting EDI Problems PUBLIC 43
Check for Other Common Order-Routing Problems

Other common order-routing problems include failure to set up an interconnect with your VAN, missing required
data, non-compliant data, or overdue functional acknowledgements. In these cases, SAP Business Network sets
the order routing status to “Failed.”

Interconnect Not Set Up

You might not have set up interconnects with your VAN. You must request proper interconnects to enable your VAN
to communicate with INOVIS (SAP Business Network's VAN).

Related Information

Request an EDI Interconnect from Ariba [page 26]

Missing Required Data

Purchase order data required by the EDI standard might be missing. The cXML standard specifies required element
tags, basic syntax, and semantic rules. EDI standards are much stricter about the data. If required data is absent,
the document is non-compliant and SAP Business Network cannot route it.

Non-Compliant Data

Non-compliant data is information in purchase order fields that is not valid. Non-compliant data can result in
routing failure.

A common example of non-compliant data is unrealistic test data, such as random characters entered for
addresses. ANSI X12 requires at least two characters for a city name, but test orders might contain <City>A</
City>, which is non-compliant.

Other examples of data restrictions in ANSI X12 that can cause non-compliance are state names must have exactly
two characters and postal codes must have 3-15 characters.

Invalid UOM (unit of measure) codes in purchase orders are another common cause of routing failure.

EDI Configuration Guide

44 PUBLIC Troubleshooting EDI Problems
Functional Acknowledgement Overdue
SAP Business Network expects to receive a functional acknowledgement (FA) within an allotted period of time. If it
does not, it sets the order-routing status to “Failed.”

When a functional acknowledgement is not received within the allotted time, the transaction log indicates:

Document failed because FA has not been received.

Related Information

Functional Acknowledgement Does Not Update Order Status [page 47]

If Your EDI System Issues Errors

If your EDI system issues mapping or semantic errors, you have not configured it for the specific mapping used by
SAP Business Network or for the specific data included by your customers.

Verify the EDI Mapping

SAP Business Network uses a single EDI map for all suppliers. If your EDI system uses a different mapping you
receive an EDI system error.

Related Information

Document Mapping [page 12]

EDI Configuration Guide

Troubleshooting EDI Problems PUBLIC 45
Check for Extrinsic Data

Your customers might include custom data (called extrinsic data) in their purchase orders. Your order receiving
system may not recognize that data. During testing, anticipate extrinsic data by looking at test orders from your
customers and configuring your systems to recognize and process it.

Related Information

Recognize and Use Extrinsic Data [page 33]

Check Your Customers’ IDs

Your EDI system might not recognize a purchase order sender. It might incorrectly assume that the ISA element in
purchase orders identifies your customer, but it actually identifies SAP Business Network.

Confirm that your EDI system uses the GS02 (ANSI X12) or UNB0203 (EDIFACT) data elements in purchase orders
to identify customers.

Related Information

Identify Your Customers [page 27]

Check Test/Production Mode

Your EDI system might not correctly differentiate test orders from production orders. One of the ways SAP
Business Network specifies the production mode of purchase orders is through the test indicator flag ISA15 (ANSI
X12) or UNB11 (EDIFACT) segment.

Related Information

Detect Test/Production Mode [page 28]

EDI Configuration Guide

46 PUBLIC Troubleshooting EDI Problems
If Functional Acknowledgement Does Not Update
Order Status
If you send a functional acknowledgment within the allotted time, but order status on SAP Business Network does
not change, investigate the areas described below.

Check Test/Production Mode

The test/production mode of your functional acknowledgments must match the mode of the corresponding
purchase orders. If it does not, order status is not updated.

For example, the ISA15 segment in ANSI X12 850 purchase orders specifies the mode with a one-character flag: T
(test) or P (production). The ISA15 segment in the ANSI X12 997 functional acknowledgment documents you send
must match the ISA15 segment in the purchase order.

Related Information

Detect Test/Production Mode [page 28]

Check the ID of Buying Organizations

If you accidentally provide the Ariba Network ID (ANID) instead of your customer’s ID in a functional
acknowledgement, order status is not updated.

Your functional acknowledgments must specify the ID of your customer, not their Ariba Network ID. For example,
the GS03 segment in ANSI X12 997 functional acknowledgments must contain your customer’s Ariba Network ID
(ANID). It must not be empty or contain the wrong ID.

 Note

ANSI X12 only: For test accounts, append “-T” to the Ariba Network ID.

EDI Configuration Guide

Troubleshooting EDI Problems PUBLIC 47
Check Reference to Purchase Orders

You must generate transaction-level, not group-level functional acknowledgments. They must reference each
purchase order being acknowledged.

Related Information

Requirements for Functional Acknowledgments [page 20]

Obtain Additional Help with Functional Acknowledgements

If you require assistance from SAP Business Network Technical Support to troubleshoot functional
acknowledgements, forward them a complete copy of the 997 or CONTRL document that you sent.

If Invoices Do Not Appear in Your SAP Business

Network Account
Immediately after you generate an invoice and send it to SAP Business Network, it should appear on the Invoices
page of your acount. If it does not, there may be translation errors, cXML validation errors, issues with customer
invoice rules, or issues with PO references.

Check for Translation Errors

When you send EDI invoices to SAP Business Network, it performs EDI-to-cXML translation. If there are errors
during translation, SAP Business Network does not display the invoices in your online Outbox. Instead, it sends a
negative 997 or CONTRL document to you.

SAP Business Network also emails an error report to your EDI Administrator.

Related Information

Identifying Your EDI Administrator [page 22]

EDI Configuration Guide

48 PUBLIC Troubleshooting EDI Problems
Check for cXML Validation Errors
If EDI-to-cXML translation succeeds, SAP Business Network validates it against the cXML DTDs. If the cXML does
not validate, SAP Business Network does not display the invoice in your online Inbox.

Check Your Customers’ Invoice Rules

If the cXML version of the invoice passes cXML validation, SAP Business Network processes the invoice against the
buying organization’s invoicing rules. If it fails, it remains in your online Outbox and is marked “failed.”

Check References to Purchase Orders

Data in invoices must match the corresponding data in purchase orders. Otherwise SAP Business Network marks
them as “failed” in your Outbox. SAP Business Network also fails purchase orders if they do not contain a unique
invoice number. Each invoice number must be unique and cannot be changed.

Related Information

Testing ANSI X12 EDI Documents [page 30]

EDI Configuration Guide

Troubleshooting EDI Problems PUBLIC 49
Example Documents

Example cXML and EDI documents provide templates and mappings you can use when configuring your EDI
system.

 Note

The separators and terminators in these examples make them easier to read. SAP Business Network does not
use these characters in production data.

cXML OrderRequest Example [page 50]

X12 850 [page 54]

X12 997 [page 55]

EDIFACT ORDERS [page 56]

EDIFACT CONTRL [page 57]

cXML OrderRequest Example

The cXML OrderRequest example provides an illustration of the mappings used to generate example EDI purchase
orders.

cXML has no maximum field sizes, so assume that full ANSI X12 or EDIFACT bounds apply for each element.

Ariba Buyer does not allow a ShipTo element at both header level and line-item level. If all ShipTo elements on
the line-item level are identical, or if only one line item exists, Ariba Buyer removes line-item ShipTo elements
and replaces them with a single header level ShipTo element. However, both levels are present in this example for
demonstration purposes and map testing.

<?xml version="1.0" encoding="utf-8"?>

<!DOCTYPE cXML SYSTEM "[Link]
<cXML payloadID="12345-67890@[Link]"
timestamp="2004-04-15T13:14:05-08:00">
<Header>
<From>
<Credential domain="AribaNetworkUserId">
<Identity>buy_test@[Link]</Identity>
</Credential>
</From>
<To>
<Credential domain="DUNS">
<Identity>284010872</Identity>
</Credential>
</To>
<Sender>
<Credential domain="AribaNetworkUserId">
<Identity>buy_test@[Link]</Identity>
<SharedSecret>abracadabra</SharedSecret>
</Credential>
<UserAgent>Ariba Buyer 8.2</UserAgent>

EDI Configuration Guide

50 PUBLIC Example Documents
 </Sender>
</Header>
<Request>
<OrderRequest>
<OrderRequestHeader orderID="DO64"orderDate=" 2003-04-15T13:13:52-08:00"
type="new" requisitionID="R1492" shipComplete="yes">
<Total>
<Money currency="USD">321.68</Money>
</Total>
<ShipTo>
<Address isoCountryCode="US" addressID="152">
<Name xml:lang="en">San Jose Office</Name>
<PostalAddress name="default">
<DeliverTo>Maria Valenzuela</DeliverTo>
<DeliverTo>B1-2462</DeliverTo>
<DeliverTo>The Buyer, Inc.</DeliverTo>
<Street>1500 Buyer Way</Street>
<City>San Jose</City>
<State>CA</State>
<PostalCode>94110</PostalCode>
<Country isoCountryCode="US">United States</Country>
</PostalAddress>
<Email name="Maria- Primary">[Link]@[Link]</Email>
<Phone name="Maria- Primary">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>408</AreaOrCityCode>
<Number>5551414</Number>
</TelephoneNumber>
</Phone>
<Fax name="Maria - Primary">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>408</AreaOrCityCode>
<Number>5551616</Number>
</TelephoneNumber>
</Fax>
</Address>
</ShipTo>
<BillTo>
<Address isoCountryCode="US" addressID="001">
<Name xml:lang="en">Corporate Office</Name>
<PostalAddress name="default">
<DeliverTo>Roxanne Barber</DeliverTo>
<DeliverTo>Accounts Payable</DeliverTo>
<DeliverTo>The Buyer, Inc.</DeliverTo>
<Street>1 Buyer Parkway</Street>
<City>Chicago</City>
<State>IL</State>
<PostalCode>35101</PostalCode>
<Country isoCountryCode="US">United States</Country>
</PostalAddress>
<Email name="AP Purchases(Roxanne)">[Link]@[Link]
</Email>
<Phone name="AP Purchases (Roxanne)">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>312</AreaOrCityCode>
<Number>5551111</Number>
</TelephoneNumber>
</Phone>
<Fax name="AP Purchases (Roxanne)">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>312</AreaOrCityCode>
<Number>5552222</Number>
</TelephoneNumber>
</Fax>

EDI Configuration Guide

Example Documents PUBLIC 51
 </Address>
</BillTo>
<Shipping trackingDomain="FedEx" trackingId="21428339882">
<Money currency="USD">46.80</Money>
<Description xml:lang="en">Fed-Ex 2 day</Description>
</Shipping>
<Tax>
<Money currency="USD">27.18</Money>
<Description xml:lang="en">Total combined taxes</Description>
</Tax>
<Payment>
<PCard number="4510294818443233" expiration="2003-03-12"
name="Visa - Purchases"></PCard>
</Payment>
<Contact role="administrator">
<Name xml:lang="en">Administration</Name>
<PostalAddress name="default">
<DeliverTo>Elmira Gulch</DeliverTo>
<DeliverTo>2nd floor</DeliverTo>
<Street>The Buyer, Inc.</Street>
<Street>1 Buyer Parkway</Street>
<City>Chicago</City>
<State>IL</State>
<PostalCode>34592</PostalCode>
<Country isoCountryCode="US">United States</Country>
</PostalAddress>
<Email name="Elmira - Admin">[Link]@[Link]</Email>
<Phone name="Elmira - Admin">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>800</AreaOrCityCode>
<Number>5551515</Number>
</TelephoneNumber>
</Phone>
<Phone>
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>800</AreaOrCityCode>
<Number>5552727</Number>
</TelephoneNumber>
</Phone>
<URL>[Link]
</Contact>
<Comments xml:lang="en">Be sure printer ink cartridges are properly
sealed to avoid spillage.</Comments>
<Extrinsic name="Packing Instructions">512 units per
carton</Extrinsic>
</OrderRequestHeader>
<ItemOut quantity="25" requisitionID="4592782"
requestedDeliveryDate="2003-04-15T00:00:00-08:00">
<ItemID>
<SupplierPartID>26409</SupplierPartID>
</ItemID>
<ItemDetail>
<UnitPrice>
<Money currency="USD">0.64</Money>
</UnitPrice>
<Description xml:lang="en">
<ShortName>3M Brand Scotch Tape</ShortName>A cellophane strip
bearing an adhesive coating on one side and wound tightly onto a
roll. A frame surrounds the roll with a tearing edge protruding
about one inch from the center of the roll's rotational axis.
</Description>
<UnitOfMeasure>D65</UnitOfMeasure>
<Classification domain="UN/SPSC">31201512</Classification>
<ManufacturerPartID>YZ323</ManufacturerPartID>
<ManufacturerName>3M</ManufacturerName>

EDI Configuration Guide

52 PUBLIC Example Documents
 <URL name="Catalog Entry">
[Link]
<Extrinsic name="Size Information">Height: 14, Width: 23</Extrinsic>
</ItemDetail>
<SupplierID domain="DUNS">352948107</SupplierID>
<ShipTo>
<Address isoCountryCode="US" addressID="152">
<Name xml:lang="en">San Jose Office</Name>
<PostalAddress name="default">
<DeliverTo>Maria Valenzuela</DeliverTo>
<DeliverTo>B1-2462</DeliverTo>
<DeliverTo>The Buyer, Inc.</DeliverTo>
<Street>1500 Buyer Way</Street>
<City>San Jose</City>
<State>CA</State>
<PostalCode>94110</PostalCode>
<Country isoCountryCode="US">United States</Country>
</PostalAddress>
<Email name="Maria- Primary">[Link]@[Link]</Email>
<Phone name="Maria- Primary">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>408</AreaOrCityCode>
<Number>5551824</Number>
</TelephoneNumber>
</Phone>
<Fax name="Maria - Primary">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>408</AreaOrCityCode>
<Number>5552001</Number>
</TelephoneNumber>
</Fax>
</Address>
</ShipTo>
<Shipping trackingDomain="FedEx" trackingId="4812489789">
<Money currency="USD">46.80</Money>
<Description xml:lang="en">2 day express</Description>
</Shipping>
<Tax>
<Money currency="USD">27.18</Money>
<Description xml:lang="en">Total taxes for line item</Description>
</Tax>
<Distribution>
<Accounting name="DistributionCharge">
<Segment type="Function" id="07" description="1:Function"/>
<Segment type="CostCenter" id="D84" description="2:Cost Center"/>
<Segment type="SubCostCenter" id="422"
description="3:Sub-Cost Center"/>
<Segment type="Object" id="E11" description="4:Object"/>
</Accounting name="DistributionCharge">
<Charge>
<Money currency="USD">98.00</Money>
</Charge>
</Distribution>
<Distribution>
<Accounting>
<Segment type="Function" id="07" description="Function"/>
<Segment type="CostCenter" id="G18" description="Cost Center"/>
<Segment type="SubCostCenter" id="422"
description="Sub-Cost Center"/>
<Segment type="Object" id="E11" description="Object"/>
</Accounting>
<Charge>
<Money currency="USD">27.00</Money>
</Charge>
</Distribution>
<Contact role="customerService">

EDI Configuration Guide

Example Documents PUBLIC 53
 <Name xml:lang="en">Devereux</Name>
<PostalAddress>
<DeliverTo>Stefanie Devereux</DeliverTo>
<Street>The Buyer, Inc.</Street>
<Street>1 Buyer Parkway</Street>
<City>Chicago</City>
<State>IL</State>
<PostalCode>34592</PostalCode>
<Country isoCountryCode="US">United States</Country>
</PostalAddress>
<Email name="Stefanie- Sales">[Link]@[Link]</Email>
<Phone name="Stefanie- Sales">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>800</AreaOrCityCode>
<Number>5552429</Number>
</TelephoneNumber>
</Phone>
</Contact>
<Comments xml:lang="en">Do not wrap with adhesive tape;
It leaves a sticky residue.</Comments>
</ItemOut>
</OrderRequest>
</Request>
</cXML>

X12 850
The X12 850 example demonstrates an EDI purchase order generated from a cXML OrderRequest document by
SAP Business Network when your EDI language is ANSI X12.

ISA*00* *00* *ZZ*ARIBAEDI *ZZ*284010872

*030415*1314*U*00401*000601828*0*T*>~
GS*PO*AN01000000001*AN01000000002*20030415*1314*000341217*X*004010~
ST*850*0001~
BEG*00*NE*DO364**20030415~
CUR*BY*USD~
REF*RQ*R1492~
CSH*SC~
SAC*C*G830***4680********FedEx:21428339882**Fed-Ex 2 day*EN~
CUR*BY*USD~
TXI*TX*27.18~
N9*PSM*4510294818443233*Visa - Purchases~
DTM*036****UN*0432~
N9*L1*Comment*en~
MSG*Be sure printer ink cartridges are properly sealed to avoid spillage.~
N9*ZZ**Packing Instructions~
MSG*512 units per carton~
N1*BT*Corporate Office*92*001~
N2*Roxanne Barber*Accounts Payable~
N2*The Buyer, Inc.~
N3*1 Buyer Parkway~
N4*Chicago*IL*35101*US~
PER*AP*AP Purchases
(Roxanne)*TE*13125551111*FX*13125552222*EM*[Link]@[Link]~
N1*ST*San Jose Office*92*152~
N2*Maria Valenzuela*B1-2462~
N2*The Buyer, Inc.~
N3*1500 Buyer Way~
N4*San Jose*CA*94110*US~
PER*RE*Maria -
Primary*TE*14085551414*FX*14085551616*EM*[Link]@[Link]~

EDI Configuration Guide

54 PUBLIC Example Documents
 N1*NG*Administration~
N2*Elmira Gulch*2nd floor~
N3*The Buyer, Inc.*1 Buyer Parkway~
N4*Chicago*IL*34592*US~
PER*AM*Elmira - Admin*TE*18005551515*EM*[Link]@[Link]~
PER*AM**TE*18005552727*UR*[Link]
PO1*1*25*RO*.64**VP*26409*MG*YZ323*MF*3M*C3*31201512~
CUR*BY*USD~
PID*F*GEN***3M Brand Scotch Tape****EN~
PID*F****A cellophane strip bearing an adhesive coating on one side and wound
tightly****EN~
PID*F****onto a roll. A frame surrounds the roll with a tearing edge protruding
about one****EN~
PID*F****inch from the center of the roll's rotational axis.****EN~
PID*S*MAC*UN*31201512***SPSC~
REF*RQ*4592782~
REF*ZA*352948107*DUNS~
SAC*C*G830***4680********FedEx:4812489789**2 day express*en~
CUR*BY*USD~
SAC*N*B840***9800********07-D84-422-E11*1*Project: 07, Cost Center: D84,
Department: 422, Account: E11~
CUR*BY*USD~
SAC*N*B840***2700********07-G18-422-E11*2*Project: 07, Cost Center: G18,
Department: 422, Account: E11~
CUR*BY*USD~
DTM*002*20030415~
TXI*TX*27.18~
N9*URL*URL*Catalog Entry~
MSG*[Link]
N9*L1*Comment*en~
MSG*Do not wrap with adhesive tape;~
MSG*It leaves a sticky residue.~
N9*ZZ**Size Information~
MSG*Height: 14, Width: 23~
N1*ST*San Jose Office*92*152~
N2*Maria Valenzuela*B1-2462~
N2*The Buyer, Inc.~
N3*1500 Buyer Way~
N4*San Jose*CA*95110*US~
PER*RE*Maria -
Primary*TE*14085551824*FX*14085552001*EM*[Link]@[Link]~
N1*A9*Devereux~
N2*Stefanie Devereux*Executive Sales Manager~
N3*The Buyer, Inc.*1 Buyer Parkway~
N4*Chicago*IL*34592*US~
PER*CR*Stefanie - Sales*TE*18005552429*EM*[Link]@[Link]~
CTT*1*25~
AMT*TT*321.68~
SE*70*0001~
GE*1*000341217~
IEA*1*000601828~

X12 997
The ANSI X12 997 example demonstrates a positive functional acknowledgement sent by a supplier to
acknowledge a purchase order. The 997 sent depends on the GS and ST segments in the 850.

For example, if you received the following 850:

ISA*00* *00* *ZZ*ARIBAEDI *ZZ*284010872

*030415*1314*U*00401*000601828*0*T*>~

EDI Configuration Guide

Example Documents PUBLIC 55
 GS*PO*AN01000000001*AN01000000002*20030415*1314*000341217*X*004010~
ST*850*0001~

You would send the following 997:

ST*997*0001~
AK1*PO*000341217~
AK2*850*0001~
AK5*A~
AK9*A*1*1*1~
SE*6*0001~

AK1 represents the functional group (GS) and AK2 represents the transaction set (ST). There is only one AK1 and
AK9 in each 997.

AK2-AK5 represents one transaction set and it can repeat. There is one AK2-AK5 pair for each ST-SE pair in the
source functional group. An AK5 with “A” means “Accepted” and with “E” means “Error.”

The following table lists the AK9 fields:

Field Description

AK901 Functional Group status: (A)ccepted, (P)artial, (E)rror, (R)eject).

AK902 Number of included transaction sets. It corresponds to the number specified by the original document.

AK903 Number of transaction sets received. It corresponds to the actual number of sets that were actually found
and processed.

AK904 Number of transactions sets accepted.

SAP Business Network does not use additional fields in AK5 and AK9, nor in the AK3 or AK4 groups that provide
failure details.

EDIFACT ORDERS
The EDIFACT ORDERS example demonstrates an EDI purchase order generated from a cXML OrderRequest
document by SAP Business Network when your EDI language is EDIFACT.

UNA:+.?*'
UNB+UNOC:3+ARIBAEDI:ZZZ:AN01765432133+284010872:ZZZ:AN123456789+000626:1356+601828++
++1++1'
UNH+1+ORDERS:D:98A:UN'
BGM+105:::Purchase Order+PC16:1.1:010+9+AB'
DTM+4:20000626:102'
FTX+ADU+3++Note the extra ink required with fountain pens.:Check paper bond
ordered.+en'
FTX+ZZZ+2+MaxWeight:ZZZ:ZZZ+<PackageWeight max="35" uom="lb"/>'
RFF+AGI:2498573'
RFF+AIU:4217481433331111'
DTM+36:1005'
NAD+BY+AN01765432133:ZZZ'
NAD+SU+AN123456789:ZZZ'
NAD+BT+001::92+Corporate Office+Roxanne Barber:Accounts Payable+1 Buyer
Parkway+Chicago+IL+35101+US'
CTA+AP+:AP Purchases (Roxanne)'
COM+312-555-1111:TE'
NAD+ST+152::92+San Jose Office+Maria Valenzuela:B1-2462:The Buyer, Inc.+1500 Buyer
Way+San Jose+CA+951103472+US'

EDI Configuration Guide

56 PUBLIC Example Documents
 CTA+GR+:Maria - Primary'
COM+[Link]@[Link]:EM'
NAD+AB++Purchasing Dept.'
CTA+PD+:Tina Bass'
COM+http?://[Link]/purchasing/[Link]:AH'
TAX+7'
MOA+161:45.19:USD:9'
SCC+1+SC'
ALC+C++++SAA:::Fed-Ex 2 day:21428339882'
MOA+23:7.18:USD:9'
LIN+5++26409:SA'
PIA+1+YZ323:MF'
IMD+E++:::3M Brand Scotch Tape::en'
IMD+F++:::A cellophane strip bearing an:adhesive coating on one side and:en'
IMD+F++:::wound tightly onto a roll. A frame:surrounds the roll with a tearing:en'
IMD+F++:::edge protruding about one inch from:the center of the rolls rotational:en'
IMD+F++:::axis.::en'
QTY+21:25:EA'
DTM+2:20000415:102'
MOA+146:.64:USD:9'
FTX+ADU+3++Do not wrap with adhesive tape;:It leaves a sticky residue.+en'
FTX+ZZZ+2+Size Information:ZZZ:ZZZ+<Size UnitOfMeasure="cm">: <Height>14</
Height>: <Width>23</Width>: <Depth>12.4</Depth>:</Size>'
RFF+AGI:4592782'
TAX+7'
MOA+161:4.18:USD:9'
NAD+SU+123456789ABCD:46:16'
NAD+ST+152::92+San Jose Office+Maria Valenzuela:B1-2462:The Buyer, Inc.+1500 Buyer
Way+San Jose+CA+951103412+US'
CTA+GR+:Maria - Primary'
COM+4085551111:TE'
NAD+SB++Devereux+Stefanie Devereux:Executive Sales Manager+The Buyer, Inc.:1 Buyer
Parkway+Chicago+IL+34592+US'
CTA+SR+:Stefanie - Sales'
COM+18005552429:TE'
COM+[Link]@[Link]:EM'
COM+http?://[Link]/Sales/:AH'
ALC+C++++SAA:::2 day express:4812489789'
MOA+23:46.80:USD:9'
ALC+N++++AEC:175:92:07-D84-422-E11:LISA'
MOA+23:98.00:USD:9'
ALC+N++++AEC:175:92:07-G18-422-E11:LISA'
MOA+23:27.00:USD:9'
UNS+S'
MOA+128:322.18:USD:9'
CNT+2:4'
UNT+58+1'
UNZ+1+601828'

EDIFACT CONTRL
The EDIFACT CONTRL example demonstrates a positive functional acknowledgement sent by a supplier to confirm
receiving a purchase order.

The control reference ID is in UCI and UCM. They come from the UNB and UNH segments in the original ORDERS
document.

UNA:+.? '
UNB+UNOC:3+ABCMUSICSUPPLY:ZZZ+ARIBAEDI:ZZZ:AN02000012345+030910:1059+1++CONTRL++1+
+1'
UNH+sample+CONTRL:D:3:UN'

EDI Configuration Guide

Example Documents PUBLIC 57
 UCI+1+ARIBAEDI:ZZZ:AN02000012345+ABCMUSICSUPPLY:ZZZ+7'
UCM+LineItemWithTx+ORDERS:D:98A:UN+7'
UNT+4+sample'
UNZ+1+1'

EDI Configuration Guide

58 PUBLIC Example Documents
Support for X12 and EDIFACT Features

SAP Business Network supports various X12 and EDIFACT features, including purchase order contact mapping,
extrinsics to REF mapping, and invoice REF, RFF mapping. Some segments are unsupported, and some ANSI
UOMs are unsupported.

Purchase Order Contact Mapping [page 59]

Purchase Order Extrinsics to REF Mapping [page 61]

Invoice REF/RFF Mapping [page 61]

Unsupported Segments [page 63]

Unsupported ANSI UOMs [page 63]

Purchase Order Contact Mapping

SAP Business Network maps all contact information when it translates cXML purchase orders to ANSI X12 or
EDIFACT purchase orders. Each cXML purchase order contact, including BillTo and ShipTo, can include an
arbitrary number of Email, Phone, Fax, and URL elements.

Each cXML contact element contains a name and the actual contact string. For example, an Email element can
contain:

<Email name="Sales">sales@[Link]</Email>.

The name attribute is optional, but if it is present, it categorizes the contact. For example, a Phone element can also
have name="Sales", which implies that the Email and the Phone are related. SAP Business Network uses these
names when grouping contacts within ANSI X12 PER segments or EDIFACT CTA/COM segments.

SAP Business Network allows contact data to overflow EDI segment within their limits. For example, the PER
segment can hold up to three contacts. If a purchase order contains four contacts with the same name, SAP
Business Network creates another PER or CTA/COM segment with the same name. If it reaches the PER segment
limit, (three in some cases) it does not create more. Typically, up to five COMs are allowed. If SAP Business Network
needs six, it creates another CTA group.

cXML Source Data for Contact Mapping

<Email name="Help Desk">helpdesk@[Link]</Email>

<Email>whatever@[Link]</Email>
<Phone>
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>512</AreaOrCityCode>
<Number>5551212</Number>
</TelephoneNumber>

EDI Configuration Guide

Support for X12 and EDIFACT Features PUBLIC 59
 </Phone>
<Phone name="Executive Office">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>408</AreaOrCityCode>
<Number>5551212</Number>
</TelephoneNumber>
</Phone>
<Phone name="Help Desk">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>800</AreaOrCityCode>
<Number>5551212</Number>
</TelephoneNumber>
</Phone>
<URL>[Link]

When SAP Business Network translates this example to EDI, it uses the following information:

• The Fax element is not used.

• The Email, Phone, and URL elements do not have a name attribute.
• The Email and Phone elements both have a “Help Desk” entry.
• Only the Phone element has “Executive Office.”

ANSI X12 850 Example Contact Translation

PER*CN**EM*whatever@[Link]*TE*1-512-555-1212*UR*[Link]
PER*CN*Executive Office*TE*1-408-555-1212~
PER*CN*Help Desk*EM*helpdesk@[Link]*TE*1-800-555-1212~

EDIFACT ORDERS Example Contact Translation

CTA+OC'
COM+whatever@[Link]:EM'
COM+1-512-555-1212:TE'
COM+http?://[Link]:AH'
CTA+OC+:Executive Office'
COM+1-408-555-1212:TE'
CTA+OC+:Help Desk'
COM+helpdesk@[Link]:EM'
COM+1-800-555-1212:TE'

EDI Configuration Guide

60 PUBLIC Support for X12 and EDIFACT Features
Purchase Order Extrinsics to REF Mapping
By default, cXML extrinsics in purchase orders appear in comment elements in EDI purchase orders. However, your
customers can upload maps to their accounts and SAP Business Network can translate cXML extrinsics to ANSI
X12 REF segments in 850 purchase orders.

The cXML/EDI Transformation link in the Customer Relationships page allows you to turn on purchase order REF
mapping.

Additional References

• cXML Transformations in the Ariba cXML Solutions Guide.

• SAP Business Network Standard Extrinsics in the Product Documentation For Administrators section
of the Learning Center.

Invoice REF/RFF Mapping

SAP Business Network translates the full set of ANSI X12 and EDIFACT invoice REF and RFF segments to cXML
invoices. It maps this information to cXML Extrinsic elements in InvoiceDetailRequest documents. Ask
your customers for the qualifiers they expect.

ANSI X12 REF Mapping

SAP Business Network translates header level REF (1/050) qualifiers and line item REF (2/120) qualifiers in ANSI
X12 invoices. Use qualifiers that are defined in X12 for the REF01 (0128) data element.

Example

REF qualifier 2N is defined in ANSI X12 as “Federal Communications Commission (FCC) Trade/Brand Identifier.”

SAP Business Network translates REF*2N*1234567~ to the following cXML:

<Extrinsic name="FCC Trade/Brand Identifier">1234567</Extrinsic>

This Extrinsic data also appears in online invoices under “Additional Information” as:

FCC Trade/Brand Identifier:1234567

Reserved Codes

Some REF codes are reserved for use by SAP Business Network, and cannot be used by you.

Do not use the following REF codes for extrinsic data.

EDI Configuration Guide

Support for X12 and EDIFACT Features PUBLIC 61
Header level REF (1/050):

REF Code Meaning Comments

AH Agreement Number Master agreement ID

IL Internal Order Number Reserved, but currently unused

IV Seller’s Invoice Number Can be used to extend invoice number from BIG02

MA Ship Notice / Manifest Number References a previously sent ship notice

PO Purchase Order Number Can be used to extend purchase order number from BIG04

VN Vendor Order Number Supplier sales order number

ZZ Mutually Defined Text extrinsic

Line item level REF (2/120):

REF Code Meaning Comments

AH Agreement Number Master agreement ID (header invoices)

IL Internal Order Number Reserved, but currently unused

FJ Line Item Control Number Required, for invoice line number

IL Internal Order Number Reserved, but currently unused

MA Ship Notice / Manifest Number References a previously sent ship notice (line item shipping)

SE Serial Number Used for serial numbers, combined with serial numbers from IT1

ZZ Mutually Defined Text extrinsic

EDIFACT RFF Mapping

SAP Business Network translates data element 1153 in EDIFACT invoices. You can use the header level RFF @0120
(SG1, RFF) or the line item RFF @1360 (SG30, RFF-DTM). SAP Business Network does not translate accompanying
segments subordinate to the RFF group (DTM @1370 for line items).

Example

RFF qualifier ERN is defined in EDIFACT D.98A as “Exporter's reference number.”

SAP Business Network translates RFF+ERN:1234567’ to the following cXML:

<Extrinsic name="Exporter's reference number">1234567</Extrinsic>

This Extrinsic data also appears in online invoices under “Additional Information” as:

Exporter's reference number:1234567

Reserved Codes

Some RFF codes are reserved for use by SAP Business Network, and cannot be used by you.

EDI Configuration Guide

62 PUBLIC Support for X12 and EDIFACT Features
Do not use the following RFF codes:

Header level RFF @0120 (SG-1 @0110):

RFF Code Meaning Comments

AJS Agreement number References a master agreement

MA Ship notice/manifest number References a previous ship notice

ON Order number (purchase) Purchase order number

VN Order number (vendor) Vendor sales order number

Line item level RFF @1360 (SG-30 @1350):

RFF Code Meaning Comments

AJS Agreement number References a master agreement

ON Order number (purchase) Purchase order number

VN Order number (vendor) Vendor sales order number

Unsupported Segments
The ANSI X12 and EDIFACT standards define segments that SAP Business Network does not use. Suppliers can
include segments that are not explicitly supported, but SAP Business Network does not translate those segments
nor does it include data from those segments in the resulting cXML documents.

If SAP Business Network encounters unsupported segments, it ignores those segments without issuing any
warnings or errors. Suppliers are encouraged to use only the segments declared in the EDI Implementation Guides
so that no data is lost.

Unsupported ANSI UOMs

X12 uses American National Standards Institute (ANSI) units of measure (UOM) codes, but SAP Business Network
does not support the entire list of codes. Do not use unsupported codes in ANSI X12 documents you send to SAP
Business Network. SAP Business Network does not use them in ANSI X12 documents it sends to you.

There are two reasons why SAP Business Network might not support a particular ANSI UOM code:

• The code has no direct translation to the United Nations Units of Measure (UNUOM) code table used by cXML.
For example, ANSI code DO (Dollars, U.S.) has no corresponding UNUOM code. Instead, use ANSI code M4
(Monetary Value). UNUOM also has code M4 with the same meaning.
Another example is ANSI code DH (Miles), which has no corresponding UNUOM code. Instead, use ANSI code
02 (Statute Mile), which has an appropriate match in UNUOM.
• The code does not yield a bidirectional translation between UNUOM and ANSI code systems. Legacy codes
superseded by newer codes for compatibility do not have a clear 1:1 translation. In such cases, multiple codes
in the same system are synonymous. Where two different but synonymous codes in one system represent

EDI Configuration Guide

Support for X12 and EDIFACT Features PUBLIC 63
 the same code in another system, the closer match (often a matching code) is supported and the other is
desupported. Supported codes must have a distinct 1:1 translation with its counterpart.

Additional References

Units of Measure Mapping for ANSI X12 document in the Product Documentation For Administrators
section of the Learning Center.

EDI Configuration Guide

64 PUBLIC Support for X12 and EDIFACT Features
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.

EDI Configuration Guide

Important Disclaimers and Legal Information PUBLIC 65
[Link]

Copyright © 2025 Ariba, Inc. All rights reserved.

This documentation, as well as the Ariba solutions, software and/or

services described in it, contain proprietary information. They are
provided under a license or other agreement containing restrictions on
use and disclosure and are also protected by copyright, patent and/or
other intellectual property laws. Except as permitted by such agreement,
no part of the document may be reproduced or transmitted in any form
by any means, electronic, mechanical or otherwise, without the prior
written permission of Ariba, Inc.

Ariba, Inc. assumes no responsibility or liability for any errors or

inaccuracies that may appear in the documentation. The information
contained in the documentation is subject to change without notice.

Ariba and Ariba products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of
Ariba, Inc. in the United States and other countries. Please see http://
[Link]/legal/trademarks for additional trademark information
and notices.

Ariba Sourcing solutions (On Demand and software) are protected

by one or more of the following patents, including without limitation:
U.S. Patent Nos. 6,199,050; 6,216,114; 6,223,167; 6,230,146; 6,230,147;
6,285,989; 6,408,283; 6,499,018; 6,564,192; 6,871,191; 6,952,682;
7,010,511; 7,072,061; 7,130,815; 7,146,331; 7,152,043;7,225,152; 7,277,878;
7,249,085; 7,283,979; 7,283,980; 7,296,001; 7,346,574; 7,383,206;
7,395,238; 7,401,035; 7,407,035; 7,444,299; 7,483,852; 7,499,876;
7,536,362; 7,558,746; 7,558,752; 7,571,137; 7,599,878; 7,634,439;
7,657,461; 7,693,747; 8,364,577; and 8,392,317. Patents pending.

Other Ariba product solutions are protected by one or more of the

following patents:

U.S. Patent Nos. 6,199,050, 6,216,114, 6,223,167, 6,230,146, 6,230,147,

6,285,989, 6,408,283, 6,499,018, 6,564,192, 6,584,451, 6,606,603,
6,714,939, 6,871,191, 6,952,682, 7,010,511, 7,047,318, 7,072,061,
7,084,998; 7,117,165; 7,225,145; 7,324,936; 7,536,362; 8,364,577; and
8,392,317. Patents pending.

Certain Ariba products may include third party software or other

intellectual property licensed from a third party. For information
regarding software or other intellectual property licensed from a third
party, go to [Link]

THE BEST RUN