ASC Adapter NW

Ariba™
Supplier
Connectivity
Adapter for SAP
NetWeaver Guide
Release 1.4
Document Version 2
February 2008
Copyright © 1996–2008 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. are registered
trademarks of Ariba, Inc. Ariba Spend Management, Ariba. This is Spend Management, Ariba Solutions Delivery, Ariba Analysis, Ariba Buyer, Ariba
Category Management, Ariba Category Procurement, Ariba Contract Compliance, Ariba Contracts, Ariba Contract Management, Ariba Contract Workbench,
Ariba Data Enrichment, Ariba eForms, Ariba Invoice, Ariba Payment, Ariba Sourcing, Ariba Spend Visibility, Ariba Travel and Expense, Ariba Procure-to-
Pay, Ariba Workforce, Ariba Supplier Network, Ariba Supplier Connectivity, Ariba Supplier Performance Management, Ariba Content Procurement, Ariba
PunchOut, Ariba QuickSource, PO-Flip, Ariba Spend Management Knowledge Base, Ariba Ready, Ariba Supply Lines, Ariba Supply Manager, Ariba LIVE,
It’s Time for Spend Management and Supplier Lifecycle Management 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,225,152; and 7,249,085. 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; and 7,117,165. Patents pending.
This documentation may reference trademarks of third parties, and the software and/or services described in this documentation may include software licensed
from third parties. For third-party trademark, software license and/or copyright information, go to http://www.ariba.com/copyrights.cfm.
14b.0047.en_us
Table of Contents
Chapter 1 Ariba Supplier Connectivity Adapter . . . . . . . . . . . . . . . . . . . . 7

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Setting Up the cXML Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Understanding cXML Adapter Document Transmission . . . . . . . . . . . . . . . . . . . . . . . . . 10
Deploying the cXML Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Configuring the Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Configuring the cXML Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Configuring the System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Importing Ariba SN Product and Component Definitions . . . . . . . . . . . . . . . . . . . . . . . . 13
Defining Technical and Business Landscape for Ariba SN . . . . . . . . . . . . . . . . . . . . . . . 14
Defining Technical and Business Landscape for SAP R/3 . . . . . . . . . . . . . . . . . . . . . . . . 15
Defining Technical and Business Landscape for NetWeaver XI File System . . . . . . . . . 16
Configuring Transaction Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Importing the Design Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuring R/3 Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuring SAP NetWeaver XI Value Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuring Integration Scenarios in the Integration Directory . . . . . . . . . . . . . . . . . . . . 24
Linking Multiple SAP instances with Ariba SN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Data Element Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Supported cXML Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Customizing Data Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configuring Supplier Quick Enablement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Configuring AN Pay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Enabling Support for Shipping and Handling Charges for Invoices. . . . . . . . . . . . . . . . . 83
Testing the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Testing Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Understanding Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Deploying the Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Ariba SN Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Chapter 2 Configuring Your SAP ERP System . . . . . . . . . . . . . . . . . . . . . 91

Importing Custom Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Creating a Vendor Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Creating Additional Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Creating an RFC-enabled Function Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Configuring SAP IDocs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide iii

Table of Contents
Configuring SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Configuring SAP for IDoc Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Configuring the Partner Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Maintaining Condition Records for Outbound Transactions . . . . . . . . . . . . . . . . . . . . . 103
Making Additional Change PO Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Maintaining Variants for Remittance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Making Additional Invoice Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Maintaining Bank Key for the House Bank for Payment Remittance Advice . . . . . . . . 105
Making User Exit Enhancements to Support Shipping and Handling Charges . . . . . . . 105
Maintaining Global Company Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Appendix A cXML Adapter Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 109

Common Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Inbound Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Outbound Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Configuring Retry Attempts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Configuring Proxy Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
iv Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide

Chapter 1 Ariba Supplier Connectivity Adapter
The Ariba Supplier Connectivity Adapter (ASC Adapter) for SAP NetWeaver is an add-on module for SAP
business applications that allows them to send and receive commerce eXtensible Markup Language (cXML)
documents to and from Ariba Supplier Network (SN).
This document describes how to install, configure, customize, and test the ASC Adapter. It includes the
following sections:
• “Overview” on page 7
• “Requirements” on page 9
• “Setting Up the cXML Adapter” on page 10
• “Configuring Transaction Processes” on page 17
• “Data Element Mapping” on page 79
• “Testing the Configuration” on page 83
• “Deploying the Project” on page 89
For more information about cXML and Ariba SN, refer to the following documents, available from
http://connect.ariba.com:
• Ariba SN Supplier Connectivity Guide

• Ariba SN Buyer’s Guide
• Ariba cXML Solutions Guide
• cXML User’s Guide
Overview
The ASC Adapter implements round-trip communication between your SAP ERP system and Ariba SN. It
allows your SAP ERP system to send and receive cXML documents to and from Ariba SN by mapping data
elements between IDoc and cXML.
The ASC Adapter runs on the SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI), and can be
thought of as a library for SAP NetWeaver XI. This library includes integration processes and Java libraries
that implement the cXML transport protocol and provide a set of facilities for resolving differences between
SAP and Ariba SN.
The ASC Adapter consists of three parts:

• The design package, which contains integration processes, interface objects, and mappings to convert
IDoc to cXML and cXML to IDoc
• The cXML Adapter, which conforms to the J2EE Connector Architecture (JCA) specification, and
implements the cXML transport protocol
For more information about the JCA specification, see the relevant section on the Sun Java website
(http://www.java.sun.com)
Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide 7

Overview Chapter 1 Ariba Supplier Connectivity Adapter
• The Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide (this document) illustrating the
deployment and configuration processes of the Ariba Supplier Connectivity integration package within
SAP NetWeaver XI.
Note: SAP has renamed XI (Exchange Infrastructure) to PI (Process Integration). You can treat all references
to XI in this guide, as references to PI.
Figure 1 illustrates how the ASC Adapter enables the communication flow between Ariba SN and the SAP
ERP system.
Figure 1 Architecture Overview
Ariba Supplier Connectivity

Adapter
Integration Engine Adapter Engine
Ariba
cXML Q iDoc cXML JCA https
SAP Adapter
cXML Supplier
transformations Messages
ERP Network
NetWeaver Exchange Infrastructure
SAP NetWeaver XI is a platform for process integration within SAP NetWeaver. It facilitates cross-system
business processes. In particular, it enables different versions of SAP and non-SAP systems from different
vendors running on different platforms to communicate with each other.
SAP NetWeaver XI integrates the following components used by the ASC Adapter and its modules:
• The Business Process Engine is a runtime component of the SAP NetWeaver XI Integration Server. It
processes the integration processes at runtime.
• The Integration Engine is the central runtime component of the SAP NetWeaver XI Integration Server
used for receiving, processing, and forwarding messages.
• The Adapter Engine is a runtime component of the SAP NetWeaver XI Integration Server. It uses
adapters to connect the Integration Engine to SAP systems (RFC adapter) and external systems.
W To use the ASC Adapter:

1 Ensure that you have met all the software and connectivity requirements described in “Requirements” on
page 9.
2 Configure an Ariba SN account. For more information, see “Installation Requirements” on page 9.
3 Install and configure the cXML Adapter and Log mechanism. For more information, see “Setting Up the
cXML Adapter” on page 10.
4 Configure transaction processes. For more information, see “Configuring Transaction Processes” on
page 17.
5 Configure the SAP ERP system. For more information, see Chapter 2, “Configuring Your SAP ERP
System.”
6 Test the configuration. For more information, see “Testing the Configuration” on page 83.
8 Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide

Chapter 1 Ariba Supplier Connectivity Adapter Requirements
Requirements
The ASC Adapter requires, at a minimum, SAP NetWeaver XI 3.0 with SAP NetWeaver 2004 SP 16 and
above. It is also compatible with SAP Process Integration 7.0 with SAP NetWeaver 7.0 (2004s) SPS 07 and
above.
For more information about the SPS and compatibility between SAP NetWeaver 2004 and 7.0, see the
following SAP NetWeaver section on the SAP Service Marketplace: services.sap.com > SAP NetWeaver >
SAP NetWeaver 7.0 (2004s) Support Package Stacks > Support Package Stacks Information.
For information about the platforms that the SAP NetWeaver suite supports, see the following SAP
NetWeaver section on the SAP Service Marketplace: services.sap.com > SAP NetWeaver > SAP NetWeaver
7.0 > Availability.
Installation Requirements
To install the ASC Adapter, you need:
• The ASC Adapter archive file, ASCAdapterNetweaver_v1.4.zip, available from Connect
(http://connect.ariba.com). To download the archive file, log in to Connect, and navigate to Software
Online > Download Software. This file contains:
Product definition files ASCAdapterNetweaver.SoftwareCatalog.zip
Mapping design and ASCAdapterNetweaver.Design.tpz

Integration configuration files ASCAdapterNetweaver.FileStruct.zip*
cXML Adapter and metadata AribaSupplierConnectivityAdapter.sda
definition files CacheCatalog.xml
CanonicalCatalog.xml
Ariba_MetaData.xml
SAP configuration files Global_Data.txt

LZ_ARIBA_OPEN_NETWORKF01.txt
Z_ARIBA_RFC_READ_TABLE.txt
Z_ARIBA_PO_ACCOUNTING_INFO.txt
Z_ARIBA_INVOICE_STATUS_UPDATE.txt
Z_ARIBA_PAYMENT_PROPOSAL.txt
Tip: Before you install the packages, please note the following:
• If you are installing the adapter for the first time, import the ASCAdapterNetweaver.Design.tpz, which
has the design packages for all the transactions.
• If you are an existing user of the ASC Adapter, and wish to install only some of the transactions,
import the corresponding design files. For example, to install the Purchase Order transaction, import
the ASCAdapterNetweaver.PurchaseOrder.tpz file.
To install the two new transactions added in this release, import the design files along with the
corresponding IDoc meta data file. For the Payment Remittance Advice transaction, import the
ASCAdapterNetweaver.PaymentRemittanceAdvice.tpz file along with the IDoc meta data file
ASCAdapterNetweaver.ACC_Document_Idoc.tpz. For the new Invoice transaction, import the
ASCAdapterNetweaver.ZInvoice.tpz file along with the IDoc meta data file
ASCAdapterNetweaver.Invoic_Invoic02_ZInvoic02.tpz file.

Setting Up the cXML Adapter Chapter 1 Ariba Supplier Connectivity Adapter
Note: * The <Root> mentioned throughout this document corresponds to the folder where you extracted the
ASCAdapterNetweaver.FileStruct.zip file.
• Connection information for your SAP ERP system.

• A valid, configured Ariba SN Buyer account. For more information about configuring your Ariba SN
Buyer account, see Chapter 4, “Configuring Supplier Connectivity” in the Ariba SN Supplier
Connectivity Guide.
• An Ariba SN supplier relationship, including an ANID-to-Private ID mapping. For more information
about creating a supplier relationship, see Chapter 4, “Configuring Supplier Connectivity” in the Ariba
SN Supplier Connectivity Guide.
• If the Ariba SN Buyer account is configured to use digital certificate authentication, then a valid Secure
Socket Layer (SSL) client certificate from one of Ariba SN’s trusted Certificate Authorities is required.
For more information about obtaining a digital certificate, see Ariba cXML Solutions Guide.
Ariba SN requires that all communication between the ASC Adapter and Ariba SN travel over the
internet using Secure HyperText Transfer Protocol (HTTPS), a secure protocol that encrypts
communication before transmission. For more detailed information about internet connectivity
requirements, see the Ariba SN Supplier Connectivity Guide. For more information about how to enable
secure communications through a proxy server, see the “Configuring Proxy Server Parameters” section.
• The latest Support Package for SAP Exchange Infrastructure and its related software components. For
more information, see SAP NetWeaver ‘04 Support Package Guide - SAP NetWeaver Support Package
Stack <stack_number> (service.sap.com/instguidesNW04).
If the system is to be used in a High Availability environment, perform the post-installation steps as
described in the High Availability Guide - SAP NetWeaver XI 3.0 (service.sap.com/instguidesNW04 >
Operations > SAP NetWeaver XI).
Setting Up the cXML Adapter

The ASC Adapter relies upon the cXML Adapter, which conforms to the JCA specification and implements
the cXML transport protocol.
This section describes how to set up the cXML Adapter, in the following topics:
• Understanding cXML Adapter Document Transmission
• Deploying the cXML Adapter
• Configuring the Log
• Configuring the cXML Adapter
Understanding cXML Adapter Document Transmission

Ariba SN exchanges business documents using the cXML (commerce eXtensible Markup Language)
protocol. cXML defines document formats and interaction processes designed for exchanging
procurement-oriented information.
The ASC Adapter always uses HTTPS Post to send documents to Ariba SN.

Chapter 1 Ariba Supplier Connectivity Adapter Setting Up the cXML Adapter
The ASC Adapter initiates the cXML GetPending transaction to pull inbound business documents. The
GetPending transaction allows the SAP ERP system to receive documents from Ariba SN through a data
pull.
The GetPending transaction is scheduled using the getPendingInterval parameter defined for each inbound
transaction. Ariba SN responds with a GetPendingResponse document that includes zero or more
DataAvailableMessage elements containing the internal ID of any waiting documents.
For more information about document transmission methods, see the Ariba SN Supplier Connectivity Guide.
For details on downloading this guide, see “To download the Ariba SN Supplier Connectivity Guide from
Connect: ” on page 90.
Deploying the cXML Adapter

Use the Software Deployment Manager (SDM) tool to deploy the cXML Adapter on SAP NetWeaver XI.
W To install the cXML Adapter:

1 Navigate to the SDM tool directory *****\SDM\program.
For example, D:\usr\sap\ARB\DVEBMGS00\SDM\program.
2 Double-click remoteGui.bat to open the Software Deployment Management GUI window.
3 Click the first button in the top toolbar to open the login window.
4 Enter your password in the login window, and then click the Login button to enter the SDM tool.
5 On the Deployment tab, click the + button on the tool bar, and then select the SDA file to be deployed from
the pop-up window.
6 After the SDA file is loaded, click Next to start the deployment.
7 Click Next in the next window.
8 Click Start Deployment in the next window to deploy the cXML Adapter.
9 Click Confirm to accept the change.

10 On the Undeployment tab, check whether the adapter has been deployed successfully.
If the name com.ariba.asc.sap.netweaver.xiadapter.ra is in the list in the left panel, the adapter can
be considered successfully deployed.
Installing Additional Resources

The validation engine uses the following files to resolve and identify the location of the DTDs related to the
exchanged cXML documents:
• CacheCatalog.xml
• CanonicalCatalog.xml
To install these files, copy the files to the following folder: <Root>/etc/catalog/.
Configuring the Log

You must configure the log using the following steps, to set the cXML Adapter to log to a separate file.

Setting Up the cXML Adapter Chapter 1 Ariba Supplier Connectivity Adapter
W To set properties for logging to a separate file:

1 Navigate to the J2EE Visual Administrator tool directory, *****\j2ee\admin.
For example, D:\usr\sap\ARB\DVEBMGS00\j2ee\admin.
2 Double-click go.bat to open the Visual Administrator window.
3 Click Connect in the pop-up window to display the login window.
4 Enter your password to log in to Visual Administrator.
5 In the left panel of Visual Administrator, click Cluster tab, and then expand the Server***** node.
6 Expand the Kernel node, and verify if the value for the property ForceSingleTraceFile is set to YES. If it is,
set the property to configure the cXML Adapter to log to a separate file, as follows:
SingleTranceFile_UnrestrictedLocation = com.ariba.asc
7 Click Update, and then click the Save button in the toolbar to save the change.
Next, set properties for the Log Configurator.
W To set properties for the Log Configurator:

1 Log on to Visual Administrator tool.
2 In the left panel of Visual Administrator, click the Cluster tab, and then expand “Server*****” node.
3 Expand the Services node, and then select the Log Configurator service.
4 Click the Locations tab in the right panel and navigate to the package com.ariba.asc.
5 Select the “asc” node to set the logging level to log the complete adapter processing information, or
“CXMLSender” under connector.cxml.util to set the logging level to log only the exchanged messages.
6 Change the severity level from Error to Info in the Severity drop-down list, and then click Save in the
toolbar.
Note: The default log level is Error; after SAP NetWeaver XI restart, it will be reset to Error. The log level
can remain Error when running in a production environment, but Ariba recommends that you change the log
level to Info.
Configuring the cXML Adapter

To allow the cXML adapter to run correctly, you must configure parameters for the Communication
Channels for different business scenarios. This configuration is done at a later stage, during the
configuration of Integration Scenarios in the Integration Directory. For more details about how to create the
Communication Channels, see the Communication Channels Configuration procedure for each scenario in
the “Configuring Integration Scenarios in the Integration Directory” section. For a description of the
parameters and instructions for how to configure retry attempts, see Appendix A, “cXML Adapter
Parameters.”

Chapter 1 Ariba Supplier Connectivity Adapter Configuring the System Landscape Directory
Configuring the System Landscape Directory

Once you have installed the cXML Adapter, you must then configure the System Landscape Directory
(SLD) by importing the ASC Adapter product definition and defining the systems involved in the
intergration. The SAP System Landscape Directory is a central repository that holds the information on the
systems and software in the customer environment. It consolidates the information about components
actively available, and on which machines, instances, and clients they are available.
The ASC Adapter leverages all the advantages of the SLD in order to maintain the coherence of the system
landscape:
• It is defined as a product and component expressed in Common Information Interface (CIM) format
importable in the SLD
• It uses a configuration using technical and business systems involved in the Ariba SN integration and
defined in the SLD.
You must make the following settings in the SLD:

• Import Ariba SN Product and Component definitions
• Define Technical and Business Landscape for Ariba SN
• Define Technical and Business Landscape for SAP R/3
• Define Technical and Business Landscape for NetWeaver XI File System.
Importing Ariba SN Product and Component Definitions

Import the product and component definitions of Ariba products that will work with SAP NetWeaver XI, as
a CIM file.
W To import product and component definitions:

1 From the XI main page, open the SLD administration home page.
2 Navigate to the Content section, and then click on Import.
3 Select the ASCAdapterNetweaver.SoftwareCatalog.zip by clicking on the Browse button, and then

navigating to the file location.
4 Start the import.
5 In the Product Catalog, verify that the following product is available:

• Vendor: ariba.com
• Product: ASN
• Version: NW04.1
6 Next, verify that the following component is available:

• Vendor: ariba.com
• Component: ERP_ASN_4.6C
• Version: 1.0
The ASC Adapter will now be recognized by the Integration Repository and Directory.

Configuring the System Landscape Directory Chapter 1 Ariba Supplier Connectivity Adapter
Defining Technical and Business Landscape for Ariba SN

Set up the technical landscape for the Ariba SN system using the Technical Landscape Wizard.
W To define the Technical Landscape for Ariba SN:

1 Select Technical Landscape from the main SLD page to open the Technical Landscape page.
2 Click on New Technical System here to open the Technical System Wizard.
3 In the Wizard, select Third-Party as the Technical System Type to set up a third-party (non-SAP)
application such as Ariba SN, and then click on Next.
4 Specify the system details as follows:
• System Name: Specify a user-defined system name here. E.g. TS_ASN
• Host Name: Enter “an” as the host name.
Important: Ariba recommends the use of fully qualified Host names.
5 Click on Next.
6 Associate the ASC Connector product and component to the system next. Select the product ASN, defined
earlier, and then click on Add. Ensure that the component ERP_ASN_4.6C, is selected.
7 Click on Finish.
Next, set up the business landscape for the Ariba SN system using the Business Landscape Wizard.
W To define the Business Landscape for Ariba SN:

1 Select Business Landscape from the main SLD page to open the Business Landscape page.
2 Click on New Business System here to open the Business System Wizard.
3 In the Wizard, enter the business system name, e.g. BS_ASN, and then click on Next.
4 Select Third-Party as the Technical System Type, and then click on Next.
5 Associate the new business system with the required Technical System. Select the technical system,
TS_ASN, created in the previous procedure, from the drop down list, and then click on Save.
Note: The Logical System Name is not required.
6 Specify the installed products. Make sure that the product ASN, NW04.1 and the related component
ERP_ASN_4.6C, 1.0 of ariba.com, installed on the technical system, are selected, and then click on Next.
7 Select the role of the business system. The only available Business System Role for a third-party Business
System is Application System. Select your SAP NetWeaver XI instance name from the drop-down list, to
specify the Related Integration Server.
8 Click on Finish.

Chapter 1 Ariba Supplier Connectivity Adapter Configuring the System Landscape Directory
Defining Technical and Business Landscape for SAP R/3

Set up the technical landscape for the SAP R/3 system using the Technical Landscape Wizard.
W To define the Technical Landscape for SAP R/3:

3 In the Wizard, select Web AS ABAP as the Technical System Type, and then click on Next.
4 To specify the SAP R/3 system details enter the Web AS ABAP name (SID), installation number, and
database host name, and then click on Next.
5 Specify the Message Server and Central Application Server. Enter the Host Name, Message Port, and
Logon Groups for the Message Server. Enter the Host Name and Instance Number for the Central
Application Server, and then click on Next.
6 Define additional application servers if required. Enter the Host Name and Instance Number for the
Application Server, and then click on Add.
7 Click on Next.
8 Define the Client. Enter the Client Number, and then click on Next.
9 To add a Logical System Name, enter the system name, and then click on Add. The logical system name is
required for enabling the communication using IDocs between the SAP NetWeaver XI and R/3 systems
and is used for routing documents in multi-ERP implementations. For more information about Multi-ERP
implementations, see the “Linking Multiple SAP instances with Ariba SN” section.
10 Define software product and components. Select the SAP R/3 version installed on this technical system,
as well all other products installed on the system, and then click on Add.
11 Click on Finish.
Next, set up the business landscape for the SAP R/3 system using the Business Landscape Wizard.
W To define the Business Landscape for SAP R/3:

3 In the Wizard, enter the business system name. E.g. BS_SAPR3_46C
4 Click on Next.
5 Select Web AS ABAP as the Technical System Type, and then click on Next.
6 Select the technical system created in the previous procedure from the drop down list, to associate it with
the business system, select a client for the selected technical system, and then click on Next.
7 Specify the installed products. Select the products that must be supported by this business system from
the ones available from the associated technical system, to install them in the business system, and then
click on Next.
8 Select the role of the business system. Select Application System as the Business System Role and select
your SAP NetWeaver XI instance name from the drop-down list to specify the Related Integration Server.
In the case of application systems, specify the integration server.
9 Click on Finish.

Configuring the System Landscape Directory Chapter 1 Ariba Supplier Connectivity Adapter
Defining Technical and Business Landscape for NetWeaver XI File System

ASC Adapter uses the local SAP NetWeaver XI file system for storing timestamp files used for the
following scheduled transactions: InvoiceStatusUpdate, PaymentProposal, and Receipt. You must define the
Technical and Business Systems to represent this file system in the Integration Directory.
Set up the technical landscape for the NetWeaver XI file system using the Technical Landscape Wizard.
W To define the Technical Landscape for XI File System:

3 In the Wizard, select Third Party as the Technical System Type, and then click on Next.
4 To specify the system details, enter the Third Party system name, for example TS_File, and the host, and
then click on Next.
5 This step is optional. To add a Logical System Name, enter the system name, and then click on Add.
6 Define software product and components next. Select the SAP NetWeaver XI product (SAP Exchange
Infrastructure) installed on the XI server, and then click on Add.
7 Click on Finish.
Next, set up the business landscape for the NetWeaver XI file system using the Business Landscape Wizard.
W To define the Business Landscape for XI File System:

3 In the Wizard, enter the business system name, for example BS_File, and then click on Next.
4 Select Third Party as the Technical System Type, and then click on Next.
5 Associate the new business system with the required Technical System. Select the technical system
TS_File, created in the previous procedure, from the drop down list, and then click on Next.
Note: The Logical System Name is not required.
6 Specify the installed products. Select the products to be installed in the business system, and then click on
Next.
7 Select the role of the business system. The only available Business System Role for a third-party Business
System is Application System. Select your SAP NetWeaver XI instance name from the drop-down list, to
specify the Related Integration Server.
8 Click on Finish.

Chapter 1 Ariba Supplier Connectivity Adapter Configuring Transaction Processes
Configuring Transaction Processes

Once you have installed the SLD, you must then:
• Import the design package containing the transactions supported by the ASC Adapter.
• Configure SAP NetWeaver XI connectivity to R/3.
• Configure SAP NetWeaver XI value mapping to provide the global configuration, and supporting
facilities such as IDoc Payload and standard code conversions.
• Configure the different transactions in the Integration Directory by importing the scenarios from the
Integration Repository.
• Configure the communication channels and the conditions for routing messages, for each supported
transaction.
Note: The names for objects in the Directory used in the configuration procedures are examples provided for
illustration. You may use them or replace them with names and format corresponding to your system
environment.
Importing the Design Package

The transport file ASCAdapterNetweaver.Design.tpz contains the definition of the business scenarios.
W To import the design package:

1 Copy the package file ASCAdapterNetweaver.Design.tpz to the import directory on the SAP NetWeaver XI
server, *****\SYS\global\xi\repository_server\import.
For example, D:\usr\sap\ARB\SYS\global\xi\repository_server\import.
2 Open the Integration Builder: Design Tool from the SAP NetWeaver XI main page.
3 From the Tools menu, select the Import Design objects... option.
4 Select ASCAdapterNetweaver.Design.tpz from the available files list, and then click on OK.
5 After the import completes, the component ERP_ASN_4.6, 1.0 of ariba.com appears in the components
list of the Integration Builder Design Tool.
Configuring R/3 Connectivity

To enable communication between SAP NetWeaver XI and SAP R/3 using IDoc documents, we need to
configure the following parameters on the SAP NetWeaver XI ABAP stack:
• Configure the RFC Destination.
• Configure the Port for the IDoc Adapter SAP NetWeaver XI connectivity to R/3.
W To configure R/3 connectivity:

1 Using Transaction SM59, create an RFC destination of type R/3 to connect to the SAP R/3 system.
2 Using Transaction IDX1, create a Port for the new RFC destination. For example, for the SAP R/3 system
D47 client 800, you must use specify following parameters to create the port:
• Port: SAPD47.
• Client 800.

Configuring Transaction Processes Chapter 1 Ariba Supplier Connectivity Adapter
• RFC Destination: Specify the destination created in SM59 here.
Important: Enter the password in UPPER case.
Assigning Business Systems in the Integration Directory

The Integration Directory configuration of the ASC Adapter uses the information on the Technical and
Business systems from the SLD. You must assign the Business Systems defined and involved in the
integration setup.
W To assign a business system:

1 Open the Configuration: Integration Builder from the XI main page.
2 In the Objects tab of the Integration Builder, navigate to Service Without Party>Business System.
3 From the context menu for Business System, select Assign Business System to start the Assign Business
System wizard.
4 Click on Continue in the first and second windows. Leave the Party field in the second window blank.
5 In the third window, Select Business Systems, select the business systems BS_ASN, BS_SAPR3_46C, and
BS_File createdearlier, from the list. For more information about creating business systems, see the
“Configuring the System Landscape Directory” section.
Note: In the case of Multi-ERP implementation, you must select all the Business Systems representing
your SAP R/3 instances involved in the integration.
Note: Uncheck the Create Communication Channel Automatically option, if it is checked, to avoid the creation
of unwanted channels.
6 Click Finish.
Creating Communication Channels for R/3

Create the communication channels used for R/3 connectivity. You must create the IDoc Receiver and RFC
Receiver communication channels from the Integration Builder, to enable communication using IDocs and
the RFC invocation on the remote SAP R/3 system. These channels will be used by almost all the scenarios
and are common to all of them. So, you only need to create them once, for each Business System
corresponding to your SAP R/3.
W To create the IDoc Receiver communication channel:

1 In the Objects tab of the Integration Builder, navigate to Service Without Party>Business
System>BS_SAPR3_46C>Communication Channel.
2 From the context menu for Communication Channel select New.
3 In the Create Object window, specify CC_IDoc_Receiver as the name of the communication channel in the
Communication Channel field, and then click on Create.
4 From the Parameters tab of the Edit Communication Channel window, click on the icon next to the Adapter
Type field to display the list of adapter types. From the adapter type list window, select the following
adapter, and then click on OK:
• Name: IDoc
• Namespace: http://sap.com/xi/XI/System

• Software Component Version: SAP BASIS 6.40
5 After selecting the adapter, click on the Receiver option, to select the corresponding type.
6 In the Adapter Engine field, select Integration Server or non-central Adapter Engine, depending on your
configuration.
7 Edit the other parameters, to match your SAP R3 system (RFC Destination, Interface Version, Port, SAP
Release).
8 Select the following options and leave the others unchecked:
• Apply Control Record Values From Payload
• Take Sender From Payload
9 Save and activate the communication channel.
Note: In the case of Multi-ERP implementation, you must create one CC_IDoc_Receiver channel per Business
System, representing each of the SAP R/3 instances involved in the integration.
W To create the RFC Receiver communication channel:

1 In the Objects tab of the Integration Builder, navigate to Service Without Party>Business
System>BS_SAPR3_46C>Communication Channel.
2 From the context menu for Communication Channel, select New.
3 In the Create Object window, specify CC_RFC_Receiver as the name of the communication channel, in the
Communication Channel field, and then click Create.
4 From the Parameters tab of the Edit Communication Channel window, click on the icon next to the Adapter
Type field to display the list of adapter types. From the adapter type list window, select the following
adapter and click OK:
• Name: RFC
• Namespace: http://sap.com/xi/XI/System
• Software Component Version: SAP BASIS 6.40
5 After selecting the adapter, click on the Receiver option, to select the corresponding type.
6 In the Adapter Engine field, select Integration Server or non-central Adapter Engine, depending on your
configuration.
7 Edit the other parameters to match your SAP R3 system (Application Server, System Number,
Authentication Mode, Logon User, Logon Password, Logon Language, Logon Client).
Important: Enter the password in UPPER case.
8 Edit the Maximum Connections option according to the excepted load.
9 Save and activate the communication channel.
Note: In the case of Multi-ERP implementation, you must create one CC_RFC_Receiver channel per Business
System, representing each of the SAP R/3 instances involved in the integration.

Creating Communication Channels by Copy (Optional)

You can create a Communication Channel from the Integration Scenario Configurator/Assign Services step
using the Communication Channel Create Wizard by copying from an already existing channel. In this case,
a similar type of Communication Channel Receiver or Sender needs to have been created and configured
before.
The main advantage of this approach is that the new channel will copy the configuration parameters from the
source channel and you need to change only a few parameters. This eliminates the need to fully configure
the new channel.
W To create a communication channel by copy for Ariba SN Business Service:

1 In the Connections from the Service Assignment tab in the Configure Connection window, click on the empty
Communication Channel cell corresponding to BS_ASN in the Receiver Business System Services for A2A
table.
2 Click on the New button, and then select Create Communication Channel as Copy to start the Create
Communication Channel wizard
3 Click on Continue, and then select the source Communication Channel used as the model to create the new
channel.
4 Click on Continue, and then enter the name for the new channel
5 Click on Finish.
6 At the Channel Configuration step, you will need to change the new channel's configuration parameter
RequestType to match the new transaction served by this channel. For example, for Advance Ship Notice
change the RequestType to ShipmentNoticeRequest. You must set the Adapter Type parameter to Receiver or
Sender, and set appropriate values for other relevant parameters.
Configuring IDoc Metadata (Optional)

This procedure allows you to preload the metadata of the IDoc documents exchanged by the IDoc adapter
during configuration. It is optional as, if you skip it, the metadata information will be downloaded and
associated to the port, the first time a given type of IDoc is exchanged.
Check and configure the IDoc Metadata parameters of the port to communicate with the SAP R/3 system in
SAP NetWeaver XI. Refer to the transaction IDX2. Check the IDoc Metadata in Metadata Overview for the
IDoc Adapter to see if all the inbound IDocs (ORDERS05, DESADV01, INVOIC02 and FIDCCH01) are there. If
they are not, click Metadata > Create to add them.

Configuring SAP NetWeaver XI Value Mapping

Configure SAP NetWeaver XI value mapping for supporting facilities such as IDoc Payload and standard
code conversions.
Configuring Units of Measure (UOM) Code Mapping

As part of the transformation of documents from IDoc to cXML, or vice versa, certain codes, such as UOM,
need to be mapped between different standards. This section provides the steps to configure these mappings.
In the value mappings, use the following parameters for UOM transformation rules:
• Source Values:
• Agency: UOM_ERP
• Schema: UOM
• Target Values:
• Agency: UOM_ISO
• Schema: UOM
Fill in the value set for UOM_ERP and UOM_ISO, to set up the transformation rules for Units of Measure.
The following table shows examples of the respective value sets:
UOM_ERP UOM_ISO
PCE C62
KGM KGM
LT LTR
Configuring Global Variables

Because SAP NetWeaver XI acts as the integration platform between SAP R/3 and Ariba SN, there are
many parameters that are global for each of the supported scenarios. This section describes the steps to
configure global variables.
In the value mappings, use the following parameters for Global Variables:
• Source Values:
• Agency: XI_Global
• Schema: GlobalVariable
• Target Values:
• Agency: XI

Fill in the global variable table as appropriate for your system.
SAP NetWeaver XI Example SAP Group Name Description

Global Variable NetWeaver XI Value
PaymentProposal 2006-10-09T12:13:13 BPMConfig Use this timestamp when
StartDateTime the timestamp file for the
PaymentProposal
transaction is not configured
or its date/time parameters
are empty. (Use it for test
and development only and
NOT for production.)
InvoiceStatus 2006-10-09T12:13:14 BPMConfig Use this timestamp when

UpdateStartDate the timestamp file for the
Time InvoiceStatusUpdate
transaction is not configured
or its date/time parameters
are empty. (Use it for test
and development only and
NOT for production)
IsMultiERPModeEnabl true/false BPMConfig Use this parameter to enable
ed (true) or disable (false) the
Multi-ERP support.
ReceiptStartDate 2006-10-09T12:13:15 BPMConfig Use this timestamp when
Time the timestamp file for the
Receipt transaction is not
configured or its date/time
parameters are empty. (Use
it for test and development
only and NOT for
production.)
TimeZone -08:00 or +05:30 BPMConfig Use this parameter label to
configure time zones in
each of the configured SAP
R3 Business Systems.
Configure the value in the
format -HH:mm or +HH:mm.
You must configure the
value for this parameter in
each agency representing
the SAP R3 Business
System.
SAPExternalPayment E BPMConfig Use this parameter to set the

Method external payment method
defined in SAP. Set this
parameter if you are using
the
PaymentRemittanceAdvice
transaction.
SAPAccountingDocType SA BPMConfig Use this parameter to set the

SAP accounting document
type.

SAP NetWeaver XI Example SAP Group Name Description

Global Variable NetWeaver XI Value
SAPUserName <a valid SAP user BPMConfig Use this parameter to set the
name> SAP user name.
OrbianPaymentMethod O BPMConfig User this parameter to set
the Orbian payment
method.
R3LS T90CLNT090 BPMConfig Use this parameter to set the
default SAP R/3 logical
system ID. Set this
parameter if you are using
the
PaymentRemittanceAdvice
transaction in a single ERP
installation, where it is not
mandatory to configure the
System ID in the Ariba SN
Buyer Account. In such
cases, the System ID will be
obtained from this
parameter.
BusinessSystem BS_SAPR3_46C Lookup Use the name of the
Business System in cases
that involve a Single ERP
configuration.
Communication RFC_Lookup_Receiver Lookup This denotes the name of
Channel the communication channel
to be used by the Lookup
API in the mapping.
Configure this parameter
with a value that indicates
the RFC Receiver
Communication Channel
configured for all the SAP
R3 Business Services in
your Configuration
Directory.
SNDPRT LI_SND SAPEDIDC This denotes a constant used
for the IDoc control field
SNDPRT.
SNDPFC LF_SND SAPEDIDC This denotes a constant used

for the IDoc control field
SNDPFC.
Note: In the case of Multi-ERP implementation, additional value mappings need to be defined. For more
information, see the “Linking Multiple SAP instances with Ariba SN” section.

Configuring Integration Scenarios in the Integration Directory

This section describes how to import and configure the integration scenarios in the SAP NetWeaver XI
Integration Directory for the supported transactions. Use an integration scenario from the Integration
Repository as a template for configuring the corresponding transaction in the Integration Directory. The
Integration Scenarios are part of the Design package, which has to be imported into the Integration
Repository first.
Important: Do not activate the Change Lists feature of Integration Builder Configuration Tool until all the
configuration steps are completed.
Configuring the Purchase Order Integration Scenario

You need to configure the integration scenario for the Purchase Order transaction in the Integration
Directory to be able to run the transaction. All the steps of a configuration scenario section must be
completed to fully configure a scenario.
Note: Ensure that the Design package is imported into your system and ready before you run these steps. The
following steps assume that the different Business Systems are defined in the SLD. For more information
about configuring the SLD, see the “Configuring the System Landscape Directory” section.
To configure the Purchase Order:

1 Transfer the Integration Scenario from the Integration Repository to the Integration Directory.
2 Configure the Integration Scenario.
3 Configure the Communication Channels.
4 Activate the new configuration.
The rest of this section describes these steps in detail.
Transferring Integration Scenario

The first step to configure the integration scenario for the Purchase Order transaction is to transfer to the
Integration Directory, the integration scenario loaded into the Integration Repository when the Design
package is imported.
W To transfer the Integration Scenario:

1 From the SAP NetWeaver XI main page, select Integration Builder: Configuration, and then login into the
Integration Builder: Configuration application.
2 In the Integration Builder menu, select Tools > Transfer Integration Scenario From Integration repository.
3 In the first screen of the Transfer Integration Scenario wizard, Select Integration Scenario, click on the
Name field, and then select the following Integration Scenario from the selection list:
• Name: AR_PurchaseOrder_Receive
• Namespace: http://ariba.com/xi/ASN/PurchaseOrder
• Software Component Version: ERP_ASN_4.6C, 1.0 of ariba.com
4 Click on Continue.
5 If required, change the name of the scenario for the Integration Directory
6 Click on Finish.

Once the transfer is completed, the Integration Scenario Configurator window appears.
Configuring the Integration Scenario

Once the Integration Scenario is selected, you must configure it using the following steps:
1 Select Component View.
2 Assign Services.
3 Configure Connections.
4 Generate.
In the Integration Scenario Configurator window, click Select Component View, and then click Apply to select
the unique component view that is selected by default.
After selecting the component view, you must assign services to the application components of the selected
integration scenario.
W To assign services:
1 In the Integration Scenario Configurator, select Assign Services.
2 In the Assign Services window, select the Business System Services for A2A tab to assign services for Ariba
SN.
3 Click on the Insert Line button ('+') to add a service entry in the table.
4 Click on the row under the Service column, and then select the business service name BS_SAPR3_46C, from
the selection list.
Note: For Multi ERP implementation, add the multiple business services defined for your multiple SAP
R/3 systems by repeating the steps 3 and 4.
5 Click the next button (right arrow next to the Role field) to go to the next screen in the wizard.
7 Click on the row under the Service column, and then select the business service name BS_ASN from the
selection list.
8 Click Assign to save the changes.
After assigning services, you must define sender/receiver relations for the individual connections in the
Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations.
W To configure connections:
1 In the Integration Scenario Configurator, select Configure Connections. You must assign Communication
Channels to set up the connections.
Communication Channel cell corresponding to BS_ASN in the Receiver Business System Services for A2A table.
3 Click on the New button, and then select Create Communication Channel with Template to start the Create
Communication Channel wizard.
4 Click on Continue, and in the next page select the following Communication Channel Template:
• Name: CCT_PurchaseOrder_cXML_Receiver

• Namespace: http://ariba.com/xi/ASN/PurchaseOrder
5 Click on Continue, modify the channel name to CC_PurchaseOrder_cXML_Receiver, and then click on Finish.
Tip: If you have already created and configured a Receiver channel for BS_ASN for another transaction,
you can create the communication channel by copy from a channel already configured. For more
information, see the “Creating Communication Channels by Copy (Optional)” section.
Note: The communication channels for SAP R/3 Sender system are not required.
6 Click on Apply to save the changes.
After making all the configuration settings in the wizard, you must generate the objects. Generation creates
the configuration objects if they do not yet exist. If they do already exist, they will be reused and enhanced,
if required. You can also simulate generation for test purposes.
W To generate the objects:

1 In the Integration Scenario Configurator, click on Generate.
2 In the Create Configuration Object window, make the following settings:

• General: Generation (select the radio button for this option)
• Scope of Generation: Select all the check boxes - Receiver Determination, Interface Determination, and
Sender/Receiver Agreement.
3 Select the Create New radio button under Change List for Generated Objects and use the proposed name or
modify it.
4 Click on Start to begin generating objects.
5 After the object generation is complete, close the wizard and click on Apply in the pop up window, to save
the new configuration settings. Close the log that is created without saving. You can also save it, if
required.
Configuring Communication Channels

Configure the communication channel CC_PuchaseOrder_cXML_Receiver under the AR_PurchaseOrder_Receive
Configuration Scenario.
W To configure the communication channel:

1 Expand Business Systems, and then select BS_ASN.
2 Under Communication Channel, select CC_PuchaseOrder_cXML_Receiver.
3 In the Parameters tab, set the parameters in the Authentication section to match your Ariba SN Buyer
account configuration.
Note: If you created the channel by copy from an existing channel, you need to change the request type to
OrderRequest.
If required, edit the other parameters. For more information about the cXML Adapter parameters, see
Appendix A, “cXML Adapter Parameters”.
4 Save the changes.

Activating the Scenario

Using the Change List tab on the main application screen, activate all the Change Lists containing the objects
created and modified during the scenario setup.
This completes the configuration of the Purchase Order transaction in SAP NetWeaver XI.
Configuring the Change Purchase Order Integration Scenario

You must configure the integration scenario for the Change Purchase Order transaction in the Integration
Note: Ensure that the design is imported into your system and ready before you run these steps. The
To configure the Change Purchase Order:

Transferring the Integration Scenario

The first step to configure the integration scenario for the Change Purchase Order transaction is to transfer to
the Integration Directory, the integration scenario loaded into the Integration Repository when the design is
imported.

• Name: AR_ChangePurchaseOrder_Receive
• Namespace: http://ariba.com/xi/ASN/ChangePurchaseOrder
• Software Component Version: ERP_ASN_4.6C, 1.0 of ariba.com.
5 If required, change the name of the scenario for the Integration Directory.
6 Click on Finish.


2 Assign Services.
4 Generate.
In the Integration Scenario Configurator window, click Select Component View, and then click on Apply to
select the unique component view that is selected by default.
SN.
the selection list.
For Multi ERP implementation add the multiple business services defined for your multiple SAP R/3
systems by repeating the steps 3 and 4.
7 Click on the row under the Service column and select the business service name BS_ASN from the selection
list.
After assigning services, you must activate sender/receiver relations for the individual connections in the
• Name: CCT_ChangePurchaseOrder_cXML_Receiver
• Namespace: http://ariba.com/xi/ASN/ChangePurchaseOrder

5 Click on Continue, modify the channel name to CC_ChangePurchaseOrder_cXML_Receiver, and then click on
Finish.


modify it.
4 Click on Start to begin generating objects.
required.

Configure the communication channel CC_ChangePuchaseOrder_cXML_Receiver under the
AR_ChangePurchaseOrder_Receive Configuration Scenario:

1 Expand Business Systems and select BS_ASN.
2 Under Communication Channel, select CC_ChangePuchaseOrder_cXML_Receiver.
ChangeOrderRequest.
4 Save the changes.


This completes the configuration of the Change Purchase Order transaction in SAP NetWeaver XI.
Configuring the Order Confirmation Integration Scenario

You must configure the integration scenario for the Order Confirmation transaction in the Integration
To configure the Order Confirmation:


The first step to configure the integration scenario for the Order Confirmation transaction is to transfer to the
Integration Directory, the integration scenario loaded into the Integration Repository when the design is
imported.

• Name: AR_OrderConfirmation_Send
• Namespace: http://ariba.com/xi/ASN/OrderConfirmation
6 Click on Finish.


2 Assign Services.
4 Generate.
In the Integration Scenario Configurator window, click Select Component View, and then click Apply to select
the unique component view that is selected by default.
SN.
4 Click on the row under the Service column and select the business service name BS_SAPR3_46C, from the
selection list.
6 Click on the Insert Line button ('+') to add a service entry in the table
list.
8 Click on Assign to save the changes.
Communication Channel cell corresponding to BS_ASN in the Sender Business System Services for A2A table.
• Name: CCT_OrderConfirmation_cXML_Sender
• Namespace: http://ariba.com/xi/ASN/OrderConfirmation

5 Click on Continue, modify the channel name to CC_OrderConfirmation_cXML_Sender, and then click on
Finish.
Communication Channel cell corresponding to BS_SAPR3_46C in the Receiver Business System Services for A2A
table.
The IDoc receiver Communication Channel needs to be created once for each Business System
corresponding to your SAP R3. For more information about how to create the IDoc receiver
Communication Channel, see the “Creating Communication Channels for R/3” section.
If a Communication Channel already exists you need to use it.
7 Select the communication channel CC_IDoc_Receiver corresponding to the SAP R/3 Business System
from the selection list.
For Multi ERP implementation, repeat the steps 6, and 7 for all the entries of the Business Systems
corresponding to your SAP R3 instances.


modify it.
4 Click Start to begin generating objects.
required.

Configure the communication channel CC_OrderConfirmation_cXML_Sender under the
AR_OrderConfirmation_Send Configuration Scenario:


2 Under Communication Channel, select CC_OrderConfirmation_cXML_Sender.
ConfirmationRequest.
If required, edit the other parameters. For more information about the cXML Adapter parameters see
4 Save the changes.
Configuring Receiver Determination

Configure the receiver determination settings manually, for the receiver
MIOut_Async_OrderConfirmation_cXML under the AR_OrderConfirmation_Send integration scenario. Retain the
default settings for the other receivers.
Note: This configuration is required only for Multi-ERP implementations.
W To configure the Receiver Determination settings:

1 Expand Receiver Determination, and then click |BS_ASN | MIOut_Async_OrderConfirmation_cXML.
2 In the Configured Receivers section of the Edit Receiver Determination window, click on the Add button to
add a new line.
3 Click on the icon next to the Condition field, to start the Condition Editor.
4 In the Condition Editor window, specify the left operand of the condition as follows:
1 Click on the icon next to the Left Operand field to open the Expression Editor.
2 Select the XPath option, and then select the following xpath from the document tree:
/cXML/Header/To/Credential/@domain.
This path should be displayed in the XPath Expression field.

3 Click OK to return to the Expression Editor.
4 Select the “=” operator in the Operator column.
5 Select the Right Operand field and enter “SystemID”.
5 Add another condition by clicking on the Insert Expression option. (The Boolean operator between the two
conditions should be “AND”.)
/cXML/Header/To/Credential/Identity.
Note: You cannot select a node having child nodes or attributes, directly from the tree. You must first
select the child node or attribute and edit the xpath expression in the XPath Expression field to remove
the child element.

3 Click on OK to return to the Expression Editor.
5 Select the Right Operand field and specify the Logical System Name corresponding to the Business
System for which you are doing the configuration. E.g. T90CLNT090.
6 Click on OK to close the Condition Editor.
7 Click on the icon next to the Service field to start the Service Editor and select the Business Service
corresponding to the Logical System Name you specified in the Condition.
Note: For Multi ERP implementation, repeat the steps 2 to 7 for all your SAP R3 instances.
8 Save the Receiver Determination settings.

This completes the configuration of the Order Confirmation transaction in SAP NetWeaver XI.
Configuring the Advance Ship Notice Integration Scenario

You must configure the integration scenario for the Advance Ship Notice transaction in the Integration
about configuring the SLD see the “Configuring the System Landscape Directory” section.
To configure the Advance Ship Notice:


The first step to configure the integration scenario for the Advance Ship Notice transaction is to transfer to
imported.


• Name: AR_AdvanceShipNotice_Send
• Namespace: http://ariba.com/xi/ASN/AdvanceShipNotice
6 Click on Finish.

Once the Integration Scenario is selected, you must configure it using the following sequence of steps:
2 Assign Services.
4 Generate.
W To assign services to the application components of the selected integration scenario:

SN.
list.
7 Click on the row under the Service column and select the business service name BS_SAPR3_46C, from the
selection list.

• Name: CCT_AdvanceShipNotice_cXML_Sender
• Namespace: http://ariba.com/xi/ASN/AdvanceShipNotice
5 Click on Continue, modify the channel name to CC_AdvanceShipNotice_cXML_Sender, and then click on
Finish in the next page.
table.
Communication Channel, see the “Creating Communication Channels for R/3” section.If a
Communication Channel already exists you need to use it.
For Multi ERP implementation, repeat the steps 6, and 7 for all the entries of the Business Systems


modify it.

required.

Configure the communication channel CC_AdvanceShipNotice_cXML_Sender under the
AR_AdvanceShipNotice_Send Configuration Scenario:
W To configure the CC_AdvanceShipNotice_cXML_Sender communication channel:

2 Under Communication Channel, select CC_AdvanceShipNotice_cXML_Sender.
ShipmentNoticeRequest.
If required, adapt the other parameters. For more information about the cXML Adapter parameters, see
4 Save the changes.

MIOut_Async_AdvanceShipNotice_cXML under the AR_AdvanceShipNotice_Send integration scenario. Retain the
default settings for the other receivers.

1 Expand Receiver Determination, and then click |BS_ASN | MIOut_Async_AdvanceShipNotice_cXML.
add a new line.


the child element.


The Advance Ship Notice transaction is now ready for execution.
Configuring the Invoice Integration Scenario

You must configure the integration scenario for the Invoice transaction in the Integration Directory to be
able to run the transaction. All the steps of a configuration scenario section must be completed to fully
configure a scenario.
To configure the Invoice:




The first step to configure the integration scenario for the Invoice transaction is to transfer to the Integration
Directory, the integration scenario loaded into the Integration Repository when the design is imported.

1 From the SAP NetWeaver XI main page, select the Integration Builder: Configuration, and then login into
• Name: AR_Invoice_ZInvoic02
• Namespace: http://ariba.com/xi/ASN/ZInvoice
6 Click on Finish.

2 Assign Services.
4 Generate.
SN.
list.

the selection list.
• Name: CCT_ZInvoice_cXML_Sender
• Namespace: http://ariba.com/xi/ASN/ZInvoice
5 Click on Continue, modify the channel name to CC_ZInvoice_cXML_Sender, and then click on Finish.
table.
Communication Channel, see the “Creating Communication Channels for R/3” section.If a
If a Communication Channel already exists you need to use it.
For Multi ERP implementation, repeat the steps 7 and 8 for all the entries of the Business Systems



modify it.
required.

Configure the communication channel CC_Invoice_cXML_Sender under the AR_Invoice_Send Configuration
Scenario:

2 Under Communication Channel, select CC_ZInvoice_cXML_Sender.
InvoiceDetailRequest.
If required, adapt the other parameters. For more information about the cXML Adapter parameters, see
4 Save the changes.

MIOut_Async_Invoice_ZInvoic02_cXML under the AR_ZInvoice_Send integration scenario. Retain the default
settings for the other receivers.

1 Expand Receiver Determination, and then click |BS_ASN | MIOut_Async_Invoice_ZInvoic02_cXML.
add a new line.


the child element.

The Invoice transaction is now ready for execution.

Configuring the Invoice Status Update Integration Scenario

You must configure the integration scenario for the Invoice Status Update transaction in the Integration
To configure the Invoice Status Update:


The first step to configure the integration scenario for the Invoice Status Update transaction is to transfer to
imported.

1 From the SAP NetWeaver XI main page, select Integration Builder: Configuration, and then login into
• Name: AR_InvoiceStatusUpdate_Receive
• Namespace: http://ariba.com/xi/ASN/InvoiceStatusUpdate
6 Click on Finish.

2 Assign Services.

4 Generate.
In the Integration Scenario Configurator window, click on Select Component View, and then click on Apply to
2 In the Assign Services window, select the Business System Services for A2A tab to assign services for SAP
Exchange Infrastructure File System.
4 Click on the row under the Service column, and then select the business service name BS_File, from the
selection list.
6 In the Assign Services window, select the Integration Process Services for A2A tab to assign the Integration
Process for the Invoice Status Update transaction.
7 Select the IP_InvoiceStatusUpdate service from the selection list.
If there is no Integration Process service in the selection list, you must create one from the template, using
the following steps:
1 Click on the new service button (the blank document icon next to the Service field) to start the Install
Integration Process wizard.
2 In the wizard window that opens, click on the Continue button.
3 In the Name field on the next page, specify IP_InvoiceStatusUpdate as the name of the integration
process to be created.
4 Click on Finish.
the selection list.
selection list.
14 Click on Assign to save the changes.

Communication Channel cell corresponding to BS_File in the Sender Business System Services for A2A table.
• Name: CCT_InvoiceStatusUpdate_File_Sender
5 Click on Continue, modify the channel name to CC_InvoiceStatusUpdate_File_Sender, and then click on
Finish.
Note: The communication channel for the Receiver Integration Process Service is not required.
6 Click the next button (right arrow next to the Role field) in the Configure Connection wizard to go to the
next screen in the wizard.
table.
The RFC Receiver Communication Channel needs to be created once for each Business System
corresponding to your SAP R3. For more information about how to create the RFC Receiver
If a Communication Channel already exists you must use it.
8 Select the communication channel CC_RFC_Receiver corresponding to the SAP R/3 Business System from
the selection list.
For Multi ERP implementation, repeat the steps 7 and 8 for all the entries of the Business Systems
Note: The communication channels for the Sender Integration Process Service is not required.
9 Click on the next button (right arrow next to the Role field) in the Configure Connection wizard to go to
the next screen in the wizard.
• Name: CCT_InvoiceStatusUpdate_cXML_Receiver


13 Click on Continue, modify the channel name to CC_InvoiceStatusUpdate_cXML_Receiver, and then click on
Finish.
Note: The communication channel for the Sender Integration Process Service is not required.
14 Click on the next button (right arrow next to the Role field) in the Configure Connection wizard to go to
the next screen in the wizard.
Communication Channel cell corresponding to BS_File in the Receiver Business System Services for A2A table.
• Name: CCT_InvoiceStatusUpdate_File_Receiver
18 Click on Continue, modify the channel name to CC_InvoiceStatusUpdate_File_Receiver and then click on
Finish.


modify it.
required.

Configure the communication channels CC_InvoiceStatusUpdate_cXML_Receiver,
CC_InvoiceStatusUpdate_File_Receiver, and CC_InvoiceStatusUpdate_File_Sender under the
AR_InvoiceStatusUpdate_Receive Configuration Scenario:

W To configure the CC_InvoiceStatusUpdate_cXML_Receiver communication channel:

2 Under Communication Channel, select CC_InvoiceStatusUpdate_cXML_Receiver.
InvoiceUpdateRequest.
4 Save the changes.
W To configure the CC_InvoiceStatusUpdate_File_Receiver communication channel:

1 Expand Business Systems and select BS_File.
2 Under Communication Channel, select CC_InvoiceStatusUpdate_File_Receiver.
3 In the Parameters tab, set the parameters in the File Access Parameters section as follows:
• Target Directory: Specify the directory in which the received file should be stored, here
• File Name Scheme: LastUpdateDateTime_InvoiceStatusUpdate_%sys_id%.xml
This XML file is available with the name LastUpdateDateTime_InvoiceStatusUpdate_INST.xml in the
ASCAdapterNetweaver.FileStruct.zip that is delivered along with the Design package. For more
information about modifying this file for use, see “To modify the
LastUpdateDateTime_InvoiceStatusUpdate_INST.xml file:”
Set the Processing Parameters as follows:

• File Construction Mode: Create
• Overwrite existing file: This option is checked
• Write Mode: Directly
• File Type: Text
Variable substitution: Enable: This option is checked

• Variable name: sys_id
• Reference: payload:MT_LastUpdate_File,1,SystemID,1
Here you need to specify only the Target Directory. You can retain the default values for all other
parameters after verifying that they match the values shown here. If required, edit the other parameters to
meet your requirements.
4 Save the changes.
Note: The templates delivered with this version of the adapter correspond to version 6.40 of the system
adapters of SAP NetWeaver XI (SAP NW 2004 / XI 3.0). If your system configuration is higher and the
version 6.40 adapters are not available, you will get an error when you try to open the Communication
Channel page. In this case, you must manually select the correct Adapter Type in the Communication
Channel. The Adapter name (e.g. File) does not change but the version differs.

W To modify the LastUpdateDateTime_InvoiceStatusUpdate_INST.xml file:

1 Extract the contents of the ASCAdapterNetweaver.FileStruct.zip file to a local folder.
2 Browse to the <root>\ASCAdapterNetweaver\InvoiceStatusUpdate folder and open the

LastUpdateDateTime_InvoiceStatusUpdate_INST.xml file for edit.
3 Replace the placeholder text “INST” with the System ID as the attribute for the <System ID> element.
4 Specify the date of last update in the format “YYYY-MM-DD”, as the attribute for the <Date> element.
5 Specify the date of last update in the format “HH:MM:SS”, as the attribute for the <Time> element.
6 Rename the file to LastUpdateDateTime_InvoiceStatusUpdate_INST.xml by replacing the placeholder text

“INST” with the System ID that is specified as the attribute in the file.
Note: For Muti-ERP implementation, each SAP R/3 instance involved in the integration must have a
separate time stamp file. Copy the file LastUpdateDateTime_InvoiceStatusUpdate_INST.xml and follow the
steps 3 to 6 for each SAP R/3 instance.
W To configure the CC_InvoiceStatusUpdate_File_Sender communication channel:

2 Under Communication Channel, select CC_InvoiceStatusUpdate_File_Sender.
• File Name Scheme: LastUpdateDateTime_InvoiceStatusUpdate_*.xml

• Quality of Service: Exactly Once
• Poll interval(secs): 1800
• Processing Mode: Set to Read-Only
parameters after verifying that they match the values shown here. If required, adapt the other parameters
to meet your requirements.
4 Save the changes.
The communication channel, CC_RFC_Receiver for SAP R3 systems, is common to all the scenarios. For
more information about how to configure the CC_RFC_Receiver see the “Creating Communication
Channels for R/3” section.

MIAbs_Sync_Z_ARIBA_INVOICE_STATUS_UPDATE under the AR_InvoiceStatusUpdate_Receive integration
scenario. Retain the default settings for the other receivers.


1 Expand Receiver Determination, and then click
|IP_InvoiceStatusUpdate|MIAbs_Sync_Z_ARIBA_INVOICE_STATUS_UPDATE.
add a new line.
3 Click on the icon next to the Condition field to start the Condition Editor.
2 Select the XPath option and then select the following xpath from the document tree:
/MT_LastUpdate_File/SystemID.

Note: You can verify the logical system name of a SAP R/3 Business System by opening the business
system under <Scenario> > Service Without Party > Business System. Then, from the Business System
panel, open the Service menu and select Adapter-Specific Identifiers.

This completes the configuration of the Invoice Status Update transaction in SAP NetWeaver XI.

Configuring the Payment Proposal Integration Scenario

You must configure the integration scenario for the Payment Proposal transaction in the Integration
Directory to be able to run the transaction. All the steps of a configuration scenario section have to be
To configure the Payment Proposal:


The first step to configure the integration scenario for the Payment Proposal transaction is to transfer to the
imported.

• Name: AR_PaymentProposal_Receive
• Namespace: http://ariba.com/xi/ASN/PaymentProposal
6 Click on Finish.

2 Assign Services.

4 Generate.
2 In the Assign Services window, select the Business System Services for A2A tab to assign services for the
SAP Exchange Infrastructure File System.
selection list.
Process for the Payment Proposal transaction.
7 Select the IP_PaymentProposal service from the selection list.
3 In the Name field on the next page, specify IP_PaymentProposal as the name of the integration process
to be created.
4 Click on Finish.
the selection list.
Note: For Multi ERP implementation add the multiple business services defined for your multiple SAP
selection list.

• Name: CCT_PaymentProposal_File_Sender
5 Click on Continue, modify the channel name to CC_PaymentProposal_File_Sender, and then click on Finish.
6 Click the next button (right arrow next to the Role field) in the Configure Connection wizard to go to the
next screen in the wizard.
table.
Note: The RFC Receiver Communication Channel needs to be created once for each Business System

the selection list.
Note: For Multi ERP implementation, repeat the steps 7 and 8 for all the entries of the Business Systems
corresponding to your SAP R/3 instances.
The communication channel for the Sender Integration Process Service is not required.
9 Click the next button (right arrow next to Role field, at the top right) in the Configure Connection wizard
to go to the next screen in the wizard.
11 Click on the New button and select Create Communication Channel with Template to start the Create
Tip: In case you have already created and configured a Receiver channel for BS_ASN for another
transaction, you can create the communication channel by copy from a channel already configured. For
more information, see the “Creating Communication Channels by Copy (Optional)” section.
• Name: CCT_PaymentProposal_cXML_Receiver


13 Click on Continue, modify the channel name to CC_PaymentProposal_cXML_Receiver, and then click on
Finish.
• Name: CCT_PaymentProposal_File_Receiver
18 Click on Continue, modify the channel name to CC_PaymentProposal_File_Receiver, and then click on
Finish.


modify it.
required.

Configure the communication channels CC_PaymentProposal_cXML_Receiver,
CC_PaymentProposal_File_Receiver,and CC_PaymentProposal_File_Sender under the
AR_PaymentProposal_Receive Configuration Scenario:

W To configure the CC_PaymentProposal_cXML_Receiver communication channel:

2 Under Communication Channel, select CC_PaymentProposal_cXML_Receiver.
PaymentProposal.
4 Save the changes.
W To configure the CC_PaymentProposal_File_Receiver communication channel:

2 Under Communication Channel, select CC_PaymentProposal_File_Receiver.
3 In the Parameters tab, set the parameters in the section File Access Parameters as follows:
• File Name Scheme: LastUpdateDateTime_PaymentProposal_%sys_id%.xml
This XML file is available with the name LastUpdateDateTime_PaymentProposal_INST.xml in the
information on modifying this file for use, see “To modify the
LastUpdateDateTime_PaymentProposal_INST.xml file:”

• Overwrite existing file: This option is checked
• File Type: Text.

• Reference: payload:MT_LastUpdate_File,1,SystemID,1
4 Save the changes.

W To modify the LastUpdateDateTime_PaymentProposal_INST.xml file:

2 Browse to the <root>\ASCAdapterNetweaver\PaymentProposal folder and open the

LastUpdateDateTime_PaymentProposal_INST.xml file for edit.
4 Specify the date of last update in the format “YYYY-MM-DD”, as the attribute for the <Date> element.
5 Specify the date of last update in the format “HH:MM:SS”, as the attribute for the <Time> element.
6 Rename the file to LastUpdateDateTime_PaymentProposal_INST.xml by replacing the placeholder text

“INST” with the System ID that is specified as the attribute in the file.
separate time stamp file. Copy the file LastUpdateDateTime_PaymentProposal_INST.xml and follow the
steps 3 to 6 for each SAP R/3 instance.
W To configure the CC_PaymentProposal_File_Sender communication channel:

2 Under Communication Channel, select CC_PaymentProposal_File_Sender.
• File Name Scheme: LastUpdateDateTime_PaymentProposal_*.xml.

• Poll interval(secs): 1800.
• Processing Mode: Set to Read-Only.
Here, you need to specify only the Target Directory. You can retain the default values for all other
4 Save the changes.
The communication channel CC_IDoc_Receiver for R3 systems is common to all the scenarios. For more
information on how to configure the CC_IDoc_Receiver see the , “Creating Communication Channels for
R/3” section.

MIAbs_Sync_Z_ARIBA_PAYMENT_PROPOSAL under the AR_PaymentProposal_Receive integration scenario. Retain
the default settings for the other receivers.


1 Expand Receiver Determination, and then click
|IP_PaymentProposal|MIAbs_Sync_Z_ARIBA_PAYMENT_PROPOSAL.
2 In the Configured Receivers section of the Edit Receiver Determination screen, click on the Add button to
add a new line.
MT_LastUpdate_File/SystemID.

panel, open the Service menu and select Adapter-Speceific Identifiers.
6 Click on the icon next to the Service field to start the Service Editor, and then select the Business Service

This completes the configuration of the Payment Proposal transaction in SAP NetWeaver XI.

Configuring the Receipt Integration Scenario

You must configure the integration scenario for the Receipt transaction in the Integration Directory to be
able to run the transaction. All the steps of a configuration scenario section have to be completed to fully
To configure the Receipt:


The first step to configure the integration scenario for the Receipt transaction is to transfer to the Integration
Directory, the integration scenario loaded into the Integration Repository when the design is imported.

• Name: AR_Receipt_Receive
• Namespace: http://ariba.com/xi/ASN/Receipt
6 Click on Finish.

Once the Integration Scenario is selected, you must configure it using the following sequence of steps:
2 Assign Services.
4 Generate.

2 In the Assign Services window, select the Business System Services for A2A tab to assign services for SAP
Exchange Infrastructure File System.
selection list.
5 Click the next button (right arrow next to Role field, at the top right) to go to the next screen in the wizard.
Process for the Receipt transaction.
7 Select as service IP_Receipt from the selection list.
3 In the Name field on the next page, specify IP_Receipt as the name of the integration process to be
created.
4 Click on Finish.
the selection list.
Note: For Multi ERP implementation, add the multiple business services defined for your multiple SAP
selection list.

• Name: CCT_Receipt_File_Sender
5 Click on Continue, modify the channel name to CC_Receipt_File_Sender, and then click on Finish.
table.
Note: The RFC Receiver Communication Channel needs to be created once for each Business System

the selection list.
corresponding to your SAP R/3 instances.
The communication channels for the Sender Integration Process Service is not required.
9 Repeat step 6 to 8 to associate the RFC Communication Channels between the following actions:
• IP_ReadTableVendors - R3_ReadTableVendors
• IP_ReadTableMKPF - R3_ReadTableMKPF
• IP_BAPIGetDetail - R3_BAPIGetDetail.
Tip: If you have already created and configured a Receiver channel for BS_ASN for another transaction, you
can create the communication channel by copy from the already configured channel. For more

• Name: CCT_Receipt_cXML_Receiver
14 Click on Continue, modify the channel name to CC_Receipt_cXML_Receiver, and then click on Finish.
• Name: CCT_Receipt_File_Receiver
19 Click on Continue, modify the channel name to CC_Receipt_File_Receiver, and then click on Finish.


3 Select the Create New radio button under Change List for Generated Objects, and then use the proposed name
or modify it.
required.

Configure the communication channels CC_Receipt_cXML_Receiver, CC_Receipt_File_Receiver, and
CC_Receipt_File_Sender under the AR_Receipt_Receive Configuration Scenario:

W To configure the CC_Receipt_cXML_Receiver communication channel:

2 Under Communication Channel, select CC_Receipt_cXML_Receiver.
ReceiptRequest.
4 Save the changes.
W To configure the CC_Receipt_File_Receiver communication channel:

2 Under Communication Channel, select CC_Receipt_File_Receiver.
• Target Directory: Specify the directory in which the received file should be stored, here. Provide a path
to the directory, as in the following example: D:/AribaDataDir/ASCAdapterNetweaver/Receipt
• File Name Scheme: LastUpdateDateTime_Receipt_%sys_id%.xml
This XML file is available with the name LastUpdateDateTime_Receipt_INST.xml in the
information on modifying this file for use, see “To modify the
LastUpdateDateTime_Receipt_INST.xml file:” on page 62

• File Type: Text

• Reference: payload:MT_LastUpdate_File,1,SystemID,1.
4 Save the changes.

W To modify the LastUpdateDateTime_Receipt_INST.xml file:

2 Browse to the <root>\ASCAdapterNetweaver\Receipt folder, and then open the

LastUpdateDateTime_Receipt_INST.xml file for edit.
4 Specify the date of last update, in the format “YYYY-MM-DD”, as the attribute for the <Date> element.
5 Specify the date of last update, in the format “HH:MM:SS”, as the attribute for the <Time> element.
6 Rename the file to LastUpdateDateTime_Receipt_INST.xml by replacing the placeholder text “INST”, with
the System ID that is specified as the attribute in the file.
separate time stamp file. Copy the file LastUpdateDateTime_Receipt_INST.xml and follow the steps 3 to 6
for each SAP R/3 instance.
W To configure the CC_Receipt_File_Sender communication channel:

2 Under Communication Channel, select CC_Receipt_File_Sender.
• Source Directory: Specify the directory in which the receipt file should be stored, here. Provide a path to
the directory, as in the following example: D:/AribaDataDir/ASCAdapterNetweaver/Receipt
• File Name Scheme: LastUpdateDateTime_Receipt_*.xml

• Poll interval(secs): 1800
• Processing Mode: Set to Read-Only.
parameters after verifying that they match the values shown here. If required, edit the other parameters to
meet your requirements.
4 Save the changes.
The communication channel CC_IDoc_Receiver for R3 systems is common to all the scenarios. For more
information about how to configure the CC_IDoc_Receiver, see the “Creating Communication Channels for
R/3” section.

Configure the receiver determination settings manually, under the AR_Receipt_Receive integration scenario.
Retain the default settings for the other receivers.


1 Expand Receiver Determination, and then click on |IP_Receipt|MIAbs_Sync_BAPI_GOODSMVT_GETDETAIL.
2 In the Configured Receivers section of the Edit Receiver Determination screen, click on the Add button to
add a new line.
/BAPI_GOODSMVT_GETDETAIL/SYSTEM_ID.


panel, open the Service menu and select Adapter-Speceific Identifiers.
5 Click OK to close the Condition Editor.
8 Click on | IP_Receipt | MIAbs_Sync_LastUpdate_File_2_MSS_GET_SY_DATE_TIME under Receiver

Determination.
9 Then repeat steps 2 to 7 for this receiver. In step 4, select the following xpath expression from the
document tree: /MT_LastUpdate_File/SystemID.
10 Click on | IP_Receipt | MIAbs_Sync_LastUpdate_File_2_Vendors_List under Receiver Determination.
document tree: /MT_LastUpdate_File/SystemID.
12 Click on | IP_Receipt | MIAbs_Sync_RFC_READ_TABLE under Receiver Determination.
document tree: /RFC_READ_TABLE/SYSTEM_ID.

This completes the configuration of the Receipt transaction in SAP NetWeaver XI.

Configuring the PayMeNow Integration Scenario

You must configure the integration scenario for the PayMeNow transaction in the Integration Directory to
be able to run the transaction. All the steps of a configuration scenario section must be completed to fully
To configure the PayMeNow:


The first step to configure the integration scenario for the PayMeNow transaction is to transfer to the
imported.

• Name: AR_PayMeNow_Send
• Namespace: http://ariba.com/xi/ASN/PayMeNow
6 Click Finish.

2 Assign Services.

4 Generate.
In the Integration Scenario Configurator window, click on Select Component View and then click on Apply,
to select the unique component view that is selected by default.
SN.
selection list.
the selection list.
1 In the Integration Scenario Configurator, select Configure Connections. You need to assign Communication
Tip: If you have already created and configured a Receiver channel for BS_ASN for another transaction, you
can create the communication channel by copy from a channel already configured. For more information
about creating a communication channel by copy, see the “Creating Communication Channels by Copy
(Optional)” section.
• Name: CCT_PayMeNow_cXML_Sender
• Namespace: http://ariba.com/xi/ASN/PayMeNow
5 Click on Continue, modify the channel name to CC_PayMeNow_cXML_Sender, and then click on Finish.

table.
Note: The IDoc receiver Communication Channel needs to be created once for each Business System
Communication Channel, see the “Creating Communication Channels for R/3” section. If a
The communication channels for SAP R/3 Sender system are not required.


modify it.
required.

Configure the communication channel CC_PayMeNow_cXML_Sender under the AR_PayMeNow_Send Configuration
Scenario:

2 Under Communication Channel, select CC_PayMeNow_cXML_Sender.
PayMeNowRequest.

4 Save the changes.

Configure the receiver determination settings manually, for the receiver MIOut_Async_PayMeNow_cXML under
the AR_PayMeNow_Send integration scenario. Retain the default settings for the other receivers.

1 Expand Receiver Determination, and then click |BS_ASN | MIOut_Async_PayMeNow_cXML.
add a new line.
/cXML/Header/From/Credential/@domain.

/cXML/Header/From/Credential/Identity.
the child element.


This completes the configuration of the Pay Me Now transaction in SAP NetWeaver XI.
Configuring the Payment Remittance Integration Scenario

You must configure the integration scenario for the Payment Remittance transaction in the Integration
To configure the Payment Remittance:


The first step to configure the integration scenario for the Payment Remittance transaction is to transfer to
imported.

• Name: AR_PaymentRemittance_Receive
• Namespace: http://ariba.com/xi/ASN/PaymentRemittance

6 Click on Finish.

2 Assign Services.
4 Generate.
SN.
4 Click on the row under the Service column, and then select the business service name BS_SAPR3_46C from
the selection list.
selection list.
Communication Channel cell corresponding to BS_ASN in the Receiver Business System Services for A2A
table.

Tip: In case you have already created and configured a Receiver channel for BS_ASN for another
transaction, you can create the communication channel by copy from a channel already configured. For
more information about creating communication channels by copying, see the “Creating Communication
Channels by Copy (Optional)” section.
• Name: CCT_PaymentRemittance_cXML_Receiver
• Namespace: http://ariba.com/xi/ASN/PaymentRemittance
5 Click on Continue, modify the channel name to CC_PaymentRemittance_cXML_Receiver, and then click on
Finish.


modify it.
required.

Configure the communication channel CC_PaymentRemittance_cXML_Receiver under the
AR_PaymentRemittance_Receive Configuration Scenario:

2 Under Communication Channel, select CC_PaymentRemittance_cXML_Receiver.
PaymentRemittanceRequest.

4 Save the changes.

This completes the configuration of the Payment Remittance transaction in SAP NetWeaver XI.
Configuring the Payment Remittance Advice Integration Scenario

You must configure the integration scenario for the Payment Remittance Advice transaction in the
Integration Directory to be able to run the transaction. All the steps of a configuration scenario section must
be completed to fully configure a scenario.
To configure the Payment Remittance Advice:


The first step to configure the integration scenario for the Payment Remittance Advice transaction is to
transfer to the Integration Directory, the integration scenario loaded into the Integration Repository when the
design is imported.

• Name: AR_PaymentRemittanceAdvice_Send
• Namespace: http://ariba.com/xi/ASN/PaymentRemittanceAdvice

6 Click on Finish.

2 Assign Services.
4 Generate.
SN.
selection list.
7 Click on the row under the Service column, and then select the business service name BS_SAPR3_46C from
the selection list.
Communication Channel cell corresponding to BS_ASN in the Sender Business System Services for A2A
table.

Tip: In case you have already created and configured a Sender channel for BS_ASN for another
transaction, you can create the communication channel by copying from this channel. For more
information about creating communication channels by copying, see the “Creating Communication
Channels by Copy (Optional)” section.
• Name: CCT_PaymentRemittanceAdvice_cXML_Sender
• Namespace: http://ariba.com/xi/ASN/PaymentRemittanceAdvice
5 Click on Continue, modify the channel name to CC_PaymentRemittanceAdvice_cXML_Sender, and then click
on Finish.


modify it.
required.

Configure the communication channel CC_PaymentRemittanceAdvice_cXML_Sender under the
AR_PaymentRemittanceAdvice_Send Configuration Scenario:

2 Under Communication Channel, select CC_PaymentRemittanceAdvice_cXML_Sender.
PaymentRemittanceRequest.

4 Save the changes.

MIOut_Async_PaymentRemittanceAdvice_cXML under the AR_PaymentRemittanceAdvice_Send integration
scenario. Retain the default settings for the other receivers.

1 Expand Receiver Determination, and then click |BS_ASN | MIOut_Async_PaymentRemittanceAdvice_cXML.
add a new line.
/cXML/Header/From/Credential/@domain.

/cXML/Header/From/Credential/Identity.
the child element.


This completes the configuration of the Payment Remittance Advice transaction in SAP NetWeaver XI.
Linking Multiple SAP instances with Ariba SN

If your organization has more than one instance of SAP, you can link them to a single Ariba SN account.
This feature allows all the documents from particular vendors to be routed to a single Ariba SN account and
in the reverse direction, the documents from Ariba SN will be routed to a particular SAP R/3 instance.
Buying organization or service provider accounts must be enabled for Multi-ERP implementation byAriba
SN Support. The required configuration sections will not be available for accounts that have not been
enabled.
This section describes the following topics:

• The mechanisms involved in the documents routing
• The configuration to setup integration with Ariba SN of multiple SAP R/3 instances.
Document Routing Mechanism

In the multi-ERP implementation scenario, each of the SAP R/3 systems involved in the integration is
identified by a unique identifier. This identifier, called the SystemID, corresponds to the logical system ID
of the concerned SAP R/3 instance.
Each document that passes through the integration will be transformed as follows, to include or to retrieve
this unique identifier from the cXML header:
<cXML payloadID="1178712117116-1738314603425509122@10.10.13.243"
timestamp="2007-05-09T05:01:57-07:00">
<Header>
<From>
<Credential domain="NetworkID">
<Identity>AN50000000365</Identity>
</Credential>
<Credential domain="PrivateID">
<Identity>0000009999</Identity>
</Credential>
</From>
<To>
<Credential domain="NetworkID">
<Identity>AN51000000349</Identity>
</Credential>
<Credential domain="SystemID">
<Identity>T90CLNT090</Identity>
</Credential>
</To>

Depending on the direction, the SystemID identifier is located in different locations:

• For outbound documents, it is located in the From element
• For inbound documents, it is located in the To element.
The following figure shows the SystemID identifier location in outbound documents at the top and in
inbound documents at the bottom.
Figure 2 SystemID identifier location in the message exchanges
<From>
<Credential domain=”SystemID”>
</Credential> SAP R/3
...
</From>
IDOC Log System Name:
T90CLNT090
SAP PI
Ariba SN SAP R/3
ASC Adapter Log System Name:
T47CLNT800
<To>
<Credential domain=”SystemID”>
</Credential> SAP R/3
...
</To>
IDOC Log System Name:
T90CLNT090
SAP PI
Ariba SN SAP R/3
ASC Adapter Log System Name:
T47CLNT800
In the case of single-ERP implementation, the SystemID identifier is not inserted in the outgoing documents
or expected in the incoming documents.
In the case of multi-ERP implementation, if the SystemID is not found in an inbound document, it is not
processed and fails in the SAP NetWeaver XI integration with a System Error.
Multi-ERP Configuration
The multi-ERP implementation requires configuration on all three sides: SAP R/3, SAP NetWeaver XI and
Ariba SN.
Configuring the System Landscape Directory

You must configure all your SAP R/3 instances in the SLD as Technical and Business Systems.
For more information, see the “Defining Technical and Business Landscape for SAP R/3” section.

Configuring SAP R/3 Connectivity

The connectivity between all the SAP R/3 instances and the SAP NetWeaver XI server has to be setup.
For more information, see the “Configuring R/3 Connectivity” section.
Configuring Integration Scenarios

The integration scenarios in the Integration Directory need to be parameterized in order to have the
information on the systems and enable message routing.
Configuring ValueMappings
You must configure the following entries in the ValueMappings to enable the multi-ERP support for the
integration:
• Enable the multi-ERP mode:
Source:
• Agency: XI_Global
• Value: IsMultiERPModeEnabled
Target:
• Agency: XI
• Value: true.
• Configure the mappings between Business Systems and Logical System Names:
Source:
• Agency: LogSys_Source
• Schema: Lookup
• Value: Logical System Name
Target:
• Agency: BusSys_Target
• Schema: Lookup
• Value: Business System Name.
Note: The Group Name is not required
The following table shows an example of values.
LogSys_Source BusSys_Target
90CLNT090 BS_SAP_46C
T47CLNT800 BS_SAP_47
Setting up Receiver Determination
Each inbound scenario, as well as the scheduled scenarios, has to be configured for messages and calls
routing.

Refer to the specific section for each transaction to setup the receiver determination rules:
For more information on setting up the receiver determination for Order Confirmation, see “To configure
the Receiver Determination settings:” on page 33.
For more information on setting up the receiver determination for Advance Ship Notice, see “To configure
For more information on setting up the receiver determination for Invoice, see“To configure the Receiver
Determination settings:” on page 41.
For more information on setting up the receiver determination for Invoice Status Update, see “To configure
For more information on setting up the receiver determination for Payment Proposal, see “To configure the
Receiver Determination settings:” on page 56.
For more information on setting up the receiver determination for Receipt, see “To configure the Receiver
Determination settings:” on page 63.
For more information on setting up the receiver determination for Pay Me Now, see “To configure the
Receiver Determination settings:” on page 67.
Modifying Scheduled Transaction and Timestamp files
For the scheduled transactions where a timestamp file is used, a separate file must exist for each instance of
the SAP R/3 involved in the integration.
Follow the procedures described in the following sections:
For Invoice Status Update, see “To modify the LastUpdateDateTime_InvoiceStatusUpdate_INST.xml file:”
on page 48.
For Payment Proposal, see “To modify the LastUpdateDateTime_PaymentProposal_INST.xml file:” on

page 55.
For Receipt, see “To modify the LastUpdateDateTime_Receipt_INST.xml file:” on page 62.
Configuring Ariba SN
You must configure Ariba SN with the information about all the instances of SAP R/3 involved in the
integration and link it with the Buyer account.
Note: Buying organization or service provider accounts must be enabled for Multi-ERP implementation by
Ariba SN Support. The required configuration sections will not be available for accounts that have not been
enabled.
Fore more information on Ariba SN setup, see the “Linking Multiple Business Applications” section, in
Chapter 4 “Configuring Supplier Connectivity”, of the Ariba SN Supplier Connectivity Guide.

Chapter 1 Ariba Supplier Connectivity Adapter Data Element Mapping
Data Element Mapping

The data elements, or fields, used by your SAP ERP system differ from the data elements used in cXML
documents. The ASC Adapter provides a mechanism for mapping field names and data from your SAP ERP
system to those used by cXML and Ariba SN. The ASC Adapter determines how data from your SAP ERP
system populates a corresponding cXML document, and it performs two-way mapping: from your SAP ERP
system to cXML, and from cXML to your SAP ERP system. The element mapping mechanism handles
one-to-one, many-to-one, and one-to-many mapping scenarios.
Figure 3 Element Mapping Overview
ASC Adapter
iDOC PO
or cXML
ER P A dapte r
payment Document
ERP cXML Ariba

SAP Mappings Payload
cXML Supplier
getPending
and Adapter Network
Connectivity
Get Data
The ASC Adapter maintains a set of cross reference or mapping tables. These tables store the information
necessary to translate values when sending or receiving cXML documents. It is likely that you will need to
customize the mappings to suit the needs of your particular implementation. For more information about
customization, see the “Customizing Data Mappings” section.
Supported cXML Transactions

The ASC Adapter supports the following cXML transactions:
• OrderRequest
• OrderConfirmationRequest
• ShipNoticeRequest
• InvoiceDetailRequest
• StatusUpdateRequest
• PaymentRemittanceRequest
• PaymentRemittanceAdviceRequest
• PaymentProposalRequest
• ReceiptRequest
For more detailed information about these transactions, see the cXML User’s Guide, the Ariba cXML
Solutions Guide and the sample mapping tables. The remainder of this section discusses the transactions on
a general level as they pertain to the ASC Adapter.

Data Element Mapping Chapter 1 Ariba Supplier Connectivity Adapter
Profile Transaction
When the ASC Adapter sends a ProfileRequest to Ariba SN, Ariba SN responds with a ProfileResponse
indicating the cXML documents that it accepts and their respective URLs. The ASC Adapter decodes the
response to extract URLs for the various transactions and stores the values so that they can be used in
subsequent transactions.
By default, the ASC Adapter runs the Profile transaction as a scheduled task every 24 hours. This interval
can be configured in the runtime. The ASC Adapter maintains a profile cache that is updated every time the
Profile transaction runs.
Purchase Order
When a buying organization requests products or services through its SAP ERP system, the ASC Adapter
maps the request to a cXML OrderRequest and sends it to Ariba SN. Ariba SN then routes the purchase
order to the appropriate supplier using the supplier’s preferred order routing method.
Note that there is no corresponding OrderResponse document. Instead, Ariba SN transmits a generic
response. When the ASC Adapter sends an OrderRequest document to Ariba SN, Ariba SN responds with a
synchronous cXML document that contains one of the following status codes:
• 2xx, indicating that Ariba SN accepted the document.
• 4xx, indicating that a permanent error has occurred and has been logged.
• 5xx, indicating that a transient error occurred. The ASC Adapter then re-sends the document with the
same payload ID for the specified number of retry attempts.
Scheduled Payments and Dynamic Discounting

Buying organizations use scheduled payments, that is, PaymentProposalRequest documents, to tell Ariba
SN and their suppliers about planned payments. These documents list scheduled payment dates, discount
amounts, and net amounts. Scheduled payments are used for information by default, but they can also be
used for Dynamic Discounting.
Dynamic Discounting allows buying organizations to pay suppliers early in exchange for discounts. Buying
organizations send proposed payment information to Ariba SN in PaymentProposalRequest documents
containing a special Extrinsic element called immediatePay. If suppliers choose schedule payments for early
settlement, Ariba SN sends the scheduled payments back to the buying organization through the ASC
Adapter. Updated PaymentProposalRequest documents are then used to update the payment schedule and
discount amount in the buying organization’s SAP system.
For more information about scheduled payments, see the Ariba cXML Solutions Guide. For more
information about Dynamic Discounting, see the Ariba SN Buyer’s Guide.
Invoice
Invoices are downloaded from Ariba SN to the ASC Adapter using the pull document transmission methods
described in “Understanding cXML Adapter Document Transmission” on page 10. For more information,
see the Ariba SN Supplier Connectivity Guide.

Chapter 1 Ariba Supplier Connectivity Adapter Data Element Mapping
Order Confirmation
Order confirmations are downloaded from Ariba SN to the ASC Adapter using the pull document
transmission method described in “Understanding cXML Adapter Document Transmission” on page 10. For
more information, see the Ariba SN Supplier Connectivity Guide.
Ship Notice
Ship Notices are downloaded from Ariba SN to the ASC Adapter using the pull document transmission
methods described in “Understanding cXML Adapter Document Transmission” on page 10. For more
information, see the Ariba SN Supplier Connectivity Guide.
Invoice Status Update

Invoice status updates are sent by buying organizations to inform Ariba SN and suppliers of the status of
invoice reconciliation. Buyers send StatusUpdateRequest documents to set invoice status to processing,
reconciled, paying, paid, rejected, or invalid. Ariba SN posts the documents to the URL that suppliers return
in their cXML ProfileResponse.
StatusUpdateRequest documents can identify invoices in two possible ways: through either a
DocumentReference or an InvoiceIDInfo element. For more information about invoice status updates, see
the Ariba cXML Solutions Guide.
Payment Remittance Request

Buyers can send a PaymentRemittanceRequest to notify suppliers when payment is made.
Payment Remittance Advice Request

Payment Remittance Advices are sent by Ariba SN to notify suppliers and SAP about external payment
made directly from Ariba SN. Ariba SN sends PaymentRemittanceAdviceRequest documents to suppliers as
well as SAP to create an accounting document.
Receipt Requests
The cXML ReceiptRequest document defines the receipt information of a purchase order or master
agreement with item details. A receipt line is a ReceiptItem element with a receipt line details. Buyers
generate receipts and address them to suppliers. However, Ariba SN routes them to Ariba Invoice and
Payment. When receipt data is successfully posted in Ariba SN, Buyers can see the receipts in their online
Outbox.
Customizing Data Mappings

The ASC Adapter mapping tables are intended as samples only. Buying organizations must customize ASC
Adapter mappings to suit their business processes. For example, each buying organization lists
requisitioners in cXML in a different way. These differences are handled by customizing mappings.
You can view and customize the sample data mappings in two ways:

Data Element Mapping Chapter 1 Ariba Supplier Connectivity Adapter
• In SAP NetWeaver XI Integration Builder Design Tool, where associated integration processes for each
transaction are presented under each namespace on the Object tab and can be edited and tested prior to
deployment.
• In spreadsheet applications such as Microsoft Excel, where you can view field-level details for each
supported transaction, and capture details relevant to the functional designs you create in SAP NetWeaver
XI Integration Builder Design tool.
The sample mapping tables are available on Connect.
W To view sample mapping tables on Connect:

1 Go to http://connect.ariba.com and log in.
2 On the navigation panel on the left, click Product Info > Ariba Supplier Connectivity > Adapter 1.4 for SAP
NetWeaver.
3 Under Ariba Supplier Connectivity Adapter 1.4 for SAP NetWeaver, click Data Transformation.
Configuring Supplier Quick Enablement

Ariba SN Quick Enablement allows buying organizations and Invoice Conversion service providers to
create new Ariba SN accounts on behalf of suppliers. They can create these accounts by specifying the
supplier’s company information in a Correspondent element in the header of purchase orders sent to the
supplier or invoices received from the supplier. Ariba SN uses this information to create the supplier’s
account.
ASC Adapter supports the Supplier Quick Enablement functionality by providing the required supplier
information, email address, and fax number, in the Purchase Order documents (transaction OrderRequest).
This information is retrieved from the Vendor Master Data.
The Quick Enablement functionality has the following limitations:

• If the information is not maintained for a particular vendor that is not referenced as a supplier in Ariba
SN, the purchase orders for this vendors forwarded to Ariba SN will be rejected.
• In case both routing information are available for a particular vendor, the fax will be used as the default
routing method.
Buying organization or service provider accounts must be enabled for Quick Enablement by Ariba SN
Support. Ariba SN ignores the Correspondent element for accounts that have not been enabled.
For more information about the Quick Enablement and the cXML, see the Quick Enablement section, in
Chapter 3 “Document Addressing and Security”, of the Ariba cXML Solutions Guide.
For more information about configuring Ariba SN for Quick Enablement, see the Inviting an Unregistered
Supplier section in Chapter 3 “Managing Supplier Relationships”, of the Ariba SN Buyer’s Guide.
For detailed steps to configure support for Multiple SAP instances, see “Linking Multiple SAP instances
with Ariba SN” on page 75.
For details on how to link multiple SAP instances from Ariba SN, see the Ariba SN Supplier Connectivity
Guide.

Chapter 1 Ariba Supplier Connectivity Adapter Testing the Configuration
Configuring AN Pay
The AN Pay feature in Ariba SN works with Ariba Invoice and Payment. With this new feature, buyers can
make payments in Ariba SN. When this feature is enabled, Ariba Invoice and Payment sends the Invoice
Status Update, and Payment Proposal to Ariba SN. Once the Payment is made in Ariba SN this information
is sent to SAP as an accounting document for reconciliation.
To enable AN Pay, the ASC Adapter has been modified. with the following new features:
• The sending of Invoice Status Updates and Payment Proposals have been disabled, as these will be
generated in Ariba Invoice and Payment.
• A new transaction, Payment Remittance Advice, has been added.
Defining the Business System ID in Ariba SN Buyer’s “Supplier Relationship” section is not mandatory,
when integrating a single SAP instance. However, the SAP R/3 system (ACC_DOCUMENT IDoc) expects the
Logical System ID, which is configured as Business System ID in Ariba SN Buyer’s “Supplier
Relationship” (received in the incoming Payment Remittance Advice cXML). This has been done to address
the possibility of a customer having multiple SAP instances where defining Business System ID is
mandatory. Therefore, the current XI mapping code will look for the System ID in cXML, and if it is not
present, it will take the value from the value mapping Global variable R3LS.
Enabling Support for Shipping and Handling Charges for Invoices

ASC Adapter supports the export of shipping and handling charges to SAP. This feature is supported in the
following cases:
• Shipping and handling charges with taxes added as service lines
Shipping and handling charges with taxes added as service lines will be sent to SAP as direct posting to
General Ledger (G/L) accounts.
• Shipping and handling charges added without any tax will be sent in the InvoiceDetail Summary only
Shipping and handling charges will be added and sent to SAP as unplanned delivery cost.
The IDoc type used for the Invoice transaction has been changed from the basic INVOICE02 to ZINVOICE02 to
support the posting of shipping and handling charges with tax added as service lines.
A new segment, ZACCOUNT_DATA, has been populated with data corresponding to the shipping and handling
charges service lines with taxes. To post this information as mentioned above either to the G/L account
directly or to unplanned delivery cost, a user exit must be implemented.
Fot more information about implementing the user exit, see “Making User Exit Enhancements to Support
Shipping and Handling Charges” on page 105.
Testing the Configuration

This section provides instructions for how to test your configuration.
To troubleshoot any errors you encounter, you can use the XI Runtime Work Bench (from the web UI) and
the Integration Engine Monitor (transaction SXMB_MONI from the SAP GUI) to track the exchanged
messages. You can also view the log files in the adapter log directory on SAP NetWeaver XI.

Testing the Configuration Chapter 1 Ariba Supplier Connectivity Adapter
For more information about error handling, see the “Understanding Error Handling” section.
Before beginning, be sure that you have at least one fully configured Ariba SN supplier relationship. For
more information about creating a supplier relationship, see Chapter 4, “Configuring Supplier Connectivity”
in the Ariba SN Supplier Connectivity Guide.
Testing Processes
After you have successfully deployed and configured the ASC Adapter, you should run test transactions to
ensure that Ariba SN and your SAP ERP system are communicating properly in both directions. To test
processes:
• Send a Purchase Order from your SAP system to Ariba SN.
• Run a getPending transaction by creating an invoice in Ariba SN and then sending it to your SAP system.
W To send a Purchase Order:

1 In your SAP ERP system, create a purchase order.
If the system is working properly, then the Purchase Order IDoc message is sent to SAP NetWeaver XI.
The ASC Adapter on SAP NetWeaver XI converts the IDoc to cXML, and then sends the cXML to Ariba
SN.
2 Verify that the messages are available in the XI monitoring tools (XI Runtime Workbench and Integration
Engine Monitor).
3 Log on to Ariba SN as the supplier. Check to see that the new order is displayed in the inbox of the
supplier. If it can be found in supplier's inbox, the outbound connection is working properly.
W To run a getPending transaction:

1 Create a test invoice in Ariba SN.
If the system is working properly, then the ASC Adapter downloads the Invoice from Ariba SN, converts
the cXML to IDoc, and then sends the IDoc to SAP ERP.
2 Verify that the messages are available in the XI monitoring tools (XI Runtime Workbench and Integration
Engine Monitor).
3 Check to see that the invoice is accepted in your SAP ERP system.
If these two checks are successful, the inbound connection is working properly.
Understanding Error Handling

The XI Runtime Work Bench and the Integration Engine Monitor (transaction SXMB_MONI) are used to
track error messages and email notifications, and to notify users about errors in inbound processing
(getPending transaction).
The following describe the error handling on the Integration server side:
• For simple transactions like Invoice: If an error occurs in the processing, or if a mapping error, or a data
retrieving error (RFC calls) occurs, the message is logged as an error in the SXMB_MONI, and can be
restarted (reprocessed).

• For complex/scheduled transactions (Receipt/PaymentProposal/InvoiceStatusUpdate): Messages are

processed in batches, and if an error occurs, it is logged in SXMB_MONI; the processing is stopped with
the timestamp of the last successfully processed message. In this case, the problem must be fixed; this
guarantees that the messages are processed only once.
The following describe the error handling on the Adapter Engine side:
• For inbound messages (AN-> R3), the Email notification is used to send an email when an error occurs
(mainly connection issues). This is because during the pull (getPending), XI is not aware of any message.
(For example, in the case of a connection issue there is no message, just a technical error in the
communication layer.)
• For outbound messages (R3 -> AN), the sending operation initiated by XI is synchronous, and if any
exception occurs, it is related to a message from XI. In this case, the adapter logs a detailed message,
which can be viewed with the RuntimeWork Bench. The message can be resent for processing manually
(in addition to the retry mechanism implemented by XI). The adapter also sends an Email Notification in
this case. The email notification is identical, except that the message is more precise and includes the
response from Ariba SN, if available (for example, in case of documents refused by Ariba SN).
Understanding Error and Status Codes

The cXML Adapter notification emails include an ASC Adapter error code, and a response status code. The
response status code refers to the cXML error/status codes received from the server. The cXML status codes
indicate success, transient errors, or permanent errors. The status code range 2xx denotes success, 4xx
denotes permanent errors, and 5xx denotes transient errors.
For more information about the different cXML status codes that can be found in the notification emails, see
the Protocol Specification > Response section of Chapter 2 “cXML Basics” in the cXML User’s Guide.
The following table describes the possible general error codes (ASC Adapter error codes) in cXML adapter
notifications:
Application Errors:
Status Text
ERR101 Invalid Configuration Parameter
ERR102 Incorrect Client Certification
ERR201 Authentication Failed on ASN
ERR202 ASN Internal Server Error
ERR203 Send cXML to ASN Failed (Invalid Request)
ERR204 Send cXML to ASN Failed (Temporary Error)
ERR205 Send cXML to ASN Failed (Unrecoverable Error)
ERR301 Get Profile Transaction Failed
ERR302 Get Pending Transaction Failed
ERR303 Outbound Transaction Failed
ERR401 Invalid Outbound Message (XI -> ASN)
ERR402 Invalid Inbound Message (ASN -> XI)

Application Errors:
Status Text
ERR403 Duplicate Outbound Message
ERR404 Duplicate Inbound Message
ERR405 Outbound Message Type Inconsistent with Channel Definition
ERR406 Inbound Message Type Inconsistent with Channel Definition
ERR407 Can not find corresponding record in download config file
Runtime Error:
Status Text
ERR501 Unexpected Error
ECC Errors:
Status Text
ECC101 Configuration Load Failed
ECC102 IO Error
ECC103 Ariba SN Not Available
Understanding Email Notifications

The following are the different parts of an error notification email:
• Date: The date and time of the error.
• Error: The ASC Adapter Error code. For a list of general error codes, see the Application Errors,
Runtime Error, and ECC Errors tables in the previous section.
• Error Detail: The error detail, which can be one of the following:
• A stack trace with the exception, if the request failed to reach Ariba SN, and the response message
from Ariba SN is not available
• Details of the cXML response, if the response from Ariba SN contains an error code. In this case, the
following sections will be available.
• Transaction: The channel name corresponding to the transaction in which the error occurred, like
[CC_Invoice_cXML_Sender].
• [Request Name/Type]: The name of the request and the type related to the transaction with the error, like
InvoiceDetailRequest/InvoiceDetailRequest.
• [Request URL]: The URL used for the request that failed, like
https://sevice.ariba.com/service/transaction/cxml.asp.

• [TimeStamp/PayloadID]: The timestamp and the payload of the response document, like
2007-09-04T17-23-29-07:00/1188951809740_498019780@10.10.61.126.
• [Response Status Code]: The cXML response status code, like 401. For a list of possible status messages,
see the Protocol Specification > Response section of Chapter 2 “cXML Basics” in the cXML User’s
Guide.
• [Response Status Text]: The text corresponding to the cXML response status code, like Unauthorized.
• [Response Status Desc]: The cXML response description “Error:Invalid sender credentials”. The
problem could be one of the following:
• Invalid, untrusted, or no certificate
• Posting to the wrong URL when your account is configured for certificate-based authentication. Please
contact customer support with the Error Reference Number: ANERR-10000000000000000000972190
for more details
The following are examples of error notification emails:
Authentication Error
Hi ,
This is an error notification from Ariba ASC Adapter.
Date: Tue Sep 04 17:23:29 PDT 2007
Error: ERR201 : Authentication Failed on ASN
Error Detail: Authentication failed when performing getPending(getPendingRequest) transaction:

[CC_Invoice_cXML_Sender] [Request Name/Type] InvoiceDetailRequest/InvoiceDetailRequest [Request
URL] https://svcitg.ariba.com/service/transaction/cxml.asp [TimeStamp/PayloadID]
2007-09-04T17-23-29-07:00/1188951809740_498019780@10.10.61.126 [Response Status Code] 401
[Response Status Text] Unauthorized [Response Status Desc] Error:Invalid sender credentials. The
problem could be either: 1) Invalid, untrusted, or no certificate; 2)posting to the wrong URL when
your account is configured for certificate-based authentication. Please contact support with the
Error Reference Number: ANERR-10000000000000000000972190 for more details
This is auto email notification, do not reply to this email.
Ariba SN System:
Ariba SN temporarily unavailable due to maintenance

Hi ,

Date: Wed Aug 29 13:34:12 PDT 2007
Error: ERR204 : Send cXML to ASN Failed (Temporary Error)
Error Detail: An temporary error occurs when performing getProfile transaction:

[CC_PurchaseOrder_cXML_Receiver_Test] [Request Name/Type] OrderRequest/OrderRequest [Request URL]
https://svcitg.ariba.com/service/transaction/cxml.asp [TimeStamp/PayloadID]
2007-08-29T13-34-12-07:00/1188419652763_824828725@10.10.61.126 [Response Status Code] 560
[Response Status Text] Temporary Server Error [Response Status Desc] Sorry, the Ariba Network is
temporarily unavailable for maintenance. Service will resume soon.
Ariba SN System:
Connection Exception
Hi ,
Date: Wed Sep 05 11:27:03 PDT 2007
Error: ECC103 : Ariba SN Not Available
Error Detail:
com.ariba.asc.connector.exception.AribaSNException: Cannot connect to Ariba SN at

com.ariba.asc.connector.cxml.util.CXMLSender.sendRequest(CXMLSender.java:199) at
com.ariba.asc.connector.cxml.util.CXMLSender.sendCXMLRequest(CXMLSender.java:119) at
com.ariba.asc.connector.controller.action.ProfileUpdateAction.sendProfileRequest(ProfileUpdateAct
ion.java:167) at
com.ariba.asc.connector.controller.action.ProfileUpdateAction.updateProfile(ProfileUpdateAction.j
ava:142) at
com.ariba.asc.connector.controller.action.ProfileUpdateAction.updateChannelProfile(ProfileUpdateA
ction.java:110) at
com.ariba.asc.connector.controller.action.ProfileUpdateAction.perform(ProfileUpdateAction.java:73
) at com.ariba.asc.connector.controller.ScheduleTaskMgr.run(ScheduleTaskMgr.java:84) at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at
java.security.AccessController.doPrivileged(Native Method) at
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by:
java.net.UnknownHostException: vcitg.ariba.com at
java.net.PlainSocketImpl.connect(PlainSocketImpl.java:153) at
java.net.Socket.connect(Socket.java:461) at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(DashoA12275) at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.(DashoA12275) at
com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(DashoA12275) at
com.ariba.asc.connector.cxml.util.AuthSSLProtocolSocketFactory.createSocket(AuthSSLProtocolSocket
Factory.java:315) at

Chapter 1 Ariba Supplier Connectivity Adapter Deploying the Project
com.ariba.asc.connector.cxml.util.AuthSSLProtocolSocketFactory.createSocket(AuthSSLProtocolSocket
Factory.java:384) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:704) at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:384) at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324) at
com.ariba.asc.connector.cxml.util.CXMLSender.sendRequest(CXMLSender.java:161) ... 10 more
Ariba SN System:
Deploying the Project

When you have customized your data mappings and tested all processes, you are ready to export and then
import the project as two SAP NetWeaver XI Export files (tpz files) using SAP NetWeaver XI Integration
Builder. SAP NetWeaver XI Integration Builder contains two parts:
• Design tool, which contains interface objects, mapping objects and integration processes
• Configuration tool, which contains business services and routing rules. For more information, see the
SAP NetWeaver XI documentation.
The design tpz file can contain one or more namespaces, which include the integration processes, mapping
objects and interface objects. The Configuration tpz file can contain one configuration scenario, which
includes business services and routing rules.
You can build as many tpz files as you need for one project. For more information about how to export a tpz
file, see the SAP NetWeaver XI documentation.
Each tpz file works as a single unit within SAP NetWeaver XI Integration Builder. For example, if you have
multiple namespaces within a single Design tpz file, all the namespaces will be imported and exported at the
same time, assuming that no other conditions are specified for these namespaces.
Ariba SN Certification
Ariba must certify any ASC Adapter that works with Ariba SN. Certification is the process by which Ariba’s
Global Solutions Organization (GSO) inspects and approves the ASC Adapter, the cXML documents it
generates, and its connection to Ariba SN.
In its default state, the ASC Adapter is Ariba SN-certified. Once you have customized data mappings, you
must perform certification testing again to ensure that all processes work as expected.
For more information about the certification process, see the Ariba SN Supplier Connectivity Guide. The
guide describes how to download certification files from Connect and provides instructions to guide you
through the certification process.

Deploying the Project Chapter 1 Ariba Supplier Connectivity Adapter
W To download the Ariba SN Supplier Connectivity Guide from Connect:

1 Go to http://connect.ariba.com and log in.
2 On the navigation panel on the left, click Product Info > Ariba Supplier Connectivity > Ariba Supplier
Connectivity.
3 Under Documentation in the Supplier Connectivity page, click Supplier Connectivity to download the
Supplier Connectivity.zip file.
4 Extract the Supplier Connectivity Guide.pdf file from the downloaded ZIP file.

Chapter 2 Configuring Your SAP ERP System
This appendix describes the configuration steps required to set up SAP applications for the following
transactions to and from the ASC Adapter:
• Outbound Purchase Orders
• Inbound Order Confirmation
• Inbound Ship Notices
• Inbound Invoice
• Outbound Payment Remittance
• Outbound Invoice status update
• Inbound and Outbound payment proposal
It includes the following sections:

• “Importing Custom Code” on page 91
• “Configuring SAP” on page 101
Importing Custom Code

The ASC Adapter uses custom code to support invoice status update and payment proposal transactions. If
you do not import the custom code for these transactions into your SAP instance, you are likely to encounter
errors.
Creating a Vendor Table

You must create a vendor table to hold all the Ariba SN-enabled vendor information.
Using SE11, create a transparent table for vendors according to the following format. Name it
ZARIBA_AN_VENDOR, and use SM30 to populate the values:
ZARIBA_AN_VENDOR
Fields Key Init Field Type Data Type Length Decimal Short Text
Places
MANDT X X MANDT CLNT 3 0 Client
BUKRS X X BUKRS CHAR 4 0 Company Code
LIFNR X X LIFNR CHAR 10 0 Account number of
vendor or creditor
You need to set the table sizing parameter by clicking on Technical Settings, and then set appropriate values
for the Data class and Size category fields.

Importing Custom Code Chapter 2 Configuring Your SAP ERP System
Creating Additional Structures

Additional structures are required for invoices, invoice status updates and payment proposal requests.
W To create additional structures:

• Using the transaction WE31, create the following structure for Invoices. Name it ZACCOUNT_DATA:
ZACCOUNT_DATA
Field Name Data Element Data Type Length Decimal Short Text
Places
WRBTR WRBTR
ANLN1 ANLN1
ANLN2 ANLN2
AUFNR AUFNR
KOSTL KOSTL
PS_PSP_PNR PS_PSP_PNR
SAKNR SAKNR
SGTXT SGTXT
WERKS WERKS
MWSKZ MWSKZ
BUKRS BUKRS
SHKZG SHKZG
Add the new accounting segment ZACCOUNT_DATA as a child element of E1EDP01.

• Using SE11, create the following structure for Invoice status updates. Name it
ZARIBA_INVOICE_STATUS_OPENNET:
ZARIBA_INVOICE_STATUS_OPENNET
Components Component Type Data Type Length Decimal Short Text

Places
LIFNR LIFNR CHAR 10 0 Account number of
vendor or creditor
INV_DOC_NO XBLNR CHAR 16 0 Reference document

number
DOC_DATE BLDAT DATS 8 0 Document date
DOC_TIME CPUTM TIMS 6 0 Time of entry
INVOICE_STATUS CHAR 50 0 Invoice status for Ariba

SN
AMT_DOCCUR BAPIWRBTR DEC 23 4 Amount in document

currency

Chapter 2 Configuring Your SAP ERP System Importing Custom Code
ZARIBA_INVOICE_STATUS_OPENNET

Places
CURRENCY WAERS CUKY 5 0 Currency Key
COMMENTS CHAR 300 0 Comments showing the

error/holds
• Using SE11, create the following structures for Payment Proposal Requests.
Name it ZARIBA_PAYMENTPROPOSAL_OPENNET:
ZARIBA_PAYMENTPROPOSAL_OPENNET

Places
PROPOSALID CHAR 20 0 Payment Proposal ID
DUE_DATE BLDAT DATS 8 0 Due Date
REF_INV_NUM XBLNR CHAR 16 0 Reference document

number
REF_DOC_DATE BLDAT DATS 8 0 Document Date
REF_DOC_TIME CPUTM TIMS 6 0 Time of Entry
PAYMENT_METHOD DZLSCH CHAR 0 Payment method
PAYMENT_METHOD_DESC TEXT1_042Z CHAR 30 0 Name of the payment

method in the
language of the
country
PYMNT_CURRENCY WAERS CUKY 5 0 Currency key
GROSS_AMT BAPIWRBTR DEC 23 4 Amount in document

currency
NET_AMT BAPIWRBTR DEC 23 4 Amount in document

currency
DISC_AMT BAPIWRBTR DEC 23 4 Amount in document

currency
DISC_CURRENCY WAERS CUKY 5 0 Currency Key
OPERATION CHAR 10 0 Operation type: new,

update, hold, cancel,
and so on

• Create the following structure. Name it ZARIBA_PYMNT_PROPOSAL_PAYEE:
ZARIBA_PYMNT_PROPOSAL_PAYEE

Places
INVOICE_NUM RE_BELNR CHAR 10 0 Document number of
an invoice document
FISCAL_YEAR GJAHR NUMC 4 0 Fiscal Year
PAYEE CHAR 10 0 Payee
LANGUAGE SPRAS LANG 1 0 Language key
VENDOR_NAME NAME1 CHAR 30 0 Name
POSTAL_ADDRESS ADRNR CHAR 10 0 Address
STREET1 AD_STREET CHAR 60 0 Street
STREET2 AD_STRSPP1 CHAR 40 0 Street 2
CITY AD_CITY1 CHAR 40 0 City
STATE REGIO CHAR 3 0 Region (State,

Province, County)
POSTAL_CODE AD_PSTCD1 CHAR 10 0 City postal code
COUNTRY LAND1 CHAR 3 0 Country key
EMAIL AD_SMTPADR CHAR 241 0 Internet mail (SMTP)

address
PHONE AD_TLNMBR1 CHAR 30 0 First telephone number;

dialing code and
number
FAX AD_FXNMBR1 CHAR 30 0 First fax number;

dialing code and
number
BANK_ACCOUNT_NUM BANKN CHAR 18 0 Bank account number
BANK_KEY BANKK CHAR 15 0 Bank key
• Create the following structure. Name it ZARIBA_PYMNT_PROPOSAL_PAYER:
ZARIBA_PYMNT_PROPOSAL_PAYER

Places
an invoice document
PAYER CHAR 10 0 Payer

ZARIBA_PYMNT_PROPOSAL_PAYER

Places
PAYER_NAME NAME1 CHAR 30 0 Name
POSTAL_ADDRESS ADRNR CHAR 10 0 Address
STREET1 AD_STREET CHAR 60 0 Street
CITY AD_CITY1 CHAR 40 0 City

Province, County)
POSTAL_CODE AD_PSTCD1 CHAR 10 0 City postal code
EMAIL AD_SMTPADR CHAR 241 0 Internet mail (SMTP)

address
PHONE AD_TLNMBR1 CHAR 30 0 First telephone number;

dialing code and
number
FAX AD_FXNMBR1 CHAR 30 0 First fax number;

dialing code and
number
• Create the following structure. Name it ZARIBA_PYMNT_PROPOSAL_REC_BANK:
ZARIBA_PYMNT_PROPOSAL_REC_BANK

Places
an invoice document
RECV_BANK BANKK CHAR 15 0 Bank key
BANK_NAME BANKA CHAR 60 0 Name of bank
CITY ORT01_GP CHAR 35 0 City

Province, County)
BANK_ACCOUNT_NUM BANKL CHAR 15 0 Bank account number

• Create the following structure. Name it ZARIBA_RFC_READ_TABLE:
ZARIBA_RFC_READ_TABLE

Places
WA CHAR4000 CHAR 4010 0 Character 4000
Creating an RFC-enabled Function Module

This section describes how to create an RFC-enabled function module and import the following sample
code:
• Z_ARIBA_ORBIAN_INFO, which returns the Payment Proposal ID required for Orbian integration
• Z_ARIBA_INVOICE_STATUS_UPDATE, which pulls incremental changes to invoices and invoice statuses in
SAP.
• Z_ARIBA_PAYMENT_PROPOSAL, which pulls incremental changes to payment proposals in SAP.
• Z_ARIBA_PO_ACCOUNTING_INFO, which pulls accounting information for purchase orders from SAP.
• Z_ARIBA_RFC_READ_TABLE, which pulls accounting information for purchase orders from SAP.
W To set up all custom code:

1 Navigate to transaction SE37 and choose Function Groups > Create Group.
2 Create a group called Z_ARIBA_OPEN_NETWORK.
3 Navigate to Function Groups > Change Group > Z_ARIBA_OPEN_NETWORK > Main Program.
4 Navigate to Program > Activate.
5 Double Click on Include for Global data (LZ_ARIBA_OPEN_NETWORKTOP).
6 Click on the pencil icon to edit. This step is required to enable the Upload menu item. From the top menu,
navigate to Utilities > More Utilities > Upload/Download> Upload <Location of the Global Data>.
7 Save and Activate.
W To set up Z_ARIBA_ORBIAN_INFO:
1 Navigate to transaction SE37.
2 Create a Function module called Z_ARIBA_ORBIAN_INFO, and supply the function group name
Z_ARIBA_OPEN_NETWORK.
3 On the Attributes tab, select Processing Type as Remote-enabled module.
4 On the Import Parameters tab enter the following parameters:
Parameter Type Reference Type Pass Value

DELIMITER LIKE SONV-FLAG “,”

5 On the Table tab, enter the following parameters:
Parameter Type Reference Type Optional

OPTIONS LIKE RFC_DB_OPT
FIELDS LIKE RFC_DB_FLD X
DATA LIKE TAB512 X
6 On the Exceptions tab, enter the following parameters:
Exception Short Text

PO_NOT_FOUND No Purchase Order Exists
7 Navigate to Utilities > More Utilities > Upload/Download > Upload <Location of the RFC code for
Z_ARIBA_ORBIAN_INFO>.
8 Save the entries.
9 Activate the Function module.
W To set up Z_ARIBA_INVOICE_STATUS_UPDATE:
2 Create a Function module called Z_ARIBA_INVOICE_STATUS_UPDATE, and supply the function group name

DATE_IN LIKE SY-DATUM X
TIME_IN LIKE SY-UZEIT X
5 On the Export Parameters tab, enter the following parameters:

DATE_OUT LIKE SY-DATUM X
TIME_OUT LIKE SY-UZEIT X
Parameter Type Reference Type

INVOICE_STATUS_INFO LIKE ZARIBA_INVOICE_STATUS_OPENNET

Z_ARIBA_INVOICE_STATUS_UPDATE>.
8 Save the entries.
9 Activate the Function module.
W To set up Z_ARIBA_PAYMENT_PROPOSAL:
2 Create a Function module called Z_ARIBA_PAYMENT_PROPOSAL, and supply the function group name

DATE_IN LIKE SY-DATUM X
TIME_IN LIKE SY-UZEIT X
5 On the Export Parameters tab, enter the following parameters:

DATE_OUT LIKE SY-DATUM X
TIME_OUT LIKE SY-UZEIT X
Parameter Type Reference Type

PAYMENT_PROPOSAL_INFO LIKE ZARIBA_PAYMENTPROPOSAL_OPENNET
PAYEE_INFO LIKE ZARIBA_PYMNT_PROPOSAL_PAYEE
PAYER_INFO LIKE ZARIBA_PYMNT_PROPOSAL_PAYER
RECV_BANK_INFO LIKE ZARIBA_PYMNT_PROPOSAL_REC_BANK
Z_ARIBA_PAYMENT_PROPOSAL>.
8 Navigate to Goto > Main Program, and check for INCLUDE LZ_ARIBA_OPEN_NETWORKF01. If it is not there,
add a line and double-click it to reach the include program.
9 In the include program INCLUDE LZ_ARIBA_OPENNETWORKF01, navigate to Utilities > More Utilities >
Upload/Download > Upload <Location of the RFC code for LZ_ARIBA_OPEN_NETWORKF01>.
10 Press back (F3) to reach the function pool SAPLZ_ARIBA_OPEN_NETWORK, and then save and activate the
entries.
11 Press back (F3) again to reach the function module Z_ARIBA_PAYMENT_PROPOSAL, and then save and
activate the entries.

W To set up Z_ARIBA_PO_ACCOUNTING_INFO:
2 Create a Function module called Z_ARIBA_PO_ACCOUNTING_INFO, and supply the function group name
Parameter Type Default Value Pass Value

DELIMITER LIKE “,” X
Parameter Type Reference Type Optional

FIELDS LIKE RFC_DB_FLD X
DATA LIKE TAB512 X

PO_NOT_FOUND No Purchase Order Exists
Z_ARIBA_PO_ACCOUNTING_INFO>.
8 Save and activate the entries.
W To set up Z_ARIBA_RFC_READ_TABLE:
2 Create a Function module called Z_ARIBA_RFC_READ_TABLE, and supply the function group name
Parameter Type Associated Default Value Optional Pass Value

Type
QUERY_TABLE LIKE DD02L-TABNAME SPACE X
DELIMITER LIKE SONV-FLAG SPACE X X
NO_DATA LIKE SONV-FLAG SPACE X X
ROWSKIPS LIKE SOID-ACCNT 0 X X

Parameter Type Associated Default Value Optional Pass Value

Type
ROWCOUNT LIKE SOID-ACCNT 0 X X
DISTINCT LIKE SONV-FLAG X X
FIX LIKE SONV-FLAG “X” X X
Parameter Type Associated Type Optional

FIELDS LIKE RFC_DB_FLD
DATA LIKE ZARIBA_RFC_READ_TABLE

TABLE_NOT_AVAILABLE QUERY_TABLE not active in Dictionary
TABLE_WITHOUT_DATA QUERY_TABLE is name of structure
OPTION_NOT_VALID Selection entries (e.g. syntax) incorrect
FIELD_NOT_VALID Field to be read not in table
NOT_AUTHORIZED User not authorized to access QUERY_TABLE
DATA_BUFFER_EXCEEDED Selected fields do not fit into structure DATA
7 On the Source Code tab, navigate to Utilities > More Utilities > Upload/Download > Upload <Location of the
RFC code for Z_ARIBA_RFC_READ_TABLE>.
8 Save and activate the entries.
Configuring SAP IDocs

The following SAP IDoc configurations are required for using the sample data mappings:
Transaction IDoc Basic Type Message Type

Purchase Order (New) ORDERS05 ORDERS
Purchase Order (Change) ORDERS05 ORDCHG
Order Confirmation ORDERS05 ORDRSP
Ship Notice DESADV01 DESADV
Invoice INVOIC02 INVOIC
Remittance PEXR2001 PAYEXT

Chapter 2 Configuring Your SAP ERP System Configuring SAP
Configuring SAP
The following steps pertain to SAP R/3 4.6c, and assume that you are familiar with your SAP application. If
you need more information about how to perform a specific step, see the documentation for your SAP
application.
Configuring SAP for IDoc Transactions

W To configure SAP for all IDoc transactions:
1 Use Transaction SM59 to create an RFC destination of type R/3.
2 Enter Target host, System Number, Getaway host, Getaway service on the Technical Settings tab, enter
Language, Client, User, Password on the Logon/Security tab, and then save your entries.
3 Use Transaction WE21 to create a port.
4 Choose Transactional RFC and click Create.
5 Enter port, description and RFC destination details, and then save your entries.
Configuring the Partner Profile

W To configure the partner profile:
• For New Purchase Order:
1 Use transaction WE20 to create a partner profile for a vendor.
2 Choose Partner type LI (Vendor) and click Create.
3 Enter partner (vendor) number, partner type (as LI) and appropriate Typ, Agent, and Lang. Save your
entries.
4 Click Create outbound parameter (the green plus sign).
5 Enter Partner function, Message type, Receiver port (created in step 4 of the previous section) and
Basic type.
6 On the message control tab, enter Application, Message type, and Process code.
7 Save your entries.

• Configure New Purchase Order using these parameters:
Parameter Value
Partner function VN
Message type ORDERS
IDoc type ORDERS05
Application EF
Message type NEUS
Process Code ME10

Configuring SAP Chapter 2 Configuring Your SAP ERP System
Retain the default selection, Transfer IDoc Immed., for the Output Mode parameter in the Outbound Options
tab.
• Configure Change Purchase Order using these parameters:
Parameter Value
Partner function VN
Message type ORDCHG
IDoc type ORDERS05
Application EF
Message type NEUS
Process Code ME11
Change True
tab.
• Configure Invoice using these inbound parameters:
Parameter Value
Partner function VN
Message type INVOIC
Process Code INVL
Select Trigger immediately as the value for the Processing by Function Module parameter if you want real
time processing.
• Configure Order Confirmation using these inbound parameters:
Parameter Value
Partner function VN
Message type ORDRSP
Process Code ORDR
Select Trigger immediately as the value for the Processing by Function Module parameter.
• Configure Advance Ship Notice with these inbound parameters:
Parameter Value
Partner function VN
Message type DESADV
Process Code DESA

time processing.
• Configure Outward Payment Remittance Advice with these outbound parameters:
Parameter Value
Partner function VN
Message type PAYEXT
IDoc Type PEXR2001
tab.
Note: You must also configure the bank in the partner profile for the remittance with the relevant port
number.
• Configure Inward Payment Remittance Advice with these inbound parameters:
Parameter Value
Partner function VN
Message type ACC_DOCUMENT
Process Code BAPI
time processing.
• Configure Early Payment with these inbound parameters:
Parameter Value
Partner function VN
Message type FIDCCH
Process Code FICH
time processing.
Maintaining Condition Records for Outbound Transactions

W To maintain condition records for outbound transactions (PO):
1 Using Tcode MN04 or NACE or NACR, in the screen enter output type NEUS and click Key combination.
2 Choose Purchasing Output Determination: Purch. Org./Vendor for EDI in the pop-up window and click the
check button to enter.
3 Verify the values for vendor number, partner function (VN), Partner number, Medium (6), and Time (4).

4 Click save.
If you also want to generate a printout, maintain the condition record for message type NEUS and select
Purchasing Output Determination: Document Type. Save the condition record.
Making Additional Change PO Configurations

W To perform additional setup:
1 Navigate to Tcode SPRO, and in the SAP reference IMG navigate to Material Management > Purchasing >
Messages > Output control > Messages Types > Define Messages type for purchase order > Fine – Tune control:
Purchase order.
2 Add new entries for condition type NEUS for Change Purchase Order with operation as 2.
3 Save the entry.
Maintaining Variants for Remittance

For generating IDocs from F110, maintain the variant for report RFFOEDI1. You must also configure the
company code, house bank, and payment method to generate IDoc for EDI.
Making Additional Invoice Configurations

Configure tax types and tax codes using transaction code OBCD. For more information, see the sample data
mapping for InvoiceDetailRequest.
.To assign the partner to a company code, use this configuration path:
• SPRO > MM > Logistic Invoice Verification > EDI > Assign company code
To assign program parameters, use this configuration path:

• SPRO > MM > Logistic Invoice Verification > EDI > Enter Program Parameters
To configure direct posting to general ledger accounts and material accounts, use this configuration path:
• SPRO > MM > Logistic Invoice Verification > Incoming Invoice > Activate Direct Posting to G/L
Accounts and Material Accounts
• Set both parameters to “active”
To configure how unplanned delivery costs are posted, use this configuration path:
• SPRO > MM > Logistic Invoice Verification > Incoming Invoice > Configure How Unplanned Delivery
Costs are Posted
• Set the value for the Distribute among invoice items parameter to blank

Maintaining IDOC Type Assignment to Function Module

Navigate to transaction code WE57, and edit the entry as follows:
Function Module Function Basic Exten Message Message Msg. Object Direct
Type Type sion Type Code Function Type ion
IDOC_INPUT_INVOIC F INVOIC0 ZINVOI INVOIC MM BUS2081 2
_MRM 2 C02
Maintaining Bank Key for the House Bank for Payment Remittance
Advice
You must configure the bank key, payment method, and general ledger for the house bank to generate IDoc
for Payment Remittance Advice.
The G/L Account to be posted to is derived using the house bank, which is maintained for the payer
company code for the payment method “E” and the remittance currency. These entries can be maintained in
transaction FBZP.
The G/L Account for Cash Discount is derived using the Chart of account for the CoCd and the transaction
key SKE. These entries can be maintained in transaction FBKP.
Note: If entries are not maintained as mentioned in the preceding section, the IDoc post will fail as it will not
be able to find the correct accounts to post to.
Making User Exit Enhancements to Support Shipping and Handling

Charges
To enable support for shipping and handling charges, using transaction WE30, create the IDoc type
ZINVOIC02 as an extension of INVOIC02.
To process the data sent in the IDoc, make the following changes in the User Exit provided by SAP. To
access the user exit, navigate to the transaction SMOD, and use the Enhancement name: MRMH0002 and Exit:
EXIT_SAPLMRMH_014.
The following example code shows the changes made to the user exit:
*&------------------------------------------------------------------*
*& Include ZXM08U25 *
*&------------------------------------------------------------------*
DATA: ls_data_s01 TYPE e1eds01,

lv_beznk TYPE mrm_rbkpv-beznk,
ls_data_k05 TYPE e1edk05,
lv_mwskz TYPE edi5279_a,
lv_mwskz_bkn TYPE mwskz_mrm.
DATA:ls_zaccount_data TYPE zaccount_data,

ls_cobl_mrm TYPE cobl_mrm,
ls_sdata TYPE edi_sdata OCCURS 0,
ls_lifnr TYPE lifnr,
ls_ebelen TYPE ebeln,
ls_e1edp02 TYPE e1edp02,
ls_land1 TYPE land1,

ls_txjcd TYPE txjcd.
* SAP Note Note 800866 - SUS-MM: Invoice with delivery costs

* This is to post the Shipping and handling charges as unplanned
* delivery cost at the header of the Invoice
IF i_idoc_data-segnam = 'E1EDS01'.
ls_data_s01 = i_idoc_data-sdata.
IF ls_data_s01-sumid = '020'.
lv_beznk = ls_data_s01-summe.
e_rbkpv-beznk = lv_beznk.
e_change = 'X'.
ENDIF.
ENDIF.
* Shipping and Handling added as service lines on invoice needs to be

* posted to G/L Directly. To post to G/L account directly we need to
* get this additional information regarding the accounting needs to
* fetched in an extension segment. Reading data from extension
* segement
IF i_idoc_data-segnam = 'ZACCOUNT_DATA'.
ls_zaccount_data = i_idoc_data-sdata.
IF NOT ls_zaccount_data IS INITIAL.
MOVE-CORRESPONDING ls_zaccount_data TO ls_cobl_mrm.
* Determine Tax Jurisidction code
* We need Tax Jurisidction code only for US so check the country from
* the Company Code
SELECT SINGLE land1 txjcd INTO (ls_land1, ls_txjcd) FROM t001
WHERE bukrs = ls_zaccount_data-bukrs.
* If the country is US then get the Tax Jurisidction code

* from Plant
IF ls_land1 = 'US'.
CLEAR ls_cobl_mrm-txjcd.
SELECT SINGLE txjcd INTO ls_cobl_mrm-txjcd FROM t001w
WHERE werks = ls_zaccount_data-werks.
* If Tax Jurisidction code is not maintained at Plant level, take it
* from Company code level
IF ls_cobl_mrm-txjcd IS INITIAL.
ls_cobl_mrm-txjcd = ls_txjcd.
ENDIF.
ENDIF.
APPEND ls_cobl_mrm TO t_frseg-cobl_mrm.

APPEND t_frseg.
ENDIF.
* We are introducing additional lines before the PO lines in t_frseg.

* SAP code try to get the PO number from the first line of t_frseg to
* get payment term and hence determine the baseline date, due this
* idoc posting fails. To Avoid it retrieving the Payment term from
* the PO line when present else get it from the Vendor data
* Read the Reference data
SELECT sdata FROM edid4 INTO TABLE ls_sdata
WHERE docnum = i_idoc_data-docnum
AND segnam = 'E1EDP02'.
LOOP AT ls_sdata INTO ls_e1edp02.

IF ls_e1edp02-qualf = '001'.

* Get the Po and fetch the payment term

SELECT SINGLE zterm INTO e_rbkpv-zterm FROM ekko
WHERE ebeln = ls_e1edp02-belnr.
ENDIF.
ENDLOOP.
* if PO line is not present get the payment term from Vendor Master
IF e_rbkpv-zterm IS INITIAL.
SELECT SINGLE sndprn INTO ls_lifnr FROM edidc
WHERE docnum = i_idoc_data-docnum.
SELECT SINGLE zterm INTO e_rbkpv-zterm FROM lfm1 WHERE
lifnr = ls_lifnr.
ENDIF.
e_change = 'X'.
ENDIF.
The following example code shows the changes made to the Exit EXIT_SAPLMRMH_015:
*&-----------------------------------------------------------------*
*& Include ZXM08U26 *
*&-----------------------------------------------------------------*
* move the data which needs to be posted directly to G/L account to

* t_co structure and delete the same from t_frseg
LOOP AT t_frseg.
LOOP AT t_frseg-cobl_mrm INTO t_co.
APPEND t_co.
e_change = 'X'.
ENDLOOP.
CLEAR t_frseg-cobl_mrm.
ENDLOOP.
IF NOT t_co[] IS INITIAL.

DELETE t_frseg WHERE ebeln IS INITIAL AND ebelp IS INITIAL AND
cobl_mrm IS NOT INITIAL.
ENDIF.
* Need to set the indicator auto tax calculation is not set.

* Apply OSS Note 385756
e_rbkpv-xmwst = 'X'.
e_change = 'X'.
Maintaining Global Company Code

Maintain the global company code using transaction code OB72. Assign this Global Company code to
company code using transaction code OBB5. Ensure that the global company code value and the company
code are same.


Appendix A cXML Adapter Parameters
This appendix describes common, inbound, and outbound parameters for the cXML Adapter. It contains the
following sections:
• “Common Parameters” on page 110
• “Inbound Parameters” on page 113
• “Outbound Parameters” on page 113
• “Configuring Retry Attempts” on page 114
• “Configuring Proxy Server Parameters” on page 114

Common Parameters Appendix A cXML Adapter Parameters
Common Parameters
Parameter Usage Type Data Type Value Description

Name
Adapter Status
Mode required string Test/Productio Deployment mode of the adapter.
n Default value: Test
Status required string Active/Inactiv The status of the adapter.

e Default value: Active
Authentication
Credential required string Shared Authentication method on Ariba SN.
Mode secret/Client Default value: Client certificate
certificate
Credential required string NetworkId/Netw The domain for the Buyer's

Domain orkUserId/DUNS credential.
Default value: NetworkId
Credential required string The Buyer's credential on Ariba SN.

The value can be NetworkId,
NetworkUserId or DUNS, depending
on the credential domain selected.
Shared Secret optional string The Buyer's shared secret on Ariba

Password SN. This parameter is only required
when parameter credentialMode is
set as Shared secret.
KeyStore optional string Certificate key store file path. This

Location parameter is only required when
parameter credentialMode is set as
Client certificate.
Example value:
file:/D:/AribaDataDir/cert/Ari
baStoreEntrust
Store Password optional string Certificate password for keystore.

This parameter is only required when
Client certificate.
Key Password optional string Certificate password for key. This

parameter is only required when
Client certificate.
Port required integer HTTPS port. This parameter is only

required when parameter
credentialMode is set as Client
certificate.
Default value: 443
cXML Configuration
AN ID required string Ariba Network ID.
Default value: AN01000000001

Appendix A cXML Adapter Parameters Common Parameters

Name
User Agent required string A textual string representing the
client system that is conducting the
cXML conversation.
Default value: Ariba SN Buyer
Language required string en-US Attribute needed for constructing

cXML request.
Default value: en-US
Data Directory required string Base directory needed to run the

adapter.
Default value: D:/AribaDataDir
cXML Version required string 1.2.017 The version number of the cXML
document data definition to be used
to generate the cXML documents
exchanged with Ariba SN. This
version number will be used in the
DOCTYPE entity of the cXML
documents.
Use XML optional boolean true/false A flag that specifies whether or not
Validation the validation is done on the
exchanged cXML documents
according to the cXML dtds. The
validation should be enabled during
the installation/ customization phase
to ensure that the exchanged cXML
documents are compliant. In the
production phase, the validation
could have a negative impact on
performance.
Email Notification
Use Email required boolean true/false A switch to turn on/off email
Notifications notification.
Default value: false
SMTP Server required string The SMTP server IP address or host

Host name.
Sender Address required string The email account for sending email.
Recipient required string The email account for email receiver.

Address
CC Address optional string The email account for email cc

receiver.
Sender Name required string The description name for sender.

Default value: AribaSN Adapter
Admin
Email required boolean true/false A flag that represents whether or not

Authentication the email server requires
authentication for sending email.
Default value: false

Common Parameters Appendix A cXML Adapter Parameters

Name
User optional string The email sender account. This
parameter is only required when
parameter emailAuthentication is
set as true.
Password optional string The password for the email sending

account. This parameter is only
required when parameter
emailAuthentication is set as true.
Certificate of SSL Server

Use optional boolean true/false A flag that specifies whether or not a
Alternative particular certificate key store is used
KeyStore and contains the certificate of the
Ariba SN server (to be used only if
the certificate key store used by the
JDK runtime does not contain the
Ariba Supplier Network Trusted
Authority Certificate.)
Trust KeyStore optional string Certificate key store file path for
Location certification of SSL server. This
parameter can be left blank when
connecting to Ariba SN in
production.
Trust KeyStore optional string Certificate password for keystore for

Password certification of SSL server. This
parameter can be left blank when
connecting to Ariba SN in
production.

Appendix A cXML Adapter Parameters Inbound Parameters
Inbound Parameters
Parameter Usage Type Data Value Description

Name Type
cXML Configuration
GetProfile required string URL used to send
URL ProfileRequest.
Default value:
https://certservice.ariba.
com/service/transaction/cx
ml.asp
GetProfile required integer Poll interval of profileRequest

Interval expressed in minutes.
(Minutes) Default value: 60
GetPending required integer Poll interval of

Interval getPendingRequest expressed in
(Minutes) minutes.
Default value: 15
Max required integer Max number of Documents that

Documents can be received from the pending
in queue in a single getPending
GetPending request.
Default value: 2
Inbound Request Type

Inbound required string One of following: The request type for Inbound.
Request ConfirmationRequest Default value:
Type InvoiceDetailRequest ConfirmationRequest
ShipmentNoticeRequest
PayMeNowRequest
Outbound Parameters
Parameter Name Usage Type Data Type Value Description

cXML Configuration
GetProfile URL required string URL used to send
ProfileRequest.
Default value:
https://certservice.ariba
.com/service/transaction/
cxml.asp
GetProfile required integer Poll interval of profileRequest

Interval expressed in minutes.
(Minutes) Default value: 60

Configuring Retry Attempts Appendix A cXML Adapter Parameters
Parameter Name Usage Type Data Type Value Description

Outbound Request Type
Outbound Request required string One of following: The request type for Outbound.
Type OrderRequest Default value: OrderRequest
ChangeOrderRequest
InvoiceUpdateRequest
PaymentRequest
PaymentRemittanceReq
uest
Configuring Retry Attempts

The following parameters control the interval and the number of times the adapter framework will attempt to
re-send a message to an adapter:
• xiadapter.outbound.retryInterval.default
• xiadapter.outbound.numberRetries.default
These parameters control the interval between retry attempts for outbound messages sent by SAP
NetWeaver XI to the cXML adapter, and the number of inbound documents sent by the cXML adapter to XI.
By default, the interval and maximum number of retries are configured to 300000 millisecond and 3 times,
respectively. The following steps describe how to change their default values.
W The change the default values for retry parameters:

1 Log in to Visual Administrator tool.
2 In the left panel of Visual Administrator, click Cluster, and then expand the Server***** node.
3 Expand the Services node, and then select the SAP NetWeaver XI Adapter: SAP NetWeaver XI service.
4 In the right panel, set the value for the xiadapter.outbound.retryInterval.default.

The default value is 30000 milliseconds.
5 Set the value for xiadapter.outbound.numberRetries.default.
The default value is 3 times.
6 Click Update, and then click Save in the toolbar to save the change.
Configuring Proxy Server Parameters

The ASC Adapter can be configured to use Secure HyperText Transfer Protocol (HTTPS) through a proxy
server. The following methods of authentication on the proxy server are supported:
• Basic
• Digest
• NTLMv1 (Note that NTLMv2 is not supported)

Appendix A cXML Adapter Parameters Configuring Proxy Server Parameters
To enable secure communication through a proxy server, configure the following parameters for the cXML
Adapter:
Parameter Name Type Value Description

Use Proxy Server Boolean No (default) Enables or disables the use of
Yes the proxy server for remote
communication with Ariba
SN
Proxy Server Host String Host name or IP address of

the proxy server
Proxy Server Port Integer Port used by the proxy server

to handle secure
communication
Proxy List None (default) Indicates the method used for

Authentication Basic authentication on the proxy
Method Digest server. If None, the proxy
NTLM server does not require
authentication.
Note that NTLMv2 is not

supported.
Username String The user name used for

authentication. Required for
all three authentication
methods.
Password String The password used for

authentication. Required for
all three authentication
methods.
Domain String The domain to which the user

identified by the Username
parameter belongs. Required
for NTLM authentication
only.

Configuring Proxy Server Parameters Appendix A cXML Adapter Parameters

Index
A channel 54
activating the scenario 27, 34, 38, 42, 49 CC_PuchaseOrder_cXML_Receive communication
activating the scenarioscenario, activating 30 channel 26
adapter engine 8 CC_Receipt_cXML_Receiver communication channel
Advance Ship Notice Integration Scenario, configuring 61
34 cefining technical and business landscape for Ariba SN
application components, assigning services to 28, 31, 35, 14
39, 44, 65 Change Purchase Order Integration Scenario,
archive file 9 configuring 27
downloading 9 Common Information Interface (CIM) format 13
Ariba SN Certification 89 communication channel for Ariba SN Business Service,
Ariba SN Product and Component Definitions, creating by copy 20
Importing 13 communication channels by copy, creating 20
ASC Adapter 7 communication channels for R/3, creating 18
ASC Adapter archive file 9 communication channels, Configuring 26
assigning business systems in the integration directory communication channels, configuring 29, 32, 37, 41, 46
18 CommunicationChannel global variable 23
assigning services to the application components 28, 31, Component View, Selecting 44
35, 39, 44, 65 component view, selecting 25, 28, 51, 65
configure connections 31, 36
configuring clobal variables 21
B configuring communication channels 26, 29, 32, 37, 41,
46
business landscape for Ariba SN, defining 14
configuring connections 25, 28, 40, 45
business landscape for SAP R/3, defining 15
configuring IDoc metadata 20
business landscape for XI File System, defining 16
configuring integration scenario 25
Business Landscape Wizard 14, 15, 16
configuring integration scenarios in the integration
Business Process Engine 8
directory 24
Business System Wizard 14, 15, 16
configuring R/3 connectivity 17
business systems, assigning in the integration directory
configuring receiver determination 33, 37, 41, 48
18
configuring SAP NetWeaver XI Value Mapping 21
BusinessSystem global variable 23
configuring Supplier Quick Enablement 82, 83
Configuring the Advance Ship Notice Integration
C Scenario 34
Configuring the Change Purchase Order Integration
CC_AdvanceShipNotice_cXML_Sender Scenario 27
communication channel 37 configuring the cXML Adapter 12
CC_ChangePuchaseOrder_cXML_Receive Configuring the Integration Scenario 28, 31, 35, 39, 43
communication channel 29 Configuring the Invoice Integration Scenario 38
CC_Invoice_cXML_Sender communication channel 41 Configuring the Log 11
CC_InvoiceStatusUpdate_cXML_Receiver Configuring the Order Confirmation Integration
communication channel 47 Scenario 30
CC_InvoiceStatusUpdate_File_Receiver Configuring the Purchase Order Integration Scenario 24
communication channel 47 configuring the System Landscape Directory 13
CC_InvoiceStatusUpdate_File_Sender communication configuring Transaction Processes 17
channel 48 configuring UOM Code Mapping 21
CC_OrderConfirmation_cXML_Sender communication connections, configure 31, 36
channel 32 connections, configuring 25, 28, 40, 45
CC_PaymentProposal_cXML_Receiver communication creating a communication channel by copy for Ariba SN

Index
Business Service 20 IDoc metadata, configuring 20

creating communication channels by copy 20 IDoc Payload 21
creating communication channels for R/3 18 IDoc Receiver 18
creating the IDoc Receiver communication channel 18 IDoc Receiver communication channel 18
creating the RFC Receiver communication channel 19 IDoc Receiver communication channel, creating 18
Customizing Data Mappings 81 Importing Ariba SN Product and Component Definitions
cXML 7 13
cXML Adapter 7 importing design package 17
deploying 11 Importing Design Packages 17
installing 11 importing product and component definitions 13
cXML Adapter and metadata definition files 9 installation requirements 9
cXML Adapter, configuring 12 integration builder 18
cXML protocol 10 Integration Builder Design tool 17
cXML transactions 79 integration engine 8
cXML transport protocol 7 integration processes 7
Integration Scenario, configuring 28, 31, 35, 39, 43
integration scenario, configuring 25
D integration scenario, transfering 24, 27, 30, 34, 43
Data Element Mapping 79 integration server 8
DataAvailableMessage element 11 Invoice Integration Scenario, configuring 38
defining business landscape InvoiceStatusUpdateStartDateTime global variable 22
for Ariba SN 14
for SAP R/3 15
for XI File System 16 L
defining technical and business landscape for LastUpdateDateTime_InvoiceStatusUpdate_INST.xml
NetWeaver XI File System 16 file, modifying 48
defining technical and business landscape for SAP R/3 linking multiple SAP instances with Ariba SN 75
15
defining technical landscape
for Ariba SN 14 M
for SAP R/3 15 mapping configuration and design files 9
for XI File System 16 modifying the
defining the business landscape for Ariba SN 14 LastUpdateDateTime_InvoiceStatusUpdate_INST.xm
defining the business landscape for SAP R/3 15 l file 48
defining the business landscape for XI File System 16
defining the technical landscape for Ariba SN 14
defining the technical landscape for SAP R/3 15 O
defining the technical landscape for XI File System 16 objects, generating 26, 29, 36
Deploying the Project 89 Order Confirmation Integration Scenario, configuring 30
design package 7 Overview 7
design package, importing 17
P
G
PaymentProposalStartDateTime global variable 22
generate the objects 41 product and component definitions, importing 13
generating the objects 26, 29, 36 Purchase Order Integration Scenario, configuring 24
generating the objects, objects, generating 46
GetPending transaction 11
getPendingInterval parameter 11 R
GetPendingResponse document 11 R/3 connectivity, configuring 17
global variable parameters 21 ReceiptRequest request type 61
Global Variables 21 ReceiptStartDate 22
global variables, configuring 21 ReceiptStartDateTime global variable 22
receiver determination, configuring 33, 37, 41, 48
I Requirements 9
RFC adapter 8
IDoc Metadata 20 RFC Receiver 19

Index
RFC Receiver communication channel 19

RFC Receiver communication channel, creating 19
S
SAP configuration files 9
SAP NetWeaver Exchange Infrastructure 7
SAP NetWeaver XI 8
about 8
SAP XI 7
scenario, Activating 42
scenario, activating 27, 34, 38, 49
Select Component View 35
Selecting Component View 44
selecting component view 51, 65
selecting the component view 25, 28
setting up the cXML Adapter 10
SNDPFC global variable 23
SNDPRT global variable 23
Supplier Quick Enablement, configuring 82, 83
supported cXML transactions 79
System Landscape Directory 13
T
technical and business landscape for Ariba SN, defining
14
technical and business landscape for NetWeaver XI File
System, defining 16
technical and business landscape for SAP R/3, defining
15
technical landscape for Ariba SN, defining 14
technical landscape for SAP R/3, defining 15
technical landscape for XI File System, defining 16
Technical Landscape Wizard 15, 16
Technical System Wizard 14, 15, 16
testing processes 84
testing the configuration 83
the integration scenario, transfering 39
TimeZone global variable 22
Transaction Processes, configuring 17
transfering integration scenario 24
transfering the integration scenario 27, 30, 34, 39, 43
U
Understanding Document Transmission 10
UOM Code Mapping, configuring 21
UOM transformation rules parameters 21
V
value mapping 21

Index

ASC Adapter NW

Uploaded by

Copyright:

Available Formats

You might also like

ASC Adapter NW

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

ASC Adapter NW

Uploaded by

Copyright:

Available Formats

Ariba™

Chapter 1 Ariba Supplier Connectivity Adapter . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Configuring Your SAP ERP System . . . . . . . . . . . . . . . . . . . . . 91

Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide iii

Configuring SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Appendix A cXML Adapter Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 109

iv Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide

• Ariba SN Supplier Connectivity Guide

The ASC Adapter consists of three parts:

Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide 7

Figure 1 Architecture Overview

Ariba Supplier Connectivity

Integration Engine Adapter Engine

NetWeaver Exchange Infrastructure

W To use the ASC Adapter:

8 Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide

Product definition files ASCAdapterNetweaver.SoftwareCatalog.zip

Mapping design and ASCAdapterNetweaver.Design.tpz

SAP configuration files Global_Data.txt

Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide 9

• Connection information for your SAP ERP system.

Setting Up the cXML Adapter

Understanding cXML Adapter Document Transmission

10 Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide

Deploying the cXML Adapter

W To install the cXML Adapter:

7 Click Next in the next window.

9 Click Confirm to accept the change.

Installing Additional Resources

Configuring the Log

Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide 11

W To set properties for logging to a separate file:

3 Click Connect in the pop-up window to display the login window.

4 Enter your password to log in to Visual Administrator.

Next, set properties for the Log Configurator.

W To set properties for the Log Configurator:

Configuring the cXML Adapter

12 Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide

Configuring the System Landscape Directory

You must make the following settings in the SLD:

Importing Ariba SN Product and Component Definitions

W To import product and component definitions:

2 Navigate to the Content section, and then click on Import.

3 Select the ASCAdapterNetweaver.SoftwareCatalog.zip by clicking on the Browse button, and then

5 In the Product Catalog, verify that the following product is available:

6 Next, verify that the following component is available:

Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide 13

Defining Technical and Business Landscape for Ariba SN

W To define the Technical Landscape for Ariba SN:

Important: Ariba recommends the use of fully qualified Host names.

W To define the Business Landscape for Ariba SN:

Note: The Logical System Name is not required.

14 Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide

Defining Technical and Business Landscape for SAP R/3

W To define the Technical Landscape for SAP R/3:

W To define the Business Landscape for SAP R/3:

3 In the Wizard, enter the business system name. E.g. BS_SAPR3_46C

Ariba Supplier Connectivity Adapter for SAP NetWeaver Guide 15

Defining Technical and Business Landscape for NetWeaver XI File System