Ariba Network Adapter for SAP NetWeaver Setup Guide

Ariba Cloud Integration 6.0 Document Version: 4 – December 2015

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network

Content

Ariba Network Adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Data Flow and Data Element Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Supported cXML Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 cXML Adapter Document Transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Setting Up the Ariba Network Adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Configuring the Ariba Network Adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Installing the Network Adapter Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 About Configuring Security Certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Importing Security Certificates into the Java JRE Keystore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Importing Security Certificates into the Java JRE TrustStore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Installing Client Certificates on Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 About Deploying the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Deploying the cXML Adapter Using JSPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Upgrading the cXML Adapter Using JSPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Installing Additional Resources for the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Undeploying the cXML Adapter using the Textconsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Deploying the cXML Adapter Using the textconsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Setting Log Configuration Parameters for the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 About Configuring the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . 46 About Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . 46 cXML Interfaces Supported in the Ariba Cloud Integration Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Features Available in the Ariba Cloud Integration Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Steps to Install the Ariba Network Adapter for SAP NetWeaver PI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Installing the SAP ERP Transports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Upgrading to a Higher Version of the Ariba Network Adapter for SAP NetWeaver Transports. . . . . . . . . 52 Changes Required on your SAP ERP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Changes Required on your SAP NetWeaver PI System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Migrating the Design Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Updating the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

2

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Content

Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Configuring SLD and Transaction Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 About Configuring the System Landscape Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Importing Ariba Network Product and Component Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Defining Technical and Business System for Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Defining the Business System for Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Defining Technical and Business System for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Defining the Business Landscape for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 About Configuring Transaction Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Importing the Design Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 About Configuring ERP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Assigning Business Systems in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Creating Communication Channels for ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Creating the IDoc Receiver Communication Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Creating the RFC Receiver Communication Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Configuring IDoc Metadata (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Configuring SAP NetWeaver PI Value Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Configuring Units of Measure (UOM) Code Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Configuring Language Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Configuring TimeZone Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Configuring Global Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 Configure the Mappings Between Business System and Logical System Names. . . . . . . . . . . . . . . . 76 Configuring Currency Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Maintaining the Value Mapping to Support Logical Systems in SAP NetWeaver PI. . . . . . . . . . . . . . . 78 Creating a New Value Mapping Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Configuring Integration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 About Configuring Integration Scenarios in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . 80 Configuring the Software Component Version for Communication Channel Templates . . . . . . . . . . . 82 Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Transferring the Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 About Configuring the Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Configuring Communication Channels for the Purchase Order Integration Scenario. . . . . . . . . . . . . 87 Configuring Interface Determination Settings for the Purchase Order Integration Scenario. . . . . . . . 88 Activating the Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Change Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Reconfiguring the SAP Partner Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 About Configuring Implicit Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Removing Change Order Configurations from Your Ariba Solution. . . . . . . . . . . . . . . . . . . . . . . . . . 93 Migrating Change Order Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Ariba Network Adapter for SAP NetWeaver Setup Guide Content

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

3

Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Transferring the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 About Configuring the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Configuring Communication Channels for the Order Confirmation Integration Scenario. . . . . . . . . . .99 Configuring Receiver Determination Settings for the Order Confirmation Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Configuring Interface Determination Settings for the Order Confirmation Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Activating the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Additional Configuration Tasks for the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . 102 Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Transferring the Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 About Configuring the Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Configuring Communication Channels for the Ship Notice Integration Scenario. . . . . . . . . . . . . . . .106 Configuring Receiver Determination Settings for the Ship Notice Integration Scenario. . . . . . . . . . . 107 Configuring Interface Determination Settings for the Ship Notice Integration Scenario. . . . . . . . . . .108 Activating the Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Ship Notice Integration Scenario to Support Creation of a Single Ship Notice Against Multiple Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Transferring the Ship Notice Integration Scenario for Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . 111 About Configuring the Ship Notice Integration Scenario for Multiple POs. . . . . . . . . . . . . . . . . . . . . 112 Configuring Communication Channels for the Ship Notice Integration Scenario with Multiple POs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Configuring Receiver Determination Settings for the Ship Notice Integration Scenario with Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 Configuring Interface Determination Settings for the Ship Notice Integration Scenario with Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Activating the Ship Notice Integration Scenario for Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Configuring the Ship Notice Integration Scenario to Receive Ship Notices with Zero Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Service Sheet and Service Sheet Response Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Transferring Service Sheet and Service Sheet Response Scenarios. . . . . . . . . . . . . . . . . . . . . . . . .118 About Configuring the Service Sheet and Service Sheet Response Integration Scenarios. . . . . . . . . 119 Configuring Communication Channels for the Service Sheet and Service Sheet Response Integration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Activating the Service Sheet and Service Sheet Response Integration Scenarios. . . . . . . . . . . . . . . 122 Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 Transferring the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 About Configuring the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Configuring Communication Channels for the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . 127 Configuring Receiver Determination Settings for the Invoice Integration Scenario. . . . . . . . . . . . . . 128 Configuring Interface Determination Settings for the Invoice Integration Scenario. . . . . . . . . . . . . . 129

4

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Content

Activating the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130 PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Transferring the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 About Configuring the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Configuring Communication Channels for the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . 134 Configuring Receiver Determination Settings for the PayMeNow Integration Scenario. . . . . . . . . . . 135 Configuring Interface Determination Settings for the PayMeNow Integration Scenario. . . . . . . . . . . 136 Activating the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 Transferring the Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 About Configuring the Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . .139 Configuring Interface Determination Settings for the Payment Remittance Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Activating the Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 Schedule Lines in Purchase Orders and Change Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Prerequisites to Enabling Schedule Lines in Purchase Orders from your SAP ERP System to Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Configuring the Purchase Order Integration Scenario to Support Schedule Lines. . . . . . . . . . . . . . .144 Blanket Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Configuring the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Transferring the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 About Configuring the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Configuring Communication Channels for the Order Inquiries Integration Scenario. . . . . . . . . . . . . 152 Configuring Interface Determination Settings for the Order Inquiries Integration Scenario. . . . . . . . 153 Activating the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 About Configuring the Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . 154 Configuring Communication Channels for the Scheduling Agreement Release Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Configuring Interface Determination Settings for the Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Activating the Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . 159 Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160 Transferring the Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 About Configuring the Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . 161 Configuring Communication Channels for the Invoice Status Update Integration Scenario. . . . . . . . 165 Configuring Interface Determination Settings for the Invoice Status Update Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Activating the Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Canceling MIRO Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Ariba Network Adapter for SAP NetWeaver Setup Guide Content

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

5

Transferring the ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 About Configuring the ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . 168 Configuring Communication Channels for the ERP-Initiated Invoice Integration Scenario. . . . . . . . . 172 Configuring Interface Determination Settings for the ERP-Initiated Invoice Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 Activating the ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Receipt Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Transferring the Integration Scenario for Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 About Configuring the Integration Scenario for Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Configuring Communication Channels the Receipts Integration Scenario. . . . . . . . . . . . . . . . . . . . 177 Configuring Interface Determination Settings for the Receipts Integration Scenario. . . . . . . . . . . . . 178 Activating the Receipts Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178 Additional Receipts Integration Requirement for SAP NetWeaver 7.1 EHP1. . . . . . . . . . . . . . . . . . . 179 Receipt Integration Scenario for Corrections and Returns in Receipts. . . . . . . . . . . . . . . . . . . . . . . . . 179 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Data Flow Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 cXML Changes to Support Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Configuring the Receipt Integration Scenario to Support Returns and Corrections. . . . . . . . . . . . . . 182 Receipt Integration Scenario for Purchase Orders with Multiple Accounting Assignments. . . . . . . . . . . 182 Activating the MM Multiple Account Assignments Enterprise Business Function. . . . . . . . . . . . . . . 183 Adding the Code in the BADI Implementation for MM Multiple Account Assignments. . . . . . . . . . . . 184 Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Transferring the Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 About Configuring the Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Configuring Interface Determination Settings for the Payment Proposal Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Activating the Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Enabling Quick Enablement for Payment Proposal Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . 190 Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Transferring the Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 About Configuring the Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . 192 Configuring Communication Channels for the Requisition Request Integration Scenario. . . . . . . . . 194 Configuring Interface Determination Settings for the Requisition Request Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Activating for the Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Request for Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196 Transferring the Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 About Configuring the Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Configuring Communication Channels for the Quotation Integration Scenario. . . . . . . . . . . . . . . . 200 Configuring Interface Determination Setting for the Quotation Integration Scenario. . . . . . . . . . . . 200 Activating the Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 Sourcing Award to Contract Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

6

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Content

Transferring the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . .202 About Configuring the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . 203 Configuring the Communication Channel for the Sourcing Award to Contract Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Configuring the Interface Determination Settings for the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Activating the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . 208 Change Purchase Order Implementation Redesigned. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Enabling Change Purchase Order Redesign. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Implementing the Redesigned Change Purchase Order Transaction. . . . . . . . . . . . . . . . . . . . . . . .209 Proxy Implementation for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Enabling Proxy Implementation for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Advanced Configuration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Linking Multiple SAP instances with Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Document Routing Mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Multi-ERP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Configuring Supplier Quick Enablement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Customizing Data Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Downloading Mapping Workbooks from Connect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Enabling Migration of Mapping Customization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Enabling Support for Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Attachments for Outbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Attachments for Inbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Managing Email Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Support for Proxy ByPass. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 HTTPS Support for Attachment Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Configuring Proxy Server ByPass for Attachment Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Troubleshooting Proxy Server ByPass for Attachment Processing. . . . . . . . . . . . . . . . . . . . . . . . . 227 Support for 2-Way Match. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Using Endpoint Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Using Endpoints for Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229 Enabling Endpoint Integration in SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Endpoint Integration for Multiple ERP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Using the SAP NetWeaver PI KeyStore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Configuring the cXML Adapter to Use the SAP NetWeaver PI Keystore. . . . . . . . . . . . . . . . . . . . . . 231 PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Enabling PDF Invoice Copy Attachment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Using PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Processing of PDF Invoice Copy Attachments by the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . 234 BADI Implementation for the BADI Definition INVOICE_UPDATE. . . . . . . . . . . . . . . . . . . . . . . . . . 237 About Configuring Your SAP ERP System for PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . 243 Ariba Network Adapter for SAP NetWeaver Setup Guide Content

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

7

Defining a New Document Class for PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . . . . . . . . 243 Defining a New Document Type for Invoice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Create a Link Between the Standard Business Object and the New Document Type for Invoice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Maintaining the INVOICE_EMAIL_SEND Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Maintaining the ZDEL Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 Configuring the Attachment Processing Mode for PDF Invoice Copy Attachments. . . . . . . . . . . . . . 245 Integrating SAP ERP with the Ariba Spot Quote Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 About SAP ERP and Ariba Spot Quote Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 SAP ERP Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Enabling SAP ERP and Ariba Spot Quote Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 SAP ERP and Ariba Spot Quote Integration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249 SAP ERP and Ariba Spot Quote Integration Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Configuring Ariba Network Buyer Settings for Ariba Spot Quote. . . . . . . . . . . . . . . . . . . . . . . . . . 250 Messages Mapping for Ariba Spot Quote. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 How to Handle cXML Document Errors for Ariba Spot Quote. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Integration of Catalog Data in SAP ERP and Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250 About Integration of Catalog Data in SAP ERP and Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . 251 Enabling the Integration of Catalog Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Using the Catalog Export Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 About Processing Purchase Information Records and Material Master Records. . . . . . . . . . . . . . . 256 Uploading Catalog Changes Using Mediated Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Uploading Catalog Changes Using the Incremental Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Maintaining Catalog Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Configuring Catalog Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Configuring Your SAP ERP System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Importing Custom Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Configuring SAP IDocs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Configuring SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Configuring SAP for IDoc Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 Configuring the Partner Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 Creating an Output Type for the Entry Sheet Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Maintaining Condition Records for Outbound Transactions: POs. . . . . . . . . . . . . . . . . . . . . . . . . . 279 Maintaining Condition Records for Outbound Transactions: Service Sheets. . . . . . . . . . . . . . . . . . 280 Making Additional Change PO Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Maintaining Variants for Remittance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Making Additional Invoice Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Making Additional Tax and Accrual Calculation Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Maintaining Bank Key for the House Bank for Payment Remittance Advice. . . . . . . . . . . . . . . . . . . 288 Making User Exit Enhancements to Support Shipping and Handling Charges. . . . . . . . . . . . . . . . . 288

8

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Content

Maintaining Global Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Configuration Related to Export of Requisitions from SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Business AddIns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Proxy Settings in SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Configuring Proxy Settings for SAP NetWeaver 7.1 or Dual Stack (ABAP and Java) Instances of SAP NetWeaver PI 7.3 and above. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Configuring Proxy Settings for Single Stack (Java only) Instances of SAP NetWeaver PI 7.3 and above. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Documentation of RFCs Within the SAP NetWeaver Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Defining Authorizations for Running Ariba Network Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Configuring Advanced Pricing Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 ABAP Programs for Outbound Transactions Implemented Using Proxies. . . . . . . . . . . . . . . . . . . . . . .299 Configuring Implicit Enhancements for Comments in Order Confirmations. . . . . . . . . . . . . . . . . . . . . 300 Configuring Invoice Status Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Invoice Status Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301 Configuring the Invoice Status Update Transaction on your SAP ERP system. . . . . . . . . . . . . . . . . 303 Configuring Order Inquiries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Configuring SAP IDOC for Order Inquiries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Configuring the Partner Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Maintaining Condition Records for Inquiries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Implementing a Custom Exit for the Order Inquiries Function Module. . . . . . . . . . . . . . . . . . . . . . .308 Support for Additional cXML Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Configuring Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Configuring SAP IDOC for Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Configuring the Partner Profile for Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . 310 Maintaining Condition Records for Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . 311 Implementing a Custom Exit for Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . . . 311 Support for Additional cXML Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Configuring IDOC Metadata (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313 Configuring Ship Notices Against Multiple Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Configuring the SAP IDOC for Ship Notices Against Multiple Purchase Orders. . . . . . . . . . . . . . . . . 313 Configuring the Partner Profile or Ship Notices Against Multiple Purchase Orders. . . . . . . . . . . . . . 314 Configuring IDoc Metadata for Scheduling Agreement Releases (Optional). . . . . . . . . . . . . . . . . . . 315 Configuring Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Configuring Parameters in the ARBA/PARAM_TAB Table for Returns and Corrections in Receipts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Maintaining Condition Records for Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . . . 317 Maintaining Printer Default Values for Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . 318 Configuring Quote Request and Quote Message Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Configuring your System for Quote Request Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Configuring your System for Quote Message Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Configuring SAP NetWeaver PI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Ariba Network Adapter for SAP NetWeaver Setup Guide Content

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

9

Configuring Support for Line Level Hierarchies in Service Purchase Orders. . . . . . . . . . . . . . . . . . . . . 321 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 About Configuring Implicit Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Direct Invoicing of Purchase Order Service Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325 Configuring Service Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Implementing Customer Exits for Invoices with Service Type Line Items. . . . . . . . . . . . . . . . . . . . . 326 Specifying Time-Out Intervals for Processing Service Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . .327 Implementing Enhancements for Service Sheets Created for New Purchase Orders. . . . . . . . . . . . 328 Implementing Enhancements for Service Sheets Created for Changed or Canceled Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Configuring ERP-Initiated Invoices to Use the IDOC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Configuring the NACE Setting to Send ERS Invoices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Configuring the NACE Setting to Send Invoicing Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Configuring the NACE Setting to Send MIRO Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Implementing the Customer Exit for MM Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Implementing Routines to Prevent Creation of Duplicate MM IDOCs . . . . . . . . . . . . . . . . . . . . . . . 336 Maintaining Partner Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Configuring the FI Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Setting Document Type Filters for FI Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339 Maintaining Output Types for FI Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 Implementing the Customer Exit for FI Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Handling Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On. . . . . . . . . . . . . . . . . . . . . . . . 343 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Installation Requirements for SAP Suite Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Setting Up the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .347 Understanding cXML Adapter Document Transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Deploying the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Deploying the cXML Adapter Using JSPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Undeploying the Adapter using the Textconsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Undeploying the Adapter using the Textconsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Configuring Logging for the SAP Suite Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Configuring the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350 Configuring the System Landscape Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Importing Ariba Network Product and Component Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 To import product and component definitions:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 Defining Technical and Business System for Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 To define the Technical System for Ariba Network:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 To define the Business System for Ariba Network:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Defining the Technical System for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Defining the Business System for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

10

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Content

Configuring Transaction Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Importing the Design Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Configuring SAP ERP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Assigning Business Systems in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355 Configuring Integration Scenarios in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 Workflow for Configuring the Integration Scenario for Inbound And Outbound Transactions. . . . . . .357 Configuring the Integration Directory for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Transferring the Integration Scenario for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . 357 About Configuring the Integration Scenario for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . 359 Assigning the Model for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Assigning Components for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Configuring Sender And Receiver Relations for Individual Connections for Inbound Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Generating Objects for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Configuring Communication Channels for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . 362 Activating the Scenario for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363 Configuring the Integration Directory for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Transferring Integration Scenario for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 About Configuring the Integration Scenario for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . 366 Assigning the Model for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366 Assigning Components for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 Configuring Sender and Receiver Relations for Individual Connections For Outbound Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Generate Objects for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Configuring Communication Channels for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . 369 Activating the Scenario for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Linking Multiple SAP Instances with Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Multi-ERP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Supported cXML Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 Testing the SAP NetWeaver for Suite Add-On Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 Sending a Purchase Order for Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Running a getPending Transaction for Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Understanding Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Understanding Error and Status Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Understanding Email Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Monitoring the cXML Adapter from Runtime Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 Deploying the Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Ariba Network Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Downloading the Ariba Network Integration Guide from Connect:. . . . . . . . . . . . . . . . . . . . . . . . . 380 Enabling Support for Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Attachments Support in cXML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Attachments for Outbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Ariba Network Adapter for SAP NetWeaver Setup Guide Content

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

11

Attachments for Inbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Using Endpoints for Integration with SAP NetWeaver for SAP Suite Add-On. . . . . . . . . . . . . . . . . . . . .382 Using the SAP NetWeaver PI KeyStore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Configuring Communication Channels to Use SAP NetWeaver PI Keystore. . . . . . . . . . . . . . . . . . . 383 Testing the Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Testing the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Sending a Purchase Order for Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Running a getPending Transaction for Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Understanding Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Monitoring of the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Monitoring the cXML Adapter from Runtime Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388 Deploying the Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Ariba Network Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Downloading the Ariba Network Integration Guide from Connect. . . . . . . . . . . . . . . . . . . . . . . . . . 389 cXML Adapter Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Common Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Inbound Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 Outbound Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 Configuring Retry Attempts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395 Configuring Proxy Server Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395 Ariba SAP Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 SAP Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 /ARBA/COMMON_OBJECTS Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 /ARBA/PURCHASEORDER Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 /ARBA/CHANGEPURCHASEORDER Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 /ARBA/ERPINVOICE Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .402 /ARBA/INVOICESTATUSUPDATE Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 /ARBA/PAYMENTPROPOSAL Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 /ARBA/RECEIPT Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 /ARBA/REQUISITION Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

12

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Content

Ariba Network Adapter for SAP NetWeaver

Overview [page 13] Data Flow and Data Element Mapping [page 14] Setting Up the Ariba Network Adapter for SAP NetWeaver [page 29]

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 13]. 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 runs on the SAP NetWeaver Process Integration (PI) component, and can be thought of as a library for SAP NetWeaver PI. This library includes integration processes and Java libraries that implement the cXML transport protocol and provide a set of facilities for resolving differences between SAP and Ariba Network. For more information about cXML and Ariba Network, refer to the following documents on Ariba Connect (http:// connect.ariba.com ): ● Ariba Network Integration Guide ● Ariba Network Buyer Administration Guide ● Ariba cXML Solutions Guide ● cXML User’s Guide The Ariba Network Adapter for SAP NetWeaver consists of the following: ● The design package in the SAP Netweaver PI 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 Netweaver PI 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 Ariba Network Adapter for SAP NetWeaver Setup Guide (this document) illustrates the deployment and configuration processes of the Ariba Network Adapter integration package within SAP NetWeaver PI. The following graphic illustrates how the Ariba Network Adapter for SAP NetWeaver enables the communication flow between Ariba Network and the SAP ERP system. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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

13

SAP NetWeaver PI is a platform for process integration within SAP NetWeaver. It facilitates cross-system business processes. In particular, it enables different versions of SAP and non-SAP systems from different vendors running on different platforms to communicate with each other. SAP NetWeaver PI 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 NetWeaver PI Integration Server. It processes the integration processes at runtime. ● The Integration Engine is the central runtime component of the SAP NetWeaver PI Integration Server used for receiving, processing, and forwarding messages. ● The Adapter Engine is a runtime component of the SAP NetWeaver PI Integration Server. It uses adapters to connect the Integration Engine to SAP systems (RFC adapter) and external systems.

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.

14

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

Figure 1: 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 216].

Supported cXML Interfaces The Ariba Network Adapter for SAP NetWeaver supports the following outbound and inbound cXML interfaces on the SAP NetWeaver PI: Outbound cXML Interfaces

Inbound cXML Interfaces

Order Request

Order Confirmation Request

Change Order Request

Ship Notice Request

Invoice Status Update Request

Invoice Detail Request

Payment Remittance Request

Pay Me Now

Payment Remittance Advice Request

Service Entry Request

Payment Proposal Request Receipt Request Requisition Request Quote Request Order Status Request Catalog Upload Request

For more detailed information about these cXML Interfaces, see the cXML User’s Guide, the Ariba cXML Solutions Guide and the sample mapping tables. The remainder of this section discusses the cXML Interfaces on a general level as they pertain to the Ariba Network Adapter for SAP NetWeaver.

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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

15

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.

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 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. For more information, see Schedule Lines in Purchase Orders and Change Purchase Orders [page 143]. 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. For more information, see Scheduling Agreement Release Integration Scenario [page 153].

Support for Service Purchase Orders Purchase orders with lines that specify category D are considered service purchase orders on Ariba Network. In the transformed OrderRequest document for a service purchase order, for all lines with category D, the ItemOut element 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 must specify a maximum amount. SAP NetWeaver 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.

16

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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 adapter 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 on configuring support for line level hierarchies in service purchase orders, see Configuring Support for Line Level Hierarchies in Service Purchase Orders [page 321].

Note Ariba Network does not support service lines in blanket purchase orders.

Support for Schedule Lines in Purchase Orders and Change Purchase Orders

You can specify multiple delivery schedules for a line item in a purchase order or change purchase order that you send suppliers on Ariba Network. This allows you 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. 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. For more information, see Schedule Lines in Purchase Orders and Change Purchase Orders [page 143].

Order Confirmation 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 391]. For more information, see the Ariba Network Integration Guide. For more information on the order confirmation integration scenario, see Order Confirmation Integration Scenario [page 93].

Ship Notice Ship Notices are downloaded from Ariba Network to the Ariba Network Adapter for SAP NetWeaver using the pull document transmission methods described in cXML Adapter Parameters [page 391]. For more information, see the Ariba Network Integration Guide. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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

17

Service Sheet A 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 391]. 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 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 Ariba Invoice Professional 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 processes 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, Ariba recommends that you specify a time-out duration. For more information, see Specifying Time-Out Intervals for Processing Service Sheets [page 327]. 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.

18

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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. See Invoice [page 20] for more information. Prerequisite [page 19] Limitations [page 19]

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.

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 Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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

19

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

Invoice Invoices are downloaded from Ariba Network to the Ariba Network Adapter for SAP NetWeaver using the pull document transmission methods described in cXML Adapter Parameters [page 391]. For more information, see the Ariba Network Integration Guide.

Support for Non-PO Invoices and Credit Memos

In addition to PO-based invoices, invoice supports the following scenarios: ● Non-PO based invoice containing accounting information ● Header-level credit memos against purchase orders created on Ariba Network and then reconciled in the Ariba procurement solution. ● Header-level credit memos against non-POs created in the Ariba procurement solution.

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. ● (For users upgrading from version 1.4 of the Ariba Network Adapter for SAP NetWeaver to version 10s2 only.) To post non-PO invoices successfully, you must delete and reload the IDoc metadata from the NetWeaver transaction IDX2 after the installation of the upgrade package. For more information on implementing the user exit, see cXML Adapter Parameters [page 391].

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

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

20

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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 nonPO 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 cXML Adapter Parameters [page 391].

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

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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

21

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 a buyer creates one invoice against multiple service sheets and the corresponding purchase order does not have the S based IV indicator enabled.

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 nonmaterial purchase orders having the standard item category.

Note Ariba 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

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 325] .

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

22

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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.

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. ERP-Initiated Invoices Using the IDOC Transmission Method [page 23] Enabling Quick Enablement for ERP-Initiated Invoices [page 25] ERP-Initiated Invoice with Cross Company Codes [page 26]

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 Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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

23

● 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. Prerequisites for Using IDOCs for ERP-Initiated Invoices [page 24] Limitations Using the IDOCs [page 25]

Related Information ERP-Initiated Invoice Integration Scenario [page 167] Configuring ERP-Initiated Invoices to Use the IDOC [page 331]

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 PI. For more information, see ERP-Initiated Invoice Integration Scenario [page 167] and Configuring ERPInitiated Invoices to Use the IDOC [page 331] .

Backward Compatibility This feature is not compatible with the releases prior to 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 Ariba Cloud Integration Release 6.0, the ERP_INV_PROCESSED_STATUS parameter is no longer required for ERP-initiated invoices.

24

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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 Ariba Cloud Integration Release 5.0 and lower must continue to maintain the ERP_INV_PROCESSED_STATUS parameter for ERP-initiated invoices. To continue using the ABAP proxy program, you must ensure that you use the ERPINV_PROCESSES_CHK parameter. This parameter supports extracting all the ERP invoices that are stored in the /ARBA/AN_ERPINV table.

Limitations Using the IDOCs Ariba Procurement Solution 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 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.

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 NetWeaver PI and the SAP ERP system.

Note Email ID must be maintained in Vendor Master and the same email ID is passed to SAP NetWeaver PI. To enable quick enablement, ensure that you have: ● Imported the AribaNetworkAdapterSAPNetweaver.Design.tpz file into your SAP NetWeaver PI system. ● Downloaded the relevant SAP transport requests from connect.ariba.com and imported them into your SAP ERP system.

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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

25

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.

Note The 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, 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.

Note The 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

26

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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

Note The 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 . Enabling ERP-Initiated Invoices with Cross Company Codes [page 27]

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 Ariba into your SAP ERP system. To do this, you must download the SAP transports (available in a ZIP file) from Connect (http://connect.ariba.com), open the ReadMe.txt that is available in the ZIP file, and check the transport number that is relevant and import it.

Invoice Status Update Invoice status updates are sent by buying organizations to inform Ariba Network and suppliers of the status of invoice reconciliation. Buyers send StatusUpdateRequest documents to set invoice status to processing, reconciled, paying, paid, rejected, invalid, parked or parked invoices that have been deleted. Ariba Network posts the documents to the URL that suppliers return in their cXML ProfileResponse. StatusUpdateRequest documents can identify invoices in two possible ways: through either a DocumentReference or an InvoiceIDInfo element. For more information about invoice status updates, see Configuring Invoice Status Updates [page 301] and the Ariba cXML Solutions Guide.

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 Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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

27

address them to suppliers. However, Ariba Network routes them to Ariba Invoice and Payment. When receipt data is successfully posted in Ariba Network, Buyers can see the receipts in their online Outbox.

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.

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

Scheduled Payments and Dynamic Discounting Buying organizations use scheduled payments, that is, PaymentProposalRequest documents, to tell Ariba Network and their suppliers about planned payments. These documents list scheduled payment dates, discount amounts, and net amounts. Scheduled payments are used for information by default, but they can also be used for Dynamic Discounting. Dynamic Discounting allows buying organizations to pay suppliers early in exchange for discounts. Buying organizations send proposed payment information to Ariba Network in PaymentProposalRequest documents containing a special Extrinsic element called immediatePay. 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. Updated PaymentProposalRequest documents are then used to update the payment schedule and discount amount in the buying organization’s SAP system. For more information about scheduled payments, see the Ariba cXML Solutions Guide. For more information about Dynamic Discounting, see the Ariba Network Buyer’s Guide.

Payment Remittance Advice Request Payment Remittance Advice requests are sent by Ariba Network to notify suppliers and SAP about external payment made directly from Ariba Network. It sends PaymentRemittanceAdviceRequest documents to suppliers as well as SAP to create an accounting document.

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.

28

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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 Downloading the Ariba Network Integration Guide from Connect [page 389].

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 13]. 2. Setting up and configuring the cXML Adapter. For more information, see About Deploying the cXML Adapter [page 34]. 3. Configuring the System Landscape Directory. For more information, see About Configuring the System Landscape Directory [page 61]. 4. Configuring transaction processes. For more information, see About Configuring Transaction Processes [page 65]. 5. Configuring the SAP ERP system. For more information, see Configuring Your SAP ERP System [page 13]. 6. Testing the configuration. For more information, see Testing the Adapter [page 13].

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver

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

29

Configuring the Ariba Network Adapter for SAP NetWeaver

Installation Requirements [page 30] About Configuring Security Certificates [page 32] About Deploying the cXML Adapter [page 34] About Configuring the cXML Adapter [page 45]

Installation Requirements Before you start up the set-up process verify that you have the required software and connectivity requirements. 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 30].

Supported SAP Netweaver PI Versions The following table lists the Ariba Network Adapter for SAP NetWeaver versions and the supported SAP Netweaver PI versions that they can be deployed on: Ariba Network Adapter for SAP NetWeaver Version

Supported SAP Netweaver PI Versions

Cloud Integration 1

SAP Netweaver PI 7.1 SAP Netweaver PI 7.3

Cloud Integration 2 or higher

SAP Netweaver PI 7.1 SAP Netweaver PI 7.3 SAP Netweaver PI 7.4

Supported SAP ERP Versions The Ariba Network Adapter for SAP NetWeaver supports SAP ERP versions starting with SAP ERP 6.0 up to SAP ERP 6.0 EHP 7. For information about the platforms that the SAP NetWeaver suite supports, see the following SAP NetWeaver section on the SAP Service Marketplace: service.sap.com > SAP NetWeaver > SAP NetWeaver PI 7.X > Availability.

30

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

Ariba Network Requirements

Ensure that you have the following Ariba Network requirements before installing the Ariba Network Adapter for SAP NetWeaver: ● A valid, configured Ariba Network Buyer account. For more information about configuring your Ariba Network Buyer account, see the Ariba Network Buyer Administration Guide. ● An Ariba Network supplier relationship, including an ANID-to-Private ID mapping. For more information about creating a supplier relationship, see 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, see About Configuring Security Certificates [page 32]. For more information about obtaining a digital certificate, see the Ariba 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 detailed 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 cXML Adapter Parameters [page 391]. ● The Ariba Network’s Certificate Authorities certificates are stored in the SAP NetWeaver PI Keystore. The cXML Adapter uses the certificates stored in the SAP NetWeaver PI Keystore to connect to Ariba Network.

Installing the Network Adapter Files Context

To install the Ariba Network Adapter for SAP NetWeaver, you need the relevant archive file which is available on Ariba’s support interface, Ariba Connect.

Procedure

1. Login to Ariba Connect (http://connect.ariba.com) and click the Download Software tab. 2. Click I Accept to accept the Ariba Software Access Agreement. 3. Select as the Product Line and the relevant Product Version. 4. Navigate to or search for the relevant file and click the download icon to download the archive file. 5. Import the relevant SAP transport requests into your SAP ERP system. 6. Import the AribaNetworkAdapterSAPNetweaver.Design.tpz file into your SAP NetWeaver PI system.

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

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

31

Results The archive ZIP files contain the following components: Product definition files

AribaNetworkAdapterSAPNetweaver.SoftwareCatalog.zip

Mapping design and Integration configuration files

AribaNetworkAdapterSAPNetweaver.Design.tpz

cXML Adapter files

AribaNetworkAdapterSAPNetWeaver.sca

Metadata definition files

AribaNetworkAdapterSAPNetweaver.xml

Software catalog files

CacheCatalog.xml CanonicalCatalog.xml

SAP configuration transport files

The required SAP transport files.

About Configuring Security Certificates Install security certificates in a Java JRE keystore or truststore.

Related Information Importing Security Certificates into the Java JRE Keystore [page 32] Importing Security Certificates into the Java JRE TrustStore [page 33] Installing Client Certificates on Ariba Network [page 34]

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

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:

32

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

echo $JAVA_HOME 2. 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/cacerts The 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/cacerts Where: 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.

Importing 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_path Where: 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.

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

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

33

Installing 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 Ariba or to add a CA to Ariba’s trusted CAs, contact your 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 page 4. 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.

Note Digital 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.

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.

34

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

If your version of SAP netweaver PI is prior to PI 7.3 EHP1, use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI. From SAP netweaver version PI7.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 Deploying the cXML Adapter Using JSPM [page 35] Upgrading the cXML Adapter Using JSPM [page 38] Installing Additional Resources for the cXML Adapter [page 42] Undeploying the cXML Adapter using the Textconsole [page 43] Deploying the cXML Adapter Using the textconsole [page 43]

Deploying the cXML Adapter Using JSPM Prerequisites In SAP NetWeaver PI, you have placed the .SCA file in the required location.

Procedure 1. Start JSPM.

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

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

35

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

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

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

36

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

5. Click Start. The Deploy Queue screen appears.

The Completed screen appears.

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

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

37

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 43].

Upgrading the cXML Adapter Using JSPM Procedure 1. Start JSPM.

38

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

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

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

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

39

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

40

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

5. Click Start. The Deploy Queue screen appears.

The Completed screen appears.

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

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

41

6. Click Exit.

Results

The cXML Adapter is upgraded successfully.

Installing 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/.

42

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

Undeploying 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: '[]'' >

Deploying the cXML Adapter Using the textconsole Context

Run the following at the Telnet prompt: deploy name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_deploy_error=stop Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

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

43

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

Note To 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 .

Setting 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 NetWeaver PI log administration section at http://XI_server_hostname/XI_port/nwa/logs. 2. Click the Log Configuration link. 3. Select Tracing Locations from the Show drop down list. 4. Select the node (package) com ariba asc , to set the logging level to log the complete adapter processing information, or select 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 drop-down list, and then click Save Configuration in the toolbar.

Note The log level can remain Error when running in a production environment, but 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.

44

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

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 30] section. For a description of the parameters and instructions for how to configure retry attempts, see cXML Adapter Parameters [page 391].

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver

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

45

Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

About Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver [page 46] cXML Interfaces Supported in the Ariba Cloud Integration Releases [page 47] Features Available in the Ariba Cloud Integration Releases [page 48] Steps to Install the Ariba Network Adapter for SAP NetWeaver PI [page 51] Installing the SAP ERP Transports [page 51] Upgrading to a Higher Version of the Ariba Network Adapter for SAP NetWeaver Transports [page 52]

About Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver To integrate the SAP NetWeaver PI with Ariba Network, Ariba recommends that you install a new version or upgrade to a higher version of Ariba Network Adapter for SAP NetWeaver. Starting Ariba Cloud Integration 6.0, all the transport files for Ariba Network Adapter for SAP NetWeaver have been merged to a single transport file for easier installation. Customers who are using versions prior to Ariba Cloud Integration 6.0 continue to install the different transport files available in the transport zip file. If you are a new customer, you must install the latest version of the transport files for Ariba Network Adapter for SAP NetWeaver. If you are existing customer, Ariba recommends that you upgrade to a higher version of the Ariba Cloud Integration. When you upgrade from an existing version of Ariba Cloud Integration to the latest version, ensure that you perform certain procedures to retain your existing settings or customization that you have on your current version of the Ariba Cloud Integration.

Prerequisites Ensure that you have all the necessary software and connectivity requirements before you install the Ariba Network Adapter for SAP NetWeaver.

Related Information Installation Requirements [page 30] Steps to Install the Ariba Network Adapter for SAP NetWeaver PI [page 51]

46

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

Upgrading to a Higher Version of the Ariba Network Adapter for SAP NetWeaver Transports [page 52]

cXML Interfaces Supported in the Ariba Cloud Integration Releases The following table shows a comparison of the supported cXML interfaces between Ariba Cloud Integration version 1.0 and version 6.0: Ariba Cloud Integration Release Version 1.0

Ariba Cloud Integration Release Version 6.0

Requisition

Requisition

Purchase Order

Purchase Order (Includes Change and Cancel Purchase Orders)

Change and Cancel Purchase Order Order Confirmation

Order Confirmation

Ship Notice

Ship Notice

Invoice

Invoice

ERP-Initiated Invoice

ERP-Initiated Invoice

Invoice Status Update

Invoice Status Update

Receipt

Receipt

Payment Proposal

Payment Proposal

Payment Remittance

Payment Remittance

Pay Me Now

Pay Me Now Request for Quotation Service Sheet Order Inquiry Scheduling Agreement Catalog

Related Information Supported cXML Interfaces [page 15]

Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

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

47

Features Available in the Ariba Cloud Integration Releases The following are the new features and changes introduced in the different Ariba Cloud Integration releases: Ariba Cloud

Ariba Cloud

Ariba Cloud

Ariba Cloud

Ariba Cloud

Ariba Cloud

Integration 1.0

Integration 2.0

Integration 3.0

Integration 4.0

Integration 5.0

The SAP code

Enhanced error

Support for

Support for Order

Support for

delivered by Ariba

messages for

Scheduling

Inquiries

sending RFQs from maintaining the

was certified by

Invoice Status

Agreement

SAP ERP to Ariba

partner profile for

SAP. As part of the

Update

Releases

Sourcing

each vendor or

certification, a new

documents.

Integration 6.0

Support for

maintain the

namespace

partner profile at a

called /ARBA/

logical system level

was registered and

for all vendors

all SAP objects delivered by Ariba were renamed from Z_ to /ARBA/ . The SAP NetWeaver PI content was changed by importing the RFCs and the ABAP objects were renamed with the /ARBA/

namespace into SAP NetWeaver PI. The namespace of

SAP NetWeaver PI

Support for

Support for

Support for Ariba

Support Invoice

invoice in the

7.4 Support for

Blanket Purchase

corrections and

Sourcing Award

Status Updates for

Orders

returns in Receipts

Integration

parked and deleted

AribaNetworkA Ariba Network dapterforSAPN

invoices

etWeaver.desi gn.tpz was changed from

http:// ariba.com/xi/ ASN/ZInvoice

48

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

Ariba Cloud

Ariba Cloud

Ariba Cloud

Ariba Cloud

Ariba Cloud

Ariba Cloud

Integration 1.0

Integration 2.0

Integration 3.0

Integration 4.0

Integration 5.0

The cXML adapter

Mapping

Support

Support line-level

Support line-level

requires the JSPM

enhancements to

integration for

hierarchies in

hierarchies in

(Java Support

support Supply

Outline

Service Purchase

Service Sheets and

Package Manager).

Chain

Agreements in SAP Orders

Integration 6.0

to http://

ariba.com/xi/ ASN/Invoice. ZINVOICE02 and ZACCOUNT_DATA were renamed to /

ARBA/INVOICE and /ARBA/

ACCOUNT _DATA respectively.

Invoices

Management Support for Order

Support for

Enhanced request

Support for change Support IDOCs for

Confirmation and

creation of a single

messages added

and cancel order

CC (ERP-Inititated)

rejection of the

ship notice against

to the cXML

transactions have

Invoices

entire purchase

multiple purchase

adapter:

been removed.

order.

orders

StatusUpdateRequ Change order est

transactions are processed as part

Note The previous

of the purchase order IDOC.

Invoice Status Update Request no longer exists. Buyers can now use the StatusUpdateR equest for both invoices and service entry sheets.

Ariba no longer

Support for

Invoice Status

Support all

Support line

uses the ccBPM

schedules lines in

Update use

releases of SAP

numbering in

engine.

purchase orders

Business

ERP 6.0 up to SAP

schedule lines

The following transactions are

Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

Transaction Events ERP 6.0 EhP7 (BTE) to process invoices created,

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

49

Ariba Cloud

Ariba Cloud

Ariba Cloud

Ariba Cloud

Ariba Cloud

Integration 1.0

Integration 2.0

Integration 3.0

Integration 4.0

Integration 5.0

supported using

changed, reversed,

the ABAP proxies:

canceled, or when

●

Integration 6.0

payments are

ERP-Initiated

received.

Invoice ●

Ariba Cloud

Invoice Status Update

●

Payment Proposal

●

Receipt

Payment

Support for SAP

Support for

Integration of

Remittance Advice

ERP Integration

purchase order

catalog data in

transaction is no

with Ariba Spot

confirmation

SAP ERP and Ariba

longer supported

Quote solution

options at the

Network

by the Ariba

header and line-

Network Adapter

item levels

for SAP NetWeaver.

ZARIBA_INV_AT

Support for large

Support summary

TACHDOC BADI

file attachments in

invoices

ZARIBA_INV_AT

invoices and

referencing

TACHDOC BADI

service sheets

multiple purchase orders and direct

support for PDF

invoicing of

copy of invoices.

purchase order service items Processing of attachments in the outbound transactional documents in the PI mapping layer before sending them to Ariba Network

50

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

Steps to Install the Ariba Network Adapter for SAP NetWeaver PI Context

Ensure that you perform the following steps to install the latest SAP NetWeaver adapter on your SAP NetWeaver PI system.

Procedure

1. Download the latest installation package. For more information, see Installing the Network Adapter Files [page 31]. 2. Ensure that you meet all the software and connectivity requirements. For more information, see the Installation Requirements [page 30] section. 3. Configure an Ariba Network account. For more information, see Installation Requirements [page 30]. 4. Configure the SAP ERP system. For more information, see Configuring Your SAP ERP System [page 269]. 5. Import the Design Package. For more information, see Importing the Design Package [page 66]. 6. Configure the System Landscape Directory. For more information, see About Configuring the System Landscape Directory [page 61]. 7. Configure the transaction processes. For more information, see About Configuring Transaction Processes [page 65]. 8. Configure the Integration Scenarios in the Integration Directory. For more information, see Configuring Integration Scenarios [page 80] . 9. Install and configure the cXML Adapter and Log mechanism. For more information, see About Deploying the cXML Adapter [page 34] and About Configuring the cXML Adapter [page 45]. 10. Test the configuration. For more information, see Testing the Adapter [page 384] .

Installing the SAP ERP Transports Context

You must install SAP ERP transports to integrate an Ariba Network application with SAP. The latest SAP ERP transports are available in AribaNetworkAdapterSAPNetweaver_vCIX.zip\SAPConfig\Trans. Place these files in the appropriate locations on your SAP instance.

Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

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

51

Procedure

1. Run the STMS transaction to install the transport files. 2. Specify the target client as the SAP instance client. 3. If the “Does not match component version” error occurs while importing the transport files that have a different software component that is not available in the target system, turn OFF the SP_TRANS_SYNC parameter: ○ Start Transaction STMS. ○ Go to the Systems Overview. ○ Double click the system identifier for which you want to add the parameter. ○ On the Transport Tool tab, click Change Mode. ○ Add SP_TRANS_SYNC to the parameter column. Set the value for the parameter to OFF. ○ Save and activate the parameter.

Upgrading to a Higher Version of the Ariba Network Adapter for SAP NetWeaver Transports When you upgrade to a higher version of the SAP transports, ensure that you make the necessary changes on your SAP NetWeaver PI and SAP ERP system. Changes Required on your SAP ERP Systems [page 52] Changes Required on your SAP NetWeaver PI System [page 54] Migrating the Design Objects [page 55] Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration [page 55] Updating the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration [page 56] Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration [page 57]

Changes Required on your SAP ERP Systems Context

The following changes are applicable when you upgrade from the Ariba Cloud Integration 1.0 to Ariba Cloud Integration 6.0.

52

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

Procedure

1. Import the Ariba Cloud Integration 6.0 transports. 2. If you want to use the new transactions, configure the necessary settings for the following transactions available in the Ariba Cloud Integration 6.0: ○ Order inquiry – For more information, see Configuring Order Inquiries [page 304]. ○ Scheduling Agreement - For more information, see Configuring Scheduling Agreement Releases [page 309]. ○ Service Sheet - For more information, see Configuring Service Sheets [page 326]. ○ Request for Quotation (Quote Request and Quote Message) - For more information, see Configuring Quote Request and Quote Message Documents [page 318]. ○ Catalog (Catalog Upload Request) - For more information, see Integration of Catalog Data in SAP ERP and Ariba Network [page 250]. 3. Ensure that you migrate the changes for the following BAdI manually. The BAdI is not automatically migrated when you upgrade to Ariba Cloud Integration 6.0. This is applicable only if you are using the BAdI for Ariba Cloud Integration 5.0 and earlier. ○ /ARBA/ISU_UPDATE Starting Ariba Cloud Integration 5.0, the Invoice Status Update BAdI definition has been changed to / ARBA/BTE_ISU_UPDATE. For more information see, Invoice Status Update Integration Scenario [page 160] and Configuring Invoice Status Updates [page 301]. 4. The following BAdIs are no longer available in Ariba Cloud Integration 6.0: ○ /ARBA/CHANGE_PO Ariba Cloud Integration 5.0 does not contain a separate IDOC and namespace for the Change Purchase Order transaction. In Ariba Cloud Integration 4.0 and earlier, change purchase orders and cancel purchase orders were handled differently from new purchase orders by the Ariba Network Adapter for SAP NetWeaver. With Ariba Cloud Integration 5.0, new purchase orders, change purchase order, and cancel purchase orders are now processed in the purchase order transaction. If you have existing change purchase order customizations, ensure that you manually move them to the purchase order transaction. For more information, see Change Purchase Order Integration Scenario [page 89]. ○ /ARBA/INVOICE_UPDATE Ariba Cloud Integration 6.0 no longer uses the proxy for ERP-Initiated Invoices. The ERP-Initiated Invoices now use the standard IDOC. To enhance the ERP-Initiated invoice transaction, you must use the standard BAdI, customer exits, and enhancements. For more information, see the ERPInitiated Invoice Integration Scenario [page 167] and Configuring ERP-Initiated Invoices to Use the IDOC [page 331]. ○ /ARBA/RECEIPT_UPDATE In Ariba Cloud Integration 4.0 and higher, the method READ_RECEIPT_DATA is no longer used. 5. Ensure that you make the following changes after you upgrade to the new version of the Ariba Cloud Integration: ○ Configure the Purchase Order transaction ○ Reconfigure the SAP Partner Profile to process change and cancel orders as variations on a standard purchase order. For more information, see Reconfiguring the SAP Partner Profile [page 90]. ○ Configure Implicit Enhancements for new purchase orders. For more information, see Configuring Implicit Enhancements for Change and Cancel Orders [page 91] . Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

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

53

○ Configure the SAP IDOC for ship notices (DELVRY06). For more information, see Configuring the SAP IDOC for Ship Notices Against Multiple Purchase Orders [page 313]. ○ Configure the Business Transaction Events (BTE) for the invoice status update transaction. For more information, see Configuring Invoice Status Updates [page 301]. ○ Configure the NACE transaction to publish receipts in real-time. For more information, see Maintaining Condition Records for Returns and Corrections in Receipts [page 317]. ○ Configure the SAP IDOC for ERP-Initiated Invoice transaction. For more information, see Configuring ERPInitiated Invoices to Use the IDOC [page 331].

Changes Required on your SAP NetWeaver PI System Context

Ensure that you make the following changes after you upgrade to the latest version of the desgin mapping objects on your SAP NetWeaver PI system.

Procedure

1. Ariba Cloud Integration 6.0 has new design mapping objects. If you are using an earlier version of Ariba Cloud Integration, ensure that you import the new design mapping objects. Ensure that you configure the integration scenarios for them. 2. If you have customizations done to the existing design mapping objects, you must migrate these design mapping objects. For more information, see section, Migrating the Design Objects [page 55].

Note Ensure that you manually make changes to your custom mappings that contain conflict. 3. You must upgrade your JCA Adapter. If your version of SAP Netweaver PI is lower than SAP PI 7.3 EHP1, use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI. If you are using the SAP Netweaver version PI7.3 EHP1 and higher, 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 system administrator. For information on how to deploy the JSPM tool, see the section, Deploying the cXML Adapter Using JSPM [page 35].

Related Information

Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration [page 55]

54

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

Migrating the Design Objects Context After you have upgraded to the Ariba Cloud Integration 6.0, ensure that you migrate the design objects on your SAP NetWeaver PI system.

Procedure 1. Go to the Enterprise Services Builder. 2. On the Tools menu, click Transfer Design Objects. The Transfer Design Object wizard appears. 3. Click Continue. The Select Source and Target page appears. 4. Select the source of your existing Ariba Cloud Integration version in the Source field. 5. Select the target of the new Ariba Cloud Integration version in the Target field. 6. Click Continue. The Select Objects page appears. 7. Select the Active Version for Ariba Cloud Integration 6.0. 8. Select All Objects of Individual Namespaces in the Object Set field. ○ Choose this option if you are upgrading from the Ariba Cloud Integration version 1.0 to 6.0. Choosing this option prevents you from errors that occur due to the mismatch of the namespace changes when you upgrade to a higher version of Ariba Cloud Integration. 9. Ensure that you do not select the following namespaces while upgrading to a higher version of Ariba Cloud Integration: ○ http://ariba.com/xi/ASN/ChangedPurchaseOrder ○ http://ariba.com/xi/Requisition ○ http://ariba.com/xi/ASN/ERPInvoiceProxy ○ http://ariba.com/xi/ASN/AdvanceShipNotice 10. After you have completed transferring the design objects, ensure that you resolve the conflicts. For more information, see Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration [page 55].

Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration When you upgrade from a lower version to a higher version of the Ariba Cloud Integration, conflicts arise after transferring the design objects. This occurs due to changes that have been implemented in the newer version of the Ariba Cloud Integration. You can resolve the conflicts for the design objects by accepting the latest version (Active Version) of the Ariba Cloud Integration. Ensure that you manually make changes to your custom mappings that contain conflicts. Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

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

55

Related Information

Migrating the Design Objects [page 55]

Updating the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration Context

After upgrading to a higher version of the Ariba Cloud Integration, ensure that you update the integration scenarios for the new and existing transactions.

Procedure

1. Delete the following integration scenarios in Ariba Cloud Integration 1.0 : Integration Scenario

These needs to be deleted because…

Requisition

The namespace for this integration scenario has been changed in Ariba Cloud Integration 5.0.

ERPInvoiceProxy (ERP-Initiated invoices)

In Ariba Cloud Integration 6.0, ERP-Initiated Invoices use the standard IDOC instead of the proxy message.

Ship Notice

The IDoc Basic Type has been changed in Ariba Cloud Integration 4.0.

Change Purchase Order

The Change Purchase Order transaction is no longer available in Ariba Cloud Integration 5.0 and 6.0. Change purchase orders are processed as part of the purchase order integration.

2. Run the following integration scenarios again with the Software Component Version for the Ariba Cloud Integration 6.0: ○ Requisition ○ ERPInvoiceProxy ○ Ship Notice (ASN) 3. Edit the integration scenario for the remaining transactions that have been migrated to Ariba Cloud Integration 6.0. For each of the migrated transactions, choose the software component version for Ariba Cloud Integration 6.0. For more information, see Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration [page 57]. 4. Configure the integration scenarios for all the new transactions available in Ariba Cloud Integration 6.0. For more information, see Configuring Integration Scenarios [page 80].

56

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration After you have upgraded to a higher version of the Ariba Cloud Integration, you must edit the integration scenario for each of the migrated transactions. Configuring the Communication Channel [page 57] Configuring the Receiver Determination [page 58] Configuring the Interface Determination [page 59] Configuring the Sender Agreement [page 59] Configuring the Receiver Agreement [page 60]

Configuring the Communication Channel Context You must edit the integration scenario for each of the migrated transactions. 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.

Procedure 1. Go to the Configuration: Integration Builder to edit the communication channel for the Software Component Version. 2. Select the configuration scenario and open it. The Display Configuration Scenario page appears. 3. Click the Edit button. 4. Go to the ES Repository Model tab and click the Display Input Help button. The Select Process Integration Scenario from Enterprise Service Repository page appears. 5. Select the process integration scenario for the software component version for Ariba Cloud Integration 6.0. 6. Click Apply. 7. On the main Configuration: Integration Builder page, click the Objects tab. 8. Double-click the cXML communication channel to open it. 9. Click the Edit button. 10. In the Parameters tab, click the Display Input Help button in the Adapter Type field. The Choose Adapter Metadata page appears. 11. Choose the adapter metadata for Ariba Cloud Integration 6.0 in the Adapter Type field. 12. Click Apply. 13. In the Parameters tab, specify the System Type as “Buyer.” 14. Select the corresponding request type in the Inbound Request Type or Outbound Request Type field. Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

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

57

○ When you select the Outbound Request Type, choose one of the following DTDs in the cXML Configuration section: ○ Default value: cXML.dtd ○ Specify PaymentRemittance.dtd for PaymentProposalRequest, PaymentRemittanceStatusUpdateRequest, or PaymentRemittanceRequest. ○ Specify Fulfill.dtd for ReceiptRequest and OrderStatusRequest ○ Specify Quote.dtd for QuoteRequest ○ Specify InvoiceDetail.dtd for CopyRequest and Invoice InvoiceDetailRequest 15. Enter a value in the Credentials Field. 16. Save and activate the changes for the communication channel.

Configuring the Receiver Determination Context After you upgrade to the Ariba Cloud Integration 6.0, you must edit the Receiver Determination for each of the migrated transactions.

Procedure 1. Go to the Configuration: Integration Builder to edit the Receiver Determination for the Software Component Version. 2. Select the configuration scenario and open it. The Display Configuration Scenario page appears. 3. Click the Edit button. 4. Go to the ES Repository Model tab and click the Display Input Help button. The Select Process Integration Scenario from Enterprise Service Repository page appears. 5. Select the process integration scenario for the software component version for Ariba Cloud Integration 6.0. 6. Click Apply. 7. On the main Configuration: Integration Builder page, click the Objects tab. 8. Double-click to select the Receiver Determination for the integration scenario. 9. Click the Edit button. 10. Choose the software component version for the Ariba Cloud Integration 6.0. 11. Save and activate the changes.

58

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

Configuring the Interface Determination Context After you upgrade to the Ariba Cloud Integration 6.0, you must edit the Interface Determination for each of the migrated transactions.

Procedure 1. Go to the Configuration: Integration Builder to edit the Interface Determination for the Software Component Version. 2. Select the configuration scenario and open it. The Display Configuration Scenario page appears. 3. Click the Edit button. 4. Go to the ES Repository Model tab and click the Display Input Help button. The Select Process Integration Scenario from Enterprise Service Repository page appears. 5. Select the process integration scenario for the software component version for Ariba Cloud Integration 6.0. 6. Click Apply. 7. On the main Configuration: Integration Builder page, click the Objects tab. 8. Double-click to select the Interface Determination for the integration scenario. 9. Click the Edit button. 10. Choose the software component version of the Sender Interface for the Ariba Cloud Integration 6.0. 11. Click the Display Input Help button in the Operation Mapping column. 12. Select the operation mapping of software component version for Ariba Cloud Integration 6.0. 13. Save and activate the changes.

Configuring the Sender Agreement Context After you upgrade to the Ariba Cloud Integration 6.0, you must edit the Sender Agreement for each of the migrated transactions.

Procedure 1. Go to the Configuration: Integration Builder to edit the Sender Agreement for the Software Component Version. 2. Select the configuration scenario and open it. The Display Configuration Scenario page appears. Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

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

59

3. Click the Edit button. 4. Go to the ES Repository Model tab and click the Display Input Help button. The Select Process Integration Scenario from Enterprise Service Repository page appears. 5. Select the process integration scenario for the software component version for Ariba Cloud Integration 6.0. 6. Click Apply. 7. On the main Configuration: Integration Builder page, click the Objects tab. 8. Double-click to select the Receiver Determination for the integration scenario. 9. Click the Edit button. 10. Choose the software component version for the Ariba Cloud Integration 6.0. 11. Save and activate the changes.

Configuring the Receiver Agreement Context After you upgrade to the Ariba Cloud Integration 6.0, you must edit the Receiver Agreement for each of the migrated transactions.

Procedure 1. Go to the Configuration: Integration Builder to edit the Receiver Agreement for the Software Component Version. 2. Select the configuration scenario and open it. The Display Configuration Scenario page appears. 3. Click the Edit button. 4. Go to the ES Repository Model tab and click the Display Input Help button. The Select Process Integration Scenario from Enterprise Service Repository page appears. 5. Select the process integration scenario for the software component version for Ariba Cloud Integration 6.0. 6. Click Apply. 7. On the main Configuration: Integration Builder page, click the Objects tab. 8. Double-click to select the Receiver Determination for the integration scenario. 9. Click the Edit button. 10. Choose the software component version for the Ariba Cloud Integration 6.0. 11. Save and activate the changes.

60

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver

Configuring SLD and Transaction Processes

About Configuring the System Landscape Directory [page 61] Importing Ariba Network Product and Component Definitions [page 62] Defining Technical and Business System for Ariba Network [page 63] Defining the Business System for Ariba Network [page 63] Defining Technical and Business System for SAP ERP [page 64] Defining the Business Landscape for SAP ERP [page 65] About Configuring Transaction Processes [page 65] Importing the Design Package [page 66] About Configuring ERP Connectivity [page 67] Assigning Business Systems in the Integration Directory [page 67] Creating Communication Channels for ERP [page 68] Creating the IDoc Receiver Communication Channel [page 68] Creating the RFC Receiver Communication Channel [page 69] Configuring IDoc Metadata (Optional) [page 70] Configuring SAP NetWeaver PI Value Mapping [page 71] Creating a New Value Mapping Table [page 79]

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. 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 61]. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

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

61

Related Information

Importing Ariba Network Product and Component Definitions [page 62] Defining Technical and Business System for Ariba Network [page 63] Defining Technical and Business System for SAP R/3 [page 64]

Importing Ariba Network Product and Component Definitions Context

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

Procedure

1. From the PI main page, open the SLD Administration page. 2. Navigate to the Content section, and then click Import. 3. Select the AribaNetworkAdapterSAPNetweaver.SoftwareCatalog.zip by clicking on the Browse button, and then navigating to the file location. 4. Start the import. 5. In the Product Catalog, verify that the following product is available: ○ Vendor: ariba.com ○ Product: ASN ○ Version: NW04.1 6. Next, verify that the following component is available: ○ Vendor: ariba.com ○ Component: ARIBA_SUPPLIER_CONN_ADAPTER ○ Version: CIX

Results

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

62

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

Defining 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. E.g. TS_ASN ○ Host Name: Enter a host name here. E.g. an 5. Click Next. 6. Associate the ASC Connector 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_SUPPLIER_CONN_ADAPTER, is selected. 7. Click Finish.

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

Defining 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

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

63

Note The 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_SUPPLIER_CONN_ADAPTER, CIX of ariba.com, installed on the technical system, are selected, and then click Next. 7. Click Finish.

Defining 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 NetWeaver PI 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 212] 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.

64

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

Next Steps

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

Defining 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 NetWeaver PI 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.

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 NetWeaver PI connectivity to ERP. ● Configure SAP NetWeaver PI 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

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

65

Note The names for objects in the Directory used in the configuration procedures are examples provided for illustration. You may use them or replace them with names and format corresponding to your system environment.

Related Information

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

Importing the Design Package Context

The transport file AribaNetworkAdapterSAPNetweaver.Design.tpz contains the definition of the business scenarios.

Procedure

1. Copy the package file AribaNetworkAdapterSAPNetweaver.Design.tpz to the import directory on the SAP NetWeaver PI server, *****\SYS\global\xi\repository_server\import. For example, D:\usr\sap\ARB\SYS\global\xi\repository_server\import. 2. Open the Enterprise Services Builder: Design Tool from the SAP NetWeaver PI main page. 3. From the Tools menu, select the Import Design objects... option. 4. If you are trying to install the Cloud Release version of the SAP PI 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 AribaNetworkAdapterSAPNetweaver.Design.tpz from the available files list, and then click OK. 6. After the import completes, the component ARIBA_SUPPLIER_CONN_ADAPTER, CIX appears in the components list of the Integration Builder Design Tool.

66

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

About Configuring ERP Connectivity Context To enable communication between SAP NetWeaver PI and SAP ERP using IDoc documents, we need to configure the following parameters on the SAP NetWeaver PI ABAP stack: ● Configure the RFC Destination. ● Configure the Port for the IDoc Adapter SAP NetWeaver PI 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.

Note Enter the password in UPPER case.

Assigning 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 PI main page. 2. In the Objects tab of the Integration Builder, navigate to Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

Service Without Party

Business System.

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

67

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 61] section.

Note In 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.

Creating Communication Channels for ERP Create the communication channels used for 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 68] Creating the RFC Receiver Communication Channel [page 69] Configuring IDoc Metadata (Optional) [page 70]

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

68

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

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 Create 6. 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 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 Payload 11. Save and activate the communication channel.

Results

Note In the case of Multi-ERP implementation, you must create one CC_IDoc_Receiver channel per Business System, representing each of the SAP ERP instances involved in the integration.

Creating the RFC Receiver Communication Channel Procedure 1. In the Objects tab of the Integration Builder, navigate to BS_SAPR3_50

Service Without Party

Business System

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: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

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

69

○ 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).

Note Enter the password in UPPER case. 8. Edit the Maximum Connections option according to the excepted load. 9. Save and activate the communication channel.

Note In the case of Multi-ERP implementation, you must create one CC_RFC_Receiver channel per Business System, representing each of the SAP ERP instances involved in the integration.

Configuring IDoc Metadata (Optional) 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 NetWeaver PI. 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

70

Create

to add them.

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

Configuring SAP NetWeaver PI Value Mapping Configure SAP NetWeaver PI 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 61].

Related Information

Configuring Units of Measure (UOM) Code Mapping [page 71] Configuring Language Mapping [page 72] Configuring TimeZone Mapping [page 72] Configuring Global Variables [page 73] Configure the Mappings Between Business System and Logical System Names [page 76] Configuring Currency Mapping [page 77] Creating a New Value Mapping Table [page 79]

Configuring Units of Measure (UOM) Code Mapping As part of the transformation of documents from IDoc to cXML, or vice versa, certain codes, such as UOM, need to be mapped between different standards. This section provides the steps to configure these mappings. In the value mappings, use the following parameters for UOM transformation rules: ● Source Values: ○ Agency: UOM_ERP ○ 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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

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

71

UOM_ERP

LT

UOM_ISO

LTR

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

F

fr

Configuring TimeZone 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.

72

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

The following table shows examples of the TimeZone transformation values: Agency

Scheme

Value

XI_Global

GlobalVariable

TimeZone

BS_SAPR3_50

TimeZone

05:45

Configuring Global Variables Because SAP NetWeaver PI 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 NetWeaver PI Global Variable

Example SAP NetWeaver PI Value

PaymentProposal StartDateTime

2006-10-09T12:13: 13

Group Name

BPMConfig

Description Use this timestamp when the timestamp file for the PaymentProposal transac­ tion is not configured or its date/time parameters are empty. (Use it for test and devel­ opment only and NOT for pro­ duction.)

InvoiceStatus UpdateStartDate Time

IsMultiERPModeEnabled

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 devel­ opment only and NOT for pro­ duction)

true/false

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

BPMConfig

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

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

73

SAP NetWeaver PI Global Variable

Example SAP NetWeaver PI Value

Group Name

Description

ReceiptStartDate Time

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 devel­ opment only and NOT for pro­ duction.)

TimeZone

-08:00 or +05:30

BPMConfig

Use this parameter label to con­ figure 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 Busi­ ness System.

SAPExternalPaymen t Method

C

BPMConfig

Use this parameter to set the payment method used in exter­ nal payment. This must be a valid method defined in SAP. Set this parameter if you are using the

PaymentRemittanceAdvic e transaction. SAPAccountingDocT ype

SA

BPMConfig

Use this parameter to set the SAP accounting document type.

SAPUserName



BPMConfig

Use this parameter to set the SAP user name.

OrbianPaymentMethod

O

BPMConfig

Use this parameter to set the Orbian payment method.

OrbianPaymentMethod Description

Orbian

BPMConfig

Use this parameter to provide a description for the Orbian pay­ ment method.

R3LS

T90CLNT090

BPMConfig

Use this parameter to set the default SAP ERP logical system ID. Set this parameter if you are using the

PaymentRemittanceAdvic e transaction in a single ERP in­ stallation, where it is not manda­ tory to configure the System ID in the Ariba Network Buyer Ac­ count. In such cases, the Sys­ tem ID will be obtained from this parameter.

74

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

SAP NetWeaver PI Global Variable

Example SAP NetWeaver PI Value

Group Name

Description

BusinessSystem

BS_SAPR3_50

Lookup

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

Communication Channel

RFC_Lookup_Receiver

Lookup

This denotes the name of the communication channel to be used by the Lookup API in the mapping. Configure this param­ eter with a value that indicates the RFC Receiver Communica­ tion 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 con­ tain a value for the language code, then the value of this pa­ rameter 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 as­ signed to their purchase orders.

Note If you want to maintain multi­ ple doc types for purchase orders, you must specify NB, NA,AS in the Value for XI field. BlanketOrderDocType

LP

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

BPMConfig

This variable must contain the value for the SAP document type for blanket orders. LP is the default doctype in the SAP sys­ tem. However, customers can have a different doc type as­ signed to their blanket orders.

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

75

SAP NetWeaver PI Global Variable

Example SAP NetWeaver PI Value

ISU_ERP_INV_Canceled canceled/rejected _Rejected_Status

Group Name

Description 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 can­ cels an invoice in SAP ERP sys­ tem, 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 in­ voice is canceled in the SAP ERP system, then you are not re­ quired 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.

Note New customers are recom­ mended 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.

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

76

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

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

Note The 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

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

Configuring Currency Mapping You can configure the currency precision maintained in the TURX table on your SAP NetWeaver PI 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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

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

77

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

Maintaining the Value Mapping to Support Logical Systems in SAP NetWeaver PI Context

To process documents through the logical system, maintain the value mapping for the logical system in the SAP NetWeaver PI.

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

Name of the logical system

XI

GlobalVariable

R3PartnerProfileLS

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:

78

Agency

Scheme

Value For SystemIDFrom_cXML

SystemIDFrom_cXML

Lookup

System ID of the ERP system

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

Agency

Scheme

Value For

Group Name

SenderPartner_LogicalSystem

SenderPartner_LogicalSyste Lookup m

Name of the logical system

SystemIDFrom_cXML

Creating 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 For Agency: UOM_ERP Scheme: UOM ○ Target Values For Agency: UOM_ISO Scheme: 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.

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes

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

79

Configuring Integration Scenarios

About Configuring Integration Scenarios in the Integration Directory [page 80] Purchase Order Integration Scenario [page 82] Change Purchase Order Integration Scenario [page 89] Order Confirmation Integration Scenario [page 93] Ship Notice Integration Scenario [page 102] Ship Notice Integration Scenario to Support Creation of a Single Ship Notice Against Multiple Purchase Orders [page 109] Service Sheet and Service Sheet Response Integration Scenario [page 117] Invoice Integration Scenario [page 123] PayMeNow Integration Scenario [page 130] Payment Remittance Integration Scenario [page 137] Schedule Lines in Purchase Orders and Change Purchase Orders [page 143] Blanket Purchase Order Integration Scenario [page 144] Order Inquiries Integration Scenario [page 146] Scheduling Agreement Release Integration Scenario [page 153] Invoice Status Update Integration Scenario [page 160] ERP-Initiated Invoice Integration Scenario [page 167] Receipt Integration Scenario [page 173] Receipt Integration Scenario for Corrections and Returns in Receipts [page 179] Receipt Integration Scenario for Purchase Orders with Multiple Accounting Assignments [page 182] Payment Proposal Integration Scenario [page 184] Requisition Request Integration Scenario [page 190] Request for Quotation Integration Scenario [page 196] Sourcing Award to Contract Integration [page 201] Change Purchase Order Implementation Redesigned [page 208] Proxy Implementation for Outbound Transactions [page 210]

About Configuring Integration Scenarios in the Integration Directory This section describes how to import and configure the integration scenarios in the SAP NetWeaver PI Integration Directory for the supported transactions. Use an integration scenario from the Integration Repository as a

80

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios

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. If you are using a SAP NetWeaver PI 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." For more information, see Configuring the Software Component Version for Communication Channel Templates [page 82].

Note Do not activate the Change Lists feature of Integration Builder Configuration Tool until all the configuration steps are completed. Configure the Integration Scenarios for the following inbound transactions: ● Order Confirmation Integration Scenario [page 93] ● Configuring and Activating the Ship Notice Integration Scenario [page 102] ● Configuring and Activating the Ship Notice Integration Scenario to Support Creation of a Single Ship Notice Against Multiple Purchase Orders [page 109] ● Service Sheet and Service Sheet Response Integration Scenario [page 117] ● Invoice Integration Scenario [page 123] ● PayMeNow Integration Scenario [page 130] Configure the Integration Directory for the following outbound transactions: ● Purchase Order Integration Scenario [page 82] ● Change Purchase Order Integration Scenario [page 89] ● Change Purchase Order Implementation Redesigned [page 208] ● Schedule Lines in Purchase Orders and Change Purchase Orders [page 143] ● Blanket Purchase Order Integration Scenario [page 144] ● Order Inquiries Integration Scenario [page 146] ● Scheduling Agreement Release Integration Scenario [page 153] ● Payment Remittance Integration Scenario [page 137] ● Invoice Status Update Integration Scenario [page 160] ● ERP-Initiated Invoice Integration Scenario [page 167] ● Configuring and Activating the Receipt Integration Scenario [page 173] ● Payment Proposal Integration Scenario [page 184] ● Requisition Request Integration Scenario [page 190] ● Request for Quotation Integration Scenario [page 196] Configuring the Software Component Version for Communication Channel Templates [page 82]

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios

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

81

Configuring the Software Component Version for Communication Channel Templates Context If you are using a SAP NetWeaver PI 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. 5. Double click each of the following communication channel template. The Display Software Component Version page appears. Software Component Version

Communication Channel

Adapter Type

Namespace

Template

ARIBA_SUPPLIER_CONN _ADAPTER CIX of ariba.com

CCT_RFC_Lookup_Rece iver

RFC

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

ARIBA_SUPPLIER_CONN _ADAPTER CIX of ariba.com

CCT_IDoc_Receiver

IDOC

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

Purchase Order Integration Scenario You need to configure the integration scenario for the Purchase Order transaction in the Integration Directory to be able to run the transaction 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. 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:

82

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios

● 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 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 system, Ariba Network Adapter for SAP NetWeaver sends the storage location address as the shipTo address.

Note If 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. Ariba recommends that customers use the BADI customization in these cases.

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios

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

83

Workflow

Note Ensure that the Design package is imported into your system and ready before you run these steps. The following steps assume that the different Business Systems are defined in the SLD. For more information about configuring the SLD, see the “About Configuring the System Landscape Directory” [page 61] section. To configure purchase orders: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario. 3. Configure the Communication Channels. 4. Activate the new configuration.

Transferring the Purchase Order Integration Scenario Context

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

Procedure

1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select

Tools

Integration Builder , and then

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, then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_PurchaseOrder_Receive ○ Namespace: http://ariba.com/xi/ASN/PurchaseOrder ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory 6. Click Finish.

84

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios

Results Once the transfer is completed, the Model Configurator window appears.

About Configuring the Purchase Order Integration Scenario After the Integration Scenario is selected, you configure it using the following steps. 1. Assign the Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects.

Selecting the Model for the Scenario Procedure In the Model Configurator window, click the Select Component View button and then click Apply to select the unique model that is selected by default.

Next Steps After selecting the model, you must assign components to the application components of the selected integration scenario.

Assigning Components for the Purchase Order Integration Scenario 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 components for Ariba Network. 3. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. 4. Click on the row under the Communication Component column, then click on the Value List drop down and select Value List 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 Implementation. 7. Click Create Enhancement Implementation. 8. Enter a name and description for the enhancement and press Enter. 9. In the package popup, specify your Z or Y package, press Enter, and save the package to a transport request. 10. Copy the following code: 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. 11. Paste the copied code into the Enhancement Implementation. 12. Activate the enhancement and save it.

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios

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

91

Configuring 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 your SAP ERP system, navigate to 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->getsystemversion_ishierarchy EXPORTING ebeln = ekpo-ebeln et_edi_esll = edi_esll[1] IMPORTING flag = l_flag CHANGING int_edidd = int_edidd[1]. 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

92

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios

ENDIF

et_edi_esll

= edi_esll[].

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

Removing Change Order Configurations from Your Ariba Solution 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 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 Ariba Customer Support representative will follow up to complete the request.

Migrating Change Order Customizations If you employ change and cancel order transaction customizations in your 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 Ariba Customer Support representative will follow up to complete the request.

Order Confirmation Integration Scenario 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios

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

93

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

Note A 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 confirmationRequestt cXML. Otherwise the delivery date is determined from the corresponding PO item. 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 configure SAP ERP enhancements for comment support, see Configuring Implicit Enhancements for Comments in Order Confirmations [page 300] .

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.

94

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios

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

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 PI system as a ConfirmationRequest cXML document. 4. The SAP PI 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. To configure the Order Confirmation: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario. 3. Configure the Communication Channels. 4. Activate the new configuration.

Note Ensure that the design is imported into your system and ready before you run these steps. The following steps assume that the different Business Systems are defined in the SLD. For more information about configuring the SLD, see the “About Configuring the System Landscape Directory” [page 61] section.

Transferring the Order Confirmation Integration Scenario Context

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios

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

95

Procedure

1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select

Tools

Integration Builder , and then

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 drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_OrderConfirmation_Send ○ Namespace: http://ariba.com/xi/ASN/OrderConfirmation ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory. 6. Click Finish.

Results

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

About Configuring the Order Confirmation Integration Scenario Once the Integration Scenario is selected, you must configure it using the following steps: 1. Assign the Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects.

Selecting the Model for the Scenario Procedure

In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default.

96

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios

Next Steps After selecting the component view, you must assign components to the application components of the selected integration scenario.

Assigning Components for the Order Confirmation Integration Scenario 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 components for Ariba Network. 3. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. 4. Click on the row under the Communication Component column, then click on the Value List drop down and select Value List update_po_text

300

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

EXPORTING i_control is_ekko it_edidd CHANGING ct_status

= i_control = order = i_data[] = i_status[].

10. Click Save, and then click Activate to activate the changes.

Configuring Invoice Status Updates Buyers can send Invoice Status Updates to Ariba Network to let suppliers know about the status of the invoice on the buyer's system. Buyers send StatusUpdateRequest documents to send status for invoices that are processing, reconciled, paying, paid, rejected, invalid, parked, or parked invoices that have been deleted. Invoice Status Updates [page 301] Configuring the Invoice Status Update Transaction on your SAP ERP system [page 303]

Invoice Status Updates 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/deleted

Note When remittances have been reversed, the Invoice Status Update transaction does not change the status of the reversed invoices to "Reconciled" on the SAP system. This is applicable only for customers using Cloud Integration Release version 3.0 and earlier.

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

301

Requirements

The Invoice Status Update transaction requires the same parameters that are applicable for the ISU batch program on your SAP system:

Note The Invoice Status Update program (/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 an SAP ERP system 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 the SAP ERP system. 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 /ARBA/PARAM_TAB. The following document types must be maintained in 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 system: ● 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 the SAP system. ● 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

302

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

Note The 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.

Note For a PO-based invoice, the “Cancelled status is set based on the MM invoices. SAP notifies users when an invoice is cancelled through the MR8M message, “Please manually clear F1 document.” Users must ensure that they clear the F1 documents using F-44. If the F1 documents remain, Ariba Network Adapter for SAP NetWeaver sends all corresponding documents (payment proposal, remittances) associated to the cancelled MM invoice to Ariba Network.

Configuring the Invoice Status Update Transaction on your SAP ERP system Context

Ensure that you import the necessary SAP transport requests into your SAP ERP system. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

303

Procedure 1. Go to the Transaction code FIBF. 2. On the Environment menu, click Infosystem(Processes). 3. Click Execute. The Process Module 00005010, appears on the Business Transaction Events: Process Interface page. 4. Go to the Transaction code FIBF. 5. On the Settings menu, click Products and then click ...of a customer. 6. Enter a new product name and description. The function module product name must start with /ARBA/. 7. Click the Active check box to select it. 8. Go back to the previous page and click the Settings menu, click Process Modules and then click ...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’. 10. Save the changes.

Configuring Order Inquiries This section contains the following topics: ● Configuring SAP IDOC for Order Inquiries [page 304] ● Configuring the Partner Profile [page 305] ● Maintaining Condition Records for Inquiries [page 307] ● Implementing a Custom Exit for the Order Inquiries Function Module [page 308] ● Support for Additional cXML Fields [page 308]

Configuring SAP IDOC for Order Inquiries Context The following SAP IDOC configuration is required for using the sample data mapping: Transaction

OrderStatusRequest

IDOC Basic Type

ORDERS05

Message Type

ORDERS

Configuring the IDOC transaction to support inquiries for purchase orders on your SAP ERP system involves the following steps: ● Installing the transports for the purchase order and change purchase order transaction. For more information, see Importing the Design Package [page 313].

304

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

● Configuring the IDOC. For more information, see Configuring SAP IDOC for Order Inquiries [page 304]. ● Configuring the partner profile. For more information, see Configuring the Partner Profile [page 271].

Procedure

1. Use Transaction SM59 to create an RFC destination of type ERP. 2. Enter the Target host, System Number, Getaway host, Getaway service on the Technical Settings tab. Enter the Language, Client, User, Password on the Logon/Security tab, and then save your entries. 3. Use Transaction WE21 to create a port. 4. Choose Transactional RFC and click Create. 5. Enter port, description and RFC destination details, and then save your entries. For more information on the IDOC, see Configuring SAP IDOC for Order Inquiries [page 304].

Configuring the Partner Profile Procedure

1. Use 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. 3. In the Outbound parameters table, click the Add button and enter the following entries: ○ Partner Function: VN ○ Receiver Port: Configure the SAP PI system that sends the inquiries. ○ Partner Number: Corresponding Partner Number ○ Partner Type: LI ○ Partner Role: VN ○ Message Type: ORDERS ○ Receiver Port: Enter the SAP PI 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:

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

305

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

306

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

Results

Parameter Message Type

Basic Type

Extension

Value

ORDERS

ORDERS05

/ARBA/ORDENQ

Maintaining Condition Records for Inquiries Procedure

1. In the main screen when you start the transaction NACE, select application records.

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 Implementation. 7. Click Create Enhancement Implementation. 8. Enter a name and description for the enhancement and press Enter. 9. In the package popup, specify your Z or Y package, press Enter, and save the package to a transport request. 10. Copy the following code: 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. 11. Paste the copied code into the Enhancement Implementation. 12. Activate the enhancement and save it.

Configuring 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

323

Procedure 1. In your SAP ERP system, navigate to 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 Enhancement popup to display Select or Create Enhancement ImplementationChoose Type of Enhancement. 9. Click Create Enhancement Implementation. 10. Choose Type ofEnter 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: l_flag(5) cl_purchaseorder cl_po_hierarchy ls_idoc_status lx_appl_idoc

TYPE TYPE TYPE TYPE TYPE

c, REF TO /arba/cl_purchaseorder, REF TO /arba/cl_po_hierarchy, bdidocstat, 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.

324

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

13. Paste the copied code into the Enhancement Implementation. 14. Activate the enhancement and save it. 15. Right-click on the line just before the end of 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 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.

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 PI adapter 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 Implementing Customer Exits for Invoices with Service Type Line Items [page 326]. Customers can implement the following methods for service sheets: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

325

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

Configuring Service Sheets Buyers must configure their SAP ERP system to process service sheets created for purchase orders containing service type items. Implementing Customer Exits for Invoices with Service Type Line Items [page 326] Specifying Time-Out Intervals for Processing Service Sheets [page 327] Implementing Enhancements for Service Sheets Created for New Purchase Orders [page 328] Implementing Enhancements for Service Sheets Created for Changed or Canceled Purchase Orders [page 330]

Implementing 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. Go to the transaction code 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 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.

326

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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( EXPORTING i_bukrs = i_bukrs i_lifnr = i_lifnr i_idoc_contrl = i_idoc_contrl IMPORTING e_bukrs = e_bukrs e_lifnr = e_lifnr e_change = e_change CHANGING t_idoc_data = t_idoc_data[] ). 11. Repeat Steps 7 to 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( CHANGING t_frseg = t_frseg[] t_co = t_co[] t_ma = t_ma[] e_rbkpv = e_rbkpv e_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.

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

327

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

Note This value depends on the time-out value required by the customer.

Implementing 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 Function Perform fill_srv_orders. 4. Double-click the function, Perform. 5. Select 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.

328

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

329

EXPORTING EDI_ESLL = edi_esll[] CHANGING INT_EDIDD = int_edidd[] . endif. 19. Activate the code.

Implementing 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. Select 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 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

330

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

CHANGING xdruvo = xdruvo. 13. Activate the code.

Configuring ERP-Initiated Invoices to Use the IDOC Configure your ERP system to can use the GSVERF03 IDOC to send MM invoices and the FIDCCP02 IDOC to send FI invoices.

Note You 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 Configuring the NACE Setting to Send ERS Invoices [page 331] Configuring the NACE Setting to Send Invoicing Plans [page 333] Configuring the NACE Setting to Send MIRO Invoices [page 334] Implementing the Customer Exit for MM Invoices [page 335] Implementing Routines to Prevent Creation of Duplicate MM IDOCs [page 336] Maintaining Partner Profiles [page 337] Configuring the FI Invoices [page 338] Setting Document Type Filters for FI Invoices [page 339] Maintaining Output Types for FI Invoices [page 340] Implementing the Customer Exit for FI Invoices [page 341] Handling Errors [page 342]

Related Information ERP-Initiated Invoices Using the IDOC Transmission Method [page 23]

Configuring the NACE Setting to Send ERS Invoices Context Configure the NACE setting to send the ERS (Evaluated Receipt Settlement) invoices using the IDOC. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

331

Procedure 1. Start transaction NACE. 2. Select application MR and then click Output types. 3. Select ERS Output type for ERS invoices and then click Processing routines. 4. Select 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: For example, 3000. ○ 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.: For example, 1000. ○ Partn. Type: LI ○ Partner Role: VN ○ Message Type: GSVERF In the Outbound Options tab, ensure that you maintain the following entries: ○ Receiver port: Enter the name of the receiver port. ○ Transfer IDoc Immed.: Select the radio button. ○ Basic type: GSVERF03 ○ Extension: /ARBA/ GSVERF03 ○ Cancel Processing After Syntax Error: Select the check box. 14. In the Partner Profiles screen, maintain the following values: ○ Partner No.: For example, 1000 .

332

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

○ Partn. Type: LI In 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.

Configuring the NACE Setting to Send Invoicing Plans Context Configure the NACE setting to send the Invoicing plans using the IDOC.

Procedure 1. Start transaction NACE. 2. Select application MR and then click Output types. 3. Select ERS Output type for ERS invoice and then click Processing routines. 4. Select 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 Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

333

○ 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: For example, 1000. ○ 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.: Select the radio button. ○ Basic type: GSVERF03 ○ Extension: /ARBA/ GSVERF03 ○ Cancel Processing After Syntax Error: Select the check box. 18. Click Save.

Configuring the NACE Setting to Send MIRO Invoices Context Configure the NACE setting to send the MIRO invoices using the IDOC.

334

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

Procedure 1. Start transaction NACE. 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

Implementing 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( Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

335

EXPORTING if_ident is_data_ers is_data_rap is_data_kons if_segnam CHANGING ct_idoc_data

= = = = =

if_ident is_data_ers is_data_rap is_data_kons if_segnam

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

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

336

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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 then 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_:

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 select the routine number on the Maintain: Requirements Output control page. 14. On the Edit menu, click Activate to activate the routine.

Maintaining 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 for that you want to maintain 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 In the Outbound Options tab, ensure that you maintain the following entries: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

337

○ Receiver port: Enter the name of the receiver port. ○ Transfer IDoc Immed.: Select the radio button. ○ Basic type: FIDCCP02 ○ Extension: /ARBA/ FIDCCP02 ○ Cancel Processing After Syntax Error: Select the check box. 4. Repeat Step 3 for the other Message Type: SYNCH.

Configuring the 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.

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.

338

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

Results

Ensure that the outbound parameters at the logical system profile have been created. Verify these changes in the Outbound Options tab. See Maintaining Partner Profiles [page 337] to create partner profiles.

Setting 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

E1FIKPF Enter a name for the ALE object type. For example, BLART.

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:

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

339

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.

Note If you maintain the company code instead of the global company code in the Global CoCde filter, the SAP ERP system 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 system. 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.

Maintaining 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 /ARBA/ PARAM_TAB table, 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 NACE transaction.

340

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

Procedure 1. Go to SM30. 2. In the /ARBA/ PARAM_TAB table, maintain the new output types that you require for the FI invoice. 3. Go to Transaction NACE. 4. Click Procedures. 5. Select application MR and then click Procedures. The Change View "Procedures": Overview page appears. 6. Click MR0002 procedure in the Procedures table and then double-click the Control folder dialog structure. The Change View “Control”: Overview page appears. 7. Enter the routine number that you created in the Requirement field for the ERS condition type in the Reference Step Overview section on the Change View “Control”: Overview page. 8. Repeat Step 5. Click the MR0004 procedure and repeat Step 6-7.

Implementing 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. 5. Save the changes. The SAP Enhancements in Enhancement Project page 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: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

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

341

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 codes. To maintain the tax code, do the following: ○ Go to transaction code SM30. ○ Maintain the required tax codes in the /ARBA/TAXCAT_MAP table.

Note When an IDOC is generated for an FI invoice, the Ariba Procurement Solution does not map the Distribution node.

Handling Errors Buyers can use the SLG1 transaction code to view all messages in the application log on the SAP system. Errors that occur while transmitting the MM and FI invoices in the Ariba Procurement Solution are stored in the SXMB_MONI if a system error occurs while sending the invoices from the ERP system to the PI. Buyers can use the SLG1 T-code to view all messages in the application log on the SAP system.

342

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System

Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

Overview [page 343] Installation Requirements for SAP Suite Add-On [page 346] Setting Up the cXML Adapter [page 347] Configuring Logging for the SAP Suite Add-On [page 350] Configuring the cXML Adapter [page 350] Configuring the System Landscape Directory [page 350] Configuring Transaction Processes [page 354] Configuring Integration Scenarios in the Integration Directory [page 356] Configuring the Integration Directory for Inbound Transactions [page 357] Configuring the Integration Directory for Outbound Transactions [page 364] Linking Multiple SAP Instances with Ariba Network [page 371] Testing the SAP NetWeaver for Suite Add-On Configuration [page 375] Understanding Error Handling [page 376] Monitoring the cXML Adapter from Runtime Workbench [page 379] Deploying the Project [page 380] Enabling Support for Attachments [page 381] Using Endpoints for Integration with SAP NetWeaver for SAP Suite Add-On [page 382] Using the SAP NetWeaver PI KeyStore [page 382]

Overview The Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On is an add-on module for SAP business applications that enables integration between Ariba Network and SAP Suite Add-On component available in your SAP ERP system. SAP Suite Add-On is developed by SAP to allow SAP ERP systems to connect to Ariba Network through SAP NetWeaver PI. SAP ERP buyers and suppliers using Ariba Network Adapter for SAP NetWeaver integrated with SAP Suite Add-On and Ariba Network can now send and receive transactional documents through the PI layer or directly without the Ariba Integration Toolkit.

Note The SAP Suite Add-On module generates documents in cXML format and therefore does not require ABAP transports.

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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

343

The Ariba Network Adapter for SAP NetWeaver runs on the SAP NetWeaver Process Integration (PI), and can be thought of as a library for SAP NetWeaver PI. This library includes integration processes and Java libraries that implement the cXML transport protocol and provide a set of facilities for resolving differences between SAP and Ariba Network. For more information about cXML and Ariba Network, refer to the following documents, available from Connect (http://connect.ariba.com ): ● Ariba Network Integration Guide ● Ariba Network Buyer Administration Guide ● Ariba cXML Solutions Guide ● cXML User’s Guide The Ariba Network Adapter for SAP NetWeaver consists of the following: ● The design package, which contains integration processes, interface objects, and communication channels. ● The cXML Adapter, which conforms to the J2EE Connector Architecture (JCA) specification, and implements the cXML transport protocol. For more information about the JCA specification, see the relevant section on the Sun Java web site (http:// www.java.sun.com ). ● The product and component definitions that are available in a CIM file. The following graphic illustrates how the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On enables the communication flow between Ariba Network and the SAP Suite Add-On.

SAP NetWeaver PI is a platform for process integration within SAP NetWeaver. It facilitates cross-system business processes. In particular, it enables different versions of SAP and non-SAP systems from different vendors running on different platforms to communicate with each other. SAP NetWeaver PI integrates the following components used by the Ariba Network Adapter for SAP NetWeaver and its modules: ● The Integration Engine is the central runtime component of the SAP NetWeaver PI Integration Server used for receiving, processing, and forwarding messages. ● The Adapter Engine is a runtime component of the SAP NetWeaver PI Integration Server. It uses adapters to connect the Integration Engine to SAP systems (RFC adapter) and external systems.

344

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

Supported Document Types

The following transactions are supported as part of the Ariba Network integration with SAP Suite Add-On: Outbound Transactions for Buyers

Inbound Transactions for Buyers

Purchase Order

Order Confirmation

Change Purchase Order

Ship Notice

Goods Receipt

Invoice

Payment Proposal

CC Invoice

Receipt Request

Pay Me Now

Remittance Advice

Service Entry Sheet

Remittance Status Update

Quote Message

Service Entry Sheet Response Status Update Request Quote Request Outbound Transactions for Suppliers

Inbound Transactions for Suppliers

Order Confirmation

Purchase/Sales Order

Ship Notice

Change Purchase Order

Invoice

Goods Receipt

CC Invoice

Payment Proposal

Pay Me Now

Receipt Request

Service Entry Sheet

Remittance Advice

Quote Message

Remittance Status Update Service Entry Sheet Response Status Update Request Quote Request

Workflow for Configuring the Ariba Network Adapter for SAP NetWeaver for SAP 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 Suite Add-On component. 6. Testing the configuration. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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

345

Installation Requirements for SAP Suite Add-On Supported SAP Netweaver PI Versions The following table lists the Ariba Network Adapter for SAP NetWeaver versions and the supported SAP Netweaver PI versions that they can be deployed on: Ariba Network Adapter for SAP NetWeaver Version

Supported SAP Netweaver PI Versions

Cloud Integration 1

SAP Netweaver PI 7.1 SAP Netweaver PI 7.3

Cloud Integration 2 or higher

SAP Netweaver PI 7.1 SAP Netweaver PI 7.3 SAP Netweaver PI 7.4

For information about the platforms that the SAP NetWeaver suite supports, see the following SAP NetWeaver section on the SAP Service Marketplace: service.sap.com > SAP NetWeaver > SAP NetWeaver PI 7.X > Availability.

Ariba Network Requirements Ensure that you have the following Ariba Network requirements before installing the Ariba Network Adapter for SAP NetWeaver: ● A valid, configured Ariba Network Buyer account. For more information about configuring your Ariba Network Buyer account, see the Ariba Network 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 Ariba 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 detailed 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 391] section. ● The Ariba Network’s Certificate Authorities certificates are stored in the SAP NetWeaver PI Keystore. The cXML Adapter uses the certificates stored in the SAP NetWeaver PI Keystore to connect to Ariba Network.

Installation Files To install the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On, you need the relevant archive file which is available on Ariba’s support interface, Ariba Connect (http://connect.ariba.com).

346

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

For example, AribaNetworkAdapterSAPNetweaver_vCI_1.zip. The archive ZIP files contain the following components: Product definition files

AribaNetworkAdapterSAPNetweaver.SoftwareCatalog.zip

Design and Integration configuration files

AribaNetworkAdapterSAPNetweaver_SapAddOn.tpz

cXML Adapter and metadata definition files

AribaNetworkAdapterSAPNetWeaver.sca CacheCatalog.xml CanonicalCatalog.xml

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. This section contains the following topics: ● Understanding cXML Adapter Document Transmission ● Deploying the cXML Adapter ● Configuring the Log ● Configuring the cXML Adapter

Understanding cXML Adapter Document Transmission Ariba Network exchanges business documents using the cXML (commerce eXtensible Markup Language) protocol. cXML defines document formats and interaction processes designed for exchanging procurementoriented 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 Ariba Network Certification [page 380].

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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

347

Deploying the cXML Adapter If your version of SAP netweaver PI is prior to PI 7.3 EHP1, use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI. From SAP netweaver version PI7.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.

Deploying the cXML Adapter Using JSPM Context

Use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI.

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

Note To 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.

348

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

Undeploying the Adapter using the Textconsole Context

You must use the textconsole script to undeploy the adapter.

Procedure

1. Go to \j2ee\console. 2. Run textconsole.bat or textconsole.sh. The Telnet console appears. 3. Login with the relevant admin user. 4. Run the following 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, 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: '[]'' >

Undeploying the Adapter using the Textconsole Procedure

Run the following at the Telnet prompt: deploy name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_deploy_error=stop

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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

349

Configuring Logging for the SAP Suite Add-On 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 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. Login to the SAP NetWeaver PI 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 drop down list. 4. Select the node (package) com ariba asc , to set the logging level to log the complete adapter processing information, or select 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 drop-down list, and then click Save Configuration in the toolbar.

Note For additional information, see the Ariba Network Integration 1.0 for SAP Business Suite http:// help.sap.com/se4aribanet10.

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 356] section. For a description of the parameters and instructions for how to configure retry attempts, see cXML Adapter Parameters [page 391].

Configuring the System Landscape Directory Once you have installed the cXML Adapter, you must then 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

350

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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

Importing Ariba Network Product and Component Definitions Import the product and component definitions of Ariba products that will work with SAP NetWeaver PI, as a CIM file.

To import product and component definitions: Procedure 1. From the SAP NetWeaver PI 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 AribaNetworkAdapterSAPNetweaver.SoftwareCatalog.zip is stored. Select this file. 6. Click Import. 7. From the SAP NetWeaver PI 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. Next, verify that the following component is available: ○ Vendor: ariba.com ○ Component: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CIX of ariba.com ○ Version: CIX Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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

351

Results The Ariba Network Adapter for SAP NetWeaver is now recognized by the Integration Repository and Directory.

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

To define the Technical System for Ariba Network: 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. E.g. TS_ASN ○ Host Name: Enter a host name here. E.g. an 5. Click Next. 6. Associate the ASC Connector 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 ARBA_SUPPLIER_CONN_ADAPTER, is selected. 7. Click Finish.

Next Steps Next, set up the business system for the Ariba Network system using the Business System Wizard.

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.

352

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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.

Note The 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 ARBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com, installed on the technical system, are selected, and then click Next. 7. Click Finish.

Defining the Technical 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. 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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

353

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

Defining the Business System 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 NetWeaver PI 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.

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. ● Configure SAP NetWeaver PI 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.

Note The names for objects in the Directory used in the configuration procedures are examples provided for illustration. You may use them or replace them with names and format corresponding to your system environment.

354

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

Importing 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 NetWeaver PI server, *****\SYS\global\xi\repository_server\import. For example, D:\usr\sap\ARB\SYS\global\xi\repository_server\import. 2. Open the Integration Builder: Design Tool from the SAP NetWeaver PI main page. 3. From the Tools menu, select the Import Design objects... option. 4. Select AribaNetworkAdapterSAPNetweaver_SapAddOn.tpz from the available files list, and then click OK. 5. After the import completes, the component ARBA_SUPPLIER_CONN_ADAPTER CIX appears in the components list of the Integration Builder Design Tool.

Note The External SAP Add-On schema is http://ariba.com/xi/ASN/AddOn/CommonBasis. The Adapter metadata is http://ariba.com/xi/ASCAdapter.

Configuring SAP ERP Connectivity The inbound and outbound documents are exchanged between SAP NetWeaver PI and SAP ERP by using ABAP proxies. For information about proxy configuration for outbound documents, see cXML Adapter Parameters [page 391].

Assigning 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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

355

Procedure 1. Open the Configuration: Integration Builder from the PI 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 Configuring the System Landscape Directory [page 350] section.

Note If you have multiple ERP systems, 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 unnecessary channels. 7. Click Finish.

Configuring Integration Scenarios in the Integration Directory This section describes how to import and configure the integration scenarios in the SAP NetWeaver 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.

Note Do 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 NetWeaver PI versions: ● SAP NetWeaver PI 7.1 ● SAP NetWeaver PI 7.3 single stack (Java only) ● SAP NetWeaver PI 7.3 dual stack (ABAP and Java) ● SAP NetWeaver PI 7.4 single stack (Java only) ● SAP NetWeaver PI 7.4 dual stack (ABAP and Java)

356

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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 Directory

Integration Repository

Enterprise Service Builder

to the

Integration Builder . For more information, see:

○ Transferring the Integration Scenario for Inbound Transactions [page 357] ○ Transferring Integration Scenario for Outbound Transactions [page 364] 2. Configure the Integration Scenario. For more information, see: ○ About Configuring the Integration Scenario for Inbound Transactions [page 359] ○ About Configuring the Integration Scenario for Outbound Transactions [page 366] 3. Configure the Communication Channels. For more information, see: ○ Configuring Communication Channels for Inbound Transactions [page 362] ○ Configuring Communication Channels for Outbound Transactions [page 369] 4. Activate the integration scenario. For more information, see: ○ Activating the Scenario for Inbound Transactions [page 363] ○ Activating the Scenario for Outbound Transactions [page 370]

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 343]. ○ 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.

Configuring the Integration Directory for Inbound Transactions Transferring 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.

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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

357

Procedure

1. From the SAP NetWeaver PI main page, select Integration Directory login to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select

Tools

Integration Builder , and then

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 pull-down menu and select Input Help. 4. Select the Process Integration Scenario for the following inbound transactions from the Enterprise Services Repository screen: Buyer ○ Order Confirmation Name: AR_AddOn_OrderConfirmation_Send Namespace: http://ariba.com/xi/ASN/AddOn/OrderConfirmation Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Ship Notice Name: AR_AddOn_AdvanceShipNotice_Send Namespace: http://ariba.com/xi/ASN/AddOn/AdvanceShipNotice Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Invoice Name: AR_AddOn_Invoice Namespace: http://ariba.com/xi/ASN/AddOn/Invoice Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Pay Me Now Name: AR__AddOn_PayMeNow_Send Namespace: http://ariba.com/xi/ASN/AddOn/PayMeNow Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Service Entry Sheet Name: AR_AddOn_ServiceEntrySheet_Send Namespace: http://ariba.com/xi/ASN/AddOn/ServiceEntrySheet Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ QuoteMessage Name: AR_AddOn_QuoteMessage_Send Namespace: http://ariba.com/xi/ASN/AddOn/QuoteMessage Software Component Version: ARIBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com Supplier ○ Sales Order Name: AR_AddOn_SalesOrder_Send Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com ○ Payment Remittances Name: AR_AddOn_PaymentRemittanceRequest_Send Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com 5. Click Continue.

358

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

6. If required, change the name of the scenario for the Integration Directory. 7. Click Finish and then Close. Once the integration scenario transfer is completed, the Model Configurator window appears.

About Configuring the Integration Scenario for Inbound Transactions 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.

Assigning the Model for Inbound Transactions Procedure 1. In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique model that is selected by default. 2. After selecting the model, assign components to the application components for the selected integration scenario.

Assigning Components for Inbound 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 |CC_AddOn_Invoice_cXML_Sender ○ PayMeNow |< Name of the Business System for Ariba Network> | CC_PayMeNow_cXML_Sender ○ Service Entry Sheet |< Name of the Business System for Ariba Network> | CC_ServiceEntrySheet_cXML_Sender ○ Quote Message < Name of the Business System for Ariba Network> | CC_AddOn_QuoteMessage_cXML_Receiver.

362

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

Supplier ○ Sales Order |< Name of the Business System for Ariba Network>| CC_AddOn_Supplier_SalesOrder_cXML_Receiver | ○ Payment Remittance < 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. 3. Under the cXML Configuration section, select the Use SAP Add on Suite check box.

Note If you created the channel by copying from an existing channel, you must change the request type for each of the transactions to the 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 391]. 6. Save the changes.

Activating 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 SAP NetWeaver PI.

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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

363

Configuring the Integration Directory for Outbound Transactions Transferring 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 NetWeaver PI main page, select Integration Directory login to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select

Tools

Integration Builder , and then

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 pull-down menu and select Input Help. 4. Select the process integration scenario for the following transactions from the Enterprise Services Repository screen: Buyer: ○ Purchase Order Name: AR_AddOn_PurchaseOrder_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PurchaseOrder Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ CC Invoice Name: AR__AddOn_CCInvoice_Receive Namespace: http://ariba.com/xi/ASN/AddOn/ERPInvoice Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Proposal Name: AR__AddOn_PaymentProposal_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PaymentProposal Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Remittance Name: AR__AddOn_PaymentRemittance_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittance Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Remittance Status Update Name: AR__AddOn_PaymentRemittanceSUR_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittanceSUR Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com

364

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

○ Receipts Name: AR_AddOn_GoodsReceipt_Receive Namespace: http://ariba.com/xi/ASN/AddOn/GoodsReceipt Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ ServiceUpdateResponse Name: AR_AddOn_StatusUpdateResponse_Receive Namespace: http://ariba.com/xi/ASN/AddOn/StatusUpdateResquest Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com

Note Buyers 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. ○ QuoteRequest Name: AR_AddOn_QuoteRequest_Receive Namespace: http://ariba.com/xi/ASN/AddOn/QuoteRequest Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com Supplier ○ Sales Order Confirmation Name: AR_AddOn_SalesOrderConfirmation_Receive Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com ○ Ship Notice Name: AR_AddOn_OutboundDeliveryNotification_Receive Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com ○ Invoice Name: AR_AddOn_Invoice_Receive Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com 5. Click Continue. 6. If required, change the name of the scenario for the Integration Directory. 7. Click Finish.

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On

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

365

About Configuring the Integration Scenario for Outbound Transactions 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.

Assigning the Model for Outbound Transactions Procedure 1. In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique model that is selected by default. 2. After selecting the model, assign components to the application components for the selected integration scenario.

Assigning 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 components for Ariba Network. 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 ERP), the Email notification is used to send an email when an error occurs (mainly connection issues). This is because during the pull (getPending), PI 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 (ERP -> AN), the sending operation initiated by PI is synchronous, and if any exception occurs, it is related to a message from PI. 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 Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter

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

385

to the retry mechanism implemented by PI). 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).

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 section of Chapter 2 “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: Table 5: Application Errors: Status

ERR101

ERR102

ERR201

ERR202

ERR203

ERR204

ERR205

ERR301

ERR302

ERR303

ERR401

386

Text

Invalid Configuration Parameter. Trusted certificates not installed properly. Incorrect Client Certification

Authentication Failed on ASN

ASN Internal Server Error

Send cXML to AN Failed (Invalid Request)

Send cXML to AN Failed (Temporary Error)

Send cXML to AN Failed (Unrecoverable Error)

Get Profile Transaction Failed

Get Pending Transaction Failed

Outbound Transaction Failed

Invalid Outbound Message (PI -> ASN)

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter

Status

ERR402

ERR403

ERR404

ERR405

ERR406

ERR407

Text

Invalid Inbound Message (ASN -> PI)

Duplicate Outbound Message

Duplicate Inbound Message

Outbound Message Type Inconsistent with Channel Definition

Inbound Message Type Inconsistent with Channel Definition

Can not find corresponding record in download config file

Table 6: Runtime Error: Status

Text

ERR501

Unexpected Error

Table 7: ERP Errors: Status

ECC101

ECC102

ECC103

Text

Configuration Load Failed

IO Error

Ariba Network Not Available

Understanding Email Notifications The following are the different parts of an error notification email: ● Date: The date and time of the error. ● Error: The 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]. Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter

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

387

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

Monitoring of 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.

Monitoring the cXML Adapter from Runtime Workbench After you deploy the Ariba Network Adapter for SAP NetWeaver on SAP NetWeaver PI 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.

Note If 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.

388

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter

Deploying the Project When you have customized your data mappings and tested all processes, you are ready to export and then import the project as two SAP NetWeaver PI Export files (tpz files) using SAP NetWeaver PI Integration Builder. SAP NetWeaver PI Integration Builder contains two parts: ● Design tool, which contains interface objects, mapping objects and integration processes ● Configuration tool, which contains business services and routing rules. For more information, see the SAP NetWeaver PI documentation. The design tpz file can contain one or more namespaces, which include the integration processes, mapping objects and interface objects. The Configuration tpz file can contain one configuration scenario, which includes business services and routing rules. You can build as many tpz files as you need for one project. For more information about how to export a tpz file, see the SAP NetWeaver PI documentation. Each tpz file works as a single unit within SAP NetWeaver PI Integration Builder. For example, if you have multiple namespaces within a single Design tpz file, all the namespaces will be imported and exported at the same time, assuming that no other conditions are specified for these namespaces.

Ariba Network Certification Ariba must certify any Ariba Network Adapter for SAP NetWeaver that works with Ariba Network. Certification is the process by which 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 Connect and provides instructions to guide you through the certification process.

Downloading the Ariba Network Integration Guide from 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter

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

389

4. Extract the IntegrationGuide.pdf file from the downloaded ZIP file.

390

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter

cXML Adapter Parameters

This section describes common, inbound, and outbound parameters for the cXML Adapter. Common Parameters [page 391] Inbound Parameters [page 393] Outbound Parameters [page 395] Configuring Retry Attempts [page 395] Configuring Proxy Server Parameters [page 395]

Common Parameters Parameter Name

Usage Type

Data Type

Value

Description

Adapter Status

Mode

required

string

Test/ Production

Status

required

string

Active/ Inactive

Credential Mode

required

string

Shared secret/ Client certificate

Credential Domain

required

string

NetworkId/ NetworkUserI d/DUNS

Credential

required

string

Deployment mode of the adapter. Default value: Test

The status of the adapter. Default value: Active

Authentication Authentication method on Ariba Network. Default value: Client certificate

The domain for the Buyer's credential. Default value: NetworkId

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

Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters

string

The Buyer's shared secret on Ariba Net­ work. This parameter is only required when parameter credentialMode is set as Shared secret.

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

391

Parameter Name

Port

Usage Type

required

Data Type

Value

Description HTTPS port. This parameter is only required when parameter credentialMode is set

integer

as Client certificate. Default value: 443

KeyStore View

Indicates the name of the view that contains all the keys/certificates required for authen­ tication between the cXML Adapter and Ariba buyer.

required

string

AN ID

required

string

User Agent

required

string

Language

required

string

Data Directory

required

string

cXML Version

required

string

1.2.018 or higher

Use XML Validation

optional

boolean

true/false

Use SAP Add on Suite

required

boolean

documentExp iryPeriod

required

integer

cXML Configuration Ariba Network ID. Default value: AN01000000001 A textual string representing the client sys­ tem that is conducting the cXML conversa­ tion. Default value: Ariba SN Buyer

en-US

Attribute needed for constructing cXML re­ quest. Default value: en-US Base directory needed to run the adapter. Default value: D:/AribaDataDir

The version number of the cXML document data definition to be used to generate the cXML documents exchanged with Ariba Network. This version number will be used in the DOCTYPE entity of the cXML docu­ ments. A flag that specifies whether or not the vali­ dation is done on the exchanged cXML documents according to the cXML dtds. The validation should be enabled during the in­ stallation/ customization phase to ensure that the exchanged cXML documents are compliant. In the production phase, the vali­ dation could have a negative impact on per­ formance. When this option is enabled, the cXML Adapter integrates Ariba Network with the SAP Suite AddOn component available in your SAP ERP system.

minimum 1 and max 360

Specify the expiry time for a document in hours after which the document can be re­ sent 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

392

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

Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters

Parameter Name

Usage Type

Data Type

Value

Use Email Notificatio ns

required

boolean

SMTP Server Host

required

string

Sender Address

required

string

Recipient Address

required

string

CC Address

optional

string

Sender Name

required

string

Description

true/false

A switch to turn on/off email notification. Default value: false

The SMTP server IP address or host name.

The email account for sending email.

The email account for email receiver.

The email account for email cc receiver.

The description name for sender. Default value: AribaSN Adapter

Admin Email Authenticat ion

required

boolean

User

optional

string

Password

optional

string

true/false

A flag that represents whether or not the email server requires authentication for sending email. Default value: false The email sender account. This parameter is only required when parameter emailAuthentication is set as true. The password for the email sending ac­ count. This parameter is only required when parameter emailAuthentication is set as true.

Inbound Parameters Parameter Name

Usage Type

Data Type

Value

Description

cXML Configuration

GetProfil e URL

required

string

Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters

URL used to send ProfileRequest. Default value: https://

certservice.ariba.com/ service/transaction/ cxml.asp

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

393

Parameter Name

Usage Type

Data Type

Value

Description

GetProfil e Interval (Minutes)

required

intege r

Poll interval of profileRequest ex­ pressed in minutes. Default value: 60

GetPendin g Interval (Minutes)

required

intege r

Poll interval of getPendingRequest ex­ pressed in minutes. Default value: 15

Max Documents in GetPendin g

required

intege r

StatusUpd ateReques tRetryCou nt

required

intege r

StatusUpd ateReques tRetryInt erval (Minutes)

required

intege r

SystemID for GetPendin g

optional

string

Max number of Documents that can be received from the pending queue in a single getPending request. Default value: 2

Number of times the status update re­ quest is to be retried if the first status update request failed. Default value: 0 Time to wait before sending the next status update, expressed in minutes. Default value: 0

The system ID for your ERP appli­ cation

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 configured in your Ariba Network buyer account.

Timeout

required

intege r

5 minutes

When the cXML Adapter is download­ ing 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 ex­ iting.

Inbound Request Type

Inbound Request Type

394

required

string

One of the following:

ConfirmationRequest InvoiceDetailRequest ShipmentNoticeRequest PayMeNowRequest

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

The request type for Inbound. Default value:

ConfirmationRequest

Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters

Outbound Parameters Parameter Name

Usage Type

Data Type

Value

Description

cXML Configuration

GetProfile URL

required

URL used to send ProfileRequest. Default value: https://

string

certservice.ariba.com/ service/transaction/ cxml.asp GetProfile Interval (Minutes)

required

intege r

required

string

Poll interval of profileRequest ex­ pressed in minutes. Default value: 60

Outbound Request Type

Outbound Request Type

One of following:

OrderRequest ChangeOrderReques t InvoiceUpdateRequ est PaymentRequest PaymentRemittance Request

The request type for Outbound. Default value: OrderRequest

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 NetWeaver Administrator. This includes the interval between retry attempts for outbound messages sent by SAP NetWeaver PI to the cXML adapter, and the number of inbound documents sent by the cXML adapter to PI. For more information on how to configure a message to be retried, see the SAP NetWeaver Process Integration 7.1 documentation.

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) Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters

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

395

To enable secure communication through a proxy server, configure the following parameters for the cXML Adapter: Parameter Name

Type

Value

No (default) Yes

Description Enables or disables the use of the proxy server for remote communication with Ariba Network

Use Proxy Server

Boolean

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 authenti­ cation on the proxy server. If None, the proxy server does not require authenti­ cation. 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.

396

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

Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters

Ariba SAP Objects

This appendix describes the SAP development objects provided by Ariba as part of the SAP integration. The audience for this appendix includes: ● BASIS administrators who import Ariba’s SAP transports and need to see the list of objects they are importing. ● ABAP developers who are responsible for customizing the Ariba SAP objects. SAP Certification [page 397] /ARBA/COMMON_OBJECTS Package [page 398] /ARBA/PURCHASEORDER Package [page 400] /ARBA/CHANGEPURCHASEORDER Package [page 401] /ARBA/ERPINVOICE Package [page 402] /ARBA/INVOICESTATUSUPDATE Package [page 403] /ARBA/PAYMENTPROPOSAL Package [page 404] /ARBA/RECEIPT Package [page 405] /ARBA/REQUISITION Package [page 405]

SAP Certification The SAP code delivered by Ariba is certified by SAP. As part of this certification, a new namespace called /ARBA/ is registered and all SAP objects delivered by Ariba are renamed from Z_ to /ARBA/. For example, the function module called Z_ARIBA_INVOICE_STATUS_UPDATE is renamed to /ARBA/ INVOICE_STATUS_UPDATE. The SAP NetWeaver PI content is changed by importing the RFCs and ABAP objects renamed with the /ARBA/ namespace into SAP NetWeaver PI.

Note Starting 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.

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects

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

397

/ARBA/COMMON_OBJECTS Package The /ARBA/COMMON_OBJECTS package contains Ariba development objects for Ariba Network Adapter for SAP NetWeaver for SAP NetWeaver objects.

Function Groups and Modules The following are the function groups in the /ARBA/COMMON_OBJECTS package: Table 8: /ARBA/COMMON_OBJECTS Function Groups Function Group

/ARBA/LOOKUP

/ARBA/TABLE_MAIN

Description Lookup Function Modules

Extended Table Maintenance (Generated)

Table 9: /ARBA/COMMON_OBJECTS Function Modules Description

Function Module

External access to R/3 tables via RFC

/ARBA/RFC_READ_TABLE

Retrieves pre-filtering restrictions

/ARBA/PREFILTER_ADAPTER

/ARBA/WHERE_CONDITION_FILTER

/ARBA/ORBIAN_INFO_GETDETAIL

Ariba function to construct where condition

Payment Proposal ID for Orbian Integration

Read BSIK and BKPF data

/ARBA/READ_BSIK_BKPF

Tables The following are the tables for the /ARBA/COMMON_OBJECTS package: Table 10: /ARBA/COMMON_OBJECTS Tables Table

Description

/ARBA/AN_VENDOR

398

Ariba Network Vendor Table

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects

Table

Description Ariba table to store configurable parameters

/ARBA/PARAM_TAB

Stores invoices created in ERP and which are sent to AN

/ARBA/AN_ERPINV

Tables read by /ARBA/RFC_READ_TABLE Function Module

/ARBA/LOOKUPTAB

Table to store Proxy Parameters for ISU, PP, ERP Invoice, and Receipts

/ARBA/PROXYPARAM

Note The 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 SM30 transaction to generate table maintenance objects to maintain records in this table. You must maintain the following entries in the /ARBA/PARAM_TAB table using Transaction 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 Transaction SM30: Fieldname

Value

BUKRS

3000

LIFNR

1000

You must maintain the following entries in the /ARBA/TAXCAT_MAP table using Transaction SM30: Fieldname

Value

MWSKZ

I1

TAX_CATEGORY

Sales Tax

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects

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

399

Structures The following are the structures for the /ARBA/COMMON_OBJECTS package: Table 11: /ARBA/COMMON_OBJECTS Structures Structure

/ARBA/WTAB

/ARBA/RFC_READ_TABLE

Description Table Structure for "WHERE (itab)" Statement

Structure to support RFC READ TABLE for Unicode Systems

/ARBA/PURCHASEORDER Package Function Group

/ARBA/PURCHASEORDER

Function Module Name

/ARBA/PO_ACCOUNTING_INFO

/ARBA/PO_SERVICE_INFO

Description Purchase Order Adapter Objects

Description Accounting Information for PO

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

400

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects

Table Type

Description

/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

/ARBA/CHANGEPURCHASEORDER Package Function Group

/ARBA/CHANGEPURCHASEORDER

Function Module Name

/ARBA/PO_GET_DETAIL

Description Change Purchase Order

Description Change Purchase Order Get Detail

Structure Name

Description

/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

Table Type

Description

/ARBA/BAPIEKET_T

Purchase Order Schedule Lines

/ARBA/BAPIEKKN_T

Purchase Order Accounting Details

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects

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

401

Table Type

Description

/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

Ariba Purchase Order Accounting Details

/ARBA/PO_ITEMS_T

Ariba Purchase Order Items

/ARBA/PO_SERVICEACCOUNT_T

Purchase Order Service Account Details

/ARBA/PO_SERVICEITEMS_T

Ariba Service Purchase Order Item Detail

/ARBA/ERPINVOICE Package Function Group

Description

/ARBA/ERPINVOICE

ERP Invoice Adapter objects

Function Module Name

Description

/ARBA/INVOICE_GET_DETAILS

Ariba Invoice FI documents to AN

Program Name

Description

/ARBA/ERPINVOICE_EXPORT

ABAP proxy for Invoice Interface

Table Name

Description

/ARBA/TAXCAT_MAP

Ariba Tax code to Tax Category Map

Structure Name

Description

/ARBA/INVOICE_HEADER_DETAILS

Ariba ERP Initiated Invoice Header details

/ARBA/INVOICE_LINE_DETAILS

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

Table Type

Description

/ARBA/INVOICE_HEADER_DETAILS_T

Invoice Header details

402

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects

Table Type

Description

/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

/ARBA/INVOICESTATUSUPDATE Package Function Group

Description

/ARBA/INVOICESTATUSUPDATE

Invoice Status Update function group

Function Module Name

Description

/ARBA/INVOICE_STATUS_UPDATE

Ariba Invoice status update

Program Name

Description

/ARBA/INVSTATUPDT_EXPORT

Program for Calling Invoice Status Update proxy

Structure Name

Description

/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

/ARBA/REVERSED_PAYMENTS

Reversed Payments Details

Table Type

Description

/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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects

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

403

Table Type

Description

/ARBA/REVERSED_INVOICE_T

Reversed Invoices

/ARBA/REVERSED_PAYMENTS_T

Reversed Payments

/ARBA/PAYMENTPROPOSAL Package Function Group

Description

/ARBA/PAYMENTPROPOSAL

Payment Proposal Adapter Objects

Function Module Name

Description

/ARBA/PAYMENT_PROPOSAL

Payment Proposal RFC

Program Name

Description

/ARBA/PAYMENTPROPOSAL_EXPORT

Payment Proposal Program (Proxy)

Structure Name

Description

/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

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

Table Type

Description

/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

404

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects

/ARBA/RECEIPT Package Program Name

Description

/ARBA/RECEIPT_PUBLISH

Proxy for Receipt Export

Structure Name

Description

/ARBA/PO_DETAIL

Ariba Purchase Order Detail Structure

/ARBA/RECEIPT

Ariba Material Document Structure

Table Type

Description

/ARBA/PO_DETAIL_T

Ariba Purchase Order Detail Structure

/ARBA/RECEIPT_T

Ariba Material Document

/ARBA/GR_HEADER_T

Goods Receipt Header

/ARBA/GR_ITEMS_T

Goods Receipt Items

/ARBA/REQUISITION Package Function Group

Description

/ARBA/REQPARAM

Extended Table Maintenance (Generated)

Program Name

Description

/ARBA/REQUISITION_EXPORT

Requisition Export (Proxy)

Table Name

Description

/ARBA/REQPARAM

Table to store Ariba Requisition Parameters

Structure Name

Description

/ARBA/REQUISITION

Requisition Details

Table Type

Description

/ARBA/REQUISITION_T

Requisition

Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects

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

405

Revision History

The following table provides a brief history of the updates to this guide. Ariba updates the technical documentation for its On Demand solutions 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. 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. Document Version

Month/Year of Update

Updated Chapter/ Section

1

September 2015

n/a Multiple Chapters

Short Description of Change

●

Reset revision history for Cloud Integration Release 6.0.

Ariba Cloud Integration Release 6.0 ●

Updated throughout for the Ariba Cloud Integration Release 6.0.

2

3

4

October 2015

November 2015

December 2015

Integration of Cata­ log Data in SAP ERP and Ariba Net­ work

●

Removed the limitation on transactional data that is no longer applicable.

Service Sheet and Service Sheet Re­ sponse Integration Scenario

●

Updated the integration scenario for Service Sheet and Service Sheet Response.

Integration of Cata­ Updated section log Data in SAP ERP and Ariba Net­ work Change Purchase Order Implementa­ tion Redesigned

Updated the section as this is available only for customers using Ariba Cloud Integration 4.0 and earlier.

Configuring the In­ terface Determina­ tion Settings for the Sourcing Award to Contract Integration Sce­ nario

Updated the task with the results and example section.

Configuring Implicit Updated the code in Step 12. Enhancements for New Service Or­ ders

406

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

Ariba Network Adapter for SAP NetWeaver Setup Guide Revision History

Important Disclaimers and Legal Information

Coding Samples Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

Accessibility The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).

Ariba Network Adapter for SAP NetWeaver Setup Guide Important Disclaimers and Legal Information

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

407

www.ariba.com

Copyright © 1996–2015 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.