Ariba cloud ci 7.0

Ariba
Document Version: 2 – 2016-04
Ariba Cloud Integration 7.0 Release Guide
Ariba Network
Ariba Procurement and Invoicing Solutions
Ariba Sourcing
Ariba Contract Management

Content
Certification for Integration of S/4HANA On-Premise Edition 1503 with Ariba Solutions. . . . . . . . 6
Enhanced Oracle Adapter to Support Oracle ERP 12.2.4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Additional References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Oracle Adapter Certification to Support Oracle Fusion Middleware 12c (12.1.3). . . . . . . . . . . . . . . . 8
About Oracle Adapter Certification to Support Oracle Fusion Middleware 12c (12.1.3). . . . . . . . . . . . . . . .8
Additional References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Changes to Existing Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installing and Configuring the Ariba Network Adapter for Oracle Fusion Middleware. . . . . . . . . . . . . . . . .9
Downloading the Ariba Network Adapter for Oracle Fusion Middleware 12c. . . . . . . . . . . . . . . . . . . . 9
Enhanced SAP Adapter to Support Additional Service Line Types in Service Purchase Orders
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
About Enhanced SAP Adapter to Support Additional Service Line Types in Service Purchase Orders
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Additional References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Technical and Functional Changes for Enhanced SAP Adapter to Support Additional Service Line
Types in Service Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Technical Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Functional Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
cXML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Installing and Configuring Enhanced SAP Adapter to Support Additional Service Line Types in Service
Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Importing the Transports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Handling Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Enhanced SAP Adapter to Support Setting Spend Limits on Service Sheets with Unplanned
Spend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
About Enhanced SAP Adapter to Support Setting Spend Limits on Service Sheets with Unplanned
Spend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Functional and Technical Changes for Enhanced SAP Adapter to Support Setting Spend Limits on
Service Sheets with Unplanned Spend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
cXML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installing and Configuring Enhanced SAP Adapter to Support Setting Spend Limits on Service Sheets
with Unplanned Spend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Enabling Support for Setting Spend Limits on Service Sheets with Unplanned Spend. . . . . . . . . . . . 22
2 © 2016 SAP SE or an SAP affiliate company. All rights reserved.
Content

Enhanced SAP Adapter to Support Invoice with Ship Notice Reference or Receipt Reference
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
About Enhanced SAP Adapter to Support Invoice with Ship Notice Reference or Receipt Reference
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Additional References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Technical and Functional Changes for Enhanced SAP Adapter to Support Invoice with Ship Notice
Reference or Receipt Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Technical Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
cXML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Installing and Configuring Enhanced SAP Adapter to Support Invoice with Ship Notice Reference or
Receipt Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Handling Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Support for Line Item-level Attachments in Requests for Quotations. . . . . . . . . . . . . . . . . . . . . . .27
About Support for Line Item-level Attachments in Requests for Quotations . . . . . . . . . . . . . . . . . . . . . .27
Changes to Existing Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Installing and Configuring Support for Line Item-Level Attachments in Request for Quotations. . . . . . . . 28
Downloading the Mapping Workbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Enhancements to Fieldglass Master Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
About Enhancements to Fieldglass Master Data Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Technical and Functional Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Installing and Configuring Enhancements to Fieldglass Master Data Integration. . . . . . . . . . . . . . . . . . .34
Authenticating Fieldglass and SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Integration of Master Data from SAP ERP with Ariba Sourcing and Ariba Contract
Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
About Integration of Master Data from SAP ERP with Ariba Sourcing and Ariba Contract Management
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Functional and Technical Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Installing and Configuring Integration of Master Data from SAP ERP with Ariba Sourcing and Ariba
Contract Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Importing the Transports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Configuring Integration of Master Data from SAP ERP with Ariba Sourcing and Ariba Contract
Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Content © 2016 SAP SE or an SAP affiliate company. All rights reserved. 3

Integration of Supplier Information and Performance Management with SAP ERP through
MDG-S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
About Integration of Ariba Supplier Information and Performance Management with SAP ERP
through MDG-S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Maintaining Supplier User Login ID Information on SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Maintaining Vendor ID Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Functional and Technical Changes for SIPM integration with SAP ERP through MDG-S. . . . . . . . . . . . . . 47
Functional Changes for Supplier Information and Performance Management Integration with SAP
ERP through MDG-S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Technical Changes for Ariba Supplier Information and Performance Management Integration with
SAP ERP through MDG-S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Installing and Configuring Integration of SIPM with SAP ERP through MDG-S. . . . . . . . . . . . . . . . . . . . .53
Configuring the Integration of Ariba Supplier Information and Performance Management with SAP
ERP through MDG-S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Exporting Supplier Master Data from SAP ERP to Ariba Supplier Information and Performance
Management in the Full Load Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Exporting Supplier Master Data from SAP ERP to Ariba Supplier Information and Performance
Management in the Incremental Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Checking the Status of Outbound Supplier Master Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . 61
Importing Supplier Master Data from Ariba Supplier Information and Performance Management
to SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Viewing Vendor ID and Business Partner Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Viewing Error Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Integration of Contract Information with SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
About the Integration of Contract Information with SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Functional and Technical Changes for the Integration of Contract Information with SAP ERP. . . . . . . . . 66
Functional Changes for the Integration of Contract Information with SAP ERP. . . . . . . . . . . . . . . . . 66
Technical Changes for the Integration of Contract Information with SAP ERP. . . . . . . . . . . . . . . . . . 68
Installing and Configuring the Integration of Contract Information with SAP ERP. . . . . . . . . . . . . . . . . . 70
Configuring PI Value Mappings for Contract Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Maintaining the Pricing Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Configuring Communication Channels for the Contract Integration Scenario. . . . . . . . . . . . . . . . . . 72
Configuring Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Real-Time Budget Integration Between Ariba Procurement Solution and SAP ERP. . . . . . . . . . . . 80
Additional References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Support for Taxes and Charges on Requisitions, Purchase Orders, and Invoices in Ariba
Procurement Solution Integrated with SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Additional References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Content

Support for Taxes and Charges on Purchase Orders in Ariba Procurement Solution Integrated
with PeopleSoft ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Additional References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Content © 2016 SAP SE or an SAP affiliate company. All rights reserved. 5

Certification for Integration of S/4HANA On-
Premise Edition 1503 with Ariba Solutions
S/4HANA, on-premise edition 1503, is certified to integrate with the following Ariba Solutions:
Ariba Collaborative Sourcing Ariba Procurement and Invoicing Solu
tions
Ariba StartSourcing
Ariba Contract Management Professio
nal
Ariba Procurement Content Ariba Strategic Sourcing and Contract
Management Solutions
Ariba Discount Professional Ariba Procure-to-Order Professional Sol
ution
Ariba Supplier Information and Perform
ance Management
Ariba Document Automation Ariba Procure-to-Pay Professional Ariba Procure-to-Order Professional
Federated Process Control
Ariba Invoice Professional Ariba Services Procurement Payment Integration Toolkit
Ariba Network Ariba Sourcing Professional Ariba Collaborative Supply Chain 1.0
Ariba Network Adapter for SAP NetWea
ver
Ariba Spot Quote
Ariba Payment Professional Ariba StartContracts
Certification for Integration of S/4HANA On-Premise Edition 1503 with Ariba
Solutions

Enhanced Oracle Adapter to Support Oracle
ERP 12.2.4
The Ariba Network Adapter for Oracle Fusion Middleware is certified to support the following transactions on
Oracle ERP 12.2.4 with Ariba Network using:
● Oracle Fusion Middleware 11g (11.1.1.4):
All transactions currently supported on Oracle ERP 12.1.1.
● Oracle Fusion Middleware 12c (12.1.3):
○ Inbound: Ship notices, invoices, and order confirmations
○ Outbound: Purchase orders
Following solutions are also certified to integrate with Oracle ERP 12.2.4 and support all transactions currently
supported on Oracle ERP 12.1.1:
● Ariba Procurement Solution
● Payment Integration Toolkit
Additional References
For more information about deploying the Ariba Network Adapter for Oracle Fusion Middleware 11g and the Ariba
Network Adapter for Oracle Fusion Middleware 12c, see the Oracle Fusion Middleware Cloud Integration Adapter
Setup Guide.
Enhanced Oracle Adapter to Support Oracle ERP 12.2.4 © 2016 SAP SE or an SAP affiliate company. All rights reserved. 7

Oracle Adapter Certification to Support Oracle
Fusion Middleware 12c (12.1.3)
About Oracle Adapter Certification to Support Oracle Fusion Middleware 12c (12.1.3) [page 8]
Changes to Existing Functionality [page 9]
Installing and Configuring the Ariba Network Adapter for Oracle Fusion Middleware [page 9]
About Oracle Adapter Certification to Support
Oracle Fusion Middleware 12c (12.1.3)
The Ariba Network Adapter for Oracle Fusion Middleware is certified to integrate with Oracle Fusion Middleware
12c (12.1.3) and Oracle ERP 12.2.4.
This feature, available in Ariba Network Adapter for Oracle Fusion Middleware 12c is applicable to Ariba Procure-
to-Pay.
The Ariba Network Adapter for Oracle Fusion Middleware 12c supports the following transactions in Cloud
Integration release 7.0:
Inbound Transactions Outbound Transactions
Ship Notice Purchase Order
Invoice -
Order Confirmation -
Enabling This Feature
This feature is enabled for all customers. For information about deploying the Ariba Network Adapter for Oracle
Fusion Middleware 12c and migrating customizations, see Installing and Configuring the Ariba Network Adapter for
Oracle Fusion Middleware [page 9].
Backward Compatibility
This feature is not compatible with previous versions of the Ariba Cloud Integration releases.
Oracle Adapter Certification to Support Oracle Fusion Middleware 12c (12.1.3)

For more information about deploying the Ariba Network Adapter for Oracle Fusion Middleware 12c, see the Oracle
Fusion Middleware Cloud Integration Adapter Setup Guide.
Changes to Existing Functionality
Previously, Ariba Network Adapter for Oracle Fusion Middleware did not support integration with Oracle Fusion
Middleware 12c (12.1.3).
Now, the Ariba Network Adapter for Oracle Fusion Middleware 12c supports out-of-the-box integration of Ariba
Network with Oracle ERP 12.2.4.
Installing and Configuring the Ariba Network
Adapter for Oracle Fusion Middleware
For information about downloading the Ariba Network Adapter for Oracle Fusion Middleware 12c, Cloud
Integration release 7.0, see the following section:
Downloading the Ariba Network Adapter for Oracle Fusion Middleware 12c [page 9]
Downloading the Ariba Network Adapter for Oracle Fusion
Middleware 12c
Context
To deploy Ariba Network Adapter for Oracle Fusion Middleware 12c, you must download the Ariba Network
Adapter for Oracle Fusion Middleware 12c ZIP file.
Procedure
1. Download the AribaNetworkAdapterOracleFusion_12c_vCI_7_FR.zip file from Ariba Connect (http://
connect.ariba.com).
2. Save and unzip the downloaded file in a location on your local drive.
For example: D:2016_Apr_CI7. Ensure that you follow the required sequence in your current directory
structure for all transactions while deploying the new changes.
Oracle Adapter Certification to Support Oracle Fusion Middleware 12c (12.1.3) © 2016 SAP SE or an SAP affiliate company. All rights reserved. 9

For information about setting up and deploying the Ariba Network Adapter for Oracle Fusion Middleware 12c, see
the Prerequisites for Deploying the Ariba Network Adapter for Oracle Fusion Middleware section in the Ariba Oracle
Fusion Middleware Adapter Setup Guide.
For information about upgrading from the Ariba Network Adapter for Oracle Fusion Middleware 11g to the Ariba
Network Adapter for Oracle Fusion Middleware 12c, see the Upgrading the Ariba Network Adapter for Oracle Fusion
Middleware and Migrating Customizations section in the Ariba Oracle Fusion Middleware Adapter Setup Guide.
Oracle Adapter Certification to Support Oracle Fusion Middleware 12c (12.1.3)

Enhanced SAP Adapter to Support Additional
Service Line Types in Service Purchase Orders
The Ariba Network Adapter for SAP NetWeaver now also supports blanket, contingency, and informational line
types on purchase orders with planned service hierarchies. By default, the line type is standard.
About Enhanced SAP Adapter to Support Additional Service Line Types in Service Purchase Orders [page
11]
Technical and Functional Changes for Enhanced SAP Adapter to Support Additional Service Line Types in
Service Purchase Orders [page 13]
Installing and Configuring Enhanced SAP Adapter to Support Additional Service Line Types in Service
Purchase Orders [page 15]
Handling Errors [page 16]
About Enhanced SAP Adapter to Support Additional
Service Line Types in Service Purchase Orders
This feature is available in the Ariba Network Adapter for SAP NetWeaver (SAP NetWeaver PI 7.1, 7.3, 7.31, or 7.4
and all SAP ERP 6.0 EhP4 and above versions). The feature supports transmission of the following additional
service line item types in purchase orders with planned service hierarchies, as an extrinsic cXML, from SAP ERP to
suppliers on the Ariba Network:
● Blanket
● Contingency
● Informatory
The following table maps each line item type between SAP ERP and Ariba Network with a brief description:
Table 1: Supported Service Line Types Mapping Between SAP ERP and Ariba Network
SAP ERP Ariba Network Description
Blanket Amount-Based Describes a service without specifying
quantity. You can create multiple service
sheets and invoices from blanket service
line type.
Note
Quantity for service lines with blanket
line types is 1, by default as per the
standard SAP ERP functionality.
Enhanced SAP Adapter to Support Additional Service Line Types in Service Purchase
Orders © 2016 SAP SE or an SAP affiliate company. All rights reserved. 11

Contingency Contingency Describes a service that is not essential
to perform an order. The value of the
contingency line is included in the total
value of the Bill of Services (BOS) only if
the contingency line item is enabled
while creating a service sheet or an in
voice. This type of service line is disabled
by default in Ariba Network. The contin
gency service line amount is not included
in the net price calculation for the item.
Informatory Information This type of service line is used to pro
vide additional information about any
other service line.
This feature is enabled for all customers. For information about importing the transports, see Importing the
Transports [page 26].
Limitations
● For service purchase orders, SAP ERP does not allow internal line items.
● For service purchase orders with informatory line type, suppliers in Ariba Network cannot create service
sheets and invoices.
This feature is compatible with previous versions of the Ariba Cloud Integration releases.
For more information on service line types, see the Service Line Types section in the Ariba Network Buyer
Administration Guide.
Orders

Technical and Functional Changes for Enhanced SAP
Adapter to Support Additional Service Line Types in
Service Purchase Orders
The following sections explain the technical and functional changes introduced in this release:
Technical Changes [page 13]
Functional Changes [page 14]
cXML [page 14]
Technical Changes
The following sections describe the technical changes for this feature:
SAP ERP Function Module
To extract the service purchase order line type values from SAP ERP, the function module /ARBA/
PO_SERVICE_INFO has been enhanced to include the following field values:
● ESLL_PAUSCH
● ESLL_EVENTUAL
● ESLL_INFORM
Accordingly, the ARBA/ESLL table and the BAdI called from SAP PI have been enhanced to include the following
additional fields:
Table 2: Field Name for the Additional Line Type
Line Type Field Name
Blanket ESLL-PAUSCH
Contingency ESLL-EVENTUAL
Informatory ESLL-INFORM
SAP PI Mapping Changes
Based on the values returned from SAP ERP, extrinsic fields have been added to the cXML structure to populate
the service purchase order line type information.

Related Information
cXML [page 14]
Functional Changes
Previously, the Ariba Network Adapter for SAP NetWeaver supported only the standard line type of service
purchase order.
Now, the Ariba Network Adapter for SAP NetWeaver supports blanket, contingency, and information line types on
purchase orders with planned service hierarchies.
cXML
Following extrinsic fields have been added to the cXML structure to populate the service purchase order line type
information:
Table 3: cXML
Line Type cXML field
Blanket <Extrinsic
name="AmountBasedReceiving">Yes</
Extrinsic>
<Extrinsic
name="HideAmountBasedInfo">Yes</Extrinsic>
Contingency <Extrinsic
name="ContingencyReceiving">Yes</
Extrinsic>
Informatory <Extrinsic
name="InformationReceiving">Yes</
Extrinsic>
The following is an excerpt of a code that shows the new extrinsic AmountBasedReceiving and
HideAmountBasedInfo to support the Blanket line type:
<ItemDetail>
<UnitPrice>
<Money currency="USD">50</Money>
</UnitPrice>
<Description xml:lang="en">bulldozer driverb</Description>
<UnitOfMeasure>HUR</UnitOfMeasure>
<Classification domain="SPSC">foo</Classification>
<ManufacturerPartID>AX4518</ManufacturerPartID>
<ManufacturerName>20008496</ManufacturerName>
<Extrinsic name="AmountBasedReceiving">Yes</Extrinsic>
Orders

<Extrinsic name="HideAmountBasedInfo">Yes</Extrinsic>
</ItemDetail>
The following is an excerpt of a code that shows the new extrinsic ContingencyReceiving to support the
Contingency line type:
<ItemDetail>
<UnitPrice>
</UnitPrice>
<UnitOfMeasure>PK</UnitOfMeasure>
<Classification domain="SPSC">foo</Classification>
<Extrinsic name="ContingencyReceiving">Yes</Extrinsic>
</ItemDetail>
The following is an excerpt of a code that shows the new extrinsic InformationReceiving to support the
Informatory line type:
<ItemDetail>
<UnitPrice>
</UnitPrice>
<UnitOfMeasure>HUR</UnitOfMeasure>
<Classification domain="PK">foo</Classification>
<Extrinsic name="InformationReceiving">Yes</Extrinsic>
</ItemDetail>
Installing and Configuring Enhanced SAP Adapter to
Support Additional Service Line Types in Service
Purchase Orders
Buyers must download and install the new transports to support additional service line types in service purchase
orders between SAP ERP and Ariba Network.
Importing the Transports
Context
You must import the new transports in SAP ERP and the design objects in SAP NetWeaver PI to use the new
functionalities in the Cloud Integration Release 7.0.

Procedure
1. Download the AribaNetworkAdapterSAPNetWeaver_vCI_7_FR.zip file from connect.ariba.com .
2. Import the AribaNetworkAdapterSAPNetweaver.Design.tpz file into your SAP NetWeaver PI.
3. Import the relevant SAP transport requests into your SAP ERP.
Handling Errors
The following section lists the cause and solution for an error condition when sending additional service line type
items in purchase orders with planned service hierarchies from SAP ERP to suppliers on the Ariba Network:
Error Condition: SAP ERP PI mapping fails when the net price of the service purchase order line item is 0 (zero).
Cause: The service purchase order contains only one service line type item either with informatory or contingency
line type. As a result, the net price of the line item is 0 (zero) by default.
Solution: Ensure that the following conditions are met:
● Service purchase order contains at least one blanket line type item in addition to either a informatory or
contingency line type item.
● Net price of the service purchase order line item is not 0 (zero).
Orders

Enhanced SAP Adapter to Support Setting
Spend Limits on Service Sheets with
Unplanned Spend
About Enhanced SAP Adapter to Support Setting Spend Limits on Service Sheets with Unplanned Spend
[page 17]
Functional and Technical Changes for Enhanced SAP Adapter to Support Setting Spend Limits on Service
Sheets with Unplanned Spend [page 19]
Installing and Configuring Enhanced SAP Adapter to Support Setting Spend Limits on Service Sheets with
Unplanned Spend [page 21]
About Enhanced SAP Adapter to Support Setting
Spend Limits on Service Sheets with Unplanned
Spend
and all SAP ERP 6.0 EhP4 and above versions).
The Ariba Network Adapter for SAP NetWeaver sends the overall limit and the expected value as extrinsic fields to
support setting spend limits on service purchase orders with unplanned spend from SAP ERP to Ariba Network.
Unplanned spend on service purchase orders refers to spend on service line items whose nature and scope are not
initially known and the details might not be completely described in the early phase of the procurement process.
Unplanned service lines include a mandatory overall limit (maximum amount) but are otherwise open-ended.
Suppliers performing the service can create service sheets against them up to the overall limit, adding grouped
items under the unplanned service line to describe the specific work they did (service line items) and the material
goods they used (material line items).
The following table describes different field names that identify the service purchase order spend limit in SAP ERP
and Ariba Network:
Enhanced SAP Adapter to Support Setting Spend Limits on Service Sheets with
Unplanned Spend © 2016 SAP SE or an SAP affiliate company. All rights reserved. 17

Table 4: Field Name Mapping Between SAP ERP And Ariba Network
Overall Limit Maximum Amount Specifies the overall limit allowed for the
service item. Additionally, the expected
value or the total amount for a service
line item cannot be greater than the over
all limit.
Note
Although the Ariba Network Adapter
for SAP NetWeaver sends overall limit
to Ariba Network, suppliers can never
see maximum amounts specified for
line items on service purchase orders.
Expected Value Expected Amount Specifies the amount estimated to pro
cure a service item.
Prerequisites
When creating service purchase orders in SAP ERP, ensure that you:
● select the Goods Receipt check box on the Delivery tab. If you do not select the Goods Receipt check box:
○ Acceptance for service sheets cannot be done in SAP ERP.
○ Suppliers cannot create invoices on the Ariba Network for the service purchase orders if the service
sheets were not created on the Ariba Network and its acceptance was not done in SAP ERP.
● specify Expected Value when you select the No Limit check box.
● do not specify a value for the Expected Value that exceeds the Overall Limit.
Limitations
You cannot specify unplanned spend limits individually for each child line item in service purchase orders.
Unplanned Spend

Functional and Technical Changes for Enhanced SAP
Adapter to Support Setting Spend Limits on Service
Sheets with Unplanned Spend
cXML [page 20]
Functional Changes
Previously, when buyers created service purchase orders in SAP ERP, the Ariba Network Adapter for SAP
NetWeaver did not send the overall limit and the expected value for unplanned services to Ariba Network.
In this release, when buyers create service purchase orders in SAP ERP, the Ariba Network Adapter for SAP
NetWeaver sends the overall limit and the expected value as extrinsic fields for unplanned services to Ariba
Network.
The behavior of SAP ERP when buyers create or update service purchase orders with unplanned service line items
is as follows:
● Expected Value (ExpectedUnplanned) is always sent to Ariba Network.
● Overall Limit (MaximumUnplanned) is sent to Ariba Network only if No Limit is not selected.
Technical Changes
The RFC function module /ARBA/PO_ACCOUNTING_INFO has been updated to extract the following fields from
the ESUH table:
● SUMLIMIT: Specifies the overall limit and is mapped to extrinsic ExpectedUnplanned.
● SUMNOLIM: Specifies that there is no limit.
● COMMITMENT: Specifies the expected value and is mapped to the extrinsic MaximumUnplanned.
The existing XSD MM_Custom_ORDERS_ORDERS05_2_CDF_cXML_XSD has been modified to add the Money field
within the Extrinsic node.

The external definition CDF_cXML_XSD in the namespace: http://ariba.com/xi/ASN/CommonBasis has been
updated with the latest XSD from Ariba Network and the following modification has been made to incorporate the
Money field:
<xs:element name="Extrinsic">
<xs:complexType mixed="true">
<xs:sequence>
<xs:element name="Money" minOccurs="0" maxOccurs="1">
<xs:complexType mixed="true">
<xs:attribute name="currency" />
</xs:complexType>
</xs:element>
Note
The curreny information in the Money field is taken from the vendor currency.
cXML
The Ariba Network Adapter for SAP NetWeaver supports sending the following extrinsics added in the
BlanketItemDetail on service purchase orders using cXML version 1.2.028 or higher from SAP ERP to Ariba
Network:
● ExpectedUnplanned
The following is an excerpt of a code that shows the ExpectedUnplanned extrinsic which specifies the
expected value for unplanned line items on the service purchase order:
<Extrinsic name=”ExpectedUnplanned”> <Money currency="USD">50</Money> </
Extrinsic>
● MaximumUnplanned
The following is an excerpt of a code that shows the MaximumUnplanned extrinsic which specifies the overall
limit available for unplanned line items on the service purchase order:
<Extrinsic name=”MaximumUnplanned”> <Money currency="USD">100</Money> </
Extrinsic>
Note
Money is a new field added under extrinsics ExpectedUnplanned and MaximumUnplanned as a child node
with the attribute currency.
Unplanned Spend

Support Setting Spend Limits on Service Sheets
with Unplanned Spend
To enable setting of spend limits on service purchase orders with unplanned spend, buyers must download and
install the new transports in SAP ERP.
Importing the Transports [page 21]
Enabling Support for Setting Spend Limits on Service Sheets with Unplanned Spend [page 22]
Context
Procedure
Next Steps
Enable support for setting spend limits on service sheets with unplanned spend.
Related Information
Enabling Support for Setting Spend Limits on Service Sheets with Unplanned Spend [page 22]

Enabling Support for Setting Spend Limits on Service
Sheets with Unplanned Spend
Context
To support setting spend limits on service purchase orders with unplanned spend, you must create a User Defined
Function (UDF) setParentNode and add it to the purchase order custom map,
MM_Custom_ORDERS_ORDERS05_2_CDF_cXML_XSD.
Note
The cXML XSD is modified to create the Money field containing the Currency attribute under the Extrinsic node
as a child element. Therefore, the Extrinsic node acts as the parent node which requires a special UDF
setParentNode node to populate the string value.
To create the UDF setParentNode, perform the following steps in the SAP NetWeaver PI:
Procedure
1. Open MM_Custom_ORDERS_ORDERS05_2_CDF_cXML_XSD in the edit mode.
2. Create the UDF setParentNode with execution Type as Single Values and with one argument Name as input
3. Add the following code in the UDF:
return Util.setParentWithValue(input, container);
4. From the External Message cXML window, select Request OrderRequest ItemOut
BlanketItemDetail Extrinsic
5. For the UDF setParentNode:
a. Select User defined Functions from the Functions pull-down menu and drag and drop the UDF
setParentNode.
b. From the Source Message, select Request OrderRequest ItemOut BlanketItemDetail
Extrinsic and map it as an input to the UDF setParentNode.
The output of the UDF setParentNode is mapped to the Extrinsic field of the target. The output contains
XML with string values contained within the Extrinsic parent node.
Unplanned Spend

Enhanced SAP Adapter to Support Invoice with
Ship Notice Reference or Receipt Reference
About Enhanced SAP Adapter to Support Invoice with Ship Notice Reference or Receipt Reference [page 23]
Technical and Functional Changes for Enhanced SAP Adapter to Support Invoice with Ship Notice Reference
or Receipt Reference [page 24]
Installing and Configuring Enhanced SAP Adapter to Support Invoice with Ship Notice Reference or Receipt
Reference [page 25]
Handling Errors [page 26]
About Enhanced SAP Adapter to Support Invoice
with Ship Notice Reference or Receipt Reference
and all SAP ERP 6.0 EhP4 and above versions).
The Ariba Network Adapter for SAP NetWeaver maps the cXML message containing ship notice or receipt
reference from Ariba Network to the IDOC format for SAP ERP. Based on the existing SAP ERP functionality, either
a three-way match or a two-way match is performed to validate the incoming invoice in SAP ERP. Invoices sent to
SAP ERP can contain either a reference to a receipt or ship notice.
Prerequisites
You must enable invoice rules on the Ariba Network to use this feature in SAP ERP.
Enhanced SAP Adapter to Support Invoice with Ship Notice Reference or Receipt
Reference © 2016 SAP SE or an SAP affiliate company. All rights reserved. 23

For more information about enabling invoice rules, limitations, and configuration options for the ship notice
feature, see the Require Ship Notices and Configuring Order Confirmation and Ship Notice Rules sections in the
Ariba Network Buyer Administration Guide.
Technical and Functional Changes for Enhanced SAP
Adapter to Support Invoice with Ship Notice
Reference or Receipt Reference
The following sections explain the technical and functional changes introduced in this release:
cXML [page 25]
Technical Changes
Mapping
Mapping for ship notices and receipts in the Ariba Network Adapter for SAP NetWeaver is done in the following:
● MM_CDF_InvoiceDetail_XSD_2_INVOIC_INVOIC02_INVOIC02
● IDOC Type: /ARBA/ INVOIC02
Functional Changes
Previously, Ariba Network Adapter for SAP NetWeaver did not map the invoice cXML message containing ship
notice or receipt reference from Ariba Network to the IDOC format for SAP ERP.
Now, Ariba Network Adapter for SAP NetWeaver maps the invoice cXML message containing ship notice or receipt
reference from Ariba Network to the IDOC format for SAP ERP.
Validation
Ship notice or receipt referenced cXML invoices sent from Ariba Network are validated in SAP ERP as follows:
● Ship notice : The ship notice number is sent in the invoice to SAP ERP and a two-way match is performed in
SAP ERP between the purchase order and ship notice and the invoice is posted in SAP ERP.
Reference

● Receipt: The receipt number is sent in the invoice to SAP ERP and a three-way match is performed based on
standard IV/GR functionality in SAP ERP. Based on the success or failure of the three-way match, the invoice
is either posted or rejected in SAP ERP.
Note
If a receipt is canceled after the invoice is posted in SAP ERP then the invoice in SAP ERP retains a reference to
the canceled receipt.
cXML
The Ariba Network Adapter for SAP NetWeaver supports new extrinsics added in the cXML version 1.2.028 to
support ship notice and receipt references in invoices.
The following is an excerpt of a code that shows the new extrinsic shipNoticeID to support invoices referencing
ship notice:
<InvoiceDetailOrder>
<invoiceDetailShipNoticeInfo>
<ShipNoticeReference shipNoticeID="" shipNoticeDate="">
<DocumentReference payloadID=""/>
</ShipNoticeReference>
</invoiceDetailShipNoticeInfo>
</InvoiceDetailOrder>
The following is an excerpt of a code that shows the new extrinsic receiptID to support invoices referencing
receipt:
<InvoiceDetailOrder>
<InvoiceDetailReceiptInfo>
<ReceiptReference receiptID="" receiptDate="">
<DocumentReference payloadID=""/>
</ReceiptReference>
</InvoiceDetailReceiptInfo>
</InvoiceDetailOrder>
Support Invoice with Ship Notice Reference or
Receipt Reference
Buyers must download and install the new transports to integrate ship notice and receipt data between Ariba
Network and SAP ERP.
Reference © 2016 SAP SE or an SAP affiliate company. All rights reserved. 25

Context
Procedure
Handling Errors
The following section lists the cause and solution for an error condition when the Ariba Network Adapter for SAP
NetWeaver maps the invoice cXML message from Ariba Network to the IDOC format for SAP ERP :
Error Condition: When performing a three-way match for invoice with a ship notice reference, the SAP PI fails to
generate the invoice.
Cause: This occurs if a receipt for the purchase order has not been created in SAP ERP.
Solution: Ensure that the purchase order has a receipt before generating the invoice with a ship notice reference.
Reference

Support for Line Item-level Attachments in
Requests for Quotations
About Support for Line Item-level Attachments in Requests for Quotations [page 27]
Changes to Existing Functionality [page 28]
Installing and Configuring Support for Line Item-Level Attachments in Request for Quotations [page 28]
About Support for Line Item-level Attachments in
Requests for Quotations
This feature, available for buyers using Ariba Network Adapter for SAP NetWeaver, enables buyers to add
attachments to line items in Requests for Quotations. Buyers can add documents that provide additional
information such as product specifications, drawings, and images to each of the line items in a Request for
Quotation.
This feature is supported on SAP ECC 6.0 EhP0 to SAP ECC 6.0 EhP7 versions.
Buyers can add multiple attachments from the Document Management Server (DMS) for each line item in a
Request for Quotation. File types that you can attach at the line level depend on the file types that the DMS
configuration supports.
Buyers can add line item-level attachments while creating (using transaction code ME41) or modifying (using
transaction code ME42) a Request for Quotations.
If the attached file is encrypted or protected with password, Ariba Network does not decrypt the file for the end
user of the attachment. In such cases, buyers that send the encrypted or password-protected attachment to Ariba
Sourcing need to share the required password with suppliers that need to view the attachment.
This feature is enabled for all customers and ready for immediate use.
Prerequisites
● Set up integration between SAP ERP systems and Ariba Sourcing. For more information, see the RFQ and
Award Integration with Ariba Sourcing Guide.
● Ensure that the files that you need to attach at the line-item level of the Request for Quotations are available
on the Document Management Server (DMS).
Support for Line Item-level Attachments in Requests for Quotations © 2016 SAP SE or an SAP affiliate company. All rights reserved. 27

● If you want to attach multiple files on a single-stack instance of SAP NetWeaver PI version 7.4, implement SAP
note number 2002735.
● If you want to attach more than five files on a dual-stack instance of SAP NetWeaver PI, implement SAP note
number 1882948.
Limitations
● The total file size of attachments to a Request for Quotation should not exceed 100 MB. The maximum
payload that Ariba Network supports for a Request for Quotation along with the attachments is 140 MB.
● If you modify or delete a line item-level attachment, you must also update the line item text. Otherwise, the
changes you made to the line item-level attachment do not get updated in the Ariba application.
● Ariba sourcing does not support header-level attachments in change RFQs.
Changes to Existing Functionality
Now, you can add attachments at the line-item level of Request for Quotations. You can add multiple attachments
from the DMS to each of the line item in a Request for Quotations.
Technical Changes
To enable buyers using Ariba Network Adapter for SAP NetWeaver add attachments at the line-item level of
Request for Quotations, the following segments have been added to /ARIBA/RFQ (ORDERS05) IDOC:
● /ARBA/DOCUMENT_ITEM
● /ARBA/HEX_CONTENT_ITEM
Function module /ARBA/RFQ_GET_DETAILS has been modified to support line item-level attachments.
Installing and Configuring Support for Line Item-
Level Attachments in Request for Quotations
The following sections provide information about the steps you need to compete before you can add line item-level
attachments in Requests for Quotations:
Downloading the Mapping Workbook [page 29]
Support for Line Item-level Attachments in Requests for Quotations

Context
You must import the new transports to SAP ERP and the design objects to SAP PI to use the new functionalities in
the Cloud Integration Release 7.0.
Procedure
1. Download the AribaNetworkAdapterSAPNetWeaver_vCI_7_FR.zip file from connect.ariba.com.
2. Import the AribaNetworkAdapterSAPNetweaver.Design.tpz file into SAP NetWeaver PI.
3. Import the relevant SAP transport requests into SAP ERP.
Downloading the Mapping Workbook
Context
You must download the new mappings for the SAP ERP system.
Procedure
1. Go to http://connect.ariba.com and log in.
2. Click Ariba Connect for On-Demand Solutions.
3. Click Ariba Network Adapters.
4. Click Ariba Network Adapter for SAP NetWeaver.
5. Under Integration Tools section, click Data Transformation.
The mapping workbooks for all transactions are available in a ZIP file.
Support for Line Item-level Attachments in Requests for Quotations © 2016 SAP SE or an SAP affiliate company. All rights reserved. 29

Enhancements to Fieldglass Master Data
Integration
About Enhancements to Fieldglass Master Data Integration [page 30]
Technical and Functional Changes [page 31]
Installing and Configuring Enhancements to Fieldglass Master Data Integration [page 34]
About Enhancements to Fieldglass Master Data
Integration
This feature, available for buyers using Ariba Procurement Solutions integrated with SAP, enables buyers to
import additional master data elements from SAP ERP 6.0 EhP0 and higher to Fieldglass.
Ariba Cloud Integration release 7.0 extends the Fieldglass master data integration support to the following master
data elements:
● Purchase Group
● Internal Order
● General Ledger
● Asset
● Account Category
● AccCategory Field Status
● ERP Commodity Code
● Currency Conversion
● Tax Code
Fieldglass uses custom field mappings for each of these master data elements from SAP ERP systems. You must
create custom field mappings in Fieldglass before you can export master data for these elements.
Fieldglass master data integration supports only the full load mode of data extraction. A full load data extraction
copies all records in the SAP ERP system to Fieldglass every time you export master data from SAP to Fieldglass.
This feature is enabled for all customers and ready for immediate use.
For information about importing the transports, see Importing the Transports [page 29].
Enhancements to Fieldglass Master Data Integration

Prerequisites
● To be able to set up master data export from SAP ERP to Fieldglass, you must download the latest Ariba
Procurement Adapter for SAP, install the latest transports for Fieldglass integration, and set up a direct or an
intermediate connection. For more information about downloading the Ariba Procurement Adapter for SAP
and installing transports, see the Procurement Solutions Integration Guide for SAP.
● To be able to set up master data export from SAP ERP to Fieldglass, you must maintain the following
parameters in the /ARBA/TVARV table:
○ /ARBA/FG_USERNAME. Contains the username for Fieldglass authentication.
○ /ARBA/FG_LICENCEKEY. Contains the password for Fieldglass authentication.
● To be able to export master data elements that require custom mapping in Fieldglass, you must define the
custom mapping in Fieldglass.
● To be able to retrieve currency conversion data, you must set /ARBA/CURR_CONV_BANK_RATE and /ARBA/
CURR_CONV_DAYS_PAST parameters to appropriate values. For more information about setting the currency
conversion data, see Ariba Procurement Solutions Integration Guide for SAP.
Technical and Functional Changes
The following sections explain the technical and functional changes introduced in this release.
Technical Changes
New function modules have been added to the /ARBA/MASTER_DATA_EXPORT program to support extraction of
additional master data elements. The function modules map to the master data elements and extract the master
data that correspond to the master data element checkboxes that you selected on the Fieldglass tab.
You must maintain the following parameters to authenticate the Fieldglass and SAP ERP system:
● /ARBA/FG_LICENCEKEY
● /ARBA/FG_USERNAME
For more information, see Authenticating Fieldglass and SAP ERP [page 34].
The following table lists the newly-added master data events, function modules, and the corresponding CSV files.
Table 5: Master Data Events, Function Modules, and CSV Files
Master Data Event Function Module CSV File
Purchase Group /ARBA/PURCHASE_GROUP_EXPORT PurchaseGroup.csv
Internal Order /ARBA/INTERNAL_ORDER_EXPORT InternalOrder.csv
Enhancements to Fieldglass Master Data Integration © 2016 SAP SE or an SAP affiliate company. All rights reserved. 31

Master Data Event Function Module CSV File
General Ledger /ARBA/GENERAL_LEDGER_EXPORT GeneralLedger.csv
Asset /ARBA/ASSET_EXPORT Asset.csv
Account Category /ARBA/ACCOUNT_CATEGORY_EXPORT AccountCategory.csv
AcctCategory Field Status /ARBA/ACCOUNT_FIELD_EXPORT AccCategoryFieldStatusCombo.csv
Currency Conversion /ARBA/CURRENCY_CONVERT_EXPORT CurrencyConversionRate.csv
Tax Code /ARBA/TAX_CODE_EXPORT TaxCode.csv
ERP Commodity Code /ARBA/MATERIAL_GROUP_EXPORT ERPCommodityCode.csv
To support the additional master data elements, a new WSDL has been introduced. The new WSDL replaces the
WSDL used in previous versions.
To support additional master data elements, the following new interfaces have been added to the /ARBA/
MASTER_DATA BAdI:
● PUBLISH_PURCHASE_ORGANIZATION
● PUBLISH_ACCOUNT_CATEGORY
● PUBLISH_ACCOUNT_FIELD
● PUBLISH_ASSET
● PUBLISH_GENERAL_LEDGER
● PUBLISH_INTERNAL_ORDER
● PUBLISH_MATERIAL_GROUP
● PUBLISH_CURRENCY_CONVERSION
● PUBLISH_TAX_CODE
A new importing parameter Solution has been added to the interfaces in the /ARBA/MASTER_DATA BAdI.
Functional Changes
Previously, you could export only the following master data elements from SAP ERP systems to Fieldglass:
● Purchasing Organization
● Company Code
● Plant
● Cost Centre and WBS Elements
● User
In this release, you can export the following additional master data elements from SAP ERP system to Fieldglass:
● Purchase Group
● Internal Order
● General Ledger

● Asset
● Account Category
● Accout Category Field Status
● ERP Commodity Code
● Currency Conversion
● Tax Code
Note
Some of these data elements might not be relevant to your implementation. Your Fieldglass Service Consultant
might be able to help you identify the elements that are relevant to the implementation.
Each of the function modules creates a CSV file to save the corresponding master data extracted from the SAP
ERP system. In mediated and direct connectivity setups, the data extraction is transparent to the users. However,
in the Ariba Integration Toolkit (ITK) setups, the extracted master data are stored as CSV files to the location you
specified.
Administrator Interface Changes [page 33]
Administrator Interface Changes
Additional master data groups and checkboxes have been added to the Fieldglass tab of the SAP user interface for
master data export. On the Fieldglass tab, checkboxes are arranged in groups that represent the type of master
data the corresponding master data elements belong to.
The following table lists the master data groups and the newly-added checkboxes in each of these groups on the
Fieldglass tab.
Table 6: Master Data Groups and Checkboxes
Master Data Groups Master Data Element Checkboxes
Organization Data Purchase Group
Accounting Data Internal Order
Accounting Data General Ledger
Accounting Data Asset
Cross, Application Configuration Data Account Category
Cross, Application Configuration Data Account Category Field Status
Cross, Application Configuration Data ERP Commodity Code
Cross, Application Configuration Data Currency Conversion
Cross, Application Configuration Data Tax Code
Apart from the checkboxes listed in the preceding table, the Fieldglass tab also contains the following master data
element checkboxes:

● Purchasing Organization, Company Code, and Plant in the Organization Data group.
● Cost Center. Previously, this was part of the Organizational Data group. Currently, this is part of the
Accounting Data group.
● User. Previously, this was part of the Organizational Data group. Currently, this is a standalone checkbox in
the User group.
Installing and Configuring Enhancements to
Fieldglass Master Data Integration
Authenticating Fieldglass and SAP ERP [page 34]
Context
You must import the new transports to SAP ERP and the design objects to SAP PI to use the new functionalities in
the Cloud Integration Release 7.0.
Procedure
1. Download the AribaNetworkAdapterSAPNetWeaver_vCI_7_FR.zip file from connect.ariba.com.
2. Import the AribaNetworkAdapterSAPNetweaver.Design.tpz file into SAP NetWeaver PI.
3. Import the relevant SAP transport requests into SAP ERP.
Authenticating Fieldglass and SAP ERP
Context
Maintain the following parameters to authenticate Fieldglass and SAP ERP applications.

Procedure
1. Run transaction SM30.
2. Open the Maintain Table Views initial screen, enter /ARBA/TVARV in the Table/View field, and click Maintain.
3. Select Edit New Entries , or click the New Entries button.
4. Maintain the following parameters in the screen that appears:
○ Variable Name:/ARBA/FG_LICENCEKEY
○ Selection cat.:P
○ Number: 0
○ INCL/EXCL: I
○ Option: EQ
○ Selection value: Enter the license key for the Fieldglass application.
○ Variable Name:/ARBA/FG_USERNAME
○ Selection cat.:P
○ Number: 0
○ INCL/EXCL: I
○ Option: EQ
○ Selection value: Enter the user name for the Fieldglass application.
5. To save your changes, select Table View Save .

Integration of Master Data from SAP ERP with
Ariba Sourcing and Ariba Contract
Management
About Integration of Master Data from SAP ERP with Ariba Sourcing and Ariba Contract Management [page
36]
Functional and Technical Changes [page 38]
Installing and Configuring Integration of Master Data from SAP ERP with Ariba Sourcing and Ariba Contract
Management [page 40]
About Integration of Master Data from SAP ERP with
Ariba Sourcing and Ariba Contract Management
This feature, available for buyers using Ariba Procurement Solutions integrated with SAP ERP, enables buyers to
export master data from SAP ERP to Ariba Sourcing and Ariba Contract Management. The master data elements
that buyers can export include organizational data, cross application data, and material master data.
You can export master data from SAP ERP to Ariba Sourcing and Ariba Contract Management over Direct or
Mediated Connectivity setups. You can export the materail master data in the full load mode or in the incremental
load mode. An incremental load export of the material master data includes material master data that has one or
more of the following values updated since the last material master export event:
● Material Group
● Base Unit of Measure
● Order Unit of Measure
● Description
● Language Key
● Material Plant Association
The incremental updates also contain information about any material master data that has been marked for
delete.
Tip
Material master data contains large volume of information. For best performance, always set filters that specify
the criteria based on which you can export smaller subsets.
The following table lists the master data groups and corresponding master data elements:
Management

Table 7: Master Data Groups and Elements
Master Data Group Master Data Element
Organizational Data Plant
Organizational Data PurchaseGroup
Organizational Data PurchaseOrg
Organizational Data PlantPurchaseOrg
Organizational Data CompanyCode
Cross Application Configuration Data PaymentTerms
Cross Application Configuration Data IncoTerms
Material Master Material Master
Material Master Item Category
Material Master ERPCommodityCode (Material Group)
When you export material master data, you also receive material master plant association data and material
master language associations data. Similarly, for Incoterms, you receive the Incoterms language association data
along with the Incoterms master data.
Every time you export the master data to Ariba Sourcing or Ariba Contract Management, the SAP ERP system
sends a copy of the schema file, which contains the ERP metadata information related to the master data extracts,
along with the master data.
This feature is enabled for all customers. For information about configuring the feature, see Installing and
Configuring Integration of Master Data from SAP ERP with Ariba Sourcing and Ariba Contract Management [page
40].
Prerequisites
● You must install the latest transports.
Limitations
Cloud Integration release 7.0 does not support Integration Tool Kit (ITK)-based connection for exporting master
data from SAP ERP systems to Ariba Sourcing and Ariba Contract Management.
Management © 2016 SAP SE or an SAP affiliate company. All rights reserved. 37

Functional and Technical Changes
The following sections provide information about functional and technical changes for the integration of master
data from SAP ERP with Ariba Sourcing and Contract Management.
Functional Changes
Previous releases of Cloud Integration did not support the master data integration between SAP ERP and Ariba
Sourcing or Ariba Contract Management.
Now, Cloud Integration supports the integration of master data from SAP ERP with Ariba Sourcing and Contract
Management. Buyers can now export master data from SAP ERP systems to Ariba Sourcing and Ariba Contract
Management.
Administrator Interface Changes
The following changes have been made to the administrator interface:
● A new option button Sourcing and Contracts has been added under Scope of Procurement Solution.
● The following master data options have been added:
Category Check Boxes
Organizational Data Plant
PurchaseOrg
PlantPurchaseOrg
Company Code
PurchaseGroup
Cross/Application Configuration Data Payment Terms
Incoterms
Material Master Material Master
Item Category
ERPCommodityCode
Management

Technical Changes
Methods
The following new methods have been added to the /ARBA/CL_MASTERDATA_EXPORT class:
● FETCH_MATERIALMASTER
● FETCH_INCOTERMS
● FETCH_ITEMCATEGORY
● WRITE_SCHEMA_FILE
● GET_SCHEMA
● GET_FIELDMAP_ENTRIES
Function Modules
The following function modules have been added:
● /ARBA/PLANT_EXPORT
● /ARBA/PURCHASE_ORG_EXPORT
● /ARBA/PURCHASE_GROUP_EXPORT
● /ARBA/PLANT_PURCHASE_EXPORT
● /ARBA/COMPANY_CODE_EXPORT
● /ARBA/PAYMENTTERM_EXPORT
● /ARBA/MATERIAL_GROUP_EXPORT
BAdI
The following methods have been added to the BAdI, /ARBA/MASTER_DATA:
● PUBLISH_PLANT
● PUBLISH_PURCHASE_ORGANIZATION
● PUBLISH_COMPANYCODE
● PUBLISH_PURCHASE_GROUP
● PUBLISH_PLANT_PURCHASE_ORG
● PUBLISH_PAYMENT_TERMS
● PUBLISH_INCOTERMS
● PUBLISH_MATERIALMASTER
● PUBLISH_ITEMCATEGORY
● PUBLISH_MATERIAL_GROUP

Installing and Configuring Integration of Master
Data from SAP ERP with Ariba Sourcing and Ariba
Contract Management
Configuring Integration of Master Data from SAP ERP with Ariba Sourcing and Ariba Contract Management
[page 40]
Context
You must download the latest version of the Ariba sourcing transports to use the new features in an Ariba Cloud
Integration release.
Procedure
1. On the Home tab of connect.ariba.com , go to Product Summary On-Demand and click Ariba
Sourcing or Ariba Supplier Information and Performance Management.
The Ariba Supplier Information and Performance Management page appears.
2. On the Resources tab, click ABAP Transports for SAP ERP. If the list does not contain this entry, contact your
Ariba account executive.
The Sourcing SAP Transports page appears.
3. Click Download and save the Ariba_Sourcing_SAP_Transports_V_CI_7.zip package.
4. Extract the contents of the ZIP file and import the transports to SAP ERP.
Configuring Integration of Master Data from SAP ERP with
Ariba Sourcing and Ariba Contract Management
Prerequisites
● Install the latest transports.
● Maintain the /ARBA/EXTERNAL_SID parameter in the /ARBA/TVARV table. The value you set for /ARBA/
EXTERNAL_SID should match the system ID you configured in the Master Data Manager External
System Configuration panel of the Ariba application.
Management

Context
You can integrate master data from SAP ERP systems with Ariba Sourcing and Ariba Contracts Management.
Procedure
1. Set up Direct Connectivity between the Ariba application and SAP ERP system.
○ If you are using ECC 6.0 EhP 3 or lower versions, use the LPCONFIG transaction. For more information
about the LPCONFIG settings, see the Configuring the LPCONFIG for ECC6.0 EHP3 section in the Ariba
Procurement Solutions Integration Guide for SAP.
○ If you are using ECC 6.0 EhP 4 or higher versions, use the SOAMANAGER transaction. For more
information about the LPCONFIG settings, see the Configuring the SOAMANAGER for ECC 6.0 EHP5
Systems section in the Ariba Procurement Solutions Integration Guide for SAP.
2. Go to the transaction code sm30 and configure the following parameters in the /ARBA/AUTH_PARAM table:
○ Solution. The Ariba application that you want to integrate the master data with.
○ Realm. The name of your company as configured in the Ariba application.
○ Wait. Number of minutes to wait before the SAP ERP system attempts to reconnect with the Ariba
application.
3. Go to the transaction code sm30 and specify the filtering criteria for the following variables in the /ARBA/
TVARV table:
Tip
Material master data contains large volume of information. For best performance, always set filters such
as /ARBA/SPLIT_NOMREC that specify the criteria based on which smaller subsets are exported.
○ /ARBA/MATERIAL_MASTER_EXPORT
○ /ARBA/MATERIAL_LANG_EXPORT
○ /ARBA/MATERIAL_ONLY_INFO
○ /ARBA/INCOTERMS_EXPORT
○ /ARBA/SPLIT_NOMREC. Specify the number of records you need to export in a batch. The recommended
value for this parameter is 40,000 records.
○ /ARBA/DC_WAITTIME. Specify the number of seconds that SAP ERP should wait between two Direct
Connectivity calls to the Ariba application. The default value is one second. This parameter is important
when the export contains multiple batches of records based on the /ARBA/SPLIT_NOMREC configuration.
4. Go to the ARBA/MASTER_DATA_EXPORT program. Alternatively, you can enter the transaction code /ARBA/
MASTER_DATA.
The Master Data Export interface appears.
5. From the Scope of Procurement Solution options, Select Contracts and Sourcing.
6. Select one of the following under the Load Options:
○ Full Load
○ Incremental Load. You can export only material master data in the incremental load setting..

7. If you selected the Full Load option in the previous step, select one or more of the following master data
elements:
○ Plant
○ PurchaseOrg
○ CompanyCode
○ PurchaseGroup
○ PlantPurchaseOrg
○ Payment Terms
○ IncoTerms
○ Material Master
○ ItemCategory
○ ERPCommodityCode
Note
If you selected the Incremental Load option in the previous step, only the Material Master option is
available for selection.
8. To export the selected master data, execute the program.
Management

Integration of Supplier Information and
Performance Management with SAP ERP
through MDG-S
About Integration of Ariba Supplier Information and Performance Management with SAP ERP through MDG-S
[page 43]
Maintaining Supplier User Login ID Information on SAP ERP [page 46]
Maintaining Vendor ID Mapping [page 46]
Functional and Technical Changes for SIPM integration with SAP ERP through MDG-S [page 47]
Installing and Configuring Integration of SIPM with SAP ERP through MDG-S [page 53]
Viewing Vendor ID and Business Partner Mappings [page 62]
Viewing Error Logs [page 63]
About Integration of Ariba Supplier Information and
Performance Management with SAP ERP through
MDG-S
This feature enables buyers using Ariba Supplier Information and Performance Management to integrate supplier
master data between Ariba Supplier Information and Performance Management and SAP ERP. The supplier
master data integration uses the SAP Business Partner integration services and supports integration between
Ariba Supplier Information and Performance Management and SAP ERP through Master Data Governance for
Suppliers (MDG-S).
Ariba Supplier Information and Performance Management uses the interfaces provided by SAP MDG Application
Foundation to integrate supplier data with SAP ERP. SAP MDG Application Foundation can be enabled only on SAP
ERP 6.0 EhP 6 and later versions.
You can use one of the following integration methods to integrate Ariba Supplier Information and Performance
Management with SAP ERP through MDG-S:
● Direct Connectivity
● Mediated Connectivity through SAP NetWeaver PI
The Ariba Supplier Information and Performance Management integration with SAP ERP is bidirectional. You can
export supplier master data from SAP ERP to Ariba Supplier Information and Performance Management
(outbound) and import supplier master data from Ariba Supplier Information and Performance Management to
SAP ERP (inbound).
When you export the supplier data from SAP ERP to Ariba Supplier Information and Performance Management for
the first time, you can use the full load option. For the outbound full load integration, you can use the SAP Data
Replication Framework (DRF). The transaction code DRFOUT enables you to access the data replication
transaction. For subsequent outbound integration events, you can use the incremental load option.
Integration of Supplier Information and Performance Management with SAP ERP
through MDG-S © 2016 SAP SE or an SAP affiliate company. All rights reserved. 43

You can use either SAP area menu items or the transaction codes to access transactions for supplier data
integration. To access the area menu, go to /n/ARBA/SIPM.
The following table lists the area menus and transaction codes codes that you can use for exporting and importing
of supplier master data and retrieving the status of master data export:
Table 8: Area Menu and Transaction Codes for Supplier Master Data Export and Import
Area Menu Transaction Code Description
DRFOUT Enables you to export the supplier master data from SAP ERP
to Ariba Supplier Information and Performance Management
in the full load mode.
SAP Menu Integration
from SAP to SIPM Reports
Integrate Suppliers to
SIPM
/n/ARBA/SIPM_OUT Enables you to export the supplier master data from SAP ERP
to Ariba Supplier Information and Performance Management
in the incremental load mode.
from SIPM to SAP Reports
Integrate Suppliers to
SAP
/n/ARBA/SIPM_IN Enables you to import the supplier master data from Ariba
Supplier Information and Performance Management to SAP
ERP in the incremental load mode.
from SAP to SIPM Reports
Download Confirmation
from SIM
/n/ARBA/SIPM_CONF Enables you to retrieve the status of supplier master data ex
port from SAP ERP to Ariba Supper Information and Perform
ance Management.
Tip
If you need to download the CSV files locally, you can select the Test Run option that is available for the
incremental load integration.
If a supplier is deleted in Ariba Supplier Information and Performance Management, the corresponding records in
SAP ERP are marked as deleted. Similarly, when a supplier is marked as deleted in SAP ERP, the corresponding
records are marked as inactive and sent to Ariba Supplier Information and Performance Management in the next
export. However, blocking of a supplier is supported only in SAP ERP. Though Ariba Supplier Information and
Performance Management sets a flag to indicate that a supplier is blocked, it does not block the supplier from
transacting on Ariba Supplier Information and Performance Management.
Enabling this Feature
This feature is disabled by default. To enable this feature, please have your Designated Support Contact log a
service request. An Ariba Customer Support representative will follow up to complete the request.
Note that Support for this feature will be made available only as part of the upcoming Ariba Application 2016
release. Contact your Ariba Account Manager for more information on integration services.
through MDG-S

For information about how to configure this feature, see Installing and Configuring Integration of SIPM with SAP
ERP through MDG-S [page 53].
Prerequisites
You must implement the prerequisites in the following order:
1. Ensure that your ERP system is SAP ERP 6.0 EhP 6 and above.
2. You must enable the business functions in Master Data Governance for Suppliers. For more information, see
the Configuring Master Data Governance for Supplier guide on the SAP Help portal.
3. Implement the following SAP notes in the order the notes are listed here:
1. 1750821 (Not required if you are using SAP ERP 6.0 EhP 7.)
2. 1974397
3. 1912305
4. 2211045
5. 2274626
4. You must import the latest Ariba sourcing transports.
5. Activate the /ARBA/SIPM replication model. You can activate /ARBA/SIPM from the DRFIMG transaction. For
more information, see Activating the Replication Model [page 56].
6. Implement implicit enhancement in SAP ERP. For more information, see Configuring Implicit Enhancement for
the Integration of Ariba Supplier Information and Performance Management with SAP ERP [page 56]
7. Maintain value mappings for region code and language in the /ARBA/VALUE_MAP table. For more information,
see Configuring the Integration of Ariba Supplier Information and Performance Management with SAP ERP
through MDG-S [page 54].
8. Supplier records in Ariba Supplier Information and Performance Managmente should be marked as "Supplier
Integration Enabled" before you can import those records to SAP ERP.
Limitations
● Integration of Ariba Supplier Information and Performance Management with SAP ERP is not supported over
Ariba Integration Tool Kit.
● Purchase organization, company code, and bank data from SAP ERP are not exported to Ariba Supplier
Information and Performance Management.
● If a supplier organization does not have any users associated with that, such supplier organizations cannot be
integrated with SAP ERP.
● Only one address is supported per supplier.
● Ariba Supplier Information and Performance Management send the full name to SAP ERP. SAP ERP splits the
full name that is received from Ariba Supplier Information and Performance Management into first name and
last name. SAP ERP assigns the part before the first space in the name as the first name and the rest as the
last name. If the first or last name exceeds 35 characters, Ariba Supplier Information and Performance
Management truncates the name by cutting the characters after the maximum allowed limit of 35 characters.
● Supplier data integration between SAP ERP and Ariba Supplier Information and Performance Management
does not occur in real time. Integration events occur at scheduled intervals. Between two integration events,
the supplier data in SAP ERP and Ariba Supplier Information and Performance Management might not be

synchronized. You must check the last integration event and ensure that the data is synchronized before you
trigger a transaction, such as raising a purchase order. For example, a purchase order from SAP ERP might
contain an outdated address or contact if a supplier record in Ariba Supplier Information and Performance
Management has been modified after the last integration event.
● Ensure that you do not enter more than ten characters while creating the Login ID for users on the Ariba
Supplier Information and Performance Management. MDG-S supports only ten characters in the reference
fields.
Maintaining Supplier User Login ID Information on
SAP ERP
You can maintain contact information for suppliers on the SAP ERP system. SAP ERP sends this contact
information as “supplier users” to Ariba Supplier Information and Performance Management. Users in Ariba
Supplier Information and Performance Management must have a unique login ID to log in to Ariba Supplier
Information and Performance Management. You can choose to maintain custom login ID for users. To do so,
maintain the Login ID for users in the /ARBA/USERID table. Ariba uses this Login ID while importing and exporting
the supplier information for users.
If you do not maintain the Login ID for users in the /ARBA/USERID table, Ariba uses the Business Partner or MDGS
ID for the contact person as the Login ID while sending the supplier information to Ariba Supplier Information and
Performance Management.
When Ariba Supplier Information and Performance Management sends the supplier information to SAP ERP, Ariba
updates the Login ID that is being sent from Ariba Supplier Information and Performance Management in the/
ARBA/USERID table on the SAP ERP system .
Related Information
Maintaining Supplier User Login IDs on SAP ERP [page 57]
Maintaining Vendor ID Mapping
You can use the /ARBA/SYSTID_MAP table to maintain a mapping between the Ariba System ID and the SAP ERP
vendor ID.
When you create a new supplier in SAP ERP, SAP ERP assigns a vendor ID to the supplier. Similarly, when you
create a supplier in an Ariba application, Ariba assigns an Ariba System ID to the supplier.
When you integrate supplier data for a vendor created in SAP ERP with Ariba Supplier Information and
Performance Management, the vendor ID that was assigned by SAP ERP is used as the Ariba System ID. However,
when a supplier created in Ariba Supplier Information and Performance Management is integrated with SAP ERP,
SAP ERP assigns a Vendor ID that is different from the Ariba System ID.
through MDG-S

Because Ariba Supplier Information and Performance Management and SAP ERP use different identifiers for
suppliers created in the Ariba application, a mapping between these two values enables SAP ERP to identify a
supplier when Ariba Supplier Information and Performance Management sends any update to a supplier record
that already a corresponding record in SAP ERP.
It is important that you maintain this mapping in SAP ERP for all supplier records that are in Ariba Supplier
Information and Performance Management before you do the first full-load export from SAP ERP. If you do not
maintain the mapping, SAP ERP creates duplicate records for the existing entries that have Ariba System ID that is
different from the Vendor ID.
Subsequently, the mapping gets updated everytime you do a supplier data import to SAP ERP.
Related Information
Maintaining Ariba System ID and Vendor ID Mapping [page 58]
Functional and Technical Changes for SIPM
integration with SAP ERP through MDG-S
This topic contains the following sections:
Functional Changes for Supplier Information and Performance Management Integration with SAP ERP through
MDG-S [page 47]
Technical Changes for Ariba Supplier Information and Performance Management Integration with SAP ERP
through MDG-S [page 50]
Functional Changes for Supplier Information and
Performance Management Integration with SAP ERP
through MDG-S
You can now integrate Ariba Supplier Information and Performance Management with SAP ERP through Master
Data Governance for Supplier (MDG-S). Integration of Ariba Supplier Information and Performance Management
with SAP ERP provides the following functionalities:
● Bidirectional integration of supplier data between Ariba Supplier Information and Performance Management
and SAP ERP.
● Full load export of supplier data from SAP ERP to Ariba Supplier Information and Performance Management.
● Incremental export of supplier data from SAP ERP to Ariba Supplier Information and Performance
Management.
● Incremental import of supplier data from Ariba Supplier Information and Performance Management to SAP
ERP.
● Ability to check the status of supplier data integration.

● Test Run option to locally download the CSV files.
● Error logging.
Administrative Interface Changes for Ariba Supplier Information and Performance Management Integration
with SAP ERP through MDG-S [page 48]
CSV Files for Ariba Supplier Information and Performance Management Integration with SAP ERP [page 48]
Administrative Interface Changes for Ariba Supplier Information
and Performance Management Integration with SAP ERP through
MDG-S
The new transaction code /ARBA/SIPM_IN launches a new screen that has the following options:
● Test Run
● Download from SIPM
The new transaction code /ARBA/SIPM_OUT launches a new screen that has the following options:
● Test Run
● Upload from SAP to SIPM
The new transaction code /ARBA/SIPM_CONF launches a new screen that has the following options:
● Test Run
● Call Confirmation In
CSV Files for Ariba Supplier Information and Performance
Management Integration with SAP ERP
Cloud Integration release 7.0 generates CSV files, which are listed in this section, to transfer supplier data between
SAP ERP and Ariba Supplier Information and Performance Management and to confirm the status of supplier
master data export and import.
A mapping of fields in SAP ERP and Ariba Supplier Information and Performance Management is maintained in
the /ARBA/FIELD_MAP table. The /ARBA/FIELD_MAP table contains the following structures under solution SIPM:
● /ARBA/SUPPLIER_INFO
● /ARBA/CONTACT_INFO
● /ARBA/SIPM_IDNUMBERS
● /ARBA/SIPM_ERRORS
Suppliers.CSV
The Suppliers.CSV file contains the following fields:
through MDG-S

● VendorID
● SystemID
● MDG ID
● NetworkID
● DUNS
● CustomDomainName
● CustomDomainValue
● Active
● Blocked
● Blocked Reason
● Name1
● Name2
● Name3
● Name4
● AddressID
● Street
● City
● Country
● State
● PostalCode
● Language
● CorporateEmailAddress
● CorporateFax
● CorporatePhone
● CorporateURL
● Legal Name
● State of Incorporation
● Global Location Number
● Tax ID
● State Tax ID
● Regional Tax ID
● VAT ID
Users.CSV
The Users.CSV file contains the following fields:
● CSV Column
● VendorID
● SystemID
● MDGID
● Active
● Name
● IsEmailInviteNeeded

● IsUserApproved
● Email Address
● Phone Number
● Fax
SuccessConfirmation.CSV
The SuccessConfirmation.CSV file contains the following fields:
● VendorID
● SystemID
● MDGID
● LoginID
Errors.CSV
The Errors.CSV file contains the following fields:
● LoginID
● MDGID
● MessageId
● MessageNum
● MessageText
● MessageType
● SystemID
● VendorID
Technical Changes for Ariba Supplier Information and
Performance Management Integration with SAP ERP
through MDG-S
The following technical changes have been introduced to support the Ariba Supplier Information and Performance
Management integration with SAP ERP through Master Data Governance for Suppliers (MDG-S).
Proxies
To support direct and mediated connectivity, the following new proxies have been added:
● /ARBA/CO_SI_SOURCING_UPLOAD for outbound connections.
through MDG-S

● /ARBA/CO_SI_SOURCING_DOWNLOAD for inbound connections.
Transaction Codes
The following new transaction codes have been added:
● /ARBA/SIPM_IN. To import incremental updates to supplier data from Ariba Supplier Information and
Performance Management to SAP ERP.
● /ARBA/SIPM_OUT. To export incremental updates to supplier data from SAP ERP to Ariba Supplier
● /ARBA/SIPM_CONF.To receive the status of supplier master data export from SAP ERP to Ariba Supplier
Packages, Programs, and Classes
● A new package, /ARBA/MD_SUPPLIER_SIPM has been added.
● The following new programs have been added:
○ /ARBA/CR_MD_SUPPLIER_SIPM_IN. To process the inbound incremental updates.
○ /ARBA/CR_SUPPLIER_SIPM_OUT. To process the outbound incremental updates.
○ /ARBA/CR_SUPPLIER_SIPM_CONF_IN. To process the status checking of outbound updates.
● The following new classes have been added:
○ /ARBA/CL_MDG_SUPPLIER. For Ariba Supplier Information and Performance Management integration
with SAP ERP.
○ /ARBA/CL_MDG_BP_REPLICATE_DRF. For outbound integration.
○ /ARBA/CL_MDG_BP_RPLCTRQ. For inbound integration.
Structures
The following new structures have been added:
● /ARBA/SUPPLIER_INFO. To maintain the fields for supplier information captured in the Suppliers.CSV file.
● /ARBA/CONTACT_INFO. To maintain the fields for contact or user information captured in the Users.CSV file.
● /ARBA/SIPM_IDNUMBERS. To maintain the fields for success confirmation information captured in the
SuccessConfirmation.CSV file.
● /ARBA/SIPM_ERROR. To maintain the fields for error messages captured in the Errors.CSV file.
BAdIs
The following new BAdIs have been added:

● /ARBA/SIPM_OUTBOUND
This BAdI enables you to enhance the Supplier.CSV and Contacts.CSV structures.
○ You can use the following code to modify the Supplier.CSV structure:
** Enhancement to change Suppliers.CSV structure
GET BADI go_badi_out.
IF go_badi_out IS BOUND.
CALL BADI go_badi_out->create_supplier_csv
EXPORTING
et_bupa_msg = lt_proxy_data
CHANGING
et_csv_out = gt_csv_out.
ENDIF.
○ You can use the following code to modify the CONTACT_INFO (for Users.CSV) structure:
** Enhancement to change contacts.csv structure
GET BADI lo_badi_out.
IF lo_badi_out IS BOUND.
CALL BADI lo_badi_out->create_contacts_csv
EXPORTING
et_csv_out = lt_csv_out
et_relshp_msg = et_relshp_msg
CHANGING
et_csv_out_contact = lt_con_out.
ENDIF.
● /ARBA/SUPPLIER_SIPM_IN
This BAdI enables you to modify the error and ID number structures and to map additional suppliers and
○ You can use the following code to modify the error and ID number structures:
*Enhancement to change error and id number structures.
GET BADI go_badi.
IF go_badi IS BOUND.
CALL BADI go_badi->call_proxy_in
EXPORTING
it_vendor = gt_vendor
it_contact = gt_contact
CHANGING
et_error = gt_error
et_idnumbers = gt_idnumbers.
ENDIF.
○ You can use the following code to map additional contact information:
*Enhancement to map additional contact information
CALL BADI go_badi->map_contactpersons_to_proxy
EXPORTING
it_contact = it_contact
it_vendor = it_vendor
CHANGING
ct_business_partner_suiterepli = lt_business_partner_suiterepli.
ENDIF.
○ You can use the following code to map additional supplier information:
*Enhancement to map additional supplier information
CALL BADI go_badi->map_vendors_to_proxy
EXPORTING
iw_vendor = gw_vendor
CHANGING
cw_business_partner_suiterepli = gw_business_partner_suiterepli.
through MDG-S

ENDIF.
Logs
The following object and subobject have been added for error logging:
● Object: /ARBA/SIPM
● Subobject: /ARBA/SUB_SIPM
Installing and Configuring Integration of SIPM with
SAP ERP through MDG-S
This topic contains the following sections:
Configuring the Integration of Ariba Supplier Information and Performance Management with SAP ERP
through MDG-S [page 54]
Exporting Supplier Master Data from SAP ERP to Ariba Supplier Information and Performance Management in
the Full Load Mode [page 58]
Exporting Supplier Master Data from SAP ERP to Ariba Supplier Information and Performance Management in
the Incremental Mode [page 60]
Checking the Status of Outbound Supplier Master Data Integration [page 61]
Importing Supplier Master Data from Ariba Supplier Information and Performance Management to SAP ERP
[page 61]
Context
You must download the latest version of the Ariba sourcing transports to use the new features in an Ariba Cloud
Integration release.
Procedure
1. On the Home tab of connect.ariba.com , go to Product Summary On-Demand and click Ariba
Sourcing or Ariba Supplier Information and Performance Management.
The Ariba Supplier Information and Performance Management page appears.

2. On the Resources tab, click ABAP Transports for SAP ERP. If the list does not contain this entry, contact your
Ariba account executive.
The Sourcing SAP Transports page appears.
3. Click Download and save the Ariba_Sourcing_SAP_Transports_V_CI_7.zip package.
4. Extract the contents of the ZIP file and import the transports to SAP ERP.
Configuring the Integration of Ariba Supplier Information
and Performance Management with SAP ERP through
MDG-S
Context
Follow these steps to configure the integration of Ariba Supplier Information and Performance Management with
SAP ERP through Master Data Governance for Supplier (MDG-S).
Procedure
1. Set up one of the following connectivity models between SAP ERP and Ariba Supplier Information and
Performance Management:
○ Direct Connectivity. To set up direct connectivity, use the SOAMANAGER transaction and follow the
instructions in the SOAMANAGER for ECC 6.0 EHP5 and ECC 6.0 EHP6 Systems section in the Ariba
Collaborative Sourcing Integration Guide.
○ Mediated Connectivity. To set up mediated connectivity, follow the instructions in the Integrating Master
Data Using the Mediated Connectivity Integration Method section in the Ariba Collaborative Sourcing
Integration Guide.
Note
The proxy names for Ariba Supplier Information and Performance Management integration are /ARBA/
CO_SI_SOURCING_UPLOAD and /ARBA/CO_SI_SOURCING_DOWNLOAD. You need to configure logical ports
for these proxies.
2. Note
To access SIPM area menu, go to /n/ARBA/SIPM.
Go to SAP Menu Configuration Parameter Direct Connectivity Parameters and configure the
following parameters in the /ARBA/AUTH_PARAM table:
○ Solution. The Ariba application that you want to integrate the master data with. For example, SIPM.
○ Realm. The name of your company as configured in the Ariba application. For example, s4All.
○ Wait. Number of minutes to wait before SAP ERP attempts to reconnect with the Ariba application. For
example, 02.
through MDG-S

Ariba cloud ci 7.0

Recommended

Recommended

More Related Content

What's hot

What's hot (10)

Similar to Ariba cloud ci 7.0

Similar to Ariba cloud ci 7.0 (20)

Recently uploaded

Recently uploaded (20)

Ariba cloud ci 7.0