Content

1 Ariba Network adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111.2 Data flow and data element mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Supported cXML interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Profile transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Supported inbound and outbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14cXML adapter document transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

1.3 Setting up the Ariba Network adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

2 Configuring the Ariba Network adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . 512.1 Installing the Ariba Network adapter for SAP NetWeaver files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512.2 Configuring security certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

How to import security certificates into the Java JRE keystore. . . . . . . . . . . . . . . . . . . . . . . . . . 51How to import security certificates into the Java JRE trustStore. . . . . . . . . . . . . . . . . . . . . . . . . 52How to install client certificates on Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

2.3 About deploying the cXML adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Understanding cXML Adapter document transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54How to deploy the cXML Adapter using JSPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54How to upgrade the cXML Adapter using JSPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58How to install additional resources for the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61How to undeploy the cXML Adapter using the TextConsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . 62How to deploy the cXML Adapter using the TextConsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62How to set log configuration parameters for the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . 63

2.4 About configuring the cXML adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

3 Topics about configuring SLD and transaction processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653.1 About configuring the system landscape directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .653.2 How to import Ariba Network product and component definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 663.3 How to define technical and business system for Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . 673.4 How to define the business system for Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.5 How to define the technical and business system for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.6 How to define the business landscape for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693.7 About configuring transaction processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.8 How to import the design package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.9 About configuring ERP connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.10 How to assign business systems in the integration directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.11 Creating communication channels for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

2 PUBLICSetting up Ariba Network adapter for SAP NetWeaver

Content

3.12 How to create the IDoc receiver communication channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.13 How to create the IDoc sender communication channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.14 How to create the RFC receiver communication channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.15 How to configure the IDoc metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.16 Configuring SAP Process Integration value mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Configuring units of measure code mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Configuring language mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Configuring time zone mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78Configuring global variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Configure the mappings between business system and logical system names. . . . . . . . . . . . . . . 82Configuring currency mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Configuring state code mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84How to maintain the value mapping to support logical systems in SAP Process Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

3.17 How to create a new value mapping table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

4 Topics about configuring integration scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874.1 About configuring integration scenarios in the integration directory. . . . . . . . . . . . . . . . . . . . . . . . .87

How to configure the software component version for communication channel templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

4.2 Topics about configuring integration scenarios in the integration directory. . . . . . . . . . . . . . . . . . . . 89Integration scenarios for outbound and inbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . 89Workflow for configuring the integration scenario for all inbound and outbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Topics about configuring outbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Topics about configuring inbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Enabling TLS support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

4.3 Purchase order integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144.4 Change purchase order integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Removing change order configurations from your Ariba solution. . . . . . . . . . . . . . . . . . . . . . . . 117Migrating change order customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

4.5 Order confirmation integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1184.6 Ship notice integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194.7 Service sheet and service sheet response integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . 1204.8 Service sheet response integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1214.9 Invoice integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224.10 Order inquiries integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234.11 Scheduling agreement release integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234.12 Invoice status update integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244.13 ERP-initiated invoice integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254.14 Receipt integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254.15 Receipt integration scenario for corrections and returns in receipts. . . . . . . . . . . . . . . . . . . . . . . . 126

Setting up Ariba Network adapter for SAP NetWeaverContent PUBLIC 3

4.16 Payment proposal integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274.17 PayMeNow integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274.18 Payment remittance (outbound) integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284.19 Liability transfer integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1294.20 Payment remittance request (inbound) integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304.21 Payment remittance batch request integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304.22 Requisition request integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314.23 Request for quotation integration scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

5 Advanced configuration scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1335.1 Linking multiple SAP ERP instances with Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Document routing mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Multi-ERP configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

5.2 Configuring supplier quick enablement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Additional references. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

5.3 Customizing data mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138How to download mapping workbooks from Ariba Connect. . . . . . . . . . . . . . . . . . . . . . . . . . . 139Enabling migration of mapping customization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

5.4 Enabling support for attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Attachments for outbound documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Attachments for inbound documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Managing email notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

5.5 Support for proxy bypass. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153HTTPS support for attachment processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153How to configure proxy server bypass for attachment processing. . . . . . . . . . . . . . . . . . . . . . . 155Troubleshooting proxy server bypass for attachment processing. . . . . . . . . . . . . . . . . . . . . . . .156

5.6 Support for 2-way match. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1565.7 Using endpoint integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

How to enable endpoint integration in SAP Process Integration. . . . . . . . . . . . . . . . . . . . . . . . .158Endpoint integration for multiple ERP systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

5.8 Using the SAP Process Integration KeyStore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159How to configure the cXML Adapter to use the SAP Process Integration Keystore. . . . . . . . . . . .160

5.9 PDF invoice copy attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Enabling PDF invoice copy attachment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Using PDF invoice copy attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Processing of PDF invoice copy attachments by the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . 164BAdI implementation for the BAdI definition INVOICE_UPDATE. . . . . . . . . . . . . . . . . . . . . . . . 166About configuring SAP ERP for PDF invoice copy attachments. . . . . . . . . . . . . . . . . . . . . . . . . 172How to define a new document class for PDF invoice copy attachments. . . . . . . . . . . . . . . . . . .172How to define a new document type for invoice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173How to create a link between the standard business object and the new document type for invoice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173


Content

Maintaining the INVOICE_EMAIL_SEND parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Maintaining the ZDEL parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174How to configure the attachment processing mode for PDF invoice copy attachments. . . . . . . . 174

5.10 Integrating SAP ERP with the SAP Ariba Commerce Automation solution. . . . . . . . . . . . . . . . . . . . 174About SAP ERP and SAP Ariba Commerce Automation integration. . . . . . . . . . . . . . . . . . . . . . 175SAP ERP integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Enabling SAP ERP and SAP Ariba Commerce Automation integration. . . . . . . . . . . . . . . . . . . . 179SAP ERP and SAP Ariba Commerce Automation integration requirements. . . . . . . . . . . . . . . . .179SAP ERP and SAP Ariba Commerce Automation integration limitations. . . . . . . . . . . . . . . . . . . 179Configuring Ariba Network buyer settings for RFQ events. . . . . . . . . . . . . . . . . . . . . . . . . . . . .180Messages mapping for SAP Ariba Commerce Automation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Handling cXML document errors for SAP Ariba Commerce Automation. . . . . . . . . . . . . . . . . . 180

5.11 Integration of catalog data in SAP ERP and Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181About integration of catalog data in SAP ERP and Ariba Network. . . . . . . . . . . . . . . . . . . . . . . .181Enabling the integration of catalog data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Using the Catalog export program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183About processing Purchase Information Records and Material Master Records. . . . . . . . . . . . . 184Uploading catalog changes using mediated connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Uploading catalog changes using the incremental load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187Maintaining catalog fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Configuring catalog data integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

5.12 Integration to support early payments through Supply Chain Financing . . . . . . . . . . . . . . . . . . . . . 192Prerequisites and limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Workflow for early payment through Supply Chain Financing. . . . . . . . . . . . . . . . . . . . . . . . . . 195Configuring early payments for Supply Chain Financing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

5.13 Integration to support SAP Ariba Payables payments through the cXML format using SAP standard payment interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205

Prerequisites and limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206Workflow to support AribaPay payments through the cXML format using SAP standard payment interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Configuring integration to support SAP Ariba Payables payments through the cXML format using SAP standard payment interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

5.14 About support for third-party logistics providers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Prerequisites and limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Workflow to support third-party logistics providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

6 Topics about configuring SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2146.1 Importing custom code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Configuring SAP IDocs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2156.2 Configuring SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

How to configure SAP ERP for IDoc transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216


Configuring the partner profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216How to create an output type for the entry sheet application. . . . . . . . . . . . . . . . . . . . . . . . . . 224How to maintain condition records for outbound transactions: service sheets. . . . . . . . . . . . . . 224How to maintain condition records for outbound transactions: purchase orders. . . . . . . . . . . . .225How to make additional change PO configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Maintaining variants for remittance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Making additional invoice configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Making additional tax and accrual calculation configurations. . . . . . . . . . . . . . . . . . . . . . . . . . 228Maintaining bank key for the house bank for payment remittance advice. . . . . . . . . . . . . . . . . .234Making user exit enhancements to support shipping and handling charges. . . . . . . . . . . . . . . . 235Maintaining global company code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Configuration related to export of requisitions from SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . .238Business AddIns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

6.3 Proxy settings in SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240How to configure proxy settings for SAP Process Integration 7.1 or dual stack (ABAP and Java) instances of SAP Process Integration 7.3 and above. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241How to configure proxy settings for single stack (Java only) instances of SAP Process Integration 7.3 and above. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

6.4 Documentation of RFCs within the Ariba Network adapter for SAP NetWeaver. . . . . . . . . . . . . . . . 2456.5 Defining authorizations for running Ariba Network transactions. . . . . . . . . . . . . . . . . . . . . . . . . . 2456.6 ABAP programs for outbound transactions implemented using proxies. . . . . . . . . . . . . . . . . . . . . 2466.7 Configuring enhancement for purchase orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

How to configure implicit enhancements for new purchase orders. . . . . . . . . . . . . . . . . . . . . . 247How to configure implicit enhancements for change and cancel Orders. . . . . . . . . . . . . . . . . . .249Implementing a custom exit for purchase orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

6.8 Configuring support for line level hierarchies in service purchase orders. . . . . . . . . . . . . . . . . . . . . 251Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Configuring implicit enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

6.9 How to enable support for setting spend limits on service purchase orders with unplanned spend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

6.10 Configuring advanced pricing details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2566.11 Configuring order confirmations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

How to implement the custom exit to process the order confirmation with rejected line items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257How to configure enhancements for comments in order confirmations. . . . . . . . . . . . . . . . . . . 258How to configure the confirmation category for order confirmations. . . . . . . . . . . . . . . . . . . . .259

6.12 Configuring order inquiries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260How to configure SAP IDOC for order inquiries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261How to configure the partner profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262How to maintain condition records for inquiries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263How to implement a custom exit for the order inquiries function module. . . . . . . . . . . . . . . . . . 264Support for additional cXML fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265


Content

6.13 Topics about configuring scheduling agreement releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Configuring SAP IDOC for scheduling agreement releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . 266How to configure the partner profile for scheduling agreement releases. . . . . . . . . . . . . . . . . . 266How to maintain condition records for scheduling agreement releases. . . . . . . . . . . . . . . . . . . 267How to implement a custom exit for scheduling agreement releases. . . . . . . . . . . . . . . . . . . . .268Support for additional cXML fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269Configuring IDOC metadata (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269

6.14 Configuring ship notices against multiple purchase orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269How to configure the ship notice integration scenario to receive ship notices with zero quantities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270How to configure the SAP IDOC for ship notices against multiple purchase orders. . . . . . . . . . . 270How to configure the partner profile or ship notices against multiple purchase orders. . . . . . . . . 271

6.15 Configuring returns and corrections in receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Configuring parameters in the ARBA/PARAM_TAB table for returns and corrections in receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272How to maintain condition records for returns and corrections in receipts. . . . . . . . . . . . . . . . . 273How to maintain printer default values for returns and corrections in receipts. . . . . . . . . . . . . . 274

6.16 Canceling MIRO Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2756.17 Topics about configuring invoice status updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275

Invoice status update transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276How to configure the invoice status update transaction on your SAP ERP. . . . . . . . . . . . . . . . . 278About enabling customization of invoice status updates from SAP ERP to Ariba Network for invoices in an approval workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

6.18 Configuring service sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279How to implement customer exits for invoices with service type line items. . . . . . . . . . . . . . . . 280How to specify time-out intervals for processing service sheets. . . . . . . . . . . . . . . . . . . . . . . . 281How to implement enhancements for service sheets created for new purchase orders. . . . . . . . 282How to implement enhancements for service sheets created for changed or canceled purchase orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283Implementing enhancements for revoking previously accepted service sheets. . . . . . . . . . . . . .284

6.19 Direct invoicing of purchase order service items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2856.20 How to maintain posting keys to process canceled invoices and credit memos. . . . . . . . . . . . . . . . 2866.21 Configuring ERP-initiated invoices to use the IDOC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287

How to configure the NACE setting to send ERS invoices . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287How to configure the NACE setting to send invoicing plans. . . . . . . . . . . . . . . . . . . . . . . . . . . 289How to configure the NACE setting to send MIRO invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . 290How to maintain tax categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291How to implement the customer exit for MM invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292How to implement routines to prevent creation of duplicate MM IDOCs . . . . . . . . . . . . . . . . . . 293How to maintain partner profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294How to configure FI Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295How to set document type filters for FI invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296


How to maintain output types for FI invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297How to implement the customer exit for FI invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298How to set filters for invoices from Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Handling errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

6.22 Configuring ERP-initiated service entry sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300How to create an event for the ERP-initiated service entry sheet create and change document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301How to activate the event type linkages to send ERP-initiated service entry sheets. . . . . . . . . . . 302Implementing enhancements to update XBLNR (reference) with the service entry sheet number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302How to implement implicit enhancements for revoking and rejecting previously accepted service entry sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303How to create an ERP-initiated service entry sheet on SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . 304

6.23 Configuring Quote Request and Quote Message documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Configuring SAP ERP for Quote Request documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Configuring SAP ERP for Quote Message documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306Configuring SAP Process Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

6.24 Configuring payment proposals for taxes and discounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Prerequisites and limitations of configuring payment proposals for taxes and discounts. . . . . . . 309Example for payment proposals with discounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310How to maintain parameters for payment proposals with discounts. . . . . . . . . . . . . . . . . . . . . .311Handling errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311

6.25 How to configure confirmation control keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

7 Topics about Ariba Network adapter for SAP NetWeaver for SAP Business Suite Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

7.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313Additional references. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

7.2 Installation requirements for using the SAP Business Suite Add-On with the Ariba Network adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

7.3 Setting up the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Deploying the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

7.4 Configuring the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3187.5 Configuring the System Landscape Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318

Importing Ariba Network product and component definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 319Defining technical and business system for Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . .320How to define the technical system for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321How to define the business system for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

7.6 Configuring transaction processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322How to import the design package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323Configuring SAP ERP connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324How to assign business systems in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . 324


Content

7.7 Configuring integration scenarios in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . 325Workflow for configuring the integration scenario for inbound and outbound transactions. . . . . 325

7.8 Topics about configuring the Integration Directory for inbound transactions. . . . . . . . . . . . . . . . . .326How to transfer the integration scenario for inbound transactions. . . . . . . . . . . . . . . . . . . . . . 326Configuring the integration scenario for inbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . 328How to assign the model for inbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328How to assign components for inbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329How to configure sender and receiver relations for individual connections for inbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329How to generate objects for inbound and outbound transactions. . . . . . . . . . . . . . . . . . . . . . . 331How to configure communication channels for inbound transactions. . . . . . . . . . . . . . . . . . . . 332How to activate the scenario for inbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333

7.9 Topics about configuring the Integration Directory for outbound transactions. . . . . . . . . . . . . . . . .333How to transfer integration scenario for outbound transactions. . . . . . . . . . . . . . . . . . . . . . . . 334Configuring the integration scenario for outbound transactions. . . . . . . . . . . . . . . . . . . . . . . . 336How to assign the model for outbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336How to assign components for outbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336How to configure sender and receiver relations for individual connections For outbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337How to generate objects for outbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339How to configure communication channels for outbound transactions. . . . . . . . . . . . . . . . . . . 339How to activate the scenario for outbound transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

7.10 Linking multiple SAP ERP instances with Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Multi-ERP configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

7.11 Testing the Ariba Network adapter for SAP NetWeaver for SAP Business Suite Add-On configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

How to send a purchase order for testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345How to run a getPending transaction for testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

7.12 Understanding error handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Understanding error and status codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Understanding email notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

7.13 Monitoring the cXML Adapter from Runtime Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3497.14 Deploying the project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

SAP Ariba Network certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349How to download the Ariba Network Integration Guide from SAP Ariba Connect. . . . . . . . . . . . 350

7.15 Enabling support for attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Attachments support in cXML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Attachments for outbound documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351Attachments for inbound documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

7.16 Using endpoints for integration with SAP Process Integration for SAP Business Suite Add-On. . . . . 3527.17 Using the SAP Process Integration KeyStore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352


How to configure communication channels to use SAP Process Integration Keystore. . . . . . . . . 353

8 Topics about testing the Ariba Network adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . 354

8.1 Testing the configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

How to send a purchase order for testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

How to run a getPending transaction for testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Understanding error handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

8.2 Monitoring the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Monitoring the cXML Adapter from Runtime Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Configuring logging for the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

8.3 Deploying the project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

Ariba Network certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Downloading the Ariba Network Integration Guide from Ariba Connect. . . . . . . . . . . . . . . . . . . 360

9 cXML Adapter parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

9.1 Common parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

9.2 Inbound parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

9.3 Outbound parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365

9.4 Configuring retry attempts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

9.5 Configuring proxy server parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

10 SAP Ariba objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367

10.1 SAP Ariba namespace certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

10.2 /ARBA/COMMON_OBJECTS package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

10.3 /ARBA/PURCHASEORDER package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

10.4 /ARBA/CHANGEPURCHASEORDER package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

10.5 /ARBA/ERPINVOICE package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371

10.6 /ARBA/INVOICESTATUSUPDATE package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372

10.7 /ARBA/PAYMENTPROPOSAL package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

10.8 /ARBA/RECEIPT package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

10.9 /ARBA/REQUISITION package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

10.10 /ARBA/INVOICE package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

10.11 /ARBA/CANCEL_ASN package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

11 Revision history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378


Content

1 Ariba Network adapter for SAP NetWeaver

Overview [page 11]

Data flow and data element mapping [page 12]

Setting up the Ariba Network adapter for SAP NetWeaver [page 49]

1.1 Overview

Unless otherwise stated, the information in this guide is applicable to the Ariba Network adapter for SAP NetWeaver. For information on the Ariba Network adapter for SAP NetWeaver for SAP Suite Add-On, see Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On [page 11].

The Ariba Network adapter for SAP NetWeaver is an add-on module for SAP business applications that enables integration between Ariba Network and your SAP ERP system. It allows your SAP ERP system to send and receive cXML (commerce eXtensible Markup Language) documents to and from Ariba Network by mapping data elements between IDoc and cXML documents.

The Ariba Network adapter for SAP NetWeaver is a library for SAP Process Integration and includes the integration processes and Java libraries to implement the cXML message format required by Ariba Network.

For more information about cXML and Ariba Network, refer to the following documents on SAP Ariba Connect (https://support.ariba.com/Connect/Log_In ):

● Ariba Network Integration Guide● Buyer Administration Guide● cXML Solutions Guide● cXML User’s Guide

The Ariba Network adapter for SAP NetWeaver consists of the following:

● The design package in the SAP Process Integration component, which contains integration processes, interface objects, and mappings to convert IDoc to cXML and cXML to IDoc

● The cXML adapter installed on the SAP Process Integration component, 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 web site (http://www.java.sun.com )

● SAP Transport files installed on the SAP ERP system

The Setting up Ariba Network adapter for SAP NetWeaver guide (this document) illustrates the deployment and configuration processes of the Ariba Network Adapter integration package within SAP Process Integration.

The following graphic illustrates how the Ariba Network adapter for SAP NetWeaver enables the communication flow between Ariba Network and the SAP ERP system.

Setting up Ariba Network adapter for SAP NetWeaverAriba Network adapter for SAP NetWeaver PUBLIC 11

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.ariba.com%2FConnect%2FLog_In

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.java.sun.com

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.java.sun.com

SAP Process Integration 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 integrates the following components used by the Ariba Network adapter for SAP NetWeaver and its modules:

● The Business Process Engine is a runtime component of the SAP Integration Server. It processes the integration processes at runtime.

● The Integration Engine is the central runtime component of the SAP Integration Server used for receiving, processing, and forwarding messages.

● The Adapter Engine is a runtime component of the SAP Integration Server. It uses adapters to connect the Integration Engine to SAP systems (RFC adapter) and external systems.

1.2 Data flow and data element mapping

The Ariba Network adapter for SAP NetWeaver processes outbound and inbound cXML transactions. Outbound transactions flow from your SAP ERP system to Ariba Network; inbound transactions flow from Ariba Network to the SAP ERP system.

The data elements, or fields, used by your SAP ERP system differ from the data elements used in cXML documents. The Ariba Network adapter for SAP NetWeaver provides a mechanism for mapping field names and data from your SAP ERP system to those used by cXML and Ariba Network. The Ariba Network adapter for SAP NetWeaver 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.


Ariba Network adapter for SAP NetWeaver

Element Mapping Overview

The Ariba Network adapter for SAP NetWeaver 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 Customizing Data Mappings [page 138].

Related Information

Supported cXML interfaces [page 13]Profile transaction [page 14]Supported inbound and outbound transactions [page 14]cXML adapter document transmission [page 49]

1.2.1 Supported cXML interfaces

The Ariba Network adapter for SAP NetWeaver supports the following outbound and inbound cXML interfaces on the SAP Process Integration:

Outbound cXML Interfaces Inbound cXML Interfaces

CatalogUploadRequest ContractRequest

ContractStatusUpdateRequest ComponentConsumptionRequest

CopyRequestInvoiceDetailRequest ComponentAcknowledgment

DespatchedDeliveryNotification InvoiceDetailRequest

EntrySheetUpdateRequest OrderConfirmationRequest

InvoiceCopyRequest PayMeNow

InvoiceStatusUpdateRequest PaymentRemittanceRequest

OrderStatusRequest ProductReplenishmentMessage


Outbound cXML Interfaces Inbound cXML Interfaces

ProductActivityMessage QuoteMessage

PaymentRemittanceBatchRequest ServiceEntryRequest

PaymentRemittanceRequest ShipNoticeRequest

PaymentRequest

QuoteRequest

ReceiptRequest

RequisitionRequest

ScheduleAgreementReleaseRequest

For more detailed information about these cXML Interfaces, see the cXML User’s Guide, cXML Solutions Guide and the sample mapping tables.

1.2.2 Profile transaction

When the Ariba Network adapter for SAP NetWeaver sends a ProfileRequest to Ariba Network, it responds with a ProfileResponse indicating the cXML documents that it accepts and their respective URLs. The Ariba Network adapter for SAP NetWeaver 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 Ariba Network adapter for SAP NetWeaver runs the Profile transaction as a scheduled task every 24 hours. This interval can be configured at runtime. The adapter maintains a profile cache that is updated every time the Profile transaction runs.

1.2.3 Supported inbound and outbound transactions

Requisition [page 15]

Purchase order [page 15]

Scheduling agreement release [page 23]

Order inquiries [page 25]

Order confirmation [page 26]

Ship notice [page 28]

Receipt requests [page 29]

Service sheet [page 33]

ERP-initiated service entry sheets [page 35]

Invoice [page 36]

ERP-initiated invoice [page 40]



Invoice status update [page 45]

Scheduled payments and dynamic discounting [page 46]

Payment remittance request (outbound) [page 48]

Payment remittance request (inbound) [page 48]

Payment remittance batch request [page 48]

Request for quotation [page 49]

1.2.3.1 Requisition

Buyers create a purchase requisition to request to purchase items for products and services on their procurement application. Once the purchase requisition has been approved, the procurement application creates a purchase order against the purchase requisition and sends it to suppliers on Ariba Network.

Related Information

Requisition request integration scenario [page 131]

1.2.3.2 Purchase order

When a buying organization requests products or services through its SAP ERP system, the Ariba Network adapter for SAP NetWeaver maps the request to a cXML OrderRequest and sends it to Ariba Network. Ariba Network 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 Network transmits a generic response. When the Ariba Network adapter for SAP NetWeaver sends an OrderRequest document to Ariba Network, it responds with a synchronous cXML document that contains one of the following status codes:

● 2xx, indicating that Ariba Network accepted the document.● 4xx, indicating that a permanent error has occurred and has been logged.● 5xx, indicating that a transient error occurred. The Ariba Network adapter for SAP NetWeaver then re-

sends the document with the same payload ID for the specified number of retry attempts.

Buyers can also send a scheduling agreement release as a purchase order (release order) to a supplier when they require material or non-material items for an extended period of time. These scheduling agreement releases contain schedules lines with details on the line item, quantity, and the different delivery dates for an extended period of time.

Buyers can set the Delivery Complete indicator (Deliv. Compl.) in the Delivery tab when sending change purchase orders.


When a buyer receives the entire quantity of the line item, the line item can be marked for delivery completion. Buyers can set the delivery complete indicator to let suppliers know that the delivery for the line item is complete and they do not expect any more items.

While creating purchase orders, buyers can include the manufacturer’s name and manufacturer Part IDs to ensure that the supplier obtains the item from the manufacturer specified in the purchase order. The manufacturer Part IDs is also included in the order confirmation and ship notices created against the purchase order.

The manufacturer PartID is available in order confirmations and ship notices for material type HERS only. Buyers can view the manufacturer PartID in the Confirmations tab of the purchase order.

NoteBuyers can configure the confirmation control key in purchase orders. This functionality is available in cloud integration release 9.0 SP1 and higher.

Service purchase order [page 17]Maintaining confirmation control keys [page 22]

Blanket Purchase Orders

Buyers can create and send blanket purchase orders from the SAP ERP system to suppliers on the Ariba Network. The blanket purchase order or the change blanket purchase order contain line items that specify the item category B (Limit) only.

You can also create a blanket purchase order having line items that specify the item category B against a single or multiple outline agreements (OLA).

The cXML blanket purchase orders sent to Ariba Network contains the value orderType=“blanket”. Additionally, the blanket purchase order also includes the Validity Start (cXML field:effectiveDate) and Validity End (cXML field:expirationDate) details for Ariba Network to successfully process blanket purchase orders. Suppliers can use these purchase orders of type “blanket” to create order confirmation and ship notices on Ariba Network.

Ariba Network adapter for SAP NetWeaver processes purchase orders containing line items that specify any other item category as regular purchase orders. Ariba Network rejects purchase orders having line items that specify different categories.

Schedule lines in purchase order and change purchase order

Buyers can specify multiple delivery schedules for a line item in a purchase order or change purchase order that they send suppliers on Ariba Network. This allows buyers to specify multiple schedule lines for a line item that needs to be supplied repeatedly over a period of time.

Each line item can have different quantities and multiple delivery dates and time in a purchase order. Buyers can send multiple delivery schedules for a line item in a purchase order with a number so that Ariba Network receives the delivery schedules numbered sequentially. The mappings for the schedule lines are stored in: /ns0:Messages/ns0:Message2/cXML/Request/OrderRequest/ItemOut/ScheduleLine/@lineNumberl.



To maintain the different delivery schedules for a line item correctly, each schedule line is numbered sequentially in the purchase order and sent to Ariba Network.

When a purchase order containing changes to the schedule lines is sent to a supplier, the newly added, deleted, or edited schedule lines are highlighted in the change purchase order on Ariba Network.

Support for temporary price and planned inspection days in purchase orders

Buyers can send the temporary price and planned inspection days for acceptance of goods in purchase orders and subcontracting purchase orders to suppliers or subcontractors on Ariba Network. The Temporary Price field in the purchase order allows buyers the flexibility to request for goods with a temporary price or without a unit price for the line item. The Planned Acceptance Days field allows buyers to specify the date by which the buyer inspects and accepts the goods sent by the supplier.

While creating standard purchase orders or subcontracting purchase orders, buyers can specify the following:

● The date in the Latest GR date and GR.proc.time fields on the Delivery tab of the purchase order.● Check Estimated Price in the Condition Control tab.

NoteTo support the new TemporaryPrice and PlannedAcceptanceDays elements, buyers must use the cXML version 1.2.030 or higher.

Related Information

Scheduling agreement release integration scenario [page 123]Purchase order integration scenario [page 114]

1.2.3.2.1 Service purchase order

Purchase orders with lines that specify category D are considered service purchase orders on Ariba Network. In the transformed document OrderRequest for a service purchase order, for all lines with category D, the element ItemOut includes a requiresServiceEntry=“yes” attribute. Suppliers must create service sheets for those lines to describe both services and material goods delivered for the order. Unplanned service lines require a maximum amount.

Prerequisites

When creating service purchase orders in SAP ERP, ensure that you:

● Check Goods Receipt on the tab Delivery. If you do not check Goods Receipt:○ 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 check No Limit.● Do not specify a value for the Expected Value that exceeds the Overall Limit.

Limitations

● Ariba Network does not support service lines in blanket purchase orders.● SAP ERP does not allow internal line items for service purchase orders.● You cannot create ERP-initiated invoices against service purchase orders.● Ariba Network adapter for SAP NetWeaver does not support creation of invoices against service purchase

orders that have the ERS (Evaluated Receipt Settlement) option enabled.

Hierarchy in service purchase orders

SAP Process Integration 7.3 or 7.4 and SAP ERP 6.0, EHP 4 and higher enables transmission of service purchase orders with service line-items in up to five levels of hierarchy (1 parent and 4 child levels) from SAP ERP to Ariba Network.

When a purchase order item of type service contains line items with a hierarchy, SAP ERP provides line item numbering information that reflects both a service item's parent and outline numbers and the service item number. The Ariba Network adapter for SAP NetWeaver transmits this information to Ariba Network for both purchases orders and change orders. Any changes or deletions made to a top-level service line or to the service items below a top level service line, including price and quantity limits, are transmitted to Ariba Network. For more information about configuring support for line level hierarchies in service purchase orders, see Configuring support for line level hierarchies in service purchase orders [page 251].

Prerequisites

Implement the SAP Note 2372821 - Service Purchase Order transfer from ERP to Ariba Network fails. This usually occurs when the business function LOG_MM_P2PSE_1 is not active on your SAP ERP system. You require this SAP Note only if the standard field SRVMAPKEY is not activated in your SAP ERP system and the SAP Process Integration mappings fail. The standard field SRVMAPKEY in the SAP Table ESLL stores service purchase order Item ID information. If the SERVMAPKEY is not available, the Item ID does not populate the line numbers for the service lines correctly.

Service line types

Ariba Network adapter for SAP NetWeaver supports transmission of the following additional service line types in service 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 service line type between SAP ERP and Ariba Network with a brief description:

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.

NoteQuantity for service lines with blanket line types is 1, by default as per the standard SAP ERP functionality.

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 invoice. This type of service line is disabled by default in Ariba Network. The contingency service line amount is not included in the net price calculation for the item.

Informatory Information This type of service line is used to provide additional information about any other service line.

Limitations

For service purchase orders with informatory line type, suppliers in Ariba Network cannot create service sheets and invoices.

cXML to Support Additional Service Line Types in Service Purchase Orders

The following is an excerpt of a code that shows the 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> <Extrinsic name="HideAmountBasedInfo">Yes</Extrinsic> </ItemDetail>


The following is an excerpt of a code that shows the extrinsic ContingencyReceiving to support the Contingency line type:

<ItemDetail> <UnitPrice> <Money currency="USD">50</Money> </UnitPrice> <Description xml:lang="en">bulldozer driverb</Description> <UnitOfMeasure>PK</UnitOfMeasure> <Classification domain="SPSC">foo</Classification> <ManufacturerPartID>AX4518</ManufacturerPartID> <ManufacturerName>20008496</ManufacturerName> <Extrinsic name="ContingencyReceiving">Yes</Extrinsic> </ItemDetail>

The following is an excerpt of a code that shows the extrinsic InformationReceiving to support the Informatory line type:

<ItemDetail> <UnitPrice> <Money currency="USD">3000</Money> </UnitPrice> <Description xml:lang="en">bulldozer driverb</Description> <UnitOfMeasure>HUR</UnitOfMeasure> <Classification domain="PK">foo</Classification> <ManufacturerPartID>AX4518</ManufacturerPartID> <ManufacturerName>20008496</ManufacturerName> <Extrinsic name="InformationReceiving">Yes</Extrinsic> </ItemDetail>

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 Process Integration 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).

Setting spend limits on service purchase orders with unplanned spend

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:

Field Name Mapping Between SAP ERP And Ariba Network

SAP ERP Ariba Network Description

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 overall limit.

NoteAlthough 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 procure a service item.

When buyers create or update service purchase orders with unplanned service line items, SAP ERP responds 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.

The Ariba Network adapter for SAP NetWeaver sends the following extrinsic added in the BlanketItemDetail on service purchase orders using cXML version 1.2.028 or higher from SAP ERP to Ariba Network:

● ExpectedUnplannedThe 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>

● MaximumUnplannedThe 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 field under extrinsic ExpectedUnplanned with MaximumUnplanned as a child node with

the attribute currency.


● Ensure that you use only the following cXML versions:○ SAP Ariba cloud integration release 8.0: cXML version 1.2.030 or higher○ SAP Ariba cloud integration release 9.0: cXML version 1.2.031 or higher○ SAP Ariba cloud integration release 9.0 SP1: cXML version 1.2.033 or higher○ SAP Ariba cloud integration release 9.0 SP2: cXML version 1.2.034 or higher

For more information about enabling support for setting spend limits on service purchase orders with unplanned spend, see How to enable support for setting spend limits on service purchase orders with unplanned spend [page 255].

Limitations

You cannot specify unplanned spend limits individually for each child line item in service purchase orders.

1.2.3.2.2 Maintaining confirmation control keys

Buyers using Ariba Network adapter for SAP NetWeaver or integrated with SAP Ariba Supply Chain Collaboration can use confirmation control keys to handle and validate order confirmations and ship notices effectively. When buyers configure the confirmation control key in purchase orders, buyers can enforce or restrict suppliers to create order confirmations and ship notices. The confirmation control key configuration is particularly useful for buyers that require advance notification about the expected delivery date and shipped quantity.

Buyers can specify the confirmation control keys at the line item level in a purchase order. Before specifying the confirmation control keys in purchase orders, buyers must configure the following confirmation control keys on their SAP ERP system:

● AB for order confirmations● LA for ship notices

The confirmation control keys specified in the purchase order is applied when a supplier creates an order confirmation or ship notice from their Ariba Network account. The confirmation control keys allow buyers to override default business rules for order confirmations and ship notices configured on Ariba Network.

For example, a buyer sends a purchase order containing critical material items with a long delivery lead time and require suppliers to confirm all the items on the purchase order and then send a ship notice to them. The buyer configures the confirmation control keys for order confirmation and ship notices. The supplier needs to confirm all the items on the purchase order before sending a ship notice to the buyer.

When buyers specify the confirmation control keys in purchase orders, the following occurs:

Confirmation control key on ERP (example values)

Maintain AB confirmation category for order confirmation

Maintain LA confirmation category for ship notice

Acknowl.Reqd field checked in purchase order

Supplier can create order confirmation

Supplier can create ship notice

001 No No No No No

002 Yes Yes No Yes Yes



Confirmation control key on ERP (example values)

Maintain AB confirmation category for order confirmation

Maintain LA confirmation category for ship notice

Acknowl.Reqd field checked in purchase order

Supplier can create order confirmation

Supplier can create ship notice

003 Yes No No Yes No

004 No Yes No No Yes

005 Yes Yes Required before sending a ship notice

No

006 Yes Yes Yes Required before sending a ship notice

Yes

For more information on the control keys, see the following guides in the Product Documentation > For Users section of the Learning Center:

● Supply chain collaboration integration and configuration guide● SAP Ariba Supply Chain Collaboration User Guide● cXML User's Guide

Prerequisites

● When creating purchase orders, ensure that you maintain the following fields in the Confirmations tab:○ Choose a value in the Conf. Control field for the order confirmation.○ Check the Acknowl.Reqd field.

● Maintain the Confirmation control keys for the order confirmations and ship notices. Ensure that you also maintain the Confirmation categories for order confirmations(AB) and ship notices (LA).

For more information, see How to configure confirmation control keys [page 312].

1.2.3.3 Scheduling agreement release

You can send a scheduling agreement release as a purchase order (release order) to a supplier when they require material or non-material items for an extended period of time. These scheduling agreement releases contain schedules lines with details on the line item, quantity, and the different delivery dates for an extended period of time. The scheduling agreement releases do not contain any pricing information.

You can create either a Forecast Delivery Schedule or JIT (Just-in-time) Delivery Schedule against a scheduling agreement release that contain schedule lines with delivery dates for different quantities for the line item. A Forecast Delivery Schedule contains schedule lines for line items required over a longer period of time,


spanning multiple weeks or months. A JIT Delivery Schedule contains line items required over a shorter period of time, spanning multiple days or even times in a day.

Suppliers receive these scheduling agreement releases as a release purchase order (orderType=“release”) containing a single line item with schedule lines. Suppliers can use this release purchase order to create ship notices for the line item based on the different delivery dates and specified quantities on Ariba Network.

Buyers can send both the LP and LPA purchase document type for scheduling agreements. The scheduling agreement releases can have the order type "release" ( for master agreements or blanket purchase orders), or regular purchase orders. To send scheduling agreement releases, buyer must enable the rule, Allow scheduling agreement release collaboration in their Ariba Network buyer account.

Note● The OrderRequestHeader element has the attribute type="new" for a new scheduling agreement.

Any updates to the same scheduling agreement contains the attribute type="update" and the Release Number is incremental by 1 for each subsequent version.

● You can create CC invoices against scheduling agreements.

Prerequisites

● Ensure that you use only the following cXML versions:○ Cloud integration release 7.0 and earlier: cXML version 1.2.026 or higher○ Cloud integration release 8.0: cXML version 1.2.030 or higher○ Cloud integration release 9.0: cXML version 1.2.031 or higher○ Cloud integration release 9.0 SP1: cXML version 1.2.033 or higher○ Cloud integration release 9.0 SP2: cXML version 1.2.034 or higher

● Make the necessary changes to the parameter cXML Version in the Communication Channel.● Configure the partner profile for scheduling agreement releases● Maintain condition records for scheduling agreement releases● Implement a custom exit for scheduling agreement releases● If you are sending a scheduling agreement with the JIT (Just-in-time) Delivery Schedule against a

scheduling agreement release, ensure that you have maintained the value in JIT Sched. Indicator field as 1-Automatically. You need to maintain this value for the material item in the Material Master-Purchasing view.

For more information, see Topics about configuring scheduling agreement releases [page 265].

Limitations

● You cannot create a scheduling agreement release containing more than one line item. You can create a Forecast Delivery Schedule or JIT Delivery Schedule against only one line item in a scheduling agreement release.

● The quantity of the line items in the scheduling agreement must be the sum of the quantities for the line items having the Commitment Level as Firm. The line item quantity must not be the sum of all the schedule lines.



● You cannot send both the Forecast Delivery Schedule or JIT (Just-in-time) Delivery Schedule against a scheduling agreement release at the same time to suppliers on Ariba Network.

Related Information

Scheduling agreement release integration scenario [page 123]

1.2.3.4 Order inquiries

When an ERP buyer creates a purchase order and requires suppliers to confirm their purchase order or deliver items by the delivery date, they specify the number of days on which suppliers must receive reminders. When suppliers do not confirm or deliver items against the purchase order within the stipulated time, they receive these reminders. These reminders are called Inquiries.

Buyers using the Ariba Network adapter for SAP NetWeaver can send an order inquiry and request information on the following:

● Delivery schedule for materials ordered against line items for an entire purchase order● Delivery date for line items having schedule lines● Reminder on the outstanding line items● Overall status of line items or the purchase order● Additional comments

Suppliers can respond to these inquiries with an order confirmation or a response to the inquiry raised against line items in the purchase order. After the supplier responds to the inquiry, Ariba Network adapter for SAP NetWeaver does not send reminders to suppliers on Ariba Network.

This feature allows both buyers and suppliers to collaborate and handle processing of purchase orders efficiently.

Note● Order Inquiries is supported in SAP Process Integration 7.1, 7.3 and 7.4 for Java only or Java and ABAP

stack (single or dual stack).● Buyers can also send inquiries for change purchase orders.● Buyers can create up to three reminders for a purchase order in an SAP system.

Order Inquiries Work Flow Overview

The following is an example that describes the process on how buyers and suppliers can create an inquiry against a purchase order:

● An ERP buyer creates a purchase order with a delivery date of July 10, 2014 and specifies reminders to be sent to a supplier if they do not confirm the purchase order or deliver items against this delivery date.

A buyer specifies two reminders: Reminder 1 having 2 days and Reminder 2 having 3 days.


● The supplier on Ariba Network receives the purchase order. If the supplier does not confirm the purchase order or delivery items by July 12, 2014, an inquiry (Reminder 1) is sent to the supplier.

● Suppliers can do one of the following:○ Confirm the entire purchase order: The supplier creates an order confirmation on Ariba Network that

is sent to the buyer.○ Responds to the inquiry on a line item. The supplier responds to the inquiry and the same is sent to the

buyer.● If the supplier still fails to confirm the order by July 15, 2014, another inquiry (Reminder 2) is sent to the

supplier.

After the supplier responds to the inquiry, they do not receive reminders from the buyer’s ERP system.

Order Inquiry Output Types and Reminders

Buyers can create two output types for an order inquiry:

● MAHN (Dunning)● AUFB (Dunning Order Confirmation)

Related Information

Order inquiries integration scenario [page 123]

1.2.3.5 Order confirmation

When a supplier confirms the line items in a purchase order, the supplier sends an order confirmation from Ariba Network to the SAP ERP system.

The Ariba Network adapter for SAP NetWeaver supports receiving order confirmations from Ariba Network for the following:

● Confirmation or rejection of entire purchase order items that contain service line items.● Confirmation of orders with or without delivery dates at the header or line-level.● Confirmation of orders containing partially confirmed, rejected, and back-ordered line items.● Confirmation of orders containing line items with multiple schedule lines (delivery dates).● Comments at the header and line-item levels.

NoteA PO item that contains service line items can only be confirmed or rejected in its entirety, not at the individual service line-item level.

If a delivery date is provided in Ariba Network when creating a confirmation request, the delivery date is derived from the confirmationRequest cXML. Otherwise the delivery date is determined from the corresponding



PO item. When the order confirmation contains line items that have been rejected, Ariba Network does not send the delivery date in the order confirmation. In such a case, Ariba Network adapter for SAP NetWeaver maps to the current date the order confirmation was received.

Order confirmations are downloaded from Ariba Network to the Ariba Network adapter for SAP NetWeaver using the pull document transmission method described in cXML Adapter Parameters [page 361]. For more information, see the Ariba Network Integration Guide.

Buyers can include the manufacturer name and manufacturer Part IDs to ensure that the supplier obtains the item from the manufacturer specified in the purchase order. The manufacturer Part IDs is also included in the order confirmation and ship notices created against the purchase order. The manufacturer PartID is available in order confirmations and ship notices for material type HERS only. Buyers can view the manufacturer PartID in the Confirmations tab of the purchase order.

Ariba Network adapter for SAP NetWeaver supports the following mapping files to process order confirmations that suppliers send SAP ERP:

● SAP Ariba cloud integration release 7.0 and higher: MM_Custom_CDF_FulFill_OC_XSD_2_ORDRSP_ORDERS05Use this mapping to process both the header and line-level values in the order confirmation. However, when suppliers send a fully confirmed order confirmation for all the line items, Ariba Network adapter for SAP NetWeaver only sends the header-level information back to Ariba Network.

● SAP Ariba cloud integration release 7.0 HF 10 and higher: MM_CDF_FulFill_OC_XSD_2_ORDRSP_ORDERS05_1Use this mapping to process both the header and line-level values in the order confirmation. Ariba Network adapter for SAP NetWeaver sends both the header-level and line-level information back to Ariba Network.

Workflow

The following is a description of the end-to-end workflow for order confirmation:

1. A buyer creates a purchase order in the SAP ERP that may or may not include service line-items, and may or may not include line items with multiple delivery dates.

2. In Ariba Network a supplier receives the purchase order and creates an order confirmations based on the purchase order.The confirmation order can contain comments at the header and line-items levels.

3. Ariba Network sends the confirmation order to the SAP Process Integration system as a ConfirmationRequest cXML document.

4. The SAP Process Integration system maps the ConfirmationRequest to an ORDRSP.ORDERS05 IDoc and sends it to the SAP ERP system.

5. SAP ERP processes the order confirmation, and the original purchase order is updated with the confirmation information received from Ariba Network.

Related Information

Order confirmation integration scenario [page 118]


1.2.3.6 Ship notice

Suppliers send a ship notice from Ariba Network when the supplier is ready to ship the items on the purchase order. Ariba Network adapter for SAP NetWeaver downloads these ship notices from Ariba Network using the pull document transmission methods described in cXML Adapter Parameters [page 361]. For more information, see the Ariba Network Integration Guide.

You can also receive a single ship notice against multiple purchase orders on your SAP ERP and SAP S/4HANA system. You can receive ship notices with the following from Ariba Network suppliers:

● A single ship notice against multiple purchase orders● Multiple ship notices against a single or multiple line items in a purchase order● Ship notices against purchase orders having line items with zero quantity to indicate the items are not

shipped● Ship notices against a purchase order having material line-items● Ship notices against purchase orders having the BatchID for the line items

You must also configure your SAP ERP or SAP S/4HANA system to accept ship notices against multiple purchase orders.

Buyers can include the manufacturer’s name and manufacturer Part IDs to ensure that the supplier obtains the item from the manufacturer specified in the purchase order. The manufacturer Part IDs is also included in the order confirmation and ship notices created against the purchase order. The manufacturer PartID is available in order confirmations and ship notices for material type HERS only. Buyers can view the manufacturer PartID in the Confirmations tab of the purchase order.

Buyers using SAP Ariba cloud integration release 9.0 SP2 can use confirmation control keys to validate delivery quantity tolerances when suppliers create ship notices against standard purchase orders. When buyers configure the confirmation control key in ship notices, buyers can enforce or restrict suppliers in exceeding the delivery quantity while creating ship notices. This is useful when buyers require a specific shipped quantity.

The confirmation control keys specified in the ship notice are applied when a supplier creates a ship notice from their Ariba Network account. The confirmation control keys allow buyers to override default business rules for ship notices configured on Ariba Network.

Prerequisites

● You need to configure the confirmation control key in purchase orders and order confirmations. This functionality is available in cloud integration release 9.0 SP1 and higher.

● When creating purchase orders, ensure that you maintain the following fields in the Confirmations tab.○ Choose a value in the Conf. Control field for the order confirmation.○ Check the Acknowl.Reqd field.

NoteAlthough Ariba Network adapter for SAP NetWeaver supports the time tolerances in ship notices, Ariba Network currently does not support this functionality.



For more information on the control keys, see the cXML User's Guide in the Product Documentation > For Users section of the Learning Center:

Cancel ship notice

Effective from cloud integration release 9.0 SP1, Ariba Network adapter for SAP NetWeaver supports cancel ship notices from Ariba Network. Suppliers can cancel previously submitted ship notices and submit new ship notices after cancellation.

When suppliers submit a cancel ship notice, the associated ship notice is removed from the Confirmations tab and the inbound delivery is deleted in SAP ERP and SAP S/4HANA. When a ship notice is canceled, it is assumed that no products have been received for that delivery. Suppliers cannot cancel a ship notice after receiving the associated goods receipt.

Prerequisites

● Use cXML version 1.2.033 or higher● Implement SAP Note 1650760 -OutboundDeliveryConfirmationCancelRequest_In short dump when

using SAP EHP4 for SAP ERP 6.0 (SAP_APPL 604 SPS05 and SAP_BASIS 701 SP05)● Complete the following configuration in the System Landscape Directory (SLD):

○ (For SAP ERP) Download and configure the ESA ECC-SE version that corresponds to the ESA ECC-SE-XX version that you run as a dependent component of ARIBA_NETWORK_ADAPTER CI9 of ariba.com

○ (For SAP S/4HANA) Download and configure S4CORE as a dependent component of ARIBA_NETWORK_ADAPTER CI9 of ariba.com.You can use the Define Prerequisite Software Component Versions button on the Dependencies tab of the ARIBA_NETWORK_ADAPTER CI9 of ariba.com page to specify the dependent component.

Related Information

Ship notice integration scenario [page 119]Configuring ship notices against multiple purchase orders [page 269]How to configure the confirmation category for order confirmations [page 259]/ARBA/CANCEL_ASN package [page 377]

1.2.3.7 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 send them to suppliers. However, Ariba Network routes them to SAP Ariba Discounting. When receipt data is successfully posted in Ariba Network, buyers can see the receipts in their online Outbox.

When buyers send a receipt for the goods received, the receipt also contains the delivery note in the header.


http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/1650760

Note● The receipt records are retrieved from SAP ERP on the basis of the date the query to fetch the records

was last run as well as the material document number.● If you are using SAP NetWeaver 7.1 EHP1, then to ensure that receipts are pulled from your SAP ERP

and SAP S/4HANA system, you must implement SAP Note: 1811043 -XI: XPATH expression returns only the first node (value). You also need to create and execute a new program Z_1811043_ADJUST_EXTRACTOR in your SAP Process Integration system. The source code of the program is provided in the SAP Note. Create the program using SE38 and execute the same.

Effective from SAP Ariba cloud integration release 9.0 SP1, Ariba Network adapter for SAP NetWeaver supports header and line level comments in goods receipts to the suppliers on Ariba Network. The header and line level comments are mapped to the following fields of the goods receipt interface in SAP ERP and SAP Ariba:

● Header level comments: HeaderText● Line level comments: Text

Buyers using SAP Ariba cloud integration release 9.0 SP2 can send the GR-Bsd IV flag values they set for invoices in the purchase orders sent to suppliers on Ariba Network. Buyers can ensure that their suppliers can only invoice based on the quantity the buyer received on Ariba Network and not exceed the quantities the buyer received.

Related Information

Receipt with corrections and returns [page 30]Receipt integration scenario [page 125]

1.2.3.7.1 Receipt with corrections and returns

Buyers using the Ariba Network adapter for SAP NetWeaver can send receipts having returns and corrections for the line items shipped against purchase orders. The cXML document ReceiptRequest sent to suppliers on Ariba Network contains detailed information on the number of goods returned, received, or any corrections made against them. The attribute type in the ReceiptItem stores the Received or Returned values. A negative value in the line item quantity denotes that there was a correction to the items received or returned. The following movement types support returns and corrections in receipts:

● 101, 103, and 105 to send received quantities● 102 to send corrections on the received quantity● 122, 124, and 161 to send returned quantities● 123 to send corrections on the returned quantities

Buyers and suppliers on Ariba Network can view the details on the returns and corrections for line items in the purchase order on the purchase order details and the order history pages. Based on the information in the receipt, the purchase order header status displays if the goods were fully received or partially received. The line




items in the purchase order on Ariba Network also display the number of items received or returned. For example, here is how items are calculated as received or returned:

Line item quantity contains Receipt type Indicates the items have been....

Positive value Received Received

Negative value Received Corrected against the received quantity

Positive value Returned Returned

Negative value Returned Corrected against the returned quantity

NoteBuyers can create receipts only for standard purchase orders.

Prerequisites

● Ensure that you use only the following cXML versions:○ Cloud integration release 5.0 and higher: cXML version 1.2.025 or higher○ Cloud integration release 8.0: cXML version 1.2.030 or higher○ Cloud integration release 9.0: cXML version 1.2.031 or higher○ Cloud integration release 9.0 SP1: cXML version 1.2.033 or higher○ Cloud integration release 9.0 SP2: cXML version 1.2.034 or higher

● Configure your SAP ERP system to send receipts with returns and corrections against purchase orders.● Make the necessary changes to the parameter cXML Version in the Communication Channel.

Limitations

When you send or receive receipts with corrections and returns, the receipt integration has the following limitations:

● Buyers cannot create receipts for blanket purchase orders.

Related Information

Receipt integration scenario for corrections and returns in receipts [page 126]


1.2.3.7.1.1 Data flow overview

The following is an example of how receipts with returns and corrections flow from a buyer’s ERP system to Ariba Network:

● An ERP buyer creates a purchase order having the following line items and sends it to the supplier on Ariba Network:○ Line item 1 having a quantity of 20○ Line item 2 having a quantity of 30

● The supplier confirms the purchase order and ships the goods to the buyer for the following:○ Line item 1 having a quantity of 15○ Line item 2 having a quantity of 30

● The buyer receives the goods and creates a receipt for the following items received:○ Received quantity 15 for line item 1○ Correction of quantity 5 that were not received for line item 1○ Received quantity 30 for line item 2○ Returned quantity 10 for line item 2

● The ReceiptItem in the cXMLReceiptRequest document sent to the supplier on Ariba Network contains the following information:○ <ReceiptItem receiptLineNumber="1" quantity="15" type="received">○ <ReceiptItem receiptLineNumber="1" quantity="-5" type="received">○ <ReceiptItem receiptLineNumber="2" quantity="20" type="received">○ <ReceiptItem receiptLineNumber="2" quantity="-10" type="returned">

Mapping Changes

Buyers can create receipts against multiple purchase orders. The mapping file support returns and corrections in receipts:

● The type attribute stores information on the returns and corrections in receipts. The quantity attribute supports positive and negative values while specifying returns and corrections in receipts.

● ○ To support different goods movement types:/ns0:Messages/ns0:Message2/cXML/Request/ReceiptRequest/ReceiptOrder/ReceiptItem/

○ To support positive and negative quantity:@quantity attribute

○ To support received and returned values:@type attribute

○ To support multiple purchase orders:/ns0:Messages/ns0:Message2/cXML/Request/ReceiptRequest/ReceiptOrder /ns0:Messages/ns0:Message2/cXML/Request/ReceiptRequest/ReceiptOrder/ReceiptOrderInfo/OrderIDInfo/@orderID /ns0:Messages/ns0:Message2/cXML/Request/ReceiptRequest/ReceiptOrder/ReceiptOrderInfo/OrderIDInfo/IdReference/@domain/ns0:Messages/ns0:Message2/cXML/Request/ReceiptRequest/ReceiptOrder/ReceiptOrderInfo/OrderIDInfo/IdReference/@identifier



1.2.3.8 Service sheetA service sheet is created against a purchase order containing service type line items. Service sheet and service sheet response transactions are supported for SAP NetWeaver Versions 7.1 and 7.3.

Service sheets are downloaded from Ariba Network to the Ariba Network adapter for SAP NetWeaver using the pull document transmission method described in cXML Adapter Parameters [page 361]. For more information, see the Ariba Network Integration Guide.

Buyers can receive service sheets containing the following:

● Service sheets with or without hierarchy● Service sheets containing unplanned service lines.

Buyer administrators can change quantity and unit price in the service sheets. To do this, the following is required in the purchase order with service type line items:

● In the Services tab, the Price Change Allowed check box must be enabled at the line item level for lines that support changes to the unit price.

● The Unlimited Overfulfillment option must be selected to support the quantity changes to line items.● The Overfulf. Tolerance option must be selected. In the Limits tab, enter the expected value in the Overall

Limits must be specified to allow suppliers to add unplanned line items.

Note● To support changes to unit price in service sheets, buyers must also enable the rule Allow suppliers to

change the unit price on service sheets on Ariba Network.● An integrated supplier can send accounting assignment information in the service sheets to a buyer

using SAP Ariba Invoice Management and this is processed in the SAP ERP system. The accounting information available in the service sheets is used by the SAP ERP system. However, Ariba Network adapter for SAP NetWeaver does not validate the accounting information available in service sheets against the account information.

When a suppliers adds an ad-hoc line item containing the unit of measure(UOM), the Ariba Network adapter for SAP NetWeaver does not process the unit of measure correctly. The Unit of Measure field displays “***.” To avoid this, buyers must ensure that they set up the Unit of Measure configuration in the CUNI transaction on their SAP ERP system. For example, if the unit of measure used on the ERP system is PCE, buyers must maintain PCE as the internal unit of measure in the CUNI transaction.

In some cases, the SAP ERP system fails while processing multiple service sheets for the same purchase order service type item. To prevent failures while processing multiple service sheets, SAP Ariba recommends that you specify a time-out duration. For more information, see How to specify time-out intervals for processing service sheets [page 281].

SAP ERP buyers using Ariba Network adapter for SAP NetWeaver can receive and process service sheets with up to five-levels hierarchy (one parent item and four child line items) created against purchase orders containing service type line items from Ariba Network. Suppliers must create service sheets containing only one parent line item from a purchase order with multiple service type line items. Service sheets against the purchase order with service type line items can have both planned and unplanned line items. These service sheets can also contain attachments. The service sheet must contain at least one-level service child line item in the hierarchical structure.

Buyers can send additional information as attachments at the header-level in the service sheet response they send suppliers onAriba Network. Ensure that the file size for the attachment does not exceed 100 MB.


Direct Invoicing of Purchase Order Service Items

The Ariba Network adapter for SAP NetWeaver supports integration of the service sheets auto-generated on Ariba Network for the invoice containing service type line items created by the supplier and sent to the SAP ERP system. For more information, see Invoice [page 36].

Related Information

Service sheet and service sheet response integration scenario [page 120]

1.2.3.8.1 Prerequisite

To send and receive service sheets with hierarchy, buyer administrators must do the following:

● Apply the SAP Note 1832628 BAPI for service PO Entry Sheet and Contract: ESLL-EXTROW that supports the line numbers available in the service sheets received from Ariba Network to be maintained in the same numbered sequence on the SAP ERP system.

● Buyers must use the service-based invoicing functionality on the SAP ERP system. The GR based IV and S based IV indicator on the Invoice tab of the purchase order containing service lines. This option is required to create separate line items for each service line in the invoice created on the SAP ERP system. When a buyer enables only the GR based IV indicator, the quantity in the service sheet and invoices are not displayed in the Qty field as the quantity is aggregated.

● Apply the SAP Note 1090663 - EDI: Multiple reference to same purchase order item. This note is applicable only a buyer creates one invoice against multiple service sheets and the corresponding purchase order does not have the S based IV indicator enabled.

● Apply the SAP Note 2208145 to process service purchase orders having accounting information in one or more child line items successfully.

1.2.3.8.2 Limitations

Ariba Network adapter for SAP NetWeaver does not support the following:

● Taxes● Charges and Allowances● Shipping and Handling charges● In the cXML for a service sheet sent from Ariba Network, the adapter does not support the operations =

“update” and “Delete”.● Although the service purchase order contains multiple line items, suppliers must create service sheets

with only one parent line item. The SAP ERP system does not process service sheets containing more than one parent line item against a purchase order containing service type line items.

● Services sheets cannot contain adhoc line items (unplanned line items). Suppliers can add unplanned line items only if the buyers maintains a value in the “Overall Limit“ field in the service purchase order created



on the SAP ERP system. However, the maximum amount allowed for unplanned line items on service sheets is based on the maximum amount allowed by buyer on Ariba Network and the Overall Limit maintained on the SAP ERP system. The maximum allowed limit to create invoices is based on the shipped or received quantity.

● The Final Entry indicator option specified in service sheets on the SAP ERP system is not supported on Ariba Network.

● Ariba Network allows changes to unit of measure in service sheets, but SAP ERP does not support changes to the unit of measure in service sheets.

● The Gross Price field in service sheets created on SAP ERP system must not exceed more than nine digits. SAP ERP allows only nine digits in service sheets.

● Lower case values in the XBLNR (document reference number) field. The SAP ERP can store only capital letters in the XBLNR field. The service sheet that buyers receive from Ariba Network must have the serviceEntryID in uppercase to avoid errors on the SAP Process Integration system.

1.2.3.9 ERP-initiated service entry sheets

1.2.3.9.1 About integration to support sending the ERP-initiated service entry sheets to Ariba Network and SAP Ariba Invoice Management

Effective SAP Ariba cloud integration release 9.0 SP2, buyers using Ariba Network adapter for SAP NetWeaver and enabled for SAP Ariba Procurement solutions can create service entry sheets in their SAP ERP system on behalf of the suppliers. Buyers can fill the required information and save the document. The approved service entry sheet is then sent to Ariba Network and can additionally be sent to SAP Ariba Invoice Management. The feature allows the buyers to accelerate the process of service procurement.

Prerequisites:

● The buyer must be on CI9 SP2 and import the latest SAP transports.● The supplier must be enabled on Ariba Network.● The supplier information must be maintained in the /ARBA/AN_VENDOR table.● The buyer needs to perform the following actions:

○ Configure service sheet response integration scenario○ Create an event for service entry sheet create and change document.○ Activate the event type linkages to send service entry sheets.○ Implement the implicit enhancement to update the XBLNR field on SAP ERP with service entry sheet

number.○ Implement the implicit enhancement for revoking and rejecting previously accepted service sheets.

Limitations

● Only approved service entry sheets in SAP ERP are sent to Ariba Network.● When a service entry sheet is modified and resubmitted, the updated information is not sent to Ariba

Network.


● The export of service entry sheets is supported only for purchase orders with standard line types.● Service entry sheets for unplanned services added to an ad hoc hierarchy are not sent from SAP ERP to

Ariba Network.

1.2.3.10 Invoice

Suppliers create an invoice against the purchase order sent by the buyer. Suppliers send invoices from Ariba Network to buyers on the SAP ERP system. Ariba Network adapter for SAP NetWeaver downloads invoices from Ariba Network using the pull document transmission methods described in cXML Adapter Parameters [page 361]. For more information, see the Ariba Network Integration Guide.

NoteLower case values in the XBLNR (document reference number) field. The SAP ERP can store only capital letters in the XBLNR field.

Support for Non-PO Invoices and Credit Memos

In addition to PO-based invoices, Ariba Network adapter for SAP NetWeaver also supports the following in invoices:

● Non-PO based invoice containing accounting information● Header-level credit memos against purchase orders created on Ariba Network and then reconciled in the

SAP Ariba Procurement solutions .● Header-level credit memos against non-POs created in the SAP Ariba Procurement solutions .

Note● To post non-PO invoices and credit memos to SAP, the segment, /ARBA/ACCOUNT_DATA, has been

populated with data corresponding to the distribution (accounting information in cXML) data.● To post this information to the General Ledger (G/L) account directly, you must implement a user exit.● Ariba Network adapter for SAP NetWeaver does not support non-PO invoices with service line items.

For more information on implementing the user exit, see Making user exit enhancements to support shipping and handling charges [page 235].

Support for Discounts in Invoices

Invoice supports the following discount scenarios:

● Discounts entered at the header and line-level on a PO based invoice● Discounts entered at header and line-level on a non-PO based invoice● Discounts entered at header and line on a line-level credit memo



NoteAs SAP does not have a provision to send the discount information, the discount amount is adjusted in the line amount.

Tax Handling for Different Types of Invoices

Invoice supports the following tax handling scenarios:

● PO based invoices, PO based line-level credit memos, and header-level credit memos (either PO based or non-PO based) use the data in segments E1EDK04/E1EDP04 and query the OBCD transaction to determine the tax applicable.

● Non-PO based invoices, non-PO line-level credit memos, and shipping or handling lines with tax use the tax code sent as extrinsic in the cXML directly.

Enabling Support for Shipping and Handling Charges for Invoices

Ariba Network adapter for SAP NetWeaver 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 is sent to SAP as direct posting to General Ledger (G/L) accounts.

● Shipping and handling charges added without any tax is sent in the Invoice Detail Summary only.

Shipping and handling charges is 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 /ARBA/INVOICE to support the posting of shipping and handling charges with tax added as service lines.

The segment, /ARBA/ACCOUNT_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.

For more information about implementing the user exit, see Making user exit enhancements to support shipping and handling charges [page 235].

Invoice with Ship Notice Reference or Receipt Reference

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.

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.

● 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.

NoteIf 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.

Prerequisites

You must enable invoice rules on the Ariba Network to use this feature in SAP ERP.

cXML to Support Ship Notice and Receipt References in Invoices

The Ariba Network adapter for SAP NetWeaver supports new extrinsics added in the cXML version 1.2.028 and higher to support ship notice and receipt references in invoices.

The following is an excerpt of a code that shows the 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 extrinsic receiptID to support invoices referencing receipt:

<InvoiceDetailOrder> <InvoiceDetailReceiptInfo> <ReceiptReference receiptID="" receiptDate=""> <DocumentReference payloadID=""/> </ReceiptReference> </InvoiceDetailReceiptInfo> </InvoiceDetailOrder>

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 Process Integration 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.



Related Information

Service invoice [page 39]Summary invoice [page 39]Direct invoicing of purchase order service items [page 40]Invoice integration scenario [page 122]

1.2.3.10.1 Service invoice

Buyers can create invoices against purchase order containing service type line items. Suppliers create service invoices based on approved service sheets. The integration of service invoices between SAP ERP and Ariba Network is supported on SAP NetWeaver versions 7.1 and 7.3.

SAP ERP buyers using Ariba Network adapter for SAP NetWeaver can receive and process invoices with up to five-levels hierarchy created against purchase orders containing service type line items from Ariba Network. These invoices can also contain attachments.

Buyers can receive invoices containing the following:

● Invoices with or without hierarchy● Invoices containing unplanned service lines.

NoteThe invoices must contain at least one-level service child line item in the hierarchical structure.

Prerequisite

To send and receive invoices with hierarchy, buyer administrators must do the following:

● Buyers must use the service-based invoicing functionality on the SAP ERP system. The GR based IV and S based IV indicator on the Invoice tab of the purchase order containing service lines. This option is required to create separate line items for each service line in the invoice created on the SAP ERP system. When a buyer enables only the GR based IV indicator, the quantity in the service sheet and invoices are not displayed in the Qty field as the quantity is aggregated.

● Apply the SAP Note 1090663 - EDI: Multiple reference to same purchase order item. This note is applicable only when a buyer creates one invoice against multiple service sheets and the corresponding purchase order does not have the S based IV indicator enabled.

1.2.3.10.2 Summary invoice

The Ariba Network adapter for SAP NetWeaver supports summary invoices for multiple purchase orders. Integrated suppliers can send summary invoices for multiple purchase order containing material items and non- material purchase orders having the standard item category.


NoteAriba Network adapter for SAP NetWeaver does not support summary invoices for service purchase orders.

Summary Invoices created against multiple purchase orders contain the following:

● Multiple line items from multiple purchase orders● Line items containing complete and partial quantities

1.2.3.10.3 Direct invoicing of purchase order service items

Buyers can directly invoice a purchase order having the service type items. The Ariba Network adapter for SAP NetWeaver supports integration of the service sheets auto-generated on Ariba Network for the invoice containing service type line items created by the supplier and sent to the SAP ERP system. Auto-generated service sheets for invoices created against purchase orders with service type items contain the following:

● Line items with or without child items● Line items with taxes

For more information, see Direct invoicing of purchase order service items [page 285] .

Prerequisite

To receive invoices created against purchase order service lines, buyer administrators must use the service-based invoicing functionality on the SAP ERP system. The S.-Based IV indicator on the Invoice tab of the purchase order containing service lines. This option is required to create separate line items for each service line in the invoice created on the SAP ERP system.

Limitations

Although the invoice for the service sheets contains taxes and other charges, Ariba Network adapter for SAP NetWeaver does not process the taxes in the service sheet.

1.2.3.11 ERP-initiated invoice

Invoices created on an SAP ERP system is called an ERP-Initiated invoices or ERP CC invoices. These invoices created in SAP ERP are then uploaded to Ariba Network. Uploads can be scheduled either on a daily basis, or on a weekly basis.

The Ariba Network adapter for SAP NetWeaver also supports transmission of invoices that are created through self billing. Invoices are automatically created for purchase orders that have been marked for self-billing and also have a goods receipt created against the purchase order.



SAP ERP buyers can send ERP-initiated or CC invoices from the SAP ERP system to Ariba Network using the IDOC transmission method. Customers can send SAP ERP MM and FI invoices using the IDOC.

Ariba Network adapter for SAP NetWeaver processes ERP-initiated (MIRO) invoices that are reversed and canceled on the SAP ERP system as follows:

● If the parameter, INVOICE_DOC_OPTION is maintained in the /ARBA/PARAM table, Ariba Network adapter for SAP NetWeaver adds "_CM" to the credit memo invoice reference number. For example, if the invoice reference number is 123, the credit memo invoice reference number is named, 123_CM.

● If the parameter is not maintained, the credit memo sent to Ariba Network contains only the invoice reference number.

ERP-initiated invoices using the IDOC transmission method [page 41]

Enabling quick enablement for ERP-initiated invoices [page 43]

ERP-initiated invoice with cross company codes [page 44]

Related Information

ERP-initiated invoice integration scenario [page 125]

1.2.3.11.1 ERP-initiated invoices using the IDOC transmission method

SAP ERP buyers can send ERP-initiated or CC invoices from the SAP ERP system to Ariba Network using the IDOC transmission method. Buyers can send SAP ERP MM and FI invoices using the IDOC.

Buyers can use the GSVERF03 IDOC to send MM invoices and the FIDCCP02 IDOC to send FI invoices.

The Ariba Network adapter for SAP NetWeaver also supports transmission of invoices that are created through self billing. Invoices are automatically created for purchase orders that have been marked for self-billing and also have a goods receipt created against the purchase order.

You can use the IDOC method for the following:

● Transmission of invoices created through ERS(Evaluated Receipt Settlement)● Transmission of manually created PO-based invoices against multiple purchase orders (Summary invoices)

with single and multiple line items. The line-items can contain material, advanced pricing details, and unplanned delivery cost items

● Transmission of manually created non-PO invoices containing material, GL account, contract, internal order, WBS elements and cost center items

● Transmission of invoices created through the Invoice plan containing both periodic and partial items● Transmission of credit memos for FI and MM invoices


The following are the IDOC methods that customers can use to send ERP-initated invoices from SAP ERP systems:

Type of Invoice IDOC Extended IDOC Type

ERS (Evaluated Receipt Settlement)/ MIRO/ MM

GSVERF03 /ARBA/GSVERF03

FI FIDCCP02 /ARBA/FIDCCP02

The /ARBA/ GSVERF03 and /ARBA/ FIDCCP02 IDOC types have been enhanced to include new segments to get additional information on the Name, Street, and City for the vendor. Customers can customize and add segments to include additional information for vendors.

Related Information

ERP-initiated invoice integration scenario [page 125]Configuring ERP-initiated invoices to use the IDOC [page 287]

1.2.3.11.1.1 Prerequisites for using IDOCs for ERP-initiated invoices

The following describes the prerequisites and changes that buyers must ensure while sending the ERP-initiated invoices using the IDOC transmission method:

Prerequisite

To send ERP-initiated invoices through the IDOC, buyer administrators must do the following:

● Make the necessary configurations on their SAP ERP system and configure the integration scenario on their SAP Process Integration. For more information, see ERP-initiated invoice integration scenario [page 125] and Configuring ERP-initiated invoices to use the IDOC [page 287] .

Backward Compatibility

This feature is not compatible with the releases prior to SAP Ariba cloud integration release 6.0. Customers must ensure that they make the necessary changes to remove the previous ABAP proxy programs that were used to process the ERP-initiated invoices.

Starting SAP Ariba cloud integration release 6.0, the ERP_INV_PROCESSED_STATUS parameter is no longer required for ERP-initiated invoices.



To use the IDOCs, you must specify the Transfer IDoc immediately option in the Output Mode section on the Generate Partner Profile page. If you are using the IDOC, you must ensure that you do not use the ERPINV_PROCESSES_CHK parameter.

Buyers must ensure that they make the necessary changes to remove the previous ABAP proxy programs to process the ERP-initiated invoices. The namespace http://ariba.com/xi/ASN/ERPInvoiceProxy no longer exists.

Customers using SAP Ariba cloud integration release 5.0 and lower must continue to maintain the ERP_INV_PROCESSED_STATUS parameter for ERP-initiated invoices. Customers using SAP Ariba cloud integration release 6.0 and higher need to maintain the parameter CHECK_ARIBA_ASN to filter invoices for Ariba Network having the header text ARIBA_ASN .

1.2.3.11.1.2 Limitations using the IDOCs

Ariba Network adapter for SAP NetWeaver integrated for SAP does not support the following while processing ERP-initiated invoices and FI invoices using the IDOC transmission method:

● Transmission of debit memos for FI and ERP-initiated invoices● The <ShippingAmount> element is only sent when the invoice contains unplanned delivery cost.● The SubTotal Amount field does not include the tax amount. Customers can use customer exits to include

the tax amount in the Sub Total Amount field.● Payment term values are not sent if the payment terms is "Immediate" with no tier discounts.● The Email name element is no longer sent in the Contact element.● Accounting information is no longer sent for FI and ERP-initiated invoices.

1.2.3.11.2 Enabling quick enablement for ERP-initiated invoices

Quick enablement is supported for the ERP-initiated invoice transaction. As a result, when an ERP-initiated invoice is sent to Ariba Network, supplier enablement is initiated even if no relationship is maintained in Ariba Network for SAP Vendor and AN Vendor. Quick enablement is achieved by adding the Email ID to the relevant structures in SAP Process Integration and the SAP ERP system.

NoteEmail ID must be maintained in Vendor Master and the same email ID is passed to SAP Process Integration.

To enable quick enablement, ensure that you have:

● Imported the latest version of the AribaNetworkAdapter.tpz file into your SAP Process Integration system.

● Downloaded the relevant SAP transport requests and imported them into your SAP ERP system.


1.2.3.11.3 ERP-initiated invoice with cross company codes

You can create a PO-based or non PO-based ERP-initiated invoice with cross company codes.

● PO-based invoice

You can create an ERP-initiated invoice with company codes that are different to the ones you specified in the corresponding PO. SAP restricts purchase orders and the related PO invoices to a single sending company code. However, it is possible to book the liability to a different paying company code.

● Non PO-based invoice

You can create an ERP-initiated invoice with company codes that are different to the ones you specified for the vendor. In this case, the sending company codes may vary in addition to the paying company code.

NoteThe handling of shipping and freight charges is same for ERP-initiated invoices and ERP-initiated invoices with cross company codes. The planned and unplanned shipping charges are handled as follows:

● Planned shipping and freight charges are sent as a separate material line item.● You can enter shipping and freight charges in the purchase order itself or while creating an ERP-

initiated invoice. If you have not specified these chargers during the creation of the purchase order, you can specify these charges while creating the invoice. When you include these charges while creating an ERP-initiated invoice, then such charges are called unplanned shipping and freight charges. When you view such an invoice in Ariba Network, such unplanned shipping and freight charges are not displayed separately as a line item. Instead, the shipping and freight charges amount is added to the gross amount of the ERP-initiated invoice.

Limitations for Non PO-Based ERP-Initiated Invoice with Cross Company Codes

For non PO-based ERP-initiated invoices, the tax amount is available at the header level only. This is a limitation on the SAP side.

Limitations for PO-Based ERP-Initiated Invoice with Cross Company Codes

● In SAP, you can create purchase orders that relate to a single sending company only. However, some companies have configured SAP to ensure that credit to a vendor account is performed using a separate paying company code. In this case, the SAP FI accounting document for vendor posting does not include information about the purchase order. Although, the reference to the PO ID may be useful, for performance reasons, SAP Ariba has not added the logic to the RFC to send the purchase order number in the invoice. As a result, when you view such an invoice in Ariba Network:○ The PO ID is not displayed as part of the invoice.○ The quantity is displayed as 1 and unit price is displayed as being equal to the line amount.



NoteThe SAP RFC for ERP-initiated invoices, like the other SAP RFCs, is intended to accelerate your IT department’s effort in building appropriate integration between SAP and Ariba system. Therefore, if your business process requires you to include the PO ID in the invoice, you must work with your IT department to add the appropriate logic to the RFC.

● When creating an ERP-initiated invoice in SAP, you can provide the tax amount for each line item. However, when you view such an invoice in Ariba Network, the tax is displayed at the header level as the sum of all the line item tax amounts.

● If you create an ERP-initiated invoice with multiple POs, then such an invoice is extracted and displayed as a non PO-based invoice and as a result, when you view such an invoice in Ariba Network:○ The PO ID is not displayed as part of the invoice.○ The invoice contains only one line item.○ Quantity is displayed as 1.○ Unit price and total invoice amount of the single line item are displayed as the invoice subtotal

excluding freight and tax (if available at header level).

NoteThe data mapping workbook for the ERP-initiated invoice transaction is available in connect.ariba.com -> Ariba Network Adapters -> Ariba Network Adapter for SAP NetWeaver -> Under Integration Tools ->

Data Transformation .

1.2.3.11.3.1 Enabling ERP-initiated invoices with cross company codes

To enable creation of an ERP-initiated invoice with cross company codes, you must import the relevant SAP transport provided by SAP Ariba into your SAP ERP system. To do this, you must download the SAP transports (available in a ZIP file) from Connect (https://support.ariba.com/Connect/Log_In ), open the ReadMe.txt that is available in the ZIP file, and check the transport number that is relevant and import it.

1.2.3.12 Invoice status update

Buyers using the Ariba Network adapter for SAP NetWeaver can send and receive the statuses of invoices created on an SAP ERP system or Ariba Network when the status for invoices are updated on the SAP system. The Invoice Status Update transaction processes invoices that are processed, paid, reconciled, rejected, canceled, parked, or parked invoices that have been deleted on the SAP system. The Business Transaction Events (BTE) has been created to process invoices created, changed, reversed, canceled, parked, parked invoices that have been deleted, or when payments are received on an SAP ERP system.

Buyers can send the following statuses for the parked invoices or the parked invoices that have been deleted to Ariba Network.



Type Status Sent Comments Sent

Parked invoices Processing Document Parked

Parked invoices that have been deleted Rejected Document manually rejected or deleted

Limitations

Ariba Network adapter for SAP NetWeaver does not support processing of the MM and FI invoices that have been created on an SAP ERP system and have been parked.

Related Information

Invoice status update integration scenario [page 124]

1.2.3.13 Scheduled payments and dynamic discounting

The SAP Ariba Discounting solution allows buyers to request or offer early settlement in exchange for a discount from suppliers. Buying organizations use scheduled payments, that is, PaymentProposalRequest documents, to tell Ariba Network and their suppliers about planned payments. The PaymentProposalRequest document containing the extrinsic element called immediatePay to store information on scheduled payments. These documents list scheduled payment dates, discount amounts, and net amounts.

If suppliers choose schedule payments for early settlement, Ariba Network sends the scheduled payments back to the buying organization through the Ariba Network adapter for SAP NetWeaver. The updated PaymentProposalRequest documents are then used to update the payment schedule and discount amount in the buying organization’s SAP ERP or SAP S/4HANA system using the PayMeNow transaction.

If you have subscribed to make payments from a Supply Chain Financing provider, you can send the payment proposals that are marked for Supply Chain Financing to the provider through Ariba Network. You can send payment proposals for approved invoices and credit memos to Ariba Network from your SAP ERP or SAP S/4HANA system. The Supply Chain Financing provider sends the supplier a TradeRequest document to make an early payment to a supplier. Ariba Network sends you the remittance advice with details on the early payment to the supplier.

Effective from SAP Ariba cloud integration release 9.0 SP1, Ariba Network adapter for SAP NetWeaver supports:

● Sending the four-character payment terms code, using the payment Terms field, in the PaymentProposalRequest document to Ariba Network.

● Integrating the dynamic discounting credit memo to SAP ERP and SAP S/4HANA using invoice cXML. Buyers can configure Ariba Network to automatically generate dynamic discounting credit memos that match with the supplier's original tax invoice. If the cXML from Ariba Network contains the following



parameter values, the Ariba Network adapter for SAP NetWeaver generates a PDF or XML which attaches with the associated invoice in SAP ERP and SAP S/4HANA:○ purpose = lineLevelCreditMemo and○ isPriceBasedLineLevelCreditMemo = yes

● Effective SAP Ariba cloud integration release 9.0 SP2, Ariba Network adapter for SAP NetWeaver processes the company code (BURKS) for payment method in the payment proposal request based on the information in Table T042 and the paying company code (ZBUKR).

● NoteSAP ERP and SAP S/4HANA only attach the dynamic discounting credit memo with the associated invoice but do not process them.

If in SAP ERP or SAP S/4HANA, the credit memo attachment to invoice fails, SAP ERP or SAP S/4HANA send an email notification.Prerequisites for integrating the dynamic discounting credit memo to SAP ERP and SAP S/4HANA○ Ariba Network: Configure dynamic discounting credit memo tolerances and countries, then assign the

Dynamic Discounting Credit Memos task to their suppliers.For more information about configuring dynamic discounting credit memos, see the section Configuring automatic generation of credit memos in the Managing discounts guide.

○ SAP ERP and SAP S/4HANA: Enable PDF invoice copy attachment.○ SAP Process Integration: Maintain the following value mapping for ProposalId in payment

remittance:○ Source Agency: XI_Global○ Source Schema: GlobalVariable○ Source Value: DynamicCreditMemo○ Target Agency: XI○ Target Schema: GlobalVariable○ Target Value: X

Quick enablement for payment proposal transactions

Quick enablement is supported for the payment proposal transaction. As a result, when a payment proposal is sent to Ariba Network, supplier enablement is initiated even if no relationship is maintained in Ariba Network for SAP Vendor and AN Vendor. Quick enablement is achieved by adding the Email ID to the relevant structures in SAP Process Integration and the SAP ERP or SAP S/4HANA system.

For more information about scheduled payments, see the cXML Solutions Guide. For more information about discounting, see the Buyer Administration Guide.

Related Information

Payment proposal integration scenario [page 127]Integration to support early payments through Supply Chain Financing [page 192]Enabling PDF invoice copy attachment [page 161]


/ARBA/INVOICE package [page 375]/ARBA/PAYMENTPROPOSAL package [page 373]

1.2.3.14 Payment remittance request (outbound)

Buyers can send a PaymentRemittanceRequest to notify suppliers when payment is made.

For more information, see Payment remittance (outbound) integration scenario [page 128].

1.2.3.15 Payment remittance request (inbound)

If you have subscribed to make payments from a Supply Chain Financing provider, you can receive payment remittances for payments made by the provider to suppliers on Ariba Network.

You can receive remittance advice for payments made against approved invoices and credit memos from Ariba Network to your SAP ERP system.

You send payment proposals for approved invoices and credit memos marked for Supply Chain Financing to Ariba Network from your SAP ERP system. The Supply Chain Financing provider sends the supplier a TradeRequest document to make an early payment to a supplier. Ariba Network sends you the remittance advice with details on the early payment to the supplier.

Related Information

Integration to support early payments through Supply Chain Financing [page 192]Payment remittance request (inbound) integration scenario [page 130]Liability transfer integration scenario [page 129]

1.2.3.16 Payment remittance batch request

Buyers can send multiple remittance advices for SAP Ariba Payables payments and payments for other payment methods from the SAP ERP system to Ariba Network in a batch file through the cXML format.

If you are an existing customer using the payment integration toolkit to send and receive payment proposals and remittances from Ariba Network, SAP Ariba recommends that you use the Ariba Network adapter for SAP NetWeaver to send payment proposals and remittance advices.

NoteSAP Ariba recommends that you send remittance advices for a single payment method in a payment batch. You cannot send remittances with more than one payment method. For example, you cannot have a payment batch file containing both ACH and the SAP Ariba Payables payment methods.



Related Information

Integration to support SAP Ariba Payables payments through the cXML format using SAP standard payment interface [page 205]Payment remittance batch request integration scenario [page 130]

1.2.3.17 Request for quotation

Buyers create a Request for Quotation document on the SAP ERP system and sends it through the Ariba Network adapter for SAP NetWeaver to create a cXML QuoteRequest document that contains specific information needed to create a sourcing request. The cXML document is sent to SAP Ariba Sourcing through the Ariba Network.

You can also configure integration scenarios for the Sourcing Award to Contracts integration scenario. For more information, see the RFQ and award integration with SAP Ariba Sourcing guide.

1.2.4 cXML adapter document transmission

The Ariba Network adapter for SAP NetWeaver always uses HTTPS Post to send documents to Ariba Network.

The Ariba Network adapter for SAP NetWeaver initiates the cXML GetPending transaction to pull inbound business documents. The GetPending transaction allows the SAP ERP system to receive documents from Ariba Network through a data pull.

The GetPending transaction is scheduled using the getPendingInterval parameter defined for each inbound transaction. Ariba Network 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 Network Integration Guide. For details on downloading this guide, see Configuring logging for the cXML Adapter [page 359].

1.3 Setting up the Ariba Network adapter for SAP NetWeaver

Setting up the Ariba Network adapter for SAP NetWeaver involves the following high-level steps:

1. Verifying that all the software and connectivity requirements are in place. For more information, see Installation Requirements [page 11].

2. Setting up and configuring the cXML Adapter. For more information, see About Deploying the cXML Adapter [page 53].

3. Configuring the System Landscape Directory. For more information, see About Configuring the System Landscape Directory [page 65].


4. Configuring transaction processes. For more information, see About Configuring Transaction Processes [page 70].

5. Configuring the SAP ERP system. For more information, see Configuring Your SAP ERP System [page 11].6. Testing the configuration. For more information, see Testing the Adapter [page 11].



2 Configuring the Ariba Network adapter for SAP NetWeaver

Installing the Ariba Network adapter for SAP NetWeaver files [page 51]

Configuring security certificates [page 51]

About deploying the cXML adapter [page 53]

About configuring the cXML adapter [page 64]

2.1 Installing the Ariba Network adapter for SAP NetWeaver files

To install the Ariba Network adapter for SAP NetWeaver, you need the relevant archive file which is available on https://support.ariba.com/Connect/Log_In . For more information, see the Installing and upgrading Ariba Network adapter for SAP NetWeaver.

2.2 Configuring security certificates

Install security certificates in a Java JRE keystore or truststore.

How to import security certificates into the Java JRE keystore [page 51]

How to import security certificates into the Java JRE trustStore [page 52]

How to install client certificates on Ariba Network [page 53]

2.2.1 How to import security certificates into the Java JRE keystore

Context

If you did not configure the trustKeyStore parameter in the Channels.Config.properties file for the purchase order transaction, then you need to import the certificates of the domains on which attachments are hosted into your Java JRE keystore.

Setting up Ariba Network adapter for SAP NetWeaverConfiguring the Ariba Network adapter for SAP NetWeaver PUBLIC 51


Procedure

1. On the system hosting the Ariba Network adapter for SAP NetWeaver, determine the path for your Java home directory. Enter the following command from the command line:

echo $JAVA_HOME2. Go to your JAVA_HOME/bin directory and issue the following command to determine the location of the

keystore in your JAVA_HOME directory:keytool -list -keystore /jre/lib/security/cacertsThe output from this command should list multiple certificates in the keystore. If the output does not list any certificates, then this is probably not the correct keystore.3. Copy the required domain certificates to your JAVA_HOME/bin directory.

4. Set your working directory to your JAVA_HOME/bin directory.

5. Import each certificate. Enter the following command:keytool -import -trustcacerts -alias alias -file domain_certificate_file -keystore JAVA_HOME/jre/lib/security/cacertsWhere:alias is a name, or alias, you want to use to refer to this certificate.domain_certificate_file is the name of the domain certificate file, such as sys123.cer.

6. The keytool utility prompts for you for the keystore password. Enter the password.

7. Repeat steps 5 and 6 for additional certificates that you need to import into the keystore.

2.2.2 How to import security certificates into the Java JRE trustStore

Context

If you configured the trustKeyStore parameter in the ChannelsConfig.properties file for the purchase order transaction, then you need to import the certificates of the domains on which attachments are hosted into your trustKeyStore file.

Procedure

1. On the command line, enter:keytool -import -trustcacerts -alias alias -file domain_certificate_file -keystore trustStore_pathWhere:alias is a name, or alias, you want to use to refer to this certificate.domain_certificate_file is the name of the domain certificate file, such as sys456.cer.trustStore_path the trustStore path configured for the purchase order communication channel.

2. Repeat the above step for additional certificates that you need to import into the truststore file.


Configuring the Ariba Network adapter for SAP NetWeaver

2.2.3 How to install client certificates on Ariba Network

Context

After you have imported the security certificates, you must configure your Ariba Network buyer account to store the client certificate.

Procedure

1. Obtain a signed digital certificate issued for the client. The certificate must be issued from a Certificate Authority (CA) trusted by Ariba. For a list of CAs trusted by SAP Ariba or to add a CA to SAP Ariba’s trusted CAs, contact your SAP Ariba Support Representative.

2. Log in to your Ariba Network account. You must have the account administrator privileges to make this change.

3. ClickManage Profile in the upper left corner of the home dashboard. The Configuration page opens.Ariba Network displays the Configuration page4. Click cXML Setup.5. In the Authentication Method section, choose the Certificate authentication method from the Select an

authentication method pull-down menu.6. Copy the certificate, starting with "-----BEGIN CERTIFICATE-----" and ending with "-----END

CERTIFICATE-----". Paste the signed client certificate into the Certificate text box.

7. You can also use a backup digital certificate. Ariba Network uses the backup certificate if your primary certificate becomes invalid. Backup certificates are useful when your primary certificate expires or when you need to perform certificate maintenance.

8. Click Save.

NoteDigital certificates expire after a predetermined period of time. It is your responsibility to periodically obtain updated certificates from your certificate authority and install them on Ariba Network.

You can also use a backup digital certificate. Ariba Network uses the backup certificate if your primary certificate becomes invalid. Backup certificates are useful when your primary certificate expires or when you need to perform certificate maintenance.9. Click OK.

2.3 About deploying the cXML adapter

The Ariba Network adapter for SAP NetWeaver relies upon the cXML Adapter, which conforms to the JCA specification and implements the cXML transport protocol.

If your version of SAP Process Integration is prior to Process Integration 7.3 EHP1, use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP Process Integration. From SAP netweaver


version Process Integration 7.3 EHP1 onwards you must use the SAP Software Update Manager (SUM) tool to deploy the adapter.

For more information on how to install or upgrade using the SUM tool, contact your SAP systems administrator.

Related Information

Understanding cXML Adapter document transmission [page 54]How to deploy the cXML Adapter using JSPM [page 54]How to upgrade the cXML Adapter using JSPM [page 58]How to install additional resources for the cXML Adapter [page 61]How to undeploy the cXML Adapter using the TextConsole [page 62]How to deploy the cXML Adapter using the TextConsole [page 62]How to set log configuration parameters for the cXML Adapter [page 63]

2.3.1 Understanding cXML Adapter document transmission

Ariba Network 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 Ariba Network adapter for SAP NetWeaver always uses HTTPS Post to send documents to Ariba Network.

The Ariba Network adapter for SAP NetWeaver initiates the cXML GetPending transaction to pull inbound business documents. The GetPending transaction allows the SAP ERP system to receive documents from Ariba Network through a data pull.

The GetPending transaction is scheduled using the getPendingInterval parameter defined for each inbound transaction. Ariba Network 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 Network Integration Guide. For details on downloading this guide, see How to download the Ariba Network Integration Guide from SAP Ariba Connect [page 350].

2.3.2 How to deploy the cXML Adapter using JSPM

Prerequisites

In SAP Process Integration, you have placed the .SCA file in the required location.



Procedure

1. Start JSPM.

2. Enter your user name and password and click Log On.

3. Choose Business Packages (advanced user only) and click Next.


4. Choose the business package you want to deploy and click Next.The Queue status appears.

5. Click Start.The Deploy Queue screen appears.



The Completed screen appears.

6. Click Exit.

Results

The cXML Adapter is successfully deployed. You must start the cXML Adapter from the SAP NetWeaver Administrator console.

You cannot undeploy the adapter using the JSPM. For information on how to undeploy the adapter, see Undeploying the cXML Adapter using the Textconsole [page 62].


2.3.3 How to upgrade the cXML Adapter using JSPM

Procedure

1. Start JSPM.

2. Enter your user name and password and click Log On.



3. Choose Single Support Packages and Patches (advanced user only) and click Next.

4. Choose the support package you want to apply and click Next.The Queue status appears.


5. Click Start.The Deploy Queue screen appears.

The Completed screen appears.



6. Click Exit.

Results

The cXML Adapter is upgraded successfully.

2.3.4 How to install additional resources for the cXML Adapter

Context

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

Procedure

To install these files, copy the files to the following folder:Install_Root/etc/catalog/.

While configuring the Communication Channel, if you check the Use XML Validation option, then you must provide the folder path to the above copied files in the Catalog Configuration Directory field.


2.3.5 How to undeploy the cXML Adapter using the TextConsole

Context

You must use the TextConsole script to undeploy the cXML adapter.

Procedure

1. Set your working directory to SAP_instance\j2ee\console.

2. Run textconsole.bat or textconsole.sh.The telnet console appears.3. Login with the relevant admin user.4. Enter the following command at the telnet prompt:

>undeploy name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_undeploy_error=stop

Undeploy Settings:

○ on_undeploy_error=stop○ on_prerequisite_error=stop○ workflow=normal

If there is an offline undeployment, the telnet connection to host might be lost and the following message appears:

Processing undeployment operation, please wait...

name: 'com.ariba.asc.sap.netweaver.xiadapter.ra', vendor: 'ariba.com', location: 'null', version: 'null', status: 'Success', description: '', sda: 'name: 'com.ariba.asc.sap.netweaver.xiadapter.ra', vendor: 'ariba.com', location: 'SAP AG', version: '3.0.1420051114090313.0000', software type: 'J2EE', dependencies: '[]'' >

2.3.6 How to deploy the cXML Adapter using the TextConsole

Context

Run the following at the Telnet prompt:

deploy <Location of .SCA File>name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_deploy_error=stop



For example:

deploy /usr/sap/LP3/DVEBMGS00/j2ee/deployment/scripts/AribaNetworkAdapterSAPNetweaver.sca name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_deploy_error=stop

NoteTo upgrade to the latest version of the Ariba Network adapter for SAP NetWeaver, you must first undeploy the existing adapter and then deploy the latest version that you have downloaded from https://connect.ariba.com .

2.3.7 How to set log configuration parameters for the cXML Adapter

Context

Set log configuration parameters so that the cXML Adapter sends log entries to a separate file.

Procedure

1. Login to the SAP Process Integration log administration section athttp://XI_server_hostname/XI_port/nwa/logs.

2. Click the Log Configuration link.3. Choose Tracing Locations from the Show dropdown list.

4. Choose the node (package) com ariba asc , to set the logging level to log the complete adapter processing information, or choose CXMLSender under connector.cxml.util to set the logging level to log only the exchanged messages.

5. Change the severity level from Error to Info / Debug in the Severity dropdown list, and then click Save Configuration in the toolbar.

NoteThe log level can remain Error when running in a production environment, but SAP Ariba recommends that you change the log level to Info.

You can also find out about the version of the Ariba Network adapter for SAP NetWeaver.


http://help.sap.com/disclaimer?site=https%3A%2F%2Fconnect.ariba.com


2.4 About 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 [page 51] section.

For a description of the parameters and instructions for how to configure retry attempts, see cXML Adapter Parameters [page 361].



3 Topics about configuring SLD and transaction processes

About configuring the system landscape directory [page 65]

How to import Ariba Network product and component definitions [page 66]

How to define technical and business system for Ariba Network [page 67]

How to define the business system for Ariba Network [page 68]

How to define the technical and business system for SAP ERP [page 68]

How to define the business landscape for SAP ERP [page 69]

About configuring transaction processes [page 70]

How to import the design package [page 70]

About configuring ERP connectivity [page 71]

How to assign business systems in the integration directory [page 72]

Creating communication channels for SAP ERP [page 72]

How to create the IDoc receiver communication channel [page 73]

How to create the IDoc sender communication channel [page 74]

How to create the RFC receiver communication channel [page 75]

How to configure the IDoc metadata [page 75]

Configuring SAP Process Integration value mapping [page 76]

How to create a new value mapping table [page 85]

3.1 About configuring the system landscape directory

After you have installed the cXML Adapter, you configure the System Landscape Directory (SLD) by importing the Ariba Network adapter for SAP NetWeaver product definition and defining the systems involved in the integration. 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 Ariba Network adapter for SAP NetWeaver 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 Network integration and defined in the SLD.

Setting up Ariba Network adapter for SAP NetWeaverTopics about configuring SLD and transaction processes PUBLIC 65

The information in this topic is applicable to the Ariba Network adapter for SAP NetWeaver. For information on the Ariba Network adapter for SAP NetWeaver for SAP Suite Add-On, see Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On [page 65].

Related Information

Importing Ariba Network Product and Component Definitions [page 66]Defining Technical and Business System for Ariba Network [page 67]Defining Technical and Business System for SAP R/3 [page 68]

3.2 How to import Ariba Network product and component definitions

Context

Import the product and component definitions of Ariba products that will work with SAP Process Integration, as a CIM file.

Procedure

1. From the Process Integration main page, open the SLD Administration page.2. Navigate to the Content section, and then click Import.3. Select the AribaNetworkAdapter.SoftwareCatalog.zip by clicking on the Browse button, and then

navigating to the file location.

NoteEnsure that you have imported Ariba_Basis.SoftwareCatalog.zip and Ariba_Adapter.SoftwareCatalog.zip before you import AribaNetworkAdapter.SoftwareCatalog.zip. For more information, see Installation Guide for Ariba Network Adapter for SAP NetWeaver.

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:


Topics about configuring SLD and transaction processes

○ Vendor: ariba.com○ Component: ARIBA_NETWORK_ADAPTER, CIx of ariba.com○ Version: CIX

Results

The Ariba Network adapter for SAP NetWeaver will now be recognized by the Integration Repository and Directory.

3.3 How to define technical and business system for Ariba Network

Context

Set up the technical system for the Ariba Network system using the Technical System Wizard.

Procedure

1. Select Technical Systems from the main SLD page to open the Technical System page.2. Click New Technical System 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 Network, and then click Next.4. Specify the system details as follows:

○ System Name: Specify a user-defined system name here. For example, TS_ASN○ Host Name: Enter a host name here. For example, an

5. Click Next.6. Associate the product and component to the system. Scroll down the list to select the product, ASN,

defined earlier, and then click Add. You can also filter to select the product to associate. Ensure that the component ARIBA_NETWORK_ADAPTER, CIx of ariba.com, is selected.

7. Click Finish.

Next Steps

Set up the business system for the Ariba Network system using the Business System Wizard.


3.4 How to define the business system for Ariba Network

Procedure

1. Select Business System from the main SLD page to open the Business System page.2. Click New Business System here to open the Business System Wizard.3. In the Wizard, select Third-Party as the technical system type to associate the business system with, and

then click Next.4. Select the technical system, TS_ASN, created in the previous procedure, from the System field, and then

click Next.

NoteThe Logical System Name is not required.

5. Enter the business system name, e.g. BS_ASN, in the Name field, and click Next.

6. Specify the installed products. Make sure that the product ASN, NW04.1 and the related component ARIBA_NETWORK_ADAPTER, CIx of ariba.com installed on the technical system, are selected, and then click Next.

7. Click Finish.

3.5 How to define the technical and business system for SAP ERP

Context

Set up the technical system for the SAP ERP system using the Technical System Wizard.

Procedure

1. Select Technical System from the main SLD page to open the Technical System page.2. Click on New Technical System here to open the Technical System Wizard.3. In the Wizard, select AS ABAP as the Technical System Type, and then click Next.4. To specify the SAP ERP system details enter values in the AS ABAP name (SID), Installation Number, and

Database Host Name fields, and then click Next.5. Specify the Message Server and Central Application Server. Enter values in the Host Name, and Message

Server Port field. Specify a logon group for the Message Server by entering a value in the Logon Groups column and clicking Add Logon Groups to assign them. You can also filter to select the logon groups. Enter values in the Host Name and Instance Number fields for the Central Application Server, and then click Next.



6. (Optional) Define additional application servers if required. Specify values in the Host Name and Instance Number columns in the Application Server List table, and click Add Application Server. You can also filter to select the application server details. Click Next.

7. Define the Client. Enter values in the Client Number and Logical Client Name columns of the Client List table, and then click Next. The logical system name is required for enabling the communication using IDocs between the SAP Process Integration and ERP 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 Network” [page 133] section.

8. Define software product and components. Select the SAP ERP version installed on this technical system, as well all other products installed on the system. You can filter to select the installed products and the software components.

9. Click Finish.

Next Steps

Set up the business system for the SAP ERP system using the Business System Wizard.

3.6 How to define the business landscape for SAP ERP

Procedure

1. Select Business System from the main SLD page to open the Business System page.2. Click New Business System here to open the Business System Wizard.3. In the Wizard, select AS ABAP as technical system type to associate the business system with, and then

click Next.4. Select the technical system created in the previous procedure from the System drop down list, to

associate it with the business system. Select a client for the selected technical system from the Client drop down list, and then click Next.

5. Enter the business system name. E.g. BS_SAPR3_50, and click Next.

6. 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 Next.

7. Select the role of the business system. Select Application System as the Business System Role and select your SAP Process Integration instance name from the Related Integration Server drop-down list to specify the integration server. In the case of application systems, specify the integration server.

8. Click Finish.


3.7 About configuring transaction processes

After you have installed the System Landscape Directory (SLD), you must:

● Import the design package containing the transactions supported by the Ariba Network adapter for SAP NetWeaver.

● Configure SAP Process Integration connectivity to ERP.● Configure SAP Process Integration 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.

NoteThe 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.

Related Information

Importing the Design Package [page 70]About Configuring ERP Connectivity [page 71]Configuring SAP NetWeaver PI Value Mapping [page 76]

3.8 How to import the design package

Context

The AribaNetworkAdapter.tpz file contains the definition of the business scenarios.

Procedure

1. Copy the package file AribaNetworkAdapter.tpz to the import directory on the SAP Process Integration server, *****\SYS\global\xi\repository_server\import.

NoteFor customizations, use AribaNetworkCustomAdapter.tpz.



For example, D:\usr\sap\ARB\SYS\global\xi\repository_server\import.

2. Open the Enterprise Services Builder: Design Tool from the SAP Process Integration main page.3. From the Tools menu, select the Import Design objects... option.4. If you are trying to install the SAP Ariba cloud release version of the SAP Process Integration Adapter on an

SAP ERP 6.0 EHP6 or higher, ensure that you click to select the check box ‘Ignore Invalid Component Version’. You must also implement the changes specified in the SAP Note 1688610.

5. Select AribaNetworkAdapter.tpz from the available files list, and then click OK.

6. After the import completes, the component ARIBA_NETWORK_ADAPTER, CIx of ariba.com appears in the components list of the Integration Builder Design Tool.

3.9 About configuring ERP connectivity

Context

To enable communication between SAP Process Integration and SAP ERP using IDoc documents, we need to configure the following parameters on the SAP Process Integration ABAP stack:

● Configure the RFC Destination.● Configure the Port for the IDoc Adapter SAP Process Integration connectivity to ERP.

Procedure

1. Using Transaction SM59, create an RFC destination of type ERP to connect to the SAP ERP system.2. Using Transaction IDX1, create a Port for the new RFC destination. For example, for the SAP ERP system

D47 client 800, you must use specify following parameters to create the port:

○ Port: SAPD47.○ Client 800.○ RFC Destination: Specify the destination created in SM59 here.

NoteEnter the password in UPPER case.


3.10 How to assign business systems in the integration directory

Context

The Integration Directory configuration of the Ariba Network adapter for SAP NetWeaver 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.

Procedure

1. Open the Configuration: Integration Builder from the Process Integration 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 and BS_SAPR3_50

created earlier, from the list. For more information about creating business systems, see the “About Configuring the System Landscape Directory” [page 65] section.

NoteIn the case of Multi-ERP implementation, you must select all the Business Systems representing your SAP ERP instances involved in the integration.

6. Click to clear the Create Communication Channel Automatically check box, if it is checked, to avoid the creation of unwanted channels.

7. Click Finish.

3.11 Creating communication channels for SAP ERP

Create the communication channels used for SAP ERP 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 ERP 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 ERP.



Related Information

Creating the IDoc Receiver Communication Channel [page 73]Creating the RFC Receiver Communication Channel [page 75]Configuring IDoc Metadata (Optional) [page 75]

3.12 How to create the IDoc receiver communication channel

Procedure

1. In the Objects tab of the Integration Builder, click 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.4. Click the Communication Component field, then click the Display Input Help drop down list and select

Input Help. In the following Choose Communication Component window, select a communication component, say BS_SAPR3_50, and click Apply.

5. Click Create6. From the Parameters tab of the Edit Communication Channel window, click the Adapter Type field, then

click the Display Input Help drop down list and select Input Help to display the list of adapter types. From the Choose Adapter Metadata window, select the following adapter, and then click Apply:

○ Name: IDoc○ Namespace: http://sap.com/xi/XI/System○ Software Component Version: SAP BASIS 7.10

Note○ If you are configuring the IDoc Receiver for a single stack, enter IDOC_AAE as the name for the

Adapter Type.○ If you have multiple ERP systems, create an IDoc Receiver for each of the business systems.

Ensure that you use the same Communication Channel name for each of the IDoc Receiver you create for the business system. For example, if you create a communication channel, CC_IDoc_Receiver. Use this communication channel name for each of your multiple ERP systems.

7. After selecting the adapter, click the Receiver option, to select the corresponding type.8. In the Adapter Engine field, select Integration Server or non-central Adapter Engine,

depending on your configuration.9. Edit the other parameters, to match your SAP R3 system (RFC Destination, Interface Version, Port, SAP

Release).10. Select the following options and leave the others unchecked:

○ Apply Control Record Values From Payload


○ Take Sender From Payload11. Save and activate the communication channel.

3.13 How to create the IDoc sender communication channel

Context

To configure the integration scenario for a single stack, create the Idoc sender for the Communication Channel.

Procedure

1. In the Objects tab of the Integration Builder, click Communication Channel.2. Go to the context menu for Communication Channel and click New.3. In the Communication Channel4. Click the Communication ChannelDisplay Input Help pull-down menu and select field, then click the field,

enter CC_IDoc_Sender as the name of the communication channel.Input HelpApply. For example, BS_SAPR3_50. In the Choose Communication Component window, select a communication component.

5. Click Create.6. In the Parameters. In the Choose Communication Component tab of the Edit Communication Channel

window, click the Adapter Type field, then click the Display Input Help pull-down menu and select Input Help to display the list of adapter types. From the Choose Adapter Metadata window, select the following adapter, and then click Apply:○ Name: IDoc_AAE○ Namespace: http://sap.com/xi/XI/System○ Software Component Version field, enter CC_IDoc_Sender field, then click the: Choose the

component version for your SAP ERP system. For example, SAP BASIS 7.10.7. Click Sender .8. In the Adapter Engine field, select Central Adapter Engine.9. Edit the other RFC Parameters, Ack Settings, and Advanced parameters as required to match the entries

on your SAP ERP system.10. Ensure that Multiple IDocs in Single XI Message (or IDOCXML) is selected.11. Save and activate the communication channel.



3.14 How to create the RFC receiver communication channel

Procedure

1. In the Objects tab of the Integration Builder, navigate to Service Without Party Business SystemBS_SAPR3_50 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 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 7.10

5. After selecting the adapter, click 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).

NoteEnter the password in UPPER case.

8. Edit the Maximum Connections option according to the excepted load.9. Save and activate the communication channel.

NoteIf you have multiple ERP systems, create an RFC for each of the business systems. Ensure that you use the same Communication Channel name for each of the RFC you create for the business system. For example, if you create a communication channel, CC_RFC_Receiver. Use this communication channel name for each of your multiple ERP systems.

3.15 How to configure the IDoc metadata

Context

You can optionally preload the metadata of the IDoc documents exchanged by the IDoc adapter during configuration. If you skip do not preload metadata, the metadata information will be downloaded and associated to the port the first time a given type of IDoc is exchanged.


Procedure

1. Check and configure the IDoc Metadata parameters of the port to communicate with the SAP ERP system in SAP Process Integration.

2. 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.

3.16 Configuring SAP Process Integration value mapping

Configure SAP Process Integration value mapping for supporting facilities such as IDoc Payload and standard code conversions.

The information in this topic is applicable to the Ariba Network adapter for SAP NetWeaver. For information on the Ariba Network adapter for SAP NetWeaver for SAP Suite Add-On, see Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On [page 65].

Related Information

Configuring Units of Measure (UOM) Code Mapping [page 76]Configuring Language Mapping [page 77]Configuring TimeZone Mapping [page 78]Configuring Global Variables [page 78]Configure the Mappings Between Business System and Logical System Names [page 82]Configuring Currency Mapping [page 83]How to create a new value mapping table [page 85]

3.16.1 Configuring units of measure code mapping

As part of the transformation of documents from IDoc to cXML, or vice versa, certain codes, such as units of measure (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○ Scheme: UOM

● Target Values:○ Agency: UOM_ISO



○ Scheme: 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

KGM KG

EA EA

ST PC

BX BOX

3.16.2 Configuring language mapping

In the value mappings, use the following parameters for language transformations rules:

● Source Values:○ Agency: LANG_ERP○ Scheme: Lang

● Target Values:○ Agency: LANG_ISO (an example value of SAP ERP Business Systems)○ Scheme: Lang

Fill in the value set for UOM_ERP and UOM_ISO, to set up the transformation rules for languages.

The following table shows examples of the respective value sets:

LANG_ERP LANG_ISO

D de

E en


LANG_ERP LANG_ISO

F fr

3.16.3 Configuring time zone mapping

In the value mappings, use the following parameters for TimeZone transformations for different Business Systems and for Ariba Network:

● Source Values:○ Agency: XI_Global○ Scheme: GlobalVariable

● Target Values:○ Agency: BS_SAPR3 (an example value of SAP ERP Business Systems)○ Scheme: TimeZone

Fill in the values to set up the transformation rules for TimeZone.

The following table shows examples of the TimeZone transformation values:

Agency Scheme Value

XI_Global GlobalVariable TimeZone

BS_SAPR3_50 TimeZone +05:45

3.16.4 Configuring global variables

Because SAP NetWeaver Process Integration acts as the integration platform between SAP ERP and Ariba Network, 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○ Scheme: GlobalVariable

● Target Values:○ Agency: XI○ Scheme: GlobalVariable

Fill in the global variable table as appropriate for your system.



SAP Process Integration Global Variable

Example SAP Process Integration Value Group Name Description

PaymentProposalStartDateTime

2006-10-09T12:13:13

BPMConfig Use this timestamp when 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.)

InvoiceStatusUpdateStartDateTime

2006-10-09T12:13:14

BPMConfig Use this timestamp when the timestamp file for the InvoiceStatusUpdate transaction is not configured or its date/time parameters are empty. (Use it for test and development only and NOT for production)

IsMultiERPModeEnabled true/false BPMConfig Use this parameter to enable (true) or disable (false) the Multi-ERP support.

ReceiptStartDateTime

2006-10-09T12:13:15 BPMConfig Use this timestamp when 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.

SAPExternalPaymentMethod

C BPMConfig Use this parameter to set the payment method used in external payment. This must be a valid 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.

SAPUserName <a valid SAP user name> BPMConfig Use this parameter to set the SAP user name.




OrbianPaymentMethod O BPMConfig Use this parameter to set the Orbian payment method.

OrbianPaymentMethodDescription

Orbian BPMConfig Use this parameter to provide a description for the Orbian payment method.

R3LS T90CLNT090 BPMConfig Use this parameter to set the default SAP ERP 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 Network Buyer Account. In such cases, the System ID will be obtained from this parameter.

BusinessSystem BS_SAPR3_50 Lookup Use the name of the Business System in cases that involve a Single ERP configuration.

CommunicationChannel

RFC_Lookup_Receiver Lookup This denotes the name of 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.

DefaultLanguageCode EN BPMConfig If the PO Idoc message from the SAP ERP system does not contain a value for the language code, then the value of this parameter will be used to populate the target cXML.





PurchaseOrderDocTypes NB BPMConfig This variable must contain the value for the SAP document type for purchase orders. NB is the default doctype in the SAP system. However, customers can have a different doc type assigned to their purchase orders.

NoteIf you want to maintain multiple doc types for purchase orders, you must specify NB, NA,AS in the Value for XI field.

BlanketOrderDocType LP BPMConfig This variable must contain the value for the SAP document type for blanket orders. LP is the default doctype in the SAP system. However, customers can have a different doc type assigned to their blanket orders.




ISU_ERP_INV_Canceled_Rejected_Status

canceled/rejected In the SAP ERP system, when an invoice fails to get created, the status code 423 and status rejected are sent to Ariba Network. However, if a user cancels an invoice in SAP ERP system, then the status code 200 and status canceled instead of rejected are sent to Ariba Network.

If you are an existing customer and want to continue using the canceled status when an invoice is canceled in the SAP ERP system, then you are not required to make any changes as the default value of this variable is set to canceled. However, if you want to send the rejected status when a user cancels an invoice in the SAP ERP system, then you must set the value of this variable to rejected.

NoteNew customers are recommended to set the value of this variable to rejected.

DefaultRequesterEmailID The email ID of the requester in the SAP ERP system.

DefaultPreparerEmailID The email ID of the preparer in the SAP ERP system.

3.16.5 Configure the mappings between business system and logical system names

In the value mappings, use the following parameters to configure the mappings between business systems and logical systems.

Source:

● Agency: LogSys_Source



● Scheme: Lookup● Value: Logical System Name

Target:

● Agency: BusSys_Target● Scheme: Lookup● Value: Business System Name

NoteThe Group Name is not required.

The following table shows an example of values.

LogSys_Source BusSys_Target

T90CLNT090 BS_SAP_46C

T47CLNT800 BS_SAP_47

NoteIn the case of Multi-ERP implementation, additional value mappings need to be defined. For more information, see the “Linking Multiple SAP instances with Ariba Network” [page 133] section.

3.16.6 Configuring currency mapping

You can configure the currency precision maintained in the TURX table on your SAP Process Integration system. By default, the precision for currencies is two decimal places.

For example, when a purchase order is created, the EKPO table is updated with the purchase order information. If the currency for one of the line items is 10.00000, the value stored in the EKPO table is 100000.00. Currencies having more than two decimal places show the NETPR value adjusted to two decimal places incorrectly.

To maintain precision in currencies correctly, you must preserve the value mappings for currencies in the TCURX table. Enter the values for the following parameters:

Source Values:

Agency: ERP_Currency

Scheme: Currency

Target Values:

Agency: Currency_Precision

Scheme: Currency


Here is an example of how the precision for currencies are maintained:

Value for Currency_Precision Values for the ERP_Currency Group Name

0 JPY Currency

5 USDN Currency

3 PKT Currency

0 TWD Currency

3.16.7 Configuring state code mapping

You can configure the value mapping to process the State code in the ShipTo, Bill To, and Contact addresses in the purchase order correctly. To do this, you need to maintain the value mapping for the State Description or State Code as follows:

● When the value for the GetRegionCodeDescription is set to YES, then only the description for the Region or State code appears.

● If you do not maintain a value for the GetRegionCodeDescription, only the Region or State code appears.

Ensure to maintain the following value mapping under the XI_GLOBAL and Group Name as RegionCode:

Agency Scheme Value

XI_Global GlobalVariable GetRegionCodeDescription

XI GlobalVariable Yes

3.16.8 How to maintain the value mapping to support logical systems in SAP Process Integration

Context

To process documents through the logical system, maintain the value mapping for the logical system in the SAP Process Integration.

Procedure

1. In the Tools menu, click Value Mapping.2. In the Display Value Mapping window enter the Agency and Scheme values for the source and target in

the respective fields, as follows:



Agency Scheme Value

XI_Global GlobalVariable IsLogicalSystemEnabled

XI GlobalVariable yes

3. Specify the logical system name as follows:

Agency Scheme Value

XI_Global GlobalVariable R3PartnerProfileLS

XI GlobalVariable Name of the logical system

4. (Mandatory if you are a buyer using multiple ERP systems) In the Display Value Mapping Agencies page, map the logical system to the system ID of the multiple ERP systems (business systems) with the following values:

Agency Scheme Value For SystemIDFrom_cXML

SystemIDFrom_cXML Lookup System ID of the ERP system

Agency Scheme

Value For SenderPartner_LogicalSystem Group Name

SenderPartner_LogicalSystem

Lookup Name of the logical system SystemIDFrom_cXML

3.17 How to create a new value mapping table

Context

Create a new value mapping table if the Agency/Scheme is not available.

Procedure

1. In the Tools menu, click Value Mapping.2. In the Display Value Mapping window enter the Agency and Scheme values for the source and target in the

respective fields, as follows:

○ Source Values ForAgency: UOM_ERPScheme: UOM

○ Target Values ForAgency: UOM_ISOScheme: UOM


3. Click Display.4. Click the Change/Edit button to bring the table into Edit Mode.5. Click on the ‘+’ icon to add the Value Mappings.



4 Topics about configuring integration scenarios

About configuring integration scenarios in the integration directory [page 87]

Topics about configuring integration scenarios in the integration directory [page 89]

Purchase order integration scenario [page 114]

Change purchase order integration scenario [page 116]

Order confirmation integration scenario [page 118]

Ship notice integration scenario [page 119]

Service sheet and service sheet response integration scenario [page 120]

Service sheet response integration scenario [page 121]

Invoice integration scenario [page 122]

Order inquiries integration scenario [page 123]

Scheduling agreement release integration scenario [page 123]

Invoice status update integration scenario [page 124]

ERP-initiated invoice integration scenario [page 125]

Receipt integration scenario [page 125]

Receipt integration scenario for corrections and returns in receipts [page 126]

Payment proposal integration scenario [page 127]

PayMeNow integration scenario [page 127]

Payment remittance (outbound) integration scenario [page 128]

Liability transfer integration scenario [page 129]

Payment remittance request (inbound) integration scenario [page 130]

Payment remittance batch request integration scenario [page 130]

Requisition request integration scenario [page 131]

Request for quotation integration scenario [page 132]

4.1 About configuring integration scenarios in the integration directory

This section describes how to import and configure the integration scenarios in the SAP Process Integration 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. Ensure that the Design package is imported into your system and ready before you run these steps.

Setting up Ariba Network adapter for SAP NetWeaverTopics about configuring integration scenarios PUBLIC 87

If you are using a SAP Process Integration version that is higher than SAP BASIS 7.10, then you must ensure that you edit the software component version for the communication channel template to avoid receiving the following error: "Software component version with name SAP BASIS 7.10 not found. See error log for details."

NoteDo not activate the Change Lists feature of Integration Builder Configuration Tool until all the configuration steps are completed.

You can configure the integration scenarios for the supported document transactions on the SAP Process Integration as a Single Stack (Java only) or Dual Stack (ABAP and Java) from version 7.3 onwards. If you are configuring the integration scenarios in the single stack Java only instance, as part of generation of objects, the Configuration wizard generates only one object called Integrated Configuration. However, in case of dual stack instance, as part of generation of objects, the Config wizard generates four objects, Receiver Determination, Interface Determination, Receiver Agreement, and Sender Agreement.

● If you configure the integration scenarios on a single stack, configure the IDoc in the Communication Channel in the Integrated Configuration object.

● If you configure the integration scenario on a dual stack, configure the IDoc and the software component version in the Sender Agreement and Receiver Agreement objects for the Communication Channel. For more information, see the section for the required document transaction.

4.1.1 How to configure the software component version for communication channel templates

Context

If you are using a SAP Process Integration version that is higher than SAP BASIS 7.10, then you must ensure that you edit the communication channel template to avoid receiving an error.

Important: Ensure that you have the necessary options enabled for the Object Properties on the Software Component Version page that allows you to edit the communication channel template.

Procedure

1. Go to the Enterprise Service Builder and edit each of the communication channel templates for the http://ariba.com/xi/ASN/CommonBasis Software Component Version:

○ CCT_IDOC_RECEIVER○ CCT_RFC_LOOKUP_RECEIVER

2. Double click the required communication channel template. The Display Communication Channel Template page appears.

3. In the Parameters tab, click the Display Input Help button in the Adapter Type field. The Choose Adapter Metadata page appears.

4. Choose the common Basis version for each of the communication channel templates.


Topics about configuring integration scenarios

5. Double click each of the following communication channel template. The Display Software Component Version page appears.

Software Component VersionCommunication Channel Template Adapter Type Namespace

ARIBA_NETWORK_ADAPTER, CIx of ariba.com

CCT_RFC_Lookup_Receiver

RFC http://ariba.com/xi/ASN/CommonBasis

ARIBA_NETWORK_ADAPTER, CIx of ariba.com

CCT_IDoc_Receiver IDOC http://ariba.com/xi/ASN/CommonBasis

4.2 Topics about configuring integration scenarios in the integration directory

Integration scenarios for outbound and inbound transactions [page 89]

Workflow for configuring the integration scenario for all inbound and outbound transactions [page 90]

Topics about configuring outbound transactions [page 90]

Topics about configuring inbound transactions [page 101]

Enabling TLS support [page 111]

4.2.1 Integration scenarios for outbound and inbound transactions

You can configure the integration scenarios for the following outbound and inbound transactions:

Outbound transactions

● Purchase order integration scenario [page 114]● Change Purchase Order Integration Scenario [page 116]● Order Inquiries Integration Scenario [page 123]● Scheduling Agreement Release Integration Scenario [page 123]● Invoice Status Update Integration Scenario [page 124]● ERP-Initiated Invoice Integration Scenario [page 125]● Receipt integration scenario [page 125]● Payment Proposal Integration Scenario [page 127]● Payment Remittance Integration Scenario [page 128]


● Payment remittance batch request integration scenario [page 130]● Requisition Request Integration Scenario [page 131]● Request for Quotation Integration Scenario [page 132]

Inbound transactions

● Order Confirmation Integration Scenario [page 118]● Ship notice integration scenario [page 119]● Service Sheet and Service Sheet Response Integration Scenario [page 120]● Invoice Integration Scenario [page 122]● PayMeNow Integration Scenario [page 127]● Liability transfer integration scenario [page 129]● Payment remittance request (inbound) integration scenario [page 130]

4.2.2 Workflow for configuring the integration scenario for all inbound and outbound transactions

Configuring the integration scenarios for the outbound and inbound transactions involves the following steps:

1. Transfer the Integration Scenario from the Integration Repository Enterprise Service Builder to the Integration Directory Integration Builder .

2. Configure the Integration Scenario. This configuration involves the following steps:1. Assigning the model.2. Assigning the components.3. Configuring the sender and receiver relations for individual connections.4. Generating the configuration objects.

3. Configure the Communication Channels.4. Activate the integration scenario.

For more information on configuring the integration scenario for inbound and outbound transactions, see Topics about configuring outbound transactions [page 90] .

Note● Ensure that the design package is imported into your system and ready before you run these steps.● All the steps of a configuration scenario section must be completed to fully configure a scenario.● If you are an existing customer, you must make changes to the existing configuration scenario and

rerun the steps for the configuration scenario.

4.2.3 Topics about configuring outbound transactions

How to transfer the integration scenarios for outbound transactions [page 91]



How to assign the model for outbound transactions [page 93]

How to assign components for outbound transactions [page 93]

How to configure the sender and receiver relations for individual connections for outbound transactions [page 94]

How to generate objects for outbound transactions [page 96]

How to configure the communication channels for outbound transactions [page 96]

How to configure the interface determination for transactions with Ariba Network [page 99]

How to activate the integration scenario [page 101]

4.2.3.1 How to transfer the integration scenarios for outbound transactions

Context

To configure the integration scenario, the first step is to transfer the integration scenario to the Integration Builder. The integration scenario is loaded into the Integration Repository when the design package has been imported.

Procedure

1. From the SAP Process Integration main page, select Integration Directory Integration Builder , and then login to the Configuration: Integration Builder application.

2. In the Integration Builder menu, select Tools Apply Model from ES Repository .3. In the first screen of the Transfer Model from ES Repository wizard, select Select Process Integration

Scenario.

4. Click the Name field, and then click the Display Input Help Input Help Input Help. The Select Process Integration Scenario from Enterprise Service Repository page appears.

5. Select the process integration scenario for the SAP Ariba cloud integration version for the following outbound transactions:

○ CatalogName: AR_CatalogUploadNamespace: http://ariba.com/xi/ASN/CatalogSoftware Component Version: ARIBA_CATALOG_SYNDICATION, CIx of ariba.com

○ ERP InvoiceName: AR_ERPInvoice_ReceiveNamespace: http://ariba.com/xi/ASN/ERPInvoiceSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Invoice Status UpdateName: AR_InvoiceStatusUpdate_ReceiveProxy


Namespace: http://ariba.com/xi/ASN/InvoiceStatusUpdateProxySoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Order InquiryName: AR_OrderEnquiry_ReceiveNamespace: http://ariba.com/xi/ASN/OrderEnquirySoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Purchase Order Name: AR_PurchaseOrder_ReceiveNamespace: http://ariba.com/xi/ASN/PurchaseOrderSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Payment ProposalName: AR_PaymentProposal_Receive_ProxyNamespace: http://ariba.com/xi/ASN/PaymentProposalProxySoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Payment RemittanceName: AR_PaymentRemittance_ReceiveNamespace: http://ariba.com/xi/ASN/PaymentRemittanceSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Payment Remittance Batch RequestName: AR_PaymentRemittanceBatchRequest_ReceiveNamespace: http://ariba.com/xi/ASN/PaymentRemittanceBatchRequestSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ ReceiptsName: AR_Receipt_Receive_ProxyNamespace: http://ariba.com/xi/ASN/ReceiptProxySoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Request for QuotationName: AR_QuoteRequest_ReceiveNamespace: http://ariba.com/xi/ASN/QuoteRequestSoftware Component Version: ARIBA_SOURCING_ADAPTER, CIx of ariba.com

○ RequisistionName: AR_Requisition_ReceiveNamespace: http://ariba.com/xi/ASN/RequisitionSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Scheduling Agreement ReleaseName: AR_ScheduleAgreementRelease_ReceiveNamespace: http://ariba.com/xi/ASN/ScheduleAgreementReleaseSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Service Sheet ResponseName: AR_ServiceEntrySheetResponse_ReceiveProxyNamespace: http://ariba.com/xi/ASN/ServiceEntrySheetResponseProxySoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

6. Click Continue.7. If required, change the name of the scenario for the Integration Directory.8. Click Finish and then Close.

Once the integration scenario transfer is completed, the Model Configurator window appears.



NoteYou can also configure integration scenarios for the Sourcing Award to Contracts integration scenario. For more information on Request for Quotations and Sourcing Award to Contracts, see the RFQ and award integration with SAP Ariba Sourcing guide.

4.2.3.2 How to assign the model for outbound transactions

Procedure

1. In the Model Configurator window, click the Select Component View button, and then click Apply to choose the unique model that is selected by default.

2. After selecting the model, assign components to the application components for the selected integration scenario.

4.2.3.3 How to assign components for outbound transactions

Procedure

1. In the Model Configurator, click the Assign Component button.2. In the Assign Components window, select the Business System Components for A2A tab to assign

business systems for the integration scenario.3. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is

available.4. Click the row under the Communication Component column, then click the Value List pull-down menu

and select Value List <F4>. Select the communication component name for the business system of your SAP Process Integration system, from the selection list and click Apply.

NoteIf you have multiple ERP systems, add the multiple communication components defined for your multiple SAP Process Integration systems by repeating the Step 3 and 4.

5. Click the Next Application Component button (the right arrow) to go to the next screen on the window.6. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is

available.7. Click the row under the Communication Component column, then click the Value List pull-down menu

and select Value List <F4>. Select the communication component name for the business system for Ariba Network, from the selection list and click Apply.

8. Click the Save Settings button.


4.2.3.4 How to configure the sender and receiver relations for individual connections for outbound transactions

Procedure

1. In the Model Configurator, click the Configure Connections button. You must assign Communication Channels to set up the connections.

2. In the Connections from Component Assignment tab in the Configure Connection window, click the empty Communication Channel cell corresponding to the business system for Ariba Network in the Sender Business System Components table.

3. Click the Create Communication Channel button (the icon at the top left), and then select Create Communication Channel with Template to start the Create Communication Channel wizard.

4. Click Continue.5. On the next page, click the Name field and then click the Input Help pull-down menu.6. Select the Communication Channel Templates for the following transactions:

○ CatalogName: CCT_CatalogUpload_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/CatalogSoftware Component Version: ARIBA_CATALOG_SYNDICATION, CIx of ariba.com

○ ERP InvoiceName: CCT_ERPInvoice_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/ERPInvoiceSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Invoice Status UpdateName: CCT_InvoiceStatusUpdateProxy_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/InvoiceStatusUpdateProxySoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Order InquiryName: CCT_OrderEnquiry_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/OrderEnquirySoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Purchase Order Name: CCT_PurchaseOrder_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/PurchaseOrderSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Payment ProposalsName: CCT_PaymentProposalProxy_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/PaymentProposalProxySoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Payment RemittanceName: CCT_PaymentRemittance_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/PaymentRemittanceSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com



○ Payment Remittance Batch RequestName: CCT_PaymentRemittanceBatchRequest_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/PaymentRemittanceBatchRequestSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ ReceiptsName: CCT_ERPReceiptProxy_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/ReceiptProxySoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Request for QuotationName: CCT_QuoteRequest_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/QuoteRequestSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ RequisistionName: CCT_Requisition_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/RequisitionSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Scheduling Agreement ReleaseName: CCT_ScheduleAgreementRelease_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/ScheduleAgreementReleaseSoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

○ Service Sheet ResponseName: CCT_ServiceEntrySheetResponseProxy_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/ServiceEntrySheetResponseProxySoftware Component Version: ARIBA_NETWORK_ADAPTER, CIx of ariba.com

TipFor customizations that you implement, use the software component ARIBA_NETWORK_CUSTOM_ADAPTER 1.0 of ariba.com.

7. Click Continue.8. You can also choose to modify the channel names. Click Finish.

TipIf you have already created and configured a Sender channel for the business system for Ariba Network in another transaction, you can create the communication channel by copying from a channel that has already been configured.

9. In the Connections from Component Assignment tab, click the empty Communication Channel cell corresponding to the business system of your ERP Process Integration system in the Receiver Business System Components table.

10. Click on the Value List drop down and select Value List <F4>. Select the CC_Idoc_Receiver communication channel from the selection list and click Apply.

11. Click the Activate All Connections button, and then click OK.12. Click the Save Settings button.


4.2.3.5 How to generate objects for outbound transactions

Procedure

1. In the Model Configurator, click the Create Configuration Object button.2. In the Create Configuration Object window, do the following:

○ Click Generation in the General section.○ Select the Receiver Determination, Interface Determination, and Sender/Receiver Agreement

check boxes in the Scope of Generation section.3. Click Create New in the Change List for Generated Objects section. The text box already contains an

object name that you can use or modify.4. Click Start to begin generating objects.5. After the object generation is complete, click Apply to save the new configuration settings. Close the log

that is created without saving. You can save it, if required.

Results

Note● Generating the objects creates the configuration objects if they do not yet exist. If they already exist,

they are reused and enhanced, if required. You can also simulate generation for test purposes.

4.2.3.6 How to configure the communication channels for outbound transactions

Context

Configure the communication channel for each of the integration scenarios.

Procedure

1. Go to the Configuration: Integration Builder page to view the communication channels for the integration scenario. Open the required configuration scenario and then click the Objects tab.

2. In the Communication Channel list, double-click the required communication channel to open it: [To be updated]

3. In the Communication Channel list, double-click the required outbound communication channel to open it:



○ Catalog|< Name of the Business System for Ariba Network> | CCT_CatalogUpload_cXML_Receiver

○ ERP Invoice|< Name of the Business System for Ariba Network> | CC_ERPInvoiceProxy_cXML_Receiver

○ Invoice Status Update|< Name of the Business System for Ariba Network> | CC_InvoiceStatusUpdateProxy_cXML_Receiver

○ Order Inquiry|< Name of the Business System for Ariba Network> | CC_OrderEnquiry_cXML_Receiver

○ Purchase Order |< Name of the Business System for Ariba Network> | CC_PurchaseOrder_cXML_Receiver

○ Payment Proposals|< Name of the Business System for Ariba Network> | CC_PaymentProposalProxy_cXML_Receiver

○ Payment Remittance|< Name of the Business System for Ariba Network> | CC_PaymentRemittance_cXML_Receiver

○ Payment Remittance Batch Request|< Name of the Business System for Ariba Network> | CCT_PaymentRemittanceBatchRequest_cXML_Receiver

○ Receipts|< Name of the Business System for Ariba Network> | CC_ERPReceiptProxy_cXML_Receiver

○ Request for Quotation|< Name of the Business System for Ariba Network> | CC_QuoteRequest_cXML_Receiver

○ Requisistion|< Name of the Business System for Ariba Network> | CC_Requisition_cXML_Receiver

○ Scheduling Agreement Release|< Name of the Business System for Ariba Network> | CC_ScheduleAgreementRelease_cXML_Receiver

○ Service Sheet Response|< Name of the Business System for Ariba Network> | CC_ServiceEntrySheetResponseProxy_cXML_Receiver


5. Choose the adapter metadata for the latest version of the SAP Ariba cloud integration in the Adapter Type field.

6. Click Apply.7. In the Backend System Type section, specify the System Type as “Buyer.” If you are configuring the

communication channel for the Catalog integration scenario, select "Supplier" as the System Type.


8. On the Parameters tab, set the parameters in the Authentication section to match your Ariba Network buyer account configuration.To enable TLS support, see Enabling TLS support [page 111].

9. Specify the request type for each of the outbound transactions in the Outbound Request Type field.○ Catalog: CatalogUploadRequest○ ERP Invoice: InvoiceCopyRequest○ Invoice Status Update: StatusUpdateRequest○ Order Inquiry: OrderStatusRequest○ Purchase Order: OrderRequest○ Payment Proposal: PaymentRequest○ Payment Remittance: PaymentRemittanceRequest○ Payment Remittance Batch Request: PaymentRemittanceRequest○ Receipts: ReceiptRequest○ Request for Quotation: QuoteRequest○ Requisition: PurchaseRequisitionRequest○ Scheduling Agreement Release: SchedulingAgreementReleaseRequest○ Service Sheet Response: EntrySheetUpdateRequest

Note○ When you select the outbound request type for the ERP invoice, ensure that you also check the Is

CopyRequest field.○ If you created the channel by copying from an existing channel, you must change the request type

for each of the transactions to the <Name of the transaction request - for example, Invoice> in the Outbound Request Type field.

10. Choose from the following DTDs associated to the outbound request type in the cXML Configuration section:○ Default value: cXML.dtd for CatalogUploadRequest, StatusUpdateRequest, OrderRequest,

PurchaseRequisitionRequest, SchedulingAgreementReleaseRequest, and EntrySheetUpdateRequest○ Specify PaymentRemittance.dtd for PaymentRequest, PaymentRemittanceRequest, and

PaymentRemittanceBatchRequest.○ Specify Fulfill.dtd for ReceiptRequest and OrderStatusRequest○ Specify Quote.dtd for QuoteRequest○ Specify InvoiceDetail.dtd for InvoiceCopyRequest

11. Enter a value in the Credentials field. If required, edit the other parameters.

NoteWhen you configure the communication channel for the Requisition or Request for Quotation transaction, ensure that you also check the To Credentials Same as From Credentials field. This allows you to keep the values you specify for the To Credentials the same as the From Credentials in the transaction request documents.

12. Update the cXML version parameter to the latest applicable version. For more information about the cXML adapter parameters, see cXML Adapter Parameters [page 361].



To ensure that attachments in service sheets are processed by the adapter and sent to SAP ERP, in the communication channel for the service sheet transaction, you must select Embedded in cXML option for the Attachment Processing Mode parameter.

13. Save the changes.

4.2.3.7 How to configure the interface determination for transactions with Ariba Network

Context

Configure the interface determination settings to enable mapping enhancements for inbound and outbound transactions.

Procedure

1. In the Objects tab, go to the Interface Determination section and then click the interface name for each of the following outbound transactions to open it:

○ Catalog| < Name of the Business System for the SAP ERP> | MIn_Async_CatalogUpload |< Name

of the Business System for Ariba Network>○ ERP Invoice

If you are using the SAP Ariba cloud integration release 6.0 and later, specify:| < Name of the Business System for the SAP ERP> | MIIn_Async_ERPInvoice_cXML |<

Name of the Business System for Ariba Network>○ Invoice Status Update

| < Name of the Business System for the SAP ERP> | MIOt_AS_InvstaUpdt_Itm |< Name of the Business System for Ariba Network>

○ Order Inquiry| < Name of the Business System for the SAP ERP> | ORDERS.ORDERS05./ARBA/ORDENQ

|< Name of the Business System for Ariba Network>○ Purchase Order

| < Name of the Business System for the SAP ERP> |ORDERS.ORDERS05 |< Name of the Business System for Ariba Network>

○ Payment Proposals| < Name of the Business System for the SAP ERP> | MIOut_Async_PayProp |< Name of the

Business System for Ariba Network>○ Payment Remittance

| < Name of the Business System for the SAP ERP> | REMADV.PEXR2001 |< Name of the Business System for Ariba Network>


○ Payment Remittance Batch Request| < Name of the Business System for the SAP ERP> |

CollectivePaymentOrderBulkRequest_Out |< Name of the Business System for Ariba Network>

○ Receipts| < Name of the Business System for the SAP ERP> | MIOut_Async_Receipt_Item |< Name

of the Business System for Ariba Network>○ Request for Quotation

| < Name of the Business System for the SAP ERP> | REQOTE.ORDERS05./ARBA/RFQ |< Name of the Business System for Ariba Network>

○ Requisition| < Name of the Business System for the SAP ERP> | MI_Out_Req |< Name of the Business

System for Ariba Network>○ Scheduling Agreement Release

| < Name of the Business System for the SAP ERP> | DELINS.DELFOR02./ARBA/DELFOR02|< Name of the Business System for Ariba Network>

○ Service Sheet Response| < Name of the Business System for the SAP ERP> | MIOt_AS_SrvEntSheetResp_Itm |<

Name of the Business System for Ariba Network>2. In the Receiver Interfaces section of the Edit Interface Determination window, click the operation

mapping value under the Operation Mapping column. Then click the Value List pull-down menu and select Value List.

3. Select the operation mapping for the following inbound transactions:

○ CatalogNot applicable

○ ERP InvoiceIf you are using the SAP Ariba cloud integration release 6.0 and later, specify:○ IFM_FIDCCP_FIDCCP02_ARBA_2_cXML to send ERS (Evaluated Receipt Settlement), MIRO, or

MM invoices.○ IFM_GSVERF_GSVERF03_ARBA_2_cXML to send FI invoices.

○ Invoice Status UpdateIFM_InvStatUpdt_Item_2_cXML

○ Order InquiryIFM_ORDERS_ORDENQ_ARBA_2_cXML

○ Purchase Order IFM_ORDERS_ORDERS05_2_cXML

○ Payment ProposalsIFM_PaymentProposal_Item_2_cXML

○ Payment RemittanceIFM_REMADV_PEXR2001_2_cXML

○ Payment Remittance Batch RequestIFM_CollectivePaymentOrderBulkRequest_2_cXML

○ ReceiptsIFM_Receipt_cXML



○ Request for QuotationIFM_REQOTE_ORDERS05_ARBA_RFQ_2_cXML

○ RequisitionIFM_Requisition_cXML

○ Scheduling Agreement ReleaseIFM_DELINS_DELFOR02_ARBA_2_cXML

○ Service Sheet ResponseIFM_SrvEntSheetResp_Item_2_cXML

4. Click Apply.5. The Multiplicity column displays the value “0..unbounded”.

6. Save and activate the interface determination settings.

NoteConfiguring the Interface Determination is a mandatory step if you must configure the mappings for outbound transactions.

4.2.3.8 How to activate the integration scenario

Context

The final configuration step in SAP Process Integration is to activate your newly created scenario.

Procedure

Using the Change List tab on the main application screen, activate all the Change Lists containing the objects created and modified during the component setup.

This completes the configuration of the integration scenarios in SAP Process Integration.

4.2.4 Topics about configuring inbound transactions

How to transfer the integration scenario for inbound transactions [page 102]

How to assign the model for inbound transactions [page 103]

How to assign components for inbound transactions [page 103]

How to configure the sender and receiver relations for individual connections for inbound transactions [page 104]

How to generate objects for inbound and outbound transactions [page 105]

How to configure the communication channels for inbound transactions [page 106]


How to configure the receiver determination settings for inbound transactions [page 107]

How to configure the interface determination for inbound transactions [page 108]

How to activate the integration scenario [page 111]

4.2.4.1 How to transfer the integration scenario for inbound transactions

Context

The first step to configure the integration scenario is to transfer the integration scenario to the Integration Builder. The integration scenario is loaded into the Integration Repository where the design package has been imported.

Procedure

1. From the SAP Process Integration main page, select Integration Directory Integration Builder , and then login to the Configuration: Integration Builder application.

2. In the Integration Builder menu, select Tools Apply Model from ES Repository .3. In the first screen of the Transfer Model from ES Repository wizard, select Select Process Integration

Scenario.

4. Click the Name field, and then click the Display Input Help Input Help .

The Select Process Integration Scenario from Enterprise Service Repository page appears.5. Select the process integration scenario for the cloud integration version for the following inbound

transactions:

○ Order confirmationName: AR_OrderConfirmation_SendNamespace: http://ariba.com/xi/ASN/OrderConfirmationSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com

○ Ship noticeName: AR_AdvanceShipNotice_DELVRY06_SendNamespace: http://ariba.com/xi/ASN/AdvanceShipNotice_DELVRY06Software Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com

○ Cancel ship noticeName: AR_AdvanceShipNotice_InboundDeliveryCancelRequest_SendNamespace: http://ariba.com/xi/ASN/AdvanceShipNotice_DELVRY06Software Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com

○ InvoiceName: AR_Invoice_Invoic02Namespace: http://ariba.com/xi/ASN/InvoiceSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com



○ Service sheet Name: AR_ServiceEntrySheet_SendNamespace: http://ariba.com/xi/ASN/ServiceEntrySheetSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com

○ Pay me nowName: AR_PayMeNow_SendNamespace: http://ariba.com/xi/ASN/PayMeNowSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com

○ Liability transferName: AR_LiabilityTransfer_SendNamespace: http://ariba.com/xi/ASN/LiabilityTransferSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com

○ Remittance adviceName: AR_RemittanceAdvice_SendNamespace: http://ariba.com/xi/ASN/RemittanceAdviceSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com



4.2.4.2 How to assign the model for inbound transactions

Procedure


2. After choosing the model, assign components to the application components for the chosen integration scenario.

4.2.4.3 How to assign components for inbound transactions

Procedure

1. In the Model Configurator, click the Assign Component button.2. In the Assign Components window, choose the Business System Components for A2A tab to assign


available.


4. Click the row under the Communication Component column, then click the Value List dropdown menu and choose Value List <F4>. Choose the communication component name for the business system of your SAP Process Integration, from the selection list and click Apply.



available.7. Click the row under the Communication Component column, then click the Value List dropdown menu

and choose Value List <F4>. Choose the communication component name for the business system for Ariba Network, from the selection list and click Apply.


4.2.4.4 How to configure the sender and receiver relations for individual connections for inbound transactions

Procedure



3. Click the Create Communication Channel button (the icon at the top left), and then select Create Communication Channel with Template to start the Create Communication Channel wizard.

4. Click Continue.5. On the next page, click the Name field and then click the Input Help pull-down menu.6. Select the Communication Channel Templates for the following transactions:

○ Order ConfirmationName: CCT_OrderConfirmation_cXML_SenderNamespace: http://ariba.com/xi/ASN/OrderConfirmationSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com

○ Ship NoticeName: CCT_AdvanceShipNotice_DELVRY06_cXML_Sender Namespace: http://ariba.com/xi/ASN/AdvanceShipNotice_DELVRY06Software Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com

○ InvoiceName: CCT_Invoice_cXML_SenderNamespace: http://ariba.com/xi/ASN/InvoiceSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com



○ Service SheetName: CCT_ServiceEntrySheet_cXML_SenderNamespace: http://ariba.com/xi/ASN/ServiceEntrySheetSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com

○ Pay Me NowName: CCT_PayMeNow_cXML_SenderNamespace: http://ariba.com/xi/ASN/PayMeNowSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com

○ LiabilityTransferName: CCT_LiabilityTransfer_cXML_SenderNamespace: http://ariba.com/xi/ASN/LiabilityTransferSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com

○ Remittance AdviceName: CCT_RemittanceAdvice_cXML_SenderNamespace: http://ariba.com/xi/ASN/RemittanceAdviceSoftware Component Version: ARIBA_NETWORK_ADAPTER CIX of ariba.com



9. In the Connections from Component Assignment tab, click the empty Communication Channel cell corresponding to the business system of your ERP Process Integration system in the Receiver Business System Components table.

10. Click on the Value List drop down and select Value List <F4>. Select the CC_Idoc_Receiver communication channel from the selection list and click Apply.


4.2.4.5 How to generate objects for inbound and outbound transactions

Procedure


○ Click Generation in the General section.○ Choose the Receiver Determination, Interface Determination, and Sender/Receiver Agreement

checkboxes in the Scope of Generation section.3. Click Create New in the Change List for Generated Objects section. The text box already contains an

object name that you can use or modify.


4. Click Start to begin generating objects.5. After the object generation is complete, click Apply to save the new configuration settings. Close the log


Results



4.2.4.6 How to configure the communication channels for inbound transactions

Context

Configure the communication channel for each of the integration scenarios.

Procedure

1. Go to the Configuration: Integration Builder page to view the communication channels for the integration scenario. Open the required configuration scenario and then click the Objects tab.

2. In the Communication Channel list, double-click the required inbound communication channel to open it:

○ Order Confirmation|< Name of the Business System for Ariba Network> | CC_OrderConfirmation_cXML_Sender

○ Ship Notice|< Name of the Business System for Ariba Network> | CC_AdvanceShipNotice_DELVRY06_cXML_Sender

○ Invoice|< Name of the Business System for Ariba Network> |CC_Invoice_cXML_Sender

○ Service Sheet|< Name of the Business System for Ariba Network> | CC_ServiceEntrySheet_cXML_Sender

○ PayMeNow|< Name of the Business System for Ariba Network> | CC_PayMeNow_cXML_Sender

○ Liability Transfer|< Name of the Business System for Ariba Network> | CC_PayMeNow_cXML_Sender

○ Remittance Advice



|< Name of the Business System for Ariba Network> | CC_RemittanceAdvice_cXML_Sender


4. Choose the adapter metadata for the latest version of the SAP Ariba cloud integration in the Adapter Type field.

5. Click Apply.6. In the Backend System Type section, specify the System Type as “Buyer.”7. On the Parameters tab, set the parameters in the Authentication section to match your Ariba Network

buyer account configuration.To enable TLS support, see Enabling TLS support [page 111].

8. Specify the request type for each of the inbound transactions in the Inbound Request Type field.○ Order Confirmation: ConfirmationRequest○ Ship Notice: ShipmentNoticeRequest○ Invoice: InvoiceDetailRequest○ Service Sheet: ServiceEntryRequest○ Pay Me Now: PayMeNowRequest○ LiabilityTransfer: PayMeNowRequest○ Remittance Advice: PaymentRemittanceRequest

NoteIf you created the channel by copying from an existing channel, you must change the request type for each of the transactions to the <Name of the transaction request - for example, Invoice> in the Inbound Request Type field.

9. Enter a value in the Credentials field. If required, edit the other parameters.10. Update the cXML version parameter to the latest applicable version. For more information about the cXML

adapter parameters, see cXML Adapter Parameters [page 361].To ensure that attachments in service sheets are processed by the adapter and sent to SAP ERP, in the communication channel for the service sheet transaction, you must select Embedded in cXML option for the Attachment Processing Mode parameter.


4.2.4.7 How to configure the receiver determination settings for inbound transactions

Context

Configure the receiver determination settings manually, for the receiver. Retain the default settings for the other receivers.

NoteThis configuration is required only if you have multiple ERP systems.


Procedure

1. In the Objects tab, go to the Receiver Determination, and click the icon next to the Condition field, to start the Condition Editor.

2. In the Condition Editor window, specify the left operand of the condition as follows:

○ Click the icon next to the Left Operand field to open the Expression Editor.○ Select the XPath option, and enter the XPath for the corresponding transaction. You can refer to

payload to form the desired Xpath. For example:○ For Ariba Network, the XPath for dispatch delivery notice would be:

/n0:DsptchdDelivNotifMsg/MessageHeader/RecipientParty/InternalID○ For SAP Ariba Procurement solutions, the company code Xpath for PO would be:

/n0:ARBCIG_BAPI_PO_CREATE1/PO_HEADER/COMP_CODE○ This path should be displayed in the XPath Expression field.○ Click OK to return to the Expression Editor.○ Select the “=” operator in the Operator column.○ Select the Right Operand field and enter “SystemID”.

3. You can add another condition by clicking the Insert Expression option.4. Click OK to close the Condition Editor.5. Click the icon next to the Communication Component field to start the Choose Communication

Component window, and select the Communication Component corresponding to the Logical System Name you specified in the Condition field.

NoteIf you have multiple ERP systems, repeat the steps for all your SAP ERP instances.

6. Save the Receiver Determination settings.

4.2.4.8 How to configure the interface determination for inbound transactions

Context

Configure the interface determination settings to enable mapping enhancements for inbound transactions.

Procedure

1. In the Objects tab, go to the Interface Determination section and then click the interface name for each of the following inbound transactions to open it:

○ Order Confirmation| < Name of the Business System for Ariba Network> |

MIOut_Async_OrderConfirmation_cXML |< Name of the Business System for the SAP ERP>



○ Ship Notice| < Name of the Business System for Ariba Network> |

MIOut_Async_AdvanceShipNotice_DELVRY06_cXML |< Name of the Business System for the SAP ERP>

○ Invoice| < Name of the Business System for Ariba Network> | MIOut_Async_Invoice_Invoic02_cXML|< Name of the Business System for the SAP ERP>

○ Service Sheet | < Name of the Business System for Ariba Network> |

MIOut_Async_ServiceEntrySheet_cXML |< Name of the Business System for the SAP ERP>○ Pay Me Now

| < Name of the Business System for Ariba Network> | MIOut_Async_PayMeNow_cXML |< Name of the Business System for the SAP ERP>

○ Liability Transfer|< Name of the Business System for Ariba Network | MIOut_Async_PayMeNow_cXML |<

Name of the Business System for the SAP ERP>○ Remittance Advice

|< Name of the Business System for Ariba Network | SI_RemittanceRequest_cXML_Async_Out |< Name of the Business System for the SAP ERP>

2. In the Receiver Interfaces section of the Edit Interface Determination window, click the operation mapping value under the Operation Mapping column. Then click the Value List pull-down menu and select Value List.

3. Select the operation mapping for the following inbound transactions:

○ Order confirmation○ SAP Ariba cloud integration release 7.0 and higher: IFM_cXML_2_ORDRSP_ORDERS05○ SAP Ariba cloud integration release 7.0 HF 10 and higher: IFM_cXML_2_ORDRSP_ORDERS05_1

○ Ship noticeIFM_cXML_2_DESADV_DELVRY06Interface determination condition: /cXML/Request/ShipNoticeRequest/ShipNoticeHeader/@operation ≠ delete

○ Cancel ship noticeIFM_cXML_2_InboundDeliveryCancelRequestInterface determination condition: /cXML/Request/ShipNoticeRequest/ShipNoticeHeader/@operation = delete

○ InvoiceIFM_cXML_2_INVOIC_INVOICE02_INVOIC02Interface determination condition: /cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader/InvoiceDetailHeaderIndicator/@isPriceBasedLineLevelCreditMemo ≠ yes AND /cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader/@purpose ≠ lineLevelCreditMemo OR /cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader/@operation ≠ = delete

○ Dynamic discounting credit memoIFM_cXML_2_CreditMemo_Attachment_CancellationInterface determination condition: /cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader/InvoiceDetailHeaderIndicator/


@isPriceBasedLineLevelCreditMemo = yes AND /cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader/@purpose = lineLevelCreditMemo OR /cXML/Request/InvoiceDetailRequest/InvoiceDetailRequestHeader/@operation = delete

○ Service sheet IFM_cXML_2_BAPI_ENTRYSHEET_CREATE

○ Pay me nowIFM_cXML_2_FIDCCH_FIDCCH01

○ Liability transfer○ IFM_cXML_2_LiabilityTransfer○ IFM_cXML_2_FIDCCH_FIDCCH01

○ Remittance adviceIFM_cXML_2_RemittanceAdvice

4. (Required for order confirmation)Do one of the following:

○ Select the Order confirmation operational mapping, IFM_cXML_2_ORDRSP_ORDERS05 and open the condition editor. Click the icon next to the Condition field, to start the Condition Editor.○ In the Condition Editor window, specify the left operand of the condition as follows:

○ Click the icon next to the Left Operand field to open the Expression Editor.○ Select the XPath option, and then select the following XPath from the document tree: /cXML/

Request/ConfirmationRequest/ConfirmationHeader/@type.This path is displayed in the XPath Expression field.

○ Click OK to return to the Expression Editor.○ Select the ≠ operator in the Operator column.○ Select the Right Operand field and enter allDetail.

○ Select the Order confirmation operational mapping, IFM_cXML_2_ORDRSP_ORDERS05_1 and open the condition editor. Click the icon next to the Condition field, to start the Condition Editor.○ In the Condition Editor window, specify the left operand of the condition as follows:


Request/ConfirmationRequest/ConfirmationHeader/@type.This path is displayed in the XPath Expression field.

○ Click OK to return to the Expression Editor.○ Select the = operator in the Operator column.○ Select the Right Operand field and enter allDetail.

5. (Required for liability transfer) Select the PayMeNow operational mapping, IFM_cXML_2_FIDCCH_FIDCCH01 and open the condition editor. Click the icon next to the Condition field, to start the Condition Editor.○ In the Condition Editor window, specify the left operand of the condition as follows:


Request/PaymentProposalRequest/PaymentPartner/IdReference/@domain.This path is displayed in the XPath Expression field.

○ Click OK to return to the Expression Editor.○ Select the ≠ operator in the Operator column.○ Select the Right Operand field and enter financialInstitutionID.



6. (Required for liability transfer) Select the IFM_cXML_2_LiabilityTransfer and open the condition editor. Click the icon next to the Condition field, to start the Condition Editor.

○ Click the icon next to the Left Operand field to open the Expression Editor.○ Click the Add button to add a new line.○ Select the XPath option, and then select the following XPath from the document tree: /cXML/

Request/PaymentProposalRequest/PaymentPartner/IdReference/@domain .○ Select the = operator in the Operator column.○ Select the Right Operand field and enter financialInstitutionID.

7. Click Apply.8. The Multiplicity column displays the value 0..unbounded.

9. Save and activate the interface determination settings.

NoteConfiguring the Interface Determination is a mandatory step if you configure the mappings for inbound transactions.

4.2.4.9 How to activate the integration scenario

Context

The final configuration step in SAP Process Integration is to activate your newly created scenario.

Procedure

Using the Change List tab on the main application screen, activate all the Change Lists containing the objects created and modified during the component setup.

This completes the configuration of the integration scenarios in SAP Process Integration.

4.2.5 Enabling TLS support

CautionSAP Ariba recommends that you use the supported TLS 1.2 versions. SAP Ariba has discontinued support for TLS 1.0 or TLS 1.1 for outbound and inbound transactions. Customers cannot use the existing URLs with TLS 1.0 or TLS 1.1 for outbound and inbound transactions.

To enable Transport Layer Security (TLS) support, TLS 1.2, do the following:

● Implement SAP Note: 2284059 -Update of SSL library within NW Java server.



NoteIn the step 5 of the note, ensure that you specify client.maxProtocolVersion=TLS12

NoteSAP Ariba no longer uses the Legacy URL or Advanced URL. Customers must use the Integration URL for all outbound and inbound transactions.

SAP Ariba uses the Legacy URLs as the Browser URL for Ariba Network and SAP Ariba applications.

To implement hardened URL:

● Ensure that the cypher suites and TLS version 1.2 are available on the system. For a list of supported cypher suites, see the supported values for the parameter cipherSuitesEnabled in the section, Parameters for TLS.

● If you are using certificate-based authentications, install the SHA256 client certificate.● Import advanced RSA certificate from https://connect.ariba.com as the legacy client certificate server

URLs and server certificates have changed. For more information, see the section, SAP Ariba SHA-256 certificates.

NoteSAP Process Integration does not support Elliptic Curve Digital Signature Algorithm (ECDCA).

4.2.5.1 Parameters for TLS

The following table specifies the parameters required to enable TLS:

Parameters for TLS

Parameter name Description Supported values

httpsProtocolsEnabled

Specifies the protocol for HTTPS communication.

TLSv1.2 (for browser and hardened URLs)




Parameter name Description Supported values

cipherSuitesEnabled Specifies the cipher suites for TLS communication.

TipTo enhance the level of security, restrict the cipher suite support to a limited set of cipher suites that provide the highest level of security. You can specify only those cipher suites that you want to support when you set values for the cipherSuitesEnabled parameter.

● TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384● TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384● TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384● TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA● TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256● TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256● TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256● TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA● TLS_RSA_WITH_AES_256_GCM_SHA384● TLS_RSA_WITH_AES_256_CBC_SHA256● TLS_RSA_WITH_AES_256_CBC_SHA● TLS_RSA_WITH_AES_128_GCM_SHA256● TLS_RSA_WITH_AES_128_CBC_SHA256● TLS_RSA_WITH_AES_128_CBC_SHA

Related Information

SAP Ariba SHA-256 certificates [page 114]


4.2.5.2 SAP Ariba SHA-256 certificates

The following table lists the integration URLs. The URLs are applicable for TLS 1.2 that support both inbound and outbound integration for transaction documents:

SAP Ariba SHA-256 (commonly known as SHA-2) certificates

Data Center Integration URLs (RSA)

US ● s1-integration.ariba.com (for SAP Ariba Applications)

● service-2.ariba.com (for Ariba Network)

● certs1-integration.ariba.com● certservice-2.ariba.com

EU ● s1-integration-eu.ariba.com● service-2-eu.ariba.com (for Ariba Network)

● certs1-integration-eu.ariba.com

RU ● s1-integration-ru.ariba.com● service-2-ru.ariba.com (for Ariba Network)

● certs1-integration-ru.ariba.com

Related Information

Parameters for TLS [page 112]

4.3 Purchase order integration scenario

Configure the integration scenario for the purchase order transaction in the Integration Directory to be able to run the transaction for new purchase orders, changed purchase orders, and canceled purchase orders.

All the steps of a configuration scenario section must be completed to fully configure a scenario. To enable SAP ERP and SAP S/4HANA to send correct new, change, and cancel purchase order information to the Ariba Network adapter for SAP NetWeaver, you must configure the implicit enhancements.

NoteEnsure 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.

When a buyer manually specifies the delivery address, Ariba Network adapter for SAP NetWeaver processes the manually entered values in the delivery address field as follows:



● If a buyer manually selected the address ID, customer ID, or vendor ID in the Delivery Address tab, and then edited the existing values of the address, Ariba Network adapter for SAP NetWeaver sends the newly saved delivery address as the ShipTo address in the purchase order. The delivery address stored on the SAP ERP and SAP S/4HANA system for the address ID, customer ID, or vendor ID is not sent in the change purchase order. For example, if a buyer selected the address ID, edited the street address, and saved the changes, Ariba Network adapter for SAP NetWeaver sends the newly edited street address as part of the ShipTo address in the purchase order.

● If a buyer manually entered the delivery address to include the following fields in the Delivery Address tab, Ariba Network adapter for SAP NetWeaver sends the associated delivery address as the ShipTo address in the purchase order:○ Address ID in the Address field○ Customer ID in the Customer field○ Vendor ID in the Vendor field

● If the buyer has only the plant address and does not have the storage location in the purchase order, Ariba Network adapter for SAP NetWeaver sends the plant address as the ShipTo address.

● If the buyer has both the plant and storage location in the line item and the storage location address is maintained in the ox09 on the SAP ERP and SAP S/4HANA system, Ariba Network adapter for SAP NetWeaver sends the storage location address as the ShipTo address.

NoteIf a buyer entered the street address as the delivery address for certain countries, the street address then contains the street name and the house number instead of the house number and street.

In some cases, Ariba Network adapter for SAP NetWeaver processes the name field from the Name_text field instead of Name1. SAP Ariba recommends that customers use the BADI customization in these cases.

● Effective from cloud integration release 9.0 SP1, Ariba Network adapter for SAP NetWeaver supports transfer of select supplier relevant fields in purchase orders from SAP ERP and SAP S/4HANA to Ariba Network.The following 9W qualifiers are now mapped to the deliver-to fields in the ship-to segment of purchase orders:○ BNAMEBNAME: IDoc user name○ HAUSN: House number○ NAME4: Street name○ TELF1: First telephone number○ TELFX: Fax number○ TELX1: Telex number○ TELTX: Teletex number

Prerequisites for transferring select supplier relevant fields in purchase orders

● Ensure that the vendor address is available in the master data.● Specify Partner type in the Partner tab of the purchase order header.● Maintain the Partner type parameter /ARBA/PARTNER_PARVW in the table /ARBA/PARAM_TAB.


Mapping Limitations

The purchase order transaction has the following mapping limitations:

● Time zone is hard coded to Pacific time zone● Bill-to and ship-to addresses in SAP ERP and SAP S/4HANA purchase orders behave as follows:

If all purchase order lines have the same ship-to address, then:

● The ship-to address appears at the header level in cXML/Ariba Network● The ship-to address does not appear at the line level in cXML/Ariba Network● The bill-to address in the header matches the ship-to address

If purchase order lines have different ship-to addresses, then:

● Ship-to addresses do not appear at the header level in cXML/Ariba Network● Ship-to addresses appear at the line level in cXML/Ariba Network● The bill-to address in the header matches the ship-to address in the first line● The shipping information is not supported.

Related Information

Purchase order [page 15]Service purchase order [page 17]About configuring the system landscape directory [page 65]Configuring enhancement for purchase orders [page 247]How to configure implicit enhancements for new purchase orders [page 247]How to configure implicit enhancements for change and cancel Orders [page 249]How to implement a custom exit for purchase orders to fill additional details [page 250]Topics about configuring outbound transactions [page 90]Implementing a custom exit for purchase orders [page 250]

4.4 Change purchase order integration scenario

You must configure the integration scenario for the Purchase Order transaction in the Integration Directory to be able to run the change purchase order transaction. The Change Purchase Order Integration scenario and the http://ariba.com/xi/ASN/ChangedPurchaseOrder namespace no longer exists from SAP Ariba cloud integration release 5.0 and higher. Change purchase orders are now subsumed into IDoc processing for purchase orders.

● Changes Required for Customers Using SAP Ariba cloud integration release 5.0 and higherCustomers must do the following:○ Must make one-time configuration changes to SAP ERP implicit enhancements, and for change and

cancel purchase orders.



○ Must set up SAP ERP Partner Profiles.

For more information on the purchase order integration scenario, see the section, Integration scenarios for Outbound and Inbound Transactions .

Removing change order configurations from your Ariba solution [page 117]

Migrating change order customizations [page 117]

Related Information

Configuring the partner profiles [page 216]Configuring the partner profile at vendor-level [page 217]Configuring the partner profile at logical system-level [page 219]How to configure the partner profile on the SAP ERP system [page 220]How to configure the partner profile for scheduling agreement releases [page 222]How to configure the partner profile for invoices [page 223]Configuring enhancement for purchase orders [page 247]How to configure implicit enhancements for new purchase orders [page 247]How to configure implicit enhancements for change and cancel Orders [page 249]How to implement a custom exit for purchase orders to fill additional details [page 250]Purchase order integration scenario [page 114]

4.4.1 Removing change order configurations from your Ariba solution

The Change Purchase Order Integration scenario and the http://ariba.com/xi/ASN/ChangedPurchaseOrder namespace no longer exists from SAP Ariba cloud integration release 5.0 and higher. Ariba Network adapter for SAP NetWeaver provides change and cancel order enhancements that no longer make use of previously existing change order configurations in your SAP Ariba solution. You must remove them.

To remove your previously existing change order configuration, please have your Designated Support Contact log a service request, and an SAP Ariba Customer Support representative will follow up to complete the request.

4.4.2 Migrating change order customizations

If you employ change and cancel order transaction customizations in your SAP Ariba solutions, the customizations must be migrated to your purchase order transaction instead.

To migrate your customizations, please have your Designated Support Contact log a service request, and an SAP Ariba Customer Support representative will follow up to complete the request.


4.5 Order confirmation integration scenario

The Ariba Network adapter for SAP NetWeaver supports receiving order confirmations from Ariba Network for purchase orders and service purchase orders.

You must configure the integration scenario for the Order Confirmation 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.

The SAP ERP administrator must configure the SAP ERP system to collect order confirmations for purchase orders and to support comments. To support comments in order confirmations, SAP ERP administrators must configure SAP ERP enhancements for comment support.

NoteEnsure that the design is imported into your system and ready before you run integration scenario for the Order Confirmation transaction.

Additional Configuration Tasks

● In an Order Confirmation, if the supplier changed the unit price and delivery date, to ensure that the IDOC is able to post the data to SAP ERP system, you must apply SAP Notes, 109273 and 456127.

● To ensure no error is reported when order confirmations with rejected line items are posted to SAP ERP, you must apply SAP Note 890812 on your SAP ERP system. To prevent errors while processing order confirmations containing line items with the “Rejected” status, buyers must implement the custom exit, MM06E001.

Mapping Limitations

The Order Confirmation transaction has the following mapping limitations:

● Order confirmations are stated at the purchase order line-item level only. SAP does not support header level purchase order confirmation. With the exception of unit price and backordered delivery date, purchase order line items cannot be overwritten.

● A new order confirmation completely overwrites prior confirmations against a purchase order line-item. Suppliers must resend the entire confirmation picture for the relevant purchase order line.

● Delivery date is always required at 'ConfirmationStatus' in the input cXML document if the header level and line level statues are 'Backordered'. Delivery date is required at 'ConfirmationStatus' level if header level statuses are 'detail' and 'except'.

● In the cXML for an order confirmation sent from Ariba Network, the adapter does not support the operation = “update” and type = “allDetail”.

● Only order confirmations for the purchase orders that are pulled from ERP using the OrderRequest transaction is supported.

● Ariba Network adapter for SAP NetWeaver does not support order confirmations for service purchase orders at the line-item level.



● The IDoc fails when an order confirmation only contains partially rejected line items. For example, if the quantity for a line item is 100, you cannot partially reject only 50 units for that line item. You can partially accept 50 units and also partially reject or back order the remaining 50 units for the line item. You must ensure that you maintain the Overdelivery Tolerance and Underdelivery Tolerance limits for the line item.However, Ariba Network adapter for SAP NetWeaver supports order confirmations that are partially accepted, rejected, or back ordered for a line item. For example, if the quantity for a line item is 100, you can partially accept 50 units and also partially back order or reject the remaining 50 units for the line item.

● Purchase orders containing service items may only be confirmed at the outline item level.● Purchase orders containing a combination of service and material items may only be confirmed at the

header level.● When purchase orders contains advanced pricing details, the unit conversion value from Ariba Network to

SAP is not supported.● The cXML header-level except status for order confirmations created in Ariba Network is not supported.● Partial rejection of a line item in an order confirmation is not supported. Full rejection of an item in an order

confirmation sets the deletion flag on the item in SAP.

Related Information

Order confirmation [page 26]About configuring the system landscape directory [page 65]How to implement the custom exit to process the order confirmation with rejected line items [page 257]How to configure enhancements for comments in order confirmations [page 258]Topics about configuring inbound transactions [page 101]

4.6 Ship notice integration scenario

You are required to configure the integration scenario for the ship notice transaction in the Integration Directory to be able to run the transaction. You can receive a single ship notice against one or multiple purchase orders on your SAP ERP and SAP S/4HANA system. Complete all the steps of a configuration scenario section to fully configure a scenario.

NoteEnsure that the design package is imported into your system and ready before you run integration scenario for the ship notice transaction.

To switch between the interfaces for the following transactions, configure the interface determination condition:

● Ship notice create● Ship notice cancel

For more information, see How to configure the interface determination for inbound transactions [page 108].


Mapping Limitations

The ship notice transaction has the following mapping limitations:

● Delivery Date is required● Only shipment notices for the purchase orders that are pulled from SAP ERP or SAP S/4HANA using

OrderRequest transaction are supported.● Ariba Network adapter for SAP NetWeaver does not support ship notices against non-POs.

To receive ship notices with zero quantities, configure you SAP ERP or SAP S/4HANA system to specify the No dialog option in the Checks for zero quantity page. For more information, see Configuring the Ship Notice Integration Scenario to Receive Ship Notices with Zero Quantities [page 270].If you are using customized business processes, you are required to configure the following SAP Process Integration mapping: MM_Custom_CDF_FulFill_XSD_AdvanceShipNotice_2_DESADV_DELVRY06.

Related Information

Ship notice [page 28]About configuring the system landscape directory [page 65]Topics about configuring inbound transactions [page 101]

4.7 Service sheet and service sheet response integration scenario

You need to configure the integration scenario for the Service Sheet transaction in the Integration Directory to be able to run the transaction. To configure the service sheet transaction, you must configure the integration scenario for the Service Sheet (Inbound transaction) and Service Sheet Response (Outbound transaction).

Note● Ensure that the design package is imported into your system and ready before you run integration

scenario for the Service Sheet transaction.● To ensure that attachments in service sheets are processed by the adapter and sent to SAP ERP, in the

communication channel for the service sheet transaction, you must select Embedded in cXML option for the Attachment Processing Mode parameter.

Related Information

Service sheet [page 33]Prerequisite [page 34]Limitations [page 34]



About configuring the system landscape directory [page 65]Configuring service sheets [page 279]How to implement customer exits for invoices with service type line items [page 280]How to specify time-out intervals for processing service sheets [page 281]How to implement enhancements for service sheets created for new purchase orders [page 282]How to implement enhancements for service sheets created for changed or canceled purchase orders [page 283]Implementing enhancements for revoking previously accepted service sheets [page 284]Topics about configuring inbound transactions [page 101]Topics about configuring outbound transactions [page 90]

4.8 Service sheet response integration scenario

Buyers need to configure the System Landscape Directory (SLD) by importing the Ariba Network adapter for SAP NetWeaver product definition and defining the systems involved in the integration. Configure the necessary inbound and outbound integration scenarios to support integration of ERP buyers and suppliers using direct materials to Ariba Network.

For more information on configuring the SLD, see the Setting up Ariba Network adapter for SAP NetWeaver guide.

To configure the service sheet transaction, you must configure the integration scenario.

Select the following process integration scenario for the SAP Ariba cloud integration version:

● Name: AR_ERPServiceEntryRequest_Receive● Namespace: http://ariba.com/xi/ASN/ERPServiceEntryRequest● Software Component Version: ARIBA_NETWORK_ADAPTER CI9 of ariba.com● Check Copy Request while creating communication channel for outbound service entry sheet.

For more information about configuring integration scenarios, see the Configuring integration scenarios section in the Setting up Ariba Network adapter for SAP NetWeaver guide.

Note● Ensure that the design package is imported into your system and is ready before you run the

integration scenario.● To ensure that attachments in service sheets are processed by the adapter, you must select the

Embedded in cXML option for the Attachment Processing Mode parameter in the communication channel.


4.9 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.

NoteEnsure that the design package is imported into your system and ready before you run integration scenario for the Invoice transaction.

Recommendations

When you receive invoices from suppliers with the PST, GST, QST, and HST tax rates, Ariba Network adapter for SAP NetWeaver recommends the following:

● When suppliers create an invoice on Ariba Network, it is mandatory to enter the tax information. When no tax is applicable to the invoice line, a zero percent tax should be entered. If the tax information is not provided then the IDOC posting fails with the error “Enter a tax code in item.”

● The tax segments at the header and line-item level in the IDOC must be equal to the number of tax segments available in the cXML file.

● It is mandatory to maintain the tax type and tax rate for a partner in the OBCD transaction. For both the header and line-item level tax, when an Invoice IDOC is sent to ERP, it does a look up to transaction OBCD and based on the partner, tax type, and tax rate, and gets the right tax code to be used for invoice posting.

Mapping Limitations

The Invoice transaction has the following mapping limitations:

● Invoice ID must be unique for a supplier○ 'Standard' type invoices and credit memos are supported○ Only 'standard' type invoices for the Purchase Orders that are pulled from ERP using OrderRequest

transaction are supported for this release.● The following information is not supported:

○ Header Invoice (debit memo)○ Information Only Invoice○ Cancel/Delete Invoice○ Payment Terms○ Subsequent Credit○ Period information○ Deposit amount○ Tax: 'VAT recoverable' feature



Related Information

Invoice [page 36]Service invoice [page 39]Summary invoice [page 39]Direct invoicing of purchase order service items [page 40]About configuring the system landscape directory [page 65]Topics about configuring inbound transactions [page 101]

4.10 Order inquiries integration scenario

Configure the integration scenario for the Order Inquiries 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.


scenario for the Order Inquiries transaction.● Order Inquiries is supported in SAP Process Integration 7.1, 7.3 and 7.4 for Java only or Java and ABAP

stack (single or dual stack).

Related Information

Order inquiries [page 25]About configuring the system landscape directory [page 65]Configuring order inquiries [page 260]How to configure SAP IDOC for order inquiries [page 261]How to configure the partner profile [page 262]How to maintain condition records for inquiries [page 263]How to implement a custom exit for the order inquiries function module [page 264]Support for additional cXML fields [page 265]Topics about configuring outbound transactions [page 90]

4.11 Scheduling agreement release integration scenario

Configure the integration scenario for the Scheduling Agreement Release transaction in the Integration Directory to be able to run the transaction for scheduling agreement release.


All the steps of a configuration scenario section must be completed to fully configure a scenario.

NoteEnsure that the design package is imported into your system and ready before you run integration scenario for the Scheduling Agreement Release transaction.

Related Information

Scheduling agreement release [page 23]About configuring the system landscape directory [page 65]Topics about configuring scheduling agreement releases [page 265]Configuring SAP IDOC for scheduling agreement releases [page 266]How to configure the partner profile for scheduling agreement releases [page 266]How to maintain condition records for scheduling agreement releases [page 267]How to implement a custom exit for scheduling agreement releases [page 268]Support for additional cXML fields [page 269]Configuring IDOC metadata (optional) [page 269]Topics about configuring outbound transactions [page 90]

4.12 Invoice status update integration scenario

Configure the integration scenario for the Invoice Status Update (ISU) transaction in the Integration Directory to run the Invoice Status Update transaction. All the steps of a configuration scenario section must be completed to fully configure the scenario.

NoteEnsure that the design package is imported into your system and ready before you run integration scenario for the Invoice Status Update transaction.

Limitation

When the task to import the status update for invoices is executed, it returns the status of all invoices for which the status was updated on that particular date. The task does not consider the time when it imports the status update. For example, assume that the task is executed at 12.00 P.M and imports the status for 10 invoices. Now, if the task is executed again at 5.00 P.M. on the same date, it must import the status for only those invoices that were updated after 12.00 P.M. However, the task imports the status update for all the invoices including the invoices for which the status has already been imported.



Related Information

Invoice status update [page 45]About configuring the system landscape directory [page 65]Topics about configuring invoice status updates [page 275]Invoice status update transaction [page 276]How to configure the invoice status update transaction on your SAP ERP [page 278]About enabling customization of invoice status updates from SAP ERP to Ariba Network for invoices in an approval workflow [page 278]Topics about configuring outbound transactions [page 90]

4.13 ERP-initiated invoice integration scenario

You need to configure the integration scenario for the ERP-initiated 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.

NoteEnsure that the design package is imported into your system and ready before you run integration scenario for the ERP-initiated invoice transaction.

Related Information

ERP-initiated invoice [page 40]ERP-initiated invoices using the IDOC transmission method [page 41]Prerequisites for using IDOCs for ERP-initiated invoices [page 42]Limitations using the IDOCs [page 43]Enabling quick enablement for ERP-initiated invoices [page 43]ERP-initiated invoice with cross company codes [page 44]Enabling ERP-initiated invoices with cross company codes [page 45]About configuring the system landscape directory [page 65]Topics about configuring outbound transactions [page 90]

4.14 Receipt integration scenario

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 must be completed to fully configure a scenario.


To send and receive corrections and returns in receipts, see Receipt Integration Scenario for Corrections and Returns in Receipts [page 126].

NoteEnsure that the design package is imported into your system and ready before you run integration scenario for the Receipt transaction.

Related Information

Receipt requests [page 29]Receipt with corrections and returns [page 30]Data flow overview [page 32]About configuring the system landscape directory [page 65]Topics about configuring outbound transactions [page 90]

4.15 Receipt integration scenario for corrections and returns in receipts

Configure the integration scenario for the Receipt transaction in the Integration Directory to be able to run the transaction for receipts with corrections and returns.

All the steps of a configuration scenario section must be completed to fully configure a scenario. To enable the SAP ERP to send receipts with corrections and returns, you must configure the parameter and maintain condition records.

NoteEnsure that the design package is imported into your system and ready before you run integration scenario for the Receipt transaction.

Related Information

Receipt with corrections and returns [page 30]Data flow overview [page 32]About configuring the system landscape directory [page 65]Topics about configuring outbound transactions [page 90]How to transfer the integration scenarios for outbound transactions [page 91]How to assign the model for outbound transactions [page 93]How to assign components for outbound transactions [page 93]



How to configure the sender and receiver relations for individual connections for outbound transactions [page 94]How to generate objects for outbound transactions [page 96]How to configure the communication channels for outbound transactions [page 96]How to configure the interface determination for transactions with Ariba Network [page 99]How to activate the integration scenario [page 111]

4.16 Payment proposal integration scenario

Configure the integration scenario for the Payment Proposal transaction in the Integration Directory to be able to run the transaction for scheduled payments. All the steps of a configuration scenario section must be completed to fully configure the scenario.


scenario for the Payment Proposal transaction.● In the production environment, for an invoice with a payment block, the payment proposal for an

invoice is sent as Hold to Ariba Network. If a user removes the payment block for the invoice, then the payment proposal is again sent as New to Ariba Network. However, this payment proposal is rejected by Ariba Network. To ensure that the payment proposal is not rejected by Ariba Network, the Extrinsic @name=Ariba.relaxedOperationCheck, which is part of the mappings, must be set with the required value.

Related Information

Scheduled payments and dynamic discounting [page 46]About configuring the system landscape directory [page 65]Topics about configuring outbound transactions [page 90]

4.17 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 configure a scenario.

NoteEnsure that the design package is imported into your system and ready before you run integration scenario for the Pay MeNow transaction.


Related Information

Scheduled payments and dynamic discounting [page 46]About configuring the system landscape directory [page 65]Topics about configuring inbound transactions [page 101]

4.18 Payment remittance (outbound) integration scenario

You must configure the integration scenario for the Payment Remittance 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.

NoteEnsure that the design package is imported into your system and ready before you run integration scenario for the Payment Remittance transaction.

Mapping Limitations

The Payment Remittance transaction has the following mapping limitations:

● Only new payment remittance pull is supported● Any changes or void payment pulls are not supported● Time zone is not factored in the invoice date mappings● Integration is tested for only 'check' and 'electronic/edi' payment methods● Payment Remittance (Full/Partial) generated using manual payments are not pulled because IDocs are

generated for manual payments (f-58 transaction). Manual payments can be done using the transaction code F-53 or F-58.○ If you use T-code F-53, Checks must be printed separately after the payment or remittance document

has been posted.○ If you use T-code F-58, Checks can be printed with the remittance or payment document.

● Cancel Remittances are not pulled to Ariba Network.

NoteCancel Remittances are not supported.

Related Information

Payment remittance request (outbound) [page 48]About configuring the system landscape directory [page 65]



Topics about configuring outbound transactions [page 90]

4.19 Liability transfer integration scenario

You must configure the integration scenario for the Liability Transfer 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.

NoteEnsure that the design package is imported into your system and ready before you run integration scenario for the transaction.

Related Information

About configuring the system landscape directory [page 65]Integration to support early payments through Supply Chain Financing [page 192]Prerequisites and limitations [page 193]Workflow for early payment through Supply Chain Financing [page 195]Configuring early payments for Supply Chain Financing [page 196]Configuring your SAP Process Integration to support early payments through Supply Chain Financing [page 197]How to configure the integration scenarios to integrate early payments through Supply Chain Financing [page 197]Topics about configuring the SAP ERP system for Supply Chain Financing [page 198]How to create a vendor for the funder on Supply Chain Financing [page 198]How to maintain the vendor and funder information [page 199]How to create payment methods by country [page 200]How to maintain the company code for the vendor as funder [page 201]How to assign the company code to the payment method [page 201]How to maintain the document type for early payments through Supply Chain Financing [page 202]How to maintain the business transaction event for invoice status update and remittance transactions [page 204]How to maintain the general ledger account configuration for a company code with the Supply Chain Financing payment method [page 205]Topics about configuring inbound transactions [page 101]


4.20 Payment remittance request (inbound) integration scenario

You must configure the integration scenario for the Remittance Advice Request 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.


Related Information

Payment remittance request (inbound) [page 48]About configuring the system landscape directory [page 65]Topics about configuring inbound transactions [page 101]

4.21 Payment remittance batch request integration scenario

You must configure the integration scenario for the Payment Remittance Batch Request 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.


Related Information

Payment remittance batch request [page 48]About configuring the system landscape directory [page 65]Integration to support SAP Ariba Payables payments through the cXML format using SAP standard payment interface [page 205]Prerequisites and limitations [page 206]Workflow to support AribaPay payments through the cXML format using SAP standard payment interface [page 208]



Configuring integration to support SAP Ariba Payables payments through the cXML format using SAP standard payment interface [page 209]Configuring SAP Process Integration to support AribaPay payments through the cXML format [page 209]How to add the software component version for SAP Enterprise Service [page 210]How to configure the integration scenarios to integrate payments through the cXML format [page 210]Configuring SAP ERP system to support AribaPay payments through the cXML format [page 211]How to create payment methods by country/region for AribaPay [page 211]Prerequisites and limitations [page 206]Workflow to support AribaPay payments through the cXML format using SAP standard payment interface [page 208]Configuring integration to support SAP Ariba Payables payments through the cXML format using SAP standard payment interface [page 209]Configuring SAP Process Integration to support AribaPay payments through the cXML format [page 209]How to add the software component version for SAP Enterprise Service [page 210]How to configure the integration scenarios to integrate payments through the cXML format [page 210]Configuring SAP ERP system to support AribaPay payments through the cXML format [page 211]How to create payment methods by country/region for AribaPay [page 211]Topics about configuring outbound transactions [page 90]

4.22 Requisition request integration scenario

Configure the integration scenario for the Requisition Request 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.

NoteEnsure that the design package is imported into your system and ready before you run integration scenario for the Requisition Request transaction.

Related Information

Requisition [page 15]About configuring the system landscape directory [page 65]Topics about configuring outbound transactions [page 90]


4.23 Request for quotation integration scenario

You need to configure the integration scenario for the Request for Quotation 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.


scenario for the Request for Quotation transaction.● To completely enable creation and cancellation of sourcing requests the SAP ERP administrator must

also install SAP ERP enhancements. For more information, see the RFQ and Award Integration with Ariba Sourcing guide.

Related Information

Request for quotation [page 49]Topics about configuring outbound transactions [page 90]



5 Advanced configuration scenarios

Linking multiple SAP ERP instances with Ariba Network [page 133]

Configuring supplier quick enablement [page 137]

Customizing data mappings [page 138]

Enabling support for attachments [page 140]

Support for proxy bypass [page 153]

Support for 2-way match [page 156]

Using endpoint integration [page 157]

Using the SAP Process Integration KeyStore [page 159]

PDF invoice copy attachments [page 160]

Integrating SAP ERP with the SAP Ariba Commerce Automation solution [page 174]

Integration of catalog data in SAP ERP and Ariba Network [page 181]

Integration to support early payments through Supply Chain Financing [page 192]

Integration to support SAP Ariba Payables payments through the cXML format using SAP standard payment interface [page 205]

About support for third-party logistics providers [page 212]

5.1 Linking multiple SAP ERP instances with Ariba Network

If your organization has more than one instance of SAP ERP, you can link them to a single Ariba Network account. This feature allows all the documents from particular vendors to be routed to a single Ariba Network account and in the reverse direction, the documents from Ariba Network will be routed to a particular SAP ERP instance.

Buying organization or service provider accounts must be enabled for Multi-ERP implementation by Ariba Network Support. The required configuration sections will not be available for accounts that have not been enabled.

This section describes the following topics:

Document routing mechanism [page 134]

Multi-ERP configuration [page 135]

Setting up Ariba Network adapter for SAP NetWeaverAdvanced configuration scenarios PUBLIC 133

5.1.1 Document routing mechanism

In the multi-ERP implementation scenario, each of the SAP ERP 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 ERP 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="[email protected]" 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.


Advanced configuration scenarios

The following figure shows the SystemID identifier location in outbound documents at the top and in inbound documents at the bottom:

● 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 Process Integration with a system error.

5.1.2 Multi-ERP configuration

The multi-ERP implementation requires configuration on all three sides: SAP ERP, SAP Process Integration and Ariba Network.

Configuring the System Landscape Directory

You must configure all your SAP ERP instances in the SLD as Technical and Business Systems.

For more information, see the How to define the technical and business system for SAP ERP [page 68] section.


Configuring SAP ERP Connectivity

The connectivity between all the SAP ERP instances and the SAP Process Integration server has to be setup.

For more information, see the About configuring ERP connectivity [page 71] section.

Configuring Integration Scenarios for Multiple ERPs

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● Scheme: GlobalVariable● Value: IsMultiERPModeEnabled

Target:

● Agency: XI● Scheme: GlobalVariable● Value: true.

● Configure the mappings between Business Systems and Logical System Names:

Source:

● Agency: LogSys_Source● Scheme: Lookup● Value: Logical System Name

Target:

● Agency: BusSys_Target● Scheme: Lookup● Value: Business System Name.

NoteThe Group Name is not required.

The following table shows an example of values.



LogSys_Source BusSys_Target

T90CLNT090 BS_SAP_46C

T47CLNT800 BS_SAP_47

Setting up Receiver Determination

Each inbound scenario, as well as the scheduled scenarios must be configured for messages and calls routing.

Refer to the specific section for each transaction to setup the receiver determination rules. For more information, see the following:

● How to configure the receiver determination settings for inbound transactions [page 107]

5.1.2.1 Configuring Ariba Network for multiple ERPs

You must configure Ariba Network with the information about all the instances of SAP ERP involved in the integration and link it with the buyer account.

NoteBuying organization or service provider accounts must be enabled for multi-ERP implementation by Ariba Network Support. The required configuration sections will not be available for accounts that have not been enabled.

Fore more information on Ariba Network setup, see the “Linking Multiple Business Applications” section, in “Configuration,” of the Ariba Network Integration Guide.

5.2 Configuring supplier quick enablement

Ariba Network Quick Enablement allows buying organizations and Invoice Conversion service providers to create new Ariba Network 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 Network uses this information to create the supplier’s account. Quick Enablement is also supported for ERP-initiated invoice and payment proposal transactions.

Ariba Network adapter for SAP NetWeaver 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 Network, the purchase orders for this vendors forwarded to Ariba Network 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 Network Support. Ariba Network ignores the Correspondent element for accounts that have not been enabled.

5.2.1 Additional references

For more information about the Quick Enablement and the cXML, see the Quick Enablement section in the cXML Solutions Guide.

For more information about configuring Ariba Network for Quick Enablement, see the Inviting an Unregistered Supplier section in the Buyer Administration Guide.

For detailed steps to configure support for multiple SAP ERP instances, see Linking Multiple SAP instances with Ariba Network [page 133].

For details on how to link multiple SAP ERP instances from Ariba Network, see the Ariba Network Integration Guide.

5.3 Customizing data mappings

The Ariba Network adapter for SAP NetWeaver mapping workbooks are intended as sample only. The buying organizations can customize mappings to suit their business needs.

● In case of outbound transactions, the data is transformed from XML to cXML and then uploaded to Ariba Network.

● In case of inbound transactions, the data is transformed from cXML to XML and then transferred to the SAP ERP system.

The information about how the fields have been mapped between XML and cXML files for both inbound and outbound transactions is available in mapping workbooks provided by SAP Ariba. You can download these mapping workbooks from https://support.ariba.com/Connect/Log_In .

You as a buying organization can change the mapping of fields between XML and cXML according to your business requirements. For example, each buying organization lists requisitioners in cXML in a different way. These differences can be handled by customizing the mappings.




5.3.1 How to download mapping workbooks from Ariba Connect

Procedure

1. Go to https://support.ariba.com/Connect/Log_In and log in using your user ID and password. If you do not have a User ID and Password for SAP Ariba Connect, contact your SAP Ariba account executive.

2. On the Home page, click Product Information and Documentation.3. Click Cloud Integration in the Product Information section and then click Resources.

The Cloud Integration Resources page appears.4. In the Integration Tools section, click Integration tools for Ariba Network..5. On the Resources tab, go to the Integration Tools section, click Data Transformation for the version you

require.6. Click Download, and specify a location on your hard drive to download the mapping workbooks.

Results

The mapping workbooks for all transactions are available in a ZIP file.

5.3.2 Enabling migration of mapping customization

The mapping customization migration feature allows customization to be retained while upgrading to subsequent versions. All future upgrades will be done using the Release Transfer Tool. To enable the customization to be retained when upgrading from an earlier version to a subsequent version of the Ariba Network adapter for SAP NetWeaver, you must make customizations only in the designated mapping objects. The Release Transfer Tool migrates the customizations unchanged.

CautionDo not change any object other than those listed in the table. If you do, upgrade may fail.

The following table lists the mapping objects for each transaction:

Transaction Mapping Object

ShipNotice MM_Custom_CDF_FulFill_XSD_AdvanceShipNotice_2_DESADV_DESADV01

ShipNotice against multiple purchase orders

MM_Custom_CDF_FulFill_XSD_AdvanceShipNotice_2_DESADV_DELVRY06’

PurchaseOrder MM_Custom_ORDERS_ORDERS05_2_CDF_cXML_XSD



Transaction Mapping Object

ChangedPurchaseOrder MM_Custom_ORDCHG_ORDERS05_2_CDF_cXML_XSD

ERPInvoice MM_Custom_Invoice_Intermediate_cXML_Item_2_cXML

Invoice MM_Custom_CDF_InvoiceDetail_XSD_2_INVOIC_INVOIC02_INVOIC02

DynamicDiscountingCreditMemo MM_Custom_CDF_InvoiceDetail_XSD_2_CreditMemo_Attachment_Cancellation_Proxy

InvoiceStatusUpdate MM_Custom_InvoiceStatusUpdate_Item_2_cXML

OrderConfirmation MM_Custom_CDF_FulFill_OC_XSD_2_ORDRSP_ORDERS05

PayMeNow MM_Custom_CDF_FulFill_XSD_PayMeNow_2_FIDCCH_FIDCCH01

PaymentProposal MM_Custom_PaymentProposal_Item_2_cXML

PaymentRemittance MM_Custom_REMADV_PEXR2001_2_cXML

PaymentRemittanceAdvice MM_Custom_CDF_PaymentRemittance_XSD_2_ACC_DOCUMENT_ACC_DOCUMENT01

Receipt MM_Custom_MT_Intermediate_cXML_2_cXML

5.4 Enabling support for attachments

The cXML protocol supports the attachment of external files of any type to cXML documents. For example, buyers sometimes need to clarify purchase orders with supporting memos, drawings, or faxes. Another example is the CatalogUploadRequest document, which includes catalog files as attachments.

Files referenced by cXML documents can reside either on a server accessible by the receiver or within an envelope that also includes the cXML documents themselves. To attach external files to a cXML document in a single envelope, use Multipurpose Internet Mail Extensions (MIME). The cXML document contains references to external parts sent within a multipart MIME envelope.

SAP ERP buyers can send and receive attachments for both outbound and inbound documents from Ariba Network.

For more information about attachments, see cXML User’s Guide and cXML Solutions Guide.

Attachments in cXML can be of any file type, such as DOC, PDF, TXT, JPEG, and so on.

Ariba Network supports attachments for the following transactions:

● Purchase Order● Invoice● Ship Notice● Order Confirmation● Service Entry Sheets● Service Sheet Response● Request for Quotations



The size of the attachments for both inbound and outbound documents cannot exceed 100 MB. Attachments can additionally have a payload of up to 40 MB.

If you attempt to exceed the file attachment size of 100 MB or 10,000 line items (40 MB) payload, SAP ERP and Ariba Network either prevent or reject the document with an error message.

SAP ERP limits the maximum number of line items depending upon the document type. For more information on limitations and workaround, see the following SAP Notes:

● 1779136 - Extended summarization of FI documents● 1801529 - Error message F5727 "Maximum number of items in FI reached" when release MM document

to accounting● 36353 - AC interface: Summarizing FI documents

Note1. Buyers must ensure that the rule Your procurement application can download invoice attachments

(MIME multipart messages) is enabled in Ariba Network .2. Multiple attachments are permitted but the combined attachment size must not exceed 100 MB.3. Although this feature allows processing of all transactional documents through the SAP Process

Integration mapping layer, the end-to-end integration for document attachments is only available for invoices and service entry sheets.

4. To avoid performance degradation when sending or receiving multiple documents with large attachments or payload, SAP Ariba recommends that you specify maxMessages=1 in the adapter communication channel in the integration builder.

Related Information

Attachments for outbound documents [page 141]Attachments for inbound documents [page 151]Managing email notifications [page 153]

5.4.1 Attachments for outbound documents

The outbound documents sent from a configured Ariba Network Adapter to the cXML Adapter can have attachments. The attachments are part of the Comments element in the cXML file. If a cXML document contains attachments, then the structure of the Comments element is as follows:

<Comments> <Attachment> <URL> “Attachment URL”</URL> </Attachment> </Comments>

The Ariba Network adapter for SAP NetWeaver processes attachments in the outbound transactional documents before sending them to Ariba Network as follows:





● The SAP Process Integration mapping layer allows access to attachments.● The SAP Process Integration mapping layer provides functionality to access attachments. You can use this

functionality through customization.● The cXML adapter receives the XI message and processes the attachment in the format required by Ariba

Network.● This setting is based on the configuration that administrators specify on their SAP ERP system. When the

cXML adapter downloads the attachments from Ariba Network, it checks the parameter settings specified for the document attachment before processing the attachment.

An outbound document can have multiple attachments, such as product specifications, images, supporting memos, and so on.

NoteEnsure that the attached files have unique names and the names do not have blank spaces.

When Ariba Network receives an outbound document with attachments, Ariba Network either forwards the attachments to the respective suppliers or stores these attachments to allow online access for suppliers. These stored attachments expire after 180 days and are not available online thereafter.

If an error occurs when the cXML Adapter is downloading a document from the HTTP location, the document is not sent to Ariba Network and the cXML Adapter reports back an error to the originating system of the outbound document.

NoteIn outbound documents with attachments, if any of the file name of the attachments include blank spaces, Ariba Network reports an error and the document processing fails in Ariba Network. To prevent such attachments failing in Ariba Network, ensure that the file name sent to the UDF does not have any blank spaces.

When the outbound documents attachment URL contain special characters, buyers must ensure that:

● the attachment URL is encoded using the UTF-8 compliant character set● http:// is not encoded in the URL for attachments

Related Information

Attachments for request for quotations [page 142]Enabling support for attachments in outbound documents [page 143]

5.4.1.1 Attachments for request for quotations

You can add line item-level attachments to requests for quotations (RFQs).

You can add multiple attachments from the Document Management Server (DMS) for each line item in a RFQ. File types that you can attach at the line level depend on the file types that the DMS configuration supports.



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 who send the encrypted or password-protected attachment to SAP Ariba Sourcing need to share the required password with suppliers who need to view the attachment.

To enable buyers using Ariba Network adapter for SAP NetWeaver add attachments at the line-item level of RFQs, the following segments have been added to /ARIBA/RFQ (ORDERS05) IDOC:

● /ARBA/DOCUMENT_ITEM● /ARBA/HEX_CONTENT_ITEM

Prerequisites

● To attach line item-level attachments, you must configure DMS and upload the files that you want to attach at the line-item level to the DMS.

● To attach multiple files on a single-stack instance of SAP Process Integration version 7.4, implement SAP Note 2002735 .

● To attach more than five files on a dual-stack instance of SAP Process Integration, implement SAP Note 1882948 .

Limitations

● 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 SAP Ariba application.

● SAP Ariba Sourcing does not support header-level attachments in change RFQs.

5.4.1.2 Enabling support for attachments in outbound documents

The following UDFs maintain a mapping of the content type and the corresponding file extensions for processing of attachments in outbound documents:

● AttachmentUtil.readAttachmentContent(content,contentType,name,container)● AttachmentUtil.readAttachmentContentURL(url,name,container)

NoteIf you are a customer using SAP Ariba cloud integration release version 9.0 and have implemented the following UDF functions for attachments, ensure that you remove them. Ariba Network adapter for SAP NetWeaver does not process purchase orders with attachments if you have these UDF functions and use SAP Ariba cloud integration release 9.0 HF 8 and above.

AttachmentUtil.readAttachmentContent(content,contentType,name,container,randomGenerator)

AttachmentUtil.readAttachmentContentURL(url,name,container,randomGenerator)




This mapping is similar to the mapping that is maintained in Ariba Network as follows:

● application/pdf=pdf● application/postscript=ai● video/x-msvideo=avi● video/quicktime=mov● video/mpeg=mpeg● text/plain=txt● text/html=html● image/tiff=tiff● image/jpeg=jpg● image/gif=gif● audio/x-wav=wav● audio/basic=au● application/x-troff=tr● application/zip=zip● text/xml=xml

The UDFs function as follows:

● AttachmentUtil.readAttachmentContent(content,contentType,name,container)When the HTTP location (URL) and filename is given as an input to the UDF, the UDF tries to download the attachment from the HTTP location. If the UDF receives the filename as null, then the UDF matches the content type with the content type/file extension mapping it maintains. The UDF adds the attachment to the outbound document. The cXML adapter uploads the cXML document to Ariba Network.

● AttachmentUtil.readAttachmentContentURL(url,name,container)When Base 64 content, content type, and filename is given as input to the UDF, the UDF reads the given content. If the UDF receives the filename as null, then the UDF matches the content type with the content type/file extension mapping it maintains. The UDF adds the attachment to the outbound document. The cXML adapter uploads the cXML document to Ariba Network.

The cXML adapter builds a MIME message and adds the attachment as a mime body part along with the content ID and content type of the attachment before uploading the cXML document to Ariba Network.

In Ariba Network, the attachments section provides details about the all the attachments that are associated with a respective outbound document.

Related Information

How to enable support for attachments in purchase orders [page 145]How to enable support for attachments in outbound documents except purchase orders [page 146]How to enable proxy and URL authentication support for attachments URLs [page 147]How to configure the SAP ArchiveLink for storing and assigning attachments on SAP ERP [page 149]How to configure invoices and service entry sheets to support large attachments [page 150]



5.4.1.2.1 How to enable support for attachments in purchase orders

Context

To support attachments in purchase orders, the following two User Defined Functions (UDFs) have been added to the purchase order custom map, MM_Custom_ORDERS_ORDERS05_2_CDF_cXML_XSD:

● UDF readAttachmentContentURL: reads the content from a given URL and adds the attachment to the outbound document.

● UDF readAttachmentContent: reads the given Base 64 content and adds the attachment to the outbound document.

To enable support for attachments in purchase orders, perform the following procedure in SAP Process Integration:

Procedure

1. Open MM_Custom_ORDERS_ORDERS05_2_CDF_cXML_XSD in edit mode.

2. Choose from the following options depending on attachment either at header-level or line-level:

○ Header-level: From the External Message cXML window, choose OrderRequestHeaderComments .

○ Line-level: From the External Message cXML window, choose ItemOut Comments .3. Choose Constant from the Functions dropdown menu and map Comments element with Constant.4. Choose Constant from the Functions dropdown menu and map Attachment element with Constant.5. Customize mapping using the UDFs:

○ UDF readAttachmentContentURL1. Choose User-defined from the Functions dropdown menu, drag and drop the UDF, concatenate

the result of the UDF with cid: and map it to the URL.2. Map the first input to the UDF with the attachment URL.3. Map the second input to the UDF with the attachment file name.

○ UDF readAttachmentContent1. Choose User-defined from the Functions dropdown menu, drag and drop the UDF, concatenate

the result of the UDF with cid: and map it to the URL.2. Map the first input to the UDF with the attachment content in Base 64 string format.3. Map the second input to the UDF with the attachment content type.4. Map the third input to the UDF with the attachment file name.

5. NoteThe content must be encoded in Base 64.

6. (Optional) To create an additional attachment, right-click the Attachment node from Comments and choose Duplicate Subtree.


An Attachment is created without any mappings. Perform step 3 through step 5 to add an attachment.

Repeat step 6 for additional attachments, as needed.7. (Optional) To send attachments with file names in the different languages, do the following:

○ If you are using SAP Ariba cloud integration release 6.0 and higher:1. Create a UDF with a new name and create a signature string variable "nonASCII".2. Call the function, AttachmentUtil.convertToASCII (nonASCII) in the custom mapping.3. Choose Constant from the Functions dropdown menu and map the Comments element with

Constant.4. Choose Constant from the Functions dropdown menu and map the Attachment element with

Constant.5. Choose User-defined from the Functions dropdown menu, drag and drop the newly-created UDF.6. Map the output for the newly created UDF to the UDF readAttachmentContent or UDF

readAttachmentContentURL.

○ If you are using SAP Ariba cloud integration release 5.0:1. Perform step 1 through step 5.2. Map the output for the newly created UDF to name attribute of the Attachment node in the

custom mapping for the attachment you are sending in the purchase order.

5.4.1.2.2 How to enable support for attachments in outbound documents except purchase orders

Context

To enable support for attachments in outbound documents other than purchase orders, perform the following procedure in SAP Process Integration:

Procedure

1. Choose the custom mapping and import the following libraries:

○ com.ariba.asc.sap.netweaver.xiadapter.mappings○ java.security

2. Create the following two UDFs in the custom mapping:

○ Create a UDF with the desired name and call AttachmentUtil.readAttachmentContent(content,contentType,name,container) function for reading the Base 64 content.

○ Create a UDF with the desired name and call AttachmentUtil.readAttachmentContentURL(url,name,container) function for reading the content from the URL

3. Open the custom map in the Edit mode.



4. Choose from the following options depending on attachment either at header-level or line-level:

○ Header-level: From the External Message cXML window, choose RequestHeader Comments .

○ Line-level: From the External Message cXML window, choose ItemOut Comments .5. Choose Constant from the Functions dropdown menu and map Comments element with Constant.6. Choose Constant from the Functions dropdown menu and map Attachment element with Constant.7. Customize mapping using the UDFs:

○ UDF readAttachmentContentURL1. Choose User-defined from the Functions dropdown menu, drag and drop the UDF, concatenate

the result of the UDF with cid: and map it to the URL.2. Map the first input to the UDF with the attachment URL.3. Map the second input to the UDF with the attachment file name.

○ UDF readAttachmentContent1. Choose User-defined from the Functions dropdown menu, drag and drop the UDF, concatenate

the result of the UDF with cid: and map it to the URL.2. Map the first input to the UDF with the attachment content in Base 64 string format.3. Map the second input to the UDF with the attachment content type.4. Map the third input to the UDF with the attachment file name.

NoteThe content must be encoded in Base 64.

8. (Optional) To create an additional attachment, right-click the Attachment node from Comments and choose Duplicate Subtree.

An Attachment is created without any mappings. Perform step 7 through step 9 to add an attachment.

Repeat step 10 for additional attachments, as needed.

5.4.1.2.3 How to enable proxy and URL authentication support for attachments URLs

Context

The API readAttachmentContentURLWithProxy() picks up the proxy parameters from the attributes to connect to the external URL. If the URL has authentication, it picks up the URL authentication parameters and connects to the external URL.


Procedure

1. Add the following method in the Attributes and Methods section of the MM_Custom_ORDERS_ORDERS05_2_CDF_cXML_XSD:

public static String readAttachmentContentURLWithProxy (String url, String name, Container container) throws StreamTransformationException { Map<String, String> attachmentParams = new HashMap<String, String>(); /* PROXY SERVER PARAMETERS */ attachmentParams.put("proxyServerUsed", "false"); /* true/false */ attachmentParams.put("proxyServerHost", ""); /* proxy host */ attachmentParams.put("proxyServerPort", "-1"); /* proxy port */ attachmentParams.put("proxyServerUser", ""); /* proxy username */ attachmentParams.put("proxyServerPassword", ""); /* proxy password */ attachmentParams.put("proxyServerAuthenticationMethod", ""); /* B/D/N */ attachmentParams.put("proxyServerDomain", ""); /* server domain */ /* ATTACHMENT AUTHENTICATION PARAMETERS */ attachmentParams.put("isAttachmentAuthenticationActive", "false"); /* true/false */ attachmentParams.put("attachmentURLUserID", ""); /* username */ attachmentParams.put("attachmentURLPassword", ""); /* password */ /* Call the attachment download API */ return AttachmentUtil.readAttachmentContentURL( url, name, attachmentParams, container; }

Proxy Parameters

Parameter Type Information

proxyServerUsed = false String Set as true if you are using a proxy.

proxyServerHost = null String Proxy host

proxyServerPort = -1 String Proxy port

proxyServerUser = null String User name

proxyServerPassword = null

String Password

proxyServerAuthenticationMethod = null

String Select proxy authentication method:

○ B○ D○ N

B-Basic, D-Digest, N-NTLM




proxyServerDomain = null String Configure this value if the authentication method is NTLM.

URL Authentication Parameters


isAttachmentAuthenticationActive = false

String Set as true if you require URL authentication.

attachmentURLUserID = null

String User name

attachmentURLPassword= null

String Password

Example: attachmentParams.put("proxyServerPort","8008"); where 8008 is the value of server port.

2. Call the function readAttachmentContentURLWithProxy(url,name,container) in the UDF readAttachmentContentURL.

5.4.1.2.4 How to configure the SAP ArchiveLink for storing and assigning attachments on SAP ERP

Context

Configure the SAP ArchiveLink for storing and assigning the attachments in invoices on SAP ERP.

Procedure

1. Go to Tcode SPRO and then click SAP NetWeaver Application Server Basis Services Archive Link Basic Customizing .

2. Edit the document class and specify the following:○ Doc.class: TIF or PDF○ Description: Portable Document Format○ Application: SAPHTML

3. Edit the document types and define a new document type for invoices. Specify the following:○ Document Type: ZMMILOGINV○ Description: Incoming invoice log. invoice verific.


○ Document Class: TIF or PDF4. Edit the link to create a new document type and define the linkage between the document type and

business object BUS2081. In the Display View, Links for Content Repositories: Details page, ensure that you have the following values:○ Object Type: BUS2081○ Object Type: BUS2081○ Document Type: ZMMILOGINV○ Link Status: X○ Link Status: X○ Storage System: MA○ Link: TOA01○ Retention per: Blank or zero

5.4.1.2.5 How to configure invoices and service entry sheets to support large attachments

Context

You must configure your SAP Process Integration system to support the end-to-end integration in sending large attachments in invoices and service entry sheets.

Procedure

1. Go to transaction SXMB_ADM.

2. Click to expand Integration Engine Configuration .3. Increase the time out setting for the parameter "HTTP_TIMEOUT" for category Runtime to 10000.

4. Go to transaction SMICM.

5. Go to the Parameters section.6. Change the parameter value of icm/HTTP/max_request_size_KB to 307200.

NotePlease note that this value goes back to 102400 after the system has rebooted.

7. Go to TCode RZ10 for the latest version of the default profile.

8. Update the Extended Maintenance and increase the parameter value of rdisp/max_wprun_time to 5400.



5.4.2 Attachments for inbound documents

When the cXML Adapter downloads a document with attachments from Ariba Network, it receives the attachments in a MIME message. For information on how the cXML Adapter processes the attachments, see PDF Invoice Copy Attachments [page 160].

For inbound documents, the SAP Process Integration mapping layer receives the attachments and the cXML adapter sends the attachment as a message to the integration engine as follows:

● The SAP Process Integration mapping layer receives the attachments.● The cXML adapter sends the attachment as a message to the integration engine. The Java mapping in the

SAP Process Integration mapping layer reads the attachment from the message received and maps them to the target schema. For invoices and service entry sheets, the SAP Process Integration mapping layers maps it to the IDOC or RFC schema.

● For invoices, the attachment information is available in the IDOC. Attachment in service entry sheets are also supported.

NoteAlthough this feature allows processing of all transactional documents through the SAP Process Integration mapping layer, the end-to-end integration for document attachments is only available for invoices and service entry sheets.

Related Information

Enabling support for attachments in inbound documents [page 151]Invoices with attachments [page 153]

5.4.2.1 Enabling support for attachments in inbound documents

You must do the following to send attachments in inbound documents:

● Configure the Attachment Processing Mode parameter and specify the Send Attachments to Mapping option in the communication channel for the adapter.

● Configure the SAP ArchiveLink for storing and assigning the attachments in invoices on the SAP ERP system. For more information, see How to configure the SAP ArchiveLink for storing and assigning attachments on SAP ERP [page 149].

● To read attachments in inbound documents received by the Ariba Network adapter for SAP NetWeaver, customers must write a Java map. A sample Java map has been provided by SAP Ariba that you can use. This sample Java map is available in the AribaNetworkAdapterSAPNetweaver_vCI_X_FR.zip on https://support.ariba.com/Connect/Log_In .If you are using SAP Ariba cloud integration version 8.0 and lower, the Java map is stored here: <root>/Archive/XI_Mapping_Services/javamappings/com/ariba/asc/sap/netweaver/xiadapter/javamappings Name of Java file - InboundAttachmentHandlerSample.java.



If you are using SAP Ariba cloud integration version 9.0 and higher, the Java map (ARB_JAVA_MAPPING) is stored as part of the AribaNetworkAdapter.Basis.tpz file under the ximappings folder.

● To process attachments in invoices, implement a BADI for the BADI definition INVOICE_UPDATE in the customer's namespace to store and access attachments for invoices. For more information, see the BADI implementation for the BADI Definition INVOICE_UPDATE section.In the BADI, implement the method CHANGE_BEFORE_UPDATE and place the function module /ARBA/ARCHIVE_IDOC_ATTACH inside the method.The following parameters must be sent to the function module:

Parameter This parameter stores the...

DOCNUM IDOC number that contains the attachment.

ARCHIV_ID Content repository identification. For example, MA.

AR_OBJECT Document type for the SAP ArchiveLink. For example, ZMMILOGINV.

OBJECT_ID The object ID (object identifier) for the SAP ArchiveLink. For example, for an invoice, the object ID would be the concatenation of the MIRO document number and fiscal year.

SAP_OBJECT The object type for the SAP ArchiveLink business object. For example, BUS2081.

RETURN (Table Parameter) Error details. This value is available only when there is an error in archiving or creating a link between the archived document.

Sample Code

Example: CONSTANTS: c_archiv_id TYPE saearchivi VALUE 'MA', c_ar_object TYPE saeobjart VALUE 'ZMMILOGINV', c_sap_object TYPE saeanwdid VALUE 'BUS2081'. DATA : l_objectid TYPE saeobjid, it_return TYPE bapiret2_t.IF s_rbkp_new-sgtxt IS NOT INITIAL AND s_rbkp_new-bktxt EQ 'ARIBA_ASN'. CLEAR l_objectid. refresh it_return. *Concatenate Invoice number with Fiscal year CONCATENATE s_rbkp_new-belnr s_rbkp_new-gjahr INTO l_objectid. CALL FUNCTION '/ARBA/ARCHIVE_IDOC_ATTACH' EXPORTING docnum = s_rbkp_new-sgtxt archiv_id = c_archiv_id ar_object = c_ar_object object_id = l_objectid sap_object = c_sap_object TABLES return = it_return. ENDIF



5.4.2.2 Invoices with attachments

An invoice can have multiple attachments such as delivery details, emails, fax, and so on. Ariba Network adds these attachments to a MIME message and sends the MIME message to the cXML Adapter for further processing.

For inbound documents, the cXML Adapter supports attachments of all file types that are supported by Ariba Network. When the cXML Adapter downloads a document with attachments from Ariba Network, it prefixes the filename of the attachment with a unique random number. This allows the Ariba Network adapter for SAP NetWeaver to differentiate attachments within documents and attachments between documents.

If a error occurs when the cXML Adapter is downloading a document with attachments from Ariba Network, the document is not removed from the pending queue. The cXML Adapter does not send a status update to Ariba Network and attempts to download the document again.

5.4.3 Managing email notifications

To receive email notifications when there is an error during the attachment processing, maintain the ATTACHMENT_EMAIL_SEND parameter in the /ARBA/PARAM_TAB and specify the email addresses of the administrator that receives the email. The SAP ERP administrator receives an email with details of the invoice number and attachment. An administrator can monitor the errors from the SXMB_MONI if an error occurs while processing attachments.

5.5 Support for proxy bypass

When a purchase order is sent from SAP ERP to Ariba Network adapter for SAP NetWeaver, the attachments of the purchase order are represented as URLs that point to a storage location on an internal domain/server. If the proxy server is configured for the purchase order transaction, then the Ariba Network adapter for SAP NetWeaver accesses these URLs and downloads attachments by going through the proxy server. However, customers primarily use a proxy server to connect to domains/servers outside their firewall. As attachments are normally stored on an internal domain/server that is within the firewall, customers do not want the Ariba Network adapter for SAP NetWeaver to use their proxy server to download and process attachments.

Proxy bypass allows you to configure a list of internal domains/servers that the Ariba Network adapter for SAP NetWeaver can access without using your proxy server to download and process attachments. As a result, when a purchase order with attachments is sent from SAP ERP, the Ariba Network adapter for SAP NetWeaver bypasses the proxy server to download and process attachments.

5.5.1 HTTPS support for attachment processing

Support for HTTPS protocol ensures that the Ariba Network adapter for SAP NetWeaver can download and process attachments that are hosted on a HTTPS domain/server. In this case, the connection to the HTTPS


domain is established using the truststore file or the default JRE cacert file. If the truststore parameter is configured, then you must import the certificates of the HTTPS domains on which attachments are hosted and the SAP Ariba certificate into the truststore file. However, if the truststore parameter is not configured, then you must import the certificates of the HTTPS domains on which attachments are hosted and the SAP Ariba certificate into the cacert keystore of the JRE.

NoteThe HTTPS support is enabled only for certificates available in the file system or JRE's cacert keystore. In addition, only basic authentication (Username and Password) is supported to download attachments hosted on a HTTPS domain/server.

The following graphic displays how the Ariba Network adapter for SAP NetWeaver bypasses the proxy server to access attachments from the SAP Doc Server:

● You have enabled the proxy server configuration in the purchase order communication channel.● In the communication channel for the purchase order transaction, you must specify a list of internal

domain/server names for the Bypass Proxy Server for Domains parameter under the Attachment Configuration section.



5.5.2 How to configure proxy server bypass for attachment processing

Context

You must configure the domains/servers that the adapter must bypass for downloading and processing attachments.

Procedure

1. Log on to your SAP Process Integration system.2. In the Model Configurator, open the communication channel for the purchase order transaction. Under

Communication Channel, double-click the communication channel |BS_ASN|CC_PurchaseOrder_cXML_Receiver or right-click and choose Open.

3. Under the Attachment Configuration section, in the Bypass Proxy Server for Domains field, enter an internal domain/server name or a list of internal domain/server names that the adapter can access by bypassing the proxy server. You can enter multiple domain/server names separated by a comma (,). Some of the sample values for this field are as follows:

○ ariba.com - Adapter bypasses the proxy server for the ariba.com domain.○ xyz.wiki.org - Adapter bypasses the proxy server for xyz.org and the sub domain

xyz.wiki.org.○ schemas.*.org - Adapter bypasses the proxy server for schemas.org and all sub domains of

schemas.org.○ abc.*.org, javajee.com - Adapter bypasses the proxy server for javajee.com, abc.org, and all

sub domains of abc.org.○ *.* - Adapter bypasses the proxy server for all top level domains.○ *.*.* - Adapter bypasses the proxy server for all top level domains and all sub domains of the top

level domain4. Save the changes.

Next Steps

After you configure the proxy server bypass, you must import the security certificates. For more information, see About Configuring Security Certificates [page 51].


5.5.3 Troubleshooting proxy server bypass for attachment processing

Some of the errors that you may encounter during attachment processing are as follows:

Error/ Info Message Description

Http connection status for attachment download is incorrect: <status for URL: <url>

This message is logged in the log file when the attachment processing fails as a result of incorrect HTTP connection status. An email notifi-cation is also sent with the error details to the configured recipient.

You may encounter an error such as No Trusted Certificate Found

To resolve this error, ensure that you have imported the security certificates into the cacert keystore or the truststore (if you have config-ured). For more information, see:

● Importing Security Certificates into the Java JRE Keystore [page 51]

● Importing Security Certificates into the Java JRE TrustStore [page 52].

This message is logged in the log file and an email notification is also sent with the error details to the configured recipient.

Domains configured to bypass proxy server This info message indicates that the attachment is hosted on a domain that is configured for proxy bypass. This message is logged only in the log file.

5.6 Support for 2-way match

In SAP ERP, a user can create a purchase order by including line items that do not require a receipt. Such line items are flagged for a 2-way match that includes only the purchase order and invoice during invoice reconciliation.

When a purchase order containing line items flagged for a 2-way match is sent from your SAP ERP, along with the purchase order, the Ariba Network adapter for SAP NetWeaver sends information about such line items to Ariba Network. When an invoice for this purchase order is sent by Ariba Network to SAP Ariba Invoice Management, SAP Ariba Invoice Management user can reconcile the invoice by performing a 2-way match that includes the purchase order and the corresponding invoice.

Establishing the 2-Way Match Flag in Your SAP ERP

When creating a purchase order in your SAP ERP, by default, all line items are flagged for a 2-way match.



5.7 Using endpoint integrationYou can configure endpoints for outbound documents sent from SAP ERP toAriba Network.

The endpoints in Ariba Network manage and control the flow of data from Ariba Network to the various systems that are connected to it. The endpoint in Ariba Network acts as a document routing placeholder that ensures documents from Ariba Network are sent to the desired system. You can create endpoints in Ariba Network according to your business requirements. If you have configured an endpoint for your SAP ERP in Ariba Network, then you must maintain the endpoint information in the Communication channel in SAP Process Integration.

When your Ariba Network adapter for SAP NetWeaver receives an outbound document from your SAP ERP, the Ariba Network adapter for SAP NetWeaver appends the endpoint information to the cXML and posts the document to Ariba Network. For example, when creating the cXML header for a purchase order, your Ariba Network adapter for SAP NetWeaver checks if the endpoint information is maintained in the communication channel in SAP Process Integration. If yes, then the Ariba Network adapter for SAP NetWeaver includes the endpoint in the cXML header as follows:

<Header> <From> <Credential domain="NetworkId"> <Identity>AN02000076701</Identity> </Credential> <Credential domain="EndPointID"> <Identity>ERPEndPoint1</Identity> </Credential> </From> <To> <Credential domain="NetworkID"> <Identity>AN02000076720</Identity> </Credential> </To> <Sender> <Credential domain="NetworkID"> <Identity>AN02000076701</Identity> <SharedSecret>welcome1a</SharedSecret> </Credential> <UserAgent>Buyer</UserAgent> </Sender> </Header> <Request> <OrderRequest>

ERPEndPoint1 is the value that you have configured in the communication channel in SAP Process Integration.

Example Scenarios

● In your system landscape, you have the SAP Ariba Buying solutions and an ERP system that integrate with Ariba Network. In this case, purchase orders can originate from both the SAP Ariba Buying solutions and SAP ERP. You can create two endpoints, one for theSAP Ariba Buying solutions and the other for SAP ERP. This allows Ariba Network to send the corresponding invoices to the respective systems.

● If you want all your invoices to be sent to the SAP Ariba Buying solutions, you can create and configure an endpoint accordingly.


Related Information

How to enable endpoint integration in SAP Process Integration [page 158]Endpoint integration for multiple ERP systems [page 158]

5.7.1 How to enable endpoint integration in SAP Process Integration

Procedure

1. In the Model Configurator, open the communication channel relevant to the outbound transaction you are configuring. Under Communication Channel, double-click the communication channel or right-click to open it.For example, when configuring the Purchase Order Integration Scenario, in the Model Configurator under Communication Channel, double-click on |BS_ASN|CC_PuchaseOrder_cXML_Receiver to open it.

2. In the Parameters tab, specify a value for the endpoint parameter.3. Save the changes.

NoteYou must set this only if you have configured an endpoint for your SAP ERP in Ariba Network.

5.7.2 Endpoint integration for multiple ERP systems

Configure end points if you have multiple ERP system.

If you have enabled both multi-ERP (for multiple ERP systems) and endpoints in Ariba Network, then you must create system IDs corresponding to the different ERP systems that are present in your system landscape. You then have to create an endpoint for each system ID. For documents that are sent from Ariba Network to ERP, the Ariba Network adapter for SAP NetWeaver uses the system ID to identify the ERP systems that must receive the respective documents. Therefore, it is sufficient to create only one endpoint with the same name for all three system IDs.

When you have multiple ERP systems and you create a purchase order, Ariba Network adapter for SAP NetWeaver checks if the endpoint information is maintained in the communication channel in SAP Process Integration. If yes, then the Ariba Network adapter for SAP NetWeaver includes the endpoint in the cXML header along with the system ID as shown:

Sample Code

<Header> <From> <Credential domain="NetworkId"> <Identity>AN02000076701</Identity> </Credential>



<Credential domain="SystemId"> <Identity>ARB2</Identity> </Credential> <Credential domain="EndPointID"> <Identity>ERPEndPoint1</Identity> </Credential> </From> <To> <Credential domain="NetworkID"> <Identity>AN02000076720</Identity> </Credential> </To> <Sender> <Credential domain="NetworkID"> <Identity>AN02000076701</Identity> <SharedSecret>welcome1a</SharedSecret> </Credential> <UserAgent>Buyer</UserAgent> </Sender> </Header> <Request> <OrderRequest>

ERPEndPoint1 is the value that you have configured in the communication channel in SAP Process Integration and ARB2 is the System ID.

5.8 Using the SAP Process Integration KeyStore

The server and client certificates that cXML Adapter uses to connect to Ariba Network must be stored in the SAP Process Integration keystore. SAP Process Integration provides functionality to manage and administer authentication certificates and keystores. As part of this functionality, you can create keys and certificates in SAP Process Integration and store them in the SAP Process Integration Keystore. The keys and certificates that you create in SAP Process Integration Keystore are grouped bases on views. Therefore, you first need to create a view and then create the required keys and certificates under that view. After you have created the required certificates, you must get them signed by a trusted Certificate Authority (CA) to enable Ariba Network to successfully establish the SSL connection.

As a result, when SAP Process Integration sends or receives documents to/from Ariba Network, based on the channel configuration, the cXML Adapter initializes and creates the Ariba Network TrustStoreView and KeystoreView (only if client certificate is selected) and uses the certificates to ensure a successful SSL handshake.

In the communication channel for all the inbound and outbound transactions, for Trust Store View and KeyStore View (only if you are using client certificate), you must specify the names of the Views that store the Server certificate and Client certificate respectively. For more information, see How to configure the cXML Adapter to use the SAP Process Integration Keystore [page 160].


The cXML Adapter connects to Ariba Network by using certificates that are stored in the SAP Process Integration Keystore as explained in the following graphic:

5.8.1 How to configure the cXML Adapter to use the SAP Process Integration Keystore

Procedure

1. Open the required communication channel.2. Under Authentication, for the Trust Store View parameter, enter the name of the view that contains the

server certificate.3. To use client certificate for authentication to Ariba Network buyer account, for Credential Mode, choose

Client certificate from the dropdown list.4. For the KeyStore View parameter, enter the name of the view that contains the client certificate.5. Click Save.6. Repeat this configuration for all the inbound and outbound transactions.

5.9 PDF invoice copy attachments

In many cases, invoice exception handlers or accounts payable personnel require a rendered format of the invoice data representing the supplier view of the invoice in Ariba Network. They can use the cXML invoice viewer, log into the Ariba Network account to view the invoice, or wait until the invoice PDF is included in the invoice archive.

In addition, customers using a 3rd party AP workflow may need a human readable invoice copy and supplier provided attachments during the approval flow to ensure that the AP approver can review invoice data. This can be achieved by using an early archiving approach to store the human readable invoice copy and other



supplier attachments. To build the early archiving workflow in SAP Process Integration, customers require a single message that contains the cXML invoice, a human readable representation of the invoice data (PDF Invoice Copy) and all supplier provided invoice attachments without storing any of these on the local file system.

PDF invoice copy attachments ensures buying organizations can have their Ariba Network account enabled to generate a copy of the invoice in PDF format and attach it to the invoice. The invoice copy layout of the PDF attachment is very similar to the print layout. This means a structured, complete, and consistent invoice view across the supplier base is now available with every invoice for side-by-side comparison of the supplier invoice view with the buyer invoice view in their SAP ERP.

Language Support

Ariba Network generates the PDF invoice copy attachment in the language of the supplier's locale (which is the preferred language configured for the account administrator). See the Ariba Network Guide to Invoicing for a list of supported languages for PDF invoice copy.

Related Information

Enabling PDF invoice copy attachment [page 161]Using PDF invoice copy attachments [page 163]Processing of PDF invoice copy attachments by the cXML Adapter [page 164]BAdI implementation for the BAdI definition INVOICE_UPDATE [page 166]About configuring SAP ERP for PDF invoice copy attachments [page 172]How to define a new document class for PDF invoice copy attachments [page 172]How to define a new document type for invoice [page 173]How to create a link between the standard business object and the new document type for invoice [page 173]Maintaining the INVOICE_EMAIL_SEND parameter [page 174]Maintaining the ZDEL parameter [page 174]How to configure the attachment processing mode for PDF invoice copy attachments [page 174]

5.9.1 Enabling PDF invoice copy attachment

This feature is disabled by default. To enable this feature, SAP Ariba Customer Support must turn on PDF generations for your Ariba Network account by selecting the option Generate an invoice copy as a PDF attachment to the invoice. Please have your Designated Support Contact log a service request and an SAP Ariba Customer Support representative will follow up to complete the request.

NoteAccounts can be enabled for PDF invoice copy in the archive zip file (if you are archiving invoices) and as attachments to invoices.


The invoicing rule Allow suppliers to send invoice attachments does not impact the PDF invoice copy attachment generation, and therefore the option to send URLs to view attachments on Ariba Network is only available for attachments added by the supplier. If PDF invoice copy generation is enabled in your Ariba Network account, all PDF invoice copy attachments are displayed as URLs.

Requirements

In the communication channel for the invoice transaction, you must configure the following parameters depending on how you want to process the invoice data, PDF invoice copy, and other attachments that are part of an invoice downloaded from Ariba Network.

Parameter Description

Attachment Processing Mode You can specify the following values:

● Use Local File System – If you specify this value, you must also provide a value for the Attachment Download Location parameter. This is the default option.

● Use Shared File System – If you specify this value, in addition to specifying a value for the Attachment Download Location parameter, you must specify values for the following parameters:○ Shared System Machine Name○ Shared System Machine User ID○ Shared System Machine Password

● Embedded In cXML – The cXML Adapter encodes the attachment contents to a Base 64 string using rg.apache.commons.codec.binary.Base64 and embeds the Base 64 string to the header part of the invoice cXML.

Attachment Download Location (only applicable for File system Mode)

A location on the file system where the cXML Adapter must download PDF invoice copy and other attachments that are part of the invoice cXML.

Store cXML Document (Optional) (only applicable for Local or Shared File System Mode)

The cXML Adapter stores the invoice cXML file to the file system location you specified for the Attachment Download Location parameter.

For more information, see Configuring the Attachment Processing Mode for PDF Invoice Copy Attachments [page 174].

Note

● If SAP Process Integration is running on Windows, then you have to use the Use Shared File System option. As a result, you need to specify the machine name of your SAP ERP system and the Admin username and password to access your SAP ERP system. In addition, you must provide a value for the Attachment Download Location parameter. The value must be a location in the file system of your SAP ERP system where attachments need to be downloaded. The cXML Adapter logs into the SAP ERP system and downloads the attachments in the file system location you specified.

● If SAP Process Integration is running on Linux and you want to use the Use Local File System, then you need to provide a value for the Attachment Download Location parameter. The value must be a location in the file system of your SAP ERP system that is mounted locally to a location in the file system of your SAP Process Integration system. The mounted folder path must be same to the actual folder path in the SAP ERP system. For example, if the folder location in the SAP ERP system is - /home/usr/attachment then



the mounted path in SAP Process Integration must be - /home/usr/attachment. The SAP service user must have Write permission to the mounted folder path in the SAP Process Integration system and the SAP service user must have Delete permission to the folder path in the SAP ERP system. In this case, the cXML Adapter downloads the attachments locally in the mounted path.

● If SAP Process Integration is running on Linux and you want to use the Use Shared File System, then you need to specify the machine name of your SAP ERP system and the Admin username and password to access your SAP ERP system. In addition, you need to provide a value for the Attachment Download Location parameter. The value must be a shared location in the file system of your SAP ERP system. To ensure that the cXML Adapter can write to this shared location, the Samba Server must be installed and configured in your SAP ERP system to accept NTLM authentication.

5.9.2 Using PDF invoice copy attachments

If your account has been enabled to generate PDF invoice copy attachments, PDF invoice copies are generated and attached to the following supplier-submitted invoice types:

● Invoices submitted through EDI or cXML that are not self-signed by the supplier● Manually created PO-based or non-PO invoices● Invoices created through CSV import● Supplier self-signed invoices

PDF copies of invoices are not generated for the Invoice Conversion Services (ICS) invoice. For this invoice, the provider or supplier is expected to include a PDF invoice copy as an invoice attachment if required.

Data Flow Overview

A PDF copy of the invoice data is automatically added as a Multipurpose Internet Mail Extension (MIME) attachment to the invoice cXML as follows:

<InvoiceDetailRequestHeader> <Extrinsic name="invoicePDF"> <Attachment> <URL>cid:[email protected]</URL> </Attachment> </Extrinsic> </InvoiceDetailRequestHeader>

The PDF invoice copy includes the text Copy of Invoice - Not A Tax Invoice to indicate that the cXML invoice remains the legal document.

The file name for the PDF invoice copy attachment is a randomized file name, for example: kBAIGmcwmN502a7638191182029.pdf


5.9.3 Processing of PDF invoice copy attachments by the cXML Adapter

When the cXML Adapter downloads an invoice with attachments from Ariba Network, the processing of attachments by the cXML Adapter depends on the value you specify for the Attachment Processing Mode parameter in the communication channel for the invoice transaction. You can specify Use Local File system, Use Shared File System, or Embedded In cXML. The processing by the cXML Adapter for all these options is explained as follows:

“Use Local File System” or “Use Shared File System” Option

When the cXML Adapter downloads a document with attachments from Ariba Network, it receives the attachment in a MIME message. If you selected Use Local File System or Use Shared File System, the cXML Adapter:

1. Stores the PDF copy of the invoice and other attachments available in the MIME message to the file system location you specified for the Attachment Download Location parameter.

2. Prefixes the filename of an attachment with the payload ID and a random number. This allows the adapter to differentiate attachments within documents and attachments between documents.

NoteThe attachment processing can fail if for example, you have not provided any value for the Attachment Download Location field or the cXML Adapter does not have access to the storage location. In this case, an exception is logged in the log file.

3. Generates a file URL for each attachment that indicates the location of the downloaded attachment. The URL is a unique content ID that the cXML Adapter assigns for each attachment. The URL is prefixed with the word cid. The adapter then adds the file URLs under the Extrinsic element tag with the attribute name as invoicePDF (for the PDF invoice copy) and SupplierAttachments (for other attachments) to the header part of the invoice cXML. The URLs are added to the header part because line level attachments are not supported in SAP ERP systems. In addition, URLs at header level ensure the integrity of a document if it is digitally signed.

4. Sends the modified invoice cXML to the mapping services for transformation in SAP Process Integration. During transformation, the file URLs are mapped to IDOC fields. You must implement a BADI for the BADI definition INVOICE_UPDATE in the customer namespace to ensure that when the IDOC reaches the SAP ERP system, the following tasks can be performed:○ Accesses the attachments from the location specified in the IDOC○ Stores the attachments in the SAP Archive Link○ Assigns the attachments to the invoice created in the SAP ERP

To implement the BADI, see BADI Implementation for the BADI Definition INVOICE_UPDATE.



“Embedded In cXML” Option

If you selected Embedded In cXML, after downloading the invoice with attachments (PDF copy of the invoice and other supplier provided attachments) from Ariba Network:

1. The cXML Adapter encodes the attachment contents to a Base 64 string using rg.apache.commons.codec.binary.Base64.

2. For the PDF copy of the invoice, the cXML Adapter adds the Extrinsic invoicePDF to the header part of the invoice cXML and embeds the Base 64 string within this Extrinsic element. See following sample.

3. For other attachments from the supplier, the cXML Adapter adds the Extrinsic SupplierAttachments to the header part of the invoice cXML and embeds the Base 64 string within this extrinsic element. If multiple attachments are there, the Base 64 strings for all attachments are embedded within this extrinsic element within <data>...<data/> elements as displayed in the following sample:

The cXML structure with the PDF copy of invoice and two supplier added attachments appears as follows:

<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE cXML …> <cXML timestamp=“…" payloadID="12345666…"><Header>…<To> <Correspondent> <Extrinsic name= “invoicePDF”> <Attachment> <data contentType= “application/pdf” fileName = “ABC.pdf”> Base64 encoded string AAgFBgcGBQgHBgcJCAgJDBQNDAsLDBgREg4UHRkeHhwZHBsgJC4nICIrI </data> </Attachment></Extrinsic> <Extrinsic name= “SupplierAttachments”> <Attachment> <data contentType= “application/pdf” fileName = “XXX.pdf”> Base64 encoded string AAgFBgcGBQgHBgcJCAgJDBQNDAsLDBgREg4UHRkeHhwZHBsgJC4nICIrI </data> </Attachment> <Attachment> <data contentType= “application/pdf” fileName = “YYY.pdf”> Base64 encoded string AAgFBgcGBQgHBgcJCAgJDBQNDAsLDBgREg4UHRkeHhwZHBsgJC4nICIrI </data> </Attachment></Extrinsic></Correspondent> </To></Header><Request> <InvoiceDetailRequest> <InvoiceDetailRequestHeader … <Comments>… <Extrinsic name="… </InvoiceDetailRequestHeader></Request><ds:Signature xmlns:xades="… </cXML>

1. The cXML Adapter sends the single cXML message that contains the cXML invoice, PDF invoice copy attachment, and other attachments.

2. To process this cXML message, you need to build a custom workflow in SAP Process Integration to ensure that:


○ The invoice is created in your SAP ERP.○ Early or late archiving of attachments is complete.○ The attachments are assigned to the corresponding invoice.○ The attachments are deleted from the location where they were downloaded.○ The cXML invoice itself (including the e-signature if signed) is archived.○ An email ID is configured to receive email notifications if attachment processing fails in your SAP ERP.

NoteYou need to decode the Base 64 string using apache.commons.codec.binary.Base64.

The configuration parameters for attachment processing mentioned in the Requirements sections Enabling PDF invoice copy attachment [page 161] are also available for the Order Confirmation and Ship Notice transactions. As a result, the cXML Adapter processes attachments of these transactions similar to the manner in which it processes attachments of the invoice transaction.

5.9.4 BAdI implementation for the BAdI definition INVOICE_UPDATE

Write the following code in the method CHANGE_BEFORE_UPDATE.

**************************************************************************************

This implementation is done to attach SAP Archive Link attachment to an invoice. The invoice number will be generated in this method in S_RBKP_NEW-BELNR. The IDOC number is stored in S_RBKP_NEW-SGTXT. The TIF/PDF URL path is fetched from table EDID4 by passing the IDOC number. After getting the URL path, the attachment document is taken from the specified location and the same is stored in SAP Archive Link using function module SCMS_AO_FILE_CREATE. Once the attachment is stored, the document is assigned to the invoice using function module ARCHIV_CONNECTION_INSERT. The attachment document is deleted from the source location immediately after the document is stored in SAP Archive link. If the document is not attached to the invoice, an email is sent to the email ID maintained in /ARBA/PARAM_TAB. The parameter to maintain the email ID is INVOICE_EMAIL_SEND.

**************************************************************************************

Types Declaration TYPES : BEGIN OF ty_path, docnum TYPE edi_docnum, counter TYPE edi_clustc, segnum TYPE idocdsgnum, segnam TYPE edi_segnam, psgnum TYPE edi_psgnum, dtint2 TYPE edi_dtint2, sdata TYPE edi_sdata, END OF ty_path.TYPES : BEGIN OF ty_documents, filepath TYPE char255, END OF ty_documents. TYPES : BEGIN OF ty_object, objectid TYPE saeobjid, END OF ty_object. TYPES : BEGIN OF ty_error, error TYPE char75, doc TYPE char255,



END OF ty_error. TYPES : BEGIN OF ty_delete, objectid TYPE saeobjid, doc TYPE char75, END OF ty_delete.*Data Declaration DATA : l_objectid TYPE saeobjid, l_doctype TYPE saedoktyp, l_counter(4) TYPE c, l_filetype TYPE e1edkt1, l_idoc TYPE char70, l_lines TYPE i, l_sep TYPE c VALUE '.', l_sapsystem TYPE string VALUE 'NONE', l_machineinfo TYPE rfcsi, l_pathname TYPE char255, l_filename TYPE char255, l_phys_path TYPE char255, l_archiveid TYPE saearchivi VALUE 'MA', l_documentid TYPE saeardoid, l_sap_object TYPE saeanwdid VALUE 'BUS2081', l_segment TYPE edi_segnam.*Internal table DATA : t_path TYPE TABLE OF ty_path, t_filepath TYPE TABLE OF ty_path, t_documents TYPE TABLE OF ty_documents, t_object TYPE TABLE OF ty_object, t_extension TYPE TABLE OF string, t_error TYPE TABLE OF ty_error, t_packlist TYPE TABLE OF sopcklsti1, t_message TYPE STANDARD TABLE OF solisti1, t_receivers TYPE TABLE OF somlreci1, t_param TYPE TABLE OF /ARBA/param_tab, t_deletefile TYPE TABLE OF ty_delete.*Work area DATA : wa_path TYPE ty_path, wa_filepath TYPE ty_path, wa_documents TYPE ty_documents, wa_object TYPE ty_object, wa_extension TYPE string, wa_error TYPE ty_error, wa_packlist TYPE sopcklsti1, wa_message TYPE solisti1, wa_receivers TYPE somlreci1, wa_param TYPE /ARBA/param_tab, wa_deletefile TYPE ty_delete.*Clearing variables, work areas and internal tables CLEAR : l_objectid, l_doctype, wa_path, wa_filepath, wa_documents, wa_object, l_counter, l_idoc, l_lines, l_doctype, wa_error, wa_packlist, wa_message, wa_receivers, wa_param, wa_deletefile, l_machineinfo.*Clearing internal tables FREE : t_path, t_filepath, t_documents,


t_object, t_extension, t_error, t_packlist, t_message, t_receivers, t_param, t_deletefile.*Email data declarations DATA : l_docdata TYPE sodocchgi1, l_subject(200) TYPE c, l_output TYPE char20, l_time TYPE char8, l_date TYPE char200, l_delimiter TYPE c. CONSTANTS: c_windows TYPE char7 VALUE 'Windows', c_windowsu TYPE char7 VALUE 'WINDOWS', c_aribainvoice TYPE char9 VALUE 'ARIBA_ASN'.*If IDOC number exists IF s_rbkp_new-sgtxt IS NOT INITIAL AND s_rbkp_new-bktxt EQ c_aribainvoice.*Fetching the File Path from EDID4 SELECT docnum counter segnum segnam psgnum dtint2 sdata FROM edid4 INTO TABLE t_path WHERE docnum = s_rbkp_new-sgtxt AND segnam IN ('E1EDKT1','E1EDKT2').*Taking the Filepath's into a separate internal table FREE t_filepath[ ]. t_filepath[] = t_path[ ]. SORT t_filepath BY segnum psgnum segnam. DELETE t_filepath WHERE segnam NE 'E1EDKT2'.*Taking E1EDKT1 into separate internal table SORT t_path BY segnam. DELETE t_path WHERE segnam NE 'E1EDKT1'.*If file path exists for the invoice IF t_path IS NOT INITIAL. LOOP AT t_path INTO wa_path. CLEAR: l_filetype, l_segment, l_idoc. IF wa_path-segnam = 'E1EDKT1'. l_filetype = wa_path-sdata. l_segment = wa_path-segnum. ENDIF. IF l_filetype-tdid = '0' OR l_filetype-tdid = '1'. LOOP AT t_filepath INTO wa_filepath WHERE segnam = 'E1EDKT2' AND psgnum = l_segment. l_idoc = wa_filepath-sdata+0(70). CONCATENATE wa_documents-filepath l_idoc INTO wa_documents-filepath. ENDLOOP.*Taking Filepath into separate internal table. APPEND wa_documents TO t_documents. CLEAR wa_documents. ENDIF. ENDLOOP.*Clearing variables CLEAR:l_machineinfo, l_delimiter.



*Getting the ERP system machine details(Windows or Linux) CALL FUNCTION 'RFC_GET_SYSTEM_INFO' EXPORTING destination = l_sapsystem IMPORTING rfcsi_export = l_machineinfo.* The attachment location path which comes from SAP XI will be like* (/usr/sap). This will contain forward slash. If the SAP ERP system* is Windows machine, the file attachment location path need to be like* (\usr\sap). IF l_machineinfo-rfcopsys+0(7) = c_windows OR l_machineinfo-rfcopsys+0(7) = c_windowsu. l_delimiter = '\'. ENDIF. LOOP AT t_documents INTO wa_documents. CLEAR : l_pathname, l_filename, l_documentid.*Getting the file format FREE t_extension. CLEAR: l_lines, l_doctype.*Splitting the file path SPLIT wa_documents-filepath AT l_sep INTO TABLE t_extension. DESCRIBE TABLE t_extension LINES l_lines. READ TABLE t_extension INTO wa_extension INDEX l_lines.*Passing document type l_doctype = wa_extension. TRANSLATE l_doctype TO UPPER CASE.*Concatenate Invoice number with Fiscal year CONCATENATE s_rbkp_new-belnr s_rbkp_new-gjahr INTO l_objectid.*All backward slashes are replaced with forward slashes*in case of Windows machine. IF l_delimiter = '\'. REPLACE ALL OCCURRENCES OF '/' IN wa_documents-filepath WITH l_delimiter. CONCATENATE l_delimiter wa_documents-filepath INTO wa_documents-filepath. ENDIF.*Splitting File path and File name PERFORM split_path IN PROGRAM oaall USING wa_documents-filepath l_pathname l_filename.*Function Module Stores files to Archive Link CALL FUNCTION 'SCMS_AO_FILE_CREATE' EXPORTING arc_id = l_archiveid file = l_filename path = l_pathname doc_type = l_doctype no_delete = 'X' IMPORTING doc_id = l_documentid EXCEPTIONS error_http = 1 error_archiv = 2 error_kernel = 3 error_config = 4 error_file = 5 OTHERS = 6. IF sy-subrc <> 0.*If document is not stored in archivelink, the error*messages are populated into internal table wa_error-doc = wa_documents-filepath. APPEND wa_error TO t_error. CLEAR wa_error. ELSE.


*Assigning the Archive Link document to the invoice CALL FUNCTION 'ARCHIV_CONNECTION_INSERT' EXPORTING archiv_id = l_archiveid arc_doc_id = l_documentid ar_object = 'ZMMILOGINV' mandant = sy-mandt object_id = l_objectid sap_object = l_sap_object doc_type = l_doctype EXCEPTIONS error_connectiontable = 1 OTHERS = 2. IF sy-subrc <> 0.*IF sap ARCHIVE link DOCUMENT IS NOT ASSIGNED to invoice, the error*messages are populated into internal table wa_error-doc = wa_documents-filepath. APPEND wa_error TO t_error. CLEAR wa_error. ELSE.*Deleting the attachment file from the location after the*attachment is stored in archivelink and assigned to invoice DELETE DATASET wa_documents-filepath. ENDIF. ENDIF. ENDLOOP. ENDIF.*If attachment is not assigned to invoice, email*sent to the specified users IF t_error[ ] IS NOT INITIAL.*getting email IDs from the /ARBA/PARAM_TAB SELECT * FROM /arba/param_tab INTO TABLE t_param WHERE name = 'INVOICE_EMAIL_SEND'. IF sy-subrc = 0.*Email Subject CLEAR : l_output, l_time.*Converting date format CALL FUNCTION 'CONVERSION_EXIT_LDATE_OUTPUT' EXPORTING input = sy-datum IMPORTING output = l_output.*Time Formatting CONCATENATE sy-uzeit+0(2) ':' sy-uzeit+2(2) ':' sy-uzeit+4(2) INTO l_time.*Forming the subject of the email l_subject = text-002. l_docdata-doc_size = 1. l_docdata-obj_langu = sy-langu. l_docdata-obj_name = 'SAPRPT'. l_docdata-obj_descr = l_subject. l_docdata-sensitivty = 'F'.*Forming Body of the email message wa_message-line = text-003. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message.*Populating Date in the email message



CLEAR l_date. CONCATENATE 'Date:' l_output l_time sy-zonlo sy-datum+0(4) INTO l_date SEPARATED BY space. wa_message-line = l_date. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message.*Populating invoice document number with the email message CLEAR l_date. CONCATENATE text-005 s_rbkp_new-belnr INTO l_date SEPARATED BY space. wa_message-line = l_date. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = text-006. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message.*Populating the attachment URL's which are not attached*to the invoice in the email message LOOP AT t_error INTO wa_error. wa_message-line = wa_error-doc. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message. ENDLOOP. wa_message-line = text-007. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = text-008. APPEND wa_message TO t_message. CLEAR wa_message.* Populating the system ID CLEAR l_date. CONCATENATE text-009 sy-sysid sy-mandt INTO l_date SEPARATED BY space. wa_message-line = l_date. APPEND wa_message TO t_message. CLEAR wa_message. wa_packlist-transf_bin = space. wa_packlist-head_start = 1. wa_packlist-head_num = 0. wa_packlist-body_start = 1. DESCRIBE TABLE t_message LINES wa_packlist-body_num. wa_packlist-doc_type = 'RAW'. APPEND wa_packlist TO t_packlist.*Populating the receipients LOOP AT t_param INTO wa_param. wa_receivers-receiver = wa_param-low. wa_receivers-rec_type = 'U'. wa_receivers-com_type = 'INT'. wa_receivers-notif_del = 'X'. wa_receivers-notif_ndel = 'X'. APPEND wa_receivers TO t_receivers.


ENDLOOP.*Calling function module to send email CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1' EXPORTING document_data = l_docdata put_in_outbox = 'X' commit_work = 'X' TABLES packing_list = t_packlist contents_txt = t_message receivers = t_receivers EXCEPTIONS too_many_receivers = 1 document_not_sent = 2 document_type_not_exist = 3 operation_no_authorization = 4 parameter_error = 5 x_error = 6 enqueue_error = 7 OTHERS = 8. IF sy-subrc <> 0. ENDIF. ENDIF. ENDIF. ENDIF.

5.9.5 About configuring SAP ERP for PDF invoice copy attachments

To ensure that the PDF invoice copy attachment is processed in SAP ERP, you must:

● Define a new document class.● Define a new document type for invoice.● Create a link between the standard business object and the new document type.● Maintain values for INVOICE_EMAIL_SEND and ZDEL parameters.

5.9.6 How to define a new document class for PDF invoice copy attachments

Procedure

1. Log on to your SAP ERP system.2. Start transaction OAD2.

3. Click New Entries.4. In the Doc Class field, enter PDF.

5. In the Description field, enter a description for the document class. For example, Portable Document Format.

6. In the MIME type field, application/pdf.



7. In the Application field, enter the name of the application that will read the attached invoice PDF. For example, SAPHTML.

8. Click Save.

5.9.7 How to define a new document type for invoice

Procedure

1. Log on to your SAP ERP system.2. Start transaction OAC2.

3. In the Doc. Type field, enter a document type for invoices.

NoteYou can copy the standard document type for invoice called MMILOGINV and create a new document type starting with Z. In this case, ensure that the value of the Status field is X. You must ensure that the Status of the document type is active.

4. In the Long Name field, enter a long name for the document type.5. In Doc.Class field, enter the document class that you created earlier. For example, PDF.6. In the Status field, enter X.

7. Click Save.

5.9.8 How to create a link between the standard business object and the new document type for invoice

Procedure

1. Log on to your SAP ERP system.2. Start transaction OAC3.

3. Click New Entries.4. In the Object Type field, enter bus2081 (Standard business object for incoming invoice).

5. In the Document type field, enter the document type you created earlier.6. In the Link Status field, enter X.

7. In the Storage system field, enter MA.

8. In the Link field, enter TOA01.

9. In the Retention per. Field, enter 0.

10. Click Save.


5.9.9 Maintaining the INVOICE_EMAIL_SEND parameter

SAP Ariba recommends you to specify an email address or multiple email addresses as a value for the parameter INVOICE_EMAIL_SEND in the /ARBA/PARAM_TAB table. This ensures that when a failure occurs while storing the attachments in the SAP Archive Link or assigning the attachments to the invoice, an email notification is sent to the specified email addresses.

5.9.10 Maintaining the ZDEL parameter

You need to specify the delete command for the ZDEL parameter by using transaction SM69. This ensures that once the BADI accesses the attachments from the file location, stores them in the SAP Archive Link, and assigns them to the invoice, the attachments in the file location are deleted.

5.9.11 How to configure the attachment processing mode for PDF invoice copy attachments

Procedure

1. Log on to your SAP Process Integration system.2. In the Model Configurator, open the communication channel for the invoice transaction. Under

Communication Channel, double-click the communication channel |BS_ASN|CC_Invoice_cXML_Sender or right-click and choose Open.

3. Under the Attachment Configuration section, specify values for the relevant parameters.4. Save the changes.

5.10 Integrating SAP ERP with the SAP Ariba Commerce Automation solution

Support for SAP ERP integration with the SAP Ariba Commerce Automation solution is available in SAP ERP 6.0 EHP0 or higher with SAP Process Integration 7.1 or higher.

You need to configure the integration scenario for the Request for Quotation transaction in the Integration Directory to be able to run SAP Ariba Commerce Automation transactions. For more information about configuring the Request for Quotation integration scenarios, see Request for Quotation Integration Scenario [page 132].

For more information about configuring your SAP ERP for Quote Request and Quote Message cXML documents, see Configuring Quote Request and Quote Message Documents [page 305].

For more information about Requests for Quotation, see the RFQ and award integration with SAP Ariba Sourcing.



Related Information

SAP ERP integration [page 176]Enabling SAP ERP and SAP Ariba Commerce Automation integration [page 179]SAP ERP and SAP Ariba Commerce Automation integration requirements [page 179]SAP ERP and SAP Ariba Commerce Automation integration limitations [page 179]Configuring Ariba Network buyer settings for RFQ events [page 180]Messages mapping for SAP Ariba Commerce Automation [page 180]Handling cXML document errors for SAP Ariba Commerce Automation [page 180]

5.10.1 About SAP ERP and SAP Ariba Commerce Automation integration

Ariba Network allows buying organizations to integrate their SAP ERP systems with the Ariba Network for the purpose of creating RFQ events. This enables you to manage quotes and purchase orders from within your SAP ERP system with the added benefits of SAP Ariba Sourcing award functionality and Ariba Network supplier research.

RFQ events are automated request for quotations (RFQs), created through a direct integration between your SAP ERP and Ariba Network, that allows you to build and publish tactical sourcing events with little to no action from project owners in SAP Ariba Sourcing. RFQ events are ideal for smaller events, for example an event with 3 to 4 suppliers, allowing you to quickly experience online sourcing without a substantial commitment of time or resources.

RFQ events originate in a your SAP ERP system and are sent across the Ariba Network to SAP Ariba Sourcing, where an RFQ event is created and published on SAP Ariba Discovery. Suppliers can either be invited as part of the RFQ event or matched through SAP Ariba Discovery. Invited and matched suppliers receive notifications about the RFQ event from Ariba Network and can then respond directly to the RFQ event in SAP Ariba Sourcing.

Depending on how the SAP Ariba Commerce Automation template is configured, supplier responses can automatically be sent back to the originating SAP ERP with no action from project owners or you can manually award suppliers directly in the SAP Ariba Commerce Automation solution.


The SAP Ariba Commerce Automation solution supports the ability to upload suppliers from your SAP ERP in to Ariba Network. Uploaded suppliers are invited to create an Ariba Network account through automated notifications, whether the suppliers are buyer invited, Ariba matched, or Ariba suggested.

For more information about the SAP Ariba Commerce Automation solution, see the Quote automation configuration and integration guide in the Administrators section of the Learning Center.

5.10.2 SAP ERP integration

Users can initiate an RFQ event from their SAP ERP system and receive winning bids back as SAP ERP purchase orders using the Ariba Network adapter for SAP NetWeaver. Using the RFQ Module in their SAP ERP, users can create a request for quotation from a purchase requisition or from scratch. SAP Ariba sends the winning bid information back to the SAP ERP and a purchase order is created in SAP ERP.

One Vendor Limitation

SAP ERP only supports the ability to invite one specific supplier using the invited supplier method. If you want to invite multiple suppliers to your RFQ event, you can create a vendor in SAP ERP to workaround the SAP ERP limitation. For example, create an “Ariba Marketplace Vendor” and configure it to not send any vendor information in the Quote Request cXML document. In this case, the SAP Process Integration does not send supplier information to SAP Ariba and SAP Ariba invites multiple suppliers in the vendor and public matching methods.

To overcome the one vendor limitation, you must maintain the following value mappings in the SAP Process Integration system:

● Source Agency "RFQ_ERP" with scheme "VendorConfig"● Target Agency "RFQ_XI" with scheme "VendorConfig"



SAP ERP RFQ Process

To create an RFQ event in SAP Ariba, SAP ERP users create an RFQ in SAP ERP MM Standard RFQ Module. Users can create RFQs in SAP ERP from a purchase requisition, from scratch, or potentially from an existing ERP contract. Users select a supplier matching option, enter event open and close dates, and specify line items with material groups and receiving plants.

The supplier matching type is tied to the document type and a value mapping must be maintained. A new document type can be created for this purpose or an existing document type can be used.

SAP ERP Quote Message Process

After a RFQ event ends, SAP Ariba sends a Quote Message cXML document with the winning bid results back to SAP ERP. The Quote Message cXML document is transformed and mapped to BAPI structures in SAP Process Integration and a purchase order is created through RFC.

One Time Vendors

When you configure the default RFQ transaction rules in Ariba Network Buyer, Ariba Network sends the Quote Message cXML document to your ERP system. If the default RFQ transaction rule is not configured in Ariba Network Buyer, the Quote Message cXML document stays in the Ariba Network and is not sent to your SAP ERP.

When the default RFQ transaction rule is configured to send the Quote Message cXML document to your SAP ERP, a purchase order cannot be created in your SAP ERP if the vendor does not exist in your SAP ERP. To overcome this issue, you can use the one time vendor functionality available in SAP ERP.

Utilizing the one time vendor functionality involves creating a one time vendor in SAP ERP and specifying the one time vendor ID in the SAP Process Integration configuration mapping. After the one time vendor ID is mapped in the SAP Process Integration configuration, purchase orders are created using the one time vendor ID and the address for the vendor who submitted the bid.

Additional Data Validation

When a purchase order is created in SAP ERP, the quote number is stored on the purchase order as the reference document number. The RFQ number is not stored on the purchase order because SAP ERP validates if the supplier on the RFQ and purchase order are the same. In the approved and public vendor scenarios, the system uses the "Ariba Market Place" vendor, so the vendors on the purchase order and RFQ do not match and the RFQ reference is not stored on the purchase order. You can view the logs to verify that the supplier on the RFQ and purchase order are the same.

Logging for purchase order creation:

● TCode used- /nslg1


● Object - /ARBA/ASCADAPTER● SubObject- /ARBA/QUOTEMESSAGE

The following is an example of the log for a successfully created purchase order:

The following is an example of the log for a purchase order that receives a warning:

The following is an example of the log for a purchase order that receives an error:



5.10.3 Enabling SAP ERP and SAP Ariba Commerce Automation integration

To enable the RFQ event functionality, please contact your Customer Success Manager or Account Manager for more information on the SAP Ariba Commerce Automation Solution.

The SAP Ariba Commerce Automation solution must be deployed in a new realm, RFQ functionality cannot be used in existing SAP Ariba Sourcing realms. Suppliers must be registered on the Ariba Network for Suppliers to participate in RFQ events.

5.10.4 SAP ERP and SAP Ariba Commerce Automation integration requirements

SAP Ariba Commerce Automation integration with SAP ERP requires SAP ERP 6.0 EHP0 or higher with SAP Process Integration 7.1 or higher.

To support the integration of RFQs and QuoteMessages, following two request types are available:

● QuoteRequest● QuoteMessage

You are required to run the configuration wizard for the request types in order to create the communication channel.

Ensure that you use only the following cXML versions:

● SAP Ariba cloud integration release 6.0 and higher: cXML version 1.2.025 or higher for RFQ and QuoteMessage transactions

● SAP Ariba cloud integration release 8.0: cXML version 1.2.030 or higher● SAP Ariba cloud integration release 9.0: cXML version 1.2.031 or higher● SAP Ariba cloud integration release 9.0 SP1: cXML version 1.2.033 or higher● SAP Ariba cloud integration release 9.0 SP2: cXML version 1.2.034 or higher

NoteMake the necessary changes to the parameter cXML Version in the Communication Channel.

5.10.5 SAP ERP and SAP Ariba Commerce Automation integration limitations

SAP Ariba Commerce Automation integration with SAP ERP has the following limitations:

● The Ariba Network adapter for SAP NetWeaver only supports the ability to invite one supplier through the Invited supplier case. Users should create an Ariba Marketplace Vendor, that allows them to invite all approved vendors to the RFQ event.

● SAP ERP does not support the ability to add attachments to the RFQ line item level.


● The Ariba Network adapter for SAP NetWeaver only supports the ability to send the lead bid back to SAP ERP and does not support the ability to send all bidding results to SAP ERP.

● After SAP Ariba sends back the bidding results, users can only create purchase orders in SAP ERP.● Quote attachments are not transferred to purchase orders.● One-time vendor option does not support purchase order automation.● SAP Ariba does not support the ability to make changes after the RFQ event is published. If changes are

made in SAP ERP after the RFQ event is published, the event will fail and SAP Ariba will send an email notification to the SAP ERP initiator.

● Ariba Network adapter for SAP NetWeaver only support "simple" service line items (service line item hierarchies with one level). You cannot create an RFQ with service sheets containing more than one level in the hierarchy.

5.10.6 Configuring Ariba Network buyer settings for RFQ events

In order for Ariba Network to forward quotes from public suppliers, you must configure the default transaction rules in Ariba Network.

When you enable the RFQ event rule in Ariba Network and the quote message supplier does not exist in your SAP ERP, the one time vendor specified in SAP ERP is used for the transaction. When the rule is disabled, quote messages are not sent to your SAP ERP and they will fail in Ariba Network. In this case, you must create a proper relationship with the supplier and then resend the quote message from Ariba Network.

5.10.7 Messages mapping for SAP Ariba Commerce Automation

The following SAP Ariba Commerce Automation mapping namespaces are available:

● http://ariba.com/xi/ASN/QuoteRequest● http://ariba.com/xi/ASN/QuoteMessage

For more information, see the mapping worksheets on https://support.ariba.com/Connect/Log_In .

5.10.8 Handling cXML document errors for SAP Ariba Commerce Automation

If the Quote Request cXML document fails in mapping, fix the error and republish the IDoc. If the Quote Message cXML document encounters an error, fix the error and resend the cXML document from the Ariba Network.




5.11 Integration of catalog data in SAP ERP and Ariba Network

When you upgrade to a higher version of the SAP ERP transports, ensure that you make the necessary changes on your SAP Process Integration and SAP ERP system.

About integration of catalog data in SAP ERP and Ariba Network [page 181]

Enabling the integration of catalog data [page 182]

Workflow [page 183]

Using the Catalog export program [page 183]

About processing Purchase Information Records and Material Master Records [page 184]

Uploading catalog changes using mediated connectivity [page 187]

Uploading catalog changes using the incremental load [page 187]

Maintaining catalog fields [page 187]

Configuring catalog data integration [page 188]

5.11.1 About integration of catalog data in SAP ERP and Ariba Network

This feature is applicable for SAP Process Integration 7.3, 7.31, or 7.4 and all SAP ERP 6.0 (EHP5 and higher versions).

The Ariba Network adapter for SAP NetWeaver allows buyers to integrate catalog data from an SAP ERP to Ariba Network seamlessly. Customers can extract the catalog data from the Purchase Information records and Materials Master records to create catalog items in a CIF file and send it to Ariba Network and SAP Ariba Buying solutions.

Creating a catalog file from an SAP ERP allows buyers to:

● Readily find items that are available and in stock directly from SAP ERP● Prevent purchase orders from being canceled or put on hold due to unavailability of items● Allow direct purchasing on SAP ERP● Support creation of the CIF items in multiple languages

The catalog data extracted from the Purchase Information records and Materials Master records are saved as catalog items in a CIF file. The CIF file contains both mandatory and optional fields that suppliers can use while maintaining the catalog files.

For more information about the CIF files, see the Ariba Catalog Format Reference Guide in the Product Documentation > For Users section of the Learning Center.

Using the /ARBA/BUYER_CATALOG_EXPORT program, buyers can integrate the catalog data using the following methods:

● Full and incremental load


● Mediated Connectivity

Buyers can use the shared secret authentication or the client-based certification to integrate the catalog data from SAP ERP to Ariba Network. For more information on the shared secret authentication and client-based certification, see the Setting up Ariba Network adapter for SAP NetWeaver guide.

5.11.2 Enabling the integration of catalog data

This section details the requirements to integrate catalog data on SAP ERP. See the Limitations section for functionalities that are not currently supported.

Prerequisite

To upload the catalog CIF file for the full and incremental through the mediated connectivity, buyers must do the following:

● Ensure that the supplier for that you are uploading the catalog must exist on Ariba Network and SAP Ariba Buying solutions. The supplier must have an active trading relationship with the buyer. For more information about creating a buyer-supplier relationship, see the Ariba Network Integration Guide.

● Customers must validate and publish the catalog sent from SAP ERP from their Ariba Network account. They must also validate the catalog based on the catalog rules specified on SAP Ariba Buying solutions.

● Ensure that the commodity codes and unit of measure that you maintain on SAP ERP must also exist on Ariba Network and SAP Ariba Buying solutions.

● Buyers must ensure that they enable the option, Allow multi-supplier CIF and set the parameter System.Catalog.Network.DefaultMSCif on their SAP Ariba Buying solutions to support a multi-supplier catalog CIF file from Ariba Network. For information about multi-supplier CIF catalogs in SAP Ariba Buying solutions, see the Catalog Administration Guide for your SAP Ariba Buying solutions.

● If the Ariba Network supplier account is configured to use digital certificate authentication, then a valid Secure Socket Layer (SSL) client certificate from one of Ariba Network's trusted Certificate Authorities is required. For more information, see About Configuring Security Certificates section.

● Enable Supplier as the System Type in the cXML Configuration section while configuring the communication channel for catalogs. To do this, you must also configure the integration scenario for uploading catalogs. For more information, see Topics about configuring outbound transactions [page 90].

● Configure the shared secret authentication or the client-based certificate authentication.● Ensure that you configure the proxy setting for single and dual stack on your SAP ERP system. For more

information see the section, Proxy Settings in SAP ERP.● Ensure that you define authorizations for running Ariba Network transactions. For more information, see

the section, Defining Authorizations for Running Ariba Network Transactions.● To extract the commodity code maintained in the characteristic value of a class that belongs to a specific

class type in the Classification view of the Material Master record, buyers must implement the SAP Note 65124 . This is required to write the change documents for the classification data for a material master record.

● Ensure that the file size of the catalog CIF file does not exceed the maximum file size supported by Ariba Network. SAP ERP does not validate or restrict the file size of the catalog file based on the file size required by Ariba Network.




Limitations

The /ARBA/BUYER_CATALOG_EXPORT program does not support the following:

● Extracting images for catalog line items.● Extracting catalog items using the Direct Connectivity method is not available in this release.● The /ARBA/BUYER_CATALOG_EXPORT program extracts the Valuated Unrestricted-Use Stock at the plant-

level by totaling up the quantity available at the storage location of the plant. The /ARBA/BUYER_CATALOG_EXPORT program does not track the change made to the quantity.

● When you create a purchase information record at a purchasing organization level for a material, and the material is also associated to a plant, you must ensure that you send the information to Ariba Network before you again extend the same purchase information record of the associated purchasing organization to the plant. If the information has been previously staged on SAP ERP, and the same purchase information record is again extended to the plant, the newly extended information is not sent to Ariba Network.For example, you have created a purchase information record at the purchasing organization level (3000) for Material ABC having a Unit Price of $20 and lead time as 2, and the ABC material is also associated to the plant 3000. This information is stored in the table \ARBA\CHANGE_DOCS on the SAP ERP system, but not yet sent to Ariba Network.Now, when you make a change and extend the same purchase information record having the purchasing organization level (3000) to the plant 3000, the /ARBA/BUYER_CATALOG_EXPORT program only sends Unit Price of $20 and lead time as 2 that was previously staged in the \ARBA\CHANGE_DOCS table on the SAP ERP system. The newly extended plant information is not staged in the \ARBA\CHANGE_DOCS table.

5.11.3 Workflow

The following describes the workflow for creating a CIF catalog file using the /ARBA/BUYER_CATALOG_EXPORT program from your SAP ERP system:

● The buyer administrator runs the /ARBA/BUYER_CATALOG_EXPORT program on the SAP ERP system.● The /ARBA/BUYER_CATALOG_EXPORT program imports the catalog data from the Purchase Information

records and Materials Master records to create a catalog CIF file.● The /ARBA/BUYER_CATALOG_EXPORT program creates the catalog CIF file and sends it to Ariba Network.

If you have specify the Test Run option and provide a file path, the catalog CIF file is stored on the SAP application server. If you do not specify the Test Run option and want to use the Mediated Connectivity option, the catalog file is sent directly to Ariba Network.

● When the Ariba Network Full Subscription Synchronization task runs, the catalog is uploaded into the SAP Ariba Buying solutions for buyers.

5.11.4 Using the Catalog export program

Buyers can create variants to run the Schedule Job for Catalog Upload Request multiple times for the full and incremental load. The variants can have different catalog filters and options that are required while running the Schedule Job for Catalog Upload Request. For more information about Schedule Job for Catalog Upload Request or to manually import catalog master data, see SAP Ariba Cloud Integration Gateway configuration guide.


5.11.5 About processing Purchase Information Records and Material Master Records

The ARBCIG_BUYER_CATALOG_EXPORT program processes the purchase information records and the material master records while extracting the data to create catalog items in the CIF file. While extracting data for an incremental load, the ARBCIG_BUYER_CATALOG_EXPORT program records all changes done to existing data for material master and purchase info records. When these records are flagged for deletion on the SAP ERP system, these changes are recorded in the catalog CIF file. The column Delete in the CIF file contains the value T (True) to indicate that there has been a change to the catalog item on the SAP ERP system.

The following describes how the ARBCIG_BUYER_CATALOG_EXPORT program processes the purchase information records and the material master records while extracting the data to create catalog item:

● Applicable to Full and Incremental Load○ The ARBCIG_BUYER_CATALOG_EXPORT program extracts catalog items only if the material has a valid

purchase information record and the material has an associated plant. If you have a material only associated to a plant, and you create a purchase information record only at the header-level, the ARBCIG_BUYER_CATALOG_EXPORT program does not consider this purchase information record for the catalog file.

○ The Valid From date for the master record is taken from the Purchasing View on the SAP ERP system. The ARBCIG_BUYER_CATALOG_EXPORT program considers this date only when the plant-specific material has the following statuses:○ 01 (Blocked for procurement/where house) OR○ BP (Blocked for purchasing) OR○ OB (Obsolete materials)

When the ARBCIG_BUYER_CATALOG_EXPORT program runs, the program checks the status for the plant-specific material and then the value in the Valid From date. If the Valid From date is within the date specified in this field, the ARBCIG_BUYER_CATALOG_EXPORT program extracts the information for the master record. If the Valid From date is an earlier date on which the program runs, the program does not extract the master record. The program pulls the material master record only till the date specified in Valid From field. For example, if the date in the Valid From field is 10 October, 2017, the program considers the material valid up to 10 October, 2017.

○ The catalog export program considers the material master record invalid when the From date field has a blank value or stores a date that is earlier than the date on which the record was previously extracted. And the Purchasing View tab for the material has the following plant-specific material status:○ 01 (Blocked for procurement/where house) OR○ BP (Blocked for purchasing) OR○ OB (obsolete materials)

NoteWhen a Full load is run, the ARBCIG_BUYER_CATALOG_EXPORT program does not include the catalog item in the CIF file if the From date is invalid and the Purchasing View tab for the material has a plant-specific material status as 01, BP, or OB.

○ If there is a purchase information record only at the purchase organization level, the ARBCIG_BUYER_CATALOG_EXPORT program extracts the purchase information record for all the plants associated to the material in the CIF catalog.



○ If the purchase information record information for a material is available at only the plant and purchasing organization level, the catalog data extracted contains the purchase information record information only for the plant that is associated to the material.

○ The ARBCIG_BUYER_CATALOG_EXPORT program does not extract the catalog item if the purchase information record is having only a material group-level.

○ The ARBCIG_BUYER_CATALOG_EXPORT program does not extract catalog items for a full load if the vendor material number (Supplier Part ID) maintained for a purchase information record is unavailable.

○ When you associate a purchase information record to a purchasing organization and make changes the existing vendor material number (Supplier Part ID), the ARBCIG_BUYER_CATALOG_EXPORT program considers only the newly entered value for the vendor material number and discards the earlier value you changed.

○ When you create a purchase information record for a material, but do not specify a vendor material number, the ARBCIG_BUYER_CATALOG_EXPORT program does not consider the purchase information record as a catalog item while running the incremental load.

○ If you mark a purchase information record or material master record for deletion on the SAP ERP system and run the incremental load, the catalog item for the purchase information record or material master record is marked for deletion on SAP Ariba Procurement solutions system. However, if you make changes to the same deleted catalog item on the SAP ERP system and run the incremental load, the deleted catalog item is again sent to SAP Ariba Procurement solutions. But this fails on SAP Ariba Procurement solutions as the catalog item has already been deleted.

○ Purchase information records and Materials master records that have records marked for block or delete. While running an incremental load, any purchase information records and materials master records marked for block or delete is processed as changes and the corresponding item in the CIF file is marked as T in the Delete column.

○ The ARBCIG_BUYER_CATALOG_EXPORT program extracts purchase information records and material master records that have vendors marked for block or delete. The ARBCIG_BUYER_CATALOG_EXPORT program does not filter the vendor marked for block or delete.

○ If you delete the language for the material description, the ARBCIG_BUYER_CATALOG_EXPORT program marks the description for the material item for deletion and sends the value “Deleted Language Record” in the Item Description field in the CIF file. This Delete column for the catalog item contains “T” in the CIF file. As a result, this item is deleted from Ariba Network and SAP Ariba Procurement solutions. The Item Description field is a mandatory field and if this is marked for delete, Ariba Network automatically deletes the catalog item.

○ The ARBCIG_BUYER_CATALOG_EXPORT program processes the following values that are stored in the Supplier Part Auxiliary ID field:○ Language for the material master description○ Material Plant○ Purchase organization○ Purchase Info category

The ARBCIG_BUYER_CATALOG_EXPORT program uses these values to uniquely identify the material master record when the material master record is assigned to more than one plant, purchase info category, or purchase organization and available in multiple languages. The ARBCIG_BUYER_CATALOG_EXPORT program creates a unique catalog item for each material master record associated to a plant, purchase organization, purchase info category, or a specific language.

● Applicable to Incremental Load○ The Flag for deletion option on the SAP ERP system is supported for the following levels:


○ Material or Plant level for material master records○ Complete Info Record or purchasing organization level for purchase information records

○ When a buyer changes the Vendor Material number (Supplier Part Id) of a valid purchase information record for a material, the ARBCIG_BUYER_CATALOG_EXPORT program considers the previously entered value of the vendor material number (Supplier Part ID) in the catalog CIF file. This catalog item with the previously entered value is marked as “T” in the Delete column of the CIF file. The ARBCIG_BUYER_CATALOG_EXPORT program adds a new entry for the vendor material number (Supplier Part id) of a valid purchase information record for a material master.

○ Purchase information records that contains any changes to the vendor material number (Supplier Part ID) are still considered records with changes. The first change that you make to the vendor material number is always recorded as marked for deletion and the ARBCIG_BUYER_CATALOG_EXPORT program does not consider any further changes.

○ While running the incremental load, the ARBCIG_BUYER_CATALOG_EXPORT program considers the changed and deleted catalog items to already exist in the SAP Ariba Procurement solutions system. The ARBCIG_BUYER_CATALOG_EXPORT program adds a new entry for the newly changed catalog item.

○ The ARBCIG_BUYER_CATALOG_EXPORT program marks the catalog item as “T” in the Delete column of the CIF file if the From date date is blank and the Purchasing View tab for the material has a plant-specific material status as 01, BP, or OB.

○ When you make changes to a specific field for a material record, and then make changes to the vendor material number for the same material record, the ARBCIG_BUYER_CATALOG_EXPORT program does not consider the changes to the vendor material number are not flagged for deletion when you run the incremental load.For example,○ You make a change to a description field for a material record. This change is staged in the change

table on SAP ERP system. This information is also not yet sent to Ariba Network.○ For the same material record, you make a change to the vendor material number.○ You run the incremental load.

Now, the ARBCIG_BUYER_CATALOG_EXPORT program processes the change as follows:If the catalog item for the material record is already available on Ariba Network, the newly changed vendor material number is added as a new catalog item in the CIF file. This Delete column for this catalog item does not store the "T" value.

NoteWhen you need to make changes to the vendor material number, ensure that you always run the incremental load first and then make the change to the vendor material number.

○ When you extend a material master to a new Plant, ensure that you do not delete the language for the material description. If the language is deleted before you save the material master, the ARBCIG_BUYER_CATALOG_EXPORT program marks the language for the newly created Plant for deletion. When the record is sent as a catalog item to Ariba Network, this catalog item for the material record fails.



5.11.6 Uploading catalog changes using mediated connectivity

Buyer can choose to upload the CIF file using the mediated connectivity. When you do not specify the Test Run option in the /ARBA/BUYER_CATALOG_EXPORT program, this program uploads the CIF file using the mediated connectivity. The CIF file is embedded as an attachment in the cXML and sent to Ariba Network.

Buyers must specify the Ariba Network ID and email address of the buyer while specifying the conditions for uploading the CIF file using the mediated connectivity.

The file path for mediated connectivity must be maintained in the parameter /ARBA/TEMP_DIRECTORY in the /ARBA/PARAM_TAB table. For more information, see How to maintain the /ARBA/TEMP_DIRECTORY parameter [page 189]. If the file path is invalid, Ariba Network displays an error.

5.11.7 Uploading catalog changes using the incremental load

New values or changes done in the purchase information record or the material master records can be uploaded on Ariba Network and SAP Ariba Procurement solutions. Buyers must run the incremental load to upload the new values to an existing catalog .CIF file. Buyers can specify a date period while running the incremental load to download data that has been changed or newly during the date period.

NoteYou must ensure that you use the existing catalog subscription name for each incremental load you run for an existing catalog.

5.11.8 Maintaining catalog fields

To maintain the SAP Ariba field names in the SAP ERP system, SAP Ariba Account Administrator must first create these custom fields with the required SAP Ariba field name on their SAP Ariba Procurement solutions. These new custom SAP Ariba fields can be mapped to the SAP fields in the ARBCIG_FIELDMAP table using the Maintain Field Map for Master Data and Catalog Upload Request activity on SPRO.

● If you add catalog fields to the customized RFC structure, add the field, its structure, and the corresponding SAP Ariba field name using the Maintain Field Map for Master Data and Catalog Upload Request activity to have a preferred column name in the CIF files.

● The CIF file created on the ERP system contains additional fields. You must maintain the SAP Ariba field names for the following fields using the Maintain Field Map for Master Data and Catalog Upload Request activity :

Field Name Description

MATNR SAP ERP Material Number

WERKS Plant


Field Name Description

EKORG Purchase Organization

ESOKZ Purchase Info Category. For example, Standard, Subcontracting, Pipeline and Consignment.

LABST Valuated Unrestricted-Use Stock

INFNR Purchase Information Record

5.11.9 Configuring catalog data integration

To support creating a catalog CIF file for the Purchase Information records and Materials Master records, you must download the latest transport files, configure your SAP Process Integration, and SAP ERP systems.

How to create the catalog CIF file [page 188]

Handling errors [page 189]

Configuring SAP Process Integration for catalog data integration [page 189]

Configuring SAP ERP for catalog data integration [page 189]

5.11.9.1 How to create the catalog CIF file

Context

Run the /ARBA/BUYER_CATALOG_EXPORT program that allows you to extract the the Purchase Information records and Materials Master records and create a catalog CIF file.

Procedure

1. Go to the T-code /nse38.

2. Enter /ARBA/BUYER_CATALOG_EXPORT in the Program field.

3. Click Execute.4. Specify the values for the catalog CIF file. For more information on the fields, see section that describes the

fields in the /ARBA/BUYER_CATALOG_EXPORT program.

5. Click Execute.



5.11.9.2 Handling errors

Buyers can use the transaction, SXMB_MONI to view the following errors:

● System errors that occurred while uploading the catalog data from SAP ERP to SAP Process Integration● Errors while sending the catalog CIF file through the mediated connectivity

5.11.9.3 Configuring SAP Process Integration for catalog data integration

Buyers must configure the integration directory to integrate catalog data from SAP ERP to Ariba Network.

Configuring the Integration Scenario involves the following steps:

1. Assigning the model.2. Assigning the components.3. Configuring the sender and receiver relations for individual connections.4. Generating the configuration objects.

For more information on the catalog data integration, see Topics about configuring outbound transactions [page 90].

5.11.9.4 Configuring SAP ERP for catalog data integration

Configure SAP ERP for catalog data integration.

How to maintain the /ARBA/TEMP_DIRECTORY parameter [page 189]

How to add additional catalog fields [page 190]

How to specify parameters for downloading commodity code [page 191]

How to customize the class type in IMG [page 192]

Using customization [page 192]

5.11.9.4.1 How to maintain the /ARBA/TEMP_DIRECTORY parameter

Context

Maintain the parameter /ARBA/TEMP_DIRECTORY in the table /ARBA/PARAM_TAB if you are using the mediated connectivity to upload the catalog .CIF file. The /ARBA/BUYER_CATALOG_EXPORT program uses the file path you maintain in this parameter.


Procedure

1. Go to /ARBA/PARAM_TAB table.

2. Maintain the following values:

○ Variable Name: /ARBA/TEMP_DIRECTORY○ Field Name Number: 0○ INCL/EXCL: I○ Option: EQ○ Selection value: File path to store the catalog .CIF file.

NoteA folder Catalog is automatically created to store the catalog file. The /ARBA/BUYER_CATALOG_EXPORT program validates the file path that you specify. If the file path is invalid, the /ARBA/BUYER_CATALOG_EXPORT program displays an error.

5.11.9.4.2 How to add additional catalog fields

Context

To maintain the SAP Ariba field names in the /ARBA/FL_MAP, buyers must first create these additional fields with the required SAP Ariba field name on their SAP Ariba Buying solutions system. These additional SAP Ariba fields can be mapped to the SAP ERP fields in the /ARBA/FL_MAP table. This is an optional task.

Procedure

1. Start transaction SM30.

2. Choose table view /ARBA/FL_MAP.

3. Click Maintain. The Change View "Table to maintain mapping of SAP to Arib fields": Overview page appears.

4. Select each of the following additional fields in the Field SAP column. Enter the corresponding SAP Ariba field name in the Field Ariba column:

○ MATNR○ WERKS○ EKORG○ ESOKZ○ LABST○ INFNR




5.11.9.4.3 How to specify parameters for downloading commodity code

Context

If you use the commodity code maintained in Classification view for the full or incremental load, you must maintain the /ARBA/BUYER_CAT_CLASS_TYPE, /ARBA/BUYER_CAT_CLASS and /ARBA/BUYER_CAT_INT_CHAR_NO. parameters in the /ARBA/PARAM_TAB. The /ARBA/BUYER_CATALOG_EXPORT program displays an error if you do not maintain these parameters when specifying the Classification Code as Commodity Code option.

Procedure

1. Go to /ARBA/PARAM_TAB.

2. Maintain the following Class type in the classification view of material master:○ Variable Name: /ARBA/BUYER_CAT_CLASS_TYPE○ Field Name Number: 0○ INCL/EXCL: I○ Option: EQ○ Selection value: For example, 001.

3. Maintain the following Class in the classification view of material master:○ Variable Name: /ARBA/BUYER_CAT_CLASS○ Field Name Number: 0○ INCL/EXCL: I○ Option: EQ○ Selection value: For example, CL125.

4. Maintain the following Characteristics Name maintained in CL01 transaction:for the characteristic value that must be extracted as the commodity code maintained in the Classification view for a particular class type and class. Ensure that you must user or create a characteristic value of the CHAR data type.○ Variable Name: /ARBA/BUYER_CAT_INT_CHAR_NO○ Field Name Number: 0○ INCL/EXCL: I○ Option: EQ○ Selection value: For example, CH0023.


5.11.9.4.4 How to customize the class type in IMG

Context

To extract the commodity code maintained in the characteristic value of a class that belongs to a specific class type in the Classification view of the Material Master record, buyers must implement the SAP Note 65124 . This is required to write the change documents for the classification data for a material master record. Buyers must also run the program RCCLUKA2 and set the Multiple Objects Type Allowed indicator.

Procedure

1. Go to Tcode SPRO and then click SAP reference IMG.

2. Click Cross Application Components.3. Click Classification System and then click Classes.4. Click Maintain Object types and Class types.5. Click the Object Table folder in the Data Structure tree view.6. Choose the MARA option in the table and double click the Class Types folder.7. Choose Class Type 001 and click the Details button.8. Ensure that Change Docs checkbox is checked in the Classification section.9. Double-click the Objects folder. Ensure that the Chg. docs for Class is chosen in the Classification

section..

5.11.9.4.5 Using customization

Customers can use each of these BAdIs to customize the /ARBA/BUYER_CATALOG_EXPORT program.

The interface /ARBA/IF_EXP_BUYER_CATALOG contains the following methods:

● MODIFY_PIR: Use this BAdI to make any changes you require to the Purchase Info records before publishing to Ariba Network.

● MODIFY_MATERIAL: Use this BAdI to make any changes you require to the Material Information before publishing to Ariba Network.

● PUBLISH_CIF: Use this BAdI to make any changes you require to the values for the catalog items before publishing to Ariba Network.

5.12 Integration to support early payments through Supply Chain Financing

Buyers using the Ariba Network adapter for SAP NetWeaver can now use a Supply Chain Financing provider to make their payments against invoices to suppliers. This allows buyers to leverage the advantages of using a




Supply Chain Financing provider and increase the number of days available to make payments to suppliers. In turn, suppliers also receive their payments earlier from the funders through the Supply Chain Financing provider.

Buyers can send payment proposals for approved invoices and credit memos to Ariba Network from their SAP ERP system. Ariba Network sends the payment proposals that are marked for Supply Chain Financing to the provider. Ariba Network and the Supply Chain Financing provider can send updates on the payment proposal back to the ERP system. This helps ERP buyers manage the account payables with the information on the funder(financing company) and the early payments made to suppliers on the SAP ERP system.

Buyers can configure their SAP ERP system to enable payments through the Supply Chain Financing provider and SAP Ariba Discounting. However, if the payment proposal request or credit memo is not marked for Supply Chain Financing, the payment for the invoice is processed through the SAP Ariba Discounting from Ariba Network.

Prerequisites and limitations [page 193]

Workflow for early payment through Supply Chain Financing [page 195]

Configuring early payments for Supply Chain Financing [page 196]

5.12.1 Prerequisites and limitations

Prerequisites

To send payment proposals for approved invoices and credit memos enabled for Supply Chain Financing, buyers must do the following on their SAP ERP system:

● Create a vendor for the funder on the Supply Chain Financing provider with the Company Code. Ensure that the account payable, general ledger account, and house bank configuration are available for the vendor.

● Create the /ARBA/FUNDER table and add the VendorID for the funder. Maintain the relationship for the funder using the unique identification reference for the funder (FinancialInstitutionID) on the Supply Chain Financing provider. Contact SAP Ariba Customer Support for information about the funder's ID.

● Maintain the payment method for a vendor for Supply Chain Financing. Ensure that you maintain the payment method with any value other than "E." Ariba Network adapter for SAP NetWeaver does not support the payment method "E" to send payment proposals to Ariba Network. You need to also ensure that you specify "Aribascf" as the description for the payment method. You need to use the new payment method while creating invoices for a vendor on the SAP ERP system.

● Maintain the new payment method by the country for Supply Chain Financing.● Assign the company code to the newly created payment method. You need to also ensure that you

maintain the sending and paying company codes for the company code.● Maintain the doc type for invoices created when the liability to pay the invoice has been transferred from

the supplier to the funder on the SAP ERP system. Maintain the doc type in the /ARBA/PARAM_TAB table. Ensure that you maintain different document types for ERP-initiated invoices and CC invoices.

● Maintain the doc type for credit memos sent in the payment proposals to Ariba Network.● Maintain the posting keys to transfer the liability from the supplier to the funder and for the remittance

advices.


● Ensure that you have the necessary authorizations for running the Ariba Network transactions. For more information on authorization, see the section, Defining Authorizations for Running Ariba Network Transactions.

● Maintain the start date and time proxy parameters for the payment proposals and Invoice Status Update (ISU) document types in the /ARBA/PROXYPARAM table. Use the TCode SE38 and run the /ARBA/BTE_INVSTATUPDT_EXPORT program.

● Maintain one general ledger account for the Supply Chain Financing payment method. This must be a unique combination of the company code and currency. Each general ledger account for a company code needs to be specific to the currency and Supply Chain Financing payment method.

● If your SAP ERP system contains the installation for both Ariba Network adapter for SAP NetWeaver and SAP Ariba Buying solutions for SAP and you run both the Invoice Status Update and Advance Payment Remittance transactions, you need to run the Business Transaction Event using the Tcode FIBF and maintain the following:○ Maintain the function module /ARBA/BTE_00005010 for the Process code 00005010.○ Ensure that the product you maintain for the Invoice Status Update transaction is checked on the

Customer Product page.

● NoteEnsure that the invoices that you create on the SAP ERP system for Supply Chain Financing do have the new payment method that you have created. If the payment proposal or credit memo is not marked for Supply Chain Financing, the payment for the invoice is processed through the SAP Ariba Discounting from Ariba Network.

Limitation

● Ariba Network adapter for SAP NetWeaver does not support processing of discounts on payment terms in the invoices sent to the Supply Chain Financing provider.

● Ensure that you do not run the F110 Automatic payment transaction or F-53 manual payment for invoices containing the payment method for Supply Chain Financing.

● The invoices should not contain cross-company code numbers. Ariba Network adapter for SAP NetWeaver does not support processing of invoices containing cross-company codes. A cross-company code transaction occurs when an invoice is associated to one company code but the payment for this invoice is made by another company code.



5.12.2 Workflow for early payment through Supply Chain Financing

The following describes the workflow for sending and receiving payment proposals and credit memos enabled for Supply Chain Financing from your SAP ERP system:

1. The buyer configures the SAP ERP system with the necessary parameters for Supply Chain Financing.2. The buyer creates invoices (ERP-initiated or ERPCC invoices) that have been enabled for Supply Chain

Financing.3. Supplier receives the ERPCC invoices on Ariba Network. When a supplier creates an invoice or credit

memo, Ariba Network sends the invoices or credit memos to the SAP ERP system.4. The buyer approves the invoices on the SAP ERP system and sends a payment proposal

(PaymentRequest) to Ariba Network. If credits are applicable, the PaymentRequest contains the credit memos.

5. Ariba Network receives the PaymentRequest and credit memos against invoices. If the PaymentRequest is marked for Supply Chain Financing, Ariba Network sends them to the Supply Chain Financing provider.

6. The Supply Chain Financing provider receives the PaymentRequest for the invoices and credit memos marked for Supply Chain Financing.

7. If the payment date in the PaymentRequest is marked on a holiday or weekend, the Supply Chain Financing provider sends an updated payment date based on the Supply Chain Financing provider calendar days. The updated payment date is available in the PaymentRequest.

8. Ariba Network receives the updated PaymentRequest with the new payment date from the Supply Chain Financing provider.

9. The buyer receives the updated PaymentRequest with the new payment date from Ariba Network. The SAP ERP now stores this updated payment date information in the invoices.


10. If the supplier elects to trade the invoice and the funder accepts the offer, the Supply Chain Financing provider sends an approved trade request to the supplier on Ariba Network.

11. The supplier receives the approved request to trade against the invoice for an early payment from the funder.

12. The supplier accepts the request from the funder to receive an early payment against the traded invoice.13. The Supply Chain Financing provider initiates the payment against the traded invoices sent to the supplier.14. Ariba Network adapter for SAP NetWeaver processes an update to the payment request sent by Ariba

Network as the result of the approved trade request. Ariba Network adapter for SAP NetWeaver transfers the payment liability from the supplier to the funder. SAP ERP system stores this information on the transferred liability from the supplier to the funder.

15. On the payment due date, the Supply Chain Financing provider initiate a payment instruction from the buyer to the funder for the traded invoice. If credits are applicable, the credit amount is applied on the payment. The provider sends a remittance advice (PaymentRemittanceRequest) with the payment details to Ariba Network.

16. Ariba Network sends the buyer the remittance advice details on the amount that the funder paid the supplier. The SAP ERP system updates the General Ledger with the payment information.

17. When the invoice is untraded, the Supply Chain Financing provider initiates a payment few days prior to the payment due date. The Supply Chain Financing provider initiates the payment from the buyer’s bank to the supplier’s bank. The provider sends a remittance advice with the payment details for the untraded invoice to Ariba Network.

18. Ariba Network sends the buyer the remittance advice details (PaymentRemittanceRequest) on the amount that the buyer paid the supplier. The SAP ERP system updates the General Ledger with the payment information for the non-traded invoices.

5.12.3 Configuring early payments for Supply Chain Financing

You need to configure your SAP ERP system to send early payments through Supply Chain Financing.

Ariba Network adapter for SAP NetWeaver uses the BAPI_ACC_DOCUMENT_POST function module to create invoices when the liability has been transferred from the supplier to the funder on the SAP ERP system. Additionally, the BTE passes the posting keys to these newly created invoice contained the transferred liability. This BTE is also applicable for the remittance advices received from Ariba Network.

Ariba Network adapter for SAP NetWeaver sends default values that are mandatory when running the BAPI_ACC_DOCUMENT_POST function module to create invoices and send remittances to Ariba Network. If you have any additional FI configuration or customizations that are mandatory fields on your SAP ERP, you must ensure that you use the BAdI SAP Ariba provides you to prevent the BAPI from returning errors.

Ariba Network adapter for SAP NetWeaver maintains the Business Transaction Event (BTE) RWBAPI01 with the following values:

● Process: RWBAPI0● Function Module: /ARBA/BTE_INVOICE_MODIFY● Product: /ARBA/LI

You can use the following BAdIs for customization:



● /ARBA/LIABILITY_INVOICE: To customize changes to be made while transferring the the payment liability to the funder (financing company).

● /ARBA/REMITTANCE_ADVICE: To customize the remittance advice that you receive from the Supply Chain Financing provider throughAriba Network.

The following message mappings are available to support payment proposals and credit memos for Supply Chain Financing:

● Payment Proposal: MM_PaymentProposal_Item2_cXML● PayMeNow: MM_CDF_FulFill_XSD_PayMeNow_2_FIDCCH_FIDCCH01 contains changes to process the

payment date changes.

For customizations, you can use the following message mapping files for Supply Chain Financing:

● Payment Proposal: MM_Custom_PaymentProposal_Item_2_cXML● PayMeNow: MM_Custom_CDF_FulFill_XSD_PayMeNow_2_FIDCCH_FIDCCH01

Configuring your SAP Process Integration to support early payments through Supply Chain Financing [page 197]

Topics about configuring the SAP ERP system for Supply Chain Financing [page 198]

5.12.3.1 Configuring your SAP Process Integration to support early payments through Supply Chain Financing

To send payment proposals for approved invoices and credit memos to a Supply Chain Financing provider, you must download the latest transport files, configure your SAP Process Integration, and SAP ERP systems.

5.12.3.1.1 How to configure the integration scenarios to integrate early payments through Supply Chain Financing

Context

To integrate early payments through Supply Chain Financing from an SAP ERP system to Ariba Network, configure the required inbound and outbound integration scenarios:

Procedure

1. Configure the following integration scenarios to integrate early payments through Supply Chain Financing from an SAP ERP system to Ariba Network:

○ Outbound Transaction


○ Payment Proposal○ Inbound Transactions

○ Pay Me Now○ Liability Transfer○ Remittance Advice

2. Perform the following steps while configuring the integration scenario:1. Transfering the integration scenario.2. Assigning the model.3. Assigning the components.4. Configuring the sender and receiver relations for individual connections.5. Generating the configuration objects.6. Configuring the Communication Channels.7. Activating the integration scenario.

For more information on the integration scenarios, see Topics about configuring outbound transactions [page 90] and Topics about configuring inbound transactions [page 101].

5.12.3.2 Topics about configuring the SAP ERP system for Supply Chain Financing

How to create a vendor for the funder on Supply Chain Financing [page 198]

How to maintain the vendor and funder information [page 199]

How to create payment methods by country [page 200]

How to create check payment method by country for SAP Ariba Payables [page 200]

How to maintain the company code for the vendor as funder [page 201]

How to assign the company code to the payment method [page 201]

How to maintain the document type for early payments through Supply Chain Financing [page 202]

How to maintain the business transaction event for invoice status update and remittance transactions [page 204]

How to maintain the general ledger account configuration for a company code with the Supply Chain Financing payment method [page 205]

5.12.3.2.1 How to create a vendor for the funder on Supply Chain Financing

Context

To integrate early payments through Supply Chain Financing from an SAP ERP system to Ariba Network, you need to create a vendor for the funder (financing company) on the SAP ERP.



Procedure

1. Go to Transaction code /nXK02.

2. Enter the value for the vendor in the Vendor field.3. Enter the following values for the vendor:

○ Company Code: Enter the company code for the vendor.○ PurchasingOrganization: Enter the purchase organization.○ Account group: Enter the account group for the vendor.

4. Specify the General data, Company code data, Purchase organization data other necessary details for the vendor.

NoteWhen specifying the payment terms for the vendor on the Payment transaction Accounting page, ensure that the value in the Payt Terms field match the same value specified on the Terms of Payment details page.

5.12.3.2.2 How to maintain the vendor and funder information

Context

To integrate early payments through Supply Chain Financing, maintain the funder (financing company) as a vendor on the SAP ERP system.You need to obtain the funder ID for the funder on the Supply Chain Financing provider. Contact SAP Ariba Customer Support for information about the funder's ID.

Procedure

1. Go to Transaction code SM30.

2. Go to the /ARBA/FUNDER table. Click Maintain.

3. Click New Entries.4. Enter the funder ID for the vendor in the SCF Funder field. Use the unique identification reference for the

funder on the Supply Chain Financing provider.5. Enter the vendor key associated to the funder in the Vendor ID field.6. Save the entries.


5.12.3.2.3 How to create payment methods by country

Context

Maintain payment methods specific for Supply Chain Financing for different countries.

Procedure

1. Go to transaction code FBZP.

2. Click Pmnt methods in country.3. Click New Entries.4. Choose the country in the Country field.5. Enter the payment method in the Pymt Method field for Supply Chain Financing. Ensure that you maintain

the payment method with any value other than "E." Ariba Network adapter for SAP NetWeaver does not support the payment method "E" to send payment proposals to Ariba Network. Use this payment method for the vendor while creating invoices on the SAP ERP system.

6. Enter "Aribascf" as the description for the payment method in the Description field. The "Aribascf" description is required to avoid the payment proposal from failing on Ariba Network.

7. Check Payment order only in the Posting details section.8. Save the changes.

5.12.3.2.4 How to create check payment method by country for SAP Ariba Payables

Context

Maintain check payment method specific for SAP Ariba Payables by countries.

Procedure

1. Run the transaction code FBZP.

2. Click Pmnt methods in country.3. Click New Entries.4. Choose the country in the Country field.5. Choose Check in the Pymt Method field to specify the required payment method for SAP Ariba Payables.6. Enter a description in the Description field.

Maintain identical payment method description between Ariba Network and SAP ERP or SAP S/4HANA.



7. Choose Check under Payment method classification.8. Save the changes.

For information about configurations required in Ariba Network, see the section Mapping a payment method in the Buyer administration guide in the Product Documentation Administration and Configuration section of the Learning Center.

5.12.3.2.5 How to maintain the company code for the vendor as funder

Context

Maintain the company code for the funder(financing company). You need to create a vendor for the funder(financing company) before you maintain the company code for the vendor (funder).

Procedure


2. Go to the /ARBA/AN_VENDOR table. Click Maintain.

3. Click New Entries.4. Enter the company code for the vendor in the Company Code field.5. Enter the vendor key associated to the funder.6. Save the entries.

5.12.3.2.6 How to assign the company code to the payment method

Context

After you create a payment method for a country, you need to assign a company code for the payment method.

Procedure


2. Click Pmnt methods in company code.


3. Click New Entries.4. Enter the company code in the Paying co. code field.5. Enter the payment method in the Pymt Method field.6. In Amount limit section, enter a value in the Minimum amount, Maximum amount, and Distribution

amnt fields.7. In the Foreign payments/foreign currency payments, check the following options:

○ Foreign business partner allowed○ Foreign currency allowed○ Cust/vendor bank abroad allowed

8. Ensure that you choose the No optimization option in the Bank selection control.9. Save the changes.

5.12.3.2.7 How to maintain the document type for early payments through Supply Chain Financing

Context

Maintain the following document types for invoices that need to be being sent to the Supply Chain Financing provider. You need to define different document types for the ERP-initiated invoices and CC invoices that you send from your SAP ERP.

Procedure


2. Go to the /ARBA/PARAM_TAB table. Click Maintain.

3. Click New Entries.4. Create the following parameters for the different doc types containing these values:

To send and receive credit memos:○ ○ Variable Name: INVOICE_DOC_TYPE

○ Field Name: KG○ Number:0 (zero)○ INCL/EXCL: I○ Option: EQ○ Selection value: KG○ Selection value: Leave it empty.

NoteThe parameter for credit memos support sending and receiving all credit memos, irrespective of the payment method from the SAP ERP system to Ariba Network



To transfer the liability from the supplier to the funder on the Supply Chain Financing provider:○ ○ Variable Name: LIABILITY_INV_DOC_TYPE

○ Field Name: AB○ Number:0 (zero)○ INCL/EXCL: I○ Option: EQ○ Selection value: AB○ Selection value: Leave it empty.

○ ○ Variable Name: LIABILITY_POST_KEY○ Field Name: 27○ Number:0 (zero)○ INCL/EXCL: I○ Option: EQ○ Selection value: 27○ Selection value: Leave it empty.

○ ○ Variable Name: LIABILITY_POST_KEY_CREDIT○ Field Name: 32○ Number:0 (zero)○ Option: EQ○ Selection value: 32○ Selection value: Leave it empty.○ INCL/EXCL: I

NoteAriba Network adapter for SAP NetWeaver uses the BAPI_ACC_DOCUMENT_POST function module to create invoices when the liability has been transferred from the supplier to the funder on the SAP ERP system. Additionally, the BTE passes the posting keys to these newly created invoice contained the transferred liability. This BTE is also applicable for the remittance advices received from Ariba Network.

Ariba Network adapter for SAP NetWeaver maintains the Business Transaction Event (BTE) RWBAPI01 with the following values:○ Process: RWBAPI0○ Function Module: /ARBA/BTE_INVOICE_MODIFY○ Product: /ARBA/LI

To receive the remittance advice from the Supply Chain Financing provider and Ariba Network:○ ○ Variable Name: REMITTANCE_INV_DOC_TYPE

○ Field Name: AB○ Number:0 (zero)○ INCL/EXCL: I○ Option: EQ○ Selection value: AB○ Selection value: Leave it empty.

○ ○ Variable Name: REMITTANCE_POST_KEY_CLEAR○ Field Name: 25○ Number:0 (zero)


○ INCL/EXCL: I○ Option: EQ○ Selection value: 25○ Selection value: Leave it empty.

○ ○ Variable Name: REMITTANCE_POST_KEY_CREDIT○ Field Name: 38○ Number:0 (zero)○ INCL/EXCL: I○ Option: EQ○ Selection value: 38○ Selection value: Leave it empty.

○ ○ Variable Name: REMITTANCE_SCF_PAYMENT_METHOD○ Field Name: Value stored for the payment method specific for Supply Chain Financing○ Number:0 (zero)○ INCL/EXCL: I○ Option: EQ○ Selection value: 38○ Selection value: Value stored for the payment method specific for Supply Chain Financing


5.12.3.2.8 How to maintain the business transaction event for invoice status update and remittance transactions

Context

You need to run the Business Transaction Event using the TCode FIBF if your SAP ERP system contains the installation for both Ariba Network adapter for SAP NetWeaver and SAP Ariba Buying solutions for SAP and run the Invoice Status Update and Advance Payment Remittance transactions using each of the SAP Aribacloud installations.

Procedure

1. Run the transaction code FIBF.

2. Click Settings Process Modules of a customer .3. Click New Entries.4. Maintain the following values:

○ Process: 00005010○ Function Module: /ARBA/BTE_00005010



○ Product: Leave it blank.5. Save the changes.

6. Click Settings Products of a customer .7. Ensure that the product you maintain for the Invoice Status Update transaction is checked on the

Customer Product page. Use the transaction code FB42 to view the value.

5.12.3.2.9 How to maintain the general ledger account configuration for a company code with the Supply Chain Financing payment method

Context

You need to maintain one general ledger account for the Supply Chain Financing payment method. This must be a unique combination of the company code and currency. Each general ledger account for a company code needs to be specific to the currency and Supply Chain Financing payment method. Ariba Network adapter for SAP NetWeaver creates one remittance advice per company code.

Procedure

1. Go to TCode FBZP.

2. Click Bank determination.3. Choose the Paying company code from the list and then double-click Bank Accounts.4. Click New Entries.5. Enter the required values for the for the house bank, Supply Chain Financing payment method, currency,

and general ledger account.6. Save the entries.

5.13 Integration to support SAP Ariba Payables payments through the cXML format using SAP standard payment interface

Buyers can send multiple remittance advices for SAP Ariba Payables payments from the SAP ERP and SAP S/4HANA system to Ariba Network in a batch file through the cXML format. The Ariba Network adapter for SAP NetWeaver processes the remittance advices for SAP Ariba Payables payments using the standard SAP F110 Automatic payment transaction. The remittance advices are batched together in a single cXML file in the SAP Process Integration system before sending them to Ariba Network. On receipt of the remittance advices, Ariba Network sends the payment details to the SAP Ariba Payables provider for settlement of payment between the buyer and supplier banks.


To process remittance advice using the F110 (Automatic payment) transaction, buyers must configure their SAP ERP and SAP Process Integration to use the SAP ERP enterprise services package (ECC-SE 605 and higher).

If you are an existing customer using the payment integration toolkit to send and receive payment proposals and remittances from Ariba Network, SAP Ariba recommends that you use the Ariba Network adapter for SAP NetWeaver to send payment proposals and remittance advices.

NoteSAP Ariba recommends that you send remittance advices for a single payment method in a payment batch. You cannot send remittances with more than one payment method. For example, you cannot have a payment batch file containing both ACH and the SAP Ariba Payables payment methods.

Effective from cloud integration release 9.0 SP1, Ariba Network adapter for SAP NetWeaver supports buyers to provide:

● Supplier physical address: The supplier address to which the check is to be mailed. Checks are designed as a pass-through for SAP Ariba Payables and no onboarding is done for the suppliers whose address is not provided by the buyer.

● Supplier email address: The supplier email address for sending emails to suppliers.


Workflow to support AribaPay payments through the cXML format using SAP standard payment interface [page 208]

Configuring integration to support SAP Ariba Payables payments through the cXML format using SAP standard payment interface [page 209]

Related Information

How to create check payment method by country for SAP Ariba Payables [page 200]


To send multiple remittances in a cXML batch, buyers need the following:

Prerequisites

● You need to have the SAP ERP enterprise services package (ECC-SE 605 and higher) on your SAP ERP system.

● If you are an existing customer using the payment integration toolkit to send payment proposals and remittances to Ariba Network, and choose to use Ariba Network adapter for SAP NetWeaver, you need to make the necessary changes to support sending the remittances batch using the SAP Process Integration.



● Ensure that you download and install the corresponding TPZ file for the SAP ERP enterprise services package. The service interface CollectivePaymentOrderBulkRequest_Out is referenced from the SAP namespace: http://sap.com/xi/APPL/SE/Global.Ensure that you use the outbound service interface CollectivePaymentOrderBulkRequest_Out from the Software Component version/namespace that belongs to SAP Enterprise Service package content (ECC-SE 605 and higher) in the SAP Ariba adapter namespace PaymentRemittanceBatchRequest. Use the SPROXY transaction to ensure that all the components are available on the SAP ERP system.

● Configure the integration scenario for the PaymentRemittanceBatchRequest namespace.● Configure the payment method by country for SAP Ariba Payables payments.● Implement the BAdI BNK_CPOR.● To send supplier physical address and email address, use cXML version 1.2.033 or higher.● To send email address in the field PAYMENT, implement SAP Note 1690026 -CPOR: BAdI

COMPLETE_CASE_EXTENSION does not receive all data.

Limitations

● Ensure that the remittance batch you send Ariba Network does not exceed 10,000 lines. Ariba Network only supports remittances batch of up to 10,000 lines.

● SAP Ariba recommends that you send remittances for a single payment method in a payment batch. You cannot send remittances with more than one payment method. For example, you cannot have a payment batch containing both ACH and the SAP Ariba Payables payment methods.



5.13.2 Workflow to support AribaPay payments through the cXML format using SAP standard payment interface

The following describes the workflow for sending remittances batched together in a single cXML file from your SAP ERP system:

1. The buyer configures their SAP ERP and SAP Process Integration to use the SAP ERP enterprise services package (ECC-SE 605 or higher).

2. The buyer configures to create the payment method by country for AribaPay.3. The buyer creates invoices (ERP-initiated or ERPCC invoices) or receives invoices and credit memos that

have been enabled for AribaPay from Ariba Network. Supplier receive the ERPCC invoices on Ariba Network. When a supplier creates an invoice or credit memo, Ariba Network sends the invoices or credit memos to the SAP ERP system.

4. The buyer approves the invoices or credit memos on the SAP ERP system and sends a payment proposal (PaymentProposalRequest) to Ariba Network.

5. The supplier receives the PaymentProposalRequest and credit memos against invoices marked for AribaPay.

6. The buyer runs the standard SAP F110 Automatic payment transaction. The remittances are batched together in a single cXML file in the SAP Process Integration system and then sent to Ariba Network. On receipt of the PaymentRemittanceRequest, Ariba Network sends the payment details to the AribaPay provider for settlement of payment between the buyer and supplier banks.



Related Information


5.13.3 Configuring integration to support SAP Ariba Payables payments through the cXML format using SAP standard payment interface

To send SAP Ariba Payables in a batch through the cXML format, you are required to configure your SAP ERP or SAP S/4HANA system. The following BAdI is available to send the remittances batch in the cXML format:

● BAdI Name: BNK_CPOR● Method Name: ENH_EXPLANATION. Call this method in the BAdI method, COMPLETE_EXPLANATION to

enhance the payment description.● Method Name: ENH_CASE_EXTENSION. Call this method in the BAdI method,

COMPLETE_CASE_EXTENSION to enhance the case extension.● Method Name: IF_EX_BNK_CPOR~COMPLETE_CASE_EXTENSION. Implementation: /ARBA/

CL_ENH_PAYMENT_BATCH=>ENH_CASE_EXTENSION to support supplier physical address and email address.

● Package Name: /ARBA/PAYMENT_BATCH● Class: /ARBA/CL_ENH_PAYMENT_BATCH

To customize the remittances batch, you can use the standard enhancements and BAdI available for payments in the F110 Automatic payment transaction. Ensure that you call the respective ARBA class and method from the implemented BAdI method.

The following SAP Enterprise Service mapping objects are available for payments sent as a cXML batch:

● CollectivePaymentOrderBulkRequest_2_RemittanceBatch_cXML● Custom_CollectivePaymentOrderBulkRequest_2_RemittanceBatch_cXML

Configuring SAP Process Integration to support AribaPay payments through the cXML format [page 209]

Configuring SAP ERP system to support AribaPay payments through the cXML format [page 211]

5.13.3.1 Configuring SAP Process Integration to support AribaPay payments through the cXML format

Configure your SAP Process Integration system to support payment methods by country for SAP Ariba Payables payments through the cXML format.

How to add the software component version for SAP Enterprise Service [page 210]

How to configure the integration scenarios to integrate payments through the cXML format [page 210]


5.13.3.1.1 How to add the software component version for SAP Enterprise Service

Context

Before you configure the integration scenario to support remittances through the cXML format, you need to add the software component version for the SAP enterprise service. This is required as SAP Ariba uses the service interface from ESA ECC-SE enterprise service package. Ensure that you have imported the corresponding TPZ file from the SAP Market Place and the AribaNetworkAdapter.tpz from connect.ariba.com .

Procedure

1. Go to the Enterprise Service Builder.2. Double-click the design object for ARIBA_NETWORK_ADAPTER, CIx of ariba.com. The Display Software

Component Version page appears.3. Click the Details page tab.4. Click the Adds Underlying Software Component Version button in the section, Underlying Software

Component Version. The Add Underlying Software Component Version page appears.5. Choose the ESA ECC-SE 605 or higher object. Click Add.

6. Click Tools Update SLD Information .

5.13.3.1.2 How to configure the integration scenarios to integrate payments through the cXML format

Context

To integrate remittance advices through the cXML format from an SAP ERP system to Ariba Network, configure the required inbound and outbound integration scenarios:

Procedure

1. Configure the following integration scenarios to integrate batched remittance advice through the cXML format from an SAP ERP system to Ariba Network:

○ Outbound Transaction○ Payment Proposal




○ Payment Remittance Batch Request○ Inbound Transactions

○ Pay Me Now2. Perform the following steps while configuring the integration scenario:

1. Transferring the integration scenario.2. Assigning the model.3. Assigning the components.4. Configuring the sender and receiver relations for individual connections.5. Generating the configuration objects.6. Configuring the Communication Channels.7. Activating the integration scenario.

For more information on the integration scenarios, see Topics about configuring outbound transactions [page 90] and Topics about configuring inbound transactions [page 101].

5.13.3.2 Configuring SAP ERP system to support AribaPay payments through the cXML format

Configure your SAP ERP system to support payment methods by country for SAP Ariba Payables payments through the cXML format.

5.13.3.2.1 How to create payment methods by country/region for AribaPay

Context

Maintain payment methods specific for SAP Ariba Payables by countries.

Procedure


2. Click Pmnt methods in country.3. Click New Entries.4. Choose the country/region in the Country field.5. Select the required payment method for SAP Ariba Payables in the Pymt Method field. Ensure that the

payment method that you associate for AribaPay is not already configured as the EDI payment method in the payment configuration on the SAP ERP system.

6. Check Use payment medium workbench in the Payment medium section.


7. Enter "CPOR_BULK" in the Format field. Save the changes.8. Enter the required parameters and run the transaction code F110. This triggers the payment batch

message to Ariba Network.9. (Required only if you want to resend the information) Run the program SAPFPAYM after specifying the Run

Date and Identification. Ensure that you run the program with the same date and ID.10. Save the changes.11. Log in to your Ariba Network buyer account and map the "CPOR_BULK" payment method to the AribaPay

payment method. Ensure that you check Use Ariba Network Payment for Ariba Network to send the payment information to the SAP Ariba Payables payment provider for processing payments. For more information, see the section Mapping a Payment Method in the Buyer Administration Guide in the

Product Documentation Administration and Configuration section of the Learning Center.

5.14 About support for third-party logistics providers

Buyers using Ariba Network adapter for SAP NetWeaver can configure their ERP systems to send transportation requests to logistics providers on Ariba Network to arrange delivery for one or more consignments.

Logistics providers transport goods or materials for buyers. Buyers sends the transportation request to Ariba Network in response to the ship notice that a supplier sends them. Logistics providers registered on Ariba Network can view and respond to confirm, accept, cancel, or reject the buyer’s request.


Prerequisites

Buyers and logistics providers must upgrade to cXML 1.2.0.30 or higher in order to support the new cXML elements and attributes added to the TransportRequest and TransportConfirmationcXML documents.

Limitations

● Buyers can only send and receive the transportation requests as a cXML document to logistics providers on Ariba Network. Ariba Network displays the transportation requests on the Pending Queue page.

● Ariba Network adapter for SAP NetWeaver does not support mapping files for logistics transports. Buyers can use the TransportRequest and TransportConfirmation transportation requests that Ariba provides to send and receive transportation request to a logistics provider registered on Ariba Network. Ariba Network adapter for SAP NetWeaver only provides the cXML structures and does not provide the mapping files for these transportation requests. Buyers can create and manage mapping files on their own for these transportation request.



5.14.2 Workflow to support third-party logistics providers

The following describes the workflow for sending the transportation request from a buyer to the logistics provider on Ariba Network:

● Buyer sends a purchase order to a supplier Ariba Network. The supplier sends a ship notice with the transportation details to a buyer.

● The buyer sends a transportation request (TransportRequest ) containing transport details to the logistics provider on Ariba Network.

● In response, the logistics provider sends a TransportConfirmation to the buyer to either accept or reject the request for each consignment. If the request is accepted, the logistics provider confirms the transport details.

● The logistics provider picks up the goods from the buyer's warehouse and informs the buyer by sending a TransportConfirmation with a consignment status of "collected". The logistics provider sends the “canceled” status when they are unable to pick up the goods.


6 Topics about configuring SAP ERP

Importing custom code [page 214]

Configuring SAP ERP [page 215]

Proxy settings in SAP ERP [page 240]

Documentation of RFCs within the Ariba Network adapter for SAP NetWeaver [page 245]

Defining authorizations for running Ariba Network transactions [page 245]

ABAP programs for outbound transactions implemented using proxies [page 246]

Configuring enhancement for purchase orders [page 247]

Configuring support for line level hierarchies in service purchase orders [page 251]

How to enable support for setting spend limits on service purchase orders with unplanned spend [page 255]

Configuring advanced pricing details [page 256]

Configuring order confirmations [page 257]

Configuring order inquiries [page 260]

Topics about configuring scheduling agreement releases [page 265]

Configuring ship notices against multiple purchase orders [page 269]

Configuring returns and corrections in receipts [page 272]

Canceling MIRO Invoices [page 275]

Topics about configuring invoice status updates [page 275]

Configuring service sheets [page 279]

Direct invoicing of purchase order service items [page 285]

How to maintain posting keys to process canceled invoices and credit memos [page 286]

Configuring ERP-initiated invoices to use the IDOC [page 287]

Configuring ERP-initiated service entry sheets [page 300]

Configuring Quote Request and Quote Message documents [page 305]

Configuring payment proposals for taxes and discounts [page 308]

How to configure confirmation control keys [page 312]

6.1 Importing custom codeThe Ariba Network adapter for SAP NetWeaver uses custom code to support ERP-initiated invoice, invoice status update, and payment proposal transactions. If you do not import the custom code for these transactions into your SAP ERP instance, you are likely to encounter errors.


Topics about configuring SAP ERP

Related Information

Configuring SAP ERP [page 215]

6.1.1 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 and Change) ORDERS05 ORDERS

Order Confirmation ORDERS05 ORDRSP

Ship Notice DELVRY06 DESADV

Invoice INVOIC02 INVOIC

Remittance PEXR2001 REMADV

Order Status Request ORDERS05 ORDERS

ScheduleAgreementReleaseRequest DELFOR02 DELINS

6.2 Configuring SAP ERP

The following steps pertain to the SAP ERP system 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 [page 216]● Configuring the Partner Profile [page 217]● Maintaining Condition Records for Outbound Transactions: POs [page 225]● Making Additional Change PO Configurations [page 226]● Maintaining Variants for Remittance [page 226]● Making Additional Invoice Configurations [page 226]● Making Additional Tax and Accrual Calculation Configurations [page 228]● Maintaining Bank Key for the House Bank for Payment Remittance Advice [page 234]● Making User Exit Enhancements to Support Shipping and Handling Charges [page 235]

Setting up Ariba Network adapter for SAP NetWeaverTopics about configuring SAP ERP PUBLIC 215

● Maintaining Global Company Code [page 238]● Configuration Related to Export of Requisitions from SAP ERP [page 238]● Business AddIns [page 239]

Related Information

Proxy settings in SAP ERP [page 240]

6.2.1 How to configure SAP ERP for IDoc transactions

Procedure

1. Use Transaction SM59 to create an RFC destination of type ERP.

2. Enter Target host, System Number, Gateway host, and Gateway service on the Technical Settings tab.3. Enter Language, Client, User, and Password on the Logon/Security tab, and then save your entries.4. Use Transaction WE21 to create a port.

5. Choose Transactional RFC and click Create.6. Enter Port, Description, and RFC destination details, and then save your entries.

Related Information

Configuring the partner profiles [page 216]

6.2.2 Configuring the partner profiles

Buyers can specify the partner profile for each vendor or maintain the partner profile at a logical system level for all vendors.

● If you are using SAP Ariba cloud integration release 5.0 or lower, you can only maintain the partner profile for each vendor.

● If you are using SAP Ariba cloud integration release 6.0 and higher, you can maintain the partner profile for each vendor or maintain the partner profile at a logical system level for all vendors.

Configuring the partner profile at vendor-level [page 217]

Configuring the partner profile at logical system-level [page 219]



Related Information

How to create an output type for the entry sheet application [page 224]

6.2.2.1 Configuring the partner profile at vendor-level

Buyers can specify the partner profile for each vendor. If you are using SAP Ariba cloud integration release 5.0 and lower, you can maintain the partner profile for each vendor.

● 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 and Change Purchase Orders using these parameters:

NoteUse the following Change Purchase Order partner profile parameters if you are using the SAP Ariba cloud integration 6.0 and higher.

Parameter Value

Partner function VN

Message type ORDERS

IDoc type ORDERS05

Application EF

Message type NEU

Process Code ME10

Change True (Checked)

Retain the default selection, Transfer IDoc Immed., for the Output Mode parameter in the Outbound Options tab.

● Configure Invoice using these inbound parameters:

Parameter Value

Partner function VN


Parameter Value

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 Ship Notice with these inbound parameters:

Parameter Value

Partner function VN

Message type DESADV

Process Code DESA


● Configure Outward Payment Remittance Advice with these outbound parameters:

Parameter Value

Partner function VN

Message type REMADV

IDoc Type PEXR2001

Retain the default selection, Transfer IDoc Immed., for the Output Mode parameter in the Outbound Options tab.

NoteYou must also configure the bank in the partner profile for the remittance with the relevant port number.

● Configure Early Payment with these inbound parameters:

Parameter Value

Partner function VN

Message type FIDCCH



Parameter Value

Process Code FICH


NoteIf you are using an SAP ERP version that is lower than the SAP ERP 6.0, EHP 6, ensure that you apply the SAP Note 1587217 - FI_DOCUMENT_CHANGE: EMPFB, XREF1_HD, XREF2_HD not changeable, before you run the PayMeNow program.

The Ref.key(head) 1 ARIBA_PMN in the SAP Process Integration Mapping checks for invoices that have been fully approved when the PayMeNow program runs. When this key is enabled, Ariba Network adapter for SAP NetWeaver does not send payment proposals that are fully processed and ready for payment to Ariba Network.

Related Information

Configuring the partner profile at logical system-level [page 219]

6.2.2.2 Configuring the partner profile at logical system-level

If you are using SAP Ariba cloud integration release 6.0 and higher, you can maintain the partner profile for each vendor or maintain the partner profile at a logical system level for all vendors.

SAP ERP buyers using Ariba Network adapter for SAP NetWeaver can maintain SAP ERP partner profile for each vendor or maintain the partner profile at a logical system level for all vendors. This eliminates the buyer's need to maintain multiple IDOC messages exchanged between SAP ERP and SAP Process Integration layer for each vendor.

Buyers can maintain the partner profile on a logical system level for the following transactional documents:

Inbound Document Types

● Order Confirmation● Invoice● Ship Notice● Pay Me Now

Outbound Document Types

● Purchase Order● Remittance● Order Inquiry● Schedule Agreement Release



● Quote Request.

How to configure the partner profile on the SAP ERP system [page 220]

How to configure the partner profile for scheduling agreement releases [page 222]

How to configure the partner profile for invoices [page 223]

6.2.2.2.1 How to configure the partner profile on the SAP ERP system

Prerequisites

SAP S/4HANA, on-premise edition 1511 does not support Output Management based on NACE for new documents in purchase orders by default. To enable the Output Management based on NACE in SAP S/4HANA, on-premise edition 1511, you must apply the following SAP Notes in the exact order listed here:

1. SAP Note 2334067 -DDIC report for enabling NAST-based Output in 1511 OP2. SAP Note 2334068 -Purchase Order: Switch to NAST-based Output Management in S/4HANA OP15113. SAP Note 2338412 -Follow-on note of note 2334068: Output Management -> Switchable Output

Context

Configure the partner profile at the logical system-level for all vendors.

Procedure

1. Run the transaction code BD54 to create a logical system.

2. Click New Entries.3. In the column Log.System, enter the name of the logical system. Save the changes.4. Run the transaction code WE20 to create a partner profile.

5. Click the button Create. Create the partner profile as Partner Type LS.

6. Enter the logical system name in the text box Partner No..7. Enter LS as the logical system in the text box Partn. Type.

8. In the sections Outbound parmtrs and Inbound parmtrs, add the message type for each type of outbound and inbound transaction.

9. In the Partner profiles: Outbound parameters, ensure that you have the following values:

Purchase Orders

○ Message Type: ORDERS○ Partner No.: Name of the logical system






○ Partn. Type: LS (Logical system)○ Partner Role: LS

In the tab Outbound Options, ensure that you have the following values:

○ Receiver port: Name of the transactional RFC port○ Transfer IDoc Immed.: Selected○ Basic type: ORDERS05

In the tab Message Control, ensure that you have the following values in the table:

○ Application: EF○ Message type: NEU○ Process code: ME10

10. In the section Partner profiles: Inbound parmtrs, add the required inbound transactions that you need.

In the section Partner profiles: Inbound parmtrs, ensure that you have the following values for the inbound transaction:

Ship Notice

○ Message Type: DESADV○ Partner Role: LS

Order Confirmation ○ Message Type: ORDRSP○ Partner Role: LS

NoteYou can add the LS partner roles for the other inbound transactions.

11. Start the NACE transaction.

12. Choose application <EF>Purchase Order and click Condition records.13. Click NEU as the output type.14. Double-click the NEU output type and click Purchasing Output Determination: Doc. Type/Purch.Org/

Vendor.15. Click Enter. Enter the values for the document type, purchase organization and vendor.16. Specify the following in the page Change Condition Record (New PO printout): Fast Change:

○ Vendor: The vendor ID○ Funct: LS○ Partner: The logical system created in Step 1.○ Medium: 6 EDI○ Dispatch time: Send immediately

Note○ You must maintain the logical system name for the Invoice Status Update (ISU) in the table /

ARBA/PARAM_TAB.○ To maintain the logical system name for Remittances, you must apply the SAP Note 1441799 -

IDoc REMADV: Alternative partner category and partner number.



○ If you are a customer using SAP ERP 6.0, EPH1, ensure that to make the necessary source code changes and the assigned corrections.

○ If you are a customer using SAP ERP 6.0, EPH 2 and EPH 3, and you already have applied the SAP Note 1441799 , then ensure that you make the assigned corrections. If you do not have the SAP Note, you must make the necessary source code changes and the assigned corrections.

○ If you are a customer using SAP ERP 6.0, EPH 7 and higher, the SAP Note 1441799 is already applied. You must ensure that you make the assigned corrections.

6.2.2.2.2 How to configure the partner profile for scheduling agreement releases

Context

Configure the partner profile on SAP ERP for the LPJ1 and LPHI output types in scheduling agreement releases.

Procedure

1. Start the NACE transaction.2. Click EL application type and then click Output Types.

A new window appears.3. Double-click the LPH1 output type.

A new window appears.4. Click the Default values tab and maintain the following values:

○ Dispatch time: Send immediately (when saving the application)○ Transmission Medium: EDI○ Partner Function: LS○ Communication strategy: To be left blank

5. Define the LS partner profile and maintain the following values:○ Medium: EDI○ Funct: LS○ Name: Logical system

6. Save the changes.7. Repeat step 3 through step 6 for the LPJ1 output type.8. Go back to the NACE transaction.9. Click EL application type and then click Condition Records.

A new window appears.10. Double-click the LPH1 output type.





11. Click Purchasing Output Determination: Doc.Type/Purch.Org/Vendor and then click Enter.

A new window appear.12. Maintain the following values and click Execute:

○ Purchasing Doc.Type: LPA○ Purch. Organization: Enter the purchase organization.○ Vendor: Enter the vendor details.

13. Repeat step 10 through step 11 for the LPJ1 output type.

6.2.2.2.3 How to configure the partner profile for invoices

Context

Configure to maintain the SAP ERP partner profile at a logical system level for invoices.

Procedure

1. Assign the partner to a company code. Go to SPRO MM Logistic Invoice Verification EDI Assign company code . Ensure that you have the following values:○ Partn. Type: LS○ PartnerNo: Enter the logical system name created for the partner profile.○ Comp.code name in the invoice: Enter the company code name.○ CoCd: Enter the company code.

2. Assign the program parameters. Go to SPRO MM Logistic Invoice Verification EDI Enter Program Parameters . Ensure that you have the following values:

○ Partn. Type: LS○ PartnerNo: Enter the logical system name created for the partner profile.○ CoCd: Enter the company code.○ Company Name: Enter the company name.○ City: Enter the city.

3. Assign the tax codes. Go to SPRO MM Logistic Invoice Verification EDI Assign Tax codes . Ensure that you have the following values:

○ Partn. Type: LS○ PartnerNo: Enter the logical system name created for the partner profile.○ Tax type: Enter the tax type.○ Tax rate: Enter the tax rate.○ Ctr: Enter a value.


6.2.3 How to create an output type for the entry sheet application

Procedure

1. Start transaction NACE.

2. Select application ES Entry Sheet and click Output types.3. In the Processing routines section, create an entry as follows:

○ Transmission Medium - 8 (Special Function)○ Program - /ARBA/ENTRYSHEET_UPDATE○ FORM routine - SEND_ENTRYSHEET_RESPONSE○ Save the entry.

4. In the Partner Functions section, create an entry as follows:

○ Medium - 8 (Special Function)○ Function - VN○ Description - Vendor

5. Save the entry.

Related Information

How to maintain condition records for outbound transactions: service sheets [page 224]

6.2.4 How to maintain condition records for outbound transactions: service sheets

Procedure

1. In the main screen when you start the transaction NACE, select application ES Entry Sheet and click Condition records.

2. Click the relevant output type.3. Click Condition records.4. Select Purchasing Output Determination: Document Type option.5. Click the Execute button and maintain the following parameters by creating a new entry:

○ Document Type - NB (for example)○ Partner Function - VN○ Partner Number - 1000 (for example)○ Medium - 8 (Special Function)



○ Date/Time - 4 (when the application is saved)

6. Save the entry.

6.2.5 How to maintain condition records for outbound transactions: purchase orders

Prerequisites

SAP S/4HANA, on-premise edition 1511 does not support Output Management based on NACE for new documents in purchase orders by default. To enable the Output Management based on NACE in SAP S/4HANA, on-premise edition 1511, you must apply the following SAP Notes in the exact order listed here:

1. SAP Note 2334067 - DDIC report for enabling NAST-based Output in 1511 OP2. SAP Note 2334068 - Purchase Order: Switch to NAST-based Output Management in S/4HANA OP15113. SAP Note 2338412 - Follow-on note of note 2334068: Output Management -> Switchable Output

Procedure

1. Using Tcode MN04 or NACE or NACR, in the screen enter output type NEU 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.

NoteIf you also want to generate a printout, maintain the condition record for message type NEU and select Purchasing Output Determination: Document Type. Save the condition record.

Related Information

How to make additional change PO configurations [page 226]





6.2.6 How to make additional change PO configurations

Procedure

1. Navigate to Tcode SPRO, and in the SAP reference IMG navigate to Material ManagementPurchasing Messages Output control Messages Types Define Messages type for purchase order Fine – Tune control: Purchase order .

2. Add new entries for condition type NEU for Change Purchase Order with operation as 2.

3. Save the entry.

Related Information

Maintaining variants for remittance [page 226]

6.2.7 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.

Related Information

Making additional invoice configurations [page 226]

6.2.8 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 VerificationEDI 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 AccountsSet both parameters to active.



● To configure how unplanned delivery costs are posted, use this configuration path: SPRO MMLogistic Invoice Verification Incoming Invoice Configure How Unplanned Delivery Costs are PostedSet the value for the Distribute among invoice items parameter to blank.

Maintaining IDOC type assignment to function module

After you have imported SAP transports that contain objects related to the invoice transaction, perform the following activities:

Navigate to transaction code WE82 and add the following entry:

Message Type Basic Type Extension Release

INVOIC INVOIC02 /ARBA/INVOICE 40A

Navigate to transaction code WE57, and edit the entry as follows:

Function ModuleFunction Type

Basic Type

Extension

Message Type

Message Code

Msg. Function Object Type

Direction

IDOC_INPUT_INVOIC_MRM

F INVOIC02

/ARBA/INVOICE

INVOIC MM BUS2081

2

Configuring Invoices From Ariba Network

When SAP ERP receives invoices from Ariba Network, the invoice is created and stored through the IDOC. To create and store invoices successfully in the IDOC, ensure that you have the following configuration:

● Go to TCode OBCE.● Create an entry at the vendor or logical system level in the Partn. Type field.● Enter the partner number and company code.● Enter value for the following fields in the Posting Details section:

○ G/L db.pstg ky○ G/L cr.pstng ky○ Vend.deb.pstng ky○ Vend.cred.pstng ky○ Tax-ex.tax code○ Invoice doc.type○ Cred.memo doc.type


Related Information

Making additional tax and accrual calculation configurations [page 228]

6.2.9 Making additional tax and accrual calculation configurations

Make the following configurations in the case of purchase order/non purchase order invoices having a tax code with full/partial accrual condition posted to different accounts.

In the transaction ftp, for a particular tax code, different tax levels are maintained using KTOSL (Transaction Key) and KSCHL (Condition Type)

For example, for a particular tax code in the section Self Assessment for the tax type A/P Sales Tax 1 Use, if the tax rate is 60.000%, then the transaction key for this tax level is MW1 and the condition type is JP1U. When the function CALCULATE_TAX_FROM_GROSSAMOUNT returns the result table, it consists of a separate entry for accrual tax, which contains the transaction key and the condition type. As transaction key and condition type may vary between SAP ERP systems, they are configurable using the field value pair in the custom table.

You must maintain the following values in the table /ARBA/PARAM_TAB:

Configuration parameters and their corresponding values for invoices in the table /ARBA/PARAM_TAB

NAME FIELDNAME SIGN OPTI LOW HIGH

ACCRUAL_CONDITION_TYPE JP1U I EQ JP1U

ACCRUAL_TRANSACTION_KEY MW1 I EQ MW1

ACCRUAL_TRANSACTION_KEY MW2 I EQ MW2

Note● The values in this table are examples of a typical configuration and may vary depending on the SAP

ERP configuration. You must maintain these values in transaction SM30 by referring to the accrual condition settings for a particular tax code in the transaction ftxp. In the case of multiple conditions for a single NAME you must change the value of FIELDNAME to form a composite key.

● These three parameters in the table are only used by the ERP CC INVOICE scheduled task.

In addition to maintaining additional tax and accrual calculation configurations, you can store values for other configuration parameters in the table /ARBA/PARAM_TAB.

Earlier document type RE was default and as a result payment proposals were not getting pulled for document types other than RE. Now, document type is not present by default. You must use /ARBA/PARAM_TAB table to store relevant document types that can be used in where condition of SELECT statements to retrieve required invoice documents.

In addition, earlier in SAP ERP, accounting document number BELNR was key field and was sent as the output invoice document number. To send the document reference number XBLNR as the output key field instead of BELNR, a new parameter INVOICE_DOC_OPTION is added to the table /ARBA/PARAM_TAB because XBLNR is a non mandatory field. You must set the INVOICE_DOC_OPTION to XBLNR to ensure that XBLNR is returned as



the output invoice document number. The following table illustrates configuration parameters and their corresponding values:

Additional configuration parameters and their corresponding values for invoices in the table /ARBA/PARAM_TAB

NAME FIELDNAME SIGN OPTI LOW HIGH DESCRIPTION

ERPCC K~XBLNR I NE To filter XBLNR not having any value for ERP-initiated invoices, payment proposals, and invoice status update.

INVOICE_DOC_OPTION I EQ XBLNR To send output invoice number as XBLNR for ERP-initiated invoices, payment proposals, and invoice status update.

INVOICE_DOC_TYPE KR I EQ KR To store general document type for ERP-initiated invoices, payment proposals, and invoice status update.

INVOICE_DOC_TYPE RE I EQ RE

INVOICE_DOC_TYPE KA I EQ KA To store non-PO invoices created in SAP ERP and reversed or canceled using FB08 (KA) and FI invoices (non-PO invoices))

INVOICE_DOC_TYPE_FULL_AUTO

ZP I EQ ZP To store doc type required for full automatic payment for invoice status update.

INVOICE_DOC_TYPE_FULL_MANUAL

KZ I EQ KZ To store doc type required for full manual payment for invoice status update.

INVOICE_DOC_TYPE_PARTIAL

KA I EQ KA To store doc type required for partial payment for invoice status update.

INVOICE_DOC_TYPE_PARTIAL

KZ I EQ KZ

INVOIC02_REJECT_STATUS

51, 71, and so on.

I EQ 51,71, and so on.

Status number of the Invoice IDOC which are rejected. if you do not maintain anything, the default value will be 51.



AVOID_DUPLICATE_ISU_PP

X I EQ X This ensures that duplicate entries for payment proposal and invoice status update are not sent to Ariba Network. If you do not maintain this parameter, duplicate entries for payment proposal and invoice status update are sent to Ariba Network if:

● An invoice is changed on 22.04.2012 and the PP and ISU are sent to Ariba Network on 22.04.2012 and the PP and ISU programs are run on the same date 22.04.2012.

● The PP and ISU for an invoice are already sent to Ariba Network and a user changes a field that does not affect the PP or ISU for example, Vendor Text, and runs the PP and ISU programs.

NET_DISCOUNT_DAYS X I EQ X You need to maintain this parameter if you want to pay only on or after the due date without any discount.

To maintain a date that is greater than 999 days on non-PO invoices, maintain this parameter as X.




GRACE_TIME_ISU_PP Unique Value (Text or Number)

I EQ 5,10, 15, so on

You must maintain the value of this parameter in minutes. The number of minutes you maintain for this parameter is subtracted from the current time (system time) and that time becomes the end time for the ISU and PP scheduled tasks.

For example, you perform the following steps:

Create an invoice Invoice1 at 10:05 A.M.

The input time for the ERPCC scheduled task is 10:00 A.M.

Assuming that the ERPCC scheduled task starts at 10:00 A.M. and ends at 10:15 A.M.

Create an invoice Invoice2 at 10:20 A.M.

Now, if current time (system time) is 10:20 A.M. and ISU and PP is scheduled to start at 10:05 A.M. and end beyond 10.20 A.M., it will pick the ISU or PP for the invoice Invoice2 created at 10:20 A.M. This ISU and PP will fail in Ariba Network because Invoice2 has not been sent to Ariba Network.

To ensure that ISU and PP is not sent for an invoice that has not been sent toAriba Network, you need to maintain a value for this parameter. In the above example, if you had maintained 5 minutes as the value for this parameter, then the end time for the ISU or PP changes to 10:15.M. (Current time - 10:20 – 5 minutes). As a result, the scheduled task does not pick the ISU or PP for the invoice Invoice2 created at 10:20 A.M.



ERP_INV_PROCESSED_STATUS

X I EQ X The invoices that you create in SAP ERP and send to Ariba Network are stored in the table /ARBA/AN_ERPINV. When the InvoiceStatusUpdate (ISU) and Payment Proposal (PP) scheduled tasks run at their scheduled time, the scheduled tasks queries the /ARBA/AN_ERPINV table and sends the ISU and PP only for the invoices that are available in the table. To ensure that ISU and PP scheduled tasks can query the table, you must provide the required value for this parameter.

The ISU and PP scheduled tasks processes invoices in the table /ARBA_AN_ERPINV as follows:

● If you have enabled the ERPCC scheduled task and send ERP-initiated invoices from SAP ERP, ERPCC scheduled task stores information on the ERP-initiated invoices in the /ARBA/AN_ERPINV table.When you send an ISU or PP from SAP ERP, the ISU or PP scheduled task looks into the table /ARBA/AN_ERPINV and filters ERP-initiated invoices associated to the ISU or PP that are already sent to Ariba Network.

● If you have not enabled the ERP CC scheduled task and send ERP-initiated invoices from SAP ERP, ERP CC scheduled task does not store information on the ERP-initiated invoices in the table /ARBA_AN_ERPINV.When you send an ISU or PP from SAP ERP, the ISU or PP scheduled task looks into the table /ARBA_AN_ERPINV to filter ERP-initiated invoices associated to the ISU or PP. In this case, the information about the ERP-initiated invoices does not exist in the table /ARBA_AN_ERPINV and the ISU or PP scheduled task sends the




Ariba Network-generated invoices associated to the ISU or PP to Ariba Network.

INVOICE_DOC_TYPE RE I EQ RE Stores doc types for the ERP-initiated invoice transaction.

● If you maintain this parameter with the document types, then the ERP-initiated invoice function module retrieves invoices for the specified document types.

● If you do not maintain this parameter, then the ERP-initiated invoice function module retrieves invoices for the document types maintained in the table INVOICE_DOC_TYPE.

TAX_AT_LINE X ● If in the transaction OBCO, you have checked the tax jurisdiction procedure (see the following graphic), then the tax is stored line-by-line in the table BSET.If you maintain the value X for the this parameter, then the tax amount for each line item in BSET is retrieved and populated against each line item in the ERP-initiated invoice. In addition, the tax is also updated at the header level.

● If in the transaction OBCO, you have not checked the tax jurisdiction procedure, then total tax for all line items is stored in the table BSET as a consolidated tax amount. In this case, you must maintain the value “ ” (blank) or do not maintain this parameter. The line item tax amount is added to the corresponding line item amount and the consolidated tax amount is added to the header level of the ERP-initiated invoice. Tax amount is not shown at the line item level.


If you maintain single value for a parameter, the field FIELDNAME can be left blank. However, if you want to maintain multiple values for a parameter, you must specify a value for the field FIELDNAME for each new parameter value to ensure a unique record is formed.

NoteIn case INVOICE_DOC_OPTION is set to XBLNR and if XBLNR values for invoice documents are missing in SAP ERP, then the program does not return any records.

Maintaining Tax Jurisdiction

Related Information

Maintaining bank key for the house bank for payment remittance advice [page 234]

6.2.10 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.

NoteIf entries are not maintained as mentioned in the preceding section, the IDoc post fails as it cannot find the correct accounts to post to.

Related Information

Making user exit enhancements to support shipping and handling charges [page 235]

6.2.11 Making user exit enhancements to support shipping and handling charges

/ARBA/Invoice is available 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:

DATA: ls_data_s01 TYPE e1eds01,lv_beznk TYPE mrm_rbkpv-beznk,lv_wskto TYPE mrm_rbkpv-wskto,ls_data_k05 TYPE e1edk05,lv_mwskz TYPE edi5279_a,lv_mwskz_bkn TYPE mwskz_mrm.DATA:ls_/ARBA/ACCOUNT_DATA TYPE /ARBA/ACCOUNT_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_e1edp04 TYPE e1edp04,ls_land1 TYPE land1,ls_txjcd TYPE txjcd,ls_addrnum TYPE ad_addrnum.DATA: t_edid4 TYPE STANDARD TABLE OF edid4.DATA: wa_edid4 TYPE edid4.* 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 InvoiceIF 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.


* Derive the Default Tax Code and Tax Jurisdiction from the* configurationSELECT SINGLE mwskz_bnk txjcd_bnk FROM t169v INTO(e_rbkpv-mwskz_bnk, e_rbkpv-txjcd_bnk)WHERE bukrs = e_rbkpv-bukrs.ENDIF.e_change = 'X'.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* segementIF i_idoc_data-segnam = '/ARBA/ACCOUNT_DATA'.ls_/ARBA/ACCOUNT_DATA = i_idoc_data-sdata.IF NOT ls_/ARBA/ACCOUNT_DATA IS INITIAL.MOVE-CORRESPONDING ls_/ARBA/ACCOUNT_DATA TO ls_cobl_mrm.* Conversion exit for WBS ElementCALL FUNCTION 'CONVERSION_EXIT_ABPSP_INPUT'EXPORTINGinput = ls_/ARBA/ACCOUNT_DATA-ps_psp_pnrIMPORTINGoutput = ls_cobl_mrm-ps_psp_pnrEXCEPTIONSnot_found = 1OTHERS = 2.IF sy-subrc <> 0.* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.ENDIF.* Determine Tax Jurisidction code* We need Tax Jurisidction code only for US so check the country from* the Company CodeSELECT SINGLE land1 adrnr INTO (ls_land1,ls_addrnum)FROM t001WHERE bukrs = ls_/ARBA/ACCOUNT_DATA-bukrs.* If the country is US then get the Tax Jurisidction code* from PlantIF ls_land1 = 'US'.CLEAR ls_cobl_mrm-txjcd.SELECT SINGLE txjcd INTO ls_cobl_mrm-txjcd FROM t001wWHERE werks = ls_/ARBA/ACCOUNT_DATA-werks.* If Tax Jurisidction code is not maintained at Plant level, take it* from Company code levelIF ls_cobl_mrm-txjcd IS INITIAL.SELECT SINGLE taxjurcode INTO ls_txjcd FROM adrcWHERE addrnumber = ls_addrnum.ls_cobl_mrm-txjcd = ls_txjcd.ENDIF.ENDIF.* If taxcode is not sent we will derive using the values maintained in* OBCD.IF ls_cobl_mrm-mwskz IS INITIAL.*SELECT sdata FROM edid4 INTO TABLE ls_sdata*WHERE docnum = i_idoc_data-docnum*AND segnam = 'E1EDP04' .FREE: t_edid4.SELECT *FROM edid4INTO TABLE t_edid4WHERE docnum = i_idoc_data-docnumAND segnam = 'E1EDP04'.SELECT SINGLE sndprn INTO ls_lifnr FROM edidcWHERE docnum = i_idoc_data-docnum.*READ TABLE t_edid4 INTO wa_edid4 INDEX 1.*LOOP AT ls_sdata INTO ls_e1edp04.LOOP AT t_edid4 INTO wa_edid4.ls_e1edp04 = wa_edid4-sdata.



SELECT SINGLE mwskz INTO ls_cobl_mrm-mwskz FROM t076mWHERE parart = 'LI' ANDkonto = ls_lifnr ANDmwart = ls_e1edp04-mwskz ANDmwsatz = ls_e1edp04-msatz ANDland1 = ls_land1.ENDLOOP.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' .FREE: t_edid4.SELECT *FROM edid4INTO TABLE t_edid4WHERE docnum = i_idoc_data-docnumAND segnam = 'E1EDP04'.LOOP AT t_edid4 INTO wa_edid4.ls_e1edp02 = wa_edid4-sdata.IF ls_e1edp02-qualf = '001'.* Get the Po and fetch the payment termSELECT SINGLE zterm INTO e_rbkpv-zterm FROM ekkoWHERE ebeln = ls_e1edp02-belnr.ENDIF.ENDLOOP.* if PO line is not present get the payment term from Vendor MasterIF e_rbkpv-zterm IS INITIAL.SELECT SINGLE sndprn INTO ls_lifnr FROM edidcWHERE docnum = i_idoc_data-docnum.SELECT SINGLE zterm INTO e_rbkpv-zterm FROM lfm1 WHERElifnr = ls_lifnr.ENDIF.e_change = 'X'.ENDIF.*Passing IDOC NumberIF i_idoc_data-segnam = 'E1EDK01'.e_rbkpv-sgtxt = i_idoc_data-docnum.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_frsegLOOP 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 385756e_rbkpv-xmwst = 'X'. e_change = 'X'.

NoteThe ABAP sample code in the two referenced user exits EXIT_SAPLMRMH_014 and EXIT_SAPLMRMH_015 expects the shipping charges to be on a E1EDS01 020 segment of the invoice IDOC.

Related Information

Maintaining global company code [page 238]

6.2.12 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.

Related Information

Configuration related to export of requisitions from SAP ERP [page 238]

6.2.13 Configuration related to export of requisitions from SAP ERP

To ensure that the requisitions created in SAP ERP are exported to Ariba Network and in turn to SAP Ariba Buying solutions, perform the following configuration activities:

Configure /ARBA/REQPARAM Table

In SAP ERP, go to transaction SM30 and configure the /ARBA/REQPARAM table with the following:

● Order Type● Purchase Requisition (optional when configuring for the first time)● Date (optional when configuring for the first time)



● Time (optional when configuring for the first time)

Enable Proxy Configuration

For more information, see Proxy Settings in SAP ERP [page 240].

Run/schedule the /ARBA/REQUISITION_EXPORT program

In SAP ERP, go to transaction SE38 and run or schedule the /ARBA/REQUISITION_EXPORT program.

Related Information

Business AddIns [page 239]

6.2.14 Business AddIns

The following Business AddIns (BAdIs) are available inside the programs that allow you to enhance the functionality as required.

BAdI Name Description

/ARBA/PO_MODIFY Available in /ARBA/PO_ACCOUNTING_INFO and /ARBA/PO_SERVICE_INFO and /ARBA/PURCHASEORDER_CSCfunction modules. Use this BAdI to enhance the purchase order transaction as required. This BAdI has the following methods:

● READ_PO_DATA● SAVE_PO_DATA● READ_SERVICE_PO_DATA● SAVE_SERVICE_PO_DATA

The first two methods are available in the /ARBA/PO_ACCOUNTING_INFO function module. The other two are available in the /ARBA/PO_SERVICE_INFO function module.

● DELETE_LINE_FILTERThis method is available in the /ARBA/PURCHASEORDER_CSC function module.

/ARBA/INVOICE_UPDATE Available in the /ARBA/ERPINVOICE_EXPORT program. Use this BAdI to enhance the ERP-initiated invoice transaction as required.


BAdI Name Description

/ARBA/ISU_UPDATE Available in the /ARBA/INVSTATUPDT_EXPORT program.

This BAdI is available only in SAP Ariba cloud integration 5.0 and earlier. For SAP Ariba cloud integration 6.0, use the BAdI /ARBA/BTE_INVSTATUPDT_EXPORT.

Use this BAdI to enhance the ISU transaction as required.

/ARBA/PP_UPDATE Available in the /ARBA/PAYPROPOSAL_EXPORT program. use this BAdI to enhance the payment proposal transaction as required. The method, change_pp_tax allows buyers to override the tax information in the payment proposal.

/ARBA/RECEIPT_UPDATE Available in the /ARBA/RECEIPT_PUBLISH program. Use this BAdI to enhance the receipt transaction as required.

/ARBA/PR_CHANGE Available in the /ARBA/REQUISITION_EXPORT program. Use this BAdI to enhance the requisition transaction as required.

Implementing a BAdI

If you want to add a new field and send it to Ariba Network, perform the following steps:

1. Identify the structure in which you want to add a field. For example, you want to add a new field to the /ARBA/EKPO structure.

2. Start transaction SE11, open the structure and click Append Structure to create a new structure and add the required fields.

3. Start transaction SE19, create an implementation for the definition /ARBA/PO_MODIFY.

After creating the implementation, write the required code inside the available methods.

1. To fetch data for the fields you added, write the code inside the READ_PO_DATA method. To send this data to SAP Process Integration, use the SAVE_PO_DATA method to populate the output structures.

2. Save and activate the BAdI.3. To send this data to Ariba Network from SAP Process Integration, enhance the custom mappings provided

by Ariba.

6.3 Proxy settings in SAP ERP

How to configure proxy settings for SAP Process Integration 7.1 or dual stack (ABAP and Java) instances of SAP Process Integration 7.3 and above [page 241]

How to configure proxy settings for single stack (Java only) instances of SAP Process Integration 7.3 and above [page 244]



Related Information

Documentation of RFCs within the Ariba Network adapter for SAP NetWeaver [page 245]

6.3.1 How to configure proxy settings for SAP Process Integration 7.1 or dual stack (ABAP and Java) instances of SAP Process Integration 7.3 and above

Context

If you are using SAP Process Integration 7.1 or the dual stack (ABAP and Java) instance of SAP Process Integration 7.3 and above, then perform the following steps to configure proxy. The following configuration is done in SAP ERP. The RFC destination names vary from system to system. While configuring, specify the RFC destination names accordingly.

Procedure

1. Start Transaction SM59 and check if following configurations exist:

○ SAP_PROXY_ESR under HTTP Connections to External Server.○ XI_INTEGRATIONSERVER_<SID> (SID - system identifier) under HTTP Connections to

ABAP System.○ LCRSAPRFC under TCP/IP Connections. Specify the program ID similar to the one created under Jco

RFC destinations (LCRSAPRFC_<SID>, where SID is the system identifier)○ SAPSLDAPI under TCP/IP Connections. Specify the program ID similar to the one created under Jco

RFC destinations (SAPSLDAPI_<SID>, where SID is the system identifier)

2. Start transaction SLDAPICUST.

3. Enter SAP XI hostname, port, XI user ID, and password.4. Start transaction SXMB_ADM.

5. Expand Integration Engine Configuration .6. Click Integration Engine Configuration to edit global configuration data.


7. Under Global Configuration Data, enter:

○ Role of Business System - Application System○ Corresponding Integ. Server - dest://<XI_INTEGRATIONSERVER_PPI> (H Type RFC destination

mentioned above)8. Click Specific Configuration.

Enter the following:

○ Category - Runtime○ Parameter - IS_URL○ Current Value - dest://<XI_INTEGRATIONSERVER_PPI> (H Type RFC destination mentioned above)

9. Run SLDCHECK command in SAP ERP.



Results

The SAP Process Integration server appears and displays the following:


Summary indicates that connection to XI is successful.

6.3.2 How to configure proxy settings for single stack (Java only) instances of SAP Process Integration 7.3 and above

Context

If you are using the single stack (Java only) instance of SAP Process Integration 7.3 or above, then perform the following steps to configure proxy:

Procedure

1. Start Transaction SM59 and create RFC destination SAP_PROXY_ESR (Type G) under HTTP Connections to External Server.a. Under the Technical Settings tab, add AEX (PI Java Stack) server host name and port.b. In the Path Prefix field, enter /rep.c. Under the Logon & Security tab, user must be assigned to role SAP_XI_REP_SERV_USER.

2. Create an HTTP destination to AEX of Type G (example: PI_AEX) as follows:a. Under the Technical Settings tab, add AEX (PI Java Stack) server host name and port.b. In the Path Prefix field, enter /XISOAPAdapter/MessageServlet?ximessage=true.c. Under the Logon & Security tab, user must be assigned to role SAP_XI_REP_SERV_USER.

3. Start transaction SXMB_ADM.

4. Expand Integration Engine -> Configuration.5. Click Integration Engine Configuration to edit global configuration data.6. Under Global Configuration Data, enter:

○ Role of Business System - Application System○ Corresponding Integ. Server - dest://<PI_AEX> (G Type RFC destination mentioned above in step

2)Refer graphic in the dual stack configuration in the previous section.

7. Click Specific Configuration and enter the following:

○ Category - Runtime○ Parameter - IS_URL○ Current Value - dest://<PI_AEX> (G Type RFC destination mentioned above in step 2)

Refer graphic in the dual stack configuration in the previous section.8. Start transaction SLDAPICUST.

9. Enter SAP XI hostname, port, XI user ID, and password.10. Run SLDCHECK command in SAP ERP.



6.4 Documentation of RFCs within the Ariba Network adapter for SAP NetWeaver

During implementation, to meet your specific integration requirements, you can enhance the RFCs provided by SAP Ariba by adding customer exits and making changes to enhancement points.

The documentation of RFCs provides details about the implementation of the RFCs for ERP-initiated invoice, invoice status update, and payment proposal transactions. Based on this information, you can enhance your implementations by making changes as required.

Related Information

Defining authorizations for running Ariba Network transactions [page 245]

6.5 Defining authorizations for running Ariba Network transactions

By default, all SAP ERP users are authorized to execute all Ariba Network transactions. However, if you require only selected users to be authorized to execute these transactions, then you need to define authorizations accordingly. To define the required authorizations, an authorization object needs to be created in SAP ERP and must be assigned to the RFC Communication Channel user. This user is assigned to the RFC communication channel in SAP Process Integration.

In SAP ERP, create an authorization object by using transaction SU21.

NoteIf you already have an authorization object class, then you can create the authorization object under that class. However, if you do not have an authorization object class specifically for SAP Ariba, then first create an authorization object class /ARB before creating the authorization object.

You must create the authorization object with the following details:

● Object name - /ARBA/RFC● Description - Ariba Network Adapter Authorization Object● Authorization Class – new /ARB or existing class

Authorization Fields:

1. RFC_TYPE - Type of the RFC object to be protected.2. RFC_NAME - Name of the RFC to be protected.

Once the authorization object /ARBA/RFC is created, it must be assigned to a role in the transaction code PFCG. If the role exists for the RFC Communication Channel user, then assign the authorization object to the role directly or create a new role and profile and then assign the authorization object.


In the transaction PFCG, while assigning the authorization object to the role:

1. Check the checkbox FUGR for RFC_TYPE.2. Provide the names of the Ariba Network RFC function modules based on the user’s transaction level

authorization for RFC_NAME.

For example, /ARBA/INVOICE_GET_DETAILS and other invoicing function modules must be assigned to users who are authorized to run the invoice transaction.

Related Information

ABAP programs for outbound transactions implemented using proxies [page 246]

6.6 ABAP programs for outbound transactions implemented using proxies

The following ABAP programs have been created by using the existing RFC code for the outbound transactions, payment proposal, receipt, and ERP-initiated invoice:

Transaction Name ABAP Program Name

ERP-Initiated Invoice /ARBA/ERPINVOICE_EXPORT

NoteThis is available only for SAP Ariba cloud integration release 5.0 and earlier.

Payment Proposal /ARBA/PAYMENTPROPOSAL_EXPORT

Receipt /ARBA/RECEIPT_PUBLISH

Note● To filter data, RFCs read the values that you maintain for the parameters in the /ARBA/PARAM_TAB.

Therefore, ensure that you have maintained values for all the required parameters.● The ABAP code is not case sensitive. Ensure that you maintain the case value in the code that SAP

Ariba provides you for specific document transaction enhancements.

These above mentioned ABAP programs have been modified as follows:

The existing RFC's use Start Date and Time as input parameters, whereas these proxy programs read date and time from a custom table /ARBA/PROXYPARAM that stores the start date and timestamp for three transactions, ERP-initiated invoice and PP and fiscal year and document number for the receipt transaction. You need to manually maintain the values in this table before the proxy programs are executed either manually or by the SAP Scheduler. The proxy programs fetch data incrementally from the last date and time or document number (in case of receipts) maintained in the table and send that data to SAP Process Integration



in a batch. The SAP Process Integration mappings then split the data into multiple cXML messages and send these cXML messages to Ariba Network through the cXML Adapter. No change is made to the data processing logic. The data, which was earlier populated to RFC tables, is now populated to the proxy structures.

The receipt program now additionally:

● Pulls receipt document numbers from MKPF● Filters documents to exclude the following:

○ Documents which are not of movement type 101○ Documents for vendors not stored in the table /ARBA/AN_VENDOR

● Fetches receipt data by using BAPI_GOODSMVT_GETDETAIL

Related Information

Configuring enhancement for purchase orders [page 247]

6.7 Configuring enhancement for purchase orders

To enable SAP ERP to send correct new, change, and cancel purchase order information to the Ariba Network adapter for SAP NetWeaver, you must implement custom exit in SAP ERP.

Related Information

Configuring support for line level hierarchies in service purchase orders [page 251]

6.7.1 How to configure implicit enhancements for new purchase orders

To enable SAP ERP to send new purchase order information to the Ariba Network adapter for SAP NetWeaver, you must configure an implicit enhancement in SAP ERP.

Procedure

1. In SAP ERP, navigate to the transaction code SE37 - IDOC_OUTPUT_ORDERS and click Display.

2. Search for Perform fill_srv_orders.

3. Double-click Perform.


4. Select SAPLEINM from the popup.5. Click Enhance in the application toolbar.

6. Click Edit Enhancement Operations Show Implicit Enhancement Options to display a line after the fill_srv_orders form.

7. Right-click the line and select Enhancement Implementation Create .8. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement

Implementation.9. Click Create Enhancement Implementation.10. Enter a name and description for the enhancement and press Enter.11. In the package popup, specify your Z or Y package, press Enter, and save the package to a transport

request.12. Copy the following code:

DATA: 1_flag(5) TYPE c, cl_purchaseorder TYPE REF TO /arba/cl_purchaseorder, cl_po_hierarchy TYPE REF TO /arba/cl_po_hierarchy, ls_idoc_status TYPE bdidocstat, lx_appl_idoc TYPE REF TO /arba/cx_appl_idoc.CONSTANTS: c_true TYPE char4 VALUE 'true', c_false(5) TYPE c VALUE 'false'.CREATE OBJECT cl_purchaseorder.CREATE OBJECT cl_po_hierarchy.TRY. CREATE OBJECT cl_po_hierarchy. CALL METHOD cl_po_hierarchy->get_systemversion_ishierarchy EXPORTING ebeln = ekpo-ebeln et_edi_esll = edi_esll[] IMPORTING flag = l_flag CHANGING int_edidd = int_edidd[]. CATCH /arba/cx_appl_idoc INTO lx_appl_idoc. MESSAGE e151(/arba/message) RAISING error_message_received. RETURN.ENDTRY.IF l_flag EQ c_true. CALL METHOD cl_purchaseorder->fill_service_line_number EXPORTING packno = ekpo-packno IMPORTING et_edi_esll = edi_esll[]. ENDIF.

13. Paste the copied code into the Enhancement Implementation.14. Activate the enhancement and save it.

15. Right-click below the last line in the fill_srv_orders form and select Enhancement Implementation Create .

16. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation.

17. Select the enhancement created and named in Step 10.



18. Copy and paste the following code:

IF l_flag EQ c_true. CALL METHOD cl_purchaseorder->create_parent_child_relation EXPORTING edi_esll = edi_esll[] CHANGING int_edidd = int_edidd[]. ENDIF

19. Activate the enhancement and save it.

6.7.2 How to configure implicit enhancements for change and cancel Orders

To enable SAP ERP to send the correct change and cancel order information to the Ariba Network adapter for SAP NetWeaver, you must configure an implicit enhancement in SAP ERP.

Procedure

1. In SAP ERP, navigate to transaction code SE38 - LEINMF0Q and click Display.

2. Select SAPLEINM from the popup.3. Click Enhance in the application toolbar.

4. Click Edit Enhancement Operations Show Implicit Enhancement Options to display a line after the lesen-beleg form.

5. Right-click the line and select Enhancement Implementation Create .6. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement



DATA: cl_PO_ChangeCancel TYPE REF TO /arba/cl_PO_ChangeCancel. CREATE OBJECT cl_PO_ChangeCancel.CALL METHOD cl_PO_ChangeCancel->trigger_delete_po_idoc EXPORTING ebeln = h_ebeln CHANGING xdruvo = xdruvo.



6.7.3 Implementing a custom exit for purchase orders

How to implement a custom exit for purchase orders to fill additional details [page 250]

How to implement a custom exit for purchase orders to send partner function 9W details [page 251]

6.7.3.1 How to implement a custom exit for purchase orders to fill additional details

Context

The FILL_ADDITIONAL_DETAILS method in the function module /ARBA/CL_PURCHASEORDER is called from a custom exit MM06E001 - this is the user exit for outbound purchase orders.

Procedure

1. In SAP ERP and SAP S/4HANA, navigate to the transaction code CMOD. Create a new custom exit. For example, ZMMIDOC.

2. Click Create.3. Click Enhancement Assignments and then enter the user exit name MM06E001.

4. Click Enter.5. Go back and click Components and then double-click the enhancement name EXIT_SAPLEINM_011.6. In the new screen that appears, double-click INCLUDE ZXM06U33 and click Enter.7. Copy and paste the following code:

DATA: lo_purchaseorder TYPE REF TO /arba/cl_purchaseorder. CREATE OBJECT lo_purchaseorder.CALL METHOD lo_purchaseorder->fill_additional_detailsEXPORTINGdekko = dekkodpekko = dpekkocontrol_record_out = control_record_outdobject = dobjectCHANGINGdekpo = dekpo[]dpekpo = dpekpo[]deket = deket[]desll = desll[]dint_edidd = dint_edidd[].

8. Click Activate.9. Go back and activate the user exit also.



Related Information


6.7.3.2 How to implement a custom exit for purchase orders to send partner function 9W details

Context

The function module /ARBA/PO_PARVW is called from a custom exit MM06E001 to add partner function 9W to the corresponding IDoc Order/Orders05 - this is the user exit for outbound purchase orders.

Procedure

1. In SAP ERP and SAP S/4HANA, navigate to the transaction code CMOD. Create a new custom exit. For example, ZMMIDOC.

2. Click Create.3. Click Enhancement Assignments and then enter the user exit name MM06E001.

4. Click Enter.5. Go back and click Components and then double-click the enhancement name EXIT_SAPLEINM_002.6. In the new screen that appears, double-click INCLUDE ZXM06U02 and click Enter.7. Click Activate.8. Go back and activate the user exit also.

Related Information


6.8 Configuring support for line level hierarchies in service purchase orders

Ariba Network adapter for SAP NetWeaver enables transmission of service purchase orders with service line-items in up to five levels of hierarchy (1 parent and 4 child levels) from SAP ERP to Ariba Network. For more information on service purchase orders, see Purchase order [page 15].


Requirements

To configure this feature a system administrator must:

● Reconfigure the SAP Partner Profile (WE20) to modify the configuration of service orders.● Create an implicit enhancement for service order functionality in the SAP ERP system. For more

information, see How to configure implicit enhancements for new service orders [page 254].

Backward Compatibility

The hierarchical display of service line items necessitates changes in SAP ERP and the Ariba Network adapter for SAP NetWeaver that affect how transmission of purchase orders, change orders, and update orders are handled. These changes are not backward compatible with previous releases.

NoteYou must remove previously existing change order configuration from your Ariba solutions. If you also have change order transaction customizations and want to continue to use them, they must be migrated to purchase order transactions instead.

Related Information

How to enable support for setting spend limits on service purchase orders with unplanned spend [page 255]

6.8.1 Limitations

The following limitations apply to the transmission of purchase orders with up to a 5-level deep hierarchy of service lines in purchase orders.

● This feature requires SAP ERP 6.0, EHP 4 and greater. Attempting to create a PO with a 5-level deep hierarchy when using EHP3 or lower generates an error message in PO Message tab.

● SAP ERP restrict a hierarchy to a maximum of 5 levels: each top-level service line-item can have up to four additional levels of nesting below the top-level item. Ariba Network can display the full hierarchy for service lines.

● Hierarchies are not supported for order confirmations.● The last service item in a hierarchy cannot be blank.● SAP Note 2020660 - Update Termination in ME_UPDATE_DOCUMENT (POEXT) might require

implementation if it is not already installed and errors are generated when changing or updating a PO.




6.8.2 Configuring implicit enhancements

To enable SAP ERP to send correct new, change, and cancel service order with hierarchical information to the Ariba Network adapter for SAP NetWeaver, you must configure two implicit enhancement in SAP ERP.

How to configure implicit enhancements for change and cancel service orders [page 253]

How to configure implicit enhancements for new service orders [page 254]

6.8.2.1 How to configure implicit enhancements for change and cancel service orders

Context

To enable SAP ERP to send the correct change and cancel order information to the Ariba Network adapter for SAP NetWeaver, you must configure an implicit enhancement in SAP ERP.

Procedure

1. In SAP ERP, navigate to transaction code SE38 - LEINMF0Q and click Display.

2. Choose SAPLEINM from the popup.3. Click Enhance in the application toolbar.

4. Click Edit Enhancement Operations Show Implicit Enhancement Options to display a line after the lesen-beleg form.

5. Right-click the line and choose Enhancement Implementation Create .6. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement






6.8.2.2 How to configure implicit enhancements for new service orders

Context

To enable SAP ERP to send new service order information to the Ariba Network adapter for SAP NetWeaver, you must configure an implicit enhancement in SAP ERP.

Procedure

1. Run the transaction code SE37 - IDOC_OUTPUT_ORDERS in SAP ERP and click Display.2. Search for Perform fill_srv_orders.3. Double-click Perform.4. Choose SAPLEINM from the popup.5. Click Enhance in the application toolbar.

6. Click Edit Enhancement Operations Show Implicit Enhancement Options to display a line after the form fill_srv_orders.

7. Right-click the line and choose Enhancement Implementation Create .8. Click Code on the popup Enhancement to display Select or Create Enhancement

ImplementationChoose Type of Enhancement.9. Click Create Enhancement Implementation.10. Enter a name and description for the enhancement and press Enter.11. In the package popup, specify your Z or Y package, press Enter, and save the package to a transport


DATA: l_flag(5) TYPE c, cl_purchaseorder TYPE REF TO /arba/cl_purchaseorder, cl_po_hierarchy TYPE REF TO /arba/cl_po_hierarchy, ls_idoc_status TYPE bdidocstat, lx_appl_idoc TYPE REF TO /arba/cx_appl_idoc. CONSTANTS: c_true TYPE char4 VALUE 'true', c_false(5) TYPE c VALUE 'false'. CREATE OBJECT cl_purchaseorder. CREATE OBJECT cl_po_hierarchy. TRY. CREATE OBJECT cl_po_hierarchy. CALL METHOD cl_po_hierarchy->get_systemversion_ishierarchy EXPORTING ebeln = ekpo-ebeln et_edi_esll = edi_esll[] IMPORTING flag = l_flag CHANGING



int_edidd = int_edidd[]. CATCH /arba/cx_appl_idoc INTO lx_appl_idoc. MESSAGE e151(/arba/message) RAISING error_message_received. RETURN. ENDTRY. IF l_flag EQ c_true. CALL METHOD cl_purchaseorder->fill_service_line_number EXPORTING packno = ekpo-packno IMPORTING et_edi_esll = edi_esll[]. ENDIF.

13. Paste the copied code into the Enhancement Implementation.14. Save the enhancement in appropriate customer package and activate it.

15. Right-click the line just before the end of the form fill_srv_orders and choose Enhancement Implementation Create .

16. Click Code on the popup Choose Type of Enhancement to display Select or Create Enhancement Implementation.

17. Choose the created and named enhancement in Step 10.18. Copy the following code:

IF l_flag EQ c_true. CALL METHOD cl_purchaseorder->create_parent_child_relation EXPORTING edi_esll = edi_esll[] spras = ekko-spras CHANGING int_edidd = int_edidd[].ENDIF.


6.9 How to enable support for setting spend limits on service purchase orders 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.

NoteThe 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 Process Integration:

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 ItemOutBlanketItemDetail Extrinsic

5. For the UDF setParentNode:

a. Choose User defined Functions from the Functions dropdown and drag and drop the UDF setParentNode.

b. From the Source Message, choose Request OrderRequest ItemOut BlanketItemDetailExtrinsic 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.

Related Information

Configuring advanced pricing details [page 256]

6.10 Configuring advanced pricing details

While creating a PO in SAP ERP, the user can specify advanced pricing details for a line item or multiple line items. Advanced pricing details includes:

● Quantity Based Pricing● Unit Conversion Pricing

Quantity based pricing allows the unit price of an item to be based on a different price unit quantity than 1. Unit Conversion Pricing allows unit of measure conversion in the pricing calculation, when the unit of measure on the order differs from the pricing unit of measure.

When a PO with advanced pricing details is exported from SAP ERP , the following fields are added in the IDOC:

● PriceBasisQuantity● PriceBasisQuantityUOM



● ConversionFactor● PriceBasisQuantityDesc

During transformation in SAP Process Integration, these fields are added to the cXML and sent to Ariba Network.

Advanced pricing details also apply for change purchase order and payments.

Related Information

Configuring order confirmations [page 257]

6.11 Configuring order confirmations

How to implement the custom exit to process the order confirmation with rejected line items [page 257]

How to configure enhancements for comments in order confirmations [page 258]

How to configure the confirmation category for order confirmations [page 259]

Related Information

Configuring order inquiries [page 260]

6.11.1 How to implement the custom exit to process the order confirmation with rejected line items

Context

This custom exit is required if you are using SAP Ariba cloud integration release version 6.0 or higher. To prevent errors while processing order confirmations containing line items with the Rejected status, buyers must implement the custom exit, MM06E001. The method, UPDATE_IDTNR has been created in the class /ARBA/CL_PO_CONFIRMATION. This method is used to select all the material numbers (Buyer Part IDs) for the purchase order from the table EKPO. Buyers must call the method UPDATE_IDTNR from EXIT_SAPLEINM_007. The class, /ARBA/CL_PO_CONFIRMATION is called from the custom exit, MM06E001. This is the user exit for all EDI inbound and outbound purchasing documents.


Procedure

1. Run the transaction code CMOD.

2. Create a new custom exit. For example, ZOR.

3. Click Create.4. Click the button Enhancement Assignments and then enter MM06E001 as the user exit name.

5. Click Enter.6. Go back and click the button Components and then double-click the enhancement name

EXIT_SAPLEINM_007.7. In the new screen that appears, double-click INCLUDE ZXM06U19 and click Enter.8. Copy and paste the following code:

data ls_status type bdidocstat. ls_status = i_status.call method /arba/cl_po_confirmation=>update_idtnr exporting i_control = i_control ct_status = i_status changing i_data = i_data[] is_ekpo = c_ekpo.

9. Save the enhancement in the appropriate customer package and activate it.10. Go back and activate the user exit also.

6.11.2 How to configure enhancements for comments in order confirmations

Prerequisites

The latest transport code must be installed in SAP ERP before creating this enhancement. This implicit enhancement allows you to process comments in order confirmations.

Procedure

1. Log in to SAP ERP and navigate to transaction SE80.

2. Click Repository Information System in the left panel.3. Choose Program Library in the Object section of the left panel.4. Double-click Includes.5. Enter ZXM06U20 in the Include name field.

6. Press F8 or click Execute.



7. Double-click the highlighted Include name in the Results list on the right panel.

8. Click Display Change to put the Include into change mode.

If prompted for the developer access key, enter the access key information.9. Copy the following code and paste it into the top of the Include just below the comments.

CALL METHOD /arba/cl_po_confirmation=>update_po_text EXPORTING i_control = i_control is_ekko = order it_edidd = i_data[] CHANGING ct_status = i_status[].

10. Click Save, and then click Activate to activate the changes.

6.11.3 How to configure the confirmation category for order confirmations

Context

Configure the confirmation category AB to process the time tolerances in order confirmations against purchase orders.

Procedure

1. Run the transaction code SPRO.

2. Go back to the Display IMG page.

3. Click the tree structure, Materials Management Purchasing Confirmations Set up Confirmation Control .

4. Ensure that you specify the following values in the Change View Confirmation control keys:Overview window:

5. Click Confirmation sequence under the Dialog Structure tree view to view the confirmation control key sequence.

6. Click New Entries.7. Enter the following values for the confirmation sequence:

○ Conf. Category: Enter AB.○ Description: Enter Order acknowledgment.○ MRP-Relevant: Check this field.○ GR-Relevant: Do not check○ GR-Assignment: Do not check○ Monitoring Pert: Leave it blank.


○ Ref. Date: Leave it blank.○ VMat: Check this checkbox to update the vendor material ID in the purchase order based on the

supplier part Id received from An through the order confirmation document.

6.12 Configuring order inquiries

Order inquiry output types and reminders

Buyers can create two output types for an order inquiry:

● MAHN (Dunning)● AUFB (Dunning Order Confirmation)

Buyers can set reminders using the transaction code ME91F. This generates the MAHN output type of order inquiry. The Ariba Network adapter for SAP NetWeaver calculates the date programmatically before sending reminders to the suppliers. The reminders are calculated as follows:

● If the calculated date is less than the current date, the reminder code is populated as zero {MAHNZ}.● If the calculated date is more than the current date, the actual reminder code is populated by taking the

value from EKET-MAHNZ.

The transaction code ME92F sends reminders by specifying the number of days in the confirmation control key SPRO setting, This generates the AUFB output type of order inquiry.

The transaction code SO10 stores the reminder text. Based on the reminder level, the associated text is picked up and sent to the supplier.

The /ARBA/PARAM_TAB stores the reminder text with the variable name ORDERENQUIRY.

For example:

Variable Name Field Name Number Option Selection Value

ORDERENQUIRY DUNNING1 I EQ ZMM_DUNNING1



ORDERENQUIRY DUNNING_OC I EQ ZMM_DUNNING_OC

ORDERENQUIRY PURCHASE_CONF_CATEGORY

AB

NotePURCHASE_ORDER_CATEGORY must be maintained and a value provided for it to prevent order inquiry failure.

The Reminder text is populated in /ARBA/ORDENQ_COMMENTS.



Note● The namespace for order inquiries is http://ariba.com/xi/ASN/OrderEnquiry.● The CDF_Fulfill_XSD structure contains changes to support order inquiries.● The Ariba Network adapter for SAP NetWeaver sends inquiries only for line items that contain

reminders.

Related Information

Order inquiries [page 25]How to configure SAP IDOC for order inquiries [page 261]How to configure the partner profile [page 262]How to maintain condition records for inquiries [page 263]How to implement a custom exit for the order inquiries function module [page 264]Support for additional cXML fields [page 265]

6.12.1 How to configure SAP IDOC for order inquiries

Context

The following SAP IDOC configuration is required for using the sample data mapping:

Transaction IDOC Basic Type Message Type

OrderStatusRequest ORDERS05 ORDERS

Configuring the IDOC transaction to support inquiries for purchase orders on SAP ERP involves the following steps:

● Installing the transports for the purchase order and change purchase order transaction. For more information, see How to import the design package [page 70].

● Configuring the IDOC. For more information, see Configuring SAP IDOC for Order Inquiries [page 261].● Configuring the partner profile. For more information, see Configuring the Partner Profile [page 217].

Procedure

1. In SAP ERP, navigate to transaction code SM59 to create an RFC destination of type ERP.

2. Enter the Target host, System Number, Getaway host, and Getaway service on the Technical Settings tab.

3. Enter the Language, Client, User, Password on the Logon/Security tab, and then save your entries.


4. Navigate to transaction code WE21 to create a port.

5. Choose Transactional RFC and click Create.6. Enter Port, Description and RFC destination details, and then save your entries.

For more information on the IDOC, see Configuring SAP IDOC for Order Inquiries [page 261].

6.12.2 How to configure the partner profile

Procedure

1. In SAP ERP, navigate to the transaction code WE20 to create a partner profile for a vendor.

2. Expand the Partner type LI (Vendor) and choose the vendor that you want to configure the partner profile.3. In the Outbound parameters table, click the Add button and enter the following entries:

○ Partner Function: VN○ Receiver Port: Configure the SAP Process Integration that sends the inquiries.○ Partner Number: Corresponding Partner Number○ Partner Type: LI○ Partner Role: VN○ Message Type: ORDERS○ Receiver Port: Enter the SAP Process Integration Receiver Port○ Basic Type: ORDERS05○ Extension: /ARBA/ORDENQ○ Message Type: ORDERS○ Message Variant: OER○ Message Function: OER

4. Click the Message Control tab.5. Click the Add button in the table control.6. Enter the following values:

Application Message Type Process Code Change Indicator

EF MAHN ME10 Blank

EF MAHN ME10 x

EF AUFB ME10 Blank

EF AUFB ME10 x

7. Select Trigger immediately as the value for the Processing by Function Module parameter, if you want real time processing.

8. Save your entries.9. Navigate to the transaction code WE57 to assign the function module to the logical message and IDOC

Type. To do this, click New Entries and enter the following values:



Parameter Value

Function Module Name IDOC_OUTPUT_ORDERS

Function Type FUNCTION MODULE

Basic Type ORDERS05

Enhancement /ARBA/ORDENQ

Message Type ORDERS

Message Code OER

Object Type BUS2012

Direction 1

10. Use the transaction WE82 to assign the function module to the logical message and IDOC Type. To do this, click New Entries and enter the following values:

Results

Parameter Value

Message Type ORDERS

Basic Type ORDERS05

Extension /ARBA/ORDENQ

6.12.3 How to maintain condition records for inquiries

Procedure

1. Run the transaction code NACE, select application EF and click Condition records.

A new screen appears.2. Double-click the output type: MAHN (Dunning) B.

A new screen appears.3. Click the tab Default Values and retain the following values in the tab:

○ Despatch time: Send immediately○ Transaction Medium: EDI○ Partner function: VN

4. Click the tab General Data and check Multiple issuing. You must perform this action.5. Save the entries and go back to the main screen.6. Click EF as the application type and then click Condition records.


7. Double-click the output type MAHN and click Purchasing Output Determination: Purch.Org/Vendor for EDI.

8. Press Enter to retain the values for the purchase organization and vendor.9. Click the button Execute and maintain the following parameters for the vendor:

○ Vendor Number-1000 (for example)○ Partner Function-VN○ Partner Number-1000 (for example)○ Medium-6 EDI○ Date/Time-4 (when the application is saved)

10. Save the entry.11. If you select the output type AUFB , perform step 5 through step 8.12. Save the entry and return to the main screen.13. Click EF as the application type and then click Output Types.14. Double-click the output type MAHN (Dunning) B.

A new screen appears.15. In the tab General Data, check Access to conditions: and Multiple issuing.16. Double-click Processing Routines and maintain the following parameters:

○ Medium-6 EDI○ Program-RSNASTED○ FORM routine-EDI_PROCESSING

6.12.4 How to implement a custom exit for the order inquiries function module

Context

The function module /ARBA/ORDENQ_DETAILS is called from a custom exit MM06E001 - this is the user exit for EDI inbound and outbound purchasing documents. You must execute the following steps to implement a custom exit. This function module helps in picking up additional inquiry details.

Procedure

1. In SAP ERP, navigate to the transaction code CMOD. Create a new custom exit. For example, ZOR.

2. Click Create.3. Click the Enhancement Assignments button and then enter the user exit name MM06E001.

4. Click Enter.5. Go back and click the Components button and then double-click the enhancement name

EXIT_SAPLEINM_002.



6. In the new screen that appears, double-click INCLUDE ZXM06U02 and click Enter.7. Copy and paste the following code:

CALL FUNCTION '/ARBA/ORDENQ_DETAILS EXPORTINGxekko = xekkoxlfa1 = xlfa1xlfb1 = xlfb1dobject = dobjectTABLESint_edidd = int_ediddxekpo = xekpoxeket = xeketdekek_x = dekek_xdekeh = dekehdsadr = dsadrdvbak = dvbakdvbap = dvbap dvbkd = dvbkd

8. Click the Activate button.9. Go back and activate the user exit also.

6.12.5 Support for additional cXML fields

The standard IDOC /ARIBA/ORDENQ allows you to send additional information on inquiries to Ariba Network.

The following segments store information as specified:

● /ARBA/ORDENQHEADER: Stores additional header-level details sent in the OrderStatusRequestHeader.● ZARIBA_ORDENQ_HEADER_EXT: Stores customized fields at the header-level sent in the

OrderStatusRequestHeader.● /ARBA/ORDENQDETAIL: Stores additional information on line items sent in the

OrderStatusRequestItem. The reminder level information is stored here.● /ARBA/ORDENQ_COMMENTS: Stores the comments sent in the OrderStatusRequestItem.● ZARIBA_ORDENQ_DETAIL_EXT: Stores customized fields at the line item-level sent in the

OrderStatusRequestItem.● Mapping changes have been done in the IDOC to support the additional inquiry fields in the

OrderStaturRequest cXML document, MM_ORDERS_ORDENQ_ARBA_2_CDF_FulFill_XSD.To customize fields, use the MM_Custom_ORDERS_ORDENQ_ARBA_2_CDF_FulFill_XSD mapping file.

6.13 Topics about configuring scheduling agreement releases

Configuring SAP IDOC for scheduling agreement releases [page 266]

How to configure the partner profile for scheduling agreement releases [page 266]

How to maintain condition records for scheduling agreement releases [page 267]


How to implement a custom exit for scheduling agreement releases [page 268]

Support for additional cXML fields [page 269]

Configuring IDOC metadata (optional) [page 269]

6.13.1 Configuring SAP IDOC for scheduling agreement releases

The following SAP IDOC configuration is required for using the sample data mapping:

Transaction IDOC Basic Type Message Type

ScheduleAgreementReleaseRequest DELFOR02 DELINS

6.13.2 How to configure the partner profile for scheduling agreement releases

Procedure

1. Log in to SAP ERP and navigate to transaction WE20 to create a partner profile for a vendor.

2. Expand the Partner type LI (Vendor) and choose the vendor that you want to configure the partner profile for.

3. In the Outbound parameters table, click the Add button and enter the following values:

○ Receiver Port: Configure the SAP Process Integration that sends the scheduling agreement release○ Partner Number: Corresponding Partner Number○ Partner Type: LI○ Partner Role: VN○ Message Type: DELINS○ Receiver Port: Enter the SAP Process Integration Receiver Port○ Basic Type: DELFOR02○ Extension: /ARBA/DELFOR02

4. On the Message control tab, enter the following:

Scenario Application Message Type Process Code Change Indicator

SAR LPA (Release) - Forecast

EL LPH1 ME14 Blank

SAR LPA (Release) - Forecast

EL LPH1 ME14 x

SAR LPA (Release) - JIT

EL LPJ1 ME13 Blank



Scenario Application Message Type Process Code Change Indicator

SAR LPA (Release) - JIT

EL LPJ1 ME13 x

SAR LP EL LPET ME13/ME14 Blank

SAR LP EL LPET ME13/ME14 x

5. Choose Trigger immediately as the value for the Processing by Function Module parameter, if you want real time processing.

6. Save your entries.

6.13.3 How to maintain condition records for scheduling agreement releases

Procedure

1. Log in to SAP ERP and navigate to transaction NACE, select application EL Purch. SchAgrReleaseEntry and click Condition records.

2. Click EL as the application type and then click relevant output type.3. Double-click the output type: LPH1 and LPJ1(Forecast and JIT)4. Click the Default Values tab and preserve the following values in the tab:

○ Despatch time: Send with Application own transaction○ Transaction Medium: EDI○ Partner function: VN

5. Click on Condition records.6. Double-click the LPH1 output type and click Purchasing Output Determination: Purch.Org/Vendor for

EDI.7. Press Enter. Preserve the values for the purchase organization and vendor.8. Click the Execute button and maintain the following parameters for the vendor:

○ Document Type - NB (for example)○ Partner Function - VN○ Partner Number - 1000 (for example)○ Medium - 8 (Special Function)○ Date/Time - 4 (when the application is saved)

9. Save the entry.10. Perform step 6 through step 9 with output type LPJ1 for the JIT Delivery Schedule.


6.13.4 How to implement a custom exit for scheduling agreement releases

Context

The function module /ARBA/SARRELEASE is called from a custom exit MM06E001, that is the user exit for EDI inbound and outbound purchasing documents. You must execute the following steps to implement a custom exit. This function module helps in picking up additional scheduling agreement release details.

Procedure

1. Run the transaction code CMOD in SAP ERP. Create a new custom exit. For example, ZSAR.

2. Click Create.3. Click the button Enhancement Assignments and then enter the user exit name MM06E001. Click Enter.

4. Go back and click the button Components and then double-click the following enhancement names:

○ For Forecast Schedule: EXIT_SAPLEINM_019 INCLUDE ZXM06U59○ For JIT Schedule: EXIT_SAPLEINM_020 INCLUDE ZXM06U60

5. In the new screen that appears, double-click the appropriate Include indicated in Step 4 and click Enter.6. Copy and paste the following code: CALL FUNCTION '/ARBA/SARELEASE'EXPORTINGdekko = dekkodpekko = dpekkocontrol_record_out = control_record_outdobject = dobjectdlfa1 = dlfa1dlfb1 = dlfb1TABLESdekpo = dekpodpekpo = dpekpodeket = deketdekek_x = dekek_xdekeh = dekehdesll = desll dint_edidd = dint_edidd.

7. Click the button Activate.8. Go back and activate the user exit also.



6.13.5 Support for additional cXML fields

The existing IDOC DELINS.DELFOR02 has been enhanced to send additional cXML fields for the Forecast Delivery Schedule or JIT Delivery Schedule information to Ariba Network. You can use the following IDOC segments to support these additional cXML fields:

● To send additional header fields (vendor address and company code address details) to Ariba Network:/ARBA/SARHEADER IDoc: Additional Header data

● To send additional line item details:○ /ARBA/SARDETAIL IDoc: Additional item data○ /ARBA/ACCOUNT IDoc: Accounting details (price unit, account category, and material group)

You can use the following customized IDOC segment to send any additional cXML fields:

● To send additional header fields to Ariba Network, customize the following segment:ZARIBA_SARHEADER_EXT IDoc: Schedule Agreement Release Header

● To send item details, customize the following segment:ZARIBA_SARDETAIL_EXT IDoc: Schedule Agreement Release Item

6.13.6 Configuring IDOC metadata (optional)

This procedure allows you to preload the metadata of the IDOC documents exchanged by the IDOC adapter during configuration. This is optional; if you skip it, the metadata information is 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 SAP ERP in SAP Process Integration. Refer to the transaction IDX2. Check the IDOC Metadata in Metadata Overview for the IDOC Adapter to see if all the inbound IDOC DELFOR02, is available. If they are not, click MetadataCreate to add the same.

6.14 Configuring ship notices against multiple purchase orders

How to configure the ship notice integration scenario to receive ship notices with zero quantities [page 270]

How to configure the SAP IDOC for ship notices against multiple purchase orders [page 270]

How to configure the partner profile or ship notices against multiple purchase orders [page 271]

Related Information

Configuring returns and corrections in receipts [page 272]


6.14.1 How to configure the ship notice integration scenario to receive ship notices with zero quantities

Procedure

1. Log in to SAP ERP and navigate to transaction 0vlp.

2. Click Position and then enter ELN as the Item category.

3. Double-click the Item category ELN. The Checks for zero quantity window appears.

4. Choose the No dialog option.

6.14.2 How to configure the SAP IDOC for ship notices against multiple purchase orders

Context

The following SAP IDoc configuration is required for using the sample data mapping:

Transaction IDoc Basic Type Message Type

Ship Notice DELVRY06 DESADV

Procedure

1. Log in to SAP ERP and navigate to transaction SM59 to create an RFC destination of type ERP.

2. Enter Target host, System Number, Gateway host, Gateway 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 How to configure the SAP IDOC for ship notices against

multiple purchase orders [page 270] details, and then save your entries.



6.14.3 How to configure the partner profile or ship notices against multiple purchase orders

Procedure

1. Log in to SAP ERP and navigate to 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 Type, Agent, and Lang. Save your

entries.4. Click Create inbound parameter (the green plus sign).5. Enter Partner Role, Message type, and Process code.6. Save your entries.7. Configure Advance Ship Notice with the following inbound parameters:

Parameter Value

Partner function VN

Message type DESADV

Process Code DELS

8. Choose Trigger immediately as the value for the Processing by Function Module parameter, if you want real time processing and then check the Cancel Processing After Syntax Error checkbox.

9. Use the transaction BD67 to assign the process code DELS to the function module IDOC_INPUT_DESADV1.

10. Use the transaction WE57 to assign the function module to the logical message and IDOC Type. To do this, click New Entries and enter the following values:

Results

Parameter Value

Function module IDOC_INPUT_DESADV1

Function type Function Module

Basic Type DELVRY06

Message Type DESADV

Object Type BUS2015

Direction Inbound

Description Delivery:Shipping notification

Name Inbound delivery


6.15 Configuring returns and corrections in receipts

Configuring the receipt transaction to support returns and correction on your SAP ERP system involves the following steps:

● Installing the transports for the receipt transaction. For more information, see How to import the design package [page 70].

● Configuring parameters in the ARBA/PARAM_TAB table. For more information, see Configuring Parameters in the ARBA/PARAM_TAB Table for Returns and Corrections in Receipts [page 272].

● Maintaining condition records for returns and corrections in receipts. For more information, see How to maintain condition records for returns and corrections in receipts [page 273].

● Maintaining default values for the printer. For more information, see How to maintain printer default values for returns and corrections in receipts [page 274].

For more information on sending and receiving corrections and returns in receipts, see Receipt Integration Scenario for Corrections and Returns in Receipts [page 126].

Related Information

Canceling MIRO Invoices [page 275]

6.15.1 Configuring parameters in the ARBA/PARAM_TAB table for returns and corrections in receipts

Ensure that you maintain the following values for the parameters in the ARBA/PRAM_TAB table using the Transaction code SM30:

Variable Name Field Name NumberINCL/EXCL Option Selection Value

GOODSRECEIPT

RECEIPT_MVT 1 I EQ Can be left blank or you can specify the following movement types: 101, 103, 104.

To specify another movement type, create the same variable and field name in another row and increment the Number value to 2. For example, you currently have the Selection Value as 101. To create the 103 movement type, create another row containing the same values, but increment the Number value to 2.



Variable Name Field Name NumberINCL/EXCL Option Selection Value

GOODSRECEIPT

RECEIPT_MVT_REVERSAL

1 I EQ Can be left blank or you can specify the 102 movement type.

GOODSRECEIPT

RETURN_MVT 1 I EQ Can be left blank or you can specify the following movement types: 122, 124, 161.

To specify another movement type, create the same variable and field name in another row and increment the Number value to 2. For example, you currently have the Selection Value as 122. To create the 124 movement type, create another row containing the same values, but increment the Number value to 2.

GOODSRECEIPT

RETURN_MVT_REVERSAL

1 I EQ Specify the 123 movement type.

Note● You can leave the Selection Value field blank or specify a particular movement type. If you leave the

value blank, the ERP system associates the 101, 102, 122, and 123 movement types as the default values for fields maintained for the GoodReceipt variable.

● If you enter a specific movement type in the Selection Value field, only this particular movement type is considered while processing receipts containing returns and corrections.

6.15.2 How to maintain condition records for returns and corrections in receipts

Procedure

1. Run the transaction code NACE, choose application ME Inventory Management and click Condition records.

2. Click ME as the application type and then choose WE03 as the output type.A new screen appears.3. Double-click the output type: WE03.

A new screen appears.4. Click the tab Default Values and retain the following values in the tab:

○ Trans./Event Type: WE○ In the Print Version, choose one of the following values:

○ 1 Individual Slip


○ 2 Indiv. Slip w Inspect Text

○ 3 Collective Slip○ Partner function: Enter the partner number of the sender system.

NoteThe option Print Version you choose in the tab Default Values must match the value you choose in the screen MIGO. For example, if you have selected 1 Individual Slip as the option Print Version in the tab Default Values , you must select the same 1 Individual Slip in the screen MIGO.

5. Click the tab Default Values and retain the following values in the tab:

○ Despatch time: 4 Send immediately (when saving the application)○ Transmission Medium: 8 Special function○ Partner function: LS

6. Save the entries and go back to the main screen.7. From the main screen, choose ME Inventory Management and click Output Types.

The Display View "Output Types": Overview screen appears.8. Choose WE03 and double-click Processing routines and enter the following values:

○ Program: /ARBA/RECEIPT_PUBLISH

NoteThis program uses NACE configuration to publish the receipts in real-time.

○ FORM routine: SEND_GOODSRECIPT_SAVED9. Press Enter.10. Click the button Execute and maintain the following parameters for the partner function:

○ Function-LS○ Medium-8 (Special Function)○ Description-Logical system

11. Save the entry.

6.15.3 How to maintain printer default values for returns and corrections in receipts

Procedure

1. Go to the Transaction code MIGO and MB01.

2. In the General tab, from the pulldown choose 3 Collective Slip for the printer.3. Go to the Transaction code SU3.

4. Click the Parameters tab and add the following entry for the user:

○ Parameter ID - NDR



○ Parameter Value - X5. Save the entry.

6.16 Canceling MIRO Invoices

Context

In some cases, you might want to cancel or reverse an invoice sent through MIRO that has already been sent to a supplier. To do this, you must cancel the MIRO invoice and its accounting documents. If you cancel only the MIRO invoice and run the ISU scheduled task, the ISU processes the MIRO invoice, but returns the status as “Processing” as the accounting-related documents still exists for the MIRO task.

Procedure

1. Cancel the MIRO invoice in the T-code MR8M.

2. Cancel the accounting documents associated to the MIRO invoice in the T-Code F-44.

3. Run the ISU scheduled task.

Results

The ISU scheduled task picks up the MIRO invoices with the status as “Canceled” and sends it to the supplier.

Related Information

Topics about configuring invoice status updates [page 275]

6.17 Topics about configuring invoice status updates

Invoice status update transaction [page 276]

How to configure the invoice status update transaction on your SAP ERP [page 278]

About enabling customization of invoice status updates from SAP ERP to Ariba Network for invoices in an approval workflow [page 278]


6.17.1 Invoice status update transaction

The Invoice Status Update transaction processes invoices that are processed, paid, reconciled, rejected, canceled, parked, or parked invoices that have been deleted on SAP ERP. The Business Transaction Events (BTE) has been created to process invoices created, changed, reversed, canceled, parked, parked invoices that have been deleted, or when payments are received on SAP ERP.

Prerequisites

● All parameters required for Invoice Status Update should be maintained in the table /ARBA/PARAM_TAB. For information on the parameters, see Configuration parameters and their corresponding values for invoices in the table /ARBA/PARAM_TAB [page 228] and Additional configuration parameters and their corresponding values for invoices in the table /ARBA/PARAM_TAB [page 229].

● The Invoice Status Update transaction requires the same parameters that are applicable for the ISU batch program on your SAP ERP.

NoteThe program Invoice Status Update (/ARBA/BTE_INVSTATUPDT_EXPORT) cannot be used along with the earlier version of the Invoice Status Update batch program (BTE_INVOICESTATUSUPDATE. Buyers can only use one of the programs for invoice transactions.

Limitations

Ariba Network adapter for SAP NetWeaver does not support processing of the MM and FI invoices that have been created on SAP ERP and have been parked.

The Invoice Status Update transaction contains the following:

● A Business Transaction Events (BTE) has been associated to the 00005010 process module to send the statuses of invoices each time there is an update to invoices on SAP ERP. The BTE function module is activated when the invoices are created, paid (partial or full payment), reconciled, rejected, canceled, parked, parked invoices that have been deleted.

When the function module is run, the Invoice Status Update transaction picks up invoices only for the document types maintained in the table /ARBA/PARAM_TAB. The following document types must be maintained in the table ARBA/PARAM_TAB:

● INVOICE_DOC_TYPE● INVOICE_DOC_TYPE_FULL_AUTO● INVOICE_DOC_TYPE_FULL_MANUAL● INVOICE_DOC_TYPE_PARTIAL

● The Invoice Status Update transaction requires the same parameters that you set for the ISU batch program on your SAP ERP:

● The table /ARBA/AN_ISUINV stores information on the invoices are ready to be sent to Ariba Network.



● The function module /ARBA/BTE_INVOICESTATUSUPDATE processes invoices created or received on SAP ERP.

● The BTE does not require the /ARBA/RFC authorization object. However, this authentication object is required when the /ARBA/BTE_INVSTATUPDT_EXPORT program runs the report containing the records to be sent to Ariba Network. The authorization object contains the following details:○ Object Name: /ARBA/RFC○ Description: Ariba Network Adapter Authorization Object○ Authorization Class: /ARB or existing class.

Authorization Fields

● RFC_TYPE: Type of RFC object to be protected● RFC_NAME: Name of RFC to be protected

● If you maintain the AVOID_DUPLICATE_ISU_PP parameter and the BTE is triggered, the Ariba Network adapter for SAP NetWeaver picks up the invoices only when the ZLSPR – Payment Block Key field values have been changed:

NoteThe ISU transaction does not use the GRACE_TIME_ISU_PP parameter.

● If the INVOICE_DOC_OPTION parameter is maintained in /ARBA/PARAM_TAB, then Ariba Network adapter for SAP NetWeaver sends the Reference Document number (XBLNR) as the invoiceID to Ariba Network.

If you do not maintain this parameter, then the Ariba Network adapter for SAP NetWeaver sends the invoice document number as the invoiceID to Ariba Network.

● If you maintain the ERP_INV_PROCESSED_STATUS parameter, the Ariba Network adapter for SAP NetWeaver stores the invoices that are sent to Ariba Network in the /ARBA/AN_ERPINV table.

● The Business AddIn (BADI) /ARBA/BTE_ISU_UPDATE is available in the BTE. The following are the available methods:

BADI Method Description

CHANGE_PROCESS_BSIK Allows you to customize the existing structure details.

CHANGE_PROCESS_BSAK Allows you to customize the existing structure details.

CHANGE_PARTIALPAID Allows you to modify the details for partially paid invoices.

CHANGE_ISU_STATUS Allows you to modify the status updates for invoices.

CHANGE_INSERTTABLE Allows you to modify the inserted details in the invoice status update table.

CHECK_CHANGED Allows you to modify the flag for check changes.

CHANGE_REJECTED Allows you to modify the rejected invoices.

CHANGE_PARKED Allows you to modify the parked invoices.

NoteFor a PO-based invoice, the Cancelled status is set based on the MM invoices. SAP ERP notifies users when an invoice is cancelled through the message MR8M, Please manually clear F1 document. Users must ensure that they clear the FI documents using F-44. If the FI documents remain, Ariba Network


adapter for SAP NetWeaver sends all corresponding documents (payment proposal, remittances) associated to the cancelled MM invoice to Ariba Network.

Related Information

Invoice status update [page 45]

6.17.2 How to configure the invoice status update transaction on your SAP ERP

Context

Ensure that you import the necessary SAP transport requests into your SAP ERP.

Procedure


2. Click Environment Infosystem(Processes)3. Click Execute.

The Process Module 00005010 appears on the page Business Transaction Events: Process Interface.


5. Click Settings Products ...of a customer .6. Enter a new product name and description. The function module product name must start with /ARBA/.

7. Check Active.

8. Go back to the previous page and click Settings Process Modules ...of a customer .9. For the process module 00005010, specify the newly created function module. The function module must

start with /ARBA/. For example, /ARBA/BTE_INVSTATUPDT_EXPORT. Specify the product /ARBA/IS.


6.17.3 About enabling customization of invoice status updates from SAP ERP to Ariba Network for invoices in an approval workflow

The following BAdI enables buyers to customize invoice status updates sent from SAP ERP to Ariba Network for invoices in an approval workflow application such as OpenText:



● BAdI: /ARBA/BTE_ISU_UPDATE● Method: PUBLISH_BEFORE_SEND

The following graphic illustrates the flow for customizing invoice status updates from SAP ERP to Ariba Network:

6.18 Configuring service sheets

Buyers must configure their SAP ERP system to process service sheets created for purchase orders containing service type items.

How to implement customer exits for invoices with service type line items [page 280]

How to specify time-out intervals for processing service sheets [page 281]

How to implement enhancements for service sheets created for new purchase orders [page 282]

How to implement enhancements for service sheets created for changed or canceled purchase orders [page 283]

Implementing enhancements for revoking previously accepted service sheets [page 284]


6.18.1 How to implement customer exits for invoices with service type line items

Context

Add customer exits to invoices with service type line items to make specific integration requirements.

Procedure

1. Log in to SAP ERP and navigate to transaction CMOD.

2. Create an SAP Enhancement project. For example, ZMRMH. If you already have an existing SAP project for enhancement MRMH0002, use the same project.

○ Click Create.○ Enter a description in the Short Text field.

3. Click Enhancement assignments. The Create Object Directory Entry screen appears.4. Choose the package.5. Save the changes. The SAP Enhancements in Enhancement Project page <object name> appears.6. Enter MRMH0002 in the Enhancement text box and then press Enter.

7. Click Components.8. Double-click EXIT_SAPLMRMH_011. The program INCLUDE - ZXM08U22 appears.9. Double-click INCLUDE - ZXM08U22 in the Function Builder: Display EXIT_SAPLMRMH_011 page to

create the program.10. Enter the following code in the program INCLUDE - ZXM08U22:

Source Code

DATA: lo_badi TYPE REF TO /arba/cl_ses_inv_hierarchy. CREATE OBJECT lo_badi.lo_badi->modify_idoc_data(EXPORTINGi_bukrs = i_bukrsi_lifnr = i_lifnri_idoc_contrl = i_idoc_contrlIMPORTINGe_bukrs = e_bukrse_lifnr = e_lifnre_change = e_changeCHANGINGt_idoc_data = t_idoc_data[] ).

11. Repeat step 7 tthrough step 10 to create the customer exit for EXIT_SAPLMRMH_015.

12. Enter the following code in the program INCLUDE-ZXM08U26:

Source Code

DATA: lo_badi TYPE REF TO /arba/cl_ses_inv_hierarchy. CREATE OBJECT lo_badi.



lo_badi->modify_frseg(CHANGINGt_frseg = t_frseg[]t_co = t_co[]t_ma = t_ma[]e_rbkpv = e_rbkpve_change = e_change ).

13. Save the entries.14. Click the Activate button to go back to the CMOD screen.15. Activate the customer exit in the CMOD screen.

6.18.2 How to specify time-out intervals for processing service sheets

Context

In some cases, the SAP ERP system fails while processing multiple service sheets for the same purchase order service type item. To prevent failures while processing multiple service sheets, Ariba recommends that you specify a time-out duration. This time-out duration ensures that no resources stay locked on the SAP ERP system. Specify the time-out duration by adding the parameter to the /ARBA/PARAM_TAB table.

Procedure

1. Go to Transaction SM30.

2. Go to the /ARBA/PARAM_TAB table.

3. Maintain the following values in the /ARBA/PARAM_TAB table:

○ Variable Name : /ARBA/ENTRYSHEET_CREATE○ Field Name : TIMEOUT○ Number : 0○ INCL/EXCL : I○ Option : EQ○ Selection Value: 100

NoteThis value depends on the time-out value required by the customer.


6.18.3 How to implement enhancements for service sheets created for new purchase orders

Context

To send statuses for service sheets created against new purchase orders to Ariba Network, you must implement the following enhancement:

Procedure

1. Go to transaction SE37.

2. Enter the program name, IDOC_OUTPUT_ORDERS and click Display.

The Function Builder: Display IDOC_OUTPUT_ORDERS page appears.3. Go to the function Perform fill_srv_orders.

4. Double-click the function, Perform.5. Choose the SAPLEINM program in the Choose Main Program for LEINMF0Q page and click Choose.

The ABAP Editor:Display Include LEINMF0Q page appears.6. Click the Enhance button on the application toolbar.7. On the Edit menu, click Enhancement Operations and then click Show Implicit Enhancement Options.8. Right-click on the line below the text FORM fill_srv_orders:, click Enhancement Implementation and

then click Create.9. Click Code on the Choose Enhancement Mode page.

The Select or Create Enhancement Implementation page appears.10. Click the Create enhancement implementation button.

The Create Enhancement Implementation page appears.11. If you already have a custom enhancement, you can use the same custom enhancement. Or you can create

a new enhancement implementation. Enter a name and description. For example, zcanceled_po.

12. Press Enter. The Package page appears.13. Specify the Z or Y package and press Enter to save it to a transport request.

14. Copy and paste the following code in the Enhancement Implementation for the Class for the create purchase order interface:

Source Code

DATA: l_flag(5) TYPE c, cl_purchaseorder TYPE REF TO /arba/cl_purchaseorder, cl_po_hierarchy TYPE REF TO /arba/cl_po_hierarchy, ls_idoc_status TYPE bdidocstat, lx_appl_idoc TYPE REF TO /arba/cx_appl_idoc. CONSTANTS: c_true TYPE char4 VALUE 'true', c_false(5) TYPE c VALUE 'false'.



CREATE OBJECT cl_purchaseorder. CREATE OBJECT cl_po_hierarchy. TRY. CREATE OBJECT cl_po_hierarchy. CALL METHOD cl_po_hierarchy->get_systemversion_ishierarchy EXPORTING ebeln = ekpo-ebeln et_edi_esll = edi_esll[] IMPORTING flag = l_flag CHANGING int_edidd = int_edidd[]. CATCH /arba/cx_appl_idoc INTO lx_appl_idoc. MESSAGE e151(/arba/message) RAISING error_message_received. RETURN. ENDTRY. IF l_flag EQ c_true. CALL METHOD cl_purchaseorder->fill_service_line_number EXPORTING packno = ekpo-packno IMPORTING et_edi_esll = edi_esll[]. ENDIF.

15. Right-click on the line below the text FORM fill_srv_orders:, click Enhancement Implementation and then click Create.

16. Click Code on the Choose Enhancement Mode page.

The Select or Create Enhancement Implementation page appears.17. Select the already created enhancement implementation that you created in Step 13.18. Copy and paste the following code in the Enhancement Implementation for the Class for the create

purchase order interface:

Source Code

if l_flag EQ c_true. CALL METHOD CL_PURCHASEORDER->CREATE_PARENT_CHILD_RELATION EXPORTING EDI_ESLL = edi_esll[] CHANGING INT_EDIDD = int_edidd[] .endif.

19. Activate the code.

6.18.4 How to implement enhancements for service sheets created for changed or canceled purchase orders

Context

To send statuses for service sheets created against purchase orders that have been changed or canceled to Ariba Network, you must implement the following enhancement.


Procedure

1. Go to transaction SE38.

2. Enter the program name, LEINMF0Q and click Display.

3. Choose the SAPLEINM program in the Choose Main Program for LEINMF0Q page and click Choose.

The ABAP Editor:Display Include LEINMF0Q page appears.4. Click the Enhance button on the application toolbar.5. On the Edit menu, click Enhancement Operations and then click Show Implicit Enhancement Options.6. Right-click on the line below the text FORM lesen_beleg:, click Enhancement Implementation and then

click Create.7. Click Code on the Choose Enhancement Mode page.

The Select or Create Enhancement Implementation page appears.8. Click the Create enhancement implementation button.

The Create Enhancement Implementation page appears.9. If you already have a custom enhancement, you can use the same custom enhancement. Or you can create

a new enhancement implementation. Enter a name and description. For example, zcanceled_po.

10. Press Enter. The Package page appears.11. Specify the Z or Y package and press Enter to save it to a transport request.

12. Copy and paste the following code in the Enhancement Implementation for the Class for the Change or Cancel interface:

Source Code


13. Activate the code.

6.18.5 Implementing enhancements for revoking previously accepted service sheets

SAP ERP buyers revoking previously accepted service sheets in SAP ERP need to import the latest transports and enhance the SAP standard function module MS_UPDATE_SERVICE_ENTRY to ensure that the:

● status of service sheets on the Ariba Network changes to Sent.● cXML payload in the Ariba Network adapter for SAP NetWeaver indicates the status as Processing.

Buyer administrators must implement the following code as an implicit enhancement at the end of the SAP standard function module MS_UPDATE_SERVICE_ENTRY:

DATA: cl_SENTRYSHEET_RESPONSE TYPE REF TO /arba/CL_SENTRYSHEET_RESPONSE.



DATA: ls_xessr TYPE uessr, ls_yessr type uessr.CREATE OBJECT cl_SENTRYSHEET_RESPONSE.READ TABLE xessr[] INTO ls_xessr INDEX 1.READ TABLE yessr[] INTO ls_yessr INDEX 1.CALL METHOD cl_sentrysheet_response->call_sesresponse_callproxy EXPORTING is_xessr = ls_xessr is_yessr = ls_yessr

NoteIf the Ariba Network service sheet number contains alphabets, SAP ERP buyers must use capital letters for the alphabets when providing the value on the Ariba Network.

6.19 Direct invoicing of purchase order service items

Buyers can directly invoice a purchase order having the service type items. The Ariba Network adapter for SAP NetWeaver supports integration of the service sheets auto-generated on Ariba Network for the invoice containing service type line items created by the supplier and sent to the SAP ERP system.

Ariba Network adapter for SAP NetWeaver processes invoices with service type line items created against purchase orders sent from Ariba Network as follows:

● Supplier create an invoice with service type line items against purchase orders.● Ariba Network auto generates a service sheet for the invoice with service type line items. The service sheet

is then sent to the SAP ERP system.● The invoice is kept on hold as Pending Approval on Ariba Network until the auto-generated service sheet

for the invoice containing service type line items is approved on the SAP ERP system.● Once the service sheet is approved on the SAP ERP system, the approved status is sent to Ariba Network.

The invoice is added to the pending queue and can be downloaded.● The Ariba Network adapter for SAP NetWeaver downloads these stored invoices with service type line

items from Ariba Networkand sends them to the SAP ERP system.

● Although the invoice for the service sheets contains taxes and other charges, Ariba Network adapter for SAP NetWeaver does not process the taxes in the service sheets.The following customer exits support auto-generated service sheets for invoices containing service type line items:○ EXIT_SAPLMRMH_011○ EXIT_SAPLMRMH_015

For more information on customer exits, see How to implement customer exits for invoices with service type line items [page 280].Customers can implement the following methods for service sheets:○ Class /ARBA/CL_SES_INV_HIERARCHY contains the following methods:

○ MODIFY_IDOC_DATA – Use this method to modify the IDoc data container in the specific format.○ MODIFY_FRSEG – Use this method to modify FRSEG-WRBTR(Amount) in the invoice line item table.


Related Information

How to maintain posting keys to process canceled invoices and credit memos [page 286]

6.20 How to maintain posting keys to process canceled invoices and credit memos

Context

The posting keys are applicable to customer using SAP Ariba cloud integration release 9.0 and higher.SAP Ariba recommends that you maintain the following parameter for posting keys for invoices and credit memos that have the same document types.

Procedure

1. Run the Transaction code SM30.

2. Go to /ARBA/PARAM_TAB table. Click Maintain.

3. Click New Entries.4. Maintain the following values for vendor invoices:

○ Variable Name: INVOICE_POSTING_KEY○ Field Name Number: 0○ INCL/EXCL: I○ Option: EQ○ Selection value: Enter the posting key for FI invoices. For example, 31.

5. Maintain the following values for credit memos:

○ Variable Name: INVOICE_POSTING_KEY○ Field Name Number: 0○ INCL/EXCL: I○ Option: EQ○ Selection value: Enter the posting key for credit memos. For example, 21.

Related Information

Configuring ERP-initiated invoices to use the IDOC [page 287]



6.21 Configuring ERP-initiated invoices to use the IDOC

Configure your SAP ERP system to use the GSVERF03 IDOC to send MM invoices and the FIDCCP02 IDOC to send FI invoices.

NoteYou must maintain the tax code for MM invoices in the /ARBA/TAXCAT_MAP table to process the tax values in the invoices correctly. If the tax code does not exist in the /ARBA/TAXCAT_MAP table, Ariba Network adapter for SAP NetWeaver does not process the tax code in the MM invoices. The tax code in the invoice that is sent to Ariba Network is blank.

How to configure the NACE setting to send ERS invoices [page 287]

How to configure the NACE setting to send invoicing plans [page 289]

How to configure the NACE setting to send MIRO invoices [page 290]

How to maintain tax categories [page 291]

How to implement the customer exit for MM invoices [page 292]

How to implement routines to prevent creation of duplicate MM IDOCs [page 293]

How to maintain partner profiles [page 294]

How to configure FI Invoices [page 295]

How to set document type filters for FI invoices [page 296]

How to maintain output types for FI invoices [page 297]

How to implement the customer exit for FI invoices [page 298]

How to set filters for invoices from Ariba Network [page 300]

Handling errors [page 300]

Related Information

ERP-initiated invoices using the IDOC transmission method [page 41]Configuring Quote Request and Quote Message documents [page 305]

6.21.1 How to configure the NACE setting to send ERS invoices

Context

Configure the NACE setting to send the ERS (Evaluated Receipt Settlement) invoices using the IDOC.


Procedure


2. Choose application MR and then click Output types.3. Choose ERS Output type for ERS invoices and then click Processing routines.4. Choose INS Output type for Invoice Plan and then click Processing routines.5. Add the EDI entry with the following values:

○ Medium: EDI○ Program: RSNASTED○ FORM routine: EDI_PROCESSING

6. Click Partner functions link and add the following EDI entries:

○ Medium: EDI○ Funct: VN○ Name: Vendor

7. Go back to the NACE transaction and click Condition records.

8. Double-click ERS output type and click CoCode, Vendor to maintain condition records. These values are also applicable for the Invoice Plan output type.

9. Click Execute.10. Enter the following values in the Change Condition Records (ERS Procedure): Fast Change screen:

○ Vendor: 3000 (as an example)○ Name: Name of the vendor○ Funct: VN○ Partner: Vendor number○ Medium: 6○ Date/Time: 4

11. Go to transaction code WE20 to maintain the partner profiles. Maintain the partner profile for the vendor. For example, Vendor 1000.

12. Double-click to expand partner type LI node and then click the vendor. For example, Vendor 1000.13. In the Partner profiles:Outbound parameters screen, maintain the following values:

○ Partner No.: 1000 (as an example)○ Partn. Type: LI○ Partner Role: VN○ Message Type: GSVERF

On the Outbound Options tab, ensure that you maintain the following entries:○ Receiver port:: Enter the name of the receiver port○ Transfer IDoc Immed.: Choose the radio button○ Basic type: GSVERF03○ Extension: /ARBA/ GSVERF03 ○ Cancel Processing After Syntax Error: Check the checkbox

14. In the Partner Profiles screen, maintain the following values:



○ Partner No.: 1000 (as an example)○ Partn. Type: LI

On the Post processing permitted agent tab, maintain the following values:○ Ty.: 0○ Agent: 50010120○ Lang.: EN

In the Outbound parmtrs. section, maintain the following values:

○ Partner Role: VN○ Message Type: GSVERF

15. Go to Message Control tab and maintain the following values:

○ Application: MR : Invoice Verification○ Message Type: ERS : ERS Procedure○ Process code: MRRL: ERS procedure for Logistics invoice verification

Results

This completes the configuration for the ERS invoices.

6.21.2 How to configure the NACE setting to send invoicing plans

Context

Configure the NACE setting to send the Invoicing plans using the IDOC.

Procedure


2. Choose application MR and then click Output types.3. Choose ERS Output type for ERS invoice and then click Processing routines.4. Choose INS Output type for Invoice Plan and then click Processing routines.5. Add the EDI entry with the following values:

○ Medium: EDI○ Program: RSNASTED○ FORM routine: EDI_PROCESSING

6. Click Partner functions link and add the following EDI entries:


○ Medium: EDI○ Funct: VN○ Name: Vendor

7. Go back to the NACE transaction and click Condition records.8. Double-click INS output type and click Company Code/Invoicing to maintain condition records.9. Enter the company code and invoicing party.10. Click Execute.11. Enter the following values in the Change Condition Records (Invoice Plan): Fast Change screen:

○ Company Code: Enter the company code○ Inv. Pty: 1000 (as an example)○ Funct: VN○ Partner: 0000001000○ Medium: 6○ Date/Time: 4

12. Click Execute.13. Go to transaction code WE20 to maintain the partner profiles.

14. Maintain the partner profile for the vendor . For example, Vendor 1000. Double-click to expand partner type LI node and then click the vendor. For example, Vendor 1000.

15. Double-click the GSVERF message type in the Outbound parmtrs. section.16. Click the Message Control tab and add the following values:

○ Application: MR○ Message type: INS○ Process code: MRRL

17. Enter the following values in the Outbound Options tab:

○ Receiver port: Enter the name of the receiver port.○ Pack. Size: 1○ Transfer IDoc Immed.: Choose the radio button.○ Basic type: GSVERF03○ Extension: /ARBA/ GSVERF03○ Cancel Processing After Syntax Error: Check the checkbox.

18. Click Save.

6.21.3 How to configure the NACE setting to send MIRO invoices

Context

Configure the NACE setting to send the MIRO invoices using the IDOC.



Procedure


2. Select application MR and then click Procedures.

The Change View "Procedures": Overview page appears.3. Click MR0002 procedure in the Procedures table and then double-click the Control folder dialog

structure.4. Add the following entries in the Reference Step Overview section on the Change View “Control”:

Overview page:

○ Step: 30○ Counter: 0○ CTyp: ERS○ Description: ERS Procedure

6.21.4 How to maintain tax categories

Context

Maintain the tax code for a single tax category or a tax code with more than one tax category in the /ARBA/TAXCAT_MAP table. When a tax code has more than one tax category, you must also maintain the tax code, tax jurisdiction code, and transaction key for each of the different tax categories. This is required to process tax for ERP-intiated invoices and payment proposals with additional tax information.

Use the TCode FTXP to view the system settings for the tax code, tax jurisdiction, and transaction key. Ensure that the tax values you maintain in the /ARBA/TAXCAT_MAP table is the same as available in the TCode FTXP.

Procedure

1. Go to transaction code SM30.

2. Maintain the following values in the /ARBA/TAXCAT_MAP table. Do one of the following:

○ If you want to maintain the tax code for a single tax category, specify the following values:○ Tax Code: Enter the tax code for the tax category. For example, IJ.○ Tax Category: Enter the tax category for the tax code. For example, pst, gst.

○ If you want to maintain the tax code for more than one tax category, specify the following values:○ Tax Code: Enter the tax code. For example, IJ.○ Tax Jurisdiction: Enter the tax location. For example, CABC.○ Transaction Key: Enter the transaction key associated to the tax code and jurisdiction. For

example, MW2.○ Tax Category: Enter the tax category for the tax code. For example, pst, gst.


NoteEnsure that you enter the value in the Tax Category field in the lower case. Ariba Network cannot process tax categories in the upper case.

6.21.5 How to implement the customer exit for MM invoices

Context

Implement customer exits to make specific integration requirements to the transmission of MM invoices.

Procedure

1. Implement the Customer exit as follows:

○ Go to the transaction code CMOD.○ Enter a name. For example, ZSUSMM1.○ Click Create.○ Enter a description in the Short Text field.

2. Click Enhancement assignments.

The Create Object Directory Entry screen appears.3. Enter the following values:

○ Object: R3IR CMOD 2SUSMM1○ Package: Enter a name.

4. Save the changes.5. Enter MRMN0001 in the Enhancement text box and then click Enter.

6. Click Components.7. Double-click EXIT_SAPLMRMN_001.8. Double-click INCLUDE ZXMRNU01 in the Function Builder: Display EXIT_SAPLMRMN_001 page.9. Enter the following code:

Code Syntax

/arba/cl_invoice_get_details=>invoice_get_details( EXPORTING if_ident = if_ident is_data_ers = is_data_ers is_data_rap = is_data_rap is_data_kons = is_data_kons if_segnam = if_segnam CHANGING ct_idoc_data = ct_idoc_data[] ).



10. Save the entries.11. Click the Activate button to go back to the CMOD screen.12. Activate the customer exit in the CMOD screen.13. To send the XBLNR – reference document number as the Invoice ID to Ariba Network, do the following:

○ Go to transaction code SM30.○ Maintain the following parameter in the /ARBA/PARAM_TAB table.

○ Variable Name: INVOICE_DOC_OPTION○ Field Name: To be left blank○ Number: 0 (zero)○ INCL/EXCL: I○ Option: EQ○ Selection value: XBLNR

14. Save the entries.

6.21.6 How to implement routines to prevent creation of duplicate MM IDOCs

Context

The Ariba Network adapter for SAP NetWeaver creates an FI IDOC each time an FI invoice is created on the SAP ERP system. In some cases, the MM invoices have duplicate IDOCs. To restrict the creation of duplicate MM IDOCs, you must implement a routine.

Procedure

1. Go to Transaction VOFM.

2. On the Requirements menu, click Output control.3. Scroll to the end and go to the routine number field.4. Enter any routing number starting with 9. For example, 904. Customer routines start with the number 9.

5. In the Application field, enter MR and press Enter.

The Register Object page appears where you must enter the access key.6. Ensure that you generate the access key for the routine to enable you to write add the ABAP code. To

generate the access key, register the object in the SSCR (SAP Software Change Registration) by providing the object name.

7. Enter the access key for the object.8. Click Continue.9. Click the routine number in the Maintain: Requirements Output control page and then click the Source

text button on the application tool bar.


10. Press Enter.

A new ABAP editor page appears.11. Copy and paste the following code in the FORM KOBEV_<Routine Number>:

Source Code

DATA: lv_subrc TYPE subrc. /arba/cl_invoice_get_details=>restrict_duplicate_idocs( EXPORTING t683s = t683s komkbmr = komkbmr CHANGING xnast = xnast[] cs_subrc = lv_subrc ). IF lv_subrc IS NOT INITIAL. sy-subrc = lv_subrc. ENDIF.

12. Save the changes and click the Activate button.13. Click the Back button to go back and choose the routine number on the Maintain: Requirements Output

control page.14. On the Edit menu, click Activate to activate the routine.

6.21.7 How to maintain partner profiles

Context

You must maintain the logical system profile for the outbound parameters if you use the IDOCs to process CC Invoices on the SAP ERP system.

Procedure

1. Go to transaction code WE20 to maintain the partner profiles.

2. Double-click to expand Partner type LS node and then click the vendor that you want to maintain for the partner profile.

3. In the Partner profiles: Outbound parameters screen, maintain the following values:

○ Partner No.: Enter the logical system for the SAP ERP system. For example, 1000.○ Partn. Type: LS○ Partner Role: Specify the vendor.○ Message Type: FIDCC2

On the Outbound Options tab, ensure that you maintain the following entries:○ Receiver port: Enter the name of the receiver port.○ Transfer IDoc Immed.: Choose the radio button.



○ Basic type: FIDCCP02○ Extension: /ARBA/ FIDCCP02○ Cancel Processing After Syntax Error: Check the checkbox.

4. Repeat Step 3 for the other Message Type: SYNCH.

6.21.8 How to configure FI Invoices

Context

Add configuration for sending FI invoices using the BD64 transaction. If the FI invoices are getting cleared automatically, please refer to Question 6 of the SAP Note 114814 - ALE FIDCCP01/02: Questions and problems with FI distribution Note.

Procedure

1. Go to transaction BD64.

2. Click the Edit button and then click Create Model View.

The Create Model View screen appears.3. Enter the following values in the Create Model View screen:

○ Short text: Enter a description.○ Technical name: Enter a technical name. For example, ZFI.○ Start date: Specify the start date.○ End Date: Specify the end date.

4. Click Add Message Type.5. Add the FIDCC2 message type and specify the sender and receiver system information.6. Click Continue.7. Go to transaction code WE82 and link the FIDCC2 message type to the /ARBA/FIDCCP02 extension.

8. Go to the transaction code BD82 to generate the partner profile for the FI transaction. Enter the following details:

○ Model View: ZFI○ Partner System: Enter the system port for the partner system.○ Pack. Size: For example, 100 IDocs.

9. Click the Transfer IDoc immediately option in the Output Mode section.10. Click the Trigger Immediately option in the Inb. Parameter section.11. Click Execute.

This creates the FIDCC2 and the SYNCH Message types as the Outbound Parameters at the logical system profile.



Results

Ensure that the outbound parameters at the logical system profile have been created. Verify these changes in the Outbound Options tab. See How to maintain partner profiles [page 294] to create partner profiles.

6.21.9 How to set document type filters for FI invoices

Context

Maintain filters for FI invoices based on the document types. These filters can also be used to process purchase orders that do not have specific document types.

Procedure

1. Go to Transaction BD59.

2. Enter FIDCC2 in the Message Type field and press Enter.

3. Click New Entries.

The New Entries: Overview of Added Entries page appears.4. Add the following segment types. Enter an object name in the ALE Object Type field for each of the

following segment types:

ALE Object Segm. Type No. Field Offset IntLength

Enter a name for the ALE object type. For example, BLART.

E1FIKPF 1 BLART 20 2

Enter a name for the ALE object. For example, BUKRS.

E1FIKPF 1 BUKRS 0 6

Enter a name for the ALE object. For example, ZXREF1_HD.

E1FIKPF 1 XREF1_HD 378 20

5. Save the entries.6. Go to Transaction BD95.

7. Click New Entries.

The New Entries: Overview of Added Entries page appears.8. Add the following entries:



ALE Object Table Name Field Name

Enter the name of the ALE object type. For example, BLART.

BKPF BLART

Enter the name of the ALE object type. For example, BUKRS.

T001 BUKRS_GLOB

Enter the name of the ALE object type. For example, ZXREF1_HD.

BKPF XREF1_HD

9. Save the entries.10. Go to Transaction BD64.

11. Click Edit and go to the model view FI. Click to expand it.12. Double-click the Data filter node.13. Click Create Filter Group. The Filter group displays the Global CoCde, Ref.key (header) 1, and Document

Type filter fields.14. Double-click Global CoCde.15. Click the Add button and add the global company codes for which the IDOC’s must be activated.

NoteIf you maintain the company code instead of the global company code in the Global CoCde filter, the SAP ERP displays a warning message. You can also save the changes. However, if you save the changes, the IDOC does not get generated for any of the FI invoices that you create on the SAP ERP. This is because the data filter specified has the company code entries instead of the global company code.

16. Double-click Ref.key (header) 1.17. Click the Add button and enter ISFIINVOICE in the Filter object type field.

18. Double-click Document Type filter and then click the Add button.19. Add the document types that you want to filter for the FI invoices. For example, KR, KZ, and RE.

20.Click Continue and save the BD64 entries.

6.21.10 How to maintain output types for FI invoices

Context

Maintain the output types that you need for the FI invoices. If you do not maintain the output types in the table /ARBA/PARAM_TAB, Ariba Network adapter for SAP NetWeaver processes the FI invoices with the standard output type as ERS (Evaluated Receipt Settlement) invoices. Ensure that you create the routine before you maintain the output types in the transaction NACE.


Procedure

1. Run the transaction code SM30.

2. In the table /ARBA/PARAM_TAB, maintain the new output types that you require for the FI invoice.

For more information, see Configuration parameters and their corresponding values for invoices in the table /ARBA/PARAM_TAB [page 228] and Additional configuration parameters and their corresponding values for invoices in the table /ARBA/PARAM_TAB [page 229].

3. Run the transaction code NACE.

4. Click Procedures.5. Choose application MR and then click Procedures.

The Change View "Procedures": Overview page appears.6. Click procedure MR0002 in the table Procedures and then double-click the folder dialog structure

Control.

The page Change View “Control”: Overview appears.7. Enter the routine number that you created in the field Requirement for the ERS condition type in the

section Reference Step Overview on the page Change View “Control”: Overview.8. Repeat Step 5. Click the procedure MR0004 and repeat Step 6 and Step 7.

6.21.11 How to implement the customer exit for FI invoices

Context

Implement customer exits to make specific integration requirements to the transmission of FI invoices.

Procedure

1. Implement the customer exit as follows:

○ Go to the transaction code CMOD.○ Enter a name. For example, ZFIDOC.○ Click Create.○ Enter a description in the Short Text field.

2. Click Enhancement assignments.

The Create Object Directory Entry screen appears.3. Click Local Object.4. Enter the following values:

○ Object: R3TR CMOD ZFIDOC○ Package: Enter a name.




The SAP Enhancements in Enhancement Project page <object name> appears.6. Enter F050S004 in the Enhancement text box and then press Enter.

7. Click Components.8. Double-click EXIT_SAPLF050_001.9. Double-click INCLUDE ZX050U01 in the Function Builder: Display EXIT_SAPLF050_001 page.10. Enter the following code:

Code Syntax

CALLMETHOD /arba/cl_invoice_get_details=>fi_get_line_amount EXPORTING message_type = message_type sap_segment_name = sap_segment_name sap_segment_data = sap_segment_data fi_document_header = fi_document_header fi_document_item = fi_document_item CHANGING cust_segment_name = cust_segment_name cust_segment_data = cust_segment_data.

11. Save the entries.12. Click the Activate button to go back to the CMOD screen.13. Double-click EXIT_SAPLF050_007.14. Double-click INCLUDE ZX050U07 in the Function Builder: Display EXIT_SAPLF050_007 page.15. Enter the following code:

Code Syntax

/arba/cl_invoice_get_details=>fi_invoice_get_details( EXPORTING if_message_type = message_type CHANGING ct_idoc_data = idoc_data[] ct_idoc_control = idoc_control cs_boole = distribution ).

16. Save the entries.17. Click the Activate button to go back to the CMOD screen.18. Activate the customer exit in the CMOD screen.19. You must maintain the Ariba tax categories. To maintain tax categories, see How to maintain tax categories

[page 291] .

NoteWhen an IDOC is generated for an FI invoice, the Ariba Network adapter for SAP NetWeaver does not map the Distribution node.


6.21.12 How to set filters for invoices from Ariba Network

Context

The CHECK_ARIBA_ASN parameter is applicable for SAP Ariba cloud integration release 6.0 and higher. This parameter supports filtering invoices from Ariba Network that have ARIBA_ASN in the header field.

Customers using SAP Ariba cloud integration release 5.0 and lower must continue to maintain the ERP_INV_PROCESSED_STATUS parameter for ERP-initiated invoices that belong to suppliers on Ariba Network. In SAP Ariba cloud integration release 6.0 and higher, the ERP_INV_PROCESSED_STATUS parameter and the /ARBA/AN_ERPINV table is no longer applicable for ERP-initiated invoices.

Procedure

1. Run the transaction code SM30.

2. Go to /ARBA/PARAM_TAB table.

3. Maintain the following values:

○ Variable Name: CHECK_ARIBA_ASN○ Field Name : X○ INCL/EXCL: I○ Option: EQ○ Selection value: X

6.21.13 Handling errors

Buyers can use the transaction code SLG1 to view all messages in the application log on the SAP ERP system. Errors that occur while transmitting the MM and FI invoices in the SAP Ariba Buying solutions are stored in the SXMB_MONI if a system error occurs while sending the invoices from the SAP ERP system to the SAP Process Integration.

6.22 Configuring ERP-initiated service entry sheets

To configure ERP-initiated service entry sheets in SAP ERP, perform the following procedures:

How to create an event for the ERP-initiated service entry sheet create and change document [page 301]

How to activate the event type linkages to send ERP-initiated service entry sheets [page 302]

Implementing enhancements to update XBLNR (reference) with the service entry sheet number [page 302]



How to implement implicit enhancements for revoking and rejecting previously accepted service entry sheets [page 303]

How to create an ERP-initiated service entry sheet on SAP ERP [page 304]

6.22.1 How to create an event for the ERP-initiated service entry sheet create and change document

Context

In the SWEC, the document object ENTRYSHEET is assigned to the business object BUS2091.

The following are the options maintained for the create event:

Business Obj. Type Event Select Option

ENTRYSHEET CREATED On Create

ENTRYSHEET CREATED On Change

Perform the following steps to create an event for service entry sheets:

Procedure

1. Run the transaction code SWEC.

The Change View "Event for Change Document”: Overview page appears.2. Click New Entries.

The New Entries: Details of Added Entries page appears.3. Maintain the following entries:

○ Change doc. object: ENTRYSHEET○ Object Category: BO BOR Object Type○ Object Type: BUS2091○ Event: CREATED

4. Select the On Create trigger event.5. Save the changes.

NoteRepeat the steps for the On Change trigger event.


6.22.2 How to activate the event type linkages to send ERP-initiated service entry sheets

Context

Activate the event type linkage required to send ERP-initiated service entry sheets to Ariba Network.

Procedure

1. Run the transaction code SWE2.

The Change View "Event Type Linkages”:Overview page appears.2. Click New Entries.

The New Entries: Details of Added Entries page appears.3. Maintain the following entries:

○ Object Category: BO BOR Object Type○ Object Type: BUS2091○ Event: CREATED○ Receiver Type: CREATED_AN

Linkage Setting (Event Receiver)○ Receiver Call: Function Module○ Receiver Function Module: /ARBA/EXT_EVENT_SES_NOTIF_OUT○ Check Function Module: Leave it blank○ Receiver Type Function Module: Leave it blank○ Destination of Receiver: Leave it blank○ Event delivery: Using tRFC (Default)○ Select Linkage Activated○ Behavior Upon Error Feedback: 0 System defaults○ Receiver Status: 0 No errors


6.22.3 Implementing enhancements to update XBLNR (reference) with the service entry sheet number

The XBLNR field in SAP ERP stores the reference document number, which is the service entry sheet number. The XBLNR field is not populated when a service entry sheet is created on SAP ERP. SAP ERP buyer administrators must implement an implicit enhancement to ensure that the XBLNR field in SAP ERP is updated with the service entry sheet number.

When an invoice is generated on Ariba Network and sent to SAP ERP, the service entry sheet number is validated against the value in the XBLNR field. If the XBLNR field is empty, the invoice is rejected on SAP ERP.



SAP ERP buyer administrators must implement the following code or add the INCLUDE /ARBA/ES_ERPSES_XBLNR_UPDATE as an implicit enhancement at the start of FORM SAVE of the LMLSRF0F standard include.

NoteThe XBLNR field is a free text field on SAP ERP. After implementing this implicit enhancement, any value entered by the user in this field is overwritten with the service entry sheet number.

FORM SAVE. """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(1) Form SAVE, Start A*$*$-Start: (1)---------------------------------------------------------------------------------$*$*ENHANCEMENT 1 ZSES_OUT. "active versionINCLUDE /ARBA/ES_ERPSES_XBLNR_UPDATE.ENDENHANCEMENT.*$*$-End: (1)---------------------------------------------------------------------------------$*$*

6.22.4 How to implement implicit enhancements for revoking and rejecting previously accepted service entry sheets

Context

SAP ERP buyers revoking or rejecting previously accepted service entry sheets in SAP ERP can enhance the SAP standard function module MS_UPDATE_SERVICE_ENTRY to ensure that the status of ERP-initiated service sheets on the Ariba Network changes to Sent.

Procedure


The Customizing: Execute Project screen appears.2. Click SAP Reference IMG.

The Display IMG screen appears.

3. Navigate to Integration with Other SAP Components SAP Ariba Cloud Integration GatewayAriba Network Integration Application Specific Settings ERP-initiated Service Sheet .

4. Click IMG activity for Implement Enhancements for Revoking Previously Accepted ERP Service Sheets.

The Function Builder: Initial Screen appears.


5. Enter MS_UPDATE_SERVICE_ENTRY in Function Module text box and click Display.

6. Click Enhance in the application toolbar.

7. Click Edit Enhancement Operations Show Implicit Enhancement Options .

8. Scroll to the bottom of the page and right-click on the last line, choose Enhancement ImplementationCreate .

9. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation.

10. Click Create Enhancement Implementation.11. Enter a name and description for the enhancement and click Enter.12. In the package popup, specify your Z or Y package, click Enter, and save the package to a transport

request.13. Paste the following code: Include ARBCIG_SES_REVOKE_ENHAN IF FOUND.


6.22.5 How to create an ERP-initiated service entry sheet on SAP ERP

Context

Buyers can create a service entry sheet on SAP ERP using the transaction code ML81N. Search the service purchase order for which you want to create a service sheet and provide the required details. Perform the following steps:

Procedure

1. Run the transaction code ML81N.

The Service Entry Against Purchase Order page appears.2. Click Other Purchase Order.

The Select Purchase Order/Entry Sheet page appears.3. Enter the purchase order number and click Continue.

The Display Entry Sheet page appears.4. Click Create Entry Sheet

The Create Entry Sheet page appears.5. Click the Service Selection button at the bottom of the screen.

The Service Selection page appears.6. Select From Purchase Order and click Continue.

The Select Services as Reference page appears.



7. Click Services and select services.8. Enter the information for the following fields:

○ Short Text○ Quantity

9. Click Accept.10. Click Save.

6.23 Configuring Quote Request and Quote Message documents

Configuring the IDOC transaction for the quote request and quote message on your SAP ERP system involves the following steps:

● Configuring your system for Quote Request documents. For more information, seeConfiguring SAP ERP for Quote Request documents [page 305].

● Configuring your system for Quote Message documents. For more information, see Configuring SAP ERP for Quote Message documents [page 306].

● Configuring the SAP Process Integration. For more information, see Configuring SAP Process Integration [page 308].

Related Information

Configuring payment proposals for taxes and discounts [page 308]

6.23.1 Configuring SAP ERP for Quote Request documents

The following configurations must be made in SAP ERP for Quote Request documents:

● Configure the IDoc Partner Profile. For more information, see IDoc partner profile configuration [page 305].● Activate the Custom Project. For more information, see How to activate the custom project [page 306].

6.23.1.1 IDoc partner profile configuration

IDoc ORDERS05 has been extended as /ARBA/RFQ and includes attachment details and additional data required for mapping. For example, supplier email, and the change RFQ indicator. New SAP Process Integration mapping contents transform the IDoc to a Quote RequestcXML message and the cXML message is sent to the Ariba Network.


The following SAP IDoc configurations are required:

● IDoc Basic Type: ORDERS05● IDoc Extension Type: /ARBA/RFQ● Message Type: REQOTE

Activating the IDoc Extension

To activate IDoc extension, you must create a custom project with Enhancement Assignment MM06E001 and component EXIT_SAPLEINM_002 and then activate the project.

6.23.1.2 How to activate the custom project

Procedure

1. Go to the CMOD transaction code and create a new custom exit. For example, ZRFQ.

2. Click Create.3. Click the Enhancement Assignments button, enter the user exit name MM06E001 and then click Enter.

4. Go back and click the Components button and then double-click the following enhancement name EXIT_SAPLEINM_002.

5. In the new screen that appears, double-click INCLUDE ZXM06U02 and click Enter.6. Copy and paste the following code:

CALL FUNCTION '/ARBA/RFQ_GET_DETAILS' EXPORTINGEKKO = xekkoLFA1 = xlfa1OBJECT = dobjectTABLESINT_EDID = int_ediddINT_EKPO = xekpo

7. Click the Activate button.8. Go back and activate the user exit also.

6.23.2 Configuring SAP ERP for Quote Message documents

To create Quote Message documents, SAP Ariba needs the following information:

● Company Code● Purchase Organization● Material Group



SAP Ariba fetches this information from the RFQ. SAP Ariba pulls account information from the requisition if the RFQ was created with reference to a requisition. If not, SAP Ariba fetches the accounting information from the /ARBA/PARAM_TAB table.

NoteThe accounting logic does not apply if the RFQ has a material number.

RFC / ARIBA/QUOTE

The RFC /ARIBA/QUOTE has been created, which uses BAPI_PO_CREATE1 to create a purchase order for the awarded quote messages. The RFC does the following:

● Defaults missing information in the cXML. For example, purchase organization, company code, purchase group, accounting information from the RFQ.To maintain this parameter, use the transaction code SM30 with the table name /ARBA/PARAM_TAB. The table needs to be maintained as follows:

Variable Name Field Name Number Include / Exclude Option Value

QUOTE ACCTASSCAT 0 I EQ K

QUOTE ASSET 0 I EQ 100

QUOTE COSTCENTER 0 I EQ 0000004120

QUOTE DOC_TYPE 0 I EQ NB

QUOTE GL_ACCOUNT 0 I EQ 0000404000

QUOTE ONETIME_VENDOR

0 I EQ 0000003960

QUOTE ORDER 0 I EQ 23122

QUOTE ORDER_TYPE 0 I EQ NB

QUOTE PLANT 0 I EQ 3000

QUOTE SUB_NUMBER 0 I EQ 44444

QUOTE WBS_ELEMENT 0 I EQ 3423

● Transforms the Quote Message cXML to /ARIBA/QUOTE using the new SAP Process Integration mapping contents.


6.23.3 Configuring SAP Process Integration

The following SAP Process Integration value mappings must be configured for Quote Request and Quote Message documents:

Source Value Target Value Parameter Name Notes

XI_Global XI IsMultiERPModeEnabled Indicates whether multi ERP is enabled or not.

XI_Global XI DefaultLanguageCode Default language.

LANG_ERP LANG_ISO ERP Language code Key value pair of ERP-ISO language map.

RFQ_ERP RFQ_XI RFQDummyVendor Indicates whether a vendor is an “Ariba Marketplace Vendor”.

RFQ_TYPE RFQ_ASN_TYPE ERP’s RFQ document type Key value parameter of ERP doc type with Ariba Network supported doc type - invitationOnly, approvedVendorOnly, public

For more information about Quote Request and Quote Message documents, see Integrating SAP ERP with the Ariba Spot Quote Solution [page 174].

6.24 Configuring payment proposals for taxes and discounts

If you have subscribed to the SAP Ariba Discounting solution, you can send and receive additional tax and discount information in the payment proposals sent for early payment to suppliers on Ariba Network.

Ariba Network adapter for SAP NetWeaver can process the tax discounts given to suppliers in countries that have a liability for the payment of Value-Added Tax (VAT) or in countries that have indirect taxes. Ariba Network adapter for SAP NetWeaver calculates the tax discounted amount on payment proposals marked for early payment based on the tax category and tax location (tax jurisdiction).

The payment proposals that Ariba Network adapter for SAP NetWeaver sends suppliers contain the following details:

● Tax category● Tax location (tax jurisdiction)● Discount Basis amount● Total tax amount for the tax category and tax location● Total tax applicable

Ariba Network adapter for SAP NetWeaver uses the tax category that buyers maintain in the table /ARBA/TAXCAT_MAP on the SAP ERP system while processing the discounts for payment proposals sent for early payment to suppliers. The table /ARBA/TAXCAT_MAP stores the mapping between the tax codes available onAriba Network and ERP system.



When Ariba Network sends an updated payment request containing discounts for invoices with the PST tax category to the SAP ERP system, Ariba Network adapter for SAP NetWeaver additionally calculates the discount based on the PST tax category. The Disc Amount. field for the vendor line item in the invoice on the SAP ERP system includes the discount and tax adjustment amount applicable for the PST tax category. For all other invoices containing discounts, Ariba Network adapter for SAP NetWeaver does not calculates the total discount amount. The value in the Disc Amount. field contains no changes after we receive the updated payment request from Ariba Network.

Ariba Network adapter for SAP NetWeaver sends payment proposals for partially paid invoices to Ariba Network. These payment proposals sent to suppliers contain details of the scheduled payment and the discount amount applicable when payments are made earlier. However Ariba Network does not sends an update to the payment proposal that contains partially paid invoices back to the SAP ERP system.

Ariba Network adapter for SAP NetWeaver derives the tax category information from /ARBA/TAXCAT_MAP table that a buyer maintains on the SAP ERP system. When a buyer has a tax code with more than one tax category, SAP Ariba recommends that you maintain the different tax categories in the /ARBA/TAXCAT_MAP table. Buyers need to also maintain the tax code for a single tax category in the /ARBA/TAXCAT_MAP table.

Ariba Network adapter for SAP NetWeaver uses the configuration that the SAP ERP system maintains for the tax location (tax jurisdiction) while processing the tax information based on the tax category. However, buyers can override this configuration using the BAdI /ARBA/PP_UPDATE provided for the payment proposal. The method, change_pp_tax the BAdI /ARBA/PP_UPDATE allows buyers to override the tax information.

Related Information

How to configure confirmation control keys [page 312]Prerequisites and limitations of configuring payment proposals for taxes and discounts [page 309]Example for payment proposals with discounts [page 310]How to maintain parameters for payment proposals with discounts [page 311]Handling errors [page 311]

6.24.1 Prerequisites and limitations of configuring payment proposals for taxes and discounts

Prerequisites

To process taxes and discounts based on the tax category and tax location, buyers must do the following:

● Maintain the parameter PP_TAX_INFO in the /ARBA/PARAM_TAB table .● Maintain the tax category in the /ARBA/TAXCAT_MAP table when the tax code has one or more than one

tax category. Ensure that you specify the tax category based on the tax code, tax jurisdiction code, and transaction key.

● Configure the tax category on your Ariba Network account. For more information, see the section, Ariba Network Configuration in the Buyer Administration Guide.


NoteEnsure that you maintain the entries required for payment proposals and invoice status updates in the /ARBA/PROXYPARAM, /ARBA/PARAM_TAB and /ARBA/AN_VENDOR tables.

Limitations

● Ariba Network adapter for SAP NetWeaver does not send the values available in the Adjustments Amount field that contains additional charges on the invoice in the payment request sent to Ariba Network.

● On the SAP ERP system, the Disc Amount. field in the invoice includes the discount for an early payment and the tax discount. Ariba Network adapter for SAP NetWeaver does not separate these amounts while running the PayMeNow transaction.

● Ensure that you enter the value in the Tax Category field in the lower case. Ariba Network cannot process tax categories in the upper case.

Related Information

How to maintain parameters for payment proposals with discounts [page 311]How to maintain tax categories [page 291]

6.24.2 Example for payment proposals with discounts

Here is an example how Ariba Network adapter for SAP NetWeaver calculates the tax for different tax categories when Ariba Network adapter for SAP NetWeaver sends a payment proposal against an invoice having an invoice amount of CAD 1000:

Line item 1: CAD 1000

Line Item Tax Category Tax Jurisdiction Tax Percentage Tax Amount

Line item 1 GST CABC 5% CAD 50

Line item 1 PST CABC 7% CAD 70

Amount for Line item 1 CAD 1000

Total invoice amount CAD 1000

Total tax amount CAD 120 (CAD 50 + CAD 70)

Total invoice amount including tax CAD 1120



Amount used to calculate the discount (Discount Basis) CAD 1000

Discount proposed by the buyer when payment is made in 10 days

2%

Discount Amount = CAD 20 (2% of 1000)

Amount payable after the tax discount CAD 1100 (Total invoice amount including tax - Discount Amount)

Discount applicable when paid in 10 days based on the 7% tax percentage, GST tax category, and CABC tax jurisdiction

CAD 1.40 (7% of CAD 20)

Total Discount Amount CAD 21.40 (CAD 20+ CAD 1.40)

Total Gross Amount CAD 1098.60

6.24.3 How to maintain parameters for payment proposals with discounts

Context

You need to maintain the parameter PP_TAX_INFO to process taxes and discounts in payment proposals.

Procedure

1. Go to transaction code SM30.

2. Maintain the following values in the /ARBA/PARAM_TAB table:

○ Variable Name: Enter the parameter name PP_TAX_INFO.○ Field Name: Leave it blank.○ Number: 0 (zero)○ INCL/EXCL: I○ Option: EQ○ Selection value: X

6.24.4 Handling errors

In some cases, the PayMeNow IDoc fails in SAP ERP with the error: You cannot change the content of field WSKTO.

To fix this error, apply the SAP Note 1954584 - FI_DOCUMENT_CHANGE: Unable to change WSKTO for vendors.



6.25 How to configure confirmation control keys

Context

Configure to process the confirmation control keys in purchase orders that buyers send suppliers on Ariba Network.

Procedure


2. Go back to the Display IMG page.

3. Click the tree structure, Materials Management Purchasing ConfirmationsSet up Confirmation Control.

4. Ensure that you specify the following values in the Change View Confirmation control keys:Overview window:

5. Click Confirmation sequence under the Dialog Structure tree view to view the confirmation control key sequence.

6. Click New Entries.7. Enter the following values for the confirmation sequences:

○ Conf. Category: Enter AB.○ Description: Enter Order acknowledgment.○ MRP-Relevant:Check this field.○ GR-Relevant: Do not check○ GR-Assignment: Do not check○ Monitoring Pert: Leave it blank.○ Ref. Date: Leave it blank.

○ Conf. Category: Enter LA.○ Description: Enter Shipping Notificat.○ MRP-Relevant: Check this field.○ GR-Relevant: Check this field.○ GR-Assignment: Check this field.○ Monitoring Pert: Leave it blank.○ Ref. Date: Leave it blank.



7 Topics about Ariba Network adapter for SAP NetWeaver for SAP Business Suite Add-On

Overview [page 313]

Installation requirements for using the SAP Business Suite Add-On with the Ariba Network adapter for SAP NetWeaver [page 315]

Setting up the cXML Adapter [page 316]

Configuring the cXML Adapter [page 318]

Configuring the System Landscape Directory [page 318]

Configuring transaction processes [page 322]

Configuring integration scenarios in the Integration Directory [page 325]

Topics about configuring the Integration Directory for inbound transactions [page 326]

Topics about configuring the Integration Directory for outbound transactions [page 333]

Linking multiple SAP ERP instances with Ariba Network [page 341]

Testing the Ariba Network adapter for SAP NetWeaver for SAP Business Suite Add-On configuration [page 344]

Understanding error handling [page 346]

Monitoring the cXML Adapter from Runtime Workbench [page 349]

Deploying the project [page 349]

Enabling support for attachments [page 350]

Using endpoints for integration with SAP Process Integration for SAP Business Suite Add-On [page 352]

Using the SAP Process Integration KeyStore [page 352]

7.1 OverviewThe SAP Business Suite Add-On for Ariba Network integration allows you to enable the following SAP Business Suite applications to integrate with Ariba Network and exchange transactional data seamlessly:

● SAP ERP● SAP Supplier Relationship Management (SAP SRM )● SAP Supply Network Collaboration (SAP SNC)

Using the SAP Business Suite Add-On, you can integrate a single SAP Business Suite system or multiple SAP Business Suite systems with Ariba Network using the Direct Connectivity or Mediated Connectivity integration methods. If you use the mediated connectivity, you can use the SAP Process Integration or your native middleware to connect to Ariba Network. SAP Ariba recommends that you use the SAP Process Integration.

Setting up Ariba Network adapter for SAP NetWeaverTopics about Ariba Network adapter for SAP NetWeaver for SAP Business Suite Add-On PUBLIC 313

The Ariba Network adapter for SAP NetWeaver allows you to integrate your SAP Business Suite system with Ariba Network as a buyer or supplier using the SAP Process Integration. This adapter is a library for SAP Process Integration and includes the integration processes and Java libraries to implement the cXML message format required by Ariba Network.

The Ariba Network adapter for SAP NetWeaver for SAP Business Suite Add-On includes the following:

● The cXML Adapter conforming to the J2EE Connector Architecture (JCA) specification which implements the cXML transport protocol.A design package containing integration processes, interface objects, and communication channels.

● A CIM file containing product and component definitions.

The following graphic illustrates how the Ariba Network adapter for SAP NetWeaver enables the transaction flow between Ariba Network and the SAP Business Suite system through the SAP Process Integration:

NoteThe SAP Business Suite Add-On generates the messages directly in the cXML format required by Ariba Network. You do not need the ABAP transports to send and receive transactional data in the cXML format.

Workflow for configuring the Ariba Network adapter for SAP NetWeaver when using the SAP Business Suite Add-On

Setting up the adapter involves the following high-level steps:

1. Verifying that all the software and connectivity requirements are in place.2. Setting up and configuring the cXML Adapter.3. Configuring the System Landscape Directory.4. Configuring transaction processes.5. Configure the SAP Business Suite Add-On component.6. Testing the configuration.

7.1.1 Additional references

● For downloading the SAP Business Suite Add-On, go to SAP Service Marketplace .● For more information about the SAP Business Suite Add-On, see the Ariba Network Integration 1.0 for SAP

Business Suite.

314 PUBLIC

Setting up Ariba Network adapter for SAP NetWeaverTopics about Ariba Network adapter for SAP NetWeaver for SAP Business Suite Add-

On

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Fproducts.html

http://help.sap.com/bni


● For more information about cXML and Ariba Network, see the following documents, available from Ariba Connect :○ Ariba Network Integration Guide○ Buyer Administration Guide○ cXML Solutions Guide○ cXML User’s Guide

● For more information about the JCA specification, see the relevant section on the Java web site (https://jcp.org/en/home/index ).

7.2 Installation requirements for using the SAP Business Suite Add-On with the Ariba Network adapter for SAP NetWeaver

The following table lists the SAP Process Integration versions supported for the deployment of the Ariba Network adapter for SAP NetWeaver:

Supported SAP Process Integration Versions

Ariba Network adapter for SAP NetWeaver Supported SAP Process Integration Versions

SAP Ariba cloud integration release 5.0 to 7.0 ● SAP Process Integration 7.1● SAP Process Integration 7.3● SAP Process Integration 7.4

SAP Ariba cloud integration release 8.0 or higher ● SAP Process Integration 7.1● SAP Process Integration 7.3● SAP Process Integration 7.4● SAP Process Integration 7.5

NoteTo prevent errors for the mandatory target fields containing a combination of NodeFunctions, CopyValue and Text Functions, ensure that you upgrade the SAP Process Integration 7.5 to SP00 Patch Level 4.

For information about the supported SAP Business Suite Add-On applications, see the Ariba Network Integration 1.0 for SAP Business Suite.


http://help.sap.com/disclaimer?site=https%3A%2F%2Fconnect.ariba.com%2F

http://help.sap.com/disclaimer?site=https%3A%2F%2Fconnect.ariba.com%2F

http://help.sap.com/disclaimer?site=https%3A%2F%2Fjcp.org%2Fen%2Fhome%2Findex

http://help.sap.com/disclaimer?site=https%3A%2F%2Fjcp.org%2Fen%2Fhome%2Findex



Prerequisites

Ensure that you meet the following Ariba Network requirements before installing the Ariba Network adapter for SAP NetWeaver:

● A valid, configured Ariba Network buyer or supplier account. For more information about configuring your Ariba Network buyer account, see the Buyer Administration Guide.

● An Ariba Network supplier relationship, including an ANID-to-Private ID mapping. For more information about creating a supplier relationship, see Chapter 4, Configuration in the Ariba Network Integration Guide.

● If the Ariba Network buyer account is configured to use digital certificate authentication, then a valid Secure Socket Layer (SSL) client certificate from one of Ariba Networks trusted Certificate Authorities is required. For more information about obtaining a digital certificate, see the cXML Solutions Guide.

● Ariba Network requires that all communication between the Ariba Network adapter for SAP NetWeaver and Ariba Network travel over the internet using Secure HyperText Transfer Protocol (HTTPS), a secure protocol that encrypts communication before transmission.For more information about internet connectivity requirements, see the Ariba Network Integration Guide. For more information about how to enable secure communications through a proxy server, see the cXML Adapter Parameters [page 361] section.

● The Ariba Network’s Certificate Authorities certificates are stored in the SAP Process Integration Keystore. The cXML Adapter uses the certificates stored in the SAP Process Integration Keystore to connect to Ariba Network.

Installation Files

To install the Ariba Network adapter for SAP NetWeaver for SAP Business Suite Add-On, you need the relevant archive file which is available on https://support.ariba.com/Connect/Log_In . For more information, see the Installing and upgrading Ariba Network adapter for SAP NetWeaver.

7.3 Setting up the cXML Adapter

The Ariba Network adapter for SAP NetWeaver relies upon the cXML Adapter, which conforms to the JCA specification and implements the cXML transport protocol.

See Configuring the Ariba Network adapter for SAP NetWeaver [page 51] for more information on the following topics:

● Understanding cXML Adapter Document Transmission● Configuring the cXML Adapter● Deploying and undeploying the cXML Adapter

For information on configuring the logs for the cXML Adapter, see Configuring logging for the cXML Adapter [page 359].

316 PUBLIC


On


Related Information

Deploying the cXML Adapter [page 317]

7.3.1 Deploying the cXML Adapter

If your version of SAP Process Integration is prior to 7.3 EHP1, use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP Process Integration.

From SAP Process Integration version 7.3 EHP1 onwards you must use the SAP Software Update Manager (SUM) tool to deploy the cXML Adapter.

For more information about how to install or upgrade using the SUM tool, contact your SAP system's administrator.

7.3.1.1 How to deploy the cXML Adapter using JSPM

Context

Use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP Process Integration.

NoteYou cannot undeploy the adapter using the JSPM. For information on how to undeploy the adapter, see How to undeploy the cXML Adapter using the TextConsole [page 62].

NoteTo upgrade to the latest version of the Ariba Network adapter for SAP NetWeaver, you must first undeploy the existing adapter and then deploy the latest version that you have downloaded from connect.ariba.com

.

Procedure

1. Navigate to the JSPM tool directory *****\JSPM\go.bat.For example, D:\usr\sap\NPI\DVEBMGS00\j2ee\\JSPM\go.bat.

2. Run the go.bat file to open the JSPM window.

3. Enter your user name and password to login.4. Place the SCA file in the specified location in the JSPM window, and click Next.

For example, D:\usr\sap\trans\EPS\in.




5. On the Start Deployment tab, choose New Software Components.6. After the SCA file is loaded, click Next to start the deployment.7. Click Next in the Specify Queue and Check Queue tabs.8. This starts the deployment of the cXML Adapter.9. Click Exit after the deployment is completed.

7.3.1.2 How to undeploy the Adapter using the Telnet

Procedure

Run the following at the Telnet prompt: deploy name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_deploy_error=stop

7.4 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.

While configuring the communication channel for each outbound or inbound transaction, the Parameters tab has the System Type option to specify the system for the buyer or supplier connecting to the Ariba Network.

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 [page 325] section. For a description of the parameters and instructions for how to configure retry attempts, see cXML Adapter Parameters [page 361].

7.5 Configuring the System Landscape Directory

Once you have installed the cXML Adapter, you must then configure the SAP System Landscape Directory (SLD) by importing the Ariba Network adapter for SAP NetWeaver product definition and defining the systems involved in the integration. The SLD 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 Ariba Network adapter for SAP NetWeaver 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 Network integration and defined in the SLD.

318 PUBLIC


On

You must make the following settings in the SLD:● Import Ariba Network Product and Component definitions● Define Technical and Business Landscape for Ariba Network● Define Technical and Business Landscape for SAP ERP

Related Information

Importing Ariba Network product and component definitions [page 319]Defining technical and business system for Ariba Network [page 320]How to define the technical system for SAP ERP [page 321]How to define the business system for SAP ERP [page 322]

7.5.1 Importing Ariba Network product and component definitions

Import the product and component definitions of SAP Ariba products that will work with SAP Process Integration, as a CIM file.

7.5.1.1 How to import product and component definitions

Procedure

1. From the SAP Process Integration main page, click System Landscape Directory.2. Click Administration.3. Open the SLD Administration page.4. Under the Content section, click Import.5. Click Browse and navigate to the location where the AribaNetworkAdapter.SoftwareCatalog.zip is

stored. Select this file.6. Click Import.7. From the SAP Process Integration main page, under Software Catalog, click Products and verify that the

following product is available:

○ Vendor: ariba.com○ Product: ASN○ Version: ASN, NW04.1

8. Verify that the following component is available:

○ Vendor: ariba.com○ Component: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CIX of ariba.com


○ Version: CIX

Results

The Ariba Network adapter for SAP NetWeaver is now recognized by the Integration Repository and Directory.

7.5.2 Defining technical and business system for Ariba Network

Set up the technical system for the Ariba Network system using the Technical System Wizard.

7.5.2.1 How to define the technical system for Ariba Network

Procedure

1. Choose Technical Systems from the main SLD page to open the Technical System page.2. Click New Technical System to open the Technical System Wizard.3. In the Wizard, choose Third-Party as the Technical System Type to set up a third-party (non-SAP)

application such as Ariba Network, and then click Next.4. Specify the system details as follows:

○ System Name: Specify a user-defined system name here. Example: TS_ASN○ Host Name: Enter a host name here. Example: an

5. Click Next.6. Associate the ASC Connector product and component to the system. Scroll down the list to choose the

product, ASN, defined earlier, and then click Add. You can also filter to choose the product to associate. Ensure that the component ARIBA_NETWORK_ADAPTER, CIx of ariba.com, is selected.

7. Click Finish.

Next Steps

Set up the business system for the Ariba Network system using the Business System Wizard.

320 PUBLIC


On

7.5.2.2 How to define the business system for Ariba Network

Procedure

1. Choose Business System from the main SLD page to open the Business System page.2. Click New Business System here to open the Business System Wizard.3. In the Wizard, choose Third-Party as the technical system type to associate the business system with, and

then click Next.4. Choose the technical system, TS_ASN, created in the previous procedure, from the System field, and then

click Next.

NoteThe Logical System Name is not required.

5. Enter the business system name, e.g. BS_ASN, in the Name field, and click Next.

6. Specify the installed products. Make sure that the product ASN, NW04.1 and the related component ARIBA_NETWORK_ADAPTER, CIx of ariba.com installed on the technical system, are selected, and then click Next.

7. Click Finish.

7.5.3 How to define the technical system for SAP ERP

Context

Set up the technical system for the SAP ERP system using the Technical System Wizard.

Procedure

1. Choose Technical System from the main SLD page to open the Technical System page.2. Click on New Technical System here to open the Technical System Wizard.3. In the Wizard, choose AS ABAP as the Technical System Type, and then click Next.4. To specify the SAP ERP system details, enter values in the AS ABAP name (SID), Installation Number,

and Database Host Name fields, and then click Next.5. Specify the Message Server and Central Application Server. Enter values in the Host Name, and Message

Server Port field. Specify a logon group for the Message Server by entering a value in the Logon Groups column and clicking Add Logon Groups to assign them. You can also filter to choose the logon groups. Enter values in the Host Name and Instance Number fields for the Central Application Server, and then click Next.


6. (Optional) Define additional application servers if required. Specify values in the Host Name and Instance Number columns in the Application Server List table, and click Add Application Server. You can also filter to choose the application server details. Click Next.

7. Define the Client. Enter values in the Client Number and Logical Client Name columns of the Client List table, and then click Next.

8. Define software product and components. Choose the SAP ERP version installed on this technical system, as well all other products installed on the system. You can filter to choose the installed products and the software components.

9. Click Finish.

Next Steps

Set up the business system for your SAP ERP using the Business System Wizard.

7.5.4 How to define the business system for SAP ERP

Procedure

1. Choose Business System from the main SLD page to open the Business System page.2. Click New Business System here to open the Business System Wizard.3. In the Wizard, choose AS ABAP as technical system type to associate the business system with, and then

click Next.4. Choose the technical system created in the previous procedure from the System dropdown list, to

associate it with the business system. Choose a client for the selected technical system from the Client dropdown list, and then click Next.

5. Enter the business system name. Example: BS_SAPR3_50, and click Next.

6. Specify the installed products. Choose 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 Next.

7. Choose the role of the business system. Choose Application System as the Business System Role and choose your SAP Process Integration instance name from the Related Integration Server drop-down list to specify the integration server. In the case of application systems, specify the integration server.

8. Click Finish.

7.6 Configuring transaction processes

Once you have installed the SLD, you must then:

● Import the design package containing the transactions supported by the Ariba Network adapter for SAP NetWeaver.

322 PUBLIC


On

● Configure SAP Process Integration connectivity to SAP ERP.● 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.

NoteThe 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.

Related Information

How to import the design package [page 323]Configuring SAP ERP connectivity [page 324]How to assign business systems in the Integration Directory [page 324]

7.6.1 How to import the design package

Context

The transport file AribaNetworkAdapterSAPNetweaver_SapAddOn.tpz contains the definition of the business scenarios.

Procedure

1. Copy the package file AribaNetworkAdapterSAPNetweaver_SapAddOn.tpz to the import directory on the SAP Process Integration 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 Process Integration main page.3. From the Tools menu, select the option Import Design objects....4. Select AribaNetworkAdapterSAPNetweaver_SapAddOn.tpz from the available files list, and then click

OK.5. After the import completes, the component ARIBA_NETWORK_ADAPTER, CIx of ariba.com appears in

the components list of the Integration Builder Design Tool.

NoteThe External SAP Add-On schema is http://ariba.com/xi/ASN/AddOn/CommonBasis.


The Adapter metadata is http://ariba.com/xi/ASCAdapter.

7.6.2 Configuring SAP ERP connectivity

The inbound and outbound documents are exchanged between SAP Process Integration and SAP ERP by using ABAP proxies.

For information about proxy configuration for outbound documents, see cXML Adapter Parameters [page 361].

7.6.3 How to assign business systems in the Integration Directory

Context

The Integration Directory configuration of the Ariba Network adapter for SAP NetWeaver 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.

Procedure

1. Open the Configuration: Integration Builder from the SAP Process Integration 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, choose 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, choose Business Systems, choose the business systems BS_ASN and BS_SAPR3_50

created earlier, from the list. For more information about creating business systems, see the Configuring the System Landscape Directory [page 318] section.

NoteIf you have multiple ERP systems, you must choose all the Business Systems representing your SAP ERP instances involved in the integration.

6. Click to clear the Create Communication Channel Automatically check box, if it is checked, to avoid the creation of unnecessary channels.

7. Click Finish.

324 PUBLIC


On

7.7 Configuring integration scenarios in the Integration Directory

This section describes how to import and configure the integration scenarios in the SAP Process Integration (PI) 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.

NoteDo not activate the Change Lists feature of Integration Builder Configuration Tool until all the configuration steps are completed.

You can configure these transaction scenarios in the following SAP Process Integration versions:

● SAP Process Integration 7.1● SAP Process Integration 7.3 single stack (Java only)● SAP Process Integration 7.3 dual stack (ABAP and Java)● SAP Process Integration 7.4 single stack (Java only)● SAP Process Integration 7.4 dual stack (ABAP and Java)● SAP Process Integration 7.5 single stack (Java only)

7.7.1 Workflow for configuring the integration scenario for inbound and outbound transactions

Configuring the integration scenarios for the outbound and inbound transactions involves the following steps:

1. Transfer the Integration Scenario from the Integration Repository Enterprise Service Builder to the Integration Directory Integration Builder . For more information, see:○ Transferring the Integration Scenario for Inbound Transactions [page 326]○ Transferring Integration Scenario for Outbound Transactions [page 334]

2. Configure the Integration Scenario. For more information, see:○ About Configuring the Integration Scenario for Inbound Transactions [page 328]○ About Configuring the Integration Scenario for Outbound Transactions [page 336]

3. Configure the Communication Channels. For more information, see:○ Configuring Communication Channels for Inbound Transactions [page 332]○ Configuring Communication Channels for Outbound Transactions [page 339]

4. Activate the integration scenario. For more information, see:○ Activating the Scenario for Inbound Transactions [page 333]○ Activating the Scenario for Outbound Transactions [page 341]


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, see About Configuring the System Landscape Directory [page 313].

○ All the steps of a configuration scenario section must be completed to fully configure a scenario.

○ If you are an existing customer, you must delete the existing Configuration scenario and rerun the steps for the configuration scenario.

7.8 Topics about configuring the Integration Directory for inbound transactions

How to transfer the integration scenario for inbound transactions [page 326]

Configuring the integration scenario for inbound transactions [page 328]

How to assign the model for inbound transactions [page 328]

How to assign components for inbound transactions [page 329]

How to configure sender and receiver relations for individual connections for inbound transactions [page 329]

How to generate objects for inbound and outbound transactions [page 331]

How to configure communication channels for inbound transactions [page 332]

How to activate the scenario for inbound transactions [page 333]

7.8.1 How to transfer the integration scenario for inbound transactions

Context

The first step to configure the integration scenario is to transfer the integration scenario to the Integration Builder. The integration scenario is loaded into the Integration Repository when the design package is imported.

Procedure

1. From the SAP Process Integration main page, choose Integration Directory Integration Builder , and then login to the Configuration: Integration Builder application.

326 PUBLIC


On

2. In the Integration Builder menu, choose Tools Apply Model from ES Repository .3. In the first screen of the Transfer Model from ES Repository wizard > Select Process Integration

Scenario, click the Name field, and then click the Display Input Help dropdown menu and choose Input Help.

4. Choose the Process Integration Scenario for the following inbound transactions from the Enterprise Services Repository screen:

Buyer

○ OrderConfirmationName: AR_AddOn_OrderConfirmation_SendNamespace: http://ariba.com/xi/ASN/AddOn/OrderConfirmationSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ ShipNoticeName: AR_AddOn_AdvanceShipNotice_SendNamespace: http://ariba.com/xi/ASN/AddOn/AdvanceShipNoticeSoftware Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ InvoiceName: AR_AddOn_InvoiceNamespace: http://ariba.com/xi/ASN/AddOn/InvoiceSoftware Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ PayMeNowName: AR__AddOn_PayMeNow_SendNamespace: http://ariba.com/xi/ASN/AddOn/PayMeNowSoftware Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ ServiceEntrySheetName: AR_AddOn_ServiceEntrySheet_SendNamespace: http://ariba.com/xi/ASN/AddOn/ServiceEntrySheetSoftware Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ QuoteMessageName: AR_AddOn_QuoteMessage_SendNamespace: http://ariba.com/xi/ASN/AddOn/QuoteMessageSoftware Component Version: ARIBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ ReceiptRequestName: AR_AddOn_ReceiptRequest_SendNamespace: http://ariba.com/xi/ASN/AddOn/ReceiptRequestSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ ComponentConsumptionRequestName: AR_AddOn_ComponentConsumptionRequest_SendNamespace: http://ariba.com/xi/ASN/AddOn/ComponentConsumptionRequestSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ ProductReplenishmentMessageName: AR_AddOn_ProductReplenishmentMessage_SendNamespace: http://ariba.com/xi/ASN/AddOn/ProductReplenishmentMessage


Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

Supplier

○ SalesOrderName: AR_AddOn_SalesOrder_SendNamespace: http://ariba.com/xi/ASN/AddOn/SalesOrderSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ PaymentRemittancesName: AR_AddOn_PaymentRemittanceRequest_SendNamespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittanceRequestSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com



7.8.2 Configuring the integration scenario for inbound transactions


1. Assigning the model.How to assign the model for inbound transactions [page 103]

2. Assigning the components.How to assign components for inbound transactions [page 103]

3. Configuring the sender and receiver relations for individual connections.How to configure sender and receiver relations for individual connections for inbound transactions [page 329]

4. Generating the configuration objects.How to generate objects for inbound and outbound transactions [page 105]

7.8.3 How to assign the model for inbound transactions

Procedure


2. After choosing the model, assign components to the application components for the chosen integration scenario.

328 PUBLIC


On

7.8.4 How to assign components for inbound transactions

Procedure




and choose Value List <F4>. Choose the communication component name for the business system of your SAP Process Integration, from the selection list and click Apply.




and choose Value List <F4>. Choose the communication component name for the business system for Ariba Network, from the selection list and click Apply.


7.8.5 How to configure sender and receiver relations for individual connections for inbound transactions

Procedure



3. Click the New Communication Channel button (the icon at the top left), and then choose Create Communication Channel with Template to start the Create Communication Channel wizard.

4. Click Continue.5. On the next page, click the Name field and then click the Display Input Help dropdown menu and choose

Input Help.6. Choose the Communication Channel Templates for the following transactions:

Buyer


○ OrderConfirmationName: CCT_AddOn_OrderConfirmation_cXML_SenderNamespace: http://ariba.com/xi/ASN/AddOn/OrderConfirmationSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ ShipNoticeName: CCT_AddOn_AdvanceShipNotice_cXML_Sender Namespace: http://ariba.com/xi/ASN/AddOn/AdvanceShipNoticeSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ InvoiceName: CCT_AddOn_Invoice_cXML_SenderNamespace: http://ariba.com/xi/ASN/AddOn/InvoiceSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ PayMeNowName: CCT_AddOn_PayMenow_cXML_SenderNamespace: http://ariba.com/xi/ASN/AddOn/PayMeNowSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ ServiceEntrySheetName: CCT_AddOn_ServiceEntrySheet_cXML_SenderNamespace: http://ariba.com/xi/ASN/AddOn/ServiceEntrySheetSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ QuoteMessageName: CCT_AddOn_QuoteMessage_cXML_SenderNamespace: http://ariba.com/xi/ASN/AddOn/QuoteMessageSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ ReceiptRequestName: CCT_AddOn_ReceiptRequest_cXML_SenderNamespace: http://ariba.com/xi/ASN/AddOn/ReceiptRequestSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ ComponentConsumptionRequestName: CCT_AddOn_ComponentConsumptionRequest_cXML_SenderNamespace: http://ariba.com/xi/ASN/AddOn/ComponentConsumptionRequestSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ ProductReplenishmentMessageName: CCT_AddOn_ProductReplenishmentMessage_cXML_SenderNamespace: http://ariba.com/xi/ASN/AddOn/ProductReplenishmentMessageSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

Supplier

○ SalesOrderName: CCT_AddOn_Supplier_SalesOrder_cXML_SenderNamespace: http://ariba.com/xi/ASN/AddOn/SalesOrderSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ PaymentRemittanceRequestName: CCT_AddOn_Supplier_PaymentRemittanceRequest_cXML_SenderNamespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittanceRequestSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

7. Click Continue.

330 PUBLIC


On

8. You can also choose to modify the channel names. Click Finish.


9. In the Connections from Component Assignment tab, click the empty Communication Channel cell corresponding to the business system of your SAP Process Integration in the Sender Business System Components table.

10. Click on the Value List drop down and select Value List <F4. Choose the CC_Proxy_Sender communication channel from the selection list and click Apply.


7.8.6 How to generate objects for inbound and outbound transactions

Procedure


○ Click Generation in the General section.○ Choose the Receiver Determination, Interface Determination, and Sender/Receiver Agreement

checkboxes in the Scope of Generation section.3. Click Create New in the Change List for Generated Objects section. The text box already contains an



Results




7.8.7 How to configure communication channels for inbound transactions

Procedure

1. In the Communication Channel list, double-click the following communication channels to open it:

Buyer

○ OrderConfirmation|< Name of the Business System for Ariba Network> | CC_AddOn_OrderConfirmation_cXML_Sender

○ Ship Notice|< Name of the Business System for Ariba Network> | CC_AddOn_AdvanceShipNotice_cXML_Sender

○ Invoice|< Name of the Business System for Ariba Network> |CC_AddOn_Invoice_cXML_Sender

○ PayMeNow|< Name of the Business System for Ariba Network> | CC_PayMeNow_cXML_Sender

○ ServiceEntrySheet|< Name of the Business System for Ariba Network> | CC_ServiceEntrySheet_cXML_Sender

○ QuoteMessage< Name of the Business System for Ariba Network> | CC_AddOn_QuoteMessage_cXML_Sender

○ ReceiptRequest< Name of the Business System for Ariba Network> | CC_AddOn_ReceiptRequest_cXML_Sender

○ ComponentConsumptionRequest< Name of the Business System for Ariba Network> | CC_AddOn_ComponentConsumptionRequest_cXML_Sender

○ ProductReplenishmentMessage< Name of the Business System for Ariba Network> | CC_AddOn_ProductReplenishmentMessage_cXML_Sender

Supplier

○ SalesOrder|< Name of the Business System for Ariba Network>| CC_AddOn_Supplier_SalesOrder_cXML_Receiver

○ PaymentRemittanceRequest< Name of the Business System for Ariba Network> | CC_AddOn_Supplier_PaymentRemittanceRequest_cXML_Receiver

2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network buyer account configuration.To enable TLS support, see Enabling TLS support [page 111].

3. Under the cXML Configuration section, select the Use SAP Add on Suite check box.

332 PUBLIC


On

NoteIf you created the channel by copying from an existing channel, you must change the request type for each of the transactions to the <Name of the transaction request - for example, Invoice> in the Inbound Request Type field.

4. If required, edit the other parameters.5. Update the cXML version parameter to the latest applicable version. For more information about the cXML

adapter parameters, see cXML Adapter Parameters [page 361].6. Save the changes.

7.8.8 How to activate the scenario for inbound transactions

Procedure

Using the Change List tab on the main application screen, activate all the change lists containing the objects created and modified during the component setup.

Results

This completes the configuration of the inbound transactions in the SAP Process Integration.

7.9 Topics about configuring the Integration Directory for outbound transactions

How to transfer integration scenario for outbound transactions [page 334]

Configuring the integration scenario for outbound transactions [page 336]

How to assign the model for outbound transactions [page 336]

How to assign components for outbound transactions [page 336]

How to configure sender and receiver relations for individual connections For outbound transactions [page 337]

How to generate objects for outbound transactions [page 339]

How to configure communication channels for outbound transactions [page 339]

How to activate the scenario for outbound transactions [page 341]


7.9.1 How to transfer integration scenario for outbound transactions

Context

The first step is to transfer the integration scenario to the Integration Builder. The integration scenario is loaded into the Integration Repository when the design package is imported.

Procedure

1. From the SAP Process Integration main page, choose Integration Directory Integration Builder , and then login to the Configuration: Integration Builder application.

2. In the Integration Builder menu, choose Tools Apply Model from ES Repository .3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration

Scenario, click the Name field, and then click the Display Input Help dropdown menu and choose Input Help.

4. Choose the process integration scenario for the following transactions from the Enterprise Services Repository screen:

Buyer:

○ PurchaseOrderName: AR_AddOn_PurchaseOrder_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/PurchaseOrderSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ ERPInvoiceName: AR__AddOn_CCInvoice_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/ERPInvoiceSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ PaymentProposalName: AR__AddOn_PaymentProposal_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/PaymentProposalSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ PaymentRemittanceName: AR__AddOn_PaymentRemittance_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittanceSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ PaymentRemittanceSURName: AR__AddOn_PaymentRemittanceSUR_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittanceSURSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ GoodsReceiptName: AR_AddOn_GoodsReceipt_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/GoodsReceipt

334 PUBLIC


On

Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com○ StatusUpdateRequest

Name: AR_AddOn_StatusUpdateResponse_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/StatusUpdateRequestSoftware Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

NoteBuyers must use the new StatusUpdateRequest to send and receive status on invoices and service entry sheets. The Invoice Status Update Request is no longer available.

○ QuoteRequestName: AR_AddOn_QuoteRequest_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/QuoteRequestSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ ProductActivityMessageName: AR_AddOn_ProductActivityMessage_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/ProductActivityMessageSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

Supplier

○ SalesOrderConfirmationName: AR_AddOn_SalesOrderConfirmation_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/SalesOrderConfirmationSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ OutboundDeliveryNotification (Ship Notice)Name: AR_AddOn_OutboundDeliveryNotification_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/OutboundDeliveryNotificationSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ InvoiceName: AR_AddOn_Invoice_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/InvoiceSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

5. Click Continue.6. If required, change the name of the scenario for the Integration Directory.7. Click Finish.

Results



7.9.2 Configuring the integration scenario for outbound transactions


1. Assigning the model.How to assign the model for outbound transactions [page 93]

2. Assigning the components.How to assign components for outbound transactions [page 336]

3. Configuring the sender and receiver relations for individual connections.How to configure sender and receiver relations for individual connections For outbound transactions [page 337]

4. Generating the configuration objects.How to generate objects for outbound transactions [page 339]

7.9.3 How to assign the model for outbound transactions

Procedure


2. After selecting the model, assign components to the application components for the selected integration scenario.

7.9.4 How to assign components for outbound transactions

Procedure


components for Ariba Network.3. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is


and choose Value List <F4. Choose the communication component name for the business system for Ariba Network, from the selection list and click Apply.


336 PUBLIC


On

5. Click the Next Role button (the right arrow) to go to the next screen on the window.6. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is


and choose Value List <F4. Choose the communication component name for the business system of your SAP Process Integration, from the selection list and click Apply.


7.9.5 How to configure sender and receiver relations for individual connections For outbound transactions

Procedure


2. In the Connections from Component Assignment tab in the Configure Connection window, click the empty Communication Channel cell corresponding to the business system for Ariba Network in the Receiver Business System Components table.

3. Click the New Communication Channel button (the icon at the top left), and then choose Create Communication Channel with Template to start the Create Communication Channel wizard.

4. Click Continue.5. On the next page, click the Name field and then click the Display Input Help dropdown menu and choose

Input Help.6. Choose the Communication Channel Templates for the following transactions:

Buyer

○ PurchaseOrderName: CCT_AddOn_PurchaseOrder_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/AddOn/PurchaseOrderSoftware Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ ERPInvoiceName: CCT_AddOn_CCInvoice_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/AddOn/ERPInvoiceSoftware Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ PaymentProposalName: CCT_AddOn_PaymentProposal_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/AddOn/PaymentProposalSoftware Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ PaymentRemittanceName: CCT_AddOn_PaymentRemittance_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittance


Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ PaymentRemittanceSURName: CCT_AddOn_PaymentRemittanceSUR_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittanceSURSoftware Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ GoodsReceiptName: CCT_AddOn_GoodsReceipt_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/AddOn/GoodsReceiptSoftware Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ StatusUpdateResponseName: CCT_AddOn_StatusUpdateResponse_cXML_ReceiveNamespace: http://ariba.com/xi/ASN/AddOn/StatusUpdateResponseSoftware Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPT CIX of ariba.com

○ QuoteRequestName: CCT_AddOn_QuoteRequest_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/AddOn/QuoteRequestSoftware Component Version: ARIBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ ProductActivityMessageName: CCT_AddOn_ProductActivityMessage_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/AddOn/ProductActivityMessageSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

Supplier

○ SalesOrderConfirmationName: CCT_Supplier_SalesOrderConfirmation_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/AddOn/SalesOrderConfirmationSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ OutboundDeliveryNotificationName: CCT_AddOn_Supplier_OutboundDeliveryNotification_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/AddOn/OutboundDeliveryNotificationSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com

○ InvoiceName: CCT_AddOn_Supplier_Invoice_cXML_ReceiverNamespace: http://ariba.com/xi/ASN/AddOn/InvoiceSoftware Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPT CIX of ariba.com


TipIf you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction, you can create the communication channel by copying from a channel that has already been configured.

338 PUBLIC


On

9. In the Connections from Component Assignment tab, click the empty Communication Channel cell corresponding to the business system of your SAP Process Integration in the Receiver Business System Components table.

10. Click on the Value List dropdown and choose Value List <F4. Choose the CC_Proxy_Receiver communication channel from the selection list and click Apply.


7.9.6 How to generate objects for outbound transactions

Procedure


○ Click Generation in the General section.○ Choose the Receiver Determination, and Interface Determination check boxes in the Scope of

Generation section.3. Click Create New in the Change List for Generated Objects section. The text box already contains an



Generating the objects creates the configuration objects if they do not yet exist. If they already exist, they are reused and enhanced, if required. You can also simulate generation for test purposes.

7.9.7 How to configure communication channels for outbound transactions

Procedure

1. In the Communication Channel list, double-click the following communication channels to open it:

Buyer

○ PurchaseOrder|< Name of the Business System for Ariba Network |

CC_AddOn_PurchaseOrder_cXML_Receiver under the AR_AddOn_PurchaseOrder_Receive Configuration Scenario.

○ ERPInvoice|< Name of the Business System for Ariba Network | CCT_ERPInvoice_cXML_Receiver

under the AR_ERPInvoice_Receive Configuration Scenario.


○ PaymentProposal|< Name of the Business System for Ariba Network |

CCT_PaymentProposal_cXML_Receiver under the AR_PaymentProposal_Receive Configuration Scenario.

○ PaymentRemittance|< Name of the Business System for Ariba Network |

CCT_PaymentRemittance_cXML_Receiver under the AR_PaymentRemittance_Receive Configuration Scenario.

○ PaymentRemittanceSUR|< Name of the Business System for Ariba Network |

CCT_PaymentRemittanceSUR_cXML_Receiver under the AR_PaymentRemittanceSUR_Receive Configuration Scenario.

○ GoodsReceipt|< Name of the Business System for Ariba Network |

CC_AddOn_GoodsReceipt_cXML_Receiver under the AR_AddOn_GoodsReceipt_Receive Configuration Scenario.

○ StatusUpdateResponse|< Name of the Business System for Ariba Network |

CC_AddOn_StatusUpdateResponse_cXML_Receiver under the AR_AddOn_StatusUpdateResponse_Receive Configuration Scenario.

○ QuoteRequest|< Name of the Business System for Ariba Network |

CC_AddOn_QuoteRequest_cXML_Receiver under the AR_AddOn_QuoteRequest_Receive Configuration Scenario.

○ ProductActivityMessage|< Name of the Business System for Ariba Network |

CC_AddOn_ProductActivityMessage_cXML_Receiver under the AR_AddOn_ProductActivityMessage_Receive Configuration Scenario.

Supplier

○ SalesOrderConfirmation|< Name of the Business System for Ariba Network |

CC_AddOn_Supplier_SalesOrderConfirmation_cXML_Receiver under the AR_AddOn_Supplier_SalesOrderConfirmation_cXML_Receive Configuration Scenario.

○ OutboundDeliveryNotification|< Name of the Business System for Ariba Network |

CC_AddOn_Supplier_OutboundDeliveryNotification_cXML_Receiver under the AR_AddOn_OutboundDeliveryNotification_cXML_Receive Configuration Scenario

○ Invoice|< Name of the Business System for Ariba Network |

CC_AddOn_Supplier_Invoice_cXML_Receive under the AR_AddOn_Supplier_Invoice_cXML_Receive Configuration Scenario

2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration.

340 PUBLIC


On

To enable TLS support, see Enabling TLS support [page 111].3. Under the cXML Configuration section, select the Use SAP Add on Suite check box.

NoteIf you created the channel by copying from an existing channel, you must change the request type for each of the transactions to the <Name of the transaction request - for example, PaymentProposalRequest> in the Outbound Request Type field. For more information about the cXML Adapter parameters, see cXML Adapter Parameters [page 361]

4. Update the cXML version parameter to the latest applicable version.5. If required, edit the other parameters.6. Save the changes.

7.9.8 How to activate the scenario for outbound transactions

Procedure

Using the Change List tab on the main application screen, activate all the change lists containing the objects created and modified during the component setup.

Results

This completes the configuration of the outbound transactions in the SAP Process Integration.

7.10 Linking multiple SAP ERP instances with Ariba Network

If your organization has more than one instance of SAP ERP, you can link them to a single Ariba Network account. This allows all the documents from particular vendors to be routed to a single Ariba Network account and in the reverse direction, the documents from Ariba Network will be routed to a particular SAP ERP instance.

Buying organization or service provider accounts must be enabled for multiple ERP systems by Ariba Network 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 Network of multiple SAP ERP instances.


Document Routing Mechanism

If you have multiple ERP systems, each of the SAP ERP 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 ERP 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="[email protected]" 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.

When you have multiple ERP systems, the SystemID identifier is not inserted in the outgoing documents or expected in the incoming documents. However, the SAP Business Suite Add-On always sends the SystemID in ERP-outbound cXML documents.

The following figure shows the SystemID identifier location in outbound documents at the top and in inbound documents at the bottom.

342 PUBLIC


On

SystemID identifier location in the message exchanges

7.10.1 Multi-ERP configuration

The multi-ERP implementation requires configuration on all three sides: SAP ERP, SAP Process Integration and Ariba Network.

Configuring the System Landscape Directory

You must configure all your SAP ERP instances in the SLD as Technical and Business Systems.

For more information, see Defining the Technical System for SAP ERP [page 321] and Defining the Business System for SAP ERP [page 322].


Configuring SAP ERP Connectivity

The connectivity between all the SAP ERP instances and the SAP Process Integration server has to be setup.

For more information, see the Configuring SAP ERP Connectivity [page 324] 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.

NoteWhen you configure your SAP Business Suite Add-On to support multiple instances of SAP ERP, you must configure a content-based routing in Process Integration for the cXML attributes. To do this, use a valid XPath Expression /p1.cXMLMessage/cXMLMessageContent/cXML that you insert manually in the Receiver Determination.

Configuring Ariba Network

You must configure Ariba Network with the information about all the instances of SAP ERP involved in the integration and link it with the Ariba Network buyer account.

NoteBuying organization or service provider accounts must be enabled for Multi-ERP implementation by Ariba Network Support. The required configuration sections is not available for accounts that have not been enabled.

Fore more information on Ariba Network setup, see the Linking Multiple Business Applications section, in Chapter 4 Configuration, of the Ariba Network Integration Guide.

7.11 Testing the Ariba Network adapter for SAP NetWeaver for SAP Business Suite Add-On configuration

This section provides instructions for how to test your configuration.

To troubleshoot any errors you encounter, you can use the SAP Process Integration 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 Process Integration.

For more information about error handling, see the Understanding Error Handling [page 346] section.

344 PUBLIC


On

Before beginning, be sure that you have at least one fully configured Ariba Network supplier relationship. For more information about creating a supplier relationship, see the Configuration section in the Ariba Network Integration Guide.

Testing Processes

After you have successfully deployed and configured the Ariba Network adapter for SAP NetWeaver for SAP Business Suite Add-On, you must run test transactions to ensure that Ariba Network and your SAP ERP system are communicating properly in both directions. To test processes:

● Send a purchase order from your SAP Business Suite Add-On to Ariba Network.● Run a getPending transaction by creating an invoice in Ariba Network and then sending it to your SAP

Business Suite Add-On.

7.11.1 How to send a purchase order for testing

Procedure

1. In your SAP ERP which has the SAP Business Suite Add-On installed, create a purchase order.If the system is working properly, then the OrderRequest cXML is sent to SAP Process Integration as the SAP Suite Add-On enables cXML from SAP ERP. TheAriba Network adapter for SAP NetWeaver for SAP Business Suite Add-On on SAP Process Integration then sends the XML message to Ariba Network.2. Verify that the messages are available in the SAP Process Integration monitoring tools (Process Integration

Runtime Workbench and Integration Engine Monitor).3. Log on to Ariba Network 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.

7.11.2 How to run a getPending transaction for testing

Procedure

1. Create a test invoice in Ariba Network.If the system is working properly, then the cXML Adapter downloads the invoice from Ariba Network and sends the cXML to SAP ERP.2. Verify that the messages are available in the SAP Process Integration monitoring tools (PI Runtime

Workbench and Integration Engine Monitor).3. Check to see that the invoice is created in your SAP ERP.


Results

If these two checks are successful, the inbound connection is working properly.

7.12 Understanding error handling

The SAP Process Integration 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, the message is logged as an error in the SXMB_MONI, and can be restarted (reprocessed).

The following describe the error handling on the Adapter Engine side:

● For inbound messages ( Ariba Network SAP ERP ), the Email notification is used to send an email when an error occurs (mainly connection issues). This is because during the pull (getPending), SAP Process Integration 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 ( SAP ERP Ariba Network ), the sending operation initiated by SAP Process Integration is synchronous, and if any exception occurs, it is related to a message from SAP Process Integration. 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 SAP Process Integration). 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 Network, if available (for example, in case of documents refused by Ariba Network).

Related Information

Understanding error and status codes [page 346]Understanding email notifications [page 348]

7.12.1 Understanding error and status codes

The cXML Adapter notification emails include an Ariba Network adapter for SAP NetWeaver 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 in the cXML Basics section in the cXML User’s Guide.

346 PUBLIC


On

The following table describes the possible general error codes (Ariba Network adapter for SAP NetWeaver error codes) in cXML adapter notifications:

Application Errors:

Status Text

ERR101 Invalid Configuration Parameter. Trusted certificates not installed properly.

ERR102 Incorrect Client Certification

ERR201 Authentication Failed on ASN

ERR202 ASN Internal Server Error

ERR203 Send cXML to AN Failed (Invalid Request)

ERR204 Send cXML to AN Failed (Temporary Error)

ERR205 Send cXML to AN Failed (Unrecoverable Error)

ERR301 Get Profile Transaction Failed

ERR302 Get Pending Transaction Failed

ERR303 Outbound Transaction Failed

ERR401 Invalid Outbound Message (PI -> ASN)

ERR402 Invalid Inbound Message (ASN -> PI)

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

ERP Errors:

Status Text

ECC101 Configuration Load Failed

ECC102 IO Error

ECC103 Ariba Network Not Available

7.12.2 Understanding email notifications

The following are the different parts of an error notification email:

● Date: The date and time of the error.● Error: The Ariba Network adapter for SAP NetWeaver Error code. For a list of general error codes, see the

Application Errors, Runtime Error, and ERP 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 Network, and the response message from Ariba Network is not available

○ Details of the cXML response, if the response from Ariba Network 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/[email protected].

● [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.

348 PUBLIC


On

7.13 Monitoring the cXML Adapter from Runtime Workbench

After you deploy the Ariba Network adapter for SAP NetWeaver on SAP Process Integration and configure the inbound and outbound transaction scenarios in the Integration Directory, communication channels are created for each inbound and outbound transaction in the Integration Directory. These communication channels are displayed within the Runtime Workbench from where an SAP NetWeaver administrator can monitor these channels. An SAP NetWeaver administrator can start or stop channels from the Runtime Workbench as required without having the need to access the Integration Directory. For example, if an administrator stops an inbound channel that downloads invoices from the Ariba Network, the channel stops to run as indicated by the status on the user interface and no invoices are downloaded.

NoteIf the cXML Adapter stops downloading documents from Ariba Network, the NetWeaver administrator needs to login to the Runtime Workbench and stop/start the respective channel. For example, if the adapter stops downloading invoices from Ariba Network, an administrator must login to the Runtime Workbench and start the invoice communication channel to ensure that the adapter starts downloading invoices.

7.14 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 Process Integration Export files (tpz files) using SAP NetWeaver Process Integration Builder. SAP Process Integration Builder contains two parts:

● Design tool, which contains interface objects and integration processes● Configuration tool, which contains business services and routing rules. For more information, see the SAP

Process Integration 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 Process Integration documentation.

Each tpz file works as a single unit within SAP Process 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.

7.14.1 SAP Ariba Network certification

SAP Ariba must certify any Ariba Network adapter for SAP NetWeaver that works with Ariba Network. Certification is the process by which SAP Ariba's Global Solutions Organization (GSO) inspects and approves


the Ariba Network adapter for SAP NetWeaver, the cXML documents it generates, and its connection to Ariba Network.

In its default state, the Ariba Network adapter for SAP NetWeaver is Ariba Network-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 Network Integration Guide. The guide describes how to download certification files from SAP Ariba Connect and provides instructions to guide you through the certification process.

7.14.2 How to download the Ariba Network Integration Guide from SAP Ariba Connect

Procedure

1. Go to https://support.ariba.com/Connect/Log_In and log in using your user ID and password. If you do not have a User ID and Password for SAP Ariba Connect, contact your SAP Ariba account executive.

2. On the Home page, click Product Information and Documentation.3. Click Cloud Integration in the Product Information section and then click Resources.

The Cloud Integration Resources page appears.4. In the Integration Tools section, click Integration tools for Ariba Network.

The Integration tools for Ariba Network page appears.5. Under Product Documentation, click Ariba Network Documentation for Buyers.6. Click the Administration tab and then click ERP Integration .7. Click Purchase Order and Invoice Automation and then click Ariba Network Integration Guide.

7.15 Enabling support for attachments

7.15.1 Attachments support in cXML

The cXML protocol supports the attachment of external files of any type to cXML documents. For example, buyers sometimes need to clarify purchase orders with supporting memos, drawings, or faxes. Another example is the CatalogUploadRequest document, which includes catalog files as attachments.

Files referenced by cXML documents can reside either on a server accessible by the receiver or within an envelope that also includes the cXML documents themselves. To attach external files to a cXML document in a single envelope, use Multipurpose Internet Mail Extensions (MIME). The cXML document contains references to external parts sent within a multipart MIME envelope.

For more information about attachments, see the cXML User’s Guide and cXML Solutions Guide.

Attachments in cXML can be of any file type, such as DOC, PDF, TXT, JPEG, and so on.

350 PUBLIC


On


Ariba Network supports attachments for the following transactions:

● Purchase Order● Invoice● Ship Notice● Order Confirmation

Limitations for Attachments

The size of the attachments for both inbound and outbound documents cannot exceed 100 MB.

7.15.2 Attachments for outbound documents

When an outbound document (purchase order) is sent from SAP Business Suite Add-On to the cXML Adapter with attachments, the attachments are part of the Comments element in the cXML file as shown below:

<Comments> <Attachment> <URL>Content ID of the Attachment</URL> </Attachment> </Comments>

The attachment is embedded in the message sent from SAP Business Suite Add-On as a Base 64 string. The cXML Adapter converts the incoming message into a MIME message, decodes and adds the attachment to the MIME message, and sends the MIME message to Ariba Network.

Purchase Orders with Attachments

A purchase order (PO) document can have multiple attachments, such as product specifications, images, supporting memos, and so on. When Ariba Network receives a PO with attachments, Ariba Network either forwards the attachments to the respective suppliers or stores these attachments to allow online access for suppliers. These stored attachments expire after 180 days and are not available online thereafter.

7.15.3 Attachments for inbound documents

Invoices with Attachments

An invoice can have multiple attachments such as delivery details, emails, fax, and so on. Ariba Network adds these attachments to a MIME message and sends the MIME message to the cXML Adapter for further processing. For inbound documents, the cXML Adapter supports attachments of all file types that are supported byAriba Network.


When the cXML Adapter downloads an inbound document (invoice, OC, or ASN) with attachments from Ariba Network, it receives the attachments as part of a MIME message. The cXML Adapter converts the cXML message to a message format that SAP Business Suite Add-On expects, encodes the attachments, and adds the attachments to the converted message. The converted message is sent to SAP Business Suite Add-On through SAP Process Integration.

7.16 Using endpoints for integration with SAP Process Integration for SAP Business Suite Add-On

The endpoints in Ariba Network manage and control the flow of data from Ariba Network to the various systems that are connected to it. The endpoint in Ariba Network acts as a document routing placeholder that ensures documents from Ariba Network are sent to the desired system. You can create endpoints in Ariba Network according to your business requirements.

For information about configuring endpoints for integration, see Using endpoint integration [page 157].

7.17 Using the SAP Process Integration KeyStore

The server and client certificates that cXML Adapter uses to connect to Ariba Network must be stored in the SAP Process Integration keystore. SAP Process Integration provides functionality to manage and administer authentication certificates and keystores. As part of this functionality, you can create keys and certificates in SAP Process Integration and store them in the SAP Process Integration Keystore. The keys and certificates that you create in SAP Process Integration Keystore are grouped bases on views. Therefore, you first need to create a view and then create the required keys and certificates under that view. After you have created the required certificates, you must get them signed by a trusted Certificate Authority (CA) to enable Ariba Network to successfully establish the SSL connection.

As a result, when SAP Process Integration sends or receives documents to/from Ariba Network, based on the channel configuration, the cXML Adapter initializes and creates the Ariba Network TrustStoreView and KeystoreView (only if client certificate is selected) and uses the certificates to ensure a successful SSL handshake.

7.17.1 Requirements

In the communication channel for all the inbound and outbound transactions, for Trust Store View and KeyStore View (only if you are using client certificate), specify the names of the Views that store the Server certificate and Client certificate respectively. For more information, see How to configure communication channels to use SAP Process Integration Keystore [page 353].

352 PUBLIC


On

7.17.2 How to configure communication channels to use SAP Process Integration Keystore

Procedure

1. Open the required communication channel.2. Under Authentication, for the Trust Store View parameter, enter the name of the view that contains the

server certificate.3. To use client certificate for authentication to Ariba Network buyer account, for Credential Mode, select

Client certificate from the dropdown.4. For the KeyStore View parameter, enter the name of the view that contains the client certificate.5. Click Save.6. Repeat this configuration for all the inbound and outbound transactions.


8 Topics about testing the Ariba Network adapter for SAP NetWeaver

Testing the configuration [page 354]

Monitoring the cXML Adapter [page 358]

Deploying the project [page 359]

8.1 Testing the configuration

This section provides instructions on how to test your configuration.

To troubleshoot any errors you encounter, you can use the SAP Process Integration Runtime Work Bench (from the web UI) and the Integration Engine Monitor (transaction SXMB_MONI from the SAP ERP GUI) to track the exchanged messages. You can also view the log files in the adapter log directory on SAP Process Integration.

For more information about error handling, see the section Understanding error handling [page 355].

Before beginning, be sure that you have at least one fully configured Ariba Network supplier relationship. For more information about creating a supplier relationship, see the topic Configuration in the Ariba Network Integration Guide.

Testing Processes

After you have successfully deployed and configured the Ariba Network adapter for SAP NetWeaver, you should run test transactions to ensure that Ariba Network and your SAP ERP system are communicating properly in both directions. To test processes:

● Send a purchase order from SAP ERP to Ariba Network.● Run a getPending transaction by creating an invoice in Ariba Network and then sending it to SAP ERP.

Related Information

How to send a purchase order for testing [page 355]How to run a getPending transaction for testing [page 355]Understanding error handling [page 355]


Topics about testing the Ariba Network adapter for SAP NetWeaver

8.1.1 How to send a purchase order for testing

Procedure

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 the SAP Process Integration. The Ariba Network adapter for SAP NetWeaver on SAP Process Integration converts the IDoc to cXML, and then sends the cXML to Ariba Network.2. Verify that the messages are available in the SAP Process Integration monitoring tools (SAP Process

Integration Runtime Workbench and Integration Engine Monitor).3. Log on to Ariba Network 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.

8.1.2 How to run a getPending transaction for testing

Procedure

1. Create a test invoice in Ariba Network.If the system is working properly, then the Ariba Network adapter for SAP NetWeaver downloads the Invoice from Ariba Network, converts the cXML to IDoc, and then sends the IDoc to SAP ERP.2. Verify that the messages are available in the SAP Process Integration monitoring tools (SAP Process

Integration Runtime Workbench and Integration Engine Monitor).3. Check to see that the invoice is accepted in SAP ERP.

Results

If these two checks are successful, the inbound connection is working properly.

8.1.3 Understanding error handling

The SAP Process Integration 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

Setting up Ariba Network adapter for SAP NetWeaverTopics about testing the Ariba Network adapter for SAP NetWeaver PUBLIC 355

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 (Ariba Network-> SAP ERP), the Email notification is used to send an email when an error occurs (mainly connection issues). This is because during the pull (getPending), SAP Process Integration 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 (SAP ERP -> Ariba Network), the sending operation initiated by SAP Process Integration is synchronous, and if any exception occurs, it is related to a message from SAP Process Integration. In this case, the Ariba Network adapter for SAP NetWeaver 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 PI). The Ariba Network adapter for SAP NetWeaver 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 Network, if available (for example, in case of documents refused by Ariba Network).

Related Information

Understanding error and status codes [page 356]Understanding email notifications [page 357]

8.1.3.1 Understanding error and status codes

The cXML Adapter notification emails include an Ariba Network adapter for SAP NetWeaver 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 code range:

● 2xx denotes success● 4xx denotes permanent errors● 5xx denotes transient errors

For more information about the different cXML status codes that can be found in the notification emails, see the section Protocol Specification Response in the chapter cXML Basics in the cXML User’s Guide.

The following table describes the possible general error codes (Ariba Network adapter for SAP NetWeaver error codes) in cXML adapter notifications:

Application Errors:

Status Text

ERR101 Invalid Configuration Parameter. Trusted certificates not installed properly.

ERR102 Incorrect Client Certification



Status Text

ERR201 Authentication Failed on ASN

ERR202 ASN Internal Server Error

ERR203 Send cXML to AN Failed (Invalid Request)

ERR204 Send cXML to AN Failed (Temporary Error)

ERR205 Send cXML to AN Failed (Unrecoverable Error)

ERR301 Get Profile Transaction Failed

ERR302 Get Pending Transaction Failed

ERR303 Outbound Transaction Failed

ERR401 Invalid Outbound Message (PI -> ASN)

ERR402 Invalid Inbound Message (ASN -> PI)

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

SAP ERP Errors:

Status Text

ECC101 Configuration Load Failed

ECC102 IO Error

ECC103 Ariba Network Not Available

8.1.3.2 Understanding email notificationsThe following are the different parts of an error notification email:

● Date: The date and time of the error.● Error: The Ariba Network adapter for SAP NetWeaver Error code. For a list of general error codes, see the

Application Errors, Runtime Error, and ERP 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 Network, and the response message from Ariba Network is not available

○ Details of the cXML response, if the response from Ariba Network 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/[email protected].

● [Response Status Code]: The cXML response status code, like 401. For a list of possible status messages, see the section Protocol Specification Response in the chapter 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.

8.2 Monitoring the cXML Adapter

The monitoring of the cXML Adapter includes a monitoring capability that continuously monitors the status of the deployed inbound and outbound channels (transactions). As part of this implementation, if a channel stops or is stuck in processing, the monitoring capability of the adapter is notified and it automatically restarts that channel without any manual intervention. For example, if invoices are not getting downloaded from Ariba Network, the monitoring capability checks the status of the invoice channel. If the channel has stopped or is stuck in processing, the monitoring capability restarts the channel to ensure that the adapter can continue to download invoices from Ariba Network.

Related Information

Monitoring the cXML Adapter from Runtime Workbench [page 358]Configuring logging for the cXML Adapter [page 359]

8.2.1 Monitoring the cXML Adapter from Runtime Workbench

After you deploy the Ariba Network adapter for SAP NetWeaver on SAP Process Integration and configure the inbound and outbound transaction scenarios in the Integration Directory, communication channels are created for each inbound and outbound transaction in the Integration Directory. These communication channels are



displayed within the Runtime Workbench from where an SAP Process Integration administrator can monitor these channels. An SAP Process Integration administrator can start or stop channels from the Runtime Workbench as required without having the need to access the Integration Directory. For example, if an administrator stops an inbound channel that downloads invoices from Ariba Network, the channel stops to run as indicated by the status on the user interface and no invoices are downloaded.

NoteIf the cXML Adapter stops downloading documents from Ariba Network, the SAP Process Integration administrator needs to login to the Runtime Workbench and stop/start the respective channel. For example, if the adapter stops downloading invoices from Ariba Network, an administrator must login to the Runtime Workbench and start the invoice communication channel to ensure that the adapter starts downloading invoices.

8.2.2 Configuring logging for the cXML Adapter

Configure logging to send log entries for the cXML adapter to a separate file.

The log level can remain Error when running in a production environment, but SAP Ariba recommends that you change the log level to Info.

You can also find out about the version of the Ariba Network adapter for SAP NetWeaver.

1. Log in to the SAP Process Integration log administration section at http://XI_hostname_server:XI_port/nwa/logs.

2. Click the Log Configuration link.3. Select Tracing Locations from the Show dropdown.4. In the Location field, enter comariba and click Go. All the adapter classes for SAP Ariba appears in the

Root Location list.5. Select the node (package) for the adapter class that you want to enable the log files.6. Change the severity level from Error to Info/Debug in the Severity dropdown, and then click Save

Configuration in the toolbar.

NoteFor additional information, see the Ariba Network Integration 1.0 for SAP Business Suite http://help.sap.com/se4aribanet10.

8.3 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 Process Integration Export files (tpz files) using SAP Process Integration Builder. SAP Process Integration Builder contains two parts:

● Design tool, which contains interface objects, mapping objects and integration processes


http://help.sap.com/se4aribanet10

http://help.sap.com/se4aribanet10

● Configuration tool, which contains business services and routing rules. For more information, see the SAP Process Integration 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 Process Integration documentation.

Each tpz file works as a single unit within SAP Process 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.

8.3.1 Ariba Network certification

SAP Ariba must certify any Ariba Network adapter for SAP NetWeaver that works with Ariba Network. Certification is the process by which SAP Ariba’s Global Solutions Organization (GSO) inspects and approves the Ariba Network adapter for SAP NetWeaver, the cXML documents it generates, and its connection to Ariba Network.

In its default state, the Ariba Network adapter for SAP NetWeaver is Ariba Network-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 Network Integration Guide. The guide describes how to download certification files from SAP Ariba Connect and provides instructions to guide you through the certification process.

8.3.2 Downloading the Ariba Network Integration Guide from Ariba Connect

Procedure

1. Go to (http://connect.ariba.com ) and log in.

2. On the navigation panel on the left, click Product Info Ariba Network Ariba Network.3. Under Documentation in the new page, click Supplier Connectivity to download the Supplier

Connectivity.zip file.

4. Extract the IntegrationGuide.pdf file from the downloaded ZIP file.



http://help.sap.com/disclaimer?site=http%3A%2F%2Fconnect.ariba.com

9 cXML Adapter parameters

This section describes common, inbound, and outbound parameters for the cXML Adapter.

Common parameters [page 361]

Inbound parameters [page 364]

Outbound parameters [page 365]

Configuring retry attempts [page 365]

Configuring proxy server parameters [page 366]

9.1 Common parameters

Parameter Name Usage Type Data Type Value Description

Adapter Status

Mode required string Test/Production

Deployment mode of the adapter. Default value: Test

Status required string Active/Inactive

The status of the adapter. Default value: Active

Authentication

Credential Mode

required string Shared secret/Client certificate

Authentication method on Ariba Network. Default value: Client certificate

Credential Domain

required string NetworkId/NetworkUserId/DUNS

The domain for the Buyer's credential. Default value: NetworkId

Credential required string The buyer's credential on Ariba Network. The value can be NetworkId, NetworkUserId, or DUNS, depending on the credential domain selected.

Shared Secret Password

optional string The buyer's shared secret on Ariba Network. This parameter is only required when parameter credentialMode is set as Shared secret.

Port required integer HTTPS port. This parameter is only required when parameter credentialMode is set as Client certificate. Default value: 443

Setting up Ariba Network adapter for SAP NetWeavercXML Adapter parameters PUBLIC 361


KeyStore View required string Indicates the name of the view that contains all the keys/certificates required for authentication between the cXML Adapter and SAP Ariba buyer.

cXML Configuration

AN ID required string Ariba Network ID. Default value: AN01000000001

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.025 or higher

The version number of the cXML document data definition to be used to generate the cXML documents exchanged with Ariba Network. This version number is used in the DOCTYPE entity of the cXML documents.

NoteEnsure that you use only the following cXML versions for:

● SAP Ariba cloud integration release 8.0: 1.2.030

● SAP Ariba cloud integration release 9.0: 1.2.031

● SAP Ariba cloud integration release 9.0 SP1: 1.2.033

● SAP Ariba cloud integration release 9.0 SP2: 1.2.034 or higher

Use XML Validation

optional boolean true/false A flag that specifies whether or not 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.


cXML Adapter parameters


Use SAP Add on Suite

Only required for SAP Business Suite Add-On integrations

boolean When this option is enabled, the cXML Adapter integrates Ariba Network with the SAP Business Suite AddOn component available in your SAP ERP system.

documentExpiryPeriod

required integer minimum 1 and max 360

Specify the expiry time for a document in hours after which the document can be resent from or to Ariba Network. The default value is 24 hours. You can set a minimum value of one hour and the maximum value as 360 hours.

Email Notification

Use Email Notifications

required boolean true/false A switch to turn on/off email notification. Default value: false

SMTP Server Host

required string The SMTP server IP address or host name.

Sender Address

required string The email account for sending email.

Recipient Address

required string The email account for email receiver.

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 Authentication

required boolean true/false A flag that represents whether or not the email server requires authentication for sending email. Default value: false

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.


9.2 Inbound parameters


cXML Configuration

GetProfile URL

required string URL used to send ProfileRequest.Default value: https://service.ariba.com/service/transaction/cxml.asp

GetProfile Interval (Minutes)

required integer Poll interval of profileRequest expressed in minutes. Default value: 60

GetPending Interval (Minutes)

required integer Poll interval of getPendingRequest expressed in minutes. Default value: 15

Max Documents in GetPending

required integer Max number of Documents that can be received from the pending queue in a single getPending request. Default value: 2

StatusUpdateRequestRetryCount

required integer Number of times the status update request is to be retried if the first status update request failed. Default value: 0

StatusUpdateRequestRetryInterval (Minutes)

required integer Time to wait before sending the next status update, expressed in minutes. Default value: 0

SystemID for GetPending

optional string The system ID for your ERP application

This parameter is required only if you are using multiple ERP applications to connect to Ariba Network

The system ID for your ERP system must match the system ID config-ured in your Ariba Network buyer account.

Timeout required integer 5 minutes When the cXML Adapter is downloading documents from Ariba Network, if the connection is lost during the download, the cXML adapter will wait for the number of minutes specified as the value for this parameter before exiting.

Inbound Request Type




Inbound Request Type

required string One of the following:

● ConfirmationRequest● InvoiceDetailReques

t● ShipmentNoticeReque

st● PayMeNowRequest

The request type for Inbound. Default value: ConfirmationRequest

9.3 Outbound parameters


cXML Configuration

GetProfile URL required string URL used to send ProfileRequest. Default value: https://service.ariba.com/service/transaction/cxml.asp

GetProfile Interval (Minutes)

required integer Poll interval of profileRequest expressed in minutes. Default value: 60

Outbound Request Type

Outbound Request Type

required string One of following:

● OrderRequest● ChangeOrderRequ

est● InvoiceUpdateRe

quest● PaymentRequest● PaymentRemittan

ceRequest

The request type for Outbound. Default value: OrderRequest

9.4 Configuring retry attempts

You can configure the interval and the number of times the adapter framework will attempt to resend a message to an adapter from the SAP Process Integration Administrator. This includes the interval between


retry attempts for outbound messages sent by SAP Process Integration to the cXML adapter, and the number of inbound documents sent by the cXML adapter to SAP Process Integration. For more information on how to configure a message to be retried, see the SAP Process Integration 7.1 documentation.

9.5 Configuring proxy server parameters

The Ariba Network adapter for SAP NetWeaver 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)

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) YesEnables or disables the use of the proxy server for remote communication with Ariba Network

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 Authentication Method

List None (default) Basic Digest NTLM

Indicates the method used for authentication on the proxy server. If None, the proxy 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.



10 SAP Ariba objects

This appendix describes the SAP development objects provided by SAP Ariba as part of the SAP integration. The audience for this appendix includes:

● BASIS administrators who import SAP Ariba’s SAP transports and need to see the list of objects they are importing.

● ABAP developers who are responsible for customizing the SAP Ariba objects.

SAP Ariba namespace certification [page 367]

/ARBA/COMMON_OBJECTS package [page 368]

/ARBA/PURCHASEORDER package [page 370]

/ARBA/CHANGEPURCHASEORDER package [page 370]

/ARBA/ERPINVOICE package [page 371]

/ARBA/INVOICESTATUSUPDATE package [page 372]

/ARBA/PAYMENTPROPOSAL package [page 373]

/ARBA/RECEIPT package [page 374]

/ARBA/REQUISITION package [page 374]

/ARBA/INVOICE package [page 375]

/ARBA/CANCEL_ASN package [page 377]

10.1 SAP Ariba namespace certification

The namespace /ARBA/ is registered and all SAP objects delivered by SAP Ariba are renamed from Z_<object name> to /ARBA/<object name>. For example, the function module called Z_ARIBA_INVOICE_STATUS_UPDATE is renamed to /ARBA/INVOICE_STATUS_UPDATE.

The SAP Process Integration content is changed by importing the RFCs and ABAP objects renamed with the /ARBA/ namespace into SAP Process Integration.

NoteStarting SAP Ariba Cloud Integration Release 1.0, all the RFC and SAP objects have been renamed to /ARBA/namespace. You cannot edit the main code without an access key from the SAP marketplace. However, you can customize the code using the BADI hooks in the program that Ariba provides you for customization.

Setting up Ariba Network adapter for SAP NetWeaverSAP Ariba objects PUBLIC 367

10.2 /ARBA/COMMON_OBJECTS package

The /ARBA/COMMON_OBJECTS package contains SAP Ariba development objects for Ariba Network adapter for SAP NetWeaver for SAP Process Integration objects.

Function Groups and Modules

The function groups in the /ARBA/COMMON_OBJECTS package are:

/ARBA/COMMON_OBJECTS Function Groups

Function Group Description

/ARBA/LOOKUP Lookup function modules

/ARBA/TABLE_MAIN Extended table maintenance (Generated)

/ARBA/COMMON_OBJECTS Function Modules

Function Module Description

/ARBA/RFC_READ_TABLE External access to R/3 tables via RFC

/ARBA/PREFILTER_ADAPTER Retrieves pre-filtering restrictions

/ARBA/WHERE_CONDITION_FILTER SAP Ariba function to construct where condition

/ARBA/ORBIAN_INFO_GETDETAIL Payment proposal ID and dynamic discount credit memo for Orbian Integration

/ARBA/READ_BSIK_BKPF Read BSIK and BKPF data

Tables

The tables for the /ARBA/COMMON_OBJECTS package are:

/ARBA/COMMON_OBJECTS Tables

Table Description

/ARBA/AN_VENDOR Ariba Network vendor table

/ARBA/PARAM_TAB SAP Ariba table to store configurable parameters

/ARBA/AN_ERPINV Stores invoices created in SAP ERP and SAP S/4HANA which are sent to Ariba Network

/ARBA/LOOKUPTAB Tables read by the function module /ARBA/RFC_READ_TABLE

/ARBA/PROXYPARAM Table to store proxy parameters for ISU, PP, ERP Invoice, and Receipts


SAP Ariba objects

NoteThe ABAP function /ARBA/invoice_get_details is designed to use the vendors from the /ARBA/AN_VENDOR table while selecting data for invoice details. Use the transaction SM30 to generate table maintenance objects to maintain records in this table.

You must maintain the following entries in the /ARBA/PARAM_TAB table using the transaction code SM30:

Variable Name Field Name Sign OPTION Select Value

GROSS_INV_RECEIPT B~BLART I EQ RE

NONPO_INVOICE B~BLART I EQ KR

PAYMENT_POSTING BLART I EQ KP

VENDOR_PAYMENT BLART I EQ KZ

VENDOR_PAYMENT B~BLART I EQ KZ

VENDOR_PAYMENT H~BLART I EQ KZ

ACCRUAL_TAX_CONDITION MW1 I EQ MW1

ACCRUAL_TAX_CONDITION MW2 I EQ MW2

You must maintain the following entries in the /ARBA/AN_VENDOR table using the transaction code SM30:

Fieldname Value

BUKRS 3000

LIFNR 1000

Structures

The structures for the /ARBA/COMMON_OBJECTS package are:

/ARBA/COMMON_OBJECTS Structures

Structure Description

/ARBA/WTAB Table Structure for "WHERE (itab)" statement

/ARBA/RFC_READ_TABLE Structure to support RFC READ TABLE for Unicode Systems


10.3 /ARBA/PURCHASEORDER package


/ARBA/PURCHASEORDER Purchase Order Adapter Objects

Function Module Name Description

/ARBA/PO_ACCOUNTING_INFO Accounting Information for PO

/ARBA/PO_SERVICE_INFO Service Purchase Order Details

Structure Name Description

/ARBA/EKKN Purchase Order Accounting Details

/ARBA/EKKN_SERVICE Purchase Order Account Assignment Structure

/ARBA/EKPO Purchase Order Line Item Details

/ARBA/EKPO_SERVICE Service Line item Details

/ARBA/ESKL Purchase Order Account Assignment Service Line

/ARBA/ESLH Purchase Order Header Service Structure

/ARBA/ESLL Purchase Order Service Line item Detail

Table Type Description

/ARBA/EKKN_SERVICE_T Table Type For Service Purchase Order Accounting Details

/ARBA/EKKN_T Table Type For Purchase Order Accounting Detail

/ARBA/EKPO_SERVICE_T Table Type For Service Line Item Details

/ARBA/EKPO_T Table Type For Purchase Order Line Item Detail

/ARBA/ESKL_T Table Type - Purchase Order Account Assignment Service Line

/ARBA/ESLH_T Table Type For Purchase Order Header Service Structure

/ARBA/ESLL_T Table Type For Purchase Order Service Line item Detail

/ARBA/RFC_DB_FLD_T Table Type For Field Names

/ARBA/TAB512_T Table Type for 512 Byte Field Structure

10.4 /ARBA/CHANGEPURCHASEORDER package


/ARBA/CHANGEPURCHASEORDER Change Purchase Order


SAP Ariba objects


/ARBA/PO_GET_DETAIL Change Purchase Order Get Detail


/ARBA/BAPIEKKOL Transfer Structure: Display/List: PO Header with Vendor Name

/ARBA/BAPIEKPO Transfer Structure: Display/List PO Item

/ARBA/BAPIEKKN Transfer Structure: Display/List: PO Account Assignment

/ARBA/BAPIESKL Communication Structure: Account Assignment Values: Service Line

/ARBA/BAPIESLL Communication Structure: Service Line


/ARBA/BAPIEKET_T Purchase Order Schedule Lines

/ARBA/BAPIEKKN_T Purchase Order Accounting Details

/ARBA/BAPIEKPO_T Transfer Structure: Display/List PO Item

/ARBA/BAPIESKL_T Service Purchase Order Account Assignment Details

/ARBA/BAPIESLL_T Service Purchase Order Detail

/ARBA/PO_ACCOUNT_T SAP Ariba Purchase Order Accounting Details

/ARBA/PO_ITEMS_T SAP Ariba Purchase Order Items

/ARBA/PO_SERVICEACCOUNT_T Purchase Order Service Account Details

/ARBA/PO_SERVICEITEMS_T SAP Ariba Service Purchase Order Item Detail

10.5 /ARBA/ERPINVOICE package


/ARBA/ERPINVOICE ERP Invoice Adapter objects


/ARBA/INVOICE_GET_DETAILS SAP Ariba Invoice FI documents to AN

Program Name Description

/ARBA/ERPINVOICE_EXPORT ABAP proxy for Invoice Interface

Table Name Description

/ARBA/TAXCAT_MAP SAP Ariba Tax code to Tax Category Map



/ARBA/INVOICE_HEADER_DETAILS SAP Ariba ERP-Initiated Invoice Header details

/ARBA/INVOICE_LINE_DETAILS SAP Ariba ERP-Initiated Invoice line item details

/ARBA/BSEG ERP Invoice Line Item Details

/ARBA/BSIK ERP Invoice Header Details

/ARBA/BSET Invoice Tax Data


/ARBA/INVOICE_HEADER_DETAILS_T Invoice Header details

/ARBA/INVOICE_LINE_DETAILS_T Invoice line item details

/ARBA/BSEG_T ERP Invoice Line Item Details

/ARBA/BSIK_T Invoice Details

/ARBA/BSET_T Invoice Tax Data

10.6 /ARBA/INVOICESTATUSUPDATE package


/ARBA/INVOICESTATUSUPDATE Invoice Status Update function group


/ARBA/INVOICE_STATUS_UPDATE SAP Ariba Invoice status update


/ARBA/INVSTATUPDT_EXPORT Program for Calling Invoice Status Update proxy


/ARBA/CONTROL_RECORD IDOC Control Record for Rejected Status Invoices

/ARBA/DATA_RECORD IDOC Data Record for Rejected Status Invoices

/ARBA/FULL_PAID_INVOICE Fully Paid Invoices

/ARBA/INVOICE Invoice Detail Structure

/ARBA/INVOICE_STATUS Structure for Invoice status update

/ARBA/PARTIAL_PAYMENTS Partial Payment Details

/ARBA/PARTIAL_PAID_INVOICE Partially Paid Invoice Details

/ARBA/REVERSED_INVOICE Invoice Status Update Reversal Documents


SAP Ariba objects


/ARBA/REVERSED_PAYMENTS Reversed Payments Details


/ARBA/CONTROL_RECORD_T IDOC Control Record for Rejected Status Invoices

/ARBA/DATA_RECORD_T IDOC Data Record for Rejected Status Invoices

/ARBA/FULL_PAID_INVOICE_T Fully Paid Invoices

/ARBA/INVOICE_T Invoice Detail Structure

/ARBA/INVOICE_STATUS_T Structure for Invoice status update

/ARBA/PARTIAL_PAYMENTS_T Partial Payment Details

/ARBA/PARTIAL_PAID_INVOICE_T Partially Paid Invoice Details

/ARBA/REVERSED_INVOICE_T Reversed Invoices

/ARBA/REVERSED_PAYMENTS_T Reversed Payments

10.7 /ARBA/PAYMENTPROPOSAL package


/ARBA/PAYMENTPROPOSAL Payment Proposal Adapter Objects


/ARBA/PAYMENT_PROPOSAL Payment Proposal RFC


/ARBA/PAYMENTPROPOSAL_EXPORT Payment Proposal Program (Proxy)


/ARBA/ACCOUNTINGDOCUMENT Payment proposal accounting data

/ARBA/PARTIALINVOICE Invoice detail structure for payment proposal customer exit

/ARBA/PARTIALPAYMENTS Partial payment structure for payment proposal customer exit

/ARBA/PAYMENTPROPOSAL SAP Ariba customer exit for payment proposal Information

/ARBA/PAYMENT_PROPOSAL Structure used in payment proposal RFC Ariba adapter

/ARBA/PAYEE Structure for payment proposal payee

/ARBA/PAYER Structure for payment proposal payer

/ARBA/REC_BANK Payment proposal bank details



/ARBA/ACCOUNTINGDOCUMENT_T Payment proposal accounting data

/ARBA/PARTIALINVOICE_T Partial invoice details

/ARBA/PARTIALPAYMENTS_T Payment proposal partial payments

/ARBA/PAYMENTPROPOSAL_T Payment proposal

/ARBA/PAYMENT_PROPOSAL_T Payment proposal

/ARBA/PAYEE_T Payment proposal payee

/ARBA/PAYER_T Payment proposal payer

/ARBA/REC_BANK_T Payment proposal bank details

/ARBA/PP_TAX_INFO_T Payment proposal tax details

/ARBA/PP_BSET_T Payment proposal tax data document segment details

10.8 /ARBA/RECEIPT package


/ARBA/RECEIPT_PUBLISH Proxy for Receipt Export


/ARBA/PO_DETAIL SAP Ariba Purchase Order Detail Structure

/ARBA/RECEIPT SAP Ariba Material Document Structure


/ARBA/PO_DETAIL_T SAP Ariba Purchase Order Detail Structure

/ARBA/RECEIPT_T SAP Ariba Material Document

/ARBA/GR_HEADER_T Goods Receipt Header

/ARBA/GR_ITEMS_T Goods Receipt Items

10.9 /ARBA/REQUISITION package


/ARBA/REQPARAM Extended Table Maintenance (Generated)


SAP Ariba objects


/ARBA/REQUISITION_EXPORT Requisition Export (Proxy)

Table Name Description

/ARBA/REQPARAM Table to store Ariba Requisition Parameters


/ARBA/REQUISITION Requisition Details


/ARBA/REQUISITION_T Requisition

10.10 /ARBA/INVOICE package

This package is applicable for invoices and credit memos.

BAdI name Description

/ARBA/BADI_CREDIT_MEMO_CANCEL Use this BAdI to modify the credit memo cancelations sent from Ariba Network.


/ARBA/DT_ARIBA_ATTACHMENT_CON1 Structure for the invoice attachment.





/ARBA/DT_ARIBA_ATTACHMENT_CON6 Data type for the discounts in credit memos having attachments.

/ARBA/DT_ARIBA_ATTACHMENT_CON Structure for the invoice attachment.

/ARBA/ACCOUNT_DATA Structure for the accounting information in invoices.

/ARBA/DT_CREDIT_MEMO_ATTACHME1 Structure for the credit memo attachment.



/ARBA/DT_CREDIT_MEMO_ATTACHME4 Data type for the discounts in credit memos having attachments.






/ARBA/DT_CREDIT_MEMO_ATTACHME Structure for the credit memo attachment.

/ARBA/DT_DEEP_DISCOUNT_CREDIT Structure for the discounts in the credit memo.

/ARBA/DT_DEEP_DISCOUNT_CREDIT1 Data type for the discounts in the credit memos.

/ARBA/DT_DEEP_DISCOUNT_CREDIT2 Structure for the discounts in the credit memo.






/ARBA/EXCHANGE_FAULT_DATA5 Structure for the credit memo.

/ARBA/EXCHANGE_LOG_DATA5 Structure for the credit memo logs.

/ARBA/MT_CREDIT_MEMO_ATTACHMEN Structure for the credit memo attachment.

/ARBA/MT_DEEP_DISCOUNT_CREDIT Message type for discounts in credit memo having attachments


/ARBA/DT_ARIBA_ATTACHMENT_TAB1 Table type for invoice attachments

/ARBA/DT_ARIBA_ATTACHMENT_TAB2 Table type for invoice attachments

/ARBA/DT_ARIBA_ATTACHMENT_TAB Table type for invoice attachments

/ARBA/DT_CREDIT_MEMO_ATTAC_TAB Table type for credit memo attachment

/ARBA/DT_CREDIT_MEMO_ATTAC_TAB1

Table type for credit memo attachment





/ARBA/DT_DEEP_DISCOUNT_CRE_TAB Table type for the discounts in the credit memo

/ARBA/DT_DEEP_DISCOUNT_CRE_TAB1

Table type for the discounts in the credit memo





/ARBA/EXCHANGE_LOG_DATA_TAB5 Table type for credit memo logs


SAP Ariba objects

Related Information

Invoice [page 36]Scheduled payments and dynamic discounting [page 46]

10.11 /ARBA/CANCEL_ASN package

Class Description

/ARBA/CL_BADI_ASN_CNCL Class for ship cancel notice

/ARBA/CL_ES_ASN_CANCEL Class for ship cancel notice

BAdI implementation Description

/ARBA/BADI_ASN_CNCL BAdI for ship cancel notice

Related Information

Ship notice [page 28]


11 Revision history

The following table provides a brief history of the updates to this guide. SAP Ariba updates the technical documentation for its cloud solutions if

● software changes delivered in service packs or hot fixes require a documentation update to correctly reflect the new or changed functionality;

● the existing content is incorrect or user feedback indicated that important content is missing.

SAP Ariba reserves the right to update its technical documentation without prior notification. Most documentation updates will be made available in the same week as the software service packs are released, but critical documentation updates may be released at any time.

Cloud integration release

Month/year of update

Updated chapter/section Short description of change

SAP Ariba cloud integration hot fix release

March 2019 All Full document edit and cleanup

June 2019 Multiple sections Added information about ERP-initiated service entry sheets


Revision history

Important Disclaimers and Legal Information

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

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

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

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

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

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

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

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Setting up Ariba Network adapter for SAP NetWeaverImportant Disclaimers and Legal Information PUBLIC 379

www.ariba.com

Copyright © 2021 Ariba, Inc. All rights reserved.

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

Ariba, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in the documentation. The information contained in the documentation is subject to change without notice.

Ariba and Ariba products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Ariba, Inc. in the United States and other countries. Please see http://www.ariba.com/legal/trademarks for additional trademark information and notices.

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

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

U.S. Patent Nos. 6,199,050, 6,216,114, 6,223,167, 6,230,146, 6,230,147, 6,285,989, 6,408,283, 6,499,018, 6,564,192, 6,584,451, 6,606,603, 6,714,939, 6,871,191, 6,952,682, 7,010,511, 7,047,318, 7,072,061, 7,084,998; 7,117,165; 7,225,145; 7,324,936; 7,536,362; 8,364,577; and 8,392,317. Patents pending.

Certain Ariba products may include third party software or other intellectual property licensed from a third party. For information regarding software or other intellectual property licensed from a third party, go to http://www.ariba.com/copyrights.cfm.

THE BEST RUN

http://www.ariba.com

http://www.ariba.com/legal/trademarks

http://www.ariba.com/legal/trademarks

http://www.ariba.com/copyrights.cfm

Setting up Ariba Network adapter for SAP NetWeaver

Documents

Transcript of Setting up Ariba Network adapter for SAP NetWeaver