Ariba Network IntegrationGuide11s1

Ariba Network
Integration Guide
Release 11s
Document Version 1
June 2011
For these users:

Application Developers
Application Administrators
Business Managers
Copyright 19962011 Ariba, Inc. All rights reserved.
This documentation, as well as the Ariba 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, the Ariba logo, AribaLIVE, SupplyWatch, Ariba.com, Ariba.com Network and Ariba Spend Management. Find it. Get it. Keep it. and PO-Flip are
registered trademarks of Ariba, Inc. Ariba Procure-to-Pay, Ariba Buyer, Ariba eForms, Ariba PunchOut, Ariba Services Procurement, Ariba Travel and
Expense, Ariba Procure-to-Order, Ariba Procurement Content, Ariba Sourcing, Ariba Savings and Pipeline Tracking, Ariba Category Management, Ariba
Category Playbooks, Ariba StartSourcing, Ariba Spend Visibility, Ariba Analysis, Ariba Data Enrichment, Ariba Contract Management, Ariba Contract
Compliance, Ariba Electronic Signatures, Ariba StartContracts, Ariba Invoice Management, Ariba Payment Management, Ariba Working Capital
Management, Ariba Settlement, Ariba Supplier Information and Performance Management, Ariba Supplier Information Management, Ariba Discovery, Ariba
Invoice Automation, Ariba PO Automation, Ariba Express Content, Ariba Ready, and Ariba LIVE are trademarks or service marks of Ariba, Inc. All other
brand or product names may be trademarks or registered trademarks of their respective companies or organizations in the United States and/or other countries.
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; and 7,693,747. 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; and 7,536,362. 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 http://www.ariba.com/copyrights.cfm.
11s.0057.en
Revision History
Revision History
The following table provides a brief history of the updates to this guide. Ariba updates the technical
documentation for its On Demand solutions when:
Software changes delivered in service packs or hot fixes require a documentation update to correctly
reflect the new or changed functionality;
The existing content is incorrect or user feedback indicated that important content is missing.
Ariba reserves the right to update its technical documentation without prior notification. Most
documentation updates will be made available in the same week as the software service packs are released,
but critical documentation updates may be released at any time.
To provide feedback on this guide or any Help@Ariba resources, click the Submit Feedback link on any
Help@Ariba page.
Document Month/Year of Updated Short Description of Change

Version Update Chapter/Section
1 June 2011 Technical Added information about rejecting a previously approved
Architecture invoice, which is currently technically possible but will be
obsoleted in a future release.
1 June 2011 Title page Resetting Document Version for Release 11s
Ariba Network Integration Guide iii

Revision History
iv Ariba Network Integration Guide

Table of Contents
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Chapter 1 Introduction to Ariba Network Integration . . . . . . . . . . . . . . . . 9

Ariba Network Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Supplier Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Document Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Basic Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Purchase Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Order Confirmations and Ship Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Invoices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Remittance Advices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Where to Go For Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
cXML Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Ariba Network User Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
The Ariba Connect Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 2 Technical Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Your Business Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Procurement Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Network Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Supplier Document Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Documents Suppliers Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Documents Suppliers Send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Internet Transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Communication Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Push Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Pull Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Supported cXML Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Profile Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Purchase Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Get Pending/Data Download Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Status Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Purchase Order Confirmations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Ship Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Invoices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Scheduled Payments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Copy Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Remittance Advice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
CC Invoice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Ariba Network Integration Guide v

Table of Contents
Chapter 3 Ariba Network Security and Reliability . . . . . . . . . . . . . . . . . . 31

Internet Channel Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Document Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Shared Secret Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Digital Certificate Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Application Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Ariba Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Your Business Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Suppliers Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Transaction Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Overview of Transaction Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Communication from Your Business Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Communication to Your Business Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Supplier Order Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Supplier Order Confirmations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Testing Document Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Testing Your Document Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Testing Suppliers Document Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Testing Document Routing Together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 4 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Supporting the cXML Requirements in Ariba Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Configuring Your Ariba Network Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Special Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Overview of Your Test Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Specifying Account Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Setting cXML Authentication Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Specifying Your URL for the Push Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Specifying Transaction Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Turning off Document Attachment Downloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Allowing Your Users to View Invoices on Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . 45
Managing Shipping Tax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Copying Tax Information to Invoices and Making Tax View-Only . . . . . . . . . . . . . . . . . 47
Allowing Higher Quantities in Order Confirmations and Ship Notices . . . . . . . . . . . . . . 48
Creating Relationships with Suppliers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Modifying Your Business Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Specifying Ariba Networks ProfileRequest URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Obtaining cXML DTDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Adding Your Network ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Adding System IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Adding Your Shared Secret. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Adding Supplier IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Adding Supplier IDs to Your Business Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Adding Private IDs for a Supplier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Linking Multiple Business Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Assigning Business Application IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Creating Multiple Bill To Addresses for a System ID . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Testing Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
cXML Document Validation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Test URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Testing with Suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Moving Settings to Your Production Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
vi Ariba Network Integration Guide

Table of Contents
Performing Ongoing Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Managing Suppliers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Managing Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Maintaining Your Organization Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Chapter 5 Developing a Network Adapter . . . . . . . . . . . . . . . . . . . . . . . . 59

Data Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Cross Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Support for MIME Envelopes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Ariba Networks Use of MIME Envelopes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
If You Do Not Support MIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Mapping Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Standard cXML Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Chapter 6 Certifying Your Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Preliminary Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Implement and Test Your Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
1. Set up a Development Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2. Configure Ariba Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3. Implement Your Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4. Test Documents and Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Apply for GSO Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Move Your Test Configuration to Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Ariba Network Integration Guide vii

Table of Contents
viii Ariba Network Integration Guide

Chapter 1 Introduction to Ariba Network Integration
Ariba Network Capabilities on page 9

Suppliers on page 10
Basic Functionality on page 11
Glossary on page 13
Where to Go For Help on page 16
Ariba Network Capabilities

Ariba Network is a global network that provides connectivity and online services to organizations engaged
in business-to-business e-commerce. Ariba Network enables buyers and suppliers to do business with each
other worldwide over the Internet and to access multiple network-delivered services to enhance interaction
and collaboration. It is a multi-protocol commerce hub that translates, validates, and routes business
documents. It contains additional services such as directory services, reporting tools, supplier tools,
payment, and sourcing.
Ariba Network provides you with a single point of integration to thousands of suppliers. Similarly, it
provides each supplier with a single point of integration to multiple large buying organizations.
You use Ariba Network to find suppliers to purchase products or services from and to invite suppliers to
form trading relationships. After suppliers accept the invitations, you can send purchase orders to them
through Ariba Network. Suppliers receive the purchase orders and return invoices.
As a buying organization, you can do the following on Ariba Network:

Search for suppliers that provide products and services you need
Invite new suppliers to form trading partnerships
Send purchase orders and receive invoices
Allow suppliers to charge your purchasing card or charge the card yourself after approving invoices
Run reports on your suppliers
Create RFXs (such as request-for-quote and request-for-proposal events)
Each buying organization and supplier has an account on Ariba Network. You use your account to configure
communication with your business application and to perform day-to-day tasks, such as inviting suppliers,
managing suppliers, reporting on your transactions, and managing orders. Ariba sends you your Ariba
Network login name and password when your organization becomes an Invoice Automation or Purchase
Order Automation member.
Ariba Network has optional services to which you can subscribe. For example, you can choose to keep
transaction data online past the standard expiration date. Similarly, suppliers have optional services, such as
Supplier Technical Support (STS). Log in to your account to see what optional services are available.
Ariba Network Integration Guide 9

Suppliers Chapter 1 Introduction to Ariba Network Integration
Suppliers
Suppliers are companies that provide products and services. Each supplier has an Ariba Network account
and can specify how it wants to receive orders and generate order confirmations, ship notices, and invoices.
Ariba Network enables suppliers to automate part of their business, providing significant advantages.
Automating the purchase order process leads to cost reductions and time savings by eliminating unnecessary
steps and manual transaction processing. Suppliers receive purchase orders that are more accurate and
timely than manually generated purchase orders. Automating the invoicing process leads to fewer billing
mistakes, improved reconciliation, and faster payment.
Supplier Relationships
You and new suppliers perform the following steps to establish a trading relationship on Ariba Network:
1 You log in to Ariba Network and invite suppliers to join the service.
2 Ariba Network automatically sends email messages that contain hyperlinks for starting the registration
process to the invited suppliers.
3 Suppliers click the hyperlinks to begin registration. On Ariba Network, they enter data about their
companies, such as addresses, fax machine numbers, the industries they serve, and the products or
services they offer.
4 After suppliers complete registration, Ariba Network grants them immediate access to preview accounts
and notifies you that they have completed registration.
5 You review their registration information on Ariba Network and create relationships with them, which
converts their accounts to production mode. Ariba Network automatically notifies suppliers through email
when their fully enabled accounts are active.
You can then use Ariba Network to send purchase orders to these suppliers and receive invoices from them.
Any supplier can register with Ariba Network; however, supplier accounts are not fully enabled until at least
one buying organization approves a relationship with them.
Document Routing
Ariba Network supports all suppliers regardless of their technical ability and infrastructure. Suppliers with
little technical infrastructure can receive purchase orders through email or fax and generate order
confirmations, ship notices, and invoices online in their Ariba Network account. Suppliers with complex
infrastructures use cXML or Electronic Data Interchange (EDI) to receive purchase orders and generate
invoices automatically.
10 Ariba Network Integration Guide

Chapter 1 Introduction to Ariba Network Integration Basic Functionality
Basic Functionality
Ariba Network Invoice Purchase Order Automation (formerly called Supplier Connectivity) are frameworks
that allow any procurement or Enterprise Resource Planning (ERP) system to connect to Ariba Network.
Buying organizations, regardless of the software they use, can access the suppliers and commerce services
available on Ariba Network.
Invoice Purchase Order Automation support the transmission of cXML purchase orders, order
confirmations, ship notices, receipts, invoices, and remittance advices. These business documents travel
between you and Ariba Network over the Internet.
Purchase Orders
Purchase orders are requests for products or services that you send to suppliers. They are created by end
users in your organization from online catalogs stored in your business application.
When Ariba Network receives a purchase order, it converts the cXML to any of the formats selected by
suppliers for order routing: email, fax, cXML, or EDI. Regardless of the order routing method used, all
suppliers can log in and view their purchase orders online in their Ariba Network account.
The following figure illustrates how Ariba Network routes purchase orders through multiple channels to
suppliers.
email
Purchase Orders
fax
Ariba cXML
Your cXML
Network Suppliers
Application
EDI
online
You can send change orders and cancel orders, which are purchase orders that modify or cancel previous
purchase orders.
Suppliers can set the ordering status of purchase order items through cXML, EDI, and online methods. They
can indicate that specific items have been accepted, rejected, or are back ordered. They can also update
purchase order shipping and tax. After shipping products, suppliers can change their status to shipped.
You can log in to your Ariba Network account and view line item status.
Order Confirmations and Ship Notices

Suppliers send you order confirmations to indicate that they will send you the items or perform the services
described your purchase orders. Suppliers send you ship notices to indicate that they have sent the ordered
items to you.
Suppliers can use cXML, EDI, or online forms to generate these documents. Your business application
accepts them from Ariba Network in cXML format.

Basic Functionality Chapter 1 Introduction to Ariba Network Integration
The following figure illustrates how Ariba Network accepts order confirmations and ship notices through
multiple channels and routes them to you.
Order Confirmations
and Ship Notices cXML
cXML Ariba EDI

Your Network Suppliers
Application
online
Invoices
Invoices are requests for payment that suppliers send to you. Suppliers can generate one or more invoices per
purchase order.
Suppliers can use cXML, EDI, or online forms to generate invoices. Your business application accepts them
from Ariba Network in cXML format. You ensure that your system can process them by configuring
business rules in your Ariba Network account. Ariba Network checks these rules when it receives invoices
and rejects any invoice that does not comply.
The following figure illustrates how Ariba Network accepts invoices through multiple channels and routes
them to you.
Invoices
cXML
cXML Ariba EDI

Your Network Suppliers
Application
online
After your business application receives invoices, your accounts payable department can perform
purchase-order-to-invoice reconciliation to match them against ordered items.
Remittance Advices
Remittance advices are notifications of payment made. They are created by your accounts payable
department to tell suppliers that payments have been made and to convey payment methods.
When Ariba Network receives remittance advices, it converts the cXML to any of the formats selected by
suppliers for remittance advice routing: email, fax, cXML, or EDI. Regardless of the order routing method
used, all suppliers can log in and view their remittance advices online in their Ariba Network accounts.

Chapter 1 Introduction to Ariba Network Integration Glossary
The following figure illustrates how Ariba Network routes your remittance advices through multiple
channels to suppliers.
email
Remittance Advices
fax
Ariba cXML
Your cXML
Network Suppliers
Application
EDI
online
Glossary
The following terms are relevant to Ariba Network Invoice Automation and Purchase Order Automation.
Term Definition
Ariba Network ID A unique identifier for a buying organization or supplier. Also called ANID and
NetworkID. Ariba Network provides these IDs and you and your suppliers cannot
change them; they have the form ANxxxxxxxxxxx.
Ariba Network username The login name of an Ariba Network account holder. These IDs have the form of an
email address; for example, judy@workchairs.com. Users can change their Ariba
Network Users IDs in their account.
Ariba Network account Each buying organization and supplier company has a password-protected supplier
account. Organizations can have multiple users who log in and perform specific
tasks.
business application An enterprise application (often an ERP system) that connects to Ariba Network to
enable you to purchase products and services. It usually resides within your firewall
and uses cXML and the Internet to connect to Ariba Network.
buying organization An entity that procures products or services. A buying organization has one Ariba
Network account.
connecting application See business application.
cXML An electronic business protocol for representing common business documents, such
(commerce eXtensible Markup as purchase orders and invoices. cXML is the only protocol your business
Language) application can use to connect to Ariba Network. See also XML.
discount management An Ariba Network feature that allows you to offer your suppliers, or your suppliers
to offer you, early payment in exchange for discounts. You set rules that determine
which of your payments to offer for early payment and your proposed discount. You
can also propose a tiered discount rate. Suppliers see your scheduled payments and
can request early payment for them, based on their cash needs. Similarly, suppliers
can request early payment with a supplier-defined discount and corresponding
revised settlement date.

Glossary Chapter 1 Introduction to Ariba Network Integration
Term Definition
EDI An electronic language for representing common business documents, such as
(Electronic Data Interchange) purchase orders and invoices. Ariba Network can convert business data between
EDI and cXML for suppliers. Ariba Network supports two EDI standards: ANSI
X12 and EDIFACT.
ERP Any software system designed to support and automate the business processes of
(Enterprise Resource Planning) medium and large businesses. ERP systems support manufacturing, distribution,
personnel, project management, payroll, and financial processing. ERP systems are
accounting-oriented information systems for identifying and planning the
enterprise-wide resources needed to receive, make, distribute, and account for
customer orders.
functional acknowledgment A confirmation that a document was received. The document receiver transmits the
acknowledgment to the document sender immediately following the receipt of a
document. The acknowledgment confirms that a document was received and is
syntactically correct.
HTTPS A communication protocol for clients and servers, commonly used over the Internet.
(Secure HyperText Transfer HTTPS is a secure protocol that encrypts communication before transmission over
Protocol) the Internet. All communication with Ariba Network travels over HTTPS
connections. HTTPS requires the server to have a digital certificate.
network adapter An add-on module that enables your business application to send and receive cXML
documents. It maps data between your business application and Ariba Network.
Network adapters can come from a third-party vendor or you can implement one
yourself.
Network ID An alphanumeric identifier that Ariba Network assigns to each organization during
account creation.
order routing The process of transmitting and converting purchase orders from your business
application to Ariba Network and then to the supplier. Suppliers specify the
purchase order format they want to receive.
password A string that users enter along with their usernames to log in to their Ariba Network
account. Users use passwords in conjunction with their Ariba Network usernames.
Users can change their password in their Ariba Network account. Do not confuse
passwords with shared secrets.
private ID An alphanumeric supplier identifier used by your business application. Ariba

Network can map these IDs to its own IDs (NetworkID) when it transfers cXML
documents to or from you.
procurement application See business application.
procurement department The department responsible for purchasing products and services and sourcing
suppliers.
pull communication A way of moving data across the Internet. The receiving party polls for data from
the sending party. Communication is initiated by the receiving party.
push communication A way of moving data across the Internet. The sending party posts information to
the receiving party. Communication is initiated by the sending party.
requisitioner A user in the buying organization who orders products or services. The requisitioner
has access to your procurement application, but does not need an Ariba Network
account.

Chapter 1 Introduction to Ariba Network Integration Glossary
Term Definition
service provider A third-party organization that provides a service to Ariba Network organizations
through integration with Ariba Network. An example of a service provider is a
credit card processor. Ariba Network uses credit card processors to process credit
card charges automatically.
shared secret A string known by an organization and Ariba Network. Shared secrets act as
passwords for authenticating cXML documents sent between Ariba Network and
the organization. Organizations can change their shared secret in their Ariba
Network accounts, but documents cannot be delivered if the shared secret in the
Ariba Network account and the cXML-enabled application do not match. Do not
confuse shared secrets with account passwords.
SSL A protocol that provides encrypted communications on networks. SSL is layered

(Secure Sockets Layer) beneath application protocols such as HTTPS and above the connection protocol
TCP/IP. The HTTPS protocol uses SSL. Transport Layer Security (TLS) is
compatible with SSL and will replace it in the future.
System ID An alphanumeric identifier you assign to each business application. This ID appears
in the header of each cXML document passed between your business application
and Ariba Network.
test account An Ariba Network account used for testing applications, documents, and
communication. Buyer test accounts can connect only with supplier test accounts.
Use test accounts for integration testing. They keep test documents separate from
production documents.
TCP/IP A communication protocol between computers, used as a standard for transmitting

(Transmission Control data over networks and as the basis for Internet protocols.
Protocol/Internet Protocol)
TLS A cryptographic protocol that is the successor to SSL. For more information, see
(Transport Layer Security) SSL.
XML A general-purpose markup language for creating special-purpose markup languages

(eXtensible Markup Language) capable of describing many types of data. XML-based languages are typically used
for passing data between Internet applications. XML-based documents contain data
in the form of tag/value pairs, similar to HTML, but Internet applications can extract
and use data from them more easily. Ariba Network accepts a specific
implementation of the cXML language.

Where to Go For Help Chapter 1 Introduction to Ariba Network Integration
Where to Go For Help

Ariba provides documentation on the technologies used by Invoice Purchase Order Automation.
cXML Resources
cXML Users GuideDescribes how to modify e-commerce websites to support PunchOut and cXML
purchase orders. Also contains a complete description of the cXML language and a table with all possible
return codes. You can view and download this manual from www.cXML.org.
cXML Release NotesDescribes new features available in the latest cXML release. You can download the
release notes from www.cXML.org.
Ariba cXML Solutions GuideDescribes the cXML behavior and restrictions of Ariba applications, such as
Ariba Network. You can download this manual from the Help@Ariba site by clicking Help at the top of any
page.
cXML Document Type Definitions (DTDs)Describe the syntax and order of cXML elements. You can
download DTDs from www.cXML.org.
Ariba Network User Documentation

Your Ariba Network account contains Acrobat PDF manuals written for buyers and suppliers. You can
download the manuals from the Help@Ariba site by clicking Help at the top of any page.
For enabling supplier through Ariba Supplier Enablement Automation, see the Ariba Supplier Enablement
Automation Guide from the Supplier Enablement tab.
The Ariba Connect Website

The Ariba Connect site contains questions, answers, and hints from other Ariba Network users. To access
the Connect site, go to connect.ariba.com.

Chapter 2 Technical Architecture
Your Business Application on page 17

Supplier Document Routing on page 18
Internet Transport on page 19
Communication Models on page 19
Supported cXML Documents on page 20
Your Business Application

To understand how Ariba Network Invoice Automation and Purchase Order Automation work, you should
understand their components (beginning with your business application), how they transport documents, and
the business transactions they support.
Your business application is a procurement or ERP system that you extend to generate and receive cXML
documents. It typically resides within your corporate firewall, although it can be hosted by an Application
Service Provider (ASP). You connect it to the Internet and configure it to communicate with Ariba Network.
Examples of these applications include Material Management Module from SAP or Maximo from MRO
Software. Some buying organizations do not use a commercial software package, choosing instead to create
their own business application.
Procurement Capabilities
Your business application generates purchase orders from internal product and service catalogs. It might
have a requisition approval flow and business logic to help users create purchase orders. It might also
generate requisitions automatically, based on input from your other systems, such as factory automation
systems.
Your business application might accept invoices from suppliers. It might allow accounting personnel to
reconcile invoices by matching them with purchase orders. It might also be part of your accounts payable
system or have connections to it.

Supplier Document Routing Chapter 2 Technical Architecture
Network Adapter
If your business application does not generate and receive cXML documents natively and you do not want to
enhance it yourself, you can use a network adapter, a translator for communicating with Ariba Network.
Network adapters are sold by Enterprise Application Integrators (EAIs).
Network adapters perform the following tasks:

Maintain connectivity with Ariba Network
Create and send outgoing cXML documents
Decode documents enclosed in MIME envelopes (optional)
Receive, validate, and parse incoming cXML documents
Map data between your application and cXML elements
Maintain cross reference information necessary for data translation
You can develop your own network adapter instead of buying a commercial one. Ariba Network uses the
cXML open standard, so it is possible for anyone with technical expertise in those standards to create a
network adapter. For more information about network adapters, see Chapter 5, Developing a Network
Adapter.
Supplier Document Routing

All communication between your business application and Ariba Network is through cXML documents over
the Internet. However, suppliers can choose their document routing method. You can see which routing
methods your suppliers select.
Documents Suppliers Receive

You send purchase orders, invoice status, scheduled payments, and remittance advices to your suppliers.
After Ariba Network receives them, it forwards them to suppliers through their online inbox, email, fax,
EDI, or cXML.
Documents Suppliers Send

Suppliers can send you order confirmations, ship notices, and invoices through their online outbox, EDI, or
cXML.

Chapter 2 Technical Architecture Internet Transport
Internet Transport
All communication between your business application and Ariba Network travels over the Internet as cXML
documents through HyperText Transfer Protocol (HTTP). For example, your business application sends a
cXML purchase order to Ariba Network through an HTTP post. Ariba Network returns a response that
acknowledges the purchase order with a status code. All applications use the HTTPS protocol to ensure that
messages are encrypted.
For purchase orders, Ariba Network is the server and your business application is the client. Regardless of
which system generates the HTTP post, Internet transport between a client and a server occurs as follows:
1 The client initiates an HTTP connection with the server on a predetermined URL.
2 The client uses a post operation to send the cXML document through the HTTP connection and then waits
for a response.
3 The server has an HTTP-compliant server that dispatches the HTTP request to the resource specified by
the URL used in step 1. This resource can be any valid location known to the servers HTTP server; for
example, a CGI program or an ASP page.
4 The servers resource reads the cXML document contents and maps the request to the appropriate handler.
5 The servers handler for the cXML request performs the work that the request specifies and formats a
cXML document as a response.
6 The server sends the cXML response to the client.
7 The client reads the cXML response and returns it to the process that initiated the request.
8 The client closes the HTTP connection.
Communication Models
When configuring your Ariba Network account, you select whether Ariba Network sends documents to your
application through either the push or pull method. The push method uses a standard HTTPS Post operation
initiated by Ariba Network. The pull method uses the cXML get pending/data download transaction initiated
by your business application. The difference between the two methods is the system that initiates
communication; push is initiated by Ariba Network and pull is initiated by your business application.
In either case, your business application always uses HTTPS Post to send documents to Ariba Network.
Push Method
The push method is the simplest to use, but it might not be compatible with your organizations security
requirements. Ariba Network sends documents to you through HTTPS Post as soon as your suppliers
generate them.
You configure this method by entering either the Profile URL or the POST URL of your business application
in your Ariba Network account. These URLs must be accessible from the Internet and they must be available
all the time so Ariba Network can send documents to it as soon as your suppliers submit them. This method
also allows your application to receive documents that are not enclosed in MIME envelopes.
For more information about the profile transaction, see Profile Transaction on page 21. To configure your
account for this method, see Specifying Your URL for the Push Method on page 42. For more information
about MIME envelopes, see Support for MIME Envelopes on page 60.

Supported cXML Documents Chapter 2 Technical Architecture
Pull Method
The pull method is more complicated to implement, but it might be more compatible with your
organizations security requirements. Ariba Network sends documents to you by storing them in a download
queue. Your procurement application polls for and retrieves them by using the cXML get pending/data
download transaction.
Your business application periodically issues cXML GetPendingRequest documents to poll for waiting
documents. Ariba Network responds with a GetPendingResponse document that contains the internal IDs of
waiting documents in the same HTTP connection. If there are waiting documents, your application issues a
DataRequest document to retrieve them. Ariba Network responds with a DataResponse that contains the
waiting document as an attachment in the same HTTP connection. Your application polls Ariba Network
regularly, such as once per hour or once per day.
This method ensures that all connections originate only from your business application. You can configure
your firewall to allow outgoing connections and disallow incoming connections. Some organizations
consider this method to be more secure because they can disallow outside parties from initiating
connections.
For more information about the get pending/data download transaction, see Get Pending/Data Download
Transaction on page 22. This transaction requires your business application to decode MIME envelopes.
For more information, see Support for MIME Envelopes on page 60.
Supported cXML Documents

Ariba Network Invoice Automation and Purchase Order Automation support the following cXML
documents and transactions:
Profile Transaction on page 21
Purchase Orders on page 22
Get Pending/Data Download Transaction on page 22
Status Updates on page 23
Purchase Order Confirmations on page 24
Ship Notices on page 24
Receipts on page 25
Invoices on page 26
Scheduled Payments on page 26
Copy Document on page 28
Remittance Advice on page 28
CC Invoice on page 29
For more information about any of these transactions, see the cXML Users Guide and Ariba cXML Solutions
Guide, both available by clicking Help at the top of any page in your account.

Chapter 2 Technical Architecture Supported cXML Documents
Profile Transaction
The cXML profile transaction (ProfileRequest/ProfileResponse) enables cXML clients to query servers for
their supported transactions and URLs. It allows servers to maintain their own supported transaction lists
without requiring the client to manually log in.
Your business application sends ProfileRequest documents to Ariba Network. If you use the push
communications method, your business application also receives ProfileRequest documents from Ariba
Network.
Sending ProfileRequest Documents

Your business application sends a ProfileRequest to Ariba Network once every 24 hours. Ariba Network
responds in the same HTTP connection with a ProfileResponse indicating the cXML documents it accepts
and their URLs. Your business application should cache the response and use the URLs it lists for the next
24 hour period.
The following figure illustrates the profile transaction.

ProfileRequest
Your
Business Ariba
Application Network
ProfileResponse
Ariba Networks URLs for receiving ProfileRequest documents are:

https://service.ariba.com/service/transaction/cxml.asp
(for shared secret authentication)
https://certservice.ariba.com/service/transaction/cxml.asp
(for digital certificate and shared secret authentication)
Ariba Network also sends a ProfileRequest document to cXML-enabled suppliers once every 24 hours to
obtain the URLs for cXML transactions they support. Each supplier could have a different set of URLs on
Ariba Network. For each of your suppliers, send a ProfileRequest document to Ariba Network to obtain
Ariba Networks URLs for that organization. Cache these URLs for up to 24 hours and use them for all
communication to that supplier. You can reduce communication overhead by querying for a suppliers URLs
only if you have documents to send to that supplier.
Receiving ProfileRequest Documents

If you use the push method, Ariba Network sends a ProfileRequest to your business application once every
24 hours to your business application. Your business application responds in the same HTTP connection
with a ProfileResponse indicating the cXML documents it accepts and their URLs. Ariba Network caches
the response and uses the URLs it lists for the next 24 hour period.
The following figure illustrates the profile transaction.

ProfileRequest
Your
Business Ariba
Application Network
ProfileResponse
You enter your business applications Profile URL when you configure your Ariba Network account.

Purchase Orders
The cXML purchase order document (OrderRequest) is a request for products or services. Your business
application sends OrderRequest documents to Ariba Network, and Ariba Network routes them to the
appropriate supplier using the suppliers preferred order routing method.
Ariba Network transmits a generic response containing a status code in the same HTTP connection as the
OrderRequest document.
OrderRequest
Your
Business Ariba
Application Network
Response
You can send change orders and cancel orders, which are purchase orders that modify or cancel previous
purchase orders by replacing the original purchase orders. You can also attach any file to purchase orders
and Ariba Network can route the file to suppliers or leave it online.
Get Pending/Data Download Transaction

The cXML get pending transaction (GetPendingRequest/GetPendingResponse) enables a client to query a
server for waiting documents. Your business application uses this transaction only if you use the pull
communication method.
The cXML data download transaction (DataRequest/DataResponse) enables a client to retrieve waiting
documents. Your business application sends GetPendingRequest documents regularly to Ariba Network to
see if there are waiting purchase order confirmations, ship notices, or invoices. If there are waiting
documents, Ariba Network responds in the same HTTP connection with a GetPendingReponse document that
contains a DataAvailableMessage document that contains the internal ID of those documents.
To retrieve waiting documents, you issue a DataRequest document containing the internal ID (one ID per
DataRequest document). Ariba Network responds in the same HTTP connection with a DataReponse
document containing the requested documents as MIME attachments.
The figure below illustrates your business application initiating communication to retrieve documents
waiting on Ariba Network:
GetPendingRequest
Your
Business Ariba
Application Network
GetPendingResponse
(containing a DataAvailableMessage document)
DataRequest
Your
Business Ariba
Application Network
DataResponse
(containing attached waiting documents)
Your application then issues a StatusUpdateRequest document to indicate that it received the document.

The get pending/data download transaction allows your application to receive documents through a pull
mechanism. You can configure your corporate firewall to allow only outbound communication and still
receive incoming documents. For more information, see Chapter 3, Ariba Network Security and
Reliability.
Status Updates
The cXML status update document (StatusUpdateRequest) allows suppliers and Ariba Network to
communicate the routing status of purchase orders. It updates purchase order routing status from accepted
and forwarded to supplier to sent, acknowledged, or failed.
You also use StatusUpdateRequest to send invoice processing status to Ariba Network and your suppliers. It
updates invoice status from sent to processing, reconciled, paying, paid, or rejected.
Note: Ariba Network currently accepts a status update of 'rejected' after an invoice has been fully
approved (previous status update was 'reconciled'). This functionality will be obsoleted in a future release
to align with Ariba Invoice Professional, which does not allow rejecting an invoice in the ERP after that
invoice was originally approved in the ERP. Ariba recommends that Invoice Automation customers
standardize on either one of the following options when rejection of a previously approved (reconciled)
invoice becomes necessary:
Have the supplier create a credit memo to reverse the original invoice (required in various European
countries)
Issue a debit memo directly in the ERP
Manually create a credit memo in Ariba Invoice Professional
Ariba Network accepts supplier input through EDI or cXML and sends a StatusUpdateRequest document to
your business application. Suppliers that use online Inbox, email, or fax cannot issue status updates.
Push Method
StatusUpdateRequest
Your
Business Ariba
Application Network
Response
Pull Method
GetPendingRequest
Your
Business Ariba
Application Network
GetPendingResponse
DataRequest
Your
Business Ariba
Application Network
DataResponse
(containing attached StatusUpdateRequest documents)
Your application issues no response if using the pull method.

Status Updates for Invoices

After you receive invoices, tell your suppliers about their status as you approve them and pay them.
StatusUpdateRequest documents for invoices contain InvoiceStatus elements.
StatusUpdateRequest
Your
Business Ariba
Application Network
Response
Purchase Order Confirmations

The cXML purchase order confirmation document (ConfirmationRequest) allows suppliers to communicate
the status of your purchase orders. Suppliers indicate ordered items they accept, reject, or have back ordered.
They can also specify values for shipping, tax, and total.
Ariba Network accepts supplier input through cXML, EDI, or online forms and sends a
ConfirmationRequest document to your business application.
Push Method
ConfirmationRequest
Your
Business Ariba
Application Network
Response
Pull Method
GetPendingRequest
Your
Business Ariba
Application Network
GetPendingResponse
DataRequest
Your
Business Ariba
Application Network
DataResponse
(containing attached ConfirmationRequest documents)
StatusUpdateRequest
Your
Business Ariba
Application Network
Response
Ship Notices
The cXML ship notice document (ShipNoticeRequest) allows suppliers to indicate when your ordered items
have shipped. Suppliers can indicate the shipment date, carrier name, tracking number, and other detailed
shipping information.

Ariba Network accepts supplier input through cXML, EDI, or online forms and sends a ShipNoticeRequest
to your business application.
Push Method
ShipNoticeRequest
Your
Business Ariba
Application Network
Response
Pull Method
GetPendingRequest
Your
Business Ariba
Application Network
GetPendingResponse
DataRequest
Your
Business Ariba
Application Network
DataResponse
(containing attached ShipNoticeRequest documents)
StatusUpdateRequest
Your
Business Ariba
Application Network
Response
Receipts
The cXML receipt document (ReceiptRequest) allows your organization to indicate that it received ordered
products or services. Receiving clerks or requisitioners in your organization create them and Ariba Network
routes them to Ariba Invoice and Payment Professional.
After your business application sends a receipt to Ariba Network, Ariba Network responds by transmitting a
generic response containing a status code in the same HTTP connection as the ReceiptRequest document.
ReceiptRequest
Your
Business Ariba
Application Network
Response
Ariba
ReceiptRequest Invoice and
Ariba Payment
Network
Professional
The receipt document is defined in the cXML Private.dtd, not in the public cXML DTDs. For more
information about the receipt document, see the Ariba cXML Solutions Guide.

Invoices
The cXML invoice document (InvoiceDetailRequest) allows suppliers to request payment for delivered
products and services.
Ariba Network accepts supplier input through cXML, EDI, or online forms and sends a
InvoiceDetailRequest to your business application. You can require suppliers to digitally sign invoices,
which ensures that the invoice content does not change after being generated by suppliers. Suppliers can also
attach any file to invoices and Ariba Network can route them to you along with invoices or leave them
online.
Push Method
InvoiceDetailRequest
Your
Business Ariba
Application Network
Response
Pull Method
GetPendingRequest
Your
Business Ariba
Application Network
GetPendingResponse
DataRequest
Your
Business Ariba
Application Network
DataResponse
(containing attached InvoiceDetailRequest documents)
StatusUpdateRequest
Your
Business Ariba
Application Network
Response
Scheduled Payments
The cXML scheduled payment document (PaymentProposalRequest) allows you to inform your suppliers
about planned payments. Your business application uses them to list payment dates and discounts. If you use
discount management, Ariba Network sends scheduled payments back to you with new dates indicating
when suppliers choose to receive early payments in exchange for discounts.

Your business application sends schedule payment documents as soon as invoices are approved for
payment. Ariba Network transmits a generic response containing a status code in the same HTTP connection
as the PaymentProposalRequest document.
PaymentProposalRequest
Your
Business Ariba
Application Network
Response
Ariba Network displays these documents to you and your suppliers in the Payments page. It does not
forward these documents to suppliers.

Copy Document
The cXML copy document (CopyRequest) allows Ariba Network to send updated scheduled payment
documents back to your business application. Ariba Network uses the copy document only if you use
discount management.
When suppliers agree to accept early payment in exchange for discounts, Ariba Network sends updated
scheduled payments back to you, each attached to a CopyRequest document.
Push Method
CopyRequest
Your
(containing an attached
Business PaymentProposalRequest document) Ariba
Application Network
Response
Pull Method
GetPendingRequest
Your
Business Ariba
Application Network
GetPendingResponse
DataRequest
Your
Business Ariba
Application Network
DataResponse
(containing attached CopyRequest documents, each
containing an attached PaymentProposalRequest document)
StatusUpdateRequest
Your
Business Ariba
Application Network
Response
Your application then issues StatusUpdateRequest documents to indicate that it received the documents.
Remittance Advice
The cXML remittance advice document (PaymentRemittanceRequest) allows you to inform your suppliers
about payment dates and payment methods. Your business application sends remittance advice immediately
after you approve payment to your suppliers.
Ariba Network transmits a generic response containing a status code in the same HTTP connection as the
PaymentRemittanceRequest document.
PaymentRemittanceRequest
Your
Business Ariba
Application Network
Response
Ariba Network displays these documents to you and your suppliers in the Payments page. It can also
forward these documents to suppliers.

CC Invoice
This feature is available only if you are using your own adapter. For more information, see Chapter 5,
Developing a Network Adapter.
The cXML CC Invoice document allows Ariba Network to receive invoice copies from your external
applications. This feature is available only if you subscribe to receiving CC invoices on Ariba Network.
Invoices originating from a buying organization's ERP system are not tracked on Ariba Network. The CC
Invoice feature allows Ariba Network to store a copy of the invoices originating from these ERP systems.
Suppliers can then log into their Ariba Network account and view the status of their invoices and monitor the
progress of the invoice through your invoice reconciliation process.
For more information, see the cXML Solution Guide.
Push Method
CopyRequest
Your
(containing an attached
Business CC Invoice document) Ariba
Application Network
Response
Pull Method
Response
Your
Business Ariba
Application Network
Status Update Request
Your application then issues StatusUpdateRequest documents to indicate that it received the documents.


Chapter 3 Ariba Network Security and Reliability
Internet Channel Security on page 31

Document Authentication on page 32
Application Security on page 33
Transaction Reliability on page 34
Testing Document Routing on page 37
Internet Channel Security

Ariba Network uses the Internet to communicate with your suppliers and you. To keep your purchasing data
confidential, Ariba Network has features that ensure that all data is secure and authentic.
Internet channel security governs the communication between Ariba Network, your business application,
and suppliers. Ariba Network requires each connecting application to use Secure HyperText Transfer
Protocol (HTTPS), which uses Secure Sockets Layer (SSL). This requirement ensures that only the intended
receiver can read the transmitted information.
HTTPS is a secure version of the standard HTTP protocol. It is secured by encrypting all data through SSL,
which is the industry standard method for protecting communications on TCP/IP networks. The SSL
standard provides data encryption, server authentication, message integrity, and optional client
authentication. HTTP creates a connection between two systems and SSL ensures that the connection is
encrypted. Both HTTP and SSL have been approved by the Internet Engineering Task Force (IETF) and are
widely used.
SSL uses secure encryption and is used by online banking, online trading, business-to-consumer, and
business-to-business sites.
To support HTTPS connections from Ariba Network, the web server used by your business application must
have a valid SSL web server certificate from a trusted certificate authority. You are responsible for obtaining,
installing, and maintaining this certificate.
For more information about digital certificates and a list of Ariba Networks trusted certificate authorities,
see the Ariba cXML Solutions Guide, available by clicking Help at the top of any page in your Ariba Network
account.

Document Authentication Chapter 3 Ariba Network Security and Reliability
Document Authentication
To ensure that received documents are authentic, all cXML-enabled applications authenticate them against a
list of trusted senders. Your business application or network adapter must perform this authentication.
Every cXML document has a sender credential to identify the sending organization. The receiving cXML
application validates that identity and decides if the sender is authorized to send on behalf of the From
credential. If the From and Sender elements identify the same organization, the receiver can assume the
organization is authorized.
You do not need to validate shared secrets in documents downloaded through the get pending/data download
transaction; they come from a trusted source, Ariba Network. You can validate Ariba Networks SSL server
certificate when you initiate the HTTPS connection.
There are two authentication methods both you and your suppliers can use: shared secret and digital
certificate. You can use a different method from your suppliers.
Shared Secret Authentication

With shared secret authentication, each cXML document contains a password known only by the sender and
the intended receiving system. The receiving system compares the documents shared secret with the one it
has stored. Mismatches indicate that the document is not valid.
Each buying organization and cXML-enabled supplier has its own shared secret, which they store on Ariba
Network when they set cXML options. When Ariba Network routes documents, it changes the shared secret
to the one used by the receiving system. For example, a purchase order you send to Ariba Network contains
your shared secret; when Ariba Network routes it to a supplier, it replaces your shared secret with the
suppliers shared secret. You do not see the suppliers shared secret and the supplier does not see your shared
secret.
Digital Certificate Authentication

With digital certificate authentication, you use a standard SSL client digital certificate, signed by a trusted
certificate authority, stored in your Ariba Network account. Both Ariba Network and your business
application refer to this certificate to ensure that each document is authentic.
You determine which authentication method to use; use the method that is most compatible with your
corporate security guidelines. If you choose digital certificate authentication, you are responsible for
purchasing, installing, and maintaining your digital certificates.
For more information about digital certificate authentication, see the Ariba cXML Solutions Guide.

Chapter 3 Ariba Network Security and Reliability Application Security
Application Security
Your purchase orders and invoices are stored in the applications that make up Ariba Network Invoice
Automation and Purchase Order Automation (Ariba Network, your business application, and suppliers
applications). Each application must allow only authorized users to see your business data.
Ariba Network
Ariba Network ensures that only qualified users can access procurement data by requiring a unique
username and password for login. Each organizations account administrator can add user accounts to the
organization. Each user account has an access control list that gives it permission to view areas within Ariba
Network.
Access to cross organization data is controlled by relationships initiated by the buying organization. A given
buying organization and supplier can see procurement data only if the buying organization has a relationship
with the supplier. Then, only the data between those specific organizations is visible. No other suppliers or
unauthorized buyers have access.
Your Business Application

You must ensure that only authorized users can view supplier catalogs, generate requisitions, and send
purchase orders. Your business application contains the proprietary prices and content from your suppliers.
Make sure it allows only approved employees and contractors to access it through a login name/password
mechanism.
You are responsible for all access to Ariba Network through your business application. Security-conscious
suppliers might ask you about your business application security when you request a trading relationship
with them.
Suppliers Applications
Suppliers can connect their order management systems to Ariba Network. They must ensure that their
systems allow only authorized users to view your purchase orders and invoices. They are encouraged to use
the same access policies as you use in your business application.
Suppliers are responsible for all access to Ariba Network that occurs through their connected applications.

Transaction Reliability Chapter 3 Ariba Network Security and Reliability
Transaction Reliability
Ariba Network has built-in reliability and error detection features to ensure that your business documents are
available to you and your suppliers immediately after they are sent and that no documents are lost.
Overview of Transaction Processing

The following steps outline the process Ariba Network uses when it receives a transaction from you or a
supplier.
1 When Ariba Network receives transactions, it first stores them in a secure database before any processing
takes place. This action ensures that no transactions are lost.
2 Ariba Network immediately sends functional acknowledgments to the sending application to indicate that
it received the transaction. If this acknowledgment does not take place, the connecting application should
consider the transaction transmission to have failed. The connecting application should automatically
resend the transaction. For more information, see Communication from Your Business Application on
page 34.
3 If an error occurs after Ariba Network acknowledges the transaction, Ariba Network sends email to your
account administrator and sets the document status to failed. If it can identify the supplier, it also sends
email to the suppliers account administrator.
4 If Ariba Network forwards the document to the supplier through cXML or EDI, the supplier must
acknowledge it. If this acknowledgment does not take place, Ariba Network considers the transaction to
have failed and it automatically resends the document. For more information, see Supplier Order
Acknowledgments on page 35.
At any time, both you and the supplier can view the status of business documents on Ariba Network.
If documents fail to route from Ariba Network for any reason, it automatically sends email messages to you
and the suppliers account administrator. The suppliers account administrator can log in to Ariba Network,
view the orders, fix the routing problem, and resend the orders by clicking the Resend button.
Communication from Your Business Application

Your business application should perform the following steps to send purchase orders or remittance advices
reliably to Ariba Network:
1 It sends a purchase order or remittance advice (cXML OrderRequest or PaymentRemittanceRequest
document) to Ariba Network. It should indicate that the documents routing status is sending.
2 It listens for an acknowledgment from Ariba Network in the same HTTP connection. The
acknowledgment is a synchronous cXML response document that contains one of the following status
codes:
200 (OK)Ariba Network accepted the document. Indicate to users that the documents routing status
is acknowledged. You will receive no further updates to the purchase order routing status.
201 (accepted)Ariba Network accepted the document and will forward it to the supplier. Indicate to
users that the documents routing status is accepted by Ariba Network. (Go to step 3 to receive
StatusUpdateRequest documents.)
280 (forwarded)Similar to code 201, except you will receive at least one status update indicating the
final state of the document. (Go to step 3 to receive StatusUpdateRequest documents.)

Chapter 3 Ariba Network Security and Reliability Transaction Reliability
281 (sent)Similar to code 201, except Ariba Network is using email, which is an unreliable
transport. You might or might not receive status updates. (Go to step 3 to receive StatusUpdateRequest
documents.)
4xx (permanent error)Ariba Network did not accept the document. Indicate to users that the
documents routing status is failed and notify the application administrator with an error and the
status text.
5xx (transient error) or there is no response after five minutesAriba Network did not accept the
document. Resend the document once an hour for the next ten hours using the same payload ID,
document ID, and time stamp. After ten hours, if Ariba Network continues to reject the document,
indicate to users that the documents routing status is failed and notify the application administrator
with an error and the status text.
3 (For status 201, 280, or 281) Ariba Network sends StatusUpdateRequest documents to update the
purchase order routing status to 201, 200, 4xx, or 5xx. Your business application receives these
documents either directly from Ariba Network (push method) or it polls for and retrieves them with the
cXML get pending/data download transaction (pull method).
Your business application should indicate the final state of the documents routing status.
Your business application should notify the application administrator with a fatal error in the case of a 4xx
(permanent error) and a warning in the case of a 5xx (transient error). It should keep a history of each
documents routing status for the administrator.
Ariba Network has test URLs for exercising your business applications handling of permanent and
temporary errors. For more information, see Test URLs on page 55.
Communication to Your Business Application

If you configure your Ariba Network account to use push communication, Ariba Network uses the same
cXML posting behavior as it does for sending cXML purchase orders to suppliers.
You must acknowledge the receipt of cXML documents by sending a generic Response document in the same
HTTP connection as Ariba Network uses to send you the cXML document. See the Ariba cXML Solutions
Guide for time outs for these acknowledgements.
For more information on push and pull communication, see Communication Models on page 19.
Supplier Order Acknowledgments

After Ariba Network receives purchase orders, it sends them to your suppliers. Ariba Networks purchase
order acknowledgment behavior depends on each suppliers document routing method.
cXML
When Ariba Network sends cXML purchase orders to suppliers, their initial routing status is sent.
Suppliers must then acknowledge them. The cXML supplier acknowledgment is a generic Response
document sent synchronously in the same HTTP connection as the cXML purchase order:
200Ariba Network sets the purchase orders routing status to acknowledged.
4xx, 5xx, or no acknowledgmentAriba Network sends email to both the buyer and the supplier account
administrators and sets the purchase orders routing status to failed.

Transaction Reliability Chapter 3 Ariba Network Security and Reliability
See the Ariba cXML Solutions Guide for time outs for these acknowledgements.
EDI
When Ariba Network sends cXML purchase orders to suppliers, their initial routing status is sent.
Suppliers must then acknowledge them. The EDI supplier acknowledgment is an X12 997 or EDIFACT
CONTRL document sent asynchronously:
Positive acknowledgmentAriba Network sets the purchase orders routing status to acknowledged.
Negative acknowledgment or no acknowledgmentAriba Network sends email to both the buyer and the
supplier account administrators and sets the purchase orders routing status to failed.
See the Ariba cXML Solutions Guide for time outs for these acknowledgements.
Online, Email, and Fax

When Ariba Network sends online, email, or fax purchase orders to suppliers, it sets the initial routing status
of these documents to sent. Suppliers cannot explicitly acknowledge them. After Ariba Network
successfully sends a fax to the suppliers fax machine, it sets the routing status to acknowledged.
Supplier Order Confirmations

Suppliers can optionally send a cXML or EDI order confirmation to confirm quantities in purchase orders
and to set the purchase order business status to confirmed.
Online, email, and fax suppliers can optionally confirm purchase orders by logging in to Ariba Network and
creating an order confirmation. A successful order confirmation sets the purchase order business status to
confirmed.

Chapter 3 Ariba Network Security and Reliability Testing Document Routing
Testing Document Routing

To ensure that you and your suppliers integrate correctly with Ariba Network, you can both send test orders.
Suppliers can also send test order confirmations, ship notices, and invoices to you.
Testing Your Document Routing

Ariba Network has document validation and transport testing tools that allow you to test your connection.
For instructions, see Testing Communication on page 54.
Testing Suppliers Document Routing

Suppliers can test their own document routing by creating mock purchase orders. They can test any order
routing method and see the effect of purchase order acknowledgments.
For more information, see the Ariba Network Catalog Administration Guide for Suppliers, available by
clicking Help at the top of any page in your Ariba Network account.
Testing Document Routing Together

After you and your suppliers test document routing separately, you can test end-to-end document routing
together. Ariba Network has test accounts to keep test documents separate from production documents. You
can send test purchase orders and receive test purchase order confirmations, ship notices, and invoices from
your suppliers.

Testing Document Routing Chapter 3 Ariba Network Security and Reliability

Chapter 4 Configuration
Supporting the cXML Requirements in Ariba Network on page 39

Configuring Your Ariba Network Account on page 39
Modifying Your Business Application on page 49
Adding Supplier IDs on page 51
Linking Multiple Business Applications on page 52
Testing Communication on page 54
Moving Settings to Your Production Account on page 56
Performing Ongoing Administration on page 57
Supporting the cXML Requirements in Ariba Network

Before you can integrate with Ariba Network, you must modify your business application to support the
cXML requirements in Ariba Network:
Business Application Requirements For more information, see

It must use the cXML profile transaction to obtain the Profile Transaction on page 21
Ariba Network URLs
It must communicate with Ariba Network only through Internet Channel Security on page 31
HTTPS
It must authenticate cXML documents with shared secrets Document Authentication on page 32
or digital certificates
These requirements ensure that all communication with Ariba Network is secure, authentic, and reliable.
Configuring Your Ariba Network Account

Ariba provides you with a username and password for logging in to your Ariba Network account. Take a few
minutes to explore Ariba Network to learn what features are available to you. You might want to change
your password to something you can remember.
To connect your business application to Ariba Network, configure your test account and test to make sure
transactions flow as expected, then make the same configuration changes to your production account.

Configuring Your Ariba Network Account Chapter 4 Configuration
Special Features
The following Ariba Network features are visible exclusively to buying organizations that subscribe to either
Ariba Network Invoice Automation or Purchase Order Automation:
POST URL field for push communication. For more information, see Specifying Your URL for the Push
Method on page 42.
Send URLs to view attachments on Ariba Network checkbox for accepting invoices, order confirmations, and
ship notices without supporting MIME envelopes. For more information, see Turning off Document
Attachment Downloading on page 44.
Allow your users to view invoices on Ariba Network checkbox to add a URL to invoices so your users can view
them on Ariba Network. For more information, see Allowing Your Users to View Invoices on Ariba
Network on page 45.
Copy tax from purchase order to invoice check box to display tax information to suppliers, and Make line item
tax on invoice read-only to prevent suppliers from editing tax information. For more information, see
Copying Tax Information to Invoices and Making Tax View-Only on page 47.
Allow shipping tax entered at header level checkbox so that suppliers can enter header level shipping tax as a
single line, and Allow shipping and special handling as separate invoice lines checkbox so that suppliers can
enter them as a separate invoice line. For more information, see Managing Shipping Tax on page 46.
Apply [invoice tolerance] rule to order confirmations and ship notices checkbox so that suppliers can exceed the
quantities specified on purchase orders without you having to issue a change notice. For more
information, see Allowing Higher Quantities in Order Confirmations and Ship Notices on page 48.
Private ID field for alternate supplier IDs. For more information, see Adding Private IDs for a Supplier
on page 51.
cXML Validate utility for checking your cXML documents. For more information, see cXML Document
Validation Utility on page 54.
Support for multiple business applications. For more information, see, Linking Multiple Business
Applications on page 52.
Ariba Network Customer Support makes these features visible when creating your account.

Chapter 4 Configuration Configuring Your Ariba Network Account
Overview of Your Test Account

Your test account is just like your production account, but it can connect only with suppliers test accounts.
Use your test account to exercise Ariba Network features, experiment with configuration settings, and test
integration with your business application. Configure your test account exactly as you would your
production account, then copy its settings to your production account.
The following figure shows communication between buyer and supplier test and production accounts:
The Ariba Network
Buyer Supplier
Production Production
Account Account
Buyer Supplier
Test Test
Account Account
Suppliers know that purchase orders in their test accounts should not be filled. Similarly, they know that
invoices they send to your test account will not be paid.
You should have two instances of your business application: a test version and a production version. The test
version should be configured to connect to your Ariba Network test account and the production version
should be configured to connect to your Ariba Network production account. After ensuring that changes in
your test configuration work as expected, copy those changes to your production configuration.
W To switch to your test account:

1 Go to buyer.ariba.com.
2 Log in to your Ariba Network production account.
3 In the masthead, click Switch to Test Account.
4 Click OK.
5 If you have not used your test account before, Ariba Network prompts you for a new username and
password. Enter the requested information and click OK.
Ariba Network logs you in to your test account.
From the login page, you can log in to your test account directly with your test account username and
password.
For more information, see the Ariba Network Buyer Administration Guide.

Specifying Account Information

Specify basic information about your account and your organization, such as:
Information about yourself (the account administrator), such as your address, telephone number, and
preferred language
Your timezone and default currency
Your organizations name, address, telephone number, and company description (include Test in your
company name so suppliers know that they are receiving test orders)
Your organizations logo on all fax, email, and online purchase orders
Your email addresses for receiving notifications of events, such as a change in a suppliers profile or an
undeliverable purchase order
Setting cXML Authentication Method

Specify your cXML document authentication method: shared secret or digital certificate. For more
information, see Document Authentication on page 32.
Specifying Your URL for the Push Method

If you receive cXML documents from Ariba Network through the push method (HTTPS Post), enter the
URL of your business application.
Note: If you use the pull method (get pending/data download transaction), do not perform this configuration.
You can enter either your Profile URL for receiving cXML ProfileRequest documents or your POST URL
for receiving business-related cXML documents. The recommended method is to enter your Profile URL.
W To specify your URL for the push method:

1 Log in to your Ariba Network account.
2 In the Property Navigator, click Manage Profile.

Ariba Network displays the Configuration page.
3 Click cXML Setup.
4 Click Yes, I want to receive documents through the POST method...

If you do not click this option, Ariba Network sends you documents through the cXML GetPending
method.

5 Enter your Profile URL, your POST URL, or both.
6 Click OK.
If you enter both URLs, Ariba Network first uses your Profile URL. If your business application returns a
ProfileResponse document that lists a URL for the cXML request waiting for you, Ariba Network uses that
URL. If your ProfileResponse does not list the cXML request, Ariba Network uses your POST URL,
instead.
If you click Yes, I want to receive documents through the POST method..., but enter no URLs, Ariba Network
makes documents available to you through the get pending/data download transaction.
The URLs you enter must have an https prefix so all communication is encrypted. These URLs must be
open to the Internet, but you can restrict access to Ariba Network only. Your business application must be
available all the time.
For more information about the push and pull communications methods, see Communication Models on
page 19. For information about MIME envelopes, see Support for MIME Envelopes on page 60.
Specifying Transaction Rules

Specify transactions rules, which determine how your Ariba Network account processes purchase orders and
invoices. For example:
Do you allow change or cancel orders
Do you accept invoices
Do you require suppliers to signed all invoices with a digital signature
Do you allow suppliers to make certain changes in invoices, such as prices, part numbers, or ship-to
addresses
Do you allow suppliers to issue a credit or debit memo for a purchase order or an invoice
Ariba Network evaluates each document it receives against these rules and it rejects any documents that do
not adhere to them.

Allowing Suppliers to Create Credit or Debit Memos

You can allow suppliers to issue a credit or debit memos for both a purchase order and an invoice.
Additionally, suppliers can also specify a line-item while creating a credit memo for an invoice. This allows
suppliers to create a credit memo for the discounts they provide you. For more information on discount
management, see the Ariba Network Buyer Administration Guide.
To enable the line-item credit memo feature, contact Ariba Network Customer Support to enable the
Line-Item Credit Memo rule for your Ariba Network account. Once this feature is enabled, you can allow
suppliers to specify the line-item.
W To allow suppliers to create credit or debit memos for purchase orders and invoices:

3 Click Transactions and find the General Rules section.
4 Click the Allow suppliers to send credit memos and debit memos check box.
W To allow line-item in credit or debit memos for invoices:

1 Contact Ariba Network Customer Support to enable the Line-Item Credit Memo rule for your Ariba
Network account.

5 Click the Allow suppliers to send credit memos and debit memos check box.
Turning off Document Attachment Downloading

If you do not support MIME envelopes, turn off downloading attachments with invoices, order
confirmations, and ship notices. Any files that suppliers attach to these documents remain on Ariba Network,
instead of being sent with the documents to your business application. You can request Ariba Network add
links to invoices, order confirmations, and credit memos so your users can view attachments on Ariba
Network.
W To turn off invoice attachment downloading:



4 Click the Send URLs to view attachments on Ariba Network check box.
5 Click OK.
If you activate this checkbox, Ariba Network adds a link so your users can view the attachments on Ariba
Network. Your business application should display this link and allow your users to click it so they can view
the attachments on Ariba Network. For more information, see Support for MIME Envelopes on page 60.
W To turn off order confirmation and ship notice attachment downloading:


3 Click Transactions and find the Order Confirmation and Ship Notice Attachment Rules section.
4 Click Leave attachments online.
5 Click OK.
If you activate this checkbox, Ariba Network adds a link so your users can view the attachments on Ariba
Network. Your business application should display this link and allow your users to click it so they can view
the attachments on Ariba Network. For more information, see Support for MIME Envelopes on page 60.
Allowing Your Users to View Invoices on Ariba Network

Note: This feature is available only if your organization uses the Ariba Network Single Sign-On (SSO)
feature, which allows users to access Ariba Network after they log in to your network. To enable SSO for
your organization, contact Ariba Network Support.
Your business application might require goods or service receipts to justify each expense before it can
successfully process invoices. If receipts do not exist, your users might need to manually create them from
information contained in invoices. Ariba Network supports this business flow.
Ariba Network can insert URLs in invoices so your users can view them online. Your business application
presents these URLs to your users to allow them to view invoices on Ariba Network. They view invoices,
invoice comments, and invoice attachments on Ariba Network and create receipts in your business
application. Your business application can then match invoices with receipts and process the invoices.
W To allow your users to view invoices online from your business application:


If this control is not visible, your account has not been enabled for SSO.
4 Click Allow users to view invoices on Ariba Network from your application.
If you turn on this feature, Ariba Network inserts the following Extrinsic as it routes invoices to you:
<InvoiceDetailRequestHeader>
...
<Extrinsic name="AribaNetwork.InvoiceDisplay">
https://service.ariba.com/Supplier.aw/ad/invoice?key=cmHTJG9FtYsbnGKEvr0zPrS7CODqT0ZmUUhaja
jN3IbSlK42TRVn&community=1
</Extrinsic>
</InvoiceDetailRequestHeader>
These URLs contain up to 132 characters. Modify your business application to display these URLs and
allow users to click them. Users will need to simultaneously view invoices on Ariba Network while they
compose receipts in your business application.
This feature does not allow users to view invoice history or download the cXML source. It requires SSO so
that users outside of your network cannot view your organizations invoices, even if they have the URL. You
do not need to create Ariba Network accounts for your users.
Managing Shipping Tax

For tax compliance, you can allow suppliers to enter shipping tax at the header level, but the shipping tax
must have the VAT amount applied. If you do not allow shipping tax at the header level, Ariba Network
allows shipping tax to be added at the line item level.
W To allow suppliers to add shipping tax at the header level:


3 Click Transactions and find the PO and Non-PO Invoice Field section.
4 Click the Allow shipping tax entered at header level check box.
5 Click OK.

W To allow suppliers to add shipping and special handling as a separate line:


3 Click Transactions and find the PO and Non-PO Invoice Field section.
4 Click the Allow suppliers to add shipping and special handling costs and tax details as separate invoice lines
check box.
5 Click OK.
If you turn on this feature, Ariba Network inserts the following Extrinsic, which indicates that
InvoiceDetailServiceItem is a shipping service line item as it routes invoices to you:
<InvoiceDetailRequest>
...
<InvoiceDetailServiceItem invoiceLineNumber="4" quantity="1">
<Extrinsic name="IsShippingServiceItem">yes
</Extrinsic>
</InvoiceDetailServiceItem>
</InvoiceDetailRequest>
Similarly, Ariba Network inserts the following Extrinsic, which indicates that InvoiceDetailServiceItem is a
special handling line item as it routes invoices to you:
<InvoiceDetailRequest>
...
<InvoiceDetailServiceItem invoiceLineNumber="4" quantity="1">
<Extrinsic name="IsSpecialHandlingServiceItem">yes
</Extrinsic>
</InvoiceDetailServiceItem>
</InvoiceDetailRequest>
Copying Tax Information to Invoices and Making Tax View-Only

Tax information in purchase orders is not automatically copied to invoices. To copy line item tax information
to invoices, click Copy tax from purchase order to invoice. If this setting is enabled, you can check Make line item
tax on invoice view-only so that the line item tax information copied to invoices is not editable by your
suppliers. If you want tax information to be copied and editable, clear this check box. Tax information will
still be adjusted automatically if the quantity changes, but only if the user does not directly change the tax
information.
Note: In Ariba Network Release 46, this setting was labeled Do you allow changes to tax information?
If the tax information on invoices is view-only, Ariba Network requires invoices to specify exactly the same
line-item taxes as corresponding purchase orders. In this case, the following line-item invoice fields are
view-only: tax amount, tax location, tax description, tax category, percentage rate, and tax purpose.

Suppliers can send invoices for a portion of ordered amounts. Ariba Network proportions line-item tax
amounts based on the percentage of the line-item quantity being invoiced. Rounding errors are possible in
these invoices. Ariba Network rounds tax amounts to the scale of the specified currency (for example, one
cent for US dollar). Special handling and shipping charges are not included in these calculations.
Ariba Network displays a new shipping tax section in the third step of the invoice generation pages, so that
your suppliers can enter tax for special handling and shipping. This section is available whether the line item
tax information is copied, editable, or view-only.
W To copy tax information to invoices:


3 Click Transactions and find the PO Invoice Fields section.
4 Click the Copy tax from purchase order to invoice check box.
If checked, tax information is copied to invoices, and suppliers can add or change line item taxes on
invoices unless the next check box is checked.
5 To make tax information view-only, click the Make line item tax on invoice view-only check box.
If checked, tax information is not editable, but will be adjusted if the quantity changes.
Allowing Higher Quantities in Order Confirmations and Ship Notices

You can apply the same rule that allows invoice quantities to exceed those on purchase orders to order
confirmations and ship notices. If checked, this rule allows suppliers with whom you have a trading
relationship on Ariba Network to ship higher quantities than those specified on a purchase order without
requiring a change order.
W To allow higher quantities in order confirmations and ship notices:


3 Click Transactions and find the PO Invoice Field section.
4 Click the Apply this rule to Order Confirmation and Ship Notice check box to apply the rule to order
confirmations and ship notices. Ariba Network does not check invoice quantities.
5 Click OK.

Chapter 4 Configuration Modifying Your Business Application
Creating Relationships with Suppliers

You can send purchase orders only to suppliers with whom you have a trading relationship on Ariba
Network. You can create trading relationships with existing Ariba Network suppliers or new suppliers:
Your test account creates relationships only with suppliers test accounts. When you move to your
production account, you must create relationships with suppliers production accounts. It is recommended
that you test with each of your suppliers to ensure that order and invoice routing work as expected. Note that
test purchase orders and invoices look the same as production purchase orders and invoices, however, you
and your suppliers might route them to a test location.
Modifying Your Business Application

Your business application must have Ariba Networks URLs and the cXML DTDs to generate and route
purchase orders. Additionally, after you configure your Ariba Network account, you can add your shared
secret and your suppliers IDs to your business application.
Specifying Ariba Networks ProfileRequest URL

Instruct your business application to post cXML ProfileRequest documents to one of the following URLs:
https://service.ariba.com/service/transaction/cxml.asp
(for shared secret authentication)
https://certservice.ariba.com/service/transaction/cxml.asp
(for digital certificate and shared secret authentication)
These URLs do not change, however Ariba Networks other URLs can change at any time. For more
information about the cXML ProfileRequest document, see Profile Transaction on page 21.
Obtaining cXML DTDs

Your business application should validate all generated and received cXML documents against the cXML
Document Type Definition (DTD) files. It should either cache these files dynamically or manually. cXML
versions do not change after they are released, so you can cache DTD files permanently. cXML DTD files
are available at www.cXML.org.
Ariba periodically releases new cXML DTD versions. Your business application must be able to validate
cXML documents that use new cXML versions. It can download new DTDs either automatically or
manually. If you use manual downloading, you must pay attention to the cXML release schedule.
For more information about cXML DTDs, see the cXML Users Guide.

Modifying Your Business Application Chapter 4 Configuration
Adding Your Network ID

The documents you send and receive contain both your shared secret and your Network ID. Ariba creates
your Network ID (also called ANID or NetworkID) during the creation of your account.
W To view your Network ID:

2 Your Network ID appears in the masthead, for example: AN02000000123. Test account IDs have a -T
appended to them.
Add your Network ID to your business application.
Adding System IDs

If you have multiple business applications that you want to use with a single Ariba Network account, modify
them to insert their System IDs in any cXML documents they generate. For more information, see Linking
Multiple Business Applications on page 52.
Adding Your Shared Secret

If you use shared secret cXML document authentication, add your shared secret to your business
application. Each Ariba Network buying organization and cXML-enabled supplier has its own shared secret
for communicating with Ariba Network. For more information, see Document Authentication on page 32.
The header of each cXML document you generate must contain your shared secret. If you change your
shared secret on Ariba Network, you must also change it in your business application or your documents
cannot be delivered.

Chapter 4 Configuration Adding Supplier IDs
Adding Supplier IDs

Your business application and Ariba Network must refer to your suppliers with the same identifiers. You can
either copy supplier IDs from Ariba Network to your business application or copy them from your business
application to Ariba Network.
Ariba Network supports four supplier ID domains in cXML documents:

NetworkIDA unique alphanumeric value assigned by Ariba Network to every organization registered on
Ariba Network; for example, AN010000000123. Organizations can see their own and their trading partners
Network IDs by logging on to Ariba Network.
DUNSA unique number assigned to organizations by Dun & Bradstreet (for example, 942888741). To look
up Dun & Bradstreet D-U-N-S numbers, go to www.dnb.com.
PrivateIdA unique alphanumeric value defined by you for a particular supplier; for example,
Supplier123. When Ariba Network receives documents from you, it maps these IDs to NetworkID. When
Ariba Network sends documents to you, it maps suppliers NetworkID, DUNS, and AribaNetworkID to
PrivateId. Suppliers cannot use this domain in cXML documents they send or receive.
AribaNetworkUserIDA login name of an Ariba Network user (for example, judy@workchairs.com). This
domain is not preferred because if suppliers change their login names, cXML documents will fail to route.
Adding Supplier IDs to Your Business Application

If your business application can map supplier IDs, look them up in your Ariba Network account and
configure them in your business application. When your business application generates cXML documents, it
maps its internal supplier IDs to IDs recognized by Ariba Network.
The preferred domain is NetworkID. To see your suppliers Network IDs, log in to your Ariba Network
account, click the Administration tab and then click Supplier Relationships. Ariba Network displays each
suppliers name and Network ID in your list of current suppliers. Test account IDs have a -T appended to
them.
Adding Private IDs for a Supplier

This feature is available only to Invoice Automation, Purchase Order Automation, and Ariba Procure-to-Pay
buying organizations.
If your procurement application cannot map supplier IDs, configure Ariba Network to map the supplier ID
from your procurement application to the suppliers Ariba Network ID. This ensures that you can continue to
refer to your suppliers by their private ID internally, but all transactions are routed to one Ariba Network
account.
PrivateId values can have any format (for example, supplier123), but they must be unique per
buyer-supplier relationship.
For more information on this feature, see the Ariba Network Buyer Administration Guide.

Linking Multiple Business Applications Chapter 4 Configuration
Linking Multiple Business Applications

If your organization has more than one business application, you can create an ID for each of them in Ariba
Network. This allows you to easily manage all transactions with suppliers using a single Ariba Network
account. To use multiple business applications with a single Ariba Network account, you must create a
System ID for each business application.
Assigning Business Application IDs

You can use multiple business applications by assigning a unique System ID to each of them. This ID helps
Ariba Network identify your business application. You can also assign one or more Bill To addresses to each
System ID.
You can edit the System ID assigned to a business application. When you modify the System ID, you must
ensure that you change them in your business applications. Your business applications must use the same
System IDs as you have configured in your account.
Note: You cannot delete a System ID.
W To create a System ID:

1 On the Administration tab, click Configuration.
2 On the Configuration page, click Business Application IDs.
3 Click Create. Ariba Network displays the Create a System ID page.
4 Enter a unique name in the System ID text box.

The System ID helps Ariba Network identify a business application. Ensure that the System ID is unique
for each of your business applications.
5 Enter a unique name in the Unique Address ID text box.
The Address ID helps Ariba Network identify the Bill To address for a System ID assigned to your
business application.
6 Enter the contact name and address.
7 Click Save. Ariba Network displays the System ID and Unique Address ID for your business application
in the Manage Business Application IDs page.

Chapter 4 Configuration Linking Multiple Business Applications
Note: Be sure your business applications cXML adapter adds this System ID to the header of any cXML
documents that it sends AN.
Creating Multiple Bill To Addresses for a System ID

You can specify one or more Bill To addresses for a System ID. This helps suppliers choose a Bill To address
when they create an invoice. Each System ID must have at least one Bill To address associated.
W To create a Bill To address:

1 On the Administration tab, click Configuration
2 Click Business Application IDs.
3 Click the link you want to modify in the System ID column. Ariba Network displays the Manage Business
Application IDs page.
4 Click Create. Ariba Network displays the Specify Bill To Address for your system ID page.
5 Enter a unique address ID, contact name and address.
6 Click Save. Ariba Network returns to the Manage Business Application IDs page.
7 Repeat steps 3-5 to create another Bill To address.

Testing Communication Chapter 4 Configuration
Testing Communication
You can test communication only after you have created a relationship with at least one supplier. Ariba
Network accepts purchase orders only if they are addressed to a specific supplier.
cXML Document Validation Utility

Ariba Network provides a way to see whether documents contain valid cXML. Your test account has a
cXML validation utility that validates documents against a set of Ariba Network specific rules. Use this
utility when developing support for cXML documents. Validate each of the document types you develop
before sending them to Ariba Network.
W To validate a cXML document:

1 Log in to your Ariba Network test account. The document validation utility is available only in your test
account.
2 Choose Contact Support from the Help menu in the masthead.
3 Below the cXML Validate section, click here.

Ariba Network displays the cXML validate utility:
4 Click Browse to navigate to your cXML file. You can also paste a cXML document into the box.
5 Click Validate.

Chapter 4 Configuration Testing Communication
Ariba Network loads your document and validates it. If there are errors, they appear at the top of the page.
You can fix errors in the box and click Validate again to see whether the document passes validation.
Test URLs
Ariba Network has three test URLs you can use to exercise your business applications handling of
permanent errors (4xx) and temporary errors (5xx). Use these URLs as negative test cases.
https://service.ariba.com/ANCXMLDispatcher.aw/ad/cxml400Test
This URL returns a random 4xx status regardless of your cXML document. Use this URL to test your
business applications permanent error handling.
https://service.ariba.com/ANCXMLDispatcher.aw/ad/cxml500Test
This URL returns a random 5xx status regardless of your cXML document. Use this URL to test your
business applications temporary error handling.
https://service.ariba.com/ANCXMLDispatcher.aw/ad/cxmlUniqueTest
This URL returns a 200 status half of the time and a 5xx status half of the time. Use this URL to test your
business applications retry capability and to make sure duplicate documents do not appear in your Ariba
Network Outbox.
For information about how your business application should behave for 4xx and 5xx errors, see
Communication from Your Business Application on page 34.
Testing with Suppliers

After performing basic integration testing, test with your suppliers test accounts. You can test with one or
multiple suppliers.
Purchase Order Routing to Suppliers
W To test purchase order routing:

1 In your business application, create a purchase order and send it to Ariba Network.
2 Log in to your Ariba Network test account.
3 Check the purchase order in your Outbox tab.
4 Ask the supplier to log in to Ariba Network and check its Inbox tab for the purchase order.
5 Ask the supplier to check the purchase orders final destination (email mailbox, fax machine, cXML
application, or EDI application).
Verify that you can also send change orders, cancel orders, and orders with attachments.

Moving Settings to Your Production Account Chapter 4 Configuration
Receiving Documents from Suppliers
W To test receiving documents from suppliers

1 Ask the supplier to send a purchase order confirmation, a ship notice, and an invoice. The supplier can
send these documents online, through cXML, or through EDI.
2 Log in to your Ariba Network test account.
3 View the document sent by the supplier.

Order Confirmations and ship notices display in the order details page in your Outbox tab. Invoices
display in your Inbox tab.
4 Receive the documents in your business application, depending on whether you configured push or pull
methods:
Method Description
Push No action is required. Ariba Network posts documents to your business application as soon as you
generate them.
Pull Trigger your business application to poll for documents through the cXML get pending/data
5 Ensure that your business application correctly authenticates, validates, and parses the received
documents.
If you support invoice attachments, ask your supplier to send an attachment and verify that your business
application can download it.
Moving Settings to Your Production Account

After testing the integration of your business application with Ariba Network, log in to your production
account and configure it to use all the settings from your test account. There should be no difference between
these two accounts, except your business applications URLs if you have two instances.
Invite and activate the production accounts of suppliers with which you want to trade. Add the suppliers
production Network IDs to your business application.

Chapter 4 Configuration Performing Ongoing Administration
Performing Ongoing Administration

As the administrator of your Ariba Network account, there are regular administrative tasks for which you are
responsible. For a complete list of all the functions you control, see the Ariba Network Buyer Administration
Guide. The main tasks are listed below.
Managing Suppliers
You are responsible for supplier management on Ariba Network. That entails inviting, activating, and
deactivating supplier accounts.
Invite and activate new suppliers to create a trading relationship with them. It is recommended that you
invite and activate suppliers first from your test account, test order and invoice routing, then invite and
activate them with from your production account. Each time you add new suppliers, add their Network IDs
to your business application or enter your own ID for them in the Private ID field in your account.
When you stop purchasing from a supplier, terminate your relationship with it. Terminating your
relationship removes it from your list of active suppliers. If the supplier has no other customers on Ariba
Network, Ariba Network deletes the suppliers account after a period of time.
Managing Users
You are responsible for creating Ariba Network users for other individuals in your organization and
assigning permissions to them. Also, you are responsible for resetting passwords when users forget them.
You are the first person your users call when they have questions about their accounts.
Managing Reports
You are responsible for defining and generating reports. You are also responsible for modifying reports as
your business needs them changed.
Maintaining Your Organization Data

You are responsible for logging in regularly and making sure your organization information and business
rules are up to date. New suppliers need this information to properly identify your organization. Your
suppliers also depend on this data to set up automatic order receiving and invoicing systems.
You are also responsible for keeping your email addresses in your account up to date. These addresses are
the primary way Ariba Network notifies you about failed orders or other events that require your attention.

Performing Ongoing Administration Chapter 4 Configuration

Chapter 5 Developing a Network Adapter
Data Mapping on page 59

Cross Reference Information on page 60
Support for MIME Envelopes on page 60
Mapping Process on page 62
Standard cXML Header on page 63
Data Mapping
Your business application and Ariba Network communicate with each other, but maintain their own data
sets. Your network adapter maps fields between your business application and Ariba Network. The
documents consumed and generated by your network adapter must use the standards and data dictated by
cXML and Ariba Network.
The data elements, or fields, used by your business application might differ from the data elements used in
cXML documents. Your network adapter provides a mechanism for mapping field names and data from your
business application to those used by cXML and Ariba Network. It determines how data from your business
application populates a corresponding cXML document and performs two-way mapping: from your business
application to cXML and from cXML to your business application.
For example, SAP applications might have a field named Material Group that classifies items in a
purchase order, but in cXML OrderRequest (purchase order) documents, this field is named Commodity
Code. When sending a purchase order, the network adapter must equate Material Group with
Commodity Code and use the correct field name and the correct classification system.
Another example is units of measure. Your business application might order items using American National
Standards Institute Units of Measure (ANSI UOM) while Ariba Network requires items to be measured in
United Nations Units of Measure (UNUOM). Your network adapter must provide a mechanism to map these
UOMs.
These examples show a one-to-one mapping. The element mapping mechanism must be sophisticated
enough to handle many-to-one and one-to-many mapping scenarios.

Cross Reference Information Chapter 5 Developing a Network Adapter
Cross Reference Information

Your network adapter maintains a set of cross reference or lookup tables to enable mapping. These tables
store the information necessary to translate values when sending or receiving cXML documents.
The following data elements are likely to require some translation or mapping:
Supplier IDs
Part Numbers
Commodity Codes
Currency Codes
Units of Measure
Language Codes
Country Codes
Times and Dates
Telephone Number Formats
Address Formats
The cXML/Ariba Network standard for each of these elements is described in the Ariba cXML Solutions
Guide, available by clicking Help at the top of any page in your Ariba Network account.
Data mapping should be flexible enough to be optional or required as determined by the data type of each
element. For example, if your business application uses the same canonical data type as Ariba Network (for
example, ISO 4217 for currency codes), then no translation is necessary. In this case, cross reference
information is not required and no error should result from lack of currency cross reference information.
However, other data might require cross reference information and your network adapter should generate an
error when it detects missing information.
Support for MIME Envelopes

Decide whether your network adapter will decode MIME (Multipurpose Internet Mail Extensions)
envelopes. Ariba Network uses MIME envelopes to transport one or more files in an HTTP document.
Ariba Networks Use of MIME Envelopes

Ariba Network uses MIME envelopes in the following cases:
When it sends documents to you through the get pending/data download transaction
When it sends attachments to you with invoices, order confirmations, and ship notices
When it sends updated scheduled payments to you for discount management

Chapter 5 Developing a Network Adapter Support for MIME Envelopes
If You Do Not Support MIME

Supporting MIME is optional. If you do not support MIME, you must:
Use push, not pull communication. Pull communication uses the get pending/data download
transaction, which uses MIME envelopes to send documents to you. Push communication uses a simple
HTTP Post operation to a URL that you enter in your Ariba Network account. For more information, see
Communication Models on page 19.
Disable sending invoice, order confirmation, and ship notice attachments. Configure your Ariba
Network account to leave attachments in your account. For more information, see Turning off Document
Attachment Downloading on page 44.
You can request Ariba Network to add links to invoices, order confirmations, and ship notices so your
users can view attachments on Ariba Network. For documents that have attachments, Ariba Network
removes the attachments and inserts a link similar to the following:
<InvoiceDetailRequestHeader>

<Comments>
<Attachment>
<URL>https://svcdev.ariba.com/Supplier.aw/ad/getAttachment?key=vdS
vdSCkwLYMTCfUN2fo6QLHij3dFug6PIFUGgPvKQorvQH&attId=1000000000000
</URL>
</Attachment>
</Comments>
</InvoiceDetailRequestHeader>
Display this link to your users so they can view attachments on Ariba Network.
You might find it easier to also disallow purchase order attachments in your business application, because
purchase orders attachments must reside in MIME envelopes.
Do not use discount management. For discount management, Ariba Network sends you updated
payment proposal documents attached to CopyRequest documents in a MIME envelope. If you do not
support MIME, do not use discount management.

Mapping Process Chapter 5 Developing a Network Adapter
Mapping Process
Your network adapter should perform the following process to generate cXML documents and transport
them to Ariba Network. This example shows the transmission of a purchase order, but the process is similar
for other types of documents.
1 Accept requisitions or purchase orders from your business application. If it accepts requisitions, it might
need to partition information to create purchase orders. Requisitions can contain items sold by multiple
suppliers, but purchase orders must be for a single supplier.
2 Verify that all mandatory data needed to compile a valid cXML purchase order is available.
3 Map data elements and names used by your business application to data elements and names used by
cXML/Ariba Network.
4 Issue a warning or an error for the following cases:
Mandatory data is missing
Mapping for a mandatory element is missing
A mandatory element must be mapped, but the source or destination entry in the cross reference table
does not exist
If the purchase order cannot be processed, trigger your network adapters failed purchase order procedure
and allow the system administrator to analyze the problem. An exception might not always be necessary.
For example, some elements are mandatory to conform to certain standards, but they are not internally
verified, for example: unit of measure or currency symbols.
5 Create a cXML purchase order (OrderRequest) document, based on the cXML standard as published at
cXML.org. Your network adapter can optionally validate the cXML document against the cXML DTDs.
6 If 24 hours have passed since you obtained Ariba Networks URLs, obtain them again by sending cXML
ProfileRequest documents through HTTPS post to Ariba Network. Ariba Network responds with its set
of supported transactions and their URLs, and your suppliers URLs on Ariba Network, which your
network adapter should use for the next 24 hours. For more information, see Profile Transaction on
page 21.
7 Send the purchase order to Ariba Network using an HTTPS post. Wait with the connection open for a
response from Ariba Network.
8 Ariba Network responds with a transport acknowledgement that contains a status code. Interpret this code
to determine if the transmission was successful. All supported status codes are explained in the cXML
Users Guide.
If the status code indicates that Ariba Network did not receive the purchase order, trigger your network
adapters failed order procedure.
9 Ariba Network processes the purchase order based on the suppliers preferred purchase order routing
configuration. It formats and queues the purchase order for routing to the supplier.
10 When EDI and cXML suppliers receive the purchase orders, they issue functional acknowledgments.
Ariba Network sends these to your business application through either the push or pull methods.
For more information about transmission reliability and retry behavior, see Transaction Reliability on
page 34.

Chapter 5 Developing a Network Adapter Standard cXML Header
Standard cXML Header

All cXML documents have a standard document header. The header contains address information, just like
an email message. The header contains the following elements:
Element Description Notes for Purchase Orders

DOCTYPE The cXML version
cXML Uniquely identifies the document Values are set automatically by your business
application
From Credential The originator Identifies your organization
To Credential The destination Identifies the supplier
Sender Credential The relaying entity Same value as the From Credential
SharedSecret A string known only to the sender and Configure your shared secret in your Ariba
Ariba Network Network account. You do not need a shared
secret if you use digital certificate
authentication.
UserAgent Identifies the system that created the The name of your network adapter and its
document version number
For example:
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE cXML SYSTEM "http://xml.cxml.org/schemas/cXML/1.2.013/cXML.dtd">
<cXML payloadID="933694607@host.buyer.com" xml:lang="en-US"
timestamp="2004-08-15T08:36:47-07:00">
<Header>
<From>
<Credential domain="NetworkID">
<Identity>AN01000000123</Identity>
</Credential>
</From>
<To>
<Credential domain="PrivateId">
<Identity>Supplier456</Identity>
</Credential>
</To>
<Sender>
<Credential domain="NetworkID">
<Identity>AN01000000123</Identity>
<SharedSecret>abracadabra</SharedSecret>
</Credential>
<UserAgent>ACME Oracle Adapter V1.2</UserAgent>
</Sender>
</Header>
Append a -T to NetworkID attribute values for test accounts; for example AN01000000123-T. Your test
account can communicate only with test supplier accounts.
Ariba Network changes cXML headers as it routes documents between you and your suppliers. For
example, it changes the Sender element. The suppliers ID in this example uses the PrivateId domain. Ariba
Network can map from this domain to the NetworkID domain. For more information, see Adding Private
IDs for a Supplier on page 51.

Standard cXML Header Chapter 5 Developing a Network Adapter
For more information, see the cXML Users Guide and Ariba cXML Solutions Guide, both available by
clicking Help at the top of any page in your account.

Chapter 6 Certifying Your Adapter
Preliminary Steps on page 65

Implement and Test Your Adapter on page 65
Apply for GSO Certification on page 67
Move Your Test Configuration to Production on page 67
Preliminary Steps
Ariba must certify that your adapter works with Ariba Network, whether you use an adapter from Ariba or
you develop your own. Certification is the process by which Aribas Global Services Organization (GSO)
inspects and approves your adapter, the cXML documents it generates, and its connection to Ariba Network.
Before you implement your adapter, learn about Supplier Connectivity, cXML, and the communication
requirements of Ariba Network.
1 Read the relevant documentation:
Ariba Network Adapter for SAP NetWeaver Setup Guide or Ariba Network Adapter for Oracle Fusion
Middleware Setup Guide (if using an adapter from Ariba)
Ariba cXML Solutions Guide
Ariba Network Buyer Administration Guide
Ariba Network Integration Guide (this guide)
2 Download the Ariba Network Integration Certification files from connect.ariba.com. The files are in a zip
archive. Unzip them after downloading.
Two files are of particular importance:
SampleDocuments.txtA description of the business scenario represented by the example documents.
TestProcedure.txtStep-by-step certification instructions.
Implement and Test Your Adapter

In this step, you implement your adapter and test it to make sure it can send and receive documents.
1. Set up a Development Instance

Set up a development instance of your business application and implement and test your adapter to work
with that instance. Do not test with a production instance of your business application.
You might find it convenient to use a source-code control system, such as SCCS or Perforce. These systems
give you control over the files used for adapter development and allow you to revert to previous versions.

Implement and Test Your Adapter Chapter 6 Certifying Your Adapter
2. Configure Ariba Network

Ariba gives you an Ariba Network buyer account and permission to create a supplier account.
1 Configure your Ariba Network buyer test account.
2 Invite a new supplier from your buyer account by providing your own email address. Create and configure
the supplier test account and then enable it from your buyer test account.
For more information, see Configuring Your Ariba Network Account on page 39.
3. Implement Your Adapter

Whether you use an Ariba Adapter or develop your own, the implementation steps are similar.
1 Install the Ariba Adapter or choose an application framework to write your own adapter.
2 Develop implementations of all cXML documents you support. Use the example cXML documents that
come with the certification files.
3 Add any Extrinsic elements you support to your cXML document implementations. Extrinsic elements
transmit data that is not part of the cXML standard to and from your suppliers.
4 Ensure your adapter can connect to the Internet. It needs only to be able to generate HTTPS posts, not
receive them. For more information, see Communication Models on page 19.
5 Add the Ariba Network IDs (ANIDs) of the buyer and supplier test accounts and your cXML shared
secret to your adapter.
For more information, see Chapter 5, Developing a Network Adapter.
4. Test Documents and Communication

Test your cXML documents, communication with your business application, and communication with Ariba
Network.
1 cXML SyntaxTest your documents with the Ariba Network cXML validator utility. For more
information, see cXML Document Validation Utility on page 54.
2 Basic ConnectivityTest the cXML transport used by your adapter by sending cXML ProfileRequest
documents to Ariba Network. Ariba Network should respond with a cXML ProfileResponse document.
3 Outgoing DocumentsTest purchase orders, change orders, and remittance advices. Log in to your
buyer account to view each of these documents.
4 Incoming DocumentsGenerate order confirmations, ship notices, and invoices from a supplier test
account. Download them into your adapter, depending on whether you use the push or pull methods:
Method Description
Push No action is required. Ariba Network posts documents to your business application as soon as you
generate them.
Pull Trigger your business application to poll for documents through the cXML get pending/data
Look for these documents in your business application.

Chapter 6 Certifying Your Adapter Apply for GSO Certification
5 Error HandlingTest negative transaction handling:

Use Ariba Networks 5xx and 4xx test URLs to test your adapters error handling. For more
information, see Test URLs on page 55.
Test duplicate transaction errors.
Test network busy (inbound and outbound) handling.
For step-by-step instructions on sending and receiving documents, see the TestProcedure.txt file, which is
part of the Ariba Network Integration Certification files.
Apply for GSO Certification

After verifying that your adapter works as planned, ask Aribas GSO group to certify your adapter
implementation.
1 Schedule a certification meeting with GSO.
2 GSO inspects and reviews the following processes:

Your implementation and testing details
cXML document formatting
cXML document posting and receiving
System error handling
Your GSO representative might perform certification at your site or remotely.
Move Your Test Configuration to Production

After GSO certifies your adapter, move your settings to your Ariba Network production account and invite
your suppliers. For more information, see Moving Settings to Your Production Account on page 56,
Test your production setup by issuing a few test documents. For example, you might order a non-existing
product from a supplier. Be sure the supplier knows that you are testing. These test documents ensure that
your production account is working as expected.
After you are satisfied that your production setup is working, tell your users how to use your business
application to generate purchase orders and receive invoices.
You must also start performing regular administration. For more information, see Performing Ongoing
Administration on page 57.

Move Your Test Configuration to Production Chapter 6 Certifying Your Adapter

Index
A credentials 32, 63
accepted 34 credit memo 44
adapter. See network adapter currency codes 60
address 42, 60 Customer Support 40
ANID 50 cXML 13
ANSI X12 14 DTD files 49
Application Service Provider (ASP) 17 header 63
Ariba Invoice and Payment Professional 25 preferences 42
Ariba Network 9 requirements 39
account 13 validation 54
cXML requirements 39 cXML documents 29
test URLs 55
Ariba Network ID 13
D
Ariba Network Invoice Automation 11
Ariba Network Purchase Order Automation 11 data download transaction 22
Ariba Network User ID 13 data mapping 59
Ariba SN dates and times 60
URLs 21 debit memo 44
AribaNetwork.InvoiceDisplay Extrinsic 46 default currency 42
attachments for invoices 61 digital certificate authentication 32
attachments, with invoices, order confirmations, ship digital certificate for SSL 31
notices 44 digital signature 26, 43
authentication 32 discount management 13
scheduled payments and 26
use of MIME envelopes for 60, 61
B DOCTYPE 63
business application 13, 17 document authentication 32
Business Application IDs 52 Dynamic Discounting. See discount management
buying organization 13
E
C early payment See discount management
cancel orders 22, 43 EDI 14
catalogs 17 EDIFACT 14
CC invoices 29 ERP 14
certificate 31 existing suppliers 49
certifying an adapter 65
change orders 22, 43
F
commodity codes 60
communication models (push vs. pull) 19 features for integration with Ariba Network 40
ConfirmationRequest 24 forwarded 34
confirmations, purchase order 24 from credential 63
connecting application. See business application functional acknowledgment 14, 34
connector. See network adapter
copy invoice 29
CopyRequest document 28 G
country codes 60 get pending transaction 22
creating relationships with suppliers 49 Global Services Organization (GSO) 65

Index
H procurement application. See business application

Help@Ariba website 16 production account 56
HTTP 19, 31 profile transaction 21
Profile URL 42
pull communication 14, 19, 23
I Purchase Order Automation features 40
purchase orders 11, 22
inviting suppliers 49
attachments 22
Invoice Automation features 40
confirmations 24
InvoiceDetailServiceItem 47
routing 18
InvoiceDisplay Extrinsic 46
push communication 14, 19, 21, 42
invoices 12
allowing higher quantities in 48
attachments 26, 61 R
attachments with 44
copying tax information from purchase orders 4748 ReceiptRequest 25
display 45 receipts 25
InvoiceDetailRequest document 26 remittance advices 12, 28
routing 18 reports 57
rules for 43 requirements 39
InvoiceStatus element 24 requisitions 62
RFX events 9
routing
L purchase orders 18
ship notices 18
language codes 60
line item credit memo 44
logo 42 S
scheduled payments 26
M sender credential 32, 63
sent 35
mapping 59
shared secret 15, 32, 50, 63
MIME 60
ship notices 11
allowing higher quantities in 48
N attachments 61
attachments with 44
network adapter 14, 18, 59 documents 24
network adapter certification 65 routing 18
Network ID 50 shipping service line item 47
new suppliers 49 shipping tax section, on invoices 48
notifications 42 Single Sign-On (SSO) 45
special handling line item 47
SSL 15, 31
O
SSL web server certificate 31
order confirmations 11 status codes 34
allowing higher quantities in 48 status update document 23
attachments 61 subaccounts 57
attachments with 44 supplier IDs 51, 60
routing 18 Supplier Technical Support (STS) 9
OrderRequest 22 suppliers 10, 49
adding private IDs for 51
System ID 15, 52
P
part numbers 60
PaymentProposalRequest 26 T
PaymentRemittanceRequest 28 tax in invoices 4748
permanent error 35 TCP/IP 15
POST URL 42 telephone number 42, 60
private IDs, adding 51

Index
test account 15, 41

test URLs 55
times and dates 60
timezone 42
TLS 15
to credential 63
trading relationships 49
transient error 35
U
units of measure 60
URL of your application 42
URLs for viewing invoices 45
user agent 63
V
validation utility 54
view-only invoices 4748
W
web server certificate 31
X
XML 15

Index

Ariba Network IntegrationGuide11s1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ariba Network IntegrationGuide11s1

Uploaded by

Copyright:

Available Formats

Ariba Network

For these users:

Document Month/Year of Updated Short Description of Change

Ariba Network Integration Guide iii

iv Ariba Network Integration Guide

Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Chapter 1 Introduction to Ariba Network Integration . . . . . . . . . . . . . . . . 9

Chapter 2 Technical Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Ariba Network Integration Guide v

Chapter 3 Ariba Network Security and Reliability . . . . . . . . . . . . . . . . . . 31

vi Ariba Network Integration Guide

Performing Ongoing Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 5 Developing a Network Adapter . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 6 Certifying Your Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Ariba Network Integration Guide vii

viii Ariba Network Integration Guide

Ariba Network Capabilities on page 9

Ariba Network Capabilities

As a buying organization, you can do the following on Ariba Network:

Ariba Network Integration Guide 9

10 Ariba Network Integration Guide

Order Confirmations and Ship Notices

Ariba Network Integration Guide 11

cXML Ariba EDI

cXML Ariba EDI

12 Ariba Network Integration Guide

connecting application See business application.

Ariba Network Integration Guide 13

private ID An alphanumeric supplier identifier used by your business application. Ariba

procurement application See business application.

14 Ariba Network Integration Guide

SSL A protocol that provides encrypted communications on networks. SSL is layered

TCP/IP A communication protocol between computers, used as a standard for transmitting

XML A general-purpose markup language for creating special-purpose markup languages

Ariba Network Integration Guide 15

Where to Go For Help

Ariba Network User Documentation

The Ariba Connect Website

16 Ariba Network Integration Guide

Your Business Application on page 17

Your Business Application

Ariba Network Integration Guide 17

Network adapters perform the following tasks:

Supplier Document Routing

Documents Suppliers Receive

Documents Suppliers Send

18 Ariba Network Integration Guide

8 The client closes the HTTP connection.

Ariba Network Integration Guide 19

Supported cXML Documents

20 Ariba Network Integration Guide

Sending ProfileRequest Documents

The following figure illustrates the profile transaction.

Ariba Networks URLs for receiving ProfileRequest documents are:

Receiving ProfileRequest Documents

The following figure illustrates the profile transaction.

Ariba Network Integration Guide 21

Get Pending/Data Download Transaction

22 Ariba Network Integration Guide

Your application issues no response if using the pull method.

Ariba Network Integration Guide 23

Status Updates for Invoices

Purchase Order Confirmations

24 Ariba Network Integration Guide