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


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



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


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



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


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



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


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



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


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



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


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


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.



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



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


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



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


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



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.



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



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


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



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.



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



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


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



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



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


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.



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



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.



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



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.



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



5. Click Start. The Deploy Queue screen appears.

The Completed screen appears.



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



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

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



39

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

40



5. Click Start. The Deploy Queue screen appears.

The Completed screen appears.



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



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


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



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



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


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


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_
name> to /ARBA/

Ariba Network Adapter for SAP NetWeaver Setup Guide

Recommend Documents