Ariba Network Adapter for SAP NetWeaver Setup Guide

AribaCloud 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 Ariba Network Adapter for SAP NetWeaver Setup Guide 2 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Content Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Configuring SLD and Transaction Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 About Configuring the System Landscape Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Importing Ariba Network Product and Component Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Defining Technical and Business System for Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Defining the Business System for Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Defining Technical and Business System for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Defining the Business Landscape for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 About Configuring Transaction Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Importing the Design Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 About Configuring ERP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Assigning Business Systems in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Creating Communication Channels for ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Creating the IDoc Receiver Communication Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Creating the RFC Receiver Communication Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Configuring IDoc Metadata (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Configuring SAP NetWeaver PI Value Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Configuring Units of Measure (UOM) Code Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Configuring Language Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Configuring TimeZone Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Configuring Global Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 Configure the Mappings Between Business System and Logical System Names. . . . . . . . . . . . . . . . 76 Configuring Currency Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Maintaining the Value Mapping to Support Logical Systems in SAP NetWeaver PI. . . . . . . . . . . . . . . 78 Creating a New Value Mapping Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Configuring Integration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 About Configuring Integration Scenarios in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . 80 Configuring the Software Component Version for Communication Channel Templates . . . . . . . . . . . 82 Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Transferring the Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 About Configuring the Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Configuring Communication Channels for the Purchase Order Integration Scenario. . . . . . . . . . . . . 87 Configuring Interface Determination Settings for the Purchase Order Integration Scenario. . . . . . . . 88 Activating the Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Change Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Reconfiguring the SAP Partner Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 About Configuring Implicit Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Removing Change Order Configurations from Your Ariba Solution. . . . . . . . . . . . . . . . . . . . . . . . . . 93 Migrating Change Order Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Ariba Network Adapter for SAP NetWeaver Setup Guide Content © 2015 SAP SE or an SAP affiliate company. All rights reserved. 3 Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Transferring the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 About Configuring the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Configuring Communication Channels for the Order Confirmation Integration Scenario. . . . . . . . . . .99 Configuring Receiver Determination Settings for the Order Confirmation Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Configuring Interface Determination Settings for the Order Confirmation Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Activating the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Additional Configuration Tasks for the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . 102 Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Transferring the Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 About Configuring the Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Configuring Communication Channels for the Ship Notice Integration Scenario. . . . . . . . . . . . . . . .106 Configuring Receiver Determination Settings for the Ship Notice Integration Scenario. . . . . . . . . . . 107 Configuring Interface Determination Settings for the Ship Notice Integration Scenario. . . . . . . . . . .108 Activating the Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Ship Notice Integration Scenario to Support Creation of a Single Ship Notice Against Multiple Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Transferring the Ship Notice Integration Scenario for Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . 111 About Configuring the Ship Notice Integration Scenario for Multiple POs. . . . . . . . . . . . . . . . . . . . . 112 Configuring Communication Channels for the Ship Notice Integration Scenario with Multiple POs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Configuring Receiver Determination Settings for the Ship Notice Integration Scenario with Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 Configuring Interface Determination Settings for the Ship Notice Integration Scenario with Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Activating the Ship Notice Integration Scenario for Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Configuring the Ship Notice Integration Scenario to Receive Ship Notices with Zero Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Service Sheet and Service Sheet Response Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Transferring Service Sheet and Service Sheet Response Scenarios. . . . . . . . . . . . . . . . . . . . . . . . .118 About Configuring the Service Sheet and Service Sheet Response Integration Scenarios. . . . . . . . . 119 Configuring Communication Channels for the Service Sheet and Service Sheet Response Integration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Activating the Service Sheet and Service Sheet Response Integration Scenarios. . . . . . . . . . . . . . . 122 Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 Transferring the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 About Configuring the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Configuring Communication Channels for the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . 127 Configuring Receiver Determination Settings for the Invoice Integration Scenario. . . . . . . . . . . . . . 128 Configuring Interface Determination Settings for the Invoice Integration Scenario. . . . . . . . . . . . . . 129 Ariba Network Adapter for SAP NetWeaver Setup Guide 4 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Content Activating the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130 PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Transferring the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 About Configuring the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Configuring Communication Channels for the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . 134 Configuring Receiver Determination Settings for the PayMeNow Integration Scenario. . . . . . . . . . . 135 Configuring Interface Determination Settings for the PayMeNow Integration Scenario. . . . . . . . . . . 136 Activating the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 Transferring the Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 About Configuring the Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . .139 Configuring Interface Determination Settings for the Payment Remittance Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Activating the Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 Schedule Lines in Purchase Orders and Change Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Prerequisites to Enabling Schedule Lines in Purchase Orders from your SAP ERP System to Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Configuring the Purchase Order Integration Scenario to Support Schedule Lines. . . . . . . . . . . . . . .144 Blanket Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Configuring the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Transferring the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 About Configuring the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Configuring Communication Channels for the Order Inquiries Integration Scenario. . . . . . . . . . . . . 152 Configuring Interface Determination Settings for the Order Inquiries Integration Scenario. . . . . . . . 153 Activating the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 About Configuring the Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . 154 Configuring Communication Channels for the Scheduling Agreement Release Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Configuring Interface Determination Settings for the Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Activating the Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . 159 Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160 Transferring the Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 About Configuring the Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . 161 Configuring Communication Channels for the Invoice Status Update Integration Scenario. . . . . . . . 165 Configuring Interface Determination Settings for the Invoice Status Update Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Activating the Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Canceling MIRO Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Ariba Network Adapter for SAP NetWeaver Setup Guide Content © 2015 SAP SE or an SAP affiliate company. All rights reserved. 5 Transferring the ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 About Configuring the ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . 168 Configuring Communication Channels for the ERP-Initiated Invoice Integration Scenario. . . . . . . . . 172 Configuring Interface Determination Settings for the ERP-Initiated Invoice Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 Activating the ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Receipt Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Transferring the Integration Scenario for Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 About Configuring the Integration Scenario for Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Configuring Communication Channels the Receipts Integration Scenario. . . . . . . . . . . . . . . . . . . . 177 Configuring Interface Determination Settings for the Receipts Integration Scenario. . . . . . . . . . . . . 178 Activating the Receipts Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178 Additional Receipts Integration Requirement for SAP NetWeaver 7.1 EHP1. . . . . . . . . . . . . . . . . . . 179 Receipt Integration Scenario for Corrections and Returns in Receipts. . . . . . . . . . . . . . . . . . . . . . . . . 179 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Data Flow Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 cXML Changes to Support Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Configuring the Receipt Integration Scenario to Support Returns and Corrections. . . . . . . . . . . . . . 182 Receipt Integration Scenario for Purchase Orders with Multiple Accounting Assignments. . . . . . . . . . . 182 Activating the MM Multiple Account Assignments Enterprise Business Function. . . . . . . . . . . . . . . 183 Adding the Code in the BADI Implementation for MM Multiple Account Assignments. . . . . . . . . . . . 184 Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Transferring the Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 About Configuring the Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Configuring Interface Determination Settings for the Payment Proposal Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Activating the Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Enabling Quick Enablement for Payment Proposal Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . 190 Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Transferring the Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 About Configuring the Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . 192 Configuring Communication Channels for the Requisition Request Integration Scenario. . . . . . . . . 194 Configuring Interface Determination Settings for the Requisition Request Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Activating for the Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Request for Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196 Transferring the Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 About Configuring the Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Configuring Communication Channels for the Quotation Integration Scenario. . . . . . . . . . . . . . . . 200 Configuring Interface Determination Setting for the Quotation Integration Scenario. . . . . . . . . . . . 200 Activating the Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 Sourcing Award to Contract Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Ariba Network Adapter for SAP NetWeaver Setup Guide 6 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Content Transferring the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . .202 About Configuring the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . 203 Configuring the Communication Channel for the Sourcing Award to Contract Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Configuring the Interface Determination Settings for the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Activating the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . 208 Change Purchase Order Implementation Redesigned. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Enabling Change Purchase Order Redesign. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Implementing the Redesigned Change Purchase Order Transaction. . . . . . . . . . . . . . . . . . . . . . . .209 Proxy Implementation for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Enabling Proxy Implementation for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Advanced Configuration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Linking Multiple SAP instances with Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Document Routing Mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Multi-ERP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Configuring Supplier Quick Enablement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Customizing Data Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Downloading Mapping Workbooks from Connect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Enabling Migration of Mapping Customization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Enabling Support for Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Attachments for Outbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Attachments for Inbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Managing Email Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Support for Proxy ByPass. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 HTTPS Support for Attachment Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Configuring Proxy Server ByPass for Attachment Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Troubleshooting Proxy Server ByPass for Attachment Processing. . . . . . . . . . . . . . . . . . . . . . . . . 227 Support for 2-Way Match. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Using Endpoint Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Using Endpoints for Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229 Enabling Endpoint Integration in SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Endpoint Integration for Multiple ERP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Using the SAP NetWeaver PI KeyStore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Configuring the cXML Adapter to Use the SAP NetWeaver PI Keystore. . . . . . . . . . . . . . . . . . . . . . 231 PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Enabling PDF Invoice Copy Attachment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Using PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Processing of PDF Invoice Copy Attachments by the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . 234 BADI Implementation for the BADI Definition INVOICE_UPDATE. . . . . . . . . . . . . . . . . . . . . . . . . . 237 About Configuring Your SAP ERP System for PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . 243 Ariba Network Adapter for SAP NetWeaver Setup Guide Content © 2015 SAP SE or an SAP affiliate company. All rights reserved. 7 Defining a New Document Class for PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . . . . . . . . 243 Defining a New Document Type for Invoice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Create a Link Between the Standard Business Object and the New Document Type for Invoice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Maintaining the INVOICE_EMAIL_SEND Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Maintaining the ZDEL Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 Configuring the Attachment Processing Mode for PDF Invoice Copy Attachments. . . . . . . . . . . . . . 245 Integrating SAP ERP with the Ariba Spot Quote Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 About SAP ERP and Ariba Spot Quote Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 SAP ERP Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Enabling SAP ERP and Ariba Spot Quote Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 SAP ERP and Ariba Spot Quote Integration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249 SAP ERP and Ariba Spot Quote Integration Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Configuring Ariba Network Buyer Settings for Ariba Spot Quote. . . . . . . . . . . . . . . . . . . . . . . . . . 250 Messages Mapping for Ariba Spot Quote. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 How to Handle cXML Document Errors for Ariba Spot Quote. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Integration of Catalog Data in SAP ERP and Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250 About Integration of Catalog Data in SAP ERP and Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . 251 Enabling the Integration of Catalog Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Using the Catalog Export Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 About Processing Purchase Information Records and Material Master Records. . . . . . . . . . . . . . . 256 Uploading Catalog Changes Using Mediated Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Uploading Catalog Changes Using the Incremental Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Maintaining Catalog Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Configuring Catalog Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Configuring Your SAP ERP System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Importing Custom Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Configuring SAP IDocs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Configuring SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Configuring SAP for IDoc Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 Configuring the Partner Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 Creating an Output Type for the Entry Sheet Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Maintaining Condition Records for Outbound Transactions: POs. . . . . . . . . . . . . . . . . . . . . . . . . . 279 Maintaining Condition Records for Outbound Transactions: Service Sheets. . . . . . . . . . . . . . . . . . 280 Making Additional Change PO Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Maintaining Variants for Remittance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Making Additional Invoice Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Making Additional Tax and Accrual Calculation Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Maintaining Bank Key for the House Bank for Payment Remittance Advice. . . . . . . . . . . . . . . . . . . 288 Making User Exit Enhancements to Support Shipping and Handling Charges. . . . . . . . . . . . . . . . . 288 Ariba Network Adapter for SAP NetWeaver Setup Guide 8 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Support for Additional cXML Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Configuring Advanced Pricing Details. . . . . . . . . 310 Configuring the Partner Profile for Scheduling Agreement Releases. 292 Business AddIns. . . . . . . . . . . . . . . . . . . . . . . . . . 319 Configuring your System for Quote Message Documents. . . 305 Maintaining Condition Records for Inquiries. . . . . . . . . . 9 . . . . . . All rights reserved. . . . . . 317 Maintaining Printer Default Values for Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Proxy Settings in SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Implementing a Custom Exit for Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Maintaining Condition Records for Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 ABAP Programs for Outbound Transactions Implemented Using Proxies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Configuring IDOC Metadata (Optional). . . . . . . Maintaining Global Company Code. . . . . . 313 Configuring the SAP IDOC for Ship Notices Against Multiple Purchase Orders. . . . . . . . . .308 Support for Additional cXML Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Invoice Status Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Configuring Parameters in the ARBA/PARAM_TAB Table for Returns and Corrections in Receipts . . . . . . . . . . . . . 310 Maintaining Condition Records for Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Configuring Proxy Settings for Single Stack (Java only) Instances of SAP NetWeaver PI 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Configuring SAP IDOC for Order Inquiries. . 320 Configuring SAP NetWeaver PI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Configuration Related to Export of Requisitions from SAP ERP. . . . . . . . . . .301 Configuring the Invoice Status Update Transaction on your SAP ERP system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Configuring IDoc Metadata for Scheduling Agreement Releases (Optional). . . 297 Documentation of RFCs Within the SAP NetWeaver Adapter. . 294 Configuring Proxy Settings for SAP NetWeaver 7. . . . . . . . . . . . . . . . 321 Ariba Network Adapter for SAP NetWeaver Setup Guide Content © 2015 SAP SE or an SAP affiliate company. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Configuring the Partner Profile or Ship Notices Against Multiple Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Configuring Quote Request and Quote Message Documents. . . . . . .3 and above. . . 298 Defining Authorizations for Running Ariba Network Transactions. . . 307 Implementing a Custom Exit for the Order Inquiries Function Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Configuring your System for Quote Request Documents. . . . . . . . .3 and above. . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Configuring Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . 308 Configuring Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Configuring Invoice Status Updates. . . . . . . . . . . . . . .313 Configuring Ship Notices Against Multiple Purchase Orders. . . . . .1 or Dual Stack (ABAP and Java) Instances of SAP NetWeaver PI 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Configuring SAP IDOC for Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . 303 Configuring Order Inquiries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Configuring the Partner Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299 Configuring Implicit Enhancements for Comments in Order Confirmations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 Defining Technical and Business System for Ariba Network. . . . . . . . . . . . . . . . . . 322 Direct Invoicing of Purchase Order Service Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 About Configuring Implicit Enhancements. 348 Deploying the cXML Adapter Using JSPM. . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Implementing Routines to Prevent Creation of Duplicate MM IDOCs . . . . . . . . . . . . . . . . . . . . . . . 336 Maintaining Partner Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .347 Understanding cXML Adapter Document Transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Overview. . . . . . . . . . . . . 353 Defining the Business System for SAP ERP. . . . . . . . . . . . . . 346 Setting Up the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Implementing the Customer Exit for MM Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Importing Ariba Network Product and Component Definitions. 343 Installation Requirements for SAP Suite Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Configuring the NACE Setting to Send Invoicing Plans. . . . 341 Handling Errors. . . . . . . . . . . 338 Setting Document Type Filters for FI Invoices. . . . . . . . . . . . . . . . . . . . . 340 Implementing the Customer Exit for FI Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Configuring Logging for the SAP Suite Add-On. . . . . . . . 342 Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On. . . . . . . . . . . . . . . . . . 348 Undeploying the Adapter using the Textconsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Configuring ERP-Initiated Invoices to Use the IDOC. . . . . . . . . . . . . . .325 Configuring Service Sheets. . . . . . . 350 Configuring the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Specifying Time-Out Intervals for Processing Service Sheets. . . . . . . . . . 352 Defining the Technical System for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339 Maintaining Output Types for FI Invoices. . . . . . . . . . . . . . . . . . . . . . . .327 Implementing Enhancements for Service Sheets Created for New Purchase Orders. . . 331 Configuring the NACE Setting to Send ERS Invoices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . All rights reserved. . . . . . . . . . . . . . . 326 Implementing Customer Exits for Invoices with Service Type Line Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Deploying the cXML Adapter. . . . . . . . 321 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Support for Line Level Hierarchies in Service Purchase Orders. . . . . . 333 Configuring the NACE Setting to Send MIRO Invoices. . . . . . . . . . . . . . 352 To define the Technical System for Ariba Network:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Implementing Enhancements for Service Sheets Created for Changed or Canceled Purchase Orders. . . . .350 Configuring the System Landscape Directory. . . . . . . . . . . . . . . . . . . . . . . 351 To import product and component definitions:. . . . . . . . . . . . . . . . . . . 352 To define the Business System for Ariba Network:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Undeploying the Adapter using the Textconsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Ariba Network Adapter for SAP NetWeaver Setup Guide 10 © 2015 SAP SE or an SAP affiliate company. . . . . . . . . . 337 Configuring the FI Invoices. . . . . . . . . . . . . . . . . . . . . . 369 Activating the Scenario for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . All rights reserved. . . . . . . . . . . . 376 Understanding Error and Status Codes. . . . . . . . . . . . . . . . 357 About Configuring the Integration Scenario for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Configuring SAP ERP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Configuring Sender And Receiver Relations for Individual Connections for Inbound Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Monitoring the cXML Adapter from Runtime Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Transaction Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 Configuring Sender and Receiver Relations for Individual Connections For Outbound Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Understanding Email Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Transferring the Integration Scenario for Inbound Transactions. . . . . . . 379 Deploying the Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Supported cXML Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Attachments for Outbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366 Assigning Components for Outbound Transactions. . . . . . 381 Attachments Support in cXML. . . . . . . . . . . . . . . . . . . . . 359 Assigning Components for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Ariba Network Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355 Configuring Integration Scenarios in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Generate Objects for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Configuring Communication Channels for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Linking Multiple SAP Instances with Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Assigning Business Systems in the Integration Directory. . . . 359 Assigning the Model for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . .363 Configuring the Integration Directory for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 Assigning the Model for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Enabling Support for Attachments. . . . . . . . . . . . . . . 371 Multi-ERP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Activating the Scenario for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Configuring Communication Channels for Inbound Transactions. . . . . . . . . . . . 375 Sending a Purchase Order for Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Downloading the Ariba Network Integration Guide from Connect:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Understanding Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Transferring Integration Scenario for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Running a getPending Transaction for Testing. . . . . . . . . . . . . . . . . . . . . . . . .357 Configuring the Integration Directory for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Importing the Design Package. . . . . . . . . . . . . . . . . . . 360 Generating Objects for Inbound Transactions. . . . . . . 381 Ariba Network Adapter for SAP NetWeaver Setup Guide Content © 2015 SAP SE or an SAP affiliate company. . . . . . . . . . . . 364 About Configuring the Integration Scenario for Outbound Transactions. . . . . . . . . . . 356 Workflow for Configuring the Integration Scenario for Inbound And Outbound Transactions. . . 374 Testing the SAP NetWeaver for Suite Add-On Configuration. . . . . . . . . . . Attachments for Inbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395 Configuring Proxy Server Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .382 Using the SAP NetWeaver PI KeyStore. . . . . . . 405 Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Testing the Configuration. . 382 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . All rights reserved. . . . . . . . . . . . . . . . . . . . . . . 404 /ARBA/RECEIPT Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Monitoring of the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Common Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 SAP Certification.402 /ARBA/INVOICESTATUSUPDATE Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388 Deploying the Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Downloading the Ariba Network Integration Guide from Connect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Monitoring the cXML Adapter from Runtime Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 /ARBA/REQUISITION Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Configuring Communication Channels to Use SAP NetWeaver PI Keystore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Testing the Adapter. . . . . . . . . . . . . . . . . . . 385 Understanding Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 /ARBA/PURCHASEORDER Package. . 397 /ARBA/COMMON_OBJECTS Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Ariba Network Certification. . . . . . . . . . . . . . 400 /ARBA/CHANGEPURCHASEORDER Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 Outbound Parameters. . . . . . . . . . . . . . . . 403 /ARBA/PAYMENTPROPOSAL Package. . . . . . . . . . . . . . . 384 Running a getPending Transaction for Testing. . 395 Configuring Retry Attempts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Using Endpoints for Integration with SAP NetWeaver for SAP Suite Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395 Ariba SAP Objects. . . . . . . . . . . . . . . . . . . . 389 cXML Adapter Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 /ARBA/ERPINVOICE Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Inbound Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Ariba Network Adapter for SAP NetWeaver Setup Guide 12 © 2015 SAP SE or an SAP affiliate company. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Sending a Purchase Order for Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . see the relevant section on the Sun Java web site (http:// www.com ) ● SAP Transport files installed on the SAP ERP system. 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. which contains integration processes. and implements the cXML transport protocol For more information about the JCA specification. refer to the following documents on Ariba Connect (http:// connect. which conforms to the J2EE Connector Architecture (JCA) specification. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. 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 information in this guide is applicable to the Ariba Network Adapter for SAP NetWeaver. and mappings to convert IDoc to cXML and cXML to IDoc ● The cXML Adapter installed on the SAP Netweaver PI component. For more information about cXML and Ariba Network. All rights reserved. The following graphic illustrates how the Ariba Network Adapter for SAP NetWeaver enables the communication flow between Ariba Network and the SAP ERP system. interface objects. 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.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. For information on the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On. and can be thought of as a library for SAP NetWeaver PI. The Ariba Network Adapter for SAP NetWeaver runs on the SAP NetWeaver Process Integration (PI) component. 13 .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.ariba.sun.java. 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. see Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On [page 13]. ● The Adapter Engine is a runtime component of the SAP NetWeaver PI Integration Server. it enables different versions of SAP and non-SAP systems from different vendors running on different platforms to communicate with each other. used by your SAP ERP system differ from the data elements used in cXML documents. It facilitates cross-system business processes. 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.SAP NetWeaver PI is a platform for process integration within SAP NetWeaver. many-to-one. In particular. and one-to-many mapping scenarios. and from cXML to your SAP ERP system. The Ariba Network Adapter for SAP NetWeaver determines how data from your SAP ERP system populates a corresponding cXML document. The element mapping mechanism handles one-to-one. and forwarding messages. All rights reserved. Data Flow and Data Element Mapping The Ariba Network Adapter for SAP NetWeaver processes outbound and inbound cXML transactions. inbound transactions flow from Ariba Network to the SAP ERP system. or fields. and it performs two-way mapping: from your SAP ERP system to cXML. Ariba Network Adapter for SAP NetWeaver . It processes the integration processes at runtime. processing. The data elements. 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. Ariba Network Adapter for SAP NetWeaver Setup Guide 14 © 2015 SAP SE or an SAP affiliate company. Outbound transactions flow from your SAP ERP system to Ariba Network. It uses adapters to connect the Integration Engine to SAP systems (RFC adapter) and external systems. ● The Integration Engine is the central runtime component of the SAP NetWeaver PI Integration Server used for receiving. For more information about customization. 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. Figure 1: Element Mapping Overview The Ariba Network Adapter for SAP NetWeaver maintains a set of cross reference or mapping tables. the Ariba cXML Solutions Guide and the sample mapping tables. All rights reserved. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. see the cXML User’s Guide. The remainder of this section discusses the cXML Interfaces on a general level as they pertain to the Ariba Network Adapter for SAP NetWeaver. see Customizing Data Mappings [page 216]. 15 . 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. indicating that a permanent error has occurred and has been logged.0. for all lines with category D. Unplanned service lines must specify a maximum amount. Suppliers must create service sheets for those lines to describe both services and material goods delivered for the order. In the transformed OrderRequest document for a service purchase order. The adapter maintains a profile cache that is updated every time the Profile transaction runs.Profile Transaction When the Ariba Network Adapter for SAP NetWeaver sends a ProfileRequest to Ariba Network. SAP NetWeaver 7. Support for Service Purchase Orders Purchase orders with lines that specify category D are considered service purchase orders on Ariba Network. Ariba Network Adapter for SAP NetWeaver . see Schedule Lines in Purchase Orders and Change Purchase Orders [page 143]. see Scheduling Agreement Release Integration Scenario [page 153]. For more information. All rights reserved. For more information. 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. quantity. 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. indicating that Ariba Network accepted the document. it responds with a ProfileResponse indicating the cXML documents that it accepts and their respective URLs. Ariba Network then routes the purchase order to the appropriate supplier using the supplier’s preferred order routing method. and the different delivery dates for an extended period of time.4 and SAP ERP 6. 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.3 or 7. indicating that a transient error occurred. 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. Note that there is no corresponding OrderResponse document. ● 5xx. the ItemOut element includes a requiresServiceEntry=“yes” attribute. By default. 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. Ariba Network transmits a generic response. These scheduling agreement releases contain schedules lines with details on the line item. 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. Instead. the Ariba Network Adapter for SAP NetWeaver runs the Profile transaction as a scheduled task every 24 hours. Ariba Network Adapter for SAP NetWeaver Setup Guide 16 © 2015 SAP SE or an SAP affiliate company. The Ariba Network Adapter for SAP NetWeaver then re-sends the document with the same payload ID for the specified number of retry attempts. ● 4xx. This allows buyers to specify multiple schedule lines for a line item that needs to be supplied repeatedly over a period of time. This interval can be configured at runtime. SAP ERP provides line item numbering information that reflects both a service item's parent and outline numbers and the service item number. see Configuring Support for Line Level Hierarchies in Service Purchase Orders [page 321]. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. 17 . This allows you to specify multiple schedule lines for a line item that needs to be supplied repeatedly over a period of time. or edited schedule lines are highlighted in the change purchase order on Ariba Network. including price and quantity limits. the newly added. For more information. 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. Note Ariba Network does not support service lines in blanket purchase orders. To maintain the different delivery schedules for a line item correctly. see Schedule Lines in Purchase Orders and Change Purchase Orders [page 143]. For more information on the order confirmation integration scenario. For more information on configuring support for line level hierarchies in service purchase orders. Any changes or deletions made to a top-level service line or to the service items below a top level service line. see Order Confirmation Integration Scenario [page 93].When a purchase order item of type service contains line items with a hierarchy. For more information. 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]. see the Ariba Network Integration Guide. When a purchase order containing changes to the schedule lines is sent to a supplier. Each line item can have different quantities and multiple delivery dates and time in a purchase order. 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. The adapter transmits this information to Ariba Network for both purchases orders and change orders. each schedule line is numbered sequentially in the purchase order and sent to Ariba Network. All rights reserved. deleted. are transmitted to Ariba Network. ● The Unlimited Overfulfillment option must be selected to support the quantity changes to line items. Buyers can receive service sheets containing the following: ● Service sheets with or without hierarchy ● Service sheets containing unplanned service lines.1 and 7. For more information. To prevent failures while processing multiple service sheets. see Specifying Time-Out Intervals for Processing Service Sheets [page 327]. In some cases. the Price Change Allowed check box must be enabled at the line item level for lines that support changes to the unit price. Buyer administrators can change quantity and unit price in the service sheets. the Ariba Network Adapter for SAP NetWeaver does not processes the unit of measure correctly. For example. Ariba Network Adapter for SAP NetWeaver Setup Guide 18 © 2015 SAP SE or an SAP affiliate company. buyers must maintain PCE as the internal unit of measure in the CUNI transaction. the following is required in the purchase order with service type line items: ● In the Services tab. if the unit of measure used on the ERP system is PCE. All rights reserved. see the Ariba Network Integration Guide. Ariba Network Adapter for SAP NetWeaver does not validate the accounting information available in service sheets against the account information. buyers must also enable the rule Allow suppliers to change the unit price on service sheets on Ariba Network. To do this. Service sheet and service sheet response transactions are supported for SAP NetWeaver Versions 7. Tolerance option must be selected. 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]. In the Limits tab. For more information. ● The Overfulf. Suppliers must create service sheets containing only one parent line item from a purchase order with multiple service type line items.Service Sheet A service sheet is created against a purchase order containing service type line items. 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.3. ● 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 Unit of Measure field displays “***. enter the expected value in the the Overall Limits must be specified to allow suppliers to add unplanned line items. Service sheets against the purchase order with service type line items can have both planned and unplanned line items. the SAP ERP system fails while processing multiple service sheets for the same purchase order service type item.These service sheets can also contain attachments. However.” To avoid this. The accounting information available in the service sheets is used by the SAP ERP system. Note ● To support changes to unit price in service sheets. Ariba recommends that you specify a time-out duration. When a suppliers adds an ad-hoc line item containing the unit of measure(UOM). buyers must ensure that they set up the Unit of Measure configuration in the CUNI transaction on their SAP ERP system. Ariba Network Adapter for SAP NetWeaver .The service sheet must contain at least one-level service child line item in the hierarchical structure. When a buyer enables only the GR based IV indicator. 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 maximum allowed limit to create invoices is based on the shipped or received quantity. ● Buyers must use the service-based invoicing functionality on the SAP ERP system.EDI: Multiple reference to same purchase order item.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. ● Although the service purchase order contains multiple line items. Prerequisite [page 19] Limitations [page 19] Prerequisite To send and receive service sheets with hierarchy. However. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. 19 . See Invoice [page 20] for more information. All rights reserved. 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. 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. ● Services sheets cannot contain adhoc line items (unplanned line items). the adapter does not support the operations = “update” and “Delete”. 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. ● Apply the SAP Note 1090663 . The GR based IV and S based IV indicator on the Invoice tab of the purchase order containing service lines. 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. the quantity in the service sheet and invoices are not displayed in the Qty field as the quantity is aggregated. ● The Final Entry indicator option specified in service sheets on the SAP ERP system is not supported on Ariba Network. 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. suppliers must create service sheets with only one parent line item. This option is required to create separate line items for each service line in the invoice created on the SAP ERP system. All rights reserved. Note ● To post non-PO invoices and credit memos to SAP. you must implement a user exit.) To post non-PO invoices successfully. Ariba Network Adapter for SAP NetWeaver . ● (For users upgrading from version 1. you must delete and reload the IDoc metadata from the NetWeaver transaction IDX2 after the installation of the upgrade package. ● To post this information to the General Ledger (G/L) account directly. ● Header-level credit memos against non-POs created in the Ariba procurement solution. 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]. the discount amount is adjusted in the line amount. has been populated with data corresponding to the distribution (accounting information in cXML) data. 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. see the Ariba Network Integration Guide. the segment. Ariba Network Adapter for SAP NetWeaver Setup Guide 20 © 2015 SAP SE or an SAP affiliate company.● Ariba Network allows changes to unit of measure in service sheets. 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. see cXML Adapter Parameters [page 391]. Support for Non-PO Invoices and Credit Memos In addition to PO-based invoices. but SAP ERP does not support changes to the unit of measure in service sheets. For more information.4 of the Ariba Network Adapter for SAP NetWeaver to version 10s2 only. /ARBA/ACCOUNT_DATA. For more information on implementing the user exit. ● Shipping and handling charges added without any tax is sent in the Invoice Detail Summary only. 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. Service Invoice Buyers can create invoices against purchase order containing service type line items. a user exit must be implemented. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company.1 and 7. SAP ERP buyers using Ariba Network Adapter for SAP NetWeaver can receive and process invoices with up to five- levels hierarchy created against purchase orders containing service type line items from Ariba Network. non-PO line-level credit memos. For more information about implementing the user exit. see cXML Adapter Parameters [page 391]. The integration of service invoices between SAP ERP and Ariba Network is supported on SAP NetWeaver versions 7. 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. 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. PO based line-level credit memos. To post this information as mentioned above either to the G/L account directly or to unplanned delivery cost. Suppliers create service invoices based on approved service sheets. and header-level credit memos (either PO based or non- PO based) use the data in segments E1EDK04/E1EDP04 and query the OBCD transaction to determine the tax applicable.3. All rights reserved. These invoices can also contain attachments. /ARBA/ACCOUNT_DATA. has been populated with data corresponding to the shipping and handling charges service lines with taxes. Buyers can receive invoices containing the following: ● Invoices with or without hierarchy ● Invoices containing unplanned service lines. The segment. Shipping and handling charges is added and sent to SAP as unplanned delivery cost. Note The invoices must contain at least one-level service child line item in the hierarchical structure.Tax Handling for Different Types of Invoices Invoice supports the following tax handling scenarios: ● PO based invoices. 21 . ● Non-PO based invoices. 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. Summary Invoice The Ariba Network Adapter for SAP NetWeaver supports summary invoices for multiple purchase orders. see Direct Invoicing of Purchase Order Service Items [page 325] . When a buyer enables only the GR based IV indicator. buyer administrators must do the following: ● Buyers must use the service-based invoicing functionality on 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. 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. ● Apply the SAP Note 1090663 . 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. Prerequisite To receive invoices created against purchase order service lines. the quantity in the service sheet and invoices are not displayed in the Qty field as the quantity is aggregated.EDI: Multiple reference to same purchase order item. buyer administrators must use the service-based invoicing functionality on the SAP ERP system.-Based IV indicator on the Invoice tab of the purchase order Ariba Network Adapter for SAP NetWeaver Setup Guide 22 © 2015 SAP SE or an SAP affiliate company. The S. 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. Integrated suppliers can send summary invoices for multiple purchase order containing material items and non- material purchase orders having the standard item category. All rights reserved.Prerequisite To send and receive invoices with hierarchy. Note Ariba Network Adapter for SAP NetWeaver does not support summary invoices for service purchase orders. Ariba Network Adapter for SAP NetWeaver . 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. 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. Limitations Although the invoice for the service sheets contains taxes and other charges. contract. and unplanned delivery cost items ● Transmission of manually created non-PO invoices containing material. SAP ERP buyers can send ERP-initiated or CC invoices from the SAP ERP system to Ariba Network using the IDOC transmission method. This option is required to create separate line items for each service line in the invoice created on the SAP ERP system. Buyers can send SAP ERP MM and FI invoices using the IDOC. The Ariba Network Adapter for SAP NetWeaver also supports transmission of invoices that are created through self billing. internal order. Buyers can use the GSVERF03 IDOC to send MM invoices and the FIDCCP02 IDOC to send FI invoices. or on a weekly basis. These invoices created in SAP ERP are then uploaded to Ariba Network. The line-items can contain material. GL account. Customers can send SAP ERP MM and FI invoices using the IDOC. All rights reserved. 23 . 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. 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. advanced pricing details.containing service lines. WBS elements and cost center items ● Transmission of invoices created through the Invoice plan containing both periodic and partial items Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. 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. Uploads can be scheduled either on a daily basis. The Ariba Network Adapter for SAP NetWeaver also supports transmission of invoices that are created through self billing. Starting Ariba Cloud Integration Release 6. Backward Compatibility This feature is not compatible with the releases prior to Cloud Integration Release 6.0. Street. Customers can customize and add segments to include additional information for vendors.● 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)/ GSVERF03 /ARBA/GSVERF03 MIRO/ MM 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. 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.0. see ERP-Initiated Invoice Integration Scenario [page 167] and Configuring ERP- Initiated Invoices to Use the IDOC [page 331] . and City for the vendor. the ERP_INV_PROCESSED_STATUS parameter is no longer required for ERP-initiated invoices. 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. For more information. buyer administrators must do the following: ● Make the necessary configurations on their SAP ERP system and configure the integration scenario on their SAP PI. All rights reserved. Ariba Network Adapter for SAP NetWeaver . Ariba Network Adapter for SAP NetWeaver Setup Guide 24 © 2015 SAP SE or an SAP affiliate company. when an ERP-initiated invoice is sent to Ariba Network. Buyers must ensure that they make the necessary changes to remove the previous ABAP proxy programs to process the ERP-initiated invoices. you must ensure that you do not use the ERPINV_PROCESSES_CHK parameter. ● The SubTotal Amount field does not include the tax amount. supplier enablement is initiated even if no relationship is maintained in Ariba Network for SAP Vendor and AN Vendor. To enable quick enablement. As a result. you must specify the Transfer IDoc immediately option in the Output Mode section on the Generate Partner Profile page. ● Downloaded the relevant SAP transport requests from connect. Quick enablement is achieved by adding the Email ID to the relevant structures in SAP NetWeaver PI and the SAP ERP system. Enabling Quick Enablement for ERP-Initiated Invoices Quick enablement is supported for the ERP-initiated invoice transaction. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. Customers can use customer exits to include the tax amount in the Sub Total Amount field. If you are using the IDOC. 25 . Customers using Ariba Cloud Integration Release 5. To continue using the ABAP proxy program.0 and lower must continue to maintain the ERP_INV_PROCESSED_STATUS parameter for ERP-initiated invoices. ● Payment term values are not sent if the payment terms is "Immediate" with no tier discounts. All rights reserved. ● The Email name element is no longer sent in the Contact element. This parameter supports extracting all the ERP invoices that are stored in the /ARBA/AN_ERPINV table.com and imported them into your SAP ERP system.com/xi/ASN/ERPInvoiceProxy no longer exists.tpz file into your SAP NetWeaver PI system. ● Accounting information is no longer sent for FI and ERP-initiated invoices. 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 <ShippingAmount> element is only sent when the invoice contains unplanned delivery cost. you must ensure that you use the ERPINV_PROCESSES_CHK parameter.Design. ensure that you have: ● Imported the AribaNetworkAdapterSAPNetweaver. Note Email ID must be maintained in Vendor Master and the same email ID is passed to SAP NetWeaver PI.ariba.. The namespace http://ariba.To use the IDOCs. the sending company codes may vary in addition to the paying company code. When you include these charges while creating an ERP-initiated invoice. some companies have configured SAP to ensure that credit to a vendor account is performed using a separate paying company code. Although. Therefore. like the other SAP RFCs. you can specify these charges while creating the invoice. In this case. However. the tax amount is available at the header level only. ● 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. As a result. the shipping and freight charges amount is added to the gross amount of the ERP-initiated invoice. Limitations for PO-Based ERP-Initiated Invoice with Cross Company Codes ● In SAP. ● 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. Note The SAP RFC for ERP-initiated invoices.ERP-Initiated Invoice with Cross Company Codes You can create a PO-based or non PO-based ERP-initiated invoice with cross company codes. for performance reasons. ○ The quantity is displayed as 1 and unit price is displayed as being equal to the line amount. you can create purchase orders that relate to a single sending company only. then such charges are called unplanned shipping and freight charges. All rights reserved. Ariba Network Adapter for SAP NetWeaver . This is a limitation on the SAP side. the SAP FI accounting document for vendor posting does not include information about the purchase order. When you view such an invoice in Ariba Network. the reference to the PO ID may be useful. is intended to accelerate your IT department’s effort in building appropriate integration between SAP and Ariba system. In this case. Note The handling of shipping and freight charges is same for ERP-initiated invoices and ERP-initiated invoices with cross company codes. ● You can enter shipping and freight charges in the purchase order itself or while creating an ERP-initiated invoice. Ariba has not added the logic to the RFC to send the purchase order number in the invoice. Instead. SAP restricts purchase orders and the related PO invoices to a single sending company code. The planned and unplanned shipping charges are handled as follows: ● Planned shipping and freight charges are sent as a separate material line item. it is possible to book the liability to a different paying company code. Limitations for Non PO-Based ERP-Initiated Invoice with Cross Company Codes For non PO-based ERP-initiated invoices. if Ariba Network Adapter for SAP NetWeaver Setup Guide 26 © 2015 SAP SE or an SAP affiliate company. when you view such an invoice in Ariba Network: ○ The PO ID is not displayed as part of the invoice. If you have not specified these chargers during the creation of the purchase order. However. such unplanned shipping and freight charges are not displayed separately as a line item. com -> Ariba Network Adapters -> Ariba Network Adapter for SAP NetWeaver -> Under Integration Tools -> Data Transformation . For more information about invoice status updates. A receipt line is a ReceiptItem element with a receipt line details. 27 . Buyers send StatusUpdateRequest documents to set invoice status to processing. To do this. then such an invoice is extracted and displayed as a non PO-based invoice and as a result. However. invalid. open the ReadMe. ○ Quantity is displayed as 1. Buyers generate receipts and Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company.ariba. see Configuring Invoice Status Updates [page 301] and the Ariba cXML Solutions Guide. you must import the relevant SAP transport provided by Ariba into your SAP ERP system. Ariba Network posts the documents to the URL that suppliers return in their cXML ProfileResponse. you can provide the tax amount for each line item. Note The data mapping workbook for the ERP-initiated invoice transaction is available in connect. All rights reserved. parked or parked invoices that have been deleted. your business process requires you to include the PO ID in the invoice. you must download the SAP transports (available in a ZIP file) from Connect (http://connect. ● If you create an ERP-initiated invoice with multiple POs. StatusUpdateRequest documents can identify invoices in two possible ways: through either a DocumentReference or an InvoiceIDInfo element. when you view such an invoice in Ariba Network. you must work with your IT department to add the appropriate logic to the RFC. when you view such an invoice in Ariba Network: ○ The PO ID is not displayed as part of the invoice. the tax is displayed at the header level as the sum of all the line item tax amounts. ○ 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). ○ The invoice contains only one line item. ● When creating an ERP-initiated invoice in SAP.com). and check the transport number that is relevant and import it. 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. Invoice Status Update Invoice status updates are sent by buying organizations to inform Ariba Network and suppliers of the status of invoice reconciliation. Receipt Requests The cXML ReceiptRequest document defines the receipt information of a purchase order or master agreement with item details. rejected. paid. reconciled. paying.ariba.txt that is available in the ZIP file. but they can also be used for Dynamic Discounting. 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. that is. discount amounts. The Ariba Network Adapter for SAP NetWeaver initiates the cXML GetPending transaction to pull inbound business documents. If suppliers choose schedule payments for early settlement. For more information about Dynamic Discounting. It sends PaymentRemittanceAdviceRequest documents to suppliers as well as SAP to create an accounting document. The GetPending transaction allows the SAP ERP system to receive documents from Ariba Network through a data pull. However. see the Ariba cXML Solutions Guide. cXML Adapter Document Transmission The Ariba Network Adapter for SAP NetWeaver always uses HTTPS Post to send documents to Ariba Network. All rights reserved. and net amounts. When receipt data is successfully posted in Ariba Network. Ariba Network routes them to Ariba Invoice and Payment. Ariba Network sends the scheduled payments back to the buying organization through the Ariba Network Adapter for SAP NetWeaver. Scheduled Payments and Dynamic Discounting Buying organizations use scheduled payments. to tell Ariba Network and their suppliers about planned payments. These documents list scheduled payment dates. Updated PaymentProposalRequest documents are then used to update the payment schedule and discount amount in the buying organization’s SAP system. Buying organizations send proposed payment information to Ariba Network in PaymentProposalRequest documents containing a special Extrinsic element called immediatePay. For more information about scheduled payments. PaymentProposalRequest documents.address them to suppliers. Ariba Network Adapter for SAP NetWeaver Setup Guide 28 © 2015 SAP SE or an SAP affiliate company. 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. Buyers can see the receipts in their online Outbox. Scheduled payments are used for information by default. Dynamic Discounting allows buying organizations to pay suppliers early in exchange for discounts. Ariba Network Adapter for SAP NetWeaver . see the Ariba Network Buyer’s Guide. 4. see Downloading the Ariba Network Integration Guide from Connect [page 389]. For more information. Ariba Network responds with a GetPendingResponse document that includes zero or more DataAvailableMessage elements containing the internal ID of any waiting documents. Testing the configuration. 6. 2. For more information. see About Deploying the cXML Adapter [page 34]. For details on downloading this guide. Configuring transaction processes. see Installation Requirements [page 13]. All rights reserved.The GetPending transaction is scheduled using the getPendingInterval parameter defined for each inbound transaction. For more information. 5. Configuring the SAP ERP system. see Configuring Your SAP ERP System [page 13]. For more information. 29 . Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. 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. For more information about document transmission methods. see Testing the Adapter [page 13]. For more information. Configuring the System Landscape Directory. see About Configuring the System Landscape Directory [page 61]. Setting up and configuring the cXML Adapter. see About Configuring Transaction Processes [page 65]. Verifying that all the software and connectivity requirements are in place. see the Ariba Network Integration Guide. 3. For more information. Ariba Network Adapter for SAP NetWeaver Setup Guide 30 © 2015 SAP SE or an SAP affiliate company.4 Supported SAP ERP Versions The Ariba Network Adapter for SAP NetWeaver supports SAP ERP versions starting with SAP ERP 6.com > SAP NetWeaver > SAP NetWeaver PI 7. The information in this topic is applicable to the Ariba Network Adapter for SAP NetWeaver.3 SAP Netweaver PI 7. see Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On [page 30]. see the following SAP NetWeaver section on the SAP Service Marketplace: service.0 EHP 7. Configuring the Ariba Network Adapter for SAP NetWeaver .X > Availability.sap.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. 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. For information about the platforms that the SAP NetWeaver suite supports. For information on the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On.3 Cloud Integration 2 or higher SAP Netweaver PI 7.0 up to SAP ERP 6. All rights reserved.1 SAP Netweaver PI 7. Import the relevant SAP transport requests into your SAP ERP system. ● The Ariba Network’s Certificate Authorities certificates are stored in the SAP NetWeaver PI Keystore.com) and click the Download Software tab. Installing the Network Adapter Files Context To install the Ariba Network Adapter for SAP NetWeaver. Ariba Connect. 3. configured Ariba Network Buyer account. The cXML Adapter uses the certificates stored in the SAP NetWeaver PI Keystore to connect to Ariba Network. see the Ariba Network Integration Guide.ariba. see the Ariba cXML Solutions Guide.Design. Navigate to or search for the relevant file and click the download icon to download the archive file. For more information about how to enable secure communications through a proxy server. a secure protocol that encrypts communication before transmission.Ariba Network Requirements Ensure that you have the following Ariba Network requirements before installing the Ariba Network Adapter for SAP NetWeaver: ● A valid. 5. Click I Accept to accept the Ariba Software Access Agreement. For more information about configuring your Ariba Network Buyer account. 6. For more information about obtaining a digital certificate. For more information. All rights reserved. see the Ariba Network Integration Guide. see the Ariba Network Buyer Administration Guide.tpz file into your SAP NetWeaver PI system. 4. Select as the Product Line and the relevant Product Version. For more information about creating a supplier relationship. 2. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. see cXML Adapter Parameters [page 391]. 31 . then a valid Secure Socket Layer (SSL) client certificate from one of Ariba Networks trusted Certificate Authorities is required. ● 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). you need the relevant archive file which is available on Ariba’s support interface. Procedure 1. ● If the Ariba Network Buyer account is configured to use digital certificate authentication. Import the AribaNetworkAdapterSAPNetweaver. ● An Ariba Network supplier relationship. For more detailed information about internet connectivity requirements. see About Configuring Security Certificates [page 32]. Login to Ariba Connect (http://connect. including an ANID-to-Private ID mapping. xml SAP configuration transport files The required SAP transport files. then you need to import the certificates of the domains on which attachments are hosted into your Java JRE keystore.properties file for the purchase order transaction.tpz files cXML Adapter files AribaNetworkAdapterSAPNetWeaver. 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. About Configuring Security Certificates Install security certificates in a Java JRE keystore or truststore.xml Software catalog files CacheCatalog. Enter the following command from the command line: Ariba Network Adapter for SAP NetWeaver Setup Guide 32 © 2015 SAP SE or an SAP affiliate company. On the system hosting the Ariba Network Adapter for SAP NetWeaver. Configuring the Ariba Network Adapter for SAP NetWeaver .zip Mapping design and Integration configuration AribaNetworkAdapterSAPNetweaver. All rights reserved.Design.Config.xml CanonicalCatalog. determine the path for your Java home directory.sca Metadata definition files AribaNetworkAdapterSAPNetweaver. Procedure 1.SoftwareCatalog.Results The archive ZIP files contain the following components: Product definition files AribaNetworkAdapterSAPNetweaver. 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.properties file for the purchase order transaction. you want to use to refer to this certificate. 5. Importing Security Certificates into the Java JRE TrustStore Context If you configured the trustKeyStore parameter in the ChannelsConfig. All rights reserved. domain_certificate_file is the name of the domain certificate file. enter: keytool -import -trustcacerts -alias alias -file domain_certificate_file -keystore trustStore_path Where: alias is a name. domain_certificate_file is the name of the domain certificate file. 6. trustStore_path the trustStore path configured for the purchase order communication channel.echo $JAVA_HOME 2. On the command line. or alias.cer. you want to use to refer to this certificate. Import each certificate. If the output does not list any certificates. 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. 2. such as sys456. 33 . Set your working directory to your JAVA_HOME/bin directory.cer. Repeat the above step for additional certificates that you need to import into the truststore file. then you need to import the certificates of the domains on which attachments are hosted into your trustKeyStore file. Copy the required domain certificates to your JAVA_HOME/bin directory. Enter the password. The keytool utility prompts for you for the keystore password. 7. such as sys123. 3. then this is probably not the correct keystore. Procedure 1. 4. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. Repeat steps 5 and 6 for additional certificates that you need to import into the keystore. Backup certificates are useful when your primary certificate expires or when you need to perform certificate maintenance. Ariba Network displays the Configuration page 4. 2. All rights reserved. 3. About Deploying the cXML Adapter The Ariba Network Adapter for SAP NetWeaver relies upon the cXML Adapter. You can also use a backup digital certificate. Log in to your Ariba Network account. Click Save. You can also use a backup digital certificate. Ariba Network uses the backup certificate if your primary certificate becomes invalid. you must configure your Ariba Network buyer account to store the client certificate. 8. Note Digital certificates expire after a predetermined period of time. Ariba Network Adapter for SAP NetWeaver Setup Guide 34 © 2015 SAP SE or an SAP affiliate company. The certificate must be issued from a Certificate Authority (CA) trusted by Ariba. choose the Certificate authentication method from the Select an authentication method pull-down menu. Copy the certificate. Paste the signed client certificate into the Certificate text box. Click cXML Setup. contact your Ariba Support Representative. The Configuration page opens. Procedure 1. starting with "-----BEGIN CERTIFICATE-----" and ending with "-----END CERTIFICATE-----". which conforms to the JCA specification and implements the cXML transport protocol.Installing Client Certificates on Ariba Network Context After you have imported the security certificates. It is your responsibility to periodically obtain updated certificates from your certificate authority and install them on Ariba Network. ClickManage Profile in the upper left corner of the home dashboard. 5. For a list of CAs trusted by Ariba or to add a CA to Ariba’s trusted CAs. In the Authentication Method section. Configuring the Ariba Network Adapter for SAP NetWeaver . 9. 6. Click OK. Backup certificates are useful when your primary certificate expires or when you need to perform certificate maintenance. Obtain a signed digital certificate issued for the client. Ariba Network uses the backup certificate if your primary certificate becomes invalid. 7. You must have the account administrator privileges to make this change. Start JSPM. From SAP netweaver version PI7. For more information on how to install or upgrade using the SUM tool. 35 . use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI. Procedure 1. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. 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.3 EHP1.3 EHP1 onwards you must use the SAP Software Update Manager (SUM) tool to deploy the adapter.SCA file in the required location.If your version of SAP netweaver PI is prior to PI 7. All rights reserved. you have placed the . contact your SAP systems administrator. Select Business Packages (advanced user only) and click Next. The Queue status appears. Enter your user name and password and click Log On. Select the business package you want to deploy and click Next.2. Configuring the Ariba Network Adapter for SAP NetWeaver . All rights reserved. Ariba Network Adapter for SAP NetWeaver Setup Guide 36 © 2015 SAP SE or an SAP affiliate company. 4. 3. 5. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. The Completed screen appears. The Deploy Queue screen appears. 37 . All rights reserved. Click Start. see Undeploying the cXML Adapter using the Textconsole [page 43]. All rights reserved. Start JSPM.6. For information on how to undeploy the adapter. Results The cXML Adapter is successfully deployed. You cannot undeploy the adapter using the JSPM. Ariba Network Adapter for SAP NetWeaver Setup Guide 38 © 2015 SAP SE or an SAP affiliate company. You must start the cXML Adapter from the SAP NetWeaver Administrator console. Configuring the Ariba Network Adapter for SAP NetWeaver . Click Exit. Upgrading the cXML Adapter Using JSPM Procedure 1. Enter your user name and password and click Log On.2. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. All rights reserved. 3. 39 . Select Single Support Packages and Patches (advanced user only) and click Next. 4. The Queue status appears. All rights reserved. Ariba Network Adapter for SAP NetWeaver Setup Guide 40 © 2015 SAP SE or an SAP affiliate company. Select the support package you want to apply and click Next. Configuring the Ariba Network Adapter for SAP NetWeaver . The Deploy Queue screen appears. All rights reserved. The Completed screen appears.5. 41 . Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. Click Start. xml ● CanonicalCatalog.6. copy the files to the following folder:Install_Root/etc/catalog/. 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. Ariba Network Adapter for SAP NetWeaver Setup Guide 42 © 2015 SAP SE or an SAP affiliate company. Click Exit. All rights reserved.xml Procedure To install these files. Configuring the Ariba Network Adapter for SAP NetWeaver . Results The cXML Adapter is upgraded successfully. 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 <Location of .SCA File>name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_deploy_error=stop Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. All rights reserved. 43 For example: deploy /usr/sap/LP3/DVEBMGS00/j2ee/deployment/scripts/ AribaNetworkAdapterSAPNetweaver.sca name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_deploy_error=stop Note To upgrade to the latest version of the Ariba Network Adapter for SAP NetWeaver, you must first undeploy the existing adapter and then deploy the latest version that you have downloaded from https://connect.ariba.com . Setting Log Configuration Parameters for the cXML Adapter Context Set log configuration parameters so that the cXML Adapter sends log entries to a separate file. Procedure 1. Login to the SAP NetWeaver PI log administration section at http://XI_server_hostname/XI_port/nwa/logs. 2. Click the Log Configuration link. 3. Select Tracing Locations from the Show drop down list. 4. Select the node (package) com ariba asc , to set the logging level to log the complete adapter processing information, or select CXMLSender under connector.cxml.util to set the logging level to log only the exchanged messages. 5. Change the severity level from Error to Info / Debug in the Severity drop-down list, and then click Save Configuration in the toolbar. Note The log level can remain Error when running in a production environment, but Ariba recommends that you change the log level to Info. You can also find out about the version of the Ariba Network Adapter for SAP NetWeaver. Ariba Network Adapter for SAP NetWeaver Setup Guide 44 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Configuring the Ariba Network Adapter for SAP NetWeaver About Configuring the cXML Adapter To allow the cXML adapter to run correctly, you must configure parameters for the Communication Channels for different business scenarios. This configuration is done at a later stage, during the configuration of Integration Scenarios in the Integration Directory. For more details about how to create the Communication Channels, see the Communication Channels Configuration procedure for each scenario in the Configuring Integration Scenarios [page 30] section. For a description of the parameters and instructions for how to configure retry attempts, see cXML Adapter Parameters [page 391]. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. All rights reserved. 45 Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver About Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver [page 46] cXML Interfaces Supported in the Ariba Cloud Integration Releases [page 47] Features Available in the Ariba Cloud Integration Releases [page 48] Steps to Install the Ariba Network Adapter for SAP NetWeaver PI [page 51] Installing the SAP ERP Transports [page 51] Upgrading to a Higher Version of the Ariba Network Adapter for SAP NetWeaver Transports [page 52] About Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver To integrate the SAP NetWeaver PI with Ariba Network, Ariba recommends that you install a new version or upgrade to a higher version of Ariba Network Adapter for SAP NetWeaver. Starting Ariba Cloud Integration 6.0, all the transport files for Ariba Network Adapter for SAP NetWeaver have been merged to a single transport file for easier installation. Customers who are using versions prior to Ariba Cloud Integration 6.0 continue to install the different transport files available in the transport zip file. If you are a new customer, you must install the latest version of the transport files for Ariba Network Adapter for SAP NetWeaver. If you are existing customer, Ariba recommends that you upgrade to a higher version of the Ariba Cloud Integration. When you upgrade from an existing version of Ariba Cloud Integration to the latest version, ensure that you perform certain procedures to retain your existing settings or customization that you have on your current version of the Ariba Cloud Integration. Prerequisites Ensure that you have all the necessary software and connectivity requirements before you install the Ariba Network Adapter for SAP NetWeaver. Related Information Installation Requirements [page 30] Steps to Install the Ariba Network Adapter for SAP NetWeaver PI [page 51] Ariba Network Adapter for SAP NetWeaver Setup Guide 46 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver Upgrading to a Higher Version of the Ariba Network Adapter for SAP NetWeaver Transports [page 52] cXML Interfaces Supported in the Ariba Cloud Integration Releases The following table shows a comparison of the supported cXML interfaces between Ariba Cloud Integration version 1.0 and version 6.0: Ariba Cloud Integration Release Version 1.0 Ariba Cloud Integration Release Version 6.0 Requisition Requisition Purchase Order Purchase Order (Includes Change and Cancel Purchase Orders) Change and Cancel Purchase Order Order Confirmation Order Confirmation Ship Notice Ship Notice Invoice Invoice ERP-Initiated Invoice ERP-Initiated Invoice Invoice Status Update Invoice Status Update Receipt Receipt Payment Proposal Payment Proposal Payment Remittance Payment Remittance Pay Me Now Pay Me Now Request for Quotation Service Sheet Order Inquiry Scheduling Agreement Catalog Related Information Supported cXML Interfaces [page 15] Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. All rights reserved. 47 Features Available in the Ariba Cloud Integration Releases The following are the new features and changes introduced in the different Ariba Cloud Integration releases: Ariba Cloud Ariba Cloud Ariba Cloud Ariba Cloud Ariba Cloud Ariba Cloud Integration 6.0 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 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. 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_<object name> to /ARBA/ <object name>. The SAP NetWeaver PI content was changed by importing the RFCs and the ABAP objects were renamed with the /ARBA/ namespace into SAP NetWeaver PI. The namespace of SAP NetWeaver PI Support for Support for Support for Ariba Support Invoice invoice in the 7.4 Support for Blanket Purchase corrections and Sourcing Award Status Updates for AribaNetworkA Ariba Network Orders returns in Receipts Integration parked and deleted dapterforSAPN invoices etWeaver.desi gn.tpz was changed from http:// ariba.com/xi/ ASN/ZInvoice Ariba Network Adapter for SAP NetWeaver Setup Guide 48 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver Ariba Cloud Ariba Cloud Ariba Cloud Ariba Cloud Ariba Cloud Ariba Cloud Integration 6.0 Integration 1.0 Integration 2.0 Integration 3.0 Integration 4.0 Integration 5.0 to http:// ariba.com/xi/ ASN/Invoice. ZINVOICE02 and ZACCOUNT_DATA were renamed to / ARBA/INVOICE and /ARBA/ ACCOUNT _DATA respectively. The cXML adapter Mapping Support Support line-level Support line-level requires the JSPM enhancements to integration for hierarchies in hierarchies in (Java Support support Supply Outline Service Purchase Service Sheets and Package Manager). Chain Agreements in SAP Orders Invoices Management Support for Order Support for Enhanced request Support for change Support IDOCs for Confirmation and creation of a single messages added and cancel order CC (ERP-Inititated) rejection of the ship notice against to the cXML transactions have Invoices entire purchase multiple purchase adapter: been removed. order. orders StatusUpdateRequ Change order est transactions are processed as part Note of the purchase order IDOC. The previous Invoice Status Update Request no longer exists. Buyers can now use the StatusUpdateR equest for both invoices and service entry sheets. Ariba no longer Support for Invoice Status Support all Support line uses the ccBPM schedules lines in Update use releases of SAP numbering in engine. purchase orders Business ERP 6.0 up to SAP schedule lines Transaction Events ERP 6.0 EhP7 The following (BTE) to process transactions are invoices created, Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. All rights reserved. 49 Ariba Cloud Ariba Cloud Ariba Cloud Ariba Cloud Ariba Cloud Ariba Cloud Integration 6.0 Integration 1.0 Integration 2.0 Integration 3.0 Integration 4.0 Integration 5.0 supported using changed, reversed, the ABAP proxies: canceled, or when payments are ● ERP-Initiated received. Invoice ● Invoice Status Update ● Payment Proposal ● Receipt Payment Support for SAP Support for Integration of Remittance Advice ERP Integration purchase order catalog data in transaction is no with Ariba Spot confirmation SAP ERP and Ariba longer supported Quote solution options at the Network by the Ariba header and line- Network Adapter item levels for SAP NetWeaver. ZARIBA_INV_AT Support for large Support summary TACHDOC BADI file attachments in invoices ZARIBA_INV_AT invoices and referencing TACHDOC BADI service sheets multiple purchase support for PDF orders and direct copy of invoices. invoicing of purchase order service items Processing of attachments in the outbound transactional documents in the PI mapping layer before sending them to Ariba Network Ariba Network Adapter for SAP NetWeaver Setup Guide 50 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver Place these files in the appropriate locations on your SAP instance. see Configuring Integration Scenarios [page 80] . For more information.zip\SAPConfig\Trans. see Installation Requirements [page 30]. Installing the SAP ERP Transports Context You must install SAP ERP transports to integrate an Ariba Network application with SAP. For more information. see Configuring Your SAP ERP System [page 269]. 9. 2. see About Configuring Transaction Processes [page 65]. Configure the Integration Scenarios in the Integration Directory. 3. For more information. 4. Import the Design Package. For more information. 8. see About Configuring the System Landscape Directory [page 61]. Test the configuration. For more information. 6. Configure the System Landscape Directory. 7. Download the latest installation package. The latest SAP ERP transports are available in AribaNetworkAdapterSAPNetweaver_vCIX. see the Installation Requirements [page 30] section. Procedure 1. For more information. Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. All rights reserved. see Importing the Design Package [page 66]. see Testing the Adapter [page 384] . Ensure that you meet all the software and connectivity requirements. see Installing the Network Adapter Files [page 31]. Configure an Ariba Network account. For more information. Install and configure the cXML Adapter and Log mechanism. For more information. Configure the SAP ERP system. Configure the transaction processes. For more information. 5. see About Deploying the cXML Adapter [page 34] and About Configuring the cXML Adapter [page 45]. 10. 51 . For more information.Steps to Install the Ariba Network Adapter for SAP NetWeaver PI Context Ensure that you perform the following steps to install the latest SAP NetWeaver adapter on your SAP NetWeaver PI system. All rights reserved.0. ○ Double click the system identifier <SID> for which you want to add the parameter.Procedure 1. Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver . Set the value for the parameter to OFF. turn OFF the SP_TRANS_SYNC parameter: ○ Start Transaction STMS. ensure that you make the necessary changes on your SAP NetWeaver PI and SAP ERP system. ○ Add SP_TRANS_SYNC to the parameter column. Upgrading to a Higher Version of the Ariba Network Adapter for SAP NetWeaver Transports When you upgrade to a higher version of the SAP transports. click Change Mode. ○ Go to the Systems Overview. ○ On the Transport Tool tab. Run the STMS transaction to install the transport files. Ariba Network Adapter for SAP NetWeaver Setup Guide 52 © 2015 SAP SE or an SAP affiliate company. Changes Required on your SAP ERP Systems [page 52] Changes Required on your SAP NetWeaver PI System [page 54] Migrating the Design Objects [page 55] Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration [page 55] Updating the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration [page 56] Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration [page 57] Changes Required on your SAP ERP Systems Context The following changes are applicable when you upgrade from the Ariba Cloud Integration 1. ○ Save and activate the parameter. If the “Does not match component version” error occurs while importing the transport files that have a different software component that is not available in the target system. 3. 2.0 to Ariba Cloud Integration 6. Specify the target client as the SAP instance client. For more information.0 no longer uses the proxy for ERP-Initiated Invoices. 5. Import the Ariba Cloud Integration 6.0 does not contain a separate IDOC and namespace for the Change Purchase Order transaction.0. ○ Service Sheet . If you want to use the new transactions.0: ○ /ARBA/CHANGE_PO Ariba Cloud Integration 5. For more information. and enhancements. see Configuring Quote Request and Quote Message Documents [page 318]. 53 . For more information. see Integration of Catalog Data in SAP ERP and Ariba Network [page 250].0: ○ Order inquiry – For more information. The ERP-Initiated Invoices now use the standard IDOC. see Configuring Scheduling Agreement Releases [page 309]. you must use the standard BAdI. For more information. see Configuring Implicit Enhancements for Change and Cancel Orders [page 91] .For more information. and cancel purchase orders are now processed in the purchase order transaction. ○ Configure Implicit Enhancements for new purchase orders. new purchase orders. change purchase order. ○ Catalog (Catalog Upload Request) . All rights reserved. ○ /ARBA/ISU_UPDATE Starting Ariba Cloud Integration 5. the method READ_RECEIPT_DATA is no longer used. If you have existing change purchase order customizations. configure the necessary settings for the following transactions available in the Ariba Cloud Integration 6.For more information. To enhance the ERP-Initiated invoice transaction. see Change Purchase Order Integration Scenario [page 89]. The BAdI is not automatically migrated when you upgrade to Ariba Cloud Integration 6. For more information. the Invoice Status Update BAdI definition has been changed to / ARBA/BTE_ISU_UPDATE. For more information see. ○ /ARBA/INVOICE_UPDATE Ariba Cloud Integration 6. see Reconfiguring the SAP Partner Profile [page 90].0. 3. With Ariba Cloud Integration 5. 4. This is applicable only if you are using the BAdI for Ariba Cloud Integration 5. Ensure that you migrate the changes for the following BAdI manually. see the ERP- Initiated Invoice Integration Scenario [page 167] and Configuring ERP-Initiated Invoices to Use the IDOC [page 331]. see Configuring Order Inquiries [page 304]. Ensure that you make the following changes after you upgrade to the new version of the Ariba Cloud Integration: ○ Configure the Purchase Order transaction ○ Reconfigure the SAP Partner Profile to process change and cancel orders as variations on a standard purchase order.0 and higher. ○ Request for Quotation (Quote Request and Quote Message) . Invoice Status Update Integration Scenario [page 160] and Configuring Invoice Status Updates [page 301]. ○ /ARBA/RECEIPT_UPDATE In Ariba Cloud Integration 4.0 and earlier.0. change purchase orders and cancel purchase orders were handled differently from new purchase orders by the Ariba Network Adapter for SAP NetWeaver.0 transports. In Ariba Cloud Integration 4.Procedure 1. customer exits. see Configuring Service Sheets [page 326]. ensure that you manually move them to the purchase order transaction. The following BAdIs are no longer available in Ariba Cloud Integration 6.For more information. Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company.0 and earlier. 2. ○ Scheduling Agreement . If you are using an earlier version of Ariba Cloud Integration. For more information.3 EHP1 and higher. For more information. ○ Configure the SAP IDOC for ship notices (DELVRY06). see Configuring the SAP IDOC for Ship Notices Against Multiple Purchase Orders [page 313]. For more information. For more information.3 EHP1. ○ Configure the SAP IDOC for ERP-Initiated Invoice transaction. You must upgrade your JCA Adapter. you must migrate these design mapping objects. 2. Ensure that you configure the integration scenarios for them. For more information. All rights reserved. see Configuring ERP- Initiated Invoices to Use the IDOC [page 331]. use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI. Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver . ○ Configure the NACE transaction to publish receipts in real-time. you must use the SAP Software Update Manager (SUM) tool to deploy the adapter.0 has new design mapping objects. ensure that you import the new design mapping objects. see Configuring Invoice Status Updates [page 301]. 3. If you are using the SAP Netweaver version PI7. Note Ensure that you manually make changes to your custom mappings that contain conflict. see section. If you have customizations done to the existing design mapping objects. contact your SAP system administrator. see the section. For information on how to deploy the JSPM tool. Ariba Cloud Integration 6. ○ Configure the Business Transaction Events (BTE) for the invoice status update transaction. see Maintaining Condition Records for Returns and Corrections in Receipts [page 317]. Procedure 1. Migrating the Design Objects [page 55]. Deploying the cXML Adapter Using JSPM [page 35]. Related Information Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration [page 55] Ariba Network Adapter for SAP NetWeaver Setup Guide 54 © 2015 SAP SE or an SAP affiliate company. Changes Required on your SAP NetWeaver PI System Context Ensure that you make the following changes after you upgrade to the latest version of the desgin mapping objects on your SAP NetWeaver PI system. If your version of SAP Netweaver PI is lower than SAP PI 7. For more information on how to install or upgrade using the SUM tool. ○ Choose this option if you are upgrading from the Ariba Cloud Integration version 1.0 to 6. see Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration [page 55]. 9. Click Continue. The Transfer Design Object wizard appears. The Select Source and Target page appears.0.com/xi/ASN/ERPInvoiceProxy ○ http://ariba. Select the Active Version for Ariba Cloud Integration 6. Click Continue. Select All Objects of Individual Namespaces in the Object Set field. Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration When you upgrade from a lower version to a higher version of the Ariba Cloud Integration.com/xi/ASN/AdvanceShipNotice 10. Select the target of the new Ariba Cloud Integration version in the Target field. Ensure that you do not select the following namespaces while upgrading to a higher version of Ariba Cloud Integration: ○ http://ariba.0. Select the source of your existing Ariba Cloud Integration version in the Source field.com/xi/ASN/ChangedPurchaseOrder ○ http://ariba. This occurs due to changes that have been implemented in the newer version of the Ariba Cloud Integration. 4. 8. 2.Migrating the Design Objects Context After you have upgraded to the Ariba Cloud Integration 6. ensure that you migrate the design objects on your SAP NetWeaver PI system. After you have completed transferring the design objects. Procedure 1. conflicts arise after transferring the design objects. 3. click Transfer Design Objects. 7. Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. 5. All rights reserved.com/xi/Requisition ○ http://ariba. For more information. Go to the Enterprise Services Builder. 6. Choosing this option prevents you from errors that occur due to the mismatch of the namespace changes when you upgrade to a higher version of Ariba Cloud Integration. The Select Objects page appears. Ensure that you manually make changes to your custom mappings that contain conflicts.0. 55 . On the Tools menu. You can resolve the conflicts for the design objects by accepting the latest version (Active Version) of the Ariba Cloud Integration. ensure that you resolve the conflicts. 0. Edit the integration scenario for the remaining transactions that have been migrated to Ariba Cloud Integration 6. ERPInvoiceProxy (ERP-Initiated invoices) In Ariba Cloud Integration 6.0.0: ○ Requisition ○ ERPInvoiceProxy ○ Ship Notice (ASN) 3. Ship Notice The IDoc Basic Type has been changed in Ariba Cloud Integration 4.0 : Integration Scenario These needs to be deleted because… Requisition The namespace for this integration scenario has been changed in Ariba Cloud Integration 5. choose the software component version for Ariba Cloud Integration 6. Ariba Network Adapter for SAP NetWeaver Setup Guide 56 © 2015 SAP SE or an SAP affiliate company. All rights reserved.0. see Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration [page 57]. see Configuring Integration Scenarios [page 80].0. Delete the following integration scenarios in Ariba Cloud Integration 1. Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver . ERP-Initiated Invoices use the standard IDOC instead of the proxy message. Procedure 1.0. For more information.0. Configure the integration scenarios for all the new transactions available in Ariba Cloud Integration 6. ensure that you update the integration scenarios for the new and existing transactions. 2.Related Information Migrating the Design Objects [page 55] Updating the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration Context After upgrading to a higher version of the Ariba Cloud Integration. 4.0. For more information. For each of the migrated transactions. Change purchase orders are processed as part of the purchase order integration.0 and 6. Change Purchase Order The Change Purchase Order transaction is no longer available in Ariba Cloud Integration 5. Run the following integration scenarios again with the Software Component Version for the Ariba Cloud Integration 6. 2. Click the Edit button. Procedure 1. Configuring the Communication Channel [page 57] Configuring the Receiver Determination [page 58] Configuring the Interface Determination [page 59] Configuring the Sender Agreement [page 59] Configuring the Receiver Agreement [page 60] Configuring the Communication Channel Context You must edit the integration scenario for each of the migrated transactions. 7. 11. Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. you must edit the integration scenario for each of the migrated transactions.0 in the Adapter Type field. 6. specify the System Type as “Buyer. click the Display Input Help button in the Adapter Type field. Click Apply. 13. 12.” 14. Go to the ES Repository Model tab and click the Display Input Help button. Double-click the cXML communication channel to open it. Go to the Configuration: Integration Builder to edit the communication channel for the Software Component Version. Select the corresponding request type in the Inbound Request Type or Outbound Request Type field. The Select Process Integration Scenario from Enterprise Service Repository page appears. In the Parameters tab. 57 . 4. 10. Select the process integration scenario for the software component version for Ariba Cloud Integration 6. Click the Edit button. In the Parameters tab. On the main Configuration: Integration Builder page. Click Apply.0. 3.Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration After you have upgraded to a higher version of the Ariba Cloud Integration. 9. All rights reserved. Ensure that you have the necessary options enabled for the Object Properties on the Software Component Version page that allows you to edit the communication channel. The Display Configuration Scenario page appears. The Choose Adapter Metadata page appears. click the Objects tab. Choose the adapter metadata for Ariba Cloud Integration 6. 5. Select the configuration scenario and open it. 8. On the main Configuration: Integration Builder page.dtd for ReceiptRequest and OrderStatusRequest ○ Specify Quote. Go to the ES Repository Model tab and click the Display Input Help button. Enter a value in the Credentials Field. PaymentRemittanceStatusUpdateRequest. Select the configuration scenario and open it. Click the Edit button.0. choose one of the following DTDs in the cXML Configuration section: ○ Default value: cXML. The Display Configuration Scenario page appears. or PaymentRemittanceRequest. The Select Process Integration Scenario from Enterprise Service Repository page appears. you must edit the Receiver Determination for each of the migrated transactions. 9. click the Objects tab. 11. Select the process integration scenario for the software component version for Ariba Cloud Integration 6. Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver . Choose the software component version for the Ariba Cloud Integration 6. Ariba Network Adapter for SAP NetWeaver Setup Guide 58 © 2015 SAP SE or an SAP affiliate company. 4. 6. Save and activate the changes for the communication channel. ○ When you select the Outbound Request Type. Click Apply. Procedure 1.dtd ○ Specify PaymentRemittance. 16. ○ Specify Fulfill. Configuring the Receiver Determination Context After you upgrade to the Ariba Cloud Integration 6.dtd for PaymentProposalRequest.dtd for QuoteRequest ○ Specify InvoiceDetail.0. Click the Edit button. Double-click to select the Receiver Determination for the integration scenario.dtd for CopyRequest and Invoice InvoiceDetailRequest 15. 8. Save and activate the changes.0. 2. 10. Go to the Configuration: Integration Builder to edit the Receiver Determination for the Software Component Version. 7. All rights reserved. 3. 5. Procedure 1.0. 10. On the main Configuration: Integration Builder page. 2. Select the operation mapping of software component version for Ariba Cloud Integration 6. you must edit the Interface Determination for each of the migrated transactions. Go to the Configuration: Integration Builder to edit the Interface Determination for the Software Component Version. Click the Edit button. 4. 7. Go to the Configuration: Integration Builder to edit the Sender Agreement for the Software Component Version. Procedure 1. Select the configuration scenario and open it. 3. All rights reserved. The Display Configuration Scenario page appears. Click the Edit button.0. 9.0. you must edit the Sender Agreement for each of the migrated transactions. 5. Go to the ES Repository Model tab and click the Display Input Help button. Double-click to select the Interface Determination for the integration scenario. 13. 6. Save and activate the changes. Configuring the Sender Agreement Context After you upgrade to the Ariba Cloud Integration 6. 12. 8. Click Apply. The Display Configuration Scenario page appears. 59 .Configuring the Interface Determination Context After you upgrade to the Ariba Cloud Integration 6. Click the Display Input Help button in the Operation Mapping column. Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver © 2015 SAP SE or an SAP affiliate company. Select the process integration scenario for the software component version for Ariba Cloud Integration 6. click the Objects tab. Select the configuration scenario and open it. The Select Process Integration Scenario from Enterprise Service Repository page appears. Choose the software component version of the Sender Interface for the Ariba Cloud Integration 6. 2.0.0. 11. 0. Click the Edit button. 5. 6. Save and activate the changes. Click Apply.3.0. 8. 11. Save and activate the changes. 8. Click the Edit button. Ariba Network Adapter for SAP NetWeaver Setup Guide 60 © 2015 SAP SE or an SAP affiliate company. Click the Edit button. 4. On the main Configuration: Integration Builder page. Double-click to select the Receiver Determination for the integration scenario. 3. 10.0. The Display Configuration Scenario page appears. Go to the ES Repository Model tab and click the Display Input Help button. 9. Choose the software component version for the Ariba Cloud Integration 6. The Select Process Integration Scenario from Enterprise Service Repository page appears.0.0. Configuring the Receiver Agreement Context After you upgrade to the Ariba Cloud Integration 6. Click Apply. Double-click to select the Receiver Determination for the integration scenario. 4. you must edit the Receiver Agreement for each of the migrated transactions. Go to the ES Repository Model tab and click the Display Input Help button. 10. 7. Procedure 1. 11. Select the process integration scenario for the software component version for Ariba Cloud Integration 6. Click the Edit button. The Select Process Integration Scenario from Enterprise Service Repository page appears. 7. click the Objects tab. 5. 6. Select the process integration scenario for the software component version for Ariba Cloud Integration 6. 9. click the Objects tab. Go to the Configuration: Integration Builder to edit the Receiver Agreement for the Software Component Version. Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver . 2. On the main Configuration: Integration Builder page. All rights reserved. Choose the software component version for the Ariba Cloud Integration 6. Select the configuration scenario and open it. instances. For information on the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On. see Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On [page 61].Configuring SLD and Transaction Processes About Configuring the System Landscape Directory [page 61] Importing Ariba Network Product and Component Definitions [page 62] Defining Technical and Business System for Ariba Network [page 63] Defining the Business System for Ariba Network [page 63] Defining Technical and Business System for SAP ERP [page 64] Defining the Business Landscape for SAP ERP [page 65] About Configuring Transaction Processes [page 65] Importing the Design Package [page 66] About Configuring ERP Connectivity [page 67] Assigning Business Systems in the Integration Directory [page 67] Creating Communication Channels for ERP [page 68] Creating the IDoc Receiver Communication Channel [page 68] Creating the RFC Receiver Communication Channel [page 69] Configuring IDoc Metadata (Optional) [page 70] Configuring SAP NetWeaver PI Value Mapping [page 71] Creating a New Value Mapping Table [page 79] About Configuring the System Landscape Directory After you have installed the cXML Adapter. The Ariba Network Adapter for SAP NetWeaver leverages all the advantages of the SLD in order to maintain the coherence of the system landscape: ● It is defined as a product and component expressed in Common Information Interface (CIM) format importable in the SLD ● It uses a configuration using technical and business systems involved in the Ariba Network integration and defined in the SLD. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes © 2015 SAP SE or an SAP affiliate company. The information in this topic is applicable to the Ariba Network Adapter for SAP NetWeaver. you configure the System Landscape Directory (SLD) by importing the Ariba Network Adapter for SAP NetWeaver product definition and defining the systems involved in the integration. 61 . The SAP System Landscape Directory is a central repository that holds the information on the systems and software in the customer environment. All rights reserved. and on which machines. It consolidates the information about components actively available. and clients they are available. Configuring SLD and Transaction Processes .zip by clicking on the Browse button. and then click Import. 4. 3. as a CIM file. Start the import.com ○ Product: ASN ○ Version: NW04.Related Information Importing Ariba Network Product and Component Definitions [page 62] Defining Technical and Business System for Ariba Network [page 63] Defining Technical and Business System for SAP R/3 [page 64] Importing Ariba Network Product and Component Definitions Context Import the product and component definitions of Ariba products that will work with SAP NetWeaver PI. Procedure 1. Ariba Network Adapter for SAP NetWeaver Setup Guide 62 © 2015 SAP SE or an SAP affiliate company. In the Product Catalog.com ○ Component: ARIBA_SUPPLIER_CONN_ADAPTER ○ Version: CIX Results The Ariba Network Adapter for SAP NetWeaver will now be recognized by the Integration Repository and Directory. verify that the following product is available: ○ Vendor: ariba. All rights reserved. verify that the following component is available: ○ Vendor: ariba. 2. From the PI main page. and then navigating to the file location. open the SLD Administration page. 5. Select the AribaNetworkAdapterSAPNetweaver. Next.SoftwareCatalog. Navigate to the Content section.1 6. 6. from the System field. In the Wizard. Scroll down the list to select the product. Procedure 1. Click New Business System here to open the Business System Wizard. Defining the Business System for Ariba Network Procedure 1. created in the previous procedure. select Third-Party as the technical system type to associate the business system with. 2. and then click Add. E. TS_ASN. Select Technical Systems from the main SLD page to open the Technical System page. 3. Click Finish. 63 . defined earlier. and then click Next. 4. 7. select Third-Party as the Technical System Type to set up a third-party (non-SAP) application such as Ariba Network. an 5. ASN. You can also filter to select the product to associate. and then click Next. Select the technical system. Click Next.Defining Technical and Business System for Ariba Network Context Set up the technical system for the Ariba Network system using the Technical System Wizard. E. 2. Select Business System from the main SLD page to open the Business System page. is selected. Specify the system details as follows: ○ System Name: Specify a user-defined system name here. Associate the ASC Connector product and component to the system. Next Steps Set up the business system for the Ariba Network system using the Business System Wizard. Ensure that the component ARIBA_SUPPLIER_CONN_ADAPTER. 4. In the Wizard.g. 3. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes © 2015 SAP SE or an SAP affiliate company. and then click Next. TS_ASN ○ Host Name: Enter a host name here. Click New Technical System to open the Technical System Wizard.g. All rights reserved. Make sure that the product ASN. Installation Number. and then click Next. Specify a logon group for the Message Server by entering a value in the Logon Groups column and clicking Add Logon Groups to assign them.com. The logical system name is required for enabling the communication using IDocs between the SAP NetWeaver PI and ERP systems and is used for routing documents in multi-ERP implementations. Configuring SLD and Transaction Processes . and Message Server Port field. For more information about Multi-ERP implementations. Enter values in the Client Number and Logical Client Name columns of the Client List table.1 and the related component ARIBA_SUPPLIER_CONN_ADAPTER. 4. NW04. 9. Specify the Message Server and Central Application Server. and then click Next.g. 8. e. 3. Note The Logical System Name is not required. 6. Click on New Technical System here to open the Technical System Wizard. Enter values in the Host Name and Instance Number fields for the Central Application Server. 7. To specify the SAP ERP system details enter values in the AS ABAP name (SID). All rights reserved. Click Next. Enter the business system name. Select the SAP ERP version installed on this technical system. as well all other products installed on the system. BS_ASN. (Optional) Define additional application servers if required. installed on the technical system. 7. and then click Next. and click Next. You can also filter to select the application server details. In the Wizard. Specify values in the Host Name and Instance Number columns in the Application Server List table. Defining Technical and Business System for SAP ERP Context Set up the technical system for the SAP ERP system using the Technical System Wizard. are selected. You can filter to select the installed products and the software components. and Database Host Name fields. Select Technical System from the main SLD page to open the Technical System page. Ariba Network Adapter for SAP NetWeaver Setup Guide 64 © 2015 SAP SE or an SAP affiliate company. see the “Linking Multiple SAP instances with Ariba Network” [page 212] section. and then click Next. 6. and then click Next. Define the Client. Enter values in the Host Name. Procedure 1. Define software product and components. 5. Specify the installed products. in the Name field. You can also filter to select the logon groups. 2. and click Add Application Server. Click Finish. CIX of ariba. Click Finish. 5. select AS ABAP as the Technical System Type. 7. Select Application System as the Business System Role and select your SAP NetWeaver PI instance name from the Related Integration Server drop-down list to specify the integration server. 8. BS_SAPR3_50. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes © 2015 SAP SE or an SAP affiliate company. ● Configure SAP NetWeaver PI value mapping to provide the global configuration. Select a client for the selected technical system from the Client drop down list. ● Configure the communication channels and the conditions for routing messages. Select the products that must be supported by this business system from the ones available from the associated technical system. Specify the installed products. Defining the Business Landscape for SAP ERP Procedure 1. Select Business System from the main SLD page to open the Business System page. About Configuring Transaction Processes After you have installed the System Landscape Directory (SLD). and click Next. and then click Next. In the Wizard. 3. 2. Click Finish. Enter the business system name. E. All rights reserved. select AS ABAP as technical system type to associate the business system with. for each supported transaction. 65 . In the case of application systems. 5. you must: ● Import the design package containing the transactions supported by the Ariba Network Adapter for SAP NetWeaver. Select the technical system created in the previous procedure from the System drop down list. to install them in the business system.Next Steps Set up the business system for the SAP ERP system using the Business System Wizard. Select the role of the business system. and then click Next. to associate it with the business system. 4. specify the integration server.g. 6. ● Configure the different transactions in the Integration Directory by importing the scenarios from the Integration Repository. and supporting facilities such as IDoc Payload and standard code conversions. ● Configure SAP NetWeaver PI connectivity to ERP. Click New Business System here to open the Business System Wizard. and then click Next. 6.tpz to the import directory on the SAP NetWeaver PI server.tpz contains the definition of the business scenarios.Design. After the import completes.. Ariba Network Adapter for SAP NetWeaver Setup Guide 66 © 2015 SAP SE or an SAP affiliate company.Design. 2. For example. You must also implement the changes specified in the SAP Note 1688610. select the Import Design objects. Procedure 1. Configuring SLD and Transaction Processes .tpz from the available files list. Select AribaNetworkAdapterSAPNetweaver. option. Related Information Importing the Design Package [page 66] About Configuring ERP Connectivity [page 67] Configuring SAP NetWeaver PI Value Mapping [page 71] Importing the Design Package Context The transport file AribaNetworkAdapterSAPNetweaver. 4. If you are trying to install the Cloud Release version of the SAP PI Adapter on an SAP ERP 6. Open the Enterprise Services Builder: Design Tool from the SAP NetWeaver PI main page. You may use them or replace them with names and format corresponding to your system environment. ensure that you click to select the check box ‘Ignore Invalid Component Version’. the component ARIBA_SUPPLIER_CONN_ADAPTER. *****\SYS\global\xi\repository_server\import. CIX appears in the components list of the Integration Builder Design Tool. and then click OK.Design..0 EHP6 or higher. All rights reserved. 5. Copy the package file AribaNetworkAdapterSAPNetweaver. 3. Note The names for objects in the Directory used in the configuration procedures are examples provided for illustration. From the Tools menu. D:\usr\sap\ARB\SYS\global\xi\repository_server\import. Assigning Business Systems in the Integration Directory Context The Integration Directory configuration of the Ariba Network Adapter for SAP NetWeaver uses the information on the Technical and Business systems from the SLD. Procedure 1.About Configuring ERP Connectivity Context To enable communication between SAP NetWeaver PI and SAP ERP using IDoc documents. navigate to Service Without Party Business System. In the Objects tab of the Integration Builder. create an RFC destination of type ERP to connect to the SAP ERP system. You must assign the Business Systems defined and involved in the integration setup. Using Transaction SM59. ○ Client 800. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes © 2015 SAP SE or an SAP affiliate company. create a Port for the new RFC destination. ● Configure the Port for the IDoc Adapter SAP NetWeaver PI connectivity to ERP. we need to configure the following parameters on the SAP NetWeaver PI ABAP stack: ● Configure the RFC Destination. 2. 67 . 2. Note Enter the password in UPPER case. Open the Configuration: Integration Builder from the PI main page. All rights reserved. you must use specify following parameters to create the port: ○ Port: SAPD47. for the SAP ERP system D47 client 800. Using Transaction IDX1. For example. ○ RFC Destination: Specify the destination created in SM59 here. Procedure 1. 3. In the third window. Creating Communication Channels for ERP Create the communication channels used for ERP connectivity. Leave the Party field in the second window blank. In the Create Object window. select Assign Business System to start the Assign Business System wizard. From the context menu for Communication Channel select New. 6. 4. Click on Continue in the first and second windows. for each Business System corresponding to your SAP ERP. see the “About Configuring the System Landscape Directory” [page 61] section. Click Finish. you only need to create them once. From the context menu for Business System. 7. specify CC_IDoc_Receiver as the name of the communication channel in the Communication Channel field. 2. Click to clear the Create Communication Channel Automatically check box. if it is checked. from the list. All rights reserved. Related Information Creating the IDoc Receiver Communication Channel [page 68] Creating the RFC Receiver Communication Channel [page 69] Configuring IDoc Metadata (Optional) [page 70] Creating the IDoc Receiver Communication Channel Procedure 1. Note In the case of Multi-ERP implementation. select the business systems BS_ASN and BS_SAPR3_50 created earlier. So. Configuring SLD and Transaction Processes . These channels will be used by almost all the scenarios and are common to all of them. click Communication Channel. In the Objects tab of the Integration Builder.3. you must select all the Business Systems representing your SAP ERP instances involved in the integration. For more information about creating business systems. You must create the IDoc Receiver and RFC Receiver communication channels from the Integration Builder to enable communication using IDocs and the RFC invocation on the remote SAP ERP system. Ariba Network Adapter for SAP NetWeaver Setup Guide 68 © 2015 SAP SE or an SAP affiliate company. to avoid the creation of unwanted channels. Select Business Systems. 5. say BS_SAPR3_50. representing each of the SAP ERP instances involved in the integration.10 7. After selecting the adapter. Edit the other parameters. select the following adapter. navigate to Service Without Party Business System BS_SAPR3_50 Communication Channel .com/xi/XI/System ○ Software Component Version: SAP BASIS 7. From the Choose Adapter Metadata window. In the Create Object window. in the Communication Channel field. 8. to select the corresponding type. select New. 4. and then click Create. depending on your configuration. specify CC_RFC_Receiver as the name of the communication channel. select the following adapter and click OK: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes © 2015 SAP SE or an SAP affiliate company. From the Parameters tab of the Edit Communication Channel window. and click Apply. In the Adapter Engine field. Interface Version. Click Create 6. From the adapter type list window. In the following Choose Communication Component window. to match your SAP R3 system (RFC Destination. then click the Display Input Help drop down list and select Input Help. Click the Communication Component field. 3. 4. then click the Display Input Help drop down list and select Input Help to display the list of adapter types. select a communication component. Save and activate the communication channel. click the icon next to the Adapter Type field to display the list of adapter types. and then click Apply: ○ Name: IDoc ○ Namespace: http://sap. All rights reserved. 2. click the Adapter Type field. 5. SAP Release). Results Note In the case of Multi-ERP implementation. From the Parameters tab of the Edit Communication Channel window. Port. 69 . click the Receiver option. 10. Select the following options and leave the others unchecked: ○ Apply Control Record Values From Payload ○ Take Sender From Payload 11. select Integration Server or non-central Adapter Engine. From the context menu for Communication Channel. 9. In the Objects tab of the Integration Builder. Creating the RFC Receiver Communication Channel Procedure 1. you must create one CC_IDoc_Receiver channel per Business System. If they are not. Note Enter the password in UPPER case. Check and configure the IDoc Metadata parameters of the port to communicate with the SAP ERP system in SAP NetWeaver PI. 6. Logon User. Save and activate the communication channel. click Metadata Create to add them. Edit the Maximum Connections option according to the excepted load. Logon Language.10 5.com/xi/XI/System ○ Software Component Version: SAP BASIS 7. Logon Password. DESADV01. In the Adapter Engine field. Refer to the transaction IDX2. the metadata information will be downloaded and associated to the port the first time a given type of IDoc is exchanged. Logon Client). representing each of the SAP ERP instances involved in the integration. Ariba Network Adapter for SAP NetWeaver Setup Guide 70 © 2015 SAP SE or an SAP affiliate company. 2. 9. Check the IDoc Metadata in Metadata Overview for the IDoc Adapter to see if all the inbound IDocs (ORDERS05. Note In the case of Multi-ERP implementation. ○ Name: RFC ○ Namespace: http://sap. After selecting the adapter. If you skip do not preload metadata. you must create one CC_RFC_Receiver channel per Business System. to select the corresponding type. 7. All rights reserved. Edit the other parameters to match your SAP R3 system (Application Server. System Number. Procedure 1. 8. INVOIC02 and FIDCCH01) are there. click the Receiver option. Authentication Mode. select Integration Server or non-central Adapter Engine. Configuring SLD and Transaction Processes . Configuring IDoc Metadata (Optional) Context You can optionally preload the metadata of the IDoc documents exchanged by the IDoc adapter during configuration. depending on your configuration. The following table shows examples of the respective value sets: UOM_ERP UOM_ISO PCE C62 KGM KGM Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes © 2015 SAP SE or an SAP affiliate company. such as UOM. All rights reserved. or vice versa. certain codes. to set up the transformation rules for Units of Measure. In the value mappings. For information on the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On. see Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On [page 61]. need to be mapped between different standards. use the following parameters for UOM transformation rules: ● Source Values: ○ Agency: UOM_ERP ○ Scheme: UOM ● Target Values: ○ Agency: UOM_ISO ○ Scheme: UOM Fill in the value set for UOM_ERP and UOM_ISO.Configuring SAP NetWeaver PI Value Mapping Configure SAP NetWeaver PI value mapping for supporting facilities such as IDoc Payload and standard code conversions. 71 . This section provides the steps to configure these mappings. Related Information Configuring Units of Measure (UOM) Code Mapping [page 71] Configuring Language Mapping [page 72] Configuring TimeZone Mapping [page 72] Configuring Global Variables [page 73] Configure the Mappings Between Business System and Logical System Names [page 76] Configuring Currency Mapping [page 77] Creating a New Value Mapping Table [page 79] Configuring Units of Measure (UOM) Code Mapping As part of the transformation of documents from IDoc to cXML. The information in this topic is applicable to the Ariba Network Adapter for SAP NetWeaver. UOM_ERP UOM_ISO LT LTR Configuring Language Mapping In the value mappings. use the following parameters for language transformations rules: ● Source Values: ○ Agency: LANG_ERP ○ Scheme: Lang ● Target Values: ○ Agency: LANG_ISO (an example value of SAP ERP Business Systems) ○ Scheme: Lang Fill in the value set for UOM_ERP and UOM_ISO. Ariba Network Adapter for SAP NetWeaver Setup Guide 72 © 2015 SAP SE or an SAP affiliate company. The following table shows examples of the respective value sets: LANG_ERP LANG_ISO D de E en F fr Configuring TimeZone Mapping In the value mappings. to set up the transformation rules for languages. use the following parameters for TimeZone transformations for different Business Systems and for Ariba Network: ● Source Values: ○ Agency: XI_Global ○ Scheme: GlobalVariable ● Target Values: ○ Agency: BS_SAPR3 (an example value of SAP ERP Business Systems) ○ Scheme: TimeZone Fill in the values to set up the transformation rules for TimeZone. All rights reserved. Configuring SLD and Transaction Processes . (Use it for test and devel­ opment only and NOT for pro­ duction) IsMultiERPModeEnabled true/false BPMConfig Use this parameter to enable (true) or disable (false) the Multi-ERP support. This section describes the steps to configure global variables.) Use this timestamp when the InvoiceStatus 2006-10-09T12:13: BPMConfig timestamp file for the UpdateStartDate 14 Time InvoiceStatusUpdate transaction is not configured or its date/time parameters are empty. SAP NetWeaver PI Global Example SAP NetWeaver PI Group Name Description Variable Value Use this timestamp when the PaymentProposal 2006-10-09T12:13: BPMConfig timestamp file for the StartDateTime 13 PaymentProposal transac­ tion is not configured or its date/time parameters are empty.The following table shows examples of the TimeZone transformation values: Agency Scheme Value XI_Global GlobalVariable TimeZone BS_SAPR3_50 TimeZone 05:45 Configuring Global Variables Because SAP NetWeaver PI acts as the integration platform between SAP ERP and Ariba Network. All rights reserved. use the following parameters for Global Variables: ● Source Values: ○ Agency: XI_Global ○ Scheme: GlobalVariable ● Target Values: ○ Agency: XI ○ Scheme: GlobalVariable Fill in the global variable table as appropriate for your system. (Use it for test and devel­ opment only and NOT for pro­ duction. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes © 2015 SAP SE or an SAP affiliate company. 73 . there are many parameters that are global for each of the supported scenarios. In the value mappings. OrbianPaymentMethod Orbian BPMConfig Use this parameter to provide a Description description for the Orbian pay­ ment method. OrbianPaymentMethod O BPMConfig Use this parameter to set the Orbian payment method.SAP NetWeaver PI Global Example SAP NetWeaver PI Group Name Description Variable Value ReceiptStartDate 2006-10-09T12:13:15 BPMConfig Use this timestamp when the Time timestamp file for the Receipt transaction is not configured or its date/time parameters are empty. Configure the value in the format -HH:mm or +HH:mm. Use this parameter to set the SAPAccountingDocT SA BPMConfig SAP accounting document type. R3LS T90CLNT090 BPMConfig Use this parameter to set the default SAP ERP logical system ID. where it is not manda­ tory to configure the System ID in the Ariba Network Buyer Ac­ count. ype SAPUserName <a valid SAP user name> BPMConfig Use this parameter to set the SAP user name. In such cases. Configuring SLD and Transaction Processes . (Use it for test and devel­ opment only and NOT for pro­ duction. the Sys­ tem ID will be obtained from this parameter. Use this parameter to set the SAPExternalPaymen C BPMConfig payment method used in exter­ t Method nal payment. Set this parameter if you are using the PaymentRemittanceAdvic e transaction in a single ERP in­ stallation. You must configure the value for this parameter in each agency representing the SAP R3 Busi­ ness System.) TimeZone -08:00 or +05:30 BPMConfig Use this parameter label to con­ figure time zones in each of the configured SAP R3 Business Systems. This must be a valid method defined in SAP. Ariba Network Adapter for SAP NetWeaver Setup Guide 74 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Set this parameter if you are using the PaymentRemittanceAdvic e transaction. you must specify NB. However. NA. Note If you want to maintain multi­ ple doc types for purchase orders. However. PurchaseOrderDocTypes NB BPMConfig This variable must contain the value for the SAP document type for purchase orders. SAP NetWeaver PI Global Example SAP NetWeaver PI Group Name Description Variable Value BusinessSystem BS_SAPR3_50 Lookup Use the name of the Business System in cases that involve a Single ERP configuration. LP is the default doctype in the SAP sys­ tem. All rights reserved.AS in the Value for XI field. 75 . then the value of this pa­ rameter will be used to populate the target cXML. DefaultLanguageCode EN BPMConfig If the PO Idoc message from the SAP ERP system does not con­ tain a value for the language code. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes © 2015 SAP SE or an SAP affiliate company. SNDPFC LF_SND SAPEDIDC This denotes a constant used for the IDoc control field SNDPFC. Configure this param­ eter with a value that indicates the RFC Receiver Communica­ tion Channel configured for all the SAP R3 Business Services in your Configuration Directory. NB is the default doctype in the SAP system. SNDPRT LI_SND SAPEDIDC This denotes a constant used for the IDoc control field SNDPRT. BlanketOrderDocType LP BPMConfig This variable must contain the value for the SAP document type for blanket orders. customers can have a different doc type as­ signed to their purchase orders. customers can have a different doc type as­ signed to their blanket orders. Communication RFC_Lookup_Receiver Lookup This denotes the name of the Channel communication channel to be used by the Lookup API in the mapping. If you are an existing customer and want to continue using the canceled status when an in­ voice is canceled in the SAP ERP system. Source: ● Agency: LogSys_Source ● Scheme: Lookup Ariba Network Adapter for SAP NetWeaver Setup Guide 76 © 2015 SAP SE or an SAP affiliate company.SAP NetWeaver PI Global Example SAP NetWeaver PI Group Name Description Variable Value ISU_ERP_INV_Canceled canceled/rejected In the SAP ERP system. DefaultRequesterEmailID The email ID of the requester in the SAP ERP system. if you want to send the rejected status when a user cancels an invoice in the SAP ERP system. However. the status code 423 and status rejected are sent to Ariba Network. then the status code 200 and status canceled instead of rejected are sent to Ariba Network. DefaultPreparerEmailID The email ID of the preparer in the SAP ERP system. All rights reserved. Configure the Mappings Between Business System and Logical System Names In the value mappings. Configuring SLD and Transaction Processes . However. when an _Rejected_Status invoice fails to get created. then you must set the value of this variable to rejected. then you are not re­ quired to make any changes as the default value of this variable is set to canceled. Note New customers are recom­ mended to set the value of this variable to rejected. if a user can­ cels an invoice in SAP ERP sys­ tem. use the following parameters to configure the mappings between business systems and logical systems. you must preserve the value mappings for currencies in the TCURX table. LogSys_Source BusSys_Target T90CLNT090 BS_SAP_46C T47CLNT800 BS_SAP_47 Note In the case of Multi-ERP implementation. The following table shows an example of values. Currencies having more than two decimal places show the NETPR value adjusted to two decimal places incorrectly. For example. If the currency for one of the line items is 10.00000. By default. additional value mappings need to be defined. 77 . To maintain precision in currencies correctly.00. the value stored in the EKPO table is 100000. when a purchase order is created. see the “Linking Multiple SAP instances with Ariba Network” [page 212] section. ● Value: Logical System Name Target: ● Agency: BusSys_Target ● Scheme: Lookup ● Value: Business System Name Note The Group Name is not required. the EKPO table is updated with the purchase order information. For more information. Configuring Currency Mapping You can configure the currency precision maintained in the TURX table on your SAP NetWeaver PI system. Enter the values for the following parameters: Source Values: Agency: ERP_Currency Scheme: Currency Target Values: Agency: Currency_Precision Scheme: Currency Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes © 2015 SAP SE or an SAP affiliate company. All rights reserved. the precision for currencies is two decimal places. Specify the logical system name as follows: Agency Scheme Value XI_Global GlobalVariable Name of the logical system XI GlobalVariable R3PartnerProfileLS 4. click Value Mapping. as follows: Agency Scheme Value XI_Global GlobalVariable IsLogicalSystemEnabled XI GlobalVariable yes 3. maintain the value mapping for the logical system in the SAP NetWeaver PI.Here is an example of how the precision for currencies are maintained: Value for Currency_Precision Values for the ERP_Currency Group Name 0 JPY Currency 5 USDN Currency 3 PKT Currency 0 TWD Currency Maintaining the Value Mapping to Support Logical Systems in SAP NetWeaver PI Context To process documents through the logical system. Procedure 1. In the Display Value Mapping window enter the Agency and Scheme values for the source and target in the respective fields. 2. (Mandatory if you are a buyer using multiple ERP systems) In the Display Value Mapping Agencies page. All rights reserved. Configuring SLD and Transaction Processes . map the logical system to the system ID of the multiple ERP systems (business systems) with the following values: Agency Scheme Value For SystemIDFrom_cXML SystemIDFrom_cXML Lookup System ID of the ERP system Ariba Network Adapter for SAP NetWeaver Setup Guide 78 © 2015 SAP SE or an SAP affiliate company. In the Tools menu. 79 . In the Display Value Mapping window enter the Agency and Scheme values for the source and target in the respective fields. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes © 2015 SAP SE or an SAP affiliate company. Agency Scheme Value For Group Name SenderPartner_LogicalSystem SenderPartner_LogicalSyste Lookup Name of the logical system SystemIDFrom_cXML m Creating a New Value Mapping Table Context Create a new value mapping table if the Agency/Scheme is not available. Procedure 1. 5. Click on the ‘+’ icon to add the Value Mappings. click Value Mapping. Click Display. as follows: ○ Source Values For Agency: UOM_ERP Scheme: UOM ○ Target Values For Agency: UOM_ISO Scheme: UOM 3. 4. 2. In the Tools menu. Click the Change/Edit button to bring the table into Edit Mode. All rights reserved. Configuring Integration Scenarios About Configuring Integration Scenarios in the Integration Directory [page 80] Purchase Order Integration Scenario [page 82] Change Purchase Order Integration Scenario [page 89] Order Confirmation Integration Scenario [page 93] Ship Notice Integration Scenario [page 102] Ship Notice Integration Scenario to Support Creation of a Single Ship Notice Against Multiple Purchase Orders [page 109] Service Sheet and Service Sheet Response Integration Scenario [page 117] Invoice Integration Scenario [page 123] PayMeNow Integration Scenario [page 130] Payment Remittance Integration Scenario [page 137] Schedule Lines in Purchase Orders and Change Purchase Orders [page 143] Blanket Purchase Order Integration Scenario [page 144] Order Inquiries Integration Scenario [page 146] Scheduling Agreement Release Integration Scenario [page 153] Invoice Status Update Integration Scenario [page 160] ERP-Initiated Invoice Integration Scenario [page 167] Receipt Integration Scenario [page 173] Receipt Integration Scenario for Corrections and Returns in Receipts [page 179] Receipt Integration Scenario for Purchase Orders with Multiple Accounting Assignments [page 182] Payment Proposal Integration Scenario [page 184] Requisition Request Integration Scenario [page 190] Request for Quotation Integration Scenario [page 196] Sourcing Award to Contract Integration [page 201] Change Purchase Order Implementation Redesigned [page 208] Proxy Implementation for Outbound Transactions [page 210] About Configuring Integration Scenarios in the Integration Directory This section describes how to import and configure the integration scenarios in the SAP NetWeaver PI Integration Directory for the supported transactions. All rights reserved. Use an integration scenario from the Integration Repository as a Ariba Network Adapter for SAP NetWeaver Setup Guide 80 © 2015 SAP SE or an SAP affiliate company. Configuring Integration Scenarios . All rights reserved.10. Configure the Integration Scenarios for the following inbound transactions: ● Order Confirmation Integration Scenario [page 93] ● Configuring and Activating the Ship Notice Integration Scenario [page 102] ● Configuring and Activating the Ship Notice Integration Scenario to Support Creation of a Single Ship Notice Against Multiple Purchase Orders [page 109] ● Service Sheet and Service Sheet Response Integration Scenario [page 117] ● Invoice Integration Scenario [page 123] ● PayMeNow Integration Scenario [page 130] Configure the Integration Directory for the following outbound transactions: ● Purchase Order Integration Scenario [page 82] ● Change Purchase Order Integration Scenario [page 89] ● Change Purchase Order Implementation Redesigned [page 208] ● Schedule Lines in Purchase Orders and Change Purchase Orders [page 143] ● Blanket Purchase Order Integration Scenario [page 144] ● Order Inquiries Integration Scenario [page 146] ● Scheduling Agreement Release Integration Scenario [page 153] ● Payment Remittance Integration Scenario [page 137] ● Invoice Status Update Integration Scenario [page 160] ● ERP-Initiated Invoice Integration Scenario [page 167] ● Configuring and Activating the Receipt Integration Scenario [page 173] ● Payment Proposal Integration Scenario [page 184] ● Requisition Request Integration Scenario [page 190] ● Request for Quotation Integration Scenario [page 196] Configuring the Software Component Version for Communication Channel Templates [page 82] Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. Note Do not activate the Change Lists feature of Integration Builder Configuration Tool until all the configuration steps are completed.10 not found. which has to be imported into the Integration Repository first. then you must ensure that you edit the software component version for the communication channel template to avoid receiving the following error: "Software component version with name SAP BASIS 7. See error log for details. 81 .template for configuring the corresponding transaction in the Integration Directory. If you are using a SAP NetWeaver PI version that is higher than SAP BASIS 7." For more information. The Integration Scenarios are part of the Design package. see Configuring the Software Component Version for Communication Channel Templates [page 82]. Go to the Enterprise Service Builder and edit each of the communication channel templates for the http:// ariba. changed purchase orders. and canceled purchase orders. The Choose Adapter Metadata page appears. When a buyer manually specifies the delivery address. click the Display Input Help button in the Adapter Type field.10.com/xi/ASN/ ariba. Configuring Integration Scenarios .com/xi/ASN/ ariba.com CommonBasis Purchase Order Integration Scenario You need to configure the integration scenario for the Purchase Order transaction in the Integration Directory to be able to run the transaction for new purchase orders. Double click each of the following communication channel template. Double click the required communication channel template.com CommonBasis ARIBA_SUPPLIER_CONN CCT_IDoc_Receiver IDOC http:// _ADAPTER CIX of ariba.com/xi/ASN/CommonBasis Software Component Version: ○ CCT_IDOC_RECEIVER ○ CCT_RFC_LOOKUP_RECEIVER 2. 4.Configuring the Software Component Version for Communication Channel Templates Context If you are using a SAP NetWeaver PI version that is higher than SAP BASIS 7. Procedure 1. In the Parameters tab. All rights reserved. 5. then you must ensure that you edit the communication channel template to avoid receiving an error. Software Component Version Communication Channel Adapter Type Namespace Template ARIBA_SUPPLIER_CONN CCT_RFC_Lookup_Rece RFC http:// _ADAPTER CIX of iver ariba. Ariba Network Adapter for SAP NetWeaver processes the manually entered values in the delivery address field as follows: Ariba Network Adapter for SAP NetWeaver Setup Guide 82 © 2015 SAP SE or an SAP affiliate company. Choose the common Basis version for each of the communication channel templates. The Display Communication Channel Template page appears. All the steps of a configuration scenario section must be completed to fully configure a scenario. 3. Important: Ensure that you have the necessary options enabled for the Object Properties on the Software Component Version page that allows you to edit the communication channel template. The Display Software Component Version page appears. then: ● The ship-to address appears at the header level in cXML/Ariba Network ● The ship-to address does not appear at the line level in cXML/Ariba Network ● The bill-to address in the header matches the ship-to address If purchase order lines have different ship-to addresses. Ariba recommends that customers use the BADI customization in these cases. Note If a buyer entered the street address as the delivery address for certain countries. Ariba Network Adapter for SAP NetWeaver sends the plant address as the ShipTo address. the street address then contains the street name and the house number instead of the house number and street. ● If a buyer manually entered the delivery address to include the following fields in the Delivery Address tab. edited the street address. Ariba Network Adapter for SAP NetWeaver sends the storage location address as the shipTo address. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. ● If a buyer manually selected the address ID. In some cases. Ariba Network Adapter for SAP NetWeaver sends the associated delivery address as the ShipTo address in the purchase order: ○ Address ID in the Address field ○ Customer ID in the Customer field ○ Vendor ID in the Vendor field ● If the buyer has only the plant address and does not have the storage location in the purchase order. or vendor ID is not sent in the change purchase order. or vendor ID in the Delivery Address tab. if a buyer selected the address ID. Ariba Network Adapter for SAP NetWeaver sends the newly saved delivery address as the ShipTo address in the purchase order. Ariba Network Adapter for SAP NetWeaver processes the name field from the Name_text field instead of Name1. Mapping Limitations The Purchase Order transaction has the following mapping limitations: ● Time Zone is hard coded to Pacific time zone ● Bill-to and Ship-to addresses in SAP purchase orders behave as follows: If all purchase order lines have the same ship-to address. ● If the buyer has both the plant and storage location in the line item and the storage location address is maintained in the ox09 on the SAP ERP system. customer ID. Ariba Network Adapter for SAP NetWeaver sends the newly edited street address as part of the Shipto address in the purchase order. and then edited the existing values of the address. All rights reserved. then: ● Ship-to addresses do not appear at the header level in cXML/Ariba Network ● Ship-to addresses appear at the line level in cXML/Ariba Network ● The bill-to address in the header matches the ship-to address in the first line ● The shipping information is not supported. The delivery address stored on the SAP ERP system for the address ID. For example. and saved the changes. customer ID. 83 . CIX of ariba. 5. In the first screen of the Transfer Model from ES Repository wizard. Activate the new configuration. Select Process Integration Scenario. select Integration Directory Integration Builder . If required. To configure purchase orders: 1. see the “About Configuring the System Landscape Directory” [page 61] section. Click Continue. Ariba Network Adapter for SAP NetWeaver Setup Guide 84 © 2015 SAP SE or an SAP affiliate company. Configuring Integration Scenarios . and then login into the Configuration: Integration Builder application. change the name of the scenario for the Integration Directory 6. 2. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 3.com 4. select Tools Apply Model from ES Repository . 3. In the Integration Builder menu. For more information about configuring the SLD. The following steps assume that the different Business Systems are defined in the SLD. All rights reserved. Configure the Integration Scenario. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_PurchaseOrder_Receive ○ Namespace: http://ariba. From the SAP NetWeaver PI main page. the integration scenario loaded into the Integration Repository when the Design package is imported. Procedure 1.com/xi/ASN/PurchaseOrder ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. 4. 2.Workflow Note Ensure that the Design package is imported into your system and ready before you run these steps. click the Name field. then click the Display Input Help drop down list and select Input Help. Click Finish. Transferring the Purchase Order Integration Scenario Context The first step to configure the integration scenario for the Purchase Order transaction is to transfer to the Integration Directory. Configure the Communication Channels. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 2.Results Once the transfer is completed. Click on the row under the Communication Component column. Generate Configuration Objects. 4. Next Steps After selecting the model. select the Business System Components for A2A tab to assign components for Ariba Network. you must assign components to the application components of the selected integration scenario. 3. Select the communication component name BS_SAPR3_50. About Configuring the Purchase Order Integration Scenario After the Integration Scenario is selected. Configure Connections. you configure it using the following steps. 2. Assign Components. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. the Model Configurator window appears. Selecting the Model for the Scenario Procedure In the Model Configurator window. click the Assign Component button. Assign the Model. In the Assign Components window. 3. click the Select Component View button and then click Apply to select the unique model that is selected by default. 1. 85 . 4. from the selection list and click Apply. then click on the Value List drop down and select Value List <F4. All rights reserved. Assigning Components for the Purchase Order Integration Scenario Procedure 1. In the Model Configurator. you can create the communication channel by copy from a channel already configured. Next Steps After assigning components. Click on the row under the Communication Component column. Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction.com 5. click the empty Communication Channel cell corresponding to BS_ASN in the Receiver Business System Components table. modify the channel name to CC_PurchaseOrder_cXML_Receiver. 5. You must assign Communication Channels to set up the connections. 2. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. Click Continue. click the Configure Connections button. Click the New Communication Channel button (the icon at the top left). In the Model Configurator. 8. Ariba Network Adapter for SAP NetWeaver Setup Guide 86 © 2015 SAP SE or an SAP affiliate company. 3. you must define sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. and then click Finish. from the selection list and click Apply. Click the Save Settings button to save the changes. add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4. then click the Display Input Help drop down list and select Input Help. Click the Next Role button (the right arrow) to go to the next screen in the window. Select the communication component name BS_ASN. CIX of ariba. Configuring Connections for the Purchase Order Integration Scenario Procedure 1. and in the next page click the Name field. then click on the Value List drop down and select Value List <F4. Configuring Integration Scenarios .com/xi/ASN/PurchaseOrder ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. Select the following Communication Channel Template: ○ Name: CCT_PurchaseOrder_cXML_Receiver ○ Namespace: http://ariba. Click Continue. Note For Multi ERP implementation. In the Connections from Component Assignment tab in the Configure Connection window. 6. All rights reserved. 4. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is present. 7. You can also simulate generation for test purposes. Procedure 1. Note The communication channels for SAP ERP Sender system are not required. they will be reused and enhanced. Click on Start to begin generating objects. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. In the Model Configurator. 6. 5. if required. Click the Save Settings button to save the changes. you must generate the objects. 7. 87 . 4. You can save it. If they do already exist. Generating Objects for the Purchase Order Integration Scenario Context After making all the configuration settings in the wizard. Configuring Communication Channels for the Purchase Order Integration Scenario Context Configure the communication channel CC_PuchaseOrder_cXML_Receiver under the AR_PurchaseOrder_Receive Configuration Scenario. make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select both the active check boxes – Receiver Determination. Close the log that is created without saving. After the object generation is complete. Generation creates the configuration objects if they do not yet exist. and Interface Determination. Click the Activate All Connections button. All rights reserved. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. if required. click Apply to save the new configuration settings. 2. In the Create Configuration Object window. 3. and then click OK in the dialog box. click the Create Configuration Object button. 5.ORDERS05 | | BS_ASN. Configuring Integration Scenarios . edit the other parameters.unbounded". In the Receiver Interfaces section of the Edit Interface Determination window. If required.. then click the Value List drop down and select Value List. All rights reserved. 4. Under Communication Channel.Procedure 1. double-click |BS_ASN|CC_PuchaseOrder_cXML_Receiver to open it. Save the changes. Save the interface determination settings. The Multiplicity column displays the value "0. Procedure 1. Configuring Interface Determination Settings for the Purchase Order Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. 2. 2. In the Parameters tab. Select the operation mapping IFM_ORDERS_ORDERS05_2_cXML and click Apply. 3. Expand Interface Determination. Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings. For more information about the cXML Adapter parameters. or right-click and select Open. you need to change the request type to OrderRequest in the Outbound Request Type field. 3. Note If you created the channel by copy from an existing channel. Ariba Network Adapter for SAP NetWeaver Setup Guide 88 © 2015 SAP SE or an SAP affiliate company. and then click |BS_SAPR3_50 | ORDERS. see cXML Adapter Parameters [page 391]. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. click the operation mapping value under the Operation Mapping column. ○ Customers who also employ change order transaction customizations must migrate those customizations to their purchase order transaction customizations. activate all the Change Lists containing the objects created and modified during the component setup. The Change Purchase Order Integration scenario and the http://ariba.com/xi/ASN/ChangedPurchaseOrder namespace no longer exists. Note This change in functionality does not affect how the adapter processes new purchase orders. 89 . For more information on the purchase order integration scenario.Activating the Purchase Order Integration Scenario Context Using the Change List tab on the main application screen. Related Information Reconfiguring the SAP Partner Profile [page 90] About Configuring Implicit Enhancements [page 91] Removing Change Order Configurations from Your Ariba Solution [page 93] Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. ○ Must remove their old change order configuration from their Ariba solutions. All rights reserved. Enhancements to change and cancel purchase order processing are not backward compatible with previous releases. ○ Must set up SAP ERP Partner Profiles. and for change and cancel purchase orders. It is no longer needed. Change Purchase Order Integration Scenario You must configure the integration scenario for the Purchase Order transaction in the Integration Directory to be able to run the change purchase order transaction. ● Changes Required for Existing Customers Existing customers must do the following: ○ Must reconfigure their existing change order configuration in the SAP ERP Partner Profile (WE20). see Purchase Order Integration Scenario [page 82] . ● Changes Required for New Customers New customers must do the following: ○ Must make one-time configuration changes to SAP ERP implicit enhancements. ○ Make one-time configuration changes to SAP ERP implicit enhancements for change and cancel purchase orders. This completes the configuration of the Purchase Order transaction in SAP NetWeaver PI. Change purchase orders are now subsumed into IDoc processing for purchase orders. Retain the default selection. 6. All rights reserved.. Go to transaction WE20 to modify an existing partner profile. for the Output Mode parameter in the Outbound Options tab. Procedure 1. 2. Table 1: Change Purchase Order Parameters Parameter Name Value Partner function VN Message type ORDERS IDoc type ORDERS05 Application EF Output type NEU Process code ME10 Change True (checked) 5. Choose Partner type LI (Vendor). Click on Insert Row (the green + sign) and enter the following parameters. Ariba Network Adapter for SAP NetWeaver Setup Guide 90 © 2015 SAP SE or an SAP affiliate company. and click Edit. 3. 4.. Select Message Type ORDERS and doublie-click. Configuring Integration Scenarios .Migrating Change Order Customizations [page 93] Reconfiguring the SAP Partner Profile To enable change order enhancements you must modify your existing SAP Partner Profile (transaction WE20) to process change and cancel orders as variations on a standard purchase order. Transfer IDoc Immed. Save your changes. select a vendor. In the package popup. CREATE OBJECT cl_PO_ChangeCancel. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 91 . Enter a name and description for the enhancement and press Enter.LEINMF0Q and click Display. CALL METHOD cl_PO_ChangeCancel->trigger_delete_po_idoc EXPORTING ebeln = h_ebeln CHANGING xdruvo = xdruvo. Configuring Implicit Enhancements for Change and Cancel Orders To enable SAP ERP to send the correct change and cancel order information to the Ariba Network Adapter for SAP NetWeaver. Activate the enhancement and save it. 6. 2. Click Create Enhancement Implementation. 8. 4. and save the package to a transport request. 5. you must configure two SAP ERP implicit enhancements. Copy the following code: DATA: cl_PO_ChangeCancel TYPE REF TO /arba/cl_PO_ChangeCancel.About Configuring Implicit Enhancements To enable SAP ERP to send correct new. 12. Right-click the line and select Enhancement Implementation > Create. In your SAP ERP system. Click Enhance in the application toolbar. navigate to transaction code SE38 . All rights reserved. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation. 10. you must configure an implicit enhancement in SAP ERP. Select SAPLEINM from the popup. specify your Z or Y package. 11. and cancel purchase order information to the Ariba Network Adapter for SAP NetWeaver. Paste the copied code into the Enhancement Implementation. 7. 3. change. press Enter.. Procedure 1. Click Edit > Enhancement Operations > Show Implicit Enhancement Options to display a line after the lesen-beleg form. 9. lx_appl_idoc TYPE REF TO /arba/cx_appl_idoc. 6. Enter a name and description for the enhancement and press Enter. IF l_flag EQ c_true. In the package popup. CALL METHOD cl_purchaseorder->fill_service_line_number EXPORTING packno = ekpo-packno IMPORTING Ariba Network Adapter for SAP NetWeaver Setup Guide 92 © 2015 SAP SE or an SAP affiliate company. CREATE OBJECT cl_purchaseorder. In your SAP ERP system. ENDTRY. cl_purchaseorder TYPE REF TO /arba/cl_purchaseorder. Click Create Enhancement Implementation. CREATE OBJECT cl_po_hierarchy. 10. and save the package to a transport request. Right-click the line and select Enhancement Implementation > Create. 4. 7. 12. 9. RETURN. CONSTANTS: c_true TYPE char4 VALUE 'true'. you must configure an implicit enhancement in SAP ERP. TRY. 11. MESSAGE e151(/arba/message) RAISING error_message_received. 8. 5. CREATE OBJECT cl_po_hierarchy. navigate to transaction code SE37 . Procedure 1. Copy the following code: DATA: 1_flag(5) TYPE c. c_false(5) TYPE c VALUE 'false'.Configuring Implicit Enhancements for New Purchase Orders To enable SAP ERP to send new purchase order information to the Ariba Network Adapter for SAP NetWeaver.IDOC_OUTPUT_ORDERS and click Display. ls_idoc_status TYPE bdidocstat. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation. All rights reserved. specify your Z or Y package. 3. Configuring Integration Scenarios . Click Edit > Enhancement Operations > Show Implicit Enhancement Options to display a line after the fill_srv_orders form. Select SAPLEINM from the popup. Search for Perform fill_srv_orders. CALL METHOD cl_po_hierarchy->getsystemversion_ishierarchy EXPORTING ebeln = ekpo-ebeln et_edi_esll = edi_esll[1] IMPORTING flag = l_flag CHANGING int_edidd = int_edidd[1]. cl_po_hierarchy TYPE REF TO /arba/cl_po_hierarchy. press Enter. Double-click Perform. 2. Click Enhance in the application toolbar. CATCH /arba/cx_appl_idoc INTO lx_appl_idoc. Removing Change Order Configurations from Your Ariba Solution Ariba Network Adapter for SAP NetWeaver provides change and cancel order enhancements that no longer make use of previously existing change order configurations in your Ariba solution. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation 17. ENDIF 13. You must remove them. please have your Designated Support Contact log a service request. please have your Designated Support Contact log a service request. et_edi_esll = edi_esll[]. Activate the enhancement and save it. 18. the customizations must be migrated to your purchase order transaction instead. ENDIF 19. and an Ariba Customer Support representative will follow up to complete the request. Activate the enhancement and save it. Right-click below the last line in the fill_srv_orders form and select Enhancement Implementation > Create. 93 . To remove your previously existing change order configuration. To migrate your customizations. 16. Copy the following code: IF l_flag EQ c_true. Select the enhancement created and named in Step 10. 15. Paste the copied code into the Enhancement Implementation. All rights reserved. and an Ariba Customer Support representative will follow up to complete the request. 14. Order Confirmation Integration Scenario The Ariba Network Adapter for SAP NetWeaver supports receiving order confirmations from Ariba Network for the following: ● Confirmation or rejection of entire purchase order items that contain service line items. Migrating Change Order Customizations If you employ change and cancel order transaction customizations in your Ariba solutions. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. CALL METHOD cl_purchaseorder->create_parent_child_relation EXPORTING edi_esll = edi_esll[] CHANGING int_edidd = int_edidd[]. You can partially accept 50 units and also partially reject or back order the remaining 50 units for the line item. rejected. not at the individual service line-item level. All rights reserved. Delivery date is required at 'ConfirmationStatus' level if header level statuses are 'detail' and 'except'. Configuring Integration Scenarios . Otherwise the delivery date is determined from the corresponding PO item. rejected. ● In the cXML for an order confirmation sent from Ariba Network. For example. the delivery date is derived from the confirmationRequestt cXML.● Confirmation of orders with or without delivery dates at the header or line-level. However. see Configuring Implicit Enhancements for Comments in Order Confirmations [page 300] . You must configure the integration scenario for the Order Confirmation transaction in the Integration Directory to be able to run the transaction. ● Confirmation of orders containing line items with multiple schedule lines (delivery dates). the adapter does not support the operation = “update” and type = “allDetail”. ● A new order confirmation completely overwrites prior confirmations against a purchase order line-item. All the steps of a configuration scenario section must be completed to fully configure a scenario. ● Ariba Network Adapter for SAP NetWeaver does not support order confirmations for service purchase orders at the line-item level. ● Confirmation of orders containing partially confirmed. The SAP ERP administrator must configure the SAP ERP system to collect order confirmations for purchase orders and to support comments. ● Purchase orders containing service items may only be confirmed at the outline item level. ● Purchase orders containing a combination of service and material items may only be confirmed at the header level. For example. If a delivery date is provided in Ariba Network when creating a confirmation request. if the quantity for a line item is 100. To configure SAP ERP enhancements for comment support. ● Delivery date is always required at 'ConfirmationStatus' in the input cXML document if the header level and line level statues are 'Backordered'. Note A PO item that contains service line items can only be confirmed or rejected in its entirety. ● Only order confirmations for the purchase orders that are pulled from ERP using the OrderRequest transaction is supported. or back ordered for a line item. you can partially accept 50 units and also partially back order or reject the remaining 50 units for the line item. Ariba Network Adapter for SAP NetWeaver Setup Guide 94 © 2015 SAP SE or an SAP affiliate company. if the quantity for a line item is 100. SAP does not support header level purchase order confirmation. you cannot partially reject only 50 units for that line item. With the exception of unit price and backordered delivery date. Suppliers must resend the entire confirmation picture for the relevant purchase order line. Mapping Limitations The Order Confirmation transaction has the following mapping limitations: ● Order confirmations are stated at the purchase order line-item level only. Ariba Network Adapter for SAP NetWeaver supports order confirmations that are partially accepted. ● The IDoc fails when an order confirmation only contains partially rejected line items. purchase order line items cannot be overwritten. You must ensure that you maintain the Overdelivery Tolerance and Underdelivery Tolerance limits for the line item. and back-ordered line items. ● Comments at the header and line-item levels. Configure the Integration Scenario. Ariba Network sends the confirmation order to the SAP PI system as a ConfirmationRequest cXML document. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. and the original purchase order is updated with the confirmation information received from Ariba Network. ● Partial rejection of a line item in an order confirmation is not supported. see the “About Configuring the System Landscape Directory” [page 61] section. the integration scenario loaded into the Integration Repository when the design is imported. ● When purchase orders contains advanced pricing details. 4. 5. the unit conversion value from Ariba Network to SAP is not supported. The SAP PI system maps the ConfirmationRequest to an ORDRSP. and may or may not include line items with multiple delivery dates. In Ariba Network a supplier receives the purchase order and creates an order confirmations based on the purchase order. For more information about configuring the SLD. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. Transferring the Order Confirmation Integration Scenario Context The first step to configure the integration scenario for the Order Confirmation transaction is to transfer to the Integration Directory. A buyer creates a purchase order in the SAP ERP that may or may not include service line-items. 2. All rights reserved. SAP ERP processes the order confirmation. 3. The following steps assume that the different Business Systems are defined in the SLD. ● The cXML header-level except status for order confirmations created in Ariba Network is not supported. 3. Configure the Communication Channels. To configure the Order Confirmation: 1. The confirmation order can contain comments at the header and line-items levels. Workflow The following is a description of the end-to-end workflow for order confirmation: 1. 4. 2. Note Ensure that the design is imported into your system and ready before you run these steps. Activate the new configuration.ORDERS05 IDoc and sends it to the SAP ERP system. 95 . Full rejection of an item in an order confirmation sets the deletion flag on the item in SAP. From the SAP NetWeaver PI main page. select Tools Apply Model from ES Repository . Select Process Integration Scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide 96 © 2015 SAP SE or an SAP affiliate company. the Model Configurator window appears. Results Once the transfer is completed. Generate Configuration Objects. Assign the Model. click the Select Component View button. click the Name field. 6. In the Integration Builder menu.com/xi/ASN/OrderConfirmation ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. 5. Click Finish. and then click the Display Input Help drop down list and select Input Help.com 4. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_OrderConfirmation_Send ○ Namespace: http://ariba. 2. select Integration Directory Integration Builder . change the name of the scenario for the Integration Directory. If required. Selecting the Model for the Scenario Procedure In the Model Configurator window. All rights reserved. In the first screen of the Transfer Model from ES Repository wizard. Assign Components. About Configuring the Order Confirmation Integration Scenario Once the Integration Scenario is selected. and then click Apply to select the unique component view that is selected by default. and then login into the Configuration: Integration Builder application. 4. 3. you must configure it using the following steps: 1. Configuring Integration Scenarios . CIX of ariba. Configure Connections.Procedure 1. 3. 2. Click Continue. 3. 5. Assigning Components for the Order Confirmation Integration Scenario Procedure 1. Click on the Insert Line button ('+') to add a service entry in the table if no component entry line is present. 7. All rights reserved. 2. you must assign components to the application components of the selected integration scenario. Click the Next Role button (the right arrow) to go to the next screen in the window. Select the communication component name BS_SAPR3_50 from the selection list and click Apply. then click on the Value List drop down and select Value List <F4. In the Assign Components window. You must assign Communication Channels to set up the connections. then click on the Value List drop down and select Value List <F4. 4. In the Model Configurator. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. you must activate sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. 97 . For Multi ERP implementation add the multiple business services defined for your multiple SAP R/3 systems by repeating the steps 3 and 4. select Configure Connections. Next Steps After assigning services. Click on the row under the Communication Component column. Click on the row under the Communication Component. 8.Next Steps After selecting the component view. Select the communication component name BS_ASN from the selection list and click Apply. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. Click the Save Settings button to save the changes. In the Model Configurator. Configuring Connections for the Order Confirmation Integration Scenario Procedure 1. 6. select the Business System Components for A2A tab to assign components for Ariba Network. click the Assign Component button. you must generate the objects. and 7 for all the entries of the Business Systems corresponding to your SAP ERP instances. If they do already exist. Click Continue. Click the Save Settings button to save the changes. 5. they will be reused and enhanced. repeat the steps 6. Configuring Integration Scenarios . and then click OK in the dialog box. 9. see the “Creating Communication Channels for R/3” [page 68] section. Select the following Communication Channel Template: ○ Name: CCT_OrderConfirmation_cXML_Sender ○ Namespace: http://ariba.com/xi/ASN/OrderConfirmation ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. you can create the communication channel by copy from a channel already configured. if required. The IDoc receiver Communication Channel needs to be created once for each Business System corresponding to your SAP R3 instance. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. click the empty Communication Channel cell corresponding to BS_ASN in the Sender Business System Components table. Click the Activate All Connections button. Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction. Generation creates the configuration objects if they do not yet exist. you can create the communication channel by copy from a channel already configured. In the Connections from Component Assignment tab in the Configure Connection window. 3. Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction. Ariba Network Adapter for SAP NetWeaver Setup Guide 98 © 2015 SAP SE or an SAP affiliate company. If a Communication Channel already exists you need to use it. All rights reserved. 7. CIX of ariba. 6. 4. For more information about how to create the IDoc receiver Communication Channel. then click the Display Input Help drop down list and select Input Help. Generating Objects for the Order Confirmation Integration Scenario Context After making all the configuration settings in the wizard.2. In the Connections from Component Assignment tab in the Configure Connection window. Click Continue.com. Click the New Communication Channel button (the icon at the top left). and then click Finish. 8. You can also simulate generation for test purposes. and in the next page click the Name field. click the empty Communication Channel cell corresponding to BS_SAPR3_50 in the Receiver Business System Components table. For Multi ERP implementation. modify the channel name to CC_OrderConfirmation_cXML_Sender. Select the communication channel CC_IDoc_Receiver corresponding to the SAP R/3 Business System from the selection list. 4. 3. After the object generation is complete. edit the other parameters. Close the log that is created without saving. 2. 5. For more information about the cXML Adapter parameters see cXML Adapter Parameters [page 391]. Interface Determination. Click Start to begin generating objects. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. click the Create Configuration Object button. In the Parameters tab. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 99 .Procedure 1. Under Communication Channel. Note If you created the channel by copy from an existing channel. and Sender/Receiver Agreement. click Apply to save the new configuration settings. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. If required. make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select all the check boxes – Receiver Determination. In the Model Configurator. 3. All rights reserved. you need to change the request type to ConfirmationRequest in the Inbound Request Type field. You can save it. double-click |BS_ASN|CC_OrderConfirmation_cXML_Sender to open it. In the Create Configuration Object window. Configuring Communication Channels for the Order Confirmation Integration Scenario Context Configure the communication channel CC_OrderConfirmation_cXML_Sender under the AR_OrderConfirmation_Send Configuration Scenario: Procedure 1. 2. Save the changes. or right-click and select Open. if required. specify the left operand of the condition as follows: ○ Click on the icon next to the Left Operand field to open the Expression Editor. Expand Receiver Determination. Click on the icon next to the Condition field. ○ You cannot select a node having child nodes or attributes. and then select the following xpath from the document tree: /cXML/ Header/To/Credential/@domain. Retain the default settings for the other receivers. Click on OK to close the Condition Editor. ○ This path should be displayed in the XPath Expression field. ○ Select the XPath option. (The Boolean operator between the two conditions should be “AND”. ○ Click OK to return to the Expression Editor. All rights reserved. ○ Select the Right Operand field and specify the Logical System Name corresponding to the Business System for which you are doing the configuration. 6.Configuring Receiver Determination Settings for the Order Confirmation Integration Scenario Context Configure the receiver determination settings manually. 4. In the Condition Editor window. ○ Select the Right Operand field and enter “SystemID”. for the receiver MIOut_Async_OrderConfirmation_cXML under the AR_OrderConfirmation_Send integration scenario. ○ Select the XPath option. ○ Select the “=” operator in the Operator column. ○ This path should be displayed in the XPath Expression field. Configuring Integration Scenarios . Note This configuration is required only for Multi-ERP implementations. ○ Select the “=” operator in the Operator column. 2. In the Configured Receivers section of the Edit Receiver Determination window.g. ○ Click on OK to return to the Expression Editor. Add another condition by clicking on the Insert Expression option. E. T90CLNT090. 5.) ○ Click on the icon next to the Left Operand field to open the Expression Editor. You must first select the child node or attribute and edit the xpath expression in the XPath Expression field to remove the child element. Procedure 1. 3. click the Add button to add a new line. Ariba Network Adapter for SAP NetWeaver Setup Guide 100 © 2015 SAP SE or an SAP affiliate company. directly from the tree. and then click |BS_ASN | MIOut_Async_OrderConfirmation_cXML. and then select the following xpath from the document tree: /cXML/ Header/To/Credential/Identity. to start the Condition Editor. All rights reserved. In the Receiver Interfaces section of the Edit Interface Determination window. 5.ORDERS05 | | BS_ASN. 4. Procedure 1.. repeat the steps 2 to 7 for all your SAP ERP instances. Activating the Order Confirmation Integration Scenario Procedure Using the Change List tab on the main application screen. 2. click the operation mapping value under the Operation Mapping column. Configuring Interface Determination Settings for the Order Confirmation Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. 101 . Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. and then click |BS_SAPR3_50 | ORDRSP. Save the Receiver Determination settings. Save the interface determination settings. 3. and select the Communication Component corresponding to the Logical System Name you specified in the Condition. 7. Click on the icon next to the Communication Component field to start the Choose Communication Component window. The Multiplicity column displays the value "0.unbounded". then click the Value List drop down and select Value List. activate all the Change Lists containing the objects created and modified during the scenario setup. Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings. 8. Note For Multi ERP implementation. Select the operation mapping IFM_cXML_2_ORDRSP_ORDERS05 and click Apply. Expand Interface Determination. you must apply SAP Notes. see the “About Configuring the System Landscape Directory” [page 61] section. For more information about configuring the SLD. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. to ensure that the IDOC is able to post the data to SAP ERP system. if the supplier changed the unit price and delivery date. Workflow Note Ensure that the design is imported into your system and ready before you run these steps. ● Delivery Date is required ● Only shipment notices for the Purchase Orders that are pulled from SAP using OrderRequest transaction are supported for this release. Ship Notice Integration Scenario You must configure the integration scenario for the Ship Notice transaction in the Integration Directory to be able to run the transaction.Results This completes the configuration of the Order Confirmation transaction in SAP NetWeaver PI. Mapping Limitations The Ship Notice transaction has the following mapping limitations: ● Only the 'new' operation is supported. The following steps assume that the different Business Systems are defined in the SLD. Configuring Integration Scenarios . ● To ensure no error is reported when order confirmations with rejected line items are posted to SAP ERP. All the steps of a configuration scenario section must be completed to fully configure a scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide 102 © 2015 SAP SE or an SAP affiliate company. 109273 and 456127. To configure the Ship Notice: 1. All rights reserved. you must apply SAP Note 890812 on your SAP ERP system. Additional Configuration Tasks for the Order Confirmation Integration Scenario ● In an Order Confirmation. 'update' and 'delete' operations are not supported. CIX of ariba. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_AdvanceShipNotice_Send ○ Namespace: http://ariba. 3. Click on Finish. Configure the Communication Channels. and then login into the Configuration: Integration Builder application. 2. click the Name field. 103 . 3. Procedure 1. Transferring the Ship Notice Integration Scenario Context The first step to configure the integration scenario for the Ship Notice transaction is to transfer to the Integration Directory. About Configuring the Ship Notice Integration Scenario Once the Integration Scenario is selected.com. Click on Continue. select Tools Apply Model from ES Repository . you must configure it using the following sequence of steps: 1. and then click the Display Input Help drop down list and select Input Help. 2. the Model Configurator window appears. Configure the Integration Scenario. Activate the new configuration. All rights reserved. From the SAP NetWeaver PI main page. Assign Components. 4. If required. the integration scenario loaded into the Integration Repository when the design is imported. 4. 2.com/xi/ASN/AdvanceShipNotice ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. Select Process Integration Scenario. change the name of the scenario for the Integration Directory 6. In the Integration Builder menu. Configure Connections. Assign the Model. select Integration Directory Integration Builder . Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 5. 3. In the first screen of the Transfer Model from ES Repository wizard. Results Once the transfer is completed. then click on the Value List drop down and select Value List <F4>. 3. click the Assign Component button. you must assign components to the application components of the selected integration scenario. Click on the Insert Line button ('+') to add a service entry in the table 7. Click on the row under the Communication Component column. Generate Configuration Objects. 6. 4.4. Ariba Network Adapter for SAP NetWeaver Setup Guide 104 © 2015 SAP SE or an SAP affiliate company. Select the communication component name BS_ASN from the selection list and click Apply. 5. then click on the Value List drop down and select Value List <F4>. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. For Multi ERP implementation add the multiple business services defined for your multiple SAP R/3 systems by repeating the steps 6 and 7. In the Model Configurator. and then click Apply to select the unique component view that is selected by default. All rights reserved. select the Business System Components for A2A tab to assign components for Ariba Network. Next Steps After selecting the component view. 2. Click the Save Settings button to save the changes. 8. Selecting the Model for the Scenario Procedure In the Model Configurator window. Click the Next Role button (the right arrow) to go to the next screen in the window. Click on the row under the Communication Component column. Select the communication component name BS_SAPR3_50 from the selection list and click Apply. Configuring Integration Scenarios . Assigning Components for the Ship Notice Integration Scenario Procedure 1. click the Select Component View button. In the Assign Components window. modify the channel name to CC_AdvanceShipNotice_cXML_Sender. click the empty Communication Channel cell corresponding to BS_SAPR3_50 in the Receiver Business System Components table. and 7 for all the entries of the Business Systems corresponding to your SAP ERP instances. For more information about how to create the IDoc receiver Communication Channel. Click the New Communication Channel button (the icon at the top left). In the Connections from Component Assignment tab in the Configure Connection window. repeat the steps 6. Click Continue. then click the Display Input Help drop down list and select Input Help. Configuring Connections for the Ship Notice Integration Scenario Procedure 1. Click Continue. Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction. Select the following Communication Channel Template: ○ Name: CCT_AdvanceShipNotice_cXML_Sender ○ Namespace: http://ariba. 5.com/xi/ASN/AdvanceShipNotice ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. see the “Creating Communication Channels for R/3” [page 68] section. you must activate sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. click the empty Communication Channel cell corresponding to BS_ASN in the Sender Business System Components table. 4. In the Connections from Component Assignment tab in the Configure Connection window. All rights reserved. you can create the communication channel by copy from a channel already configured.Next Steps After assigning services. If a Communication Channel already exists you need to use it. For Multi ERP implementation. 7. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. and then click Finish. The IDoc receiver Communication Channel needs to be created once for each Business System corresponding to your SAP ERP. 2. 105 . 8. CIX of ariba. You must assign Communication Channels to set up the connections. Click on Apply to save the changes. In the Model Configurator.com. and in the next page click the Name field. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 3. Note The communication channels for SAP ERP Sender system are not required. click the Configure Connections button. Select the communication channel CC_IDoc_Receiver corresponding to the SAP ERP Business System from the selection list. 6. In the Model Configurator. you must generate the objects. if required. double-click |BS_ASN|CC_AdvanceShipNotice_cXML_Sender to open it. Interface Determination. click the Create Configuration Object button. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. close the wizard and click Apply in the pop up window. If they do already exist. Configuring Integration Scenarios . 2. Procedure 1. Under Communication Channel. they will be reused and enhanced. Note If you created the channel by copy from an existing channel. 3.Generating Objects for the Ship Notice Integration Scenario Context After making all the configuration settings in the wizard. you need to change the request type to ShipmentNoticeRequest in the Inbound Request Type field. Click Start to begin generating objects. After the object generation is complete. You can also simulate generation for test purposes. Ariba Network Adapter for SAP NetWeaver Setup Guide 106 © 2015 SAP SE or an SAP affiliate company. 2. Configuring Communication Channels for the Ship Notice Integration Scenario Context Configure the communication channel CC_AdvanceShipNotice_cXML_Sender under the AR_AdvanceShipNotice_Send Configuration Scenario: Procedure 1. 5. Close the log that is created without saving. Generation creates the configuration objects if they do not yet exist. to save the new configuration settings. make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select all the check boxes – Receiver Determination. 4. or right-click and select Open. All rights reserved. You can save it. In the Create Configuration Object window. and Sender/Receiver Agreement. In the Parameters tab. if required. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. ○ Select the Right Operand field and enter “SystemID”. Add another condition by clicking on the Insert Expression option. Procedure 1. for the receiver MIOut_Async_AdvanceShipNotice_cXML under the AR_AdvanceShipNotice_Send integration scenario. Retain the default settings for the other receivers.) ○ Click on the icon next to the Left Operand field to open the Expression Editor. Expand Receiver Determination.If required. 2. ○ Select the XPath option. 5. ○ Click OK to return to the Expression Editor. ○ Select the XPath option. Configuring Receiver Determination Settings for the Ship Notice Integration Scenario Context Configure the receiver determination settings manually. ○ Select the “=” operator in the Operator column. Note This configuration is required only for Multi-ERP implementations. All rights reserved. and then click |BS_ASN | MIOut_Async_AdvanceShipNotice_cXML. You must first select the child node or attribute and edit the xpath expression in the XPath Expression field to remove the child element. In the Condition Editor window. directly from the tree. 3. specify the left operand of the condition as follows: ○ Click on the icon next to the Left Operand field to open the Expression Editor. Click on the icon next to the Condition field. For more information about the cXML Adapter parameters. 4. 107 . ○ This path should be displayed in the XPath Expression field. and then select the following xpath from the document tree: /cXML/ Header/To/Credential/Identity. ○ You cannot select a node having child nodes or attributes. (The Boolean operator between the two conditions should be “AND”. see cXML Adapter Parameters [page 391]. click the Add button to add a new line. 3. adapt the other parameters. In the Configured Receivers section of the Edit Receiver Determination window. to start the Condition Editor. and then select the following xpath from the document tree: /cXML/ Header/To/Credential/@domain. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. ○ This path should be displayed in the XPath Expression field. Save the changes. Procedure 1. 6.g. then click the Value List drop down and select Value List. Configuring Interface Determination Settings for the Ship Notice Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. Save the Receiver Determination settings. 4. Configuring Integration Scenarios . The Multiplicity column displays the value "0. and then click |BS_SAPR3_50 | DESADV. Expand Interface Determination. In the Receiver Interfaces section of the Edit Interface Determination window. 5. Select the operation mapping IFM_cXML_2_DESADV_DESADV01 and click Apply. Click on OK to close the Condition Editor. 3. Click on the icon next to the Communication Component field to start the Choose Communication Component window. Note For Multi ERP implementation. Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings. 7..DESADV01 | | BS_ASN. ○ Select the “=” operator in the Operator column. Save the interface determination settings. E. click the operation mapping value under the Operation Mapping column. ○ Select the Right Operand field and specify the Logical System Name corresponding to the Business System for which you are doing the configuration. ○ Click on OK to return to the Expression Editor. repeat the steps 2 to 7 for all your SAP ERP instances. T90CLNT090.unbounded". and select the Communication Component corresponding to the Logical System Name you specified in the Condition. 8. 2. All rights reserved. Ariba Network Adapter for SAP NetWeaver Setup Guide 108 © 2015 SAP SE or an SAP affiliate company. You must download and import the necessary mapping changes in your SAP PI system. For more information. Limitations Ariba Network Adapter for SAP NetWeaver does not support ship notices against non-POs. You must also configure your SAP R/3 system to accept ship notices against multiple POs. Ship Notice Integration Scenario to Support Creation of a Single Ship Notice Against Multiple Purchase Orders You can receive a single ship notice against multiple purchase orders (POs) on your SAP ERP system. 109 . activate all the Change Lists containing the objects created and modified during the scenario setup.Activating the Ship Notice Integration Scenario Procedure Using the Change List tab on the main application screen. see Configuring Ship Notices Against Multiple Purchase Orders [page 313].com/xi/ASN/AdvanceShipNotice_DELVRY06 supports ship notices for multiple purchase orders. you must delete the existing configuration scenario using the old namespace http://ariba. You can receive ship notices with the following from Ariba Network suppliers: ● A single ship notice against multiple POs ● Multiple ship notices against a single or multiple line items in a PO ● Ship notices against POs having line items with zero quantity to indicate the items are not shipped ● Ship notices against a PO having material line-items ● Ship notices against POs having the BatchID for the line items The namespace http://ariba.com/xi/ASN/AdvanceShipNotice and reconfigure the Configuration scenario with the new model for the namespace 'http://ariba. Results The Ship Notice transaction is now ready for execution.com/xi/ASN/ AdvanceShipNotice_DELVRY06'. All rights reserved. Note If you are an existing customer and want to use this feature. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. Activate the integration scenario. For more information. For more information. If you are using customized business processes. Configure the Interface Determination. Configure to receive ship notices with zero quantities. see Transferring the Ship Notice Integration Scenario for Multiple POs [page 111]. For more information. you must also configure you SAP ERP system to specify the ‘No dialog’ option in the Checks for zero quantity page. Transfer the Integration Scenario from the Integration Repository Enterprise Service Builder to the Integration Directory Integration Builder . you must configure the following second PI mapping: ‘MM_Custom_CDF_FulFill_XSD_AdvanceShipNotice_2_DESADV_DELVRY06’. see About Configuring the Ship Notice Integration Scenario for Multiple POs [page 112]. For more information. Workflow Configuring the ship notice integration scenario to support multiple POs involves the following steps: 1. 5. All rights reserved. Configuring Integration Scenarios . Configure the Communication Channels. Configure the Integration Scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide 110 © 2015 SAP SE or an SAP affiliate company. 4. see Configuring Communication Channels for the Ship Notice Integration Scenario with Multiple POs [page 114]. see Activating the Ship Notice Integration Scenario for Multiple POs [page 117]. 3. see Configuring the Ship Notice Integration Scenario to Receive Ship Notices with Zero Quantities [page 117]. see Configuring Interface Determination Settings for the Ship Notice Integration Scenario with Multiple POs [page 116]. For more information. see Configuring the Ship Notice Integration Scenario to Receive Ship Notices with Zero Quantities [page 117]. For more information. 6. 2. For more information.To receive ship notices with zero quantities. com/xi/ASN/AdvanceShipNotice_DELVRY06 ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba. The following steps assume that the different Business Systems are defined in the SLD. ○ If you are an existing customer. the Model Configurator window appears. The integration scenario is loaded into the Integration Repository when the design package is imported. 4. click the Name field. Transferring the Ship Notice Integration Scenario for Multiple POs Context The first step to configure the integration scenario to support multiple purchase orders is to configure the existing Ship Notice transaction and transfer the integration scenario to the Integration Builder. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. and then login into the Configuration: Integration Builder application. If required. Click Finish. change the name of the scenario for the Integration Directory 6.com. Results Once the integration scenario transfer is completed. In the Integration Builder menu. 5. and then click the Display Input Help pull-down menu and select Input Help. 3. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_AdvanceShipNotice_DELVERY06_Send ○ Namespace: http://ariba. Note ○ Ensure that the design package is imported into your system and ready before you run these steps. 2. Procedure 1. select Integration Directory Integration Builder . select Tools Apply Model from ES Repository . you must delete the existing Configuration scenario and rerun the steps for the configuration scenario. Click Continue. All rights reserved. 111 . From the SAP NetWeaver PI main page. In the first screen of the Transfer Model from ES Repository wizard > Select Process Integration Scenario. ○ All the steps of a configuration scenario section must be completed to fully configure a scenario. 2. assign components to the application components for the selected integration scenario. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is available. click the Assign Component button. In the Model Configurator. 4. select the Business System Components for A2A tab to assign components for Ariba Network. 5. and then click Apply to select the unique model that is selected by default. 8. Select the communication component name of the business system for your SAP ERP system from the selection list and click Apply. add the multiple business services defined for your multiple SAP ERP systems by repeating the Step# 6 and 7. In the Assign Components window. Assigning the components. Click the Next Role button (the right arrow) to go to the next screen in the window. 6. In the Model Configurator window. Click the Insert Line button ('+') to add a service entry in the table. All rights reserved. 7. If you have multiple ERP systems.About Configuring the Ship Notice Integration Scenario for Multiple POs Configuring the Integration Scenario involves the following steps: 1. Assigning Components for the Ship Notice Integration Scenario with Multiple POs Procedure 1. Click the row under the Communication Component column. Select the communication component name of the business system for Ariba Network from the selection list and click Apply. Configuring Integration Scenarios . click the Select Component View button. 3. Selecting the model. Ariba Network Adapter for SAP NetWeaver Setup Guide 112 © 2015 SAP SE or an SAP affiliate company. then click the Value List pull-down menu and select Value List <F4. Selecting the Model for the Ship Notice Integration Scenario with Multiple POs Procedure 1. then click the Value List pull-down menu and select Value List <F4>. 2. 4. Click the row under the Communication Component column. Generating the configuration objects. After selecting the model. Click the Save Settings button. Configuring the sender and receiver relations for individual connections. 3. 2. Select the communication channel CC_IDoc_Receiver corresponding to the SAP ERP Business System from the selection list. 2. You must assign Communication Channels to set up the connections. If you have multiple ERP systems. If a Communication Channel already exists. you can continue to use it. On the next page. Note The communication channels for SAP ERP Sender system are not required. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. In the Connections from Component Assignment tab in the Configure Connection window. Click Continue. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. 9. 3. Click the New Communication Channel button (the icon at the top left). Tip If you have already created and configured a Receiver channel name for the business system in Ariba Network for another transaction. In the Model Configurator. Click Continue. click the Name field and then click the Display Input Help pull-down menu and select Input Help. All rights reserved. 8. 6.com/xi/ASN/AdvanceShipNotice_DELVRY06 ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba. 7. modify the channel name to CC_AdvanceShipNotice_cXML_Sender. click the empty Communication Channel cell corresponding to the name of the business system of your SAP R/3 system in the Receiver Business System Components table. 4. 5. click the empty Communication Channel cell corresponding to name of the business system for Ariba Network in the Sender Business System Components table. Select the following Communication Channel Template: ○ Name: CCT_AdvanceShipNotice_DELVRY06_cXML_Sender ○ Namespace: http://ariba. 113 .com. Click Apply to save the changes. you can create the communication channel by copying from a channel that has already been configured. The IDoc receiver Communication Channel needs to be created once for each Business System corresponding to your SAP ERP. and then click Finish. repeat Step# 6 and 7 for all the entries of the Business Systems corresponding to your SAP ERP instances. In the Connections from Component Assignment tab in the Configure Connection window. click the Configure Connections button.Configuring Sender and Receiver Relations for Individual Connections for the Ship Notice Integration Scenario with Multiple POs Procedure 1. 2. do the following: ○ Click Generation in the General section. 4. 5. click Apply to save the new configuration settings. Close the log that is created without saving. edit the other parameters. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. if required. Configuring Integration Scenarios . Ariba Network Adapter for SAP NetWeaver Setup Guide 114 © 2015 SAP SE or an SAP affiliate company. if required. The text box already contains an object name that you can use or modify. double-click |< Name of the Business System for Ariba Network | CC_AdvanceShipNotice_cXML_Sender to open it. You can save it. ○ Select the Receiver Determination and Interface Determination check boxes in the Scope of Generation section. In the Communication Channel list. Click Start to begin generating objects. Configuring Communication Channels for the Ship Notice Integration Scenario with Multiple POs Context Configure the communication channel CC_AdvanceShipNotice_cXML_Sender under the AR_AdvanceShipNotice_DELVRY06 Configuration Scenario: Procedure 1. click the Create Configuration Object button. In the Parameters tab. If they already exist. You can also simulate generation for test purpose Procedure 1. In the Model Configurator. If required. 2. All rights reserved. they are reused and enhanced.Generating Objects for the Ship Notice Integration Scenario with Multiple POs Context Generating the objects creates the configuration objects if they do not yet exist. Select Create New in the Change List for Generated Objects section. 3. In the Create Configuration Objects dialog box. After the object generation is complete. click the Add button to add a new line. you must change the request type to ShipmentNoticeRequest in the Inbound Request Type field. ○ Click the icon next to the Left Operand field to open the Expression Editor. ○ Select the XPath option. to start the Condition Editor. Procedure 1. ○ This path should be displayed in the XPath Expression field.2. 115 . All rights reserved. ○ Select the “=” operator in the Operator column. Retain the default settings for the other receivers. ○ Select the Right Operand field and enter “SystemID”. 4. Expand Receiver Determination.025 version. 5. Add another condition by clicking on the Insert Expression option. Note If you created the channel by copying from an existing channel. ○ Click OK to return to the Expression Editor. ○ Select the XPath option. In the Condition Editor window. In the Configured Receivers section of the Edit Receiver Determination window. 3. and then select the following Xpath from the document tree: /cXML/ Header/To/Credential/@domain. Note This configuration is required only if you have multiple ERP systems. and then click |< Name of the Business System for Ariba Network | MIOut_Async_AdvanceShipNotice_cXML . Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. and then select the following xpath from the document tree: /cXML/ Header/To/Credential/Identity. 4. The Boolean operator between the two conditions should be “AND”. for the receiver MIOut_Async_AdvanceShipNotice_cXML under the AR_AdvanceShipNotice_DELVRY_06_Send integration scenario. Configuring Receiver Determination Settings for the Ship Notice Integration Scenario with Multiple POs Context Configure the receiver determination settings manually. Update the cXML version parameter to the 1. 2. Click the icon next to the Condition field. Save and activate the changes. 3. specify the left operand of the condition as follows: ○ Click the icon next to the Left Operand field to open the Expression Editor. Procedure 1. Click OK to close the Condition Editor. repeat the Step# 2 to 7 for all your SAP ERP instances.unbounded". T90CLNT090. ○ Select the Right Operand field and specify the Logical System Name corresponding to the Business System for which you are doing the configuration. 2. ○ Click OK to return to the Expression Editor. Note If you have multiple ERP systems. In the Receiver Interfaces section of the Edit Interface Determination window. Configuring Interface Determination Settings for the Ship Notice Integration Scenario with Multiple POs Context Configure the interface determination settings to enable mapping enhancements.. All rights reserved. and select the Communication Component corresponding to the Logical System Name you specified in the Condition. 4. Note Configuring the Interface Determination is a mandatory step if you must configure the mappings. directly from the tree. Click the icon next to the Communication Component field to start the Choose Communication Component window.DELVRY06 | | < Name of the Business System for Ariba Network . ○ This path should be displayed in the XPath Expression field. 6. ○ You cannot select a node having child nodes or attributes. 3. Configuring Integration Scenarios . For example. 8. 7. You must first select the child node or attribute and edit the Xpath expression in the XPath Expression field to remove the child element. Save the Receiver Determination settings. Save and activate the interface determination settings. click the operation mapping value under the Operation Mapping column. and then click |< Name of the Business System for SAP ERP | DESADV. Select the operation mapping IFM_cXML_2_DESADV_DELVRY06 and click Apply. Ariba Network Adapter for SAP NetWeaver Setup Guide 116 © 2015 SAP SE or an SAP affiliate company. 5. The Multiplicity column displays the value "0. then click the Value List pull-down menu and select Value List. Expand Interface Determination. ○ Select the “=” operator in the Operator column. Results This completes the configuration of the Ship Notice transaction. activate all the change lists containing the objects created and modified during the scenario setup. Click Position and then enter “ELN” as the Item category. Note Ensure that the Design package is imported into your system and ready before you run these steps. All rights reserved. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. To configure the service sheet transaction: 1. 2. 2. 4. 117 . Double-click the Item category “ELN”. see About Configuring the System Landscape Directory [page 61]. Service Sheet and Service Sheet Response Integration Scenario You need to configure the integration scenario for the Service Sheet transaction in the Integration Directory to be able to run the transaction. Go to the transaction code “0vlp”. Transfer the Integration Scenario from the Integration Repository to the Integration Directory.Activating the Ship Notice Integration Scenario for Multiple POs Procedure Using the Change List tab on the main application screen. Configuring the Ship Notice Integration Scenario to Receive Ship Notices with Zero Quantities Procedure 1. Select the No dialog option. The following steps assume that the different Business Systems are defined in the SLD. 3. For more information about configuring the SLD. The Checks for zero quantity window appears. Configure the Integration Scenario. Select the following Process Integration Scenario from the Enterprise Services Repository screen for the Service Sheet transaction: ○ Name: AR_ServiceEntrySheet_Send ○ Namespace: http://ariba. Activate the new configuration. In the first screen of the Transfer Model from ES Repository wizard. Transferring Service Sheet and Service Sheet Response Scenarios Context The first step to configure the integration scenario for the service sheet and service sheet response transactions is to transfer to the Integration Directory. select Integration Directory Integration Builder . change the name of the scenario for the Integration Directory 6. 7. 4. select Tools Apply Model from ES Repository . In the Integration Builder menu. 3. Click Finish.3. Results After the transfer is completed. Configure the Communication Channels. then click the Display Input Help drop down list and select Input Help. Select Process Integration Scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide 118 © 2015 SAP SE or an SAP affiliate company.com/xi/ASN/ServiceEntrySheet ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba. Click Continue.com 4. and then login into the Configuration: Integration Builder application. If required. Click Close. 5. the integration scenario loaded into the Integration Repository when the Design package is imported. the Model Configurator window appears.com Select the following Process Integration Scenario from the Enterprise Services Repository screen for the Service Sheet Response transaction: ○ Name: AR_ServiceEntrySheetResponse_ReceiveProxy ○ Namespace: http://ariba.com/xi/ASN/ServiceEntrySheetResponseProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba. click the Name field. All rights reserved. 2. From the SAP NetWeaver PI main page. Configuring Integration Scenarios . Procedure 1. select the Business System Components for A2A tab to assign business systems for the integration scenario. All rights reserved. 4. 4. Click on the row under the Communication Component column. 3. Select the communication component name BS_BS_ERPERFLNX1 (sample value) from the selection list and click Apply.About Configuring the Service Sheet and Service Sheet Response Integration Scenarios Once the Integration Scenario is selected. Assign the Model. click the Select Component View button. click the Assign Component button. 3. Configure Connections. 2. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. Generate Configuration Objects. then click on the Value List drop down and select Value List <F4>. Assign Components. In the Model Configurator. Note For Multi ERP implementation. In the Assign Components window. 119 . you must assign components to the application components of the selected integration scenario. Assigning Components for the Service Sheet and Service Sheet Response Integration Scenarios Procedure 1. you must configure it using the following steps: 1. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. Selecting the Model for the Scenario Procedure In the Model Configurator window. add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4. Next Steps After selecting the component view. 2. and then click Apply to select the unique component view that is selected by default. Click Continue. and then click Finish. 4. from the selection list and click Apply. click the empty Communication Channel cell corresponding to < Name of the Business System for Ariba Network> in the Sender Business System Components table.com Select the following Communication Channel Template for the Service Sheet Response transaction: ○ Name: CCT_ServiceEntrySheetResponseProxy_cXML_Receiver ○ Namespace: http://ariba. Configuring Integration Scenarios . You must assign Communication Channels to set up the connections. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is present. click the Configure Connections button.com 5. Select the following Communication Channel Template for the Service Sheet transaction: ○ Name: CCT_ServiceEntrySheet_cXML_Sender ○ Namespace: http://ariba. Tip If you have already created and configured a Receiver channel for <Name of the Business System for Ariba Network>| for another transaction. Select the communication component name BS_ASN (sample value). you must define sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. Configuring Connections for the Service Sheet and Service Sheet Response Integration Scenarios Procedure 1. 7. Ariba Network Adapter for SAP NetWeaver Setup Guide 120 © 2015 SAP SE or an SAP affiliate company. 6. Click on the row under the Communication Component column. In the Connections from Component Assignment tab. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. modify the channel names to CC_ServiceEntrySheet_cXML_Sender and CC_ServiceEntrySheetResponseProxy_cXML_Receiver. Click the Next Application Component button (the right arrow) to go to the next screen in the window. Click the New Communication Channel button (the icon at the top left). then click the Display Input Help drop down list and select Input Help. Click Continue.com/xi/ASN/ServiceEntrySheetResponseProxy ○ Software Component Version: ARBA_SUPPLIER_CONN_ADAPT CIx of ariba. 8.com/xi/ASN/ServiceEntrySheet ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba. and in the next page click the Name field. In the Model Configurator. All rights reserved. 3. you can create the communication channel by copying from an already configured channel. 2. Next Steps After assigning components.5. then click on the Value List drop down and select Value List <F4>. Click the Save Settings button to save the changes. select the Generation option. After the object generation is complete. 6. 8. make the following settings: ○ Under General. Click Apply to save the new configuration settings. and Interface Determination. 4. you must generate the objects. All rights reserved. if required. Select the CC_Proxy_Receiver communication channel from the selection list and click Apply. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. In the Create Configuration Objects window. if required. 7. You can save it. Click on the Value List drop down and select Value List <F4>. 6. click the empty Communication Channel cell corresponding to BS_ERPERFLNX1 in the Receiver Business System Components table. close the log that is created without saving. 2. 3. and then click OK in the dialog box. In the Connections from Component Assignment tab. In the Model Configurator. Configuring Communication Channels for the Service Sheet and Service Sheet Response Integration Scenarios Context Configure the communication channels CCT_ServiceEntrySheet_cXML_Sender and CCT_ServiceEntrySheetResponseProxy_cXML_Receiver under the AR_ServiceEntrySheet_Send and AR_ServiceEntrySheetResponse_ReceiveProxy Configuration Scenarios respectively. ○ Scope of Generation: Select both the active check boxes – Receiver Determination. Generating Objects for the Service Sheet and Service Sheet Response Integration Scenarios Context After making all the configuration settings in the wizard. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. 9. Click the Activate All Connections button. Procedure 1. 121 . Click on Start to begin generating objects. 5. they will be reused and enhanced. You can also simulate generation for test purposes. Generation creates the configuration objects if they do not yet exist. click the Create Configuration Object button. Click the Save Settings button to save the changes. If they do already exist. In the Objects tab on the right side. Note For the cXML Version parameter. To ensure that attachments in service sheets are processed by the adapter and sent to SAP ERP. All rights reserved. enter 1. Activating the Service Sheet and Service Sheet Response Integration Scenarios Procedure Using the Change List tab on the main application screen. 3.2. in the communication channel for the service sheet transaction.Procedure 1. activate all the Change Lists containing the objects created and modified during the component setup. Ariba Network Adapter for SAP NetWeaver Setup Guide 122 © 2015 SAP SE or an SAP affiliate company. set the parameters in the Authentication section to match your Ariba Network buyer account configuration. <|Name of the Business System for Ariba Network>|<| CCT_ServiceEntrySheetResponseProxy_cXML_Receiver 2. Configuring Integration Scenarios . you need to change the request type to ServiceEntryRequest in the Inbound Request Type field. Save the changes. or right-click and select Open: Service Sheet 1. Note If you created the channel by copying an existing channel. 4.025 or higher for service sheet and service sheet response transactions respectively. <|Name of the Business System for Ariba Network>|<|CCT_ServiceEntrySheet_cXML_Sender Service Sheet Response 1. In the Parameters tab. you must select Embedded in cXML option for the Attachment Processing Mode parameter. Specify values for the other parameters as required. Results This completes the configuration of the service sheet and service sheet response transactions in SAP NetWeaver PI. double-click the following to open it. and HST tax rates. If the tax information is not provided then the IDOC posting fails with the error “Enter a tax code in item.” ● The tax segments at the header and line-item level in the IDOC must be equal to the number of tax segments available in the cXML file. when an Invoice IDOC is sent to ERP. When no tax is applicable to the invoice line. it does a look up to transaction OBCD and based on the partner. Recommendations When you receive invoices from suppliers with the PST. All rights reserved. Ariba Network Adapter for SAP NetWeaver recommends the following: ● When suppliers create an invoice on Ariba Network.Invoice Integration Scenario You must configure the integration scenario for the Invoice transaction in the Integration Directory to be able to run the transaction. Mapping Limitations The Invoice transaction has the following mapping limitations: ● Invoice ID must be unique for a supplier ○ 'Standard' type invoices and credit memos are supported ○ Only 'standard' type invoices for the Purchase Orders that are pulled from ERP using OrderRequest transaction are supported for this release. ● It is mandatory to maintain the tax type and tax rate for a partner in the OBCD transaction. and tax rate. All the steps of a configuration scenario section must be completed to fully configure a scenario. tax type. and gets the right tax code to be used for invoice posting. GST. 123 . ● The following information is not supported: ○ Header Invoice (debit memo) ○ Information Only Invoice ○ Cancel/Delete Invoice ○ Payment Terms ○ Subsequent Credit ○ Period information ○ Deposit amount ○ Tax: 'VAT recoverable' feature Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. a zero percent tax should be entered. it is mandatory to enter the tax information. QST. For both the header and line-item level tax. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_Invoice_Invoic02 ○ Namespace: http://ariba. select the Integration Directory Integration Builder . 4. 3. Click Continue. 5.Workflow Note Ensure that the design is imported into your system and ready before you run these steps. 4. Transferring the Invoice Integration Scenario Context The first step to configure the integration scenario for the Invoice transaction is to transfer to the Integration Directory. Configure the Communication Channels. For more information about configuring the SLD.com. and then login into Configuration: Integration Builder application. change the name of the scenario for the Integration Directory 6. In the first screen of the Transfer Model from ES Repository wizard. Procedure 1. 2. Ariba Network Adapter for SAP NetWeaver Setup Guide 124 © 2015 SAP SE or an SAP affiliate company. Click on Finish. CIX of ariba. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. In the Integration Builder menu. To configure the Invoice integration scenario: 1. see the “About Configuring the System Landscape Directory” [page 61] section. Configuring Integration Scenarios . From the SAP NetWeaver PI main page. select Tools Apply Model from ES Repository . 3. The following steps assume that the different Business Systems are defined in the SLD. If required.com/xi/ASN/Invoice ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. and then click the Display Input Help drop down list and select Input Help. click the Name field. Activate the new configuration. Select Process Integration Scenario. Configure the Integration Scenario. All rights reserved. the integration scenario loaded into the Integration Repository when the design is imported. 2. Assigning Components for the Invoice Integration Scenario Procedure 1. All rights reserved. the Model Configurator window appears. and then click Apply to select the unique component view that is selected by default. Select the communication component name BS_ASN from the selection list and click Apply. Assign the Model. About Configuring the Invoice Integration Scenario Once the Integration Scenario is selected. you must configure it using the following steps: 1. Generate Configuration Objects. 2. 2. click the Select Component View button. Click on the row under the Communication Component column. In the Assign Components window.Results Once the transfer is completed. 4. click the Assign Component button. then click on the Value List drop down and select Value List <F4>. 3. Configure Connections. select the Business System Components for A2A tab to assign components for Ariba Network. Assign Components. Next Steps After selecting the component view. 125 . 3. In the Model Configurator. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. you must assign components to the application components of the selected integration scenario. 4. Selecting the Model for the Scenario Procedure In the Model Configurator window. For Multi ERP implementation add the multiple business services defined for your multiple SAP ERP systems by repeating the steps 6 and 7. then click the Display Input Help drop down list and select Input Help. Click on Continue. The IDoc receiver Communication Channel needs to be created once for each Business System corresponding to your SAP ERP. Select the communication component name BS_SAPR3_50 from the selection list and click Apply. modify the channel name to CC_Invoice_cXML_Sender. 3. For Multi ERP implementation. All rights reserved. Next Steps After assigning services. If a Communication Channel already exists you need to use it. 4. Click the New Communication Channel button (the icon at the top left). see the “Creating Communication Channels for R/3” [page 68] section. click the empty Communication Channel cell corresponding to BS_ASN in the Sender Business System Components table. If a Communication Channel already exists you need to use it. In the Connections from Component Assignment tab in the Configure Connection window. then click on the Value List drop down and select Value List <F4>.com/xi/ASN/Invoice ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. Click Continue. 2. In the Connections from Component Assignment tab in the Configure Connection window. click the Configure Connections button. Ariba Network Adapter for SAP NetWeaver Setup Guide 126 © 2015 SAP SE or an SAP affiliate company. and in the next page click the Name field. you must activate sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations.5. Click on the Insert Line button ('+') to add a service entry in the table 7. CIX of ariba. Select the communication channel CC_IDoc_Receiver corresponding to the SAP ERP Business System from the selection list. 7. 6. and then click Finish. Click the Save Settings button to save the changes. For more information about how to create the IDoc receiver Communication Channel. 8. Configuring Connections for the Invoice Integration Scenario Procedure 1. 5. In the Model Configurator. click the empty Communication Channel cell corresponding to BS_SAPR3_50 in the Receiver Business System Components table. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. You must assign Communication Channels to set up the connections. Click on the row under the Communication Component column. Click the Next Role button (the right arrow) to go to the next screen in the window.com. Select the following Communication Channel Template: ○ Name: CCT_Invoice_cXML_Sender ○ Namespace: http://ariba. 6. Configuring Integration Scenarios . repeat the steps 6 and 7 for all the entries of the Business Systems corresponding to your SAP ERP instances. you must generate the objects. 127 . After the object generation is complete. Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction. Configuring Communication Channels for the Invoice Integration Scenario Context Configure the communication channel CC_Invoice_cXML_Sender under the AR_Invoice_Send Configuration Scenario. Procedure 1. Click the Save Settings button to save the changes. Close the log that is created without saving. and then click OK in the dialog box. In the Create Configuration Object window. click Apply to save the new configuration settings. if required. Generating Objects for the Invoice Integration Scenario Context After making all the configuration settings in the wizard. click the Create Configuration Object button. You can save it. 9. make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select all the check boxes – Receiver Determination. Generation creates the configuration objects if they do not yet exist. In the Model Configurator. they will be reused and enhanced. 3. 5. and Sender/Receiver Agreement. 4. if required. Click the Activate All Connections button. Click Start to begin generating objects. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. You can also simulate generation for test purposes. 2. you can create the communication channel by copy from a channel already configured. All rights reserved. Note The communication channels for SAP ERP Sender system are not required. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. Interface Determination. 8. If they do already exist. adapt the other parameters. specify the left operand of the condition as follows: ○ Click the icon next to the Left Operand field to open the Expression Editor. In the Condition Editor window. double-click |BS_ASN|CC_Invoice_cXML_Sender to open it. In the Configured Receivers section of the Edit Receiver Determination window. If required. ○ Click OK to return to the Expression Editor. 3. to start the Condition Editor. and then select the following xpath from the document tree: /cXML/ Header/To/Credential/@domain.Procedure 1. Note This configuration is required only for Multi-ERP implementations. Save the changes. Retain the default settings for the other receivers. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. see cXML Adapter Parameters [page 391]. All rights reserved. Configuring Receiver Determination Settings for the Invoice Integration Scenario Context Configure the receiver determination settings manually. Click the icon next to the Condition field. Note If you created the channel by copy from an existing channel. 3. and then click |BS_ASN | MIOut_Async_Invoice_ZInvoic02_cXML. 4. For more information about the cXML Adapter parameters. Ariba Network Adapter for SAP NetWeaver Setup Guide 128 © 2015 SAP SE or an SAP affiliate company. ○ Select the XPath option. or right-click and select Open. In the Parameters tab. click the Add button to add a new line. for the receiver MIOut_Async_Invoice_Invoic02_cXML under the AR_Invoice_Send integration scenario. 2. 2. Under Communication Channel. Configuring Integration Scenarios . Expand Receiver Determination. you need to change the request type to InvoiceDetailRequest in the Inbound Request Type field. ○ This path should be displayed in the XPath Expression field. Procedure 1. and then select the following xpath from the document tree: /cXML/ Header/To/Credential/Identity. ○ Select the Right Operand field and specify the Logical System Name corresponding to the Business System for which you are doing the configuration. In the Receiver Interfaces section of the Edit Interface Determination window. ○ Click OK to return to the Expression Editor. repeat the steps 2 to 7 for all your SAP ERP instances. Add another condition by clicking on the Insert Expression option. 129 . Click OK to close the Condition Editor. ○ Select the “=” operator in the Operator column.) ○ Click the icon next to the Left Operand field to open the Expression Editor. Select the operation mapping IFM_cXML_2_INVOIC_INVOICE02_INVOIC02 and click Apply. ○ Select the “=” operator in the Operator column. 8. 3. directly from the tree. and select the Communication Component corresponding to the Logical System Name you specified in the Condition. E.INVOIC02. ○ Select the XPath option.INVOIC02. Configuring Interface Determination Settings for the Invoice Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. Note You cannot select a node having child nodes or attributes. Save the Receiver Determination settings. Click the icon next to the Communication Component field to start the Choose Communication Component window. T90CLNT090. 2. You must first select the child node or attribute and edit the xpath expression in the XPath Expression field to remove the child element. All rights reserved. 6. 7. Expand Interface Determination. click the operation mapping value under the Operation Mapping column. This path should be displayed in the XPath Expression field.g. 5. (The Boolean operator between the two conditions should be “AND”. and then click | BS_ASN | | BS_SAPR3_50 | INVOIC. Procedure 1. Note For Multi ERP implementation. then click the Value List drop down and select Value List. ○ Select the Right Operand field and enter “SystemID”. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 4. The Multiplicity column displays the value "0..unbounded". 5. Save the interface determination settings. Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings. Activating the Invoice Integration Scenario Procedure Using the Change List tab on the main application screen, activate all the Change Lists containing the objects created and modified during the scenario setup. Results The Invoice transaction is now ready for execution. PayMeNow Integration Scenario You must configure the integration scenario for the PayMeNow transaction in the Integration Directory to be able to run the transaction. All the steps of a configuration scenario section must be completed to fully configure a scenario. Note Ensure that the design is imported into your system and ready before you run these steps. The following steps assume that the different Business Systems are defined in the SLD. For more information about configuring the SLD see the “About Configuring the System Landscape Directory” [page 61] section. To configure the PayMeNow scenario: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario. 3. Configure the Communication Channels. 4. Activate the new configuration. Ariba Network Adapter for SAP NetWeaver Setup Guide 130 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Configuring Integration Scenarios Transferring the PayMeNow Integration Scenario Context The first step to configure the integration scenario for the PayMeNow transaction is to transfer to the Integration Directory, the integration scenario loaded into the Integration Repository when the design is imported. Procedure 1. From the SAP NetWeaver PI main page, select Integration Directory Integration Builder , and then login to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select Tools Apply Model from ES Repository . 3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, and then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_PayMeNow_Send ○ Namespace: http://ariba.com/xi/ASN/PayMeNow ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com. 4. Click on Continue. 5. If required, change the name of the scenario for the Integration Directory. 6. Click Finish. Results Once the transfer is completed, the Model Configurator window appears. About Configuring the PayMeNow Integration Scenario Once the Integration Scenario is selected, you must configure it using the following steps: 1. Assign the Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. All rights reserved. 131 Selecting the Model for the Scenario Procedure In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default. Next Steps After selecting the component view, you must assign components to the application components of the selected integration scenario. Assigning Components for the PayMeNow Integration Scenario Procedure 1. In the Model Configurator, click the Assign Component button. 2. In the Assign Components window, select the Business System Components for A2A tab to assign components for Ariba Network. 3. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. 4. Click on the row under the Communication Component column, then click on the Value List drop down and select Value List <F4>. Select the communication component name BS_ASN from the selection list and click Apply. 5. Click the Next Role button (the right arrow) to go to the next screen in the window. 6. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. 7. Click on the row under the Communication Component column, then click on the Value List drop down and select Value List <F4>. Select the communication component name BS_SAPR3_50 from the selection list and click Apply. Note For Multi ERP implementation add the multiple business services defined for your multiple SAP ERP systems by repeating the steps 6 and 7. 8. Click the Save Settings button to save the changes. Ariba Network Adapter for SAP NetWeaver Setup Guide 132 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Configuring Integration Scenarios Next Steps After assigning services, you must activate sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. Configuring Connections for the PayMeNow Integration Scenario Procedure 1. In the Model Configurator, select Configure Connections. You need to assign Communication Channels to set up the connections. 2. In the Connections from Component Assignment tab in the Configure Connection window, click the empty Communication Channel cell corresponding to BS_ASN in the Sender Business System Components table. 3. Click the New Communication Channel button (the icon at the top left), and then select Create Communication Channel with Template to start the Create Communication Channel wizard. Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction, you can create the communication channel by copy from a channel already configured. 4. Click Continue, and in the next page select the following Communication Channel Template: ○ Name: CCT_PayMeNow_cXML_Sender ○ Namespace: http://ariba.com/xi/ASN/PayMeNow ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com. 5. Click Continue, modify the channel name to CC_PayMeNow_cXML_Sender, and then click Finish. 6. In the Connections from the Service Assignment tab in the Configure Connection window, click the empty Communication Channel cell corresponding to BS_SAPR3_50 in the Receiver Business System Components table. Note The IDoc receiver Communication Channel needs to be created once for each Business System corresponding to your SAP R/3. For more information about how to create the IDoc receiver Communication Channel, see the “Creating Communication Channels for R/3” [page 68] section. If a Communication Channel already exists you need to use it. 7. Select the communication channel CC_IDoc_Receiver corresponding to the SAP R/3 Business System from the selection list. Note For Multi ERP implementation, repeat the steps 6 and 7 for all the entries of the Business Systems corresponding to your SAP ERP instances. The communication channels for SAP ERP Sender system are not required. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. All rights reserved. 133 8. Click the Activate All Connections button, and then click OK in the dialog box. 9. Click the Save Settings button to save the changes. Generating Objects for the PayMeNow Integration Scenario Context After making all the configuration settings in the wizard, you must generate the objects. Generation creates the configuration objects if they do not yet exist. If they do already exist, they will be reused and enhanced, if required. You can also simulate generation for test purposes. Procedure 1. In the Model Configurator, the Create Configuration Object button. 2. In the Create Configuration Object window, make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select all the check boxes – Receiver Determination, Interface Determination, and Sender/Receiver Agreement. 3. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. 4. Click Start to begin generating objects. 5. After the object generation is complete, click Apply to save the new configuration settings. Close the log that is created without saving. You can save it, if required. Configuring Communication Channels for the PayMeNow Integration Scenario Context Configure the communication channel CC_PayMeNow_cXML_Sender under the AR_PayMeNow_Send Configuration Scenario: Procedure 1. Under Communication Channel, double-click |BS_ASN|CC_PayMeNow_cXML_Sender. 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. Ariba Network Adapter for SAP NetWeaver Setup Guide 134 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Configuring Integration Scenarios Note If you created the channel by copy from an existing channel, you need to change the request type to PayMeNowRequest in the Inbound Request Type field. If required, edit the other parameters. For more information about the cXML Adapter parameters, see cXML Adapter Parameters [page 391]. 3. Save the changes. Configuring Receiver Determination Settings for the PayMeNow Integration Scenario Context Configure the receiver determination settings manually, for the receiver MIOut_Async_PayMeNow_cXML under the AR_PayMeNow_Send integration scenario. Retain the default settings for the other receivers. Note This configuration is required only for Multi-ERP implementations. Procedure 1. Expand Receiver Determination, and then click |BS_ASN | MIOut_Async_PayMeNow_cXML. 2. In the Configured Receivers section of the Edit Receiver Determination window, click the Add button to add a new line. 3. Click the icon next to the Condition field, to start the Condition Editor. 4. In the Condition Editor window, specify the left operand of the condition as follows: ○ Click the icon next to the Left Operand field to open the Expression Editor. ○ Select the XPath option, and then select the following xpath from the document tree: /cXML/Header/ From/Credential/@domain. This path should be displayed in the XPath Expression field. ○ Click OK to return to the Expression Editor. ○ Select the “=” operator in the Operator column. ○ Select the Right Operand field and enter “SystemID”. 5. Add another condition by clicking on the Insert Expression option. (The Boolean operator between the two conditions should be “AND”.) ○ Click the icon next to the Left Operand field to open the Expression Editor. ○ Select the XPath option, and then select the following xpath from the document tree: /cXML/Header/ From/Credential/Identity. This path should be displayed in the XPath Expression field. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. All rights reserved. 135 Note You cannot select a node having child nodes or attributes, directly from the tree. You must first select the child node or attribute and edit the xpath expression in the XPath Expression field to remove the child element. ○ Click on OK to return to the Expression Editor. ○ Select the “=” operator in the Operator column. ○ Select the Right Operand field and specify the Logical System Name corresponding to the Business System for which you are doing the configuration. E.g. T90CLNT090. 6. Click on OK to close the Condition Editor. 7. Click on the icon next to the Communication Component field to start the Choose Communication Component window, and select the Communication Component corresponding to the Logical System Name you specified in the Condition. Note For Multi ERP implementation, repeat the steps 2 to 7 for all your SAP ERP instances. 8. Save the Receiver Determination settings. Configuring Interface Determination Settings for the PayMeNow Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. Procedure 1. Expand Interface Determination, and then click |BS_SAPR3_50 | FIDCCH.FIDCCH01 | | BS_ASN. 2. In the Receiver Interfaces section of the Edit Interface Determination window, click the operation mapping value under the Operation Mapping column, then click the Value List drop down and select Value List. 3. Select the operation mapping IFM_cXML_2_FIDCCH_FIDCCH01 and click Apply. 4. The Multiplicity column displays the value "0..unbounded". 5. Save the interface determination settings. Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings. Ariba Network Adapter for SAP NetWeaver Setup Guide 136 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Configuring Integration Scenarios Activating the PayMeNow Integration Scenario Procedure Using the Change List tab on the main application screen, activate all the Change Lists containing the objects created and modified during the scenario setup. Results This completes the configuration of the Pay Me Now transaction in SAP NetWeaver PI. Payment Remittance Integration Scenario You must configure the integration scenario for the Payment Remittance transaction in the Integration Directory to be able to run the transaction. All the steps of a configuration scenario section must be completed to fully configure a scenario. Mapping Limitations The Payment Remittance transaction has the following mapping limitations: ● Only new payment remittance pull is supported ● Any changes or void payment pulls are not supported ● Time zone is not factored in the invoice date mappings ● Integration is tested for only 'check' and 'electronic/edi' payment methods ● Payment Remittance (Full/Partial) generated using manual payments are not pulled, because no IDocs are generated for manual payments (f-58 transaction ● Cancel Remittances are not pulled to Ariba Network. Note Cancel Remittances are not supported. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. All rights reserved. 137 change the name of the scenario for the Integration Directory. Ariba Network Adapter for SAP NetWeaver Setup Guide 138 © 2015 SAP SE or an SAP affiliate company. 3. 6.com. Activate the new configuration. CIX of ariba. and then click the Display Input Help drop down list and select Input Help. All rights reserved. Procedure 1. Configure the Integration Scenario. In the first screen of the Transfer Model from ES Repository wizard. see the cXML Adapter Parameters [page 391] section. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_PaymentRemittance_Receive ○ Namespace: http://ariba. Configuring Integration Scenarios . click the Name field. 2. In the Integration Builder menu.Workflow Note Ensure that the design is imported into your system and ready before you run these steps. and then login into Configuration: Integration Builder application. the integration scenario loaded into the Integration Repository when the design is imported. 4. Click Continue. Configure the Communication Channels. Transferring the Payment Remittance Integration Scenario Context The first step to configure the integration scenario for the Payment Remittance transaction is to transfer to the Integration Directory. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 5. To configure the Payment Remittance: 1. If required. select the Integration Directory Integration Builder . 2. The following steps assume that the different Business Systems are defined in the SLD.com/xi/ASN/PaymentRemittance ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. select Tools Apply Model from ES Repository . 4. Click on Finish. 3. For more information about configuring the SLD. Select Process Integration Scenario. From the SAP NetWeaver PI main page. Note For Multi ERP implementation add the multiple business services defined for your multiple SAP ERP systems by repeating the steps 3 and 4. 4. Configure Connections. Click on the row under the Communication Component column. Generate Configuration Objects. Select the communication component name BS_SAPR3_50. 2. 6. After selecting the model. and then click Apply to select the unique model that is selected by default. you must configure it using the following steps: 1. Select Model.Results Once the transfer is completed. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. the Model Configurator window appears. click the Assign Component button. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. In the Model Configurator. In the Assign Components window. Assign Components. then click on the Value List drop down and select Value List <F4. 4. you must assign components to the application components of the selected integration scenario. Assigning Components for the Payment Remittance Integration Scenario Procedure 1. All rights reserved. Click the Next Role button (the right arrow) to go to the next screen in the window. 3. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. from the selection list and click Apply. 5. About Configuring the Payment Remittance Integration Scenario Once the Integration Scenario is selected. 139 . In the Model Configurator window. 2. 3. click the Select Component View button. select the Business System Components for A2A tab to assign components for Ariba Network. You must assign Communication Channels to set up the connections. you must activate sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. All rights reserved. modify the channel name to CC_PaymentRemittance_cXML_Receiver. In the Connections from Component Assignment tab in the Configure Connection window. from the selection list and click Apply. Ariba Network Adapter for SAP NetWeaver Setup Guide 140 © 2015 SAP SE or an SAP affiliate company. click the empty Communication Channel cell corresponding to BS_ASN in the Receiver Business System Components table. then click on the Value List drop down and select Value List <F4. 4. Note The communication channels for SAP ERP Sender system are not required. you can create the communication channel by copy from a channel already configured. click the Configure Connections button.com/xi/ASN/PaymentRemittance ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. Select the communication component name BS_ASN. Click on Apply to save the changes.7. In the Model Configurator. Click the New Communication Channel button (the icon at the top left). Click Continue. Configuring Integration Scenarios . then click the Display Input Help drop down list and select Input Help. and in the next page click the Name field. 2. Click Continue. 6. 8. Tip In case you have already created and configured a Receiver channel for BS_ASN for another transaction. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. Click on the row under the Communication Component column. Select the following Communication Channel Template: ○ Name: CCT_PaymentRemittance_cXML_Receiver ○ Namespace: http://ariba. CIX of ariba. Click the Save Settings button to save the changes. and then click Finish. Configuring Connections for the Payment Remittance Integration Scenario Procedure 1. 3. 5. Next Steps After assigning services.com. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. click Apply to save the new configuration settings. 3. In the Model Configurator. if required. Under Communication Channel. 2. select |BS_ASN{CC_PaymentRemittance_cXML_Receiver. If they do already exist. You can save it. click the Create Configuration Object button. 5. In the Parameters tab. Configuring Communication Channels for the Payment Remittance Integration Scenario Context Configure the communication channel CC_PaymentRemittance_cXML_Receiver under the AR_PaymentRemittance_Receive Configuration Scenario: Procedure 1. 4. You can also simulate generation for test purposes. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. you must generate the objects. 2. Click Start to begin generating objects. In the Create Configuration Object window. Close the log that is created without saving. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. and Interface Determination. Procedure 1. 141 . After the object generation is complete. they will be reused and enhanced.Generating Objects for the Payment Remittance Integration Scenario Context After making all the configuration settings in the wizard. All rights reserved. if required. make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select both the active check boxes – Receiver Determination. Generation creates the configuration objects if they do not yet exist. All rights reserved.PEXR2001 | | BS_ASN. edit the other parameters. Configuring Integration Scenarios . and then click | BS_SAPR3_50 | REMADV. click the operation mapping value under the Operation Mapping column. 5. Select the operation mapping IFM_REMADV_PEXR2001_2_cXML and click Apply. 2. activate all the Change Lists containing the objects created and modified during the scenario setup. For more information about the cXML Adapter parameters. you need to change the request type to PaymentRemittanceRequest. 3. Save the interface determination settings. see cXML Adapter Parameters [page 391]. 3. Note If you created the channel by copy from an existing channel. The Multiplicity column displays the value "0. Expand Interface Determination. Save the changes. Ariba Network Adapter for SAP NetWeaver Setup Guide 142 © 2015 SAP SE or an SAP affiliate company.unbounded". In the Receiver Interfaces section of the Edit Interface Determination window. then click the Value List drop down and select Value List.. Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings. Procedure 1. Configuring Interface Determination Settings for the Payment Remittance Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. If required. 4. Activating the Payment Remittance Integration Scenario Procedure Using the Change List tab on the main application screen. All rights reserved. deleted. ship notices. suppliers cannot create order confirmations. However. Each line item can have different quantities and multiple delivery dates and time in a purchase order. This allows you to specify multiple schedule lines for a line item that needs to be supplied repeatedly over a period of time. Import the relevant SAP transport requests into your SAP ERP system. and invoices for each of the schedule lines on Ariba Network. When a purchase order containing changes to the schedule lines is sent to a supplier. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 2. The mappings for the schedule lines are stored in: / ns0:Messages/ns0:Message2/cXML/Request/OrderRequest/ItemOut/ScheduleLine/@lineNumberl. Download the latest AribaNetworkAdapterSAPNetweaver_vCI_x_FR.Design. Prerequisites to Enabling Schedule Lines in Purchase Orders from your SAP ERP System to Ariba Network Procedure 1.com. 143 . Buyers can send multiple delivery schedules for a line item in a purchase order with a number so that Ariba Network receives the delivery schedules numbered sequentially.Results This completes the configuration of the Payment Remittance transaction in SAP NetWeaver PI.tpz file into your SAP NetWeaver PI system. Ariba Network Adapter for SAP NetWeaver extracts the line numbers from the SAP ERP MM table (EKET-ETENR) and assigns this value to the lineNumber attribute for the ScheduleLine element in the cXML file. Import the AribaNetworkAdapterSAPNetweaver. or edited schedule lines are highlighted in the change purchase order on Ariba Network. This feature has the following limitations: ● A line item in a purchase order or change purchase order can have a maximum of 50 schedule lines. 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. ● You can send purchase orders containing schedule lines to suppliers that can view them.zip from connect.ariba. Purchase orders containing more than 50 schedule lines for a line item fail on Ariba Network. the newly added. 3. see: ○ : Configuring Communication Channels for the Purchase Order Integration Scenario [page 87] 4. Configure the Communication Channels for Purchase and Change Orders. For more information. For more information about the streamlining and merging of Change Order processing into Purchase Order processing. Transfer the Integration Scenario from the Integration Repository Enterprise Service Builder to the Integration Directory Integration Builder . Configure the Integration Scenario. The following steps assume that the different Business Systems are defined in the SLD. see: ○ Activating the Purchase Order Integration Scenario [page 89] Blanket Purchase Order Integration Scenario You can create and send blanket purchase orders from your SAP ERP system to suppliers on the Ariba Network.Configuring the Purchase Order Integration Scenario to Support Schedule Lines Context ● Ensure that the design package is imported into your system and ready before you run these steps. For more information. ● All the steps of the configuration scenario section must be completed to fully configure a scenario. All rights reserved. ● If you are an existing customer. see: ○ Configuring Interface Determination Settings for the Purchase Order Integration Scenario [page 88] 5. Configure the Interface Determination. Additionally. For more information. see Change Purchase Order Integration Scenario [page 89] as well as the links to Purchase Order configuration in the following steps. ● Ensure that you make the necessary changes to the cXML Version parameter in the Communication Channel. see: ○ Transferring the Purchase Order Integration Scenario [page 84] 2. the blanket purchase order also includes the Validity Start (cXML Ariba Network Adapter for SAP NetWeaver Setup Guide 144 © 2015 SAP SE or an SAP affiliate company. For more information. Activate the integration scenario. For more information. see: ○ About Configuring the Purchase Order Integration Scenario [page 85] 3. Configuring Integration Scenarios . The blanket purchase order or the change blanket purchase order contain line items that specify the item category B (Limit) only. Procedure 1. you must delete the existing Configuration scenario and rerun the steps for the configuration scenario. Note In SAP ERP and Ariba Network Adapter for SAP NetWeaver Purchase and Change Orders are now processed using the same internal mechanisms. see Transferring the Purchase Order Integration Scenario [page 84]. ● If you are an existing customer. 3. you must delete the existing Configuration scenario and rerun the steps for the configuration scenario.field:effectiveDate) and Validity End (cXML field:expirationDate) details for Ariba Network to successfully process blanket purchase orders. this purchase order having line items with different types of item categories fail on Ariba Network. Buyers must ensure that they create a blanket purchase order containing line items that specify the item category B in their SAP ERP system. C (standard) and approve the same in the SAP ERP system. see Configuring Communication Channels for the Purchase Order Integration Scenario [page 87]. ● You cannot create a blanket purchase order containing split accounting for the line items Workflow Ensure that the design package is imported into your system and ready before you run these steps. ● The SAP ERP system allows you to create a purchase order with line items having different types of item categories. see Activating the Purchase Order Integration Scenario [page 89]. This feature has the following limitations: ● You cannot create a blanket purchase order for services. Activate the integration scenario. The following steps assume that the different Business Systems are defined in the SLD. The cXML blanket purchase orders sent to Ariba Network contains the value orderType=“blanket”. Suppliers can use these purchase orders of type “blanket” to create order confirmation and ship notices on Ariba Network. You can also create a dedicated document type in the SPRO configuration to ensure that only item category 'B' is available for selection in a blanket purchase order. Configure the Interface Determination. D (services). For more information. Configure the Integration Scenario. For more information. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. For more information. 4. All rights reserved. see Configuring Interface Determination Settings for the Purchase Order Integration Scenario [page 88]. You can also create a blanket purchase order having line items that specify the item category B against a single or multiple outline agreements (OLA). 5. 2. 1. Note ● All the steps of a configuration scenario section must be completed to fully configure a scenario. For example. Transfer the Integration Scenario from the Integration Repository Enterprise Service Builder to the Integration Directory Integration Builder . Ariba Network rejects purchase orders having line items that specify different categories. Configure the Communication Channels. Ariba Network Adapter for SAP NetWeaver processes purchase orders containing line items that specify any other item category as regular purchase orders. you can create a single purchase order having line items that specify item category B (Limit). For more information. 145 . see About Configuring the Purchase Order Integration Scenario [page 85]. For more information. However. Buyers using the Ariba Network Adapter for SAP NetWeaver can send an order inquiry and request information on the following: ● Delivery schedule for materials ordered against line items for an entire purchase order ● Delivery date for line items having schedule lines ● Reminder on the outstanding line items ● Overall status of line items or the purchase order ● Additional comments Suppliers can respond to these inquiries with an order confirmation or a response to the inquiry raised against line items in the purchase order. Ariba Network Adapter for SAP NetWeaver does not send reminders to suppliers on Ariba Network. ● Suppliers can do one of the following: ○ Confirm the entire purchase order: The supplier creates an order confirmation on Ariba Network that is sent to the buyer. they specify the number of days on which suppliers must receive reminders. ● Buyers can create up to three reminders for a purchase order in an SAP system.Order Inquiries Integration Scenario When an ERP buyer creates a purchase order and requires suppliers to confirm their purchase order or deliver items by the delivery date.4 for Java only or Java and ABAP stack (single or dual stack). Configuring Integration Scenarios . an inquiry (Reminder 1) is sent to the supplier. These reminders are called Inquiries. All rights reserved. Ariba Network Adapter for SAP NetWeaver Setup Guide 146 © 2015 SAP SE or an SAP affiliate company. If the supplier does not confirm the purchase order or delivery items by July 12. This feature allows both buyers and suppliers to collaborate and handle processing of purchase orders efficiently. This section has the following topics: ● Order Inquiries Data Flow Overview [page 146] ● Order Inquiry Output Types and Reminders [page 147] ● Configuring the Order Inquiries Integration Scenario [page 148] Order Inquiries Data Flow Overview The following is an example that describes the process on how buyers and suppliers can create an inquiry against a purchase order: ● An ERP buyer creates a purchase order with a delivery date of July 10. A buyer specifies two reminders: Reminder 1 having 2 days and Reminder 2 having 3 days. 2014 and specifies reminders to be sent to a supplier if they do not confirm the purchase order or deliver items against this delivery date. After the supplier responds to the inquiry. ● Buyers can also send inquiries for change purchase orders. 2014. 7.3 and 7. ● The supplier on Ariba Network receives the purchase order.1. When suppliers do not confirm or deliver items against the purchase order within the stipulated time. they receive these reminders. Note ● Order Inquiries is supported in SAP NetWeaver PI 7. ○ Responds to the inquiry on a line item. The reminders are calculated as follows: ● If the calculated date is less than the current date. ME92F is the transaction code to send reminders by specifying the number of days in the confirmation control key SPRO setting. The supplier responds to the inquiry and the same is sent to the buyer. they do not receive reminders from the buyer’s ERP system. After the supplier responds to the inquiry. another inquiry (Reminder 2) is sent to the supplier. This generates the MAHN output type of order inquiry. All rights reserved. This generates the AUFB output type of order inquiry. 2014. Based on the reminder level. ● If the supplier still fails to confirm the order by July 15. For example: Variable Name Field Name Number Option Selection Value ORDERENQUIRY DUNNING1 I EQ ZMM_DUNNING1 ORDERENQUIRY DUNNING2 I EQ ZMM_DUNNING2 ORDERENQUIRY DUNNING3 I EQ ZMM_DUNNING3 Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 147 . The Ariba Network Adapter for SAP NetWeaver calculates the date programmatically before sending reminders to the suppliers. Order Inquiry Output Types and Reminders Buyers can create two output types for an order inquiry: ● MAHN (Dunning) ● AUFB (Dunning Order Confirmation) Buyers can set reminders using the transaction code ME91F. The SO10 transaction code stores the reminder text. The /ARBA/PARAM_TAB stores the reminder text with the variable name ORDERENQUIRY. ● If the calculated date is more than the current date. the actual reminder code is populated by taking the value from EKET-MAHNZ. the reminder code is populated as zero {MAHNZ]. the associated text is picked up and sent to the supplier. Transfer the Integration Scenario from the Integration Repository Enterprise Service Builder to the Integration Directory Integration Builder . For more information. Note ● The namespace for order inquiries is http://ariba. For more information. For more information. see Configuring Communication Channels for the Order Inquiries Integration Scenario [page 152]. Configure the Communication Channels. For more information. The Reminder text is populated in /ARBA/ORDENQ_COMMENTS. ● The Ariba Network Adapter for SAP NetWeaver sends inquiries only for line items that contain reminders. The following steps assume that the different Business Systems are defined in the SLD. ● The CDF_Fulfill_XSD structure contains changes to support order inquiries. 5.com/xi/ASN/OrderEnquiry. All rights reserved. Configure the Integration Scenario. see Activating the Order Inquiries Integration Scenario [page 153]. Ensure that the design package is imported into your system and ready before you run these steps. Configuring Integration Scenarios .Design. see Configuring Interface Determination Settings for the Order Inquiries Integration Scenario [page 153]. 4. see Transferring the Order Inquiries Integration Scenario [page 149]. For more information.com. see About Configuring the Order Inquiries Integration Scenario [page 149]. Configure the Interface Determination. Ensure that you import the AribaNetworkAdapterSAPNetweaver.Variable Name Field Name Number Option Selection Value ORDERENQUIRY DUNNING_OC I EQ ZMM_DUNNING_OC ORDERENQUIRY PUR­ AB Ø>d¢ço¨V!{x¨³aüÃÆä1ˆ¿¶~é"¼Ç²ª EGORY Note PURCHASE_ORDER_CATEGORY must be maintained and a value provided for it to prevent order inquiry failure. Configuring the Order Inquiries Integration Scenario Prerequisites You must download the latest AribaNetworkAdapterSAPNetweaver_vCI_x_FR.zip from connect.tpz file into your SAP NetWeaver PI System and transports in your ERP systems. Activate the integration scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide 148 © 2015 SAP SE or an SAP affiliate company. Procedure 1. 2.ariba. 3. select Integration Directory Integration Builder .com 4. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. select Tools Apply Model from ES Repository . Select Process Integration Scenario. and then log in to the Configuration: Integration Builder application. 6. Click Finish. Note All the steps of a configuration scenario section must be completed to fully configure a scenario. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_OrderEnquiry_Receive ○ Namespace: http://ariba.com/xi/ASN/OrderEnquiry ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba. change the name of the scenario for the Integration Directory. 3. About Configuring the Order Inquiries Integration Scenario Configuring the Integration Scenario involves the following steps: 1. Results After the integration scenario transfer is completed. All rights reserved. 2. In the first screen of the Transfer Model from ES Repository wizard. the Model Configurator window appears. click the Name field. If required. Click Continue. From the SAP NetWeaver PI main page. and then click the Display Input Help pull-down menu and select Input Help. 149 . The integration scenario is loaded into the Integration Repository when the design package is imported. 5. Transferring the Order Inquiries Integration Scenario Context The first step to support inquiries in purchase orders is to configure the Purchase Order transaction and transfer the integration scenario to the Integration Builder. In the Integration Builder menu. Procedure 1. Selecting the model. from the selection list and click Apply. click the Assign Component button. and then click Apply to select the unique component view that is selected by default. 6. Select the communication component name for the business system for Ariba Network. Generating the configuration objects. Click the row under the Communication Component column. 5. Configuring Integration Scenarios . All rights reserved. select the Business System Components for A2A tab to assign components for Ariba Network. 7. from the selection list and click Apply. Selecting the Model for the Scenario Procedure In the Model Configurator window. Ariba Network Adapter for SAP NetWeaver Setup Guide 150 © 2015 SAP SE or an SAP affiliate company. click the Select Component View button. then click the Value List pull-down menu and select Value List <F4. In the Assign Components window. 3. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is available. Next Steps After selecting the component view. Assigning the components. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. you must assign components to the application components of the selected integration scenario. In the Model Configurator. 3. 8. Note If you have multiple ERP systems. 2.2. Select the communication component name for the business system of your SAP R/3. Click the Save Settings button. Click the Next Role button (the right arrow) to go to the next screen on the window. Click the row under the Communication Component column. Assigning Components for the Order Inquiries Integration Scenario Procedure 1. Configuring the sender and receiver relations for individual connections. then click the Value List pull-down menu and select Value List <F4. add the multiple communication components defined for your multiple SAP ERP systems by repeating the Step 3 and 4. 4. 4. click the empty Communication Channel cell corresponding to the business system for Ariba Network in the Receiver Business System Components table. Tip If you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction. Generating Objects for the Order Inquiries Integration Scenario Context Generating the objects creates the configuration objects if they do not yet exist. 3.Configuring the Sender and Receiver Relations for Individual Connections for the Order Inquiries Integration Scenario Procedure 1. if required. they are reused and enhanced. You must assign Communication Channels to set up the connections. Click Continue. Click the Save Settings button. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. You can also simulate generation for test purposes. 8. Note The communication channels for SAP ERP Sender system are not required. click the Configure Connections button. 7. Click the Activate All Connections button. Click Continue.com 6. and then click Finish. In the Model Configurator. Click the New Communication Channel button (the icon at the top left). Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 151 . 2. you can create the communication channel by copying from a channel that has already been configured. and then click OK. In the Connections from Component Assignment tab in the Configure Connection window. modify the channel name to CC_OrderEnquiry_cXML_Receiver. click the Name field and then click the Display Input Help pull-down menu and select Input Help. 4. If they already exist. All rights reserved. On the next page.com/xi/ASN/OrderEnquiry ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba. Select the following Communication Channel Template: ○ Name: CCT_OrderEnquiry_cXML_Receiver ○ Namespace: http://ariba. 5. 4. All rights reserved. Click Create New in the Change List for Generated Objects section. 2. edit the other parameters. double-click |< Name of the Business System for Ariba Network | CC_OrderEnquiry_cXML_Receiver to open it. Ariba Network Adapter for SAP NetWeaver Setup Guide 152 © 2015 SAP SE or an SAP affiliate company. Update the cXML version parameter to the 1. The text box already contains an object name that you can use or modify. 5. Note If you created the channel by copying from an existing channel. you must change the request type to OrderEnquiry in the Outbound Request Type field. Configuring Communication Channels for the Order Inquiries Integration Scenario Context Configure the communication channel CC_OrderEnquiry_cXML_Receiver under the AR_OrderEnquiry_Receive Configuration Scenario. 4. click the Create Configuration Object button. do the following: ○ Click Generation in the General section. 2. After the object generation is complete. If required. ○ Select the Receiver Determination. click Apply to save the new configuration settings. Save the changes. if required. 3. In the Create Configuration Object window. You can save it. In the Parameters tab. Configuring Integration Scenarios . Close the log that is created without saving.2. Click Start to begin generating objects. and Interface Determination check boxes in the Scope of Generation section. In the Communication Channel list. In the Model Configurator. 3. Procedure 1.Procedure 1. set the parameters in the Authentication section to match your Ariba Network buyer account configuration.026 version. The Multiplicity column displays the value “0. 3. 5. A Forecast Delivery Schedule contains schedule lines for line items required over a longer period of time. The scheduling agreement releases do not contain any pricing information. 153 . Then click the Value List pull-down menu and select Value List. You can create either a Forecast Delivery Schedule or JIT (Just-in-time) Delivery Schedule against a scheduling agreement release that contain schedule lines with delivery dates for different quantities for the line item. and then click |< Name of the Business System for SAP ERP | ORDERS05. In the Receiver Interfaces section of the Edit Interface Determination window. 4.Configuring Interface Determination Settings for the Order Inquiries Integration Scenario Procedure 1. quantity. These scheduling agreement releases contain schedules lines with details on the line item. click the operation mapping value under the Operation Mapping column. Activating the Order Inquiries Integration Scenario Procedure Using the Change List tab on the main application screen. Expand Interface Determination. Note Configuring the Interface Determination is a mandatory step if you must configure the mappings./ARBA/ORDERS05 | | < Name of the Business System for Ariba Network . spanning Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. activate all the change lists containing the objects created and modified during the component setup. Save and activate the interface determination settings. and the different delivery dates for an extended period of time. 2.unbounded”. Select the operation mapping IFM_ORDERS_ORDENQ_ARBA_2_cXML and click Apply. Results This completes the configuration of the purchase order transaction to support inquiries on SAP NetWeaver PI. All rights reserved.. Scheduling Agreement Release Integration Scenario You can send a scheduling agreement release as a purchase order (release order) to a supplier when they require material or non-material items for an extended period of time. Ensure that you make the necessary changes to the cXML Version parameter in the Communication Channel. suppliers can create ship notices for line items having the Commitment Level as “Firm. Activate the integration scenario. ● Suppliers cannot create order confirmations or invoices against a scheduling agreement release. Any updates to the same scheduling agreement contains the attribute type="update" and the Release Number is incremental by 1 for each subsequent version. see Transferring the Scheduling Agreement Release Integration Scenario [page 155]. For more information. Suppliers can use this release purchase order to create ship notices for the line item based on the different delivery dates and specified quantities on Ariba Network. For more information.2.2. see Activating the Scheduling Agreement Release Integration Scenario [page 159]. ● The OrderRequestHeader element has the attribute type="new" for a new scheduling agreement. For more information. see Configuring Interface Determination Settings for the Scheduling Agreement Release Integration Scenario [page 159]. However. see Configuring Communication Channels for the Scheduling Agreement Release Integration Scenario [page 158]. Limitations ● You cannot create a scheduling agreement release containing more than one line item.026 will be made available as part of the Ariba Network 2014 August release.multiple weeks or months. Configure the Interface Determination. Ariba Network Adapter for SAP NetWeaver Setup Guide 154 © 2015 SAP SE or an SAP affiliate company. Note ● You must upgrade to the cXML version 1. see Configuring the Integration Scenario [page 156]. 4. About Configuring the Scheduling Agreement Release Integration Scenario Configuring the scheduling agreement release integration scenario involves the following steps: 1. For more information. ● You can create CC invoices against scheduling agreements. For more information on . Suppliers receive these scheduling agreement releases as a release purchase order (orderType=“release”) containing a single line item with schedule lines. 2. ● You can create a Forecast Delivery Schedule or JIT Delivery Schedule against only one line item in a scheduling agreement release. Transfer the Integration Scenario from the Integration Repository Enterprise Service Builder to the Integration Directory Integration Builder . Please contact your Ariba Account Manager for more information on integration services. 3.026 and configure your SAP R/3 system to send scheduling agreement releases. However. A JIT Delivery Schedule contains line items required over a shorter period of time. 5. All rights reserved. Configure the Communication Channels. spanning multiple days or even times in a day." ● The quantity of the line items in the scheduling agreement must be the sum of the quantities for the line items having the Commitment Level as “Firm. Configuring Integration Scenarios . support for this feature and the cXML version 1. Configure the Integration Scenario.” The line item quantity must not be the sum of all the schedule lines. 6. Click Finish. click the Name field. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_ScheduleAgreementRelease_Receive ○ Namespace: http://ariba. select Integration Directory Integration Builder . and then log in to the Configuration: Integration Builder application. 155 . From the SAP NetWeaver PI main page. Procedure 1.com/xi/ASN/ScheduleAgreementRelease ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba. the Model Configurator window appears. 3. The integration scenario is loaded into the Integration Repository when the design package is imported. In the first screen of the Transfer Model from ES Repository wizard. The following steps assume that the different Business Systems are defined in the SLD. Transferring the Scheduling Agreement Release Integration Scenario Context The first step to configure the integration scenario for scheduling agreement releases is to configure the Scheduling Agreement Release transaction and transfer the integration scenario to the Integration Builder. If required. Select Process Integration Scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. select Tools Apply Model from ES Repository . change the name of the scenario for the Integration Directory. and then click the Display Input Help pull-down menu and select Input Help. All rights reserved. 2. ○ All the steps of a configuration scenario section must be completed to fully configure a scenario. Results After the integration scenario transfer is completed. In the Integration Builder menu. 5. Note ○ Ensure that the design package is imported into your system and ready before you run these steps. ○ To configure scheduling agreement releases on your SAP ERP system. see Configuring Scheduling Agreement Releases [page 309].com 4. Click Continue. Ariba Network Adapter for SAP NetWeaver Setup Guide 156 © 2015 SAP SE or an SAP affiliate company. 5. Selecting the model. In the Assign Components window. then click the Value List pull-down menu and select Value List <F4. Assigning Components for the Scheduling Agreement Release Integration Scenario Procedure 1. Generating the configuration objects. Selecting the Model for the Scenario Procedure In the Model Configurator window. Click the Next Role button (the right arrow) to go to the next screen on the window. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is available. 4. 3.Configuring the Integration Scenario Configuring the Integration Scenario involves the following steps: 1. 4. click the Assign Component button. Click the row under the Communication Component column. Select the communication component name for the business system of your SAP R/3. 3. In the Model Configurator. and then click Apply to select the unique component view that is selected by default. Assigning the components. All rights reserved. 2. click the Select Component View button. Configuring Integration Scenarios . from the selection list and click Apply. select the Business System Components for A2A tab to assign components for Ariba Network. add the multiple communication components defined for your multiple SAP ERP systems by repeating the Step 3 and 4. 2. Note If you have multiple ERP systems. you must assign components to the application components of the selected integration scenario. Configuring the sender and receiver relations for individual connections. Next Steps After selecting the component view. and then click Finish. Click the Save Settings button. In the Model Configurator. You must assign Communication Channels to set up the connections. Click the New Communication Channel button (the icon at the top left). then click the Value List pull-down menu and select Value List <F4. 2. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. Select the communication component name for the business system for Ariba Network. 5.com/xi/ASN/ScheduleAgreementRelease ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba. In the Connections from Component Assignment tab in the Configure Connection window. 157 .com 6. Tip If you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction. 7. Select the following Communication Channel Template: ○ Name: CCT_ScheduleAgreementRelease_cXML_Receiver ○ Namespace: http://ariba. All rights reserved. click the Name field and then click the Display Input Help pull-down menu and select Input Help. click the Configure Connections button. Note The communication channels for SAP ERP Sender system are not required. 8. you can create the communication channel by copying from a channel that has already been configured. modify the channel name to CC_ScheduleAgreementRelease_cXML_Receiver. from the selection list and click Apply. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. Click the Activate All Connections button. 3. Click the Save Settings button. Click Continue. Click Continue. 6. 4. 8. Click the row under the Communication Component column. and then click OK. On the next page. 7. click the empty Communication Channel cell corresponding to the business system for Ariba Network in the Receiver Business System Components table. Configuring the Sender and Receiver Relations for Individual Connections for the Scheduling Agreement Release Integration Scenario Procedure 1. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 2. You can also simulate generation for test purposes. Click Start to begin generating objects. You can save it. if required. Configuring Communication Channels for the Scheduling Agreement Release Integration Scenario Context Configure the communication channel CC_ScheduleAgreementRelease_cXML_Receiver under the AR_ScheduleAgreementRelease_Receive Configuration Scenario. In the Communication Channel list. In the Model Configurator. 4. All rights reserved. and Interface Determination check boxes in the Scope of Generation section. After the object generation is complete. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. Configuring Integration Scenarios . click Apply to save the new configuration settings.Generating Objects for the Scheduling Agreement Release Integration Scenario Context Generating the objects creates the configuration objects if they do not yet exist. they are reused and enhanced. 5. ○ Select the Receiver Determination. do the following: ○ Click Generation in the General section. Click Create New in the Change List for Generated Objects section. double-click |< Name of the Business System for Ariba Network | CC_ScheduleAgreementRelease_cXML_Receiver to open it. In the Create Configuration Object window. Ariba Network Adapter for SAP NetWeaver Setup Guide 158 © 2015 SAP SE or an SAP affiliate company. click the Create Configuration Object button. The text box already contains an object name that you can use or modify. if required. 2. Procedure 1. In the Parameters tab. If they already exist. 3. Procedure 1. Close the log that is created without saving. 3.unbounded”. 4. In the Receiver Interfaces section of the Edit Interface Determination window. Configuring Interface Determination Settings for the Scheduling Agreement Release Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. 4. Expand Interface Determination. Save and activate the interface determination settings.. The Multiplicity column displays the value “0. 159 . If required. Note Configuring the Interface Determination is a mandatory step if you must configure the mappings.026 version. Then click the Value List pull-down menu and select Value List. Select the operation mapping IFM_DELINS_DELFOR02_ARBA_2_cXML and click Apply. Procedure 1. activate all the change lists containing the objects created and modified during the component setup. Update the cXML version parameter to the 1.2. click the operation mapping value under the Operation Mapping column. and then click |< Name of the Business System for SAPR3 | DELINS. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. Save the changes. you must change the request type to SchedulAgreementReleaseRequest in the Outbound Request Type field. Activating the Scheduling Agreement Release Integration Scenario Procedure Using the Change List tab on the main application screen. All rights reserved. 2.DELFOR02. Note If you created the channel by copying from an existing channel. 5./ARBA/DELFOR02 | | < Name of the Business System for Ariba Network . 3. edit the other parameters. 00 P. Activate the new configuration.Results This completes the configuration of the scheduling agreement transactions in SAP NetWeaver PI. 2. Configuring Integration Scenarios . Configure the Communication Channels. assume that the task is executed at 12.00 P. see About Configuring the System Landscape Directory [page 61]. Configure the Integration Scenario. Invoice Status Update Integration Scenario You need to configure the integration scenario for the Invoice Status Update (ISU) transaction in the Integration Directory to be able to run the transaction. All the steps of a configuration scenario section must be completed to fully configure a scenario. 4. For more information. the task imports the status update for all the invoices including the invoices for which the status has already been imported. if the task is executed again at 5. Ariba Network Adapter for SAP NetWeaver Setup Guide 160 © 2015 SAP SE or an SAP affiliate company. Now. The following steps assume that the different Business Systems are defined in the SLD. All rights reserved.M. Limitation When the task to import the status update for invoices is executed.M. 3. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. However.M and imports the status for 10 invoices.00 P. it returns the status of all invoices for which the status was updated on that particular date. it must import the status for only those invoices that were updated after 12. Workflow Note Ensure that the Design package is imported into your system and ready before you run these steps. on the same date. For example. The task does not consider the time when it imports the status update. To configure the Invoice Status Update transaction: 1. Select Model. change the name of the scenario for the Integration Directory 6. 2. In the first screen of the Transfer Model from ES Repository wizard. 3. Click Continue. 161 . select Tools Apply Model from ES Repository . From the SAP NetWeaver PI main page. Results Once the transfer is completed. Select Process Integration Scenario. 3. All rights reserved. click the Name field. About Configuring the Invoice Status Update Integration Scenario Once the Integration Scenario is selected. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_InvoiceStatusUpdate_ReceiveProxy ○ Namespace: http://ariba. the integration scenario loaded into the Integration Repository when the Design package is imported. Configure Connections. If required. CIX of ariba. Assign Components. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 2. then click the Display Input Help drop down list and select Input Help. select Integration Directory Integration Builder . Procedure 1.com/xi/ASN/InvoiceStatusUpdateProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER.com 4. and then login into the Configuration: Integration Builder application. the Model Configurator window appears. In the Integration Builder menu. Generate Configuration Objects. Click Finish. you must configure it using the following steps: 1. 4. 5.Transferring the Invoice Status Update Integration Scenario Context The first step to configure the integration scenario for the ISU transaction is to transfer to the Integration Directory. Selecting the Model for the Scenario Procedure In the Model Configurator window. then click on the Value List drop down and select Value List <F4. Select the communication component name BS_ASN (sample value). All rights reserved. Next Steps After selecting the component view. and then click Apply to select the unique component view that is selected by default. then click on the Value List drop down and select Value List <F4. 6. 5. you must assign components to the application components of the selected integration scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide 162 © 2015 SAP SE or an SAP affiliate company. 4. In the Model Configurator. click the Select Component View button. Note For Multi ERP implementation. from the selection list and click Apply. In the Assign Components window. click the Assign Component button. Assigning Components for the Invoice Status Update Integration Scenario Procedure 1. 3. Click the Next Role button (the right arrow) to go to the next screen in the window. Click on the row under the Communication Component column. Click on the row under the Communication Component column. 2. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is present. Select the communication component name BS_SAPR3_50 (sample value) from the selection list and click Apply. 8. 7. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. Configuring Integration Scenarios . add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4. select the Business System Components for A2A tab to assign components for Ariba Network. Click the Save Settings button to save the changes. com Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. click the empty Communication Channel cell corresponding to BS_ASN in the Receiver Business System Components table. 4. This is required for the other transactions. you must define sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. requisition request. 163 . receipts. See the graphic below for details: 2. ERP-initiated invoice. and payment proposal. All rights reserved.3 onwards. In the Model Configurator. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. Click the New Communication Channel button (the icon at the top left). then click the Display Input Help drop down list and select Input Help. Select the following Communication Channel Template: ○ Name: CCT_InvoiceStatusUpdateProxy_cXML_Receiver ○ Namespace: http://ariba. Note A sender channel of the SOAP Adapter is required if proxies are being used on single stack (Java only) instance of SAP NetWeaver PI 7. You must assign Communication Channels to set up the connections. click the Configure Connections button.com/xi/ASN/InvoiceStatusUpdateProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. CIX of ariba. Click Continue. In the Connections from Component Assignment tab in the Configure Connection window. 3. Configuring Connections for the Invoice Status Update Integration Scenario Procedure 1.Next Steps After assigning components. and in the next page click the Name field. After the object generation is complete. You can save it. and Interface Determination. Generation creates the configuration objects if they do not yet exist. 3. Click the Activate All Connections button. you must generate the objects. make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select both the active check boxes – Receiver Determination. 4. click Apply to save the new configuration settings. Click Continue. and then click OK in the dialog box. In the Model Configurator. Generating Objects for the Invoice Status Update Integration Scenario Context After making all the configuration settings in the wizard. In the Create Configuration Object window. 6. Close the log that is created without saving. they will be reused and enhanced. Ariba Network Adapter for SAP NetWeaver Setup Guide 164 © 2015 SAP SE or an SAP affiliate company. Click on Start to begin generating objects. If they do already exist. You can also simulate generation for test purposes. Note The communication channels for SAP ERP Sender system are not required. and then click Finish.5. Configuring Integration Scenarios . if required. 7. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. 5. All rights reserved. you can create the communication channel by copying from an already configured channel. click the Create Configuration Object button. 2. modify the channel name to CC_InvoiceStatusUpdateProxy_cXML_Receiver. Click the Save Settings button to save the changes. Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction. if required. Procedure 1. ITEM | | BS_ASN. 4.unbounded". In the Parameters tab. Select the operation mapping IFM_InvStatUpdt_Item_2_cXML and click Apply. Procedure 1. 165 .Configuring Communication Channels for the Invoice Status Update Integration Scenario Context Configure the communication channel CC_InvoiceStatusUpdateProxy_cXML_Receiver under the AR_InvoiceStatusUpdate_ReceiveProxy Configuration Scenario. Under Communication Channel. double-click |BS_ASN|CC_InvoiceStatusUpdateProxy_cXML_Receiver to open it. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. In the Receiver Interfaces section of the Edit Interface Determination window. 3. then click the Value List drop down and select Value List. Configuring Interface Determination Settings for the Invoice Status Update Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. All rights reserved. or right-click and select Open. Save the changes. For more information about the cXML Adapter parameters.. 3. The Multiplicity column displays the value "0. see cXML Adapter Parameters [page 391]. Note If you created the channel by copying an existing channel. click the operation mapping value under the Operation Mapping column. If required. 2. and then click |BS_SAPR3_50 | INVSTATUPDT. Expand Interface Determination. you need to change the request type to StatusUpdateRequest in the Outbound Request Type field. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. 2. Procedure 1. edit the other parameters. the ISU processes the MIRO invoice. All rights reserved. Activating the Invoice Status Update Integration Scenario Procedure Using the Change List tab on the main application screen.5. If you cancel only the MIRO invoice and run the ISU scheduled task. 3. you must cancel the MIRO invoice and its accounting documents. Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings. Run the ISU scheduled task. you might want to cancel or reverse an invoice sent through MIRO that has already been sent to a supplier. Cancel the MIRO invoice in the T-code MR8M. activate all the Change Lists containing the objects created and modified during the component setup. 2. Canceling MIRO Invoices Context In some cases. Save the interface determination settings. Configuring Integration Scenarios . but returns the status as “Processing” as the accounting-related documents still exists for the MIRO task. Cancel the accounting documents associated to the MIRO invoice in the T-Code F-44. To do this. Results This completes the configuration of the ISU transaction in SAP NetWeaver PI. Procedure 1. Ariba Network Adapter for SAP NetWeaver Setup Guide 166 © 2015 SAP SE or an SAP affiliate company. Results The ISU scheduled task picks up the MIRO invoices with the status as “Canceled” and sends it to the supplier. In the first screen of the Transfer Model from ES Repository wizard. see About Configuring the System Landscape Directory [page 61].com/xi/ASN/ERPInvoice ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIX of ariba. 3. and then log in to the Configuration: Integration Builder application. Configure the Integration Scenario. All rights reserved. 4. Configure the Communication Channels. Activate the new configuration. In the Integration Builder menu. select Tools Apply Model from ES Repository .com Note If you are using Ariba Cloud Integration Release 5. To configure the ERP-initiated invoice transaction: 1.0 and earlier. specify the following: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company.ERP-Initiated Invoice Integration Scenario You need to configure the integration scenario for the ERP-initiated invoice transaction in the Integration Directory to be able to run the transaction. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_ERPInvoice_Receive ○ Namespace: http://ariba. From the SAP NetWeaver PI main page. Note Ensure that the Design package is imported into your system and ready before you run these steps. Procedure 1. All the steps of a configuration scenario section must be completed to fully configure a scenario. the integration scenario loaded into the Integration Repository when the design package is imported. and then click the Display Input Help pull-down menu and select Input Help. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. 167 . Select Process Integration Scenario. The following steps assume that the different Business Systems are defined in the SLD. 2. For more information. 3. Transferring the ERP-Initiated Invoice Integration Scenario Context The first step to configure the integration scenario for the ERP-initiated invoice transaction is to transfer to the Integration Directory. click the Name field. select Integration Directory Integration Builder . Generating the configuration objects. Next Steps After selecting the component view. Click Continue. About Configuring the ERP-Initiated Invoice Integration Scenario Once the Integration Scenario is selected. 3. Results Once the transfer is completed. and then click Apply to select the unique component view that is selected by default. 5. you must assign components to the application components of the selected integration scenario.com/xi/ASN/ERPInvoiceProxy 4. Selecting the model. All rights reserved. change the name of the scenario for the Integration Directory. Selecting the Model for the Scenario Procedure In the Model Configurator window. you must configure it using the following steps: 1. the Model Configurator window appears. click the Select Component View button. Click Finish. Ariba Network Adapter for SAP NetWeaver Setup Guide 168 © 2015 SAP SE or an SAP affiliate company. 6. Configuring the sender and receiver relations for individual connections. If required. Configuring Integration Scenarios . 2. Assigning the components. 4. ○ Name: AR_ERPInvoice_ReceiveProxy ○ Namespace: http://ariba. In the Model Configurator. 2. click the Assign Component button. select the Business System Components for A2A tab to assign components for Ariba Network. Note If you have multiple ERP systems. Click the row under the Communication Component column.Assigning Components for the ERP-Initiated Invoice Integration Scenario Context Prior to assigning components. add the multiple communication components defined for your multiple SAP ERP systems by repeating the Step 3 and 4. Click the Next Role button (the right arrow) to go to the next screen on the window. 8. then click the Value List pull-down menu and select Value List <F4>. Click the Save Settings button. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 7. Select the communication component name of the business system for your SAP ERP system from the selection list and click Apply. 6. then click the Value List pull-down menu and select Value List <F4>. Click the row under the Communication Component column. 4. from the selection list and click Apply. Next Steps After assigning components. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is available. All rights reserved. 169 . Select the communication component name of the business system for Ariba Network. In the Assign Components window. 3. you must define sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. Procedure 1. 5. you must transfer the ERP-initated invoice integration scenario and select the model for the scenario. click the empty Communication Channel cell corresponding to the business system for Ariba Network in the Receiver Business System Components table.com/xi/ASN/ERPInvoice ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIX of ariba. 3. Click Continue. specify the following: ○ Name: CCT_ERPInvoiceProxy_cXML_Receiver ○ Namespace: http://ariba. If you have multiple ERP systems. The IDoc receiver Communication Channel needs to be created once for each Business System corresponding to your SAP ERP. All rights reserved. Select the following Communication Channel Template: ○ Name: CCT_ERPInvoice_cXML_Receiver ○ Namespace: http://ariba.com Note If you are using the Ariba Cloud Integration Release 5. In the Model Configurator. 2. On the next page. You must assign Communication Channels to set up the connections. click the Configure Connections button. modify the channel name to CCT_ERPInvoice_cXML_Receiver.com/xi/ASN/ERPInvoiceProxy 6. you must assign components for the integration scenario. Configuring Integration Scenarios . Ariba Network Adapter for SAP NetWeaver Setup Guide 170 © 2015 SAP SE or an SAP affiliate company. In the Connections from Component Assignment tab in the Configure Connection window. In the Connections from Component Assignment tab in the Configure Connection window. and then select Create Communication Channel with Template to start the Create Communication Channel wizard.0 and earlier. click the empty Communication Channel cell corresponding to the name of the business system of your SAP ERP system in the Receiver Business System Components table. 5. repeat Step 6 and 7 for all the entries of the Business Systems corresponding to your SAP ERP instances. 4. you can continue to use it. If a Communication Channel already exists. 8. and then click Finish. specify the channel name as CC_ERPInvoiceProxy_cXML_Receiver .Configuring the Sender and Receiver Relations for Individual Connections for the ERP-Initiated Invoice Integration Scenario Context Prior to configuring the sender and receiver relations. Click the New Communication Channel button (the icon at the top left). Click Continue. Select the communication channel CC_IDoc_Sender corresponding to the SAP ERP Business System from the selection list. 7. click the Name field and then click the Display Input Help pull-down menu and select Input Help. Procedure 1.0 and earlier. Note If you are using the Ariba Cloud Integration Release 5. if required. 10. 9. make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select both the active check boxes – Receiver Determination. and then click OK. and Interface Determination. Generating Objects for the ERP-Initiated Invoice Integration Scenario Context Prior to generating the objects. Click the Save Settings button. 5. All rights reserved. If they already exist. Note The communication channels for SAP ERP Sender system are not required. click Apply to save the new configuration settings. 3. Click on Start to begin generating objects. Tip If you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. In the Model Configurator. In the Create Configuration Object window. Close the log that is created without saving. you can create the communication channel by copying from a channel that has already been configured. you should have configured sender and receiver relations for the integration scenario. if required. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 171 . Click the Activate All Connections button. they are reused and enhanced. 4. Generating the objects creates the configuration objects if they do not yet exist. click the Create Configuration Object button. 2. You can also simulate generation for test purposes. Procedure 1. You can save it. After the object generation is complete. you must assign communication channels for the integration scenario.2. Update the cXML version parameter to the 1. In the Communication Channel list.0 and earlier. double-click |< Name of the Business System for Ariba Network | CCT_ERPInvoice_cXML_Receiver to open it. Ariba Network Adapter for SAP NetWeaver Setup Guide 172 © 2015 SAP SE or an SAP affiliate company. If required.026 version. specify 1. 2. If you are using Ariba Cloud Integration Release 5. configure the communication channel CC_ERPInvoiceProxy_cXML_Receiver under the AR_ERPInvoice_ReceiveProxy Configuration Scenario. you must configure the sender and receiver relations for the individual connections. specify CC_ERPInvoiceProxy_cXML_Receiver. 3. you must change the request type to InvoiceCopyRequestin the Outbound Request Type field. edit the other parameters.0 and earlier. set the parameters in the Authentication section to match your Ariba Network buyer account configuration. 4.Configuring Communication Channels for the ERP-Initiated Invoice Integration Scenario Context Prior to configuring the communication channels. In the Parameters tab.025 version. Note If you created the channel by copying from an existing channel. Configuring Integration Scenarios . If you are using the Ariba Cloud Integration Release 5. Procedure 1. Save the changes.0 and earlier. If you are using the Ariba Cloud Integration Release 5. Prior to configuring the interface determination setting. Configuring Interface Determination Settings for the ERP- Initiated Invoice Integration Scenario Context Configure the interface determination settings to enable mapping enhancements.2. All rights reserved. 0 and earlier. All the steps of a configuration scenario section must be completed to fully configure a scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. and then click |< Name of the Business System for SAP ERP | MIIn_Async_ERPInvoice_cXML | | < Name of the Business System for Ariba Network .unbounded”.0 and earlier. In the Receiver Interfaces section of the Edit Interface Determination window. If you are using the Ariba Cloud Integration Release 5. 5. The Multiplicity column displays the value “0.ITEM. click the operation mapping value under the Operation Mapping column. Note Configuring the Interface Determination is a mandatory step if you must configure the mappings. 2. Receipt Integration Scenario You need to configure the integration scenario for the receipt transaction in the Integration Directory to be able to run the transaction. Save and activate the interface determination settings.. Activating the ERP-Initiated Invoice Integration Scenario Procedure Using the Change List tab on the main application screen. 3. see Receipt Integration Scenario for Corrections and Returns in Receipts [page 179]. choose IFM_Inv_cXML_Item_2_cXML.Procedure 1. 173 . Select the operation mapping IFM_FIDCCP_FIDCCP02_ARBA_2_cXML and click Apply. Then click the Value List pull-down menu and select Value List. Repeat Step 3 to 5 for the operation mapping IFM_GSVERF_GSVERF03_ARBA_2_cXML.CXML. 4. All rights reserved. specify INV. Results This completes the configuration of the ERP-initiated invoice transaction in SAP NetWeaver PI. activate all the Change Lists containing the objects created and modified during the component setup. Expand Interface Determination. To send and receive corrections and returns in receipts. 6. If you are using the Ariba Cloud Integration Release 5. Note ○ Ensure that the design package is imported into your system and ready before you run these steps. see About Configuring the Integration Scenario for Receipts [page 175]. Note Ensure that the Design package is imported into your system and ready before you run these steps. select Tools Apply Model from ES Repository . All rights reserved. For more information. select Integration Directory Integration Builder . In the Integration Builder menu. Configure the Communication Channels. The following steps assume that the different Business Systems are defined in the SLD. see cXML Adapter Parameters [page 391]. Workflow Configuring the receipt integration scenario involves the following steps: 1. For more information. click the Name field. For more information. For more information. 2. For more information. From the SAP NetWeaver PI main page. Select the following Process Integration Scenario from the Enterprise Services Repository screen: Ariba Network Adapter for SAP NetWeaver Setup Guide 174 © 2015 SAP SE or an SAP affiliate company. ○ All the steps of a configuration scenario section must be completed to fully configure a scenario. see Transferring the Integration Scenario for Receipts [page 174]. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Activate the new configuration. Configuring Integration Scenarios . In the first screen of the Transfer Model from ES Repository wizard. 4. see Configuring Communication Channels the Receipts Integration Scenario [page 177]. see Activating the Receipts Integration Scenario [page 178]. and then login into the Configuration: Integration Builder application. Procedure 1. Transferring the Integration Scenario for Receipts Context The first step to support returns and corrections in receipts is to configure the Receipt transaction and transfer the integration scenario to the Integration Builder. Configure the Integration Scenario. Select Process Integration Scenario. The following steps assume that the different Business Systems are defined in the SLD. then click the Display Input Help drop down list and select Input Help. 3. 3. The integration scenario is loaded into the Integration Repository when the design package is imported. you must configure it using the following steps: 1. the Model Configurator window appears. Click Continue. Select the Model. 5. 175 . you must assign components to the application components of the selected integration scenario. Assign Components.com 4. change the name of the scenario for the Integration Directory 6. and then click Apply to select the unique component view that is selected by default. Selecting the Model for the Scenario Procedure In the Model Configurator window. 3. Click Finish. 2. All rights reserved. If required. Next Steps After selecting the component view. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 4. Generate Configuration Objects. Results After the integration scenario transfer is completed.com/xi/ASN/ReceiptProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. click the Select Component View button. Configure Connections. CIX of ariba. ○ Name: AR_Receipt_Receive_Proxy ○ Namespace: http://ariba. About Configuring the Integration Scenario for Receipts Once the Integration Scenario is selected. 3. In the Model Configurator. Note If you have multiple ERP systems. CIX of ariba. Click the row under the Communication Component column. then click the Value List pull-down menu and select Value List <F4. add the multiple communication components defined for your multiple SAP ERP systems by repeating the Step# 3 and 4. then click the Value List pull-down menu and select Value List <F4. In the Assign Components window. 5. 6. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. click the Configure Connections button. All rights reserved. Select the communication component name for the business system of your SAP ERP. 3. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. You must assign Communication Channels to set up the connections. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present.com/xi/ASN/ReceiptProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. On the next page. click the Assign Component button. 2. Click the row under the Communication Component column. Click Continue. select the Business System Components for A2A tab to assign components for Ariba Network. modify the channel name to CC_ERPReceiptProxy_cXML_Receiver. 4. from the selection list and click Apply. Configuring Integration Scenarios . Click Continue. 5. Select the following Communication Channel Template: ○ Name: CCT_ERPReceiptProxy_cXML_Receiver ○ Namespace: http://ariba. Configuring Connections for the Receipts Integration Scenario Procedure 1.Assigning Components for the Receipts Integration Scenario Procedure 1. 2. click the empty Communication Channel cell corresponding to the business system for Ariba Network in the Receiver Business System Components table. In the Connections from Component Assignment tab in the Configure Connection window. Click the Next Role button (the right arrow) to go to the next screen on the window. 4. Ariba Network Adapter for SAP NetWeaver Setup Guide 176 © 2015 SAP SE or an SAP affiliate company. In the Model Configurator. Click the New Communication Channel button (the icon at the top left). 7. and then click Finish. Select the communication component name for the business system for Ariba Network. click the Name field and then click the Display Input Help pull-down menu and select Input Help.com 6. from the selection list and click Apply. Configuring Communication Channels the Receipts Integration Scenario Context Configure the communication channel CC_ERPReceiptProxy_cXML_Receiver under the AR_Receipt_Receive_Proxy Configuration Scenario. click Apply to save the new configuration settings. Click Start to begin generating objects 5. do the following: ○ Click Generation in the General section. All rights reserved. and then click OK in the dialog box. Close the log that is created without saving. if required. 8. In the Create Configuration Object window. In the Model Configurator. they are reused and enhanced. click the Create Configuration Object button. and Interface Determination check boxes in the Scope of Generation section. Tip If you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction. 3. if required. Generating Objects for the Receipts Integration Scenario Context Generating the objects creates the configuration objects if they do not yet exist. You can save it. 177 . 4. Click the Activate All Connections button. The text box already contains an object name that you can use or modify. Click the Save Settings button. you can create the communication channel by copying from a channel that has already been configured. After the object generation is complete. Note The communication channels for SAP ERP Sender system are not required. ○ Select the Receiver Determination. You can also simulate generation for test purposes Procedure 1. 7. Click Create New in the Change List for Generated Objects section. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. If they already exist. 2. 025 version. 3. Save the changes. 3. Ariba Network Adapter for SAP NetWeaver Setup Guide 178 © 2015 SAP SE or an SAP affiliate company. In the Receiver Interfaces section of the Edit Interface Determination window. then click the Value List drop down and select Value List. Save the interface determination settings. If required. activate all the Change Lists containing the objects created and modified during the component setup. Expand Interface Determination..Procedure 1. Procedure 1. 6. 4. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. and then click |BS_SAPR3_50 | RECEIPT | | BS_ASN. All rights reserved. 5. Under Communication Channel. 2. double-click |B Name of the Business System for Ariba Network | CC_ERPReceiptProxy_cXML_Receiver to open it. The Multiplicity column displays the value "0. Specify the Fulfill. Select the operation mapping IFM_Receipt_cXML and click Apply.2. In the Parameters tab. 5. edit the other parameters. Configuring Integration Scenarios . Activating the Receipts Integration Scenario Procedure Using the Change List tab on the main application screen. If you created the channel by copying an existing channel. 4. Configuring Interface Determination Settings for the Receipts Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. 2.dtd in the DTD field. click the operation mapping value under the Operation Mapping column.unbounded". you need to change the request type to ReceiptRequest in the Outbound Request Type field. Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings. Update the cXML version parameter to the 1. The cXML ReceiptRequest document sent to suppliers on Ariba Network contains detailed information on the number of goods returned. and 105 to send received quantities ● 102 to send corrections on the received quantity ● 122. The source code of the program is provided in the SAP Note. then to ensure that receipts are pulled from your SAP ERP system. The following movement types support returns and corrections in receipts: ● 101. You also need to create and execute a new program Z_1811043_ADJUST_EXTRACTOR in your SAP PI system. The type attribute in the ReceiptItem stores the “Received” or “Returned” values. Based on the information in the receipt. 124. 103. you must implement SAP note 1811043.Results This completes the configuration of the receipt transaction in SAP NetWeaver PI. Receipt Integration Scenario for Corrections and Returns in Receipts This section has the following topics: ● Limitations [page 180] ● Data Flow Overview [page 180] ● cXML Changes to Support Returns and Corrections in Receipts [page 181] Buyers using the Ariba Network Adapter for SAP NetWeaver can send receipts having returns and corrections for the line items shipped against purchase orders.1 EHP1 Note If you are using SAP NetWeaver 7. received. and 161 to send returned quantities ● 123 to send corrections on the returned quantities Buyers and suppliers on Ariba Network can view the details on the returns and corrections for line items in the purchase order on the purchase order details and the order history pages.1 EHP1. Additional Receipts Integration Requirement for SAP NetWeaver 7. the purchase order header status displays if the goods were fully received or partially received. Create the program in SE38 and execute the same. 179 . or any corrections made against them. The line items in Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. A negative value in the line item quantity denotes that there was a correction to the items received or returned. All rights reserved. Positive value Received Received Negative value Received Corrected against the received quantity Positive value Returned Returned Negative value Returned Corrected against the returned quantity Note Buyers can create receipts only for standard purchase orders.2. For example. the receipt integration has the following limitations: ● Buyers cannot create receipts for blanket purchase orders.. Configuring Integration Scenarios .. Requirements You must have the cXML version 1. The existing /ARBA/RECEIPT_EXPORT program is no longer used to process receipts that contain returns and corrections. Limitations When you send or receive receipts with corrections and returns. Ensure that you make the necessary changes to the cXML Version parameter in the Communication Channel..0 for returns and corrections. All rights reserved.025 and configure your SAP system to send receipts with returns and corrections against purchase orders.the purchase order on Ariba Network also display the number of items received or returned. Data Flow Overview The following is an example of how receipts with returns and corrections flow from a buyer’s ERP system to Ariba Network: ● An ERP buyer creates a purchase order having the following line items and sends it to the supplier on Ariba Network: ○ Line item 1 having a quantity of 20 ○ Line item 2 having a quantity of 30 ● The supplier confirms the purchase order and ships the goods to the buyer for the following: ○ Line item 1 having a quantity of 15 ○ Line item 2 having a quantity of 30 Ariba Network Adapter for SAP NetWeaver Setup Guide 180 © 2015 SAP SE or an SAP affiliate company. ● Ariba Network Adapter for SAP NetWeaver does not support receipts created prior to Cloud Integration Release 4. here is how items are calculated as received or returned: Line Item Quantity Contains Receipt Type Indicates the items have been. You must import the CDF_Fulfill_XSD structure that contains the type attribute in the ReceiptItem element. The existing quantity attribute supports positive and negative values while specifying returns and corrections in receipts. ○ The type attribute stores information on the returns and corrections in receipts. ● The buyer receives the goods and creates a receipt for the following items received: ○ Received quantity 15 for line item 1 ○ Correction of quantity 5 that were not received for line item 1 ○ Received quantity 30 for line item 2 ○ Returned quantity 10 for line item 2 ● The ReceiptItem in the cXMLReceiptRequest document sent to the supplier on Ariba Network contains the following information: ○ <ReceiptItem receiptLineNumber="1" quantity="15" type="received"> ○ <ReceiptItem receiptLineNumber="1" quantity="-5" type="received"> ○ <ReceiptItem receiptLineNumber="2" quantity="20" type="received"> ○ <ReceiptItem receiptLineNumber="2" quantity="-10" type="returned"> cXML Changes to Support Returns and Corrections in Receipts The following changes have been made to support returns and corrections in receipts: ● A new structure has been added to cXML to support returns and corrections in receipts. All rights reserved. 181 . ● The mappings files have been enhanced to support the following changes: ○ To support different goods movement types: /ns0:Messages/ns0:Message2/cXML/Request/ReceiptRequest/ReceiptOrder/ReceiptItem/ ○ To support positive and negative quantity: @quantity attribute ○ To support received and returned values: @type attribute ○ To support multiple purchase orders: /ns0:Messages/ns0:Message2/cXML/Request/ReceiptRequest/ReceiptOrder /ns0:Messages/ns0:Message2/cXML/Request/ReceiptRequest/ReceiptOrder/ ReceiptOrderInfo/OrderIDInfo/@orderID /ns0:Messages/ns0:Message2/cXML/Request/ReceiptRequest/ReceiptOrder/ ReceiptOrderInfo/OrderIDInfo/IdReference/@domain /ns0:Messages/ns0:Message2/cXML/Request/ReceiptRequest/ReceiptOrder/ ReceiptOrderInfo/OrderIDInfo/IdReference/@identifier Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. ● Buyers can create receipts against multiple purchase orders. see Activating the Receipts Integration Scenario [page 178]. All rights reserved. you specify which account assignment object is to be charged using the account assignment category. you must perform the following tasks: 1. 2. Add the code in the BADI implementation for MM Multiple Account Assignments Related Information Activating the MM Multiple Account Assignments Enterprise Business Function [page 183] Adding the Code in the BADI Implementation for MM Multiple Account Assignments [page 184] Ariba Network Adapter for SAP NetWeaver Setup Guide 182 © 2015 SAP SE or an SAP affiliate company. For example. Activate the new configuration. Receipt Integration Scenario for Purchase Orders with Multiple Accounting Assignments Buyers using Ariba Procure to Pay integrated with SAP ERP can send receipts for purchase orders with multiple accounting assignments to the SAP ERP. see Transferring the Integration Scenario for Receipts [page 174]. see Configuring Communication Channels the Receipts Integration Scenario [page 177]. 4. For more information. Configure the Communication Channels. Configure the Integration Scenario. see About Configuring the Integration Scenario for Receipts [page 175]. For more information.Configuring the Receipt Integration Scenario to Support Returns and Corrections Procedure 1. To send multiple receipts for purchase orders with multiple accounting assignments. Configuring Integration Scenarios . For more information. Activate the MM Multiple Account Assignments enterprise business function 2. 3. For more information. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. Multiple account assignment feature on the SAP ERP system allows you to apportion the cost of a material covered by a purchase order among your own cost center and several others. Click Save. Go to Tcode SPRO and then in the SAP reference IMG navigate to SAP Customizing Implementation Guide Activate Business Functions . the following changes apply: ● For the account assignment category that you have enabled with multiple account assignment functionality. Results Now. All rights reserved. For example. the purchase order line item can be GR-valuated thereby allowing the goods receipt of that line to pass a value to the Financial Accounting. ● You can use the multiple account assignment functionality for delivery costs. The check box GR non-valuated is now not active. 3. Procedure 1. 183 . if you enter a freight condition cost on the line item of a purchase order. Select the business function LOG_MM_MAA_1 and click Activate Changes. when you create a purchase requisition or purchase order. Related Information Adding the Code in the BADI Implementation for MM Multiple Account Assignments [page 184] Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. you can enter amounts into the account assignment lines.Activating the MM Multiple Account Assignments Enterprise Business Function Prerequisites SAP ERP 6.0 (Enhancement Pack 4 or higher) must be installed on your system. ● Under the Account Assignment tab of the purchase order line item. 2. the cost of freight applied to split product items is proportional to the cost of the split product items. READ TABLE gritems INTO wa_gritems index 1. wa_ekkn type ekkn. endif. Configuring Integration Scenarios . Next Steps Run the program /ARBA/CR_GR_CREATE to verify that the receipts are posted accurately to SAP ERP. endloop. wa_gritems type /ARBA/GOODS_RECEIPTS_ITEM. All the steps of a configuration scenario section must be completed to fully configure a scenario. loop at t_ekkn into wa_ekkn.wa_gritems. under the method GOODS_RECEIPTS_BDCDATA: DATA : t_ekkn type table of ekkn. refresh : t_ekkn.Adding the Code in the BADI Implementation for MM Multiple Account Assignments Add the following code. DATA : lv_rec type I. PERFORM fill_bdc_table IN PROGRAM /ARBA/SAPLGOODSRECEIPTS_CREATE USING: '' 'bdc_okcode' '/0'. Related Information Activating the MM Multiple Account Assignments Enterprise Business Function [page 183] Receipt Integration Scenario for Purchase Orders with Multiple Accounting Assignments [page 182] Payment Proposal Integration Scenario You need to configure the integration scenario for the payment proposal transaction in the Integration Directory to be able to run the transaction. if t_ekkn[] is not INITIAL and lv_rec GT 1. DESCRIBE TABLE t_ekkn LINES lv_rec. Ariba Network Adapter for SAP NetWeaver Setup Guide 184 © 2015 SAP SE or an SAP affiliate company. select * from ekkn into table t_ekkn where ebeln = wa_gritems-ebeln and ebelp = itemnumber. PERFORM fill_bdc_table IN PROGRAM /ARBA/SAPLGOODSRECEIPTS_CREATE USING: 'X' 'SAPMM07M' '0210'. clear : lv_rec. All rights reserved. see cXML Adapter Parameters [page 391]. Activate the new configuration. change the name of the scenario for the Integration Directory 6. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_PaymentProposal_Receive_Proxy ○ Namespace: http://ariba. Select Process Integration Scenario. and then login into the Configuration: Integration Builder application. 4. In the first screen of the Transfer Model from ES Repository wizard. 2. Click Continue. 5. In the Integration Builder menu. 3.com/xi/ASN/PaymentProposalProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. For more information. Transferring the Payment Proposal Integration Scenario Context The first step to configure the integration scenario for the payment proposal transaction is to transfer to the Integration Directory. From the SAP NetWeaver PI main page. 185 . Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. the Model Configurator window appears. Note Ensure that the Design package is imported into your system and ready before you run these steps. click the Name field. 2.com 4. select Integration Directory Integration Builder . If required. 3. Configure the Integration Scenario. CIX of ariba. All rights reserved. To configure the payment proposal transaction: 1. The following steps assume that the different Business Systems are defined in the SLD. the integration scenario loaded into the Integration Repository when the Design package is imported. Click Finish. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. select Tools Apply Model from ES Repository . Configure the Communication Channels. Results Once the transfer is completed. then click the Display Input Help drop down list and select Input Help. Procedure 1. Generate Configuration Objects. Note For Multi ERP implementation. In the Assign Components window. 2. Select the communication component name BS_ASN (sample value). click the Select Component View button. you must assign components to the application components of the selected integration scenario. Click on the row under the Communication Component column. Configuring Integration Scenarios . Click the Save Settings button to save the changes. add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4. In the Model Configurator. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. Assign Components. click the Assign Component button. 3. from the selection list and click Apply. 6. Select the communication component name BS_SAPR3_50 (sample value) from the selection list and click Apply. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is present.About Configuring the Payment Proposal Integration Scenario Once the Integration Scenario is selected. Configure Connections. you must configure it using the following steps: 1. 2. 8. Ariba Network Adapter for SAP NetWeaver Setup Guide 186 © 2015 SAP SE or an SAP affiliate company. 5. then click on the Value List drop down and select Value List <F4. Select Model. then click on the Value List drop down and select Value List <F4. and then click Apply to select the unique model that is selected by default. 7. All rights reserved. 4. Assigning Components for the Payment Proposal Integration Scenario Procedure 1. Click on the row under the Communication Component column. In the Model Configurator window. select the Business System Components for A2A tab to assign components for Ariba Network. 4. 3. After selecting the model. Click the Next Role button (the right arrow) to go to the next screen in the window. and then click OK in the dialog box.com 5. modify the channel name to CC_PaymentProposalProxy_cXML_Receiver. Note The communication channels for SAP ERP Sender system are not required. Click Continue. 187 . you can create the communication channel by copying from an already configured channel. Configuring Connections for the Payment Proposal Integration Scenario Procedure 1.com/xi/ASN/PaymentProposalProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. 7. Click the New Communication Channel button (the icon at the top left). CIX of ariba. click the empty Communication Channel cell corresponding to BS_ASN in the Receiver Business System Components table. 3. 4. Click the Save Settings button to save the changes. You must assign Communication Channels to set up the connections. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 2. Click Continue. Select the following Communication Channel Template: ○ Name: CCT_PaymentProposalProxy_cXML_Receiver ○ Namespace: http://ariba. Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction. 6. you must define sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. and in the next page click the Name field.Next Steps After assigning components. All rights reserved. and then click Finish. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. In the Model Configurator. then click the Display Input Help drop down list and select Input Help. click the Configure Connections button. Click the Activate All Connections button. In the Connections from Component Assignment tab in the Configure Connection window. Click on Start to begin generating objects.Generating Objects for the Payment Proposal Integration Scenario Context After making all the configuration settings in the wizard. After the object generation is complete. or right-click and select Open. Configuring Communication Channels for the Payment Proposal Integration Scenario Context Configure the communication channel CC_PaymentProposalProxy_cXML_Receiver under the AR_PaymentProposal_Receive_Proxy Configuration Scenario. 3. if required. if required. make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select both the active check boxes – Receiver Determination. In the Create Configuration Object window. Note If you created the channel by copying an existing channel. Generation creates the configuration objects if they do not yet exist. You can also simulate generation for test purposes. 5. If they do already exist. click Apply to save the new configuration settings. Configuring Integration Scenarios . Procedure 1. click the Create Configuration Object button. you must generate the objects. 4. In the Model Configurator. Procedure 1. 2. 2. In the Parameters tab. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. Under Communication Channel. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. and Interface Determination. All rights reserved. you need to change the request type to PaymentProposalRequest in the Outbound Request Type field. double-click |BS_ASN|CC_PaymentProposalProxy_cXML_Receiver to open it. Close the log that is created without saving. You can save it. they will be reused and enhanced. Ariba Network Adapter for SAP NetWeaver Setup Guide 188 © 2015 SAP SE or an SAP affiliate company. .If required. edit the other parameters. 189 . 2.dtd in the DTD field. see cXML Adapter Parameters [page 391].unbounded". Activating the Payment Proposal Integration Scenario Procedure Using the Change List tab on the main application screen. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. activate all the Change Lists containing the objects created and modified during the component setup. Results This completes the configuration of the payment proposal transaction in SAP NetWeaver PI.ITEM | | BS_ASN. 5. The Multiplicity column displays the value "0. Expand Interface Determination. 4. Specify the PaymentRemittance. click the operation mapping value under the Operation Mapping column. For more information about the cXML Adapter parameters. Configuring Interface Determination Settings for the Payment Proposal Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. Save the interface determination settings. All rights reserved. Select the operation mapping IFM_PaymentProposal_Item_2_cXML and click Apply. Save the changes. Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings. 3. Procedure 1. 4. 3. then click the Value List drop down and select Value List. In the Receiver Interfaces section of the Edit Interface Determination window. and then click |BS_SAPR3_50 | PAYMENTPROPOSAL. see About Configuring the System Landscape Directory [page 61]. see cXML Adapter Parameters [page 391].Design. must be set with the required value. then the payment proposal is again sent as New to Ariba Network. Requisition Request Integration Scenario You need to configure the integration scenario for the requisition request transaction in the Integration Directory to be able to run the transaction.relaxedOperationCheck. All the steps of a configuration scenario section must be completed to fully configure a scenario. Quick enablement is achieved by adding the Email ID to the relevant structures in SAP NetWeaver PI and the SAP ERP system. ● SAP NetWeaver PI can be installed as single stack (Java only) or dual stack (ABAP and Java) from version 7. Ariba Network Adapter for SAP NetWeaver Setup Guide 190 © 2015 SAP SE or an SAP affiliate company. For information on the ABAP programs created for the above mentioned outbound transactions. this payment proposal is rejected by Ariba Network.tpz file into your SAP NetWeaver PI system. supplier enablement is initiated even if no relationship is maintained in Ariba Network for SAP Vendor and AN Vendor. All rights reserved.3 onwards. Note Ensure that the Design package is imported into your system and ready before you run these steps. However. For more information. Enabling Quick Enablement for Payment Proposal Transactions Quick enablement is supported for the payment proposal transaction. However. Receiver Determination.com and imported them into your SAP ERP system. ● Downloaded the relevant SAP transport requests from connect. in case of dual stack instance. for an invoice with a payment block. If a user removes the payment block for the invoice. If you are configuring the above mentioned integration scenarios in the single stack Java only instance. see cXML Adapter Parameters [page 391]. Configuring Integration Scenarios . The following steps assume that the different Business Systems are defined in the SLD. To ensure that the payment proposal is not rejected by Ariba Network. when a payment proposal is sent to Ariba Network. For more information. as part of generation of objects. To enable quick enablement. ensure that you have: ● Imported the AribaNetworkAdapterSAPNetweaver. and Sender Agreement. Receiver Agreement. the Extrinsic @name=Ariba. the payment proposal for this invoice is sent as Hold to Ariba Network. the Config wizard generates only one object called Integrated Configuration. as part of generation of objects. You also need configure proxy in your SAP ERP system.ariba. Note ● In the production environment. As a result. the Config wizard generates four objects. Interface Determination. which is part of the mappings. 2. Click Continue. All rights reserved. Procedure 1. Results Once the transfer is completed. Configure the Communication Channels. then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_Requisition_Request ○ Namespace: http://ariba. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. the Model Configurator window appears. 4. From the SAP NetWeaver PI main page. 5. If required. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. Activate the new configuration. Transferring the Requisition Request Integration Scenario Context The first step to configure the integration scenario for the ISU transaction is to transfer to the Integration Directory. 2. Select Process Integration Scenario.com 4. 3. Configure the Integration Scenario. In the Integration Builder menu. the integration scenario loaded into the Integration Repository when the Design package is imported. Click Finish. 191 . In the first screen of the Transfer Model from ES Repository wizard. and then login into the Configuration: Integration Builder application. 3. select Tools Apply Model from ES Repository . change the name of the scenario for the Integration Directory 6. click the Name field.To configure the requisition request transaction: 1.com/xi/ASN/Requisition ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. select Integration Directory Integration Builder . CIX of ariba. In the Model Configurator. Click on the row under the Communication Component column. All rights reserved. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4. 2. you must assign components to the application components of the selected integration scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide 192 © 2015 SAP SE or an SAP affiliate company. Selecting the Model for the Scenario Procedure In the Model Configurator window. In the Assign Components window. Generate Configuration Objects. 3.About Configuring the Requisition Request Integration Scenario Once the Integration Scenario is selected. 2. 3. 4. Select the communication component name BS_SAPR3_50 (sample value) from the selection list and click Apply. click the Select Component View button. you must configure it using the following steps: 1. then click on the Value List drop down and select Value List <F4. Assigning Components for the Requisition Request Integration Scenario Procedure 1. Note For Multi ERP implementation. Configure Connections. 4. select the Business System Components for A2A tab to assign components for Ariba Network. Next Steps After selecting the component view. Configuring Integration Scenarios . Assign the Model. click the Assign Component button. and then click Apply to select the unique component view that is selected by default. Assign Components. Note The communication channels for SAP ERP Sender system are not required. and in the next page click the Name field. Next Steps After assigning components. Select the following Communication Channel Template: ○ Name: CCT_InvoiceStatusUpdateProxy_cXML_Receiver ○ Namespace: http://ariba. Click the Next Role button (the right arrow) to go to the next screen in the window. 6. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. All rights reserved. Click Continue. 5. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is present. 2. Configuring Connections for the Requisition Request Integration Scenario Procedure 1. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. In the Connections from Component Assignment tab in the Configure Connection window. then click on the Value List drop down and select Value List <F4. then click the Display Input Help drop down list and select Input Help. 3. Click the New Communication Channel button (the icon at the top left). click the empty Communication Channel cell corresponding to BS_ASN in the Receiver Business System Components table. and then click OK in the dialog box. Click the Save Settings button to save the changes. you must define sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. 4.com 5. click the Configure Connections button. You must assign Communication Channels to set up the connections. Click on the row under the Communication Component column. 193 . Select the communication component name BS_ASN (sample value). 6. 7. Click Continue.com/xi/ASN/Requisition ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. and then click Finish. you can create the communication channel by copying from an already configured channel. CIX of ariba. 8. modify the channel name to CC_InvoiceStatusUpdateProxy_cXML_Receiver. from the selection list and click Apply. In the Model Configurator. Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction. Click the Activate All Connections button. 4. click Apply to save the new configuration settings. they will be reused and enhanced. All rights reserved. Procedure 1. Generation creates the configuration objects if they do not yet exist. Close the log that is created without saving. Ariba Network Adapter for SAP NetWeaver Setup Guide 194 © 2015 SAP SE or an SAP affiliate company. double-click |BS_ASN|CC_InvoiceStatusUpdateProxy_cXML_Receiver to open it. 3. click the Create Configuration Object button. you must generate the objects. In the Model Configurator. 5. In the Create Configuration Object window. make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select both the active check boxes – Receiver Determination. You can also simulate generation for test purposes. Configuring Communication Channels for the Requisition Request Integration Scenario Context Configure the communication channel CC_InvoiceStatusUpdateProxy_cXML_Receiver under the AR_InvoiceStatusUpdate_ReceiveProxy Configuration Scenario. If they do already exist. 2. Configuring Integration Scenarios . or right-click and select Open. Click the Save Settings button to save the changes. if required. You can save it. if required.7. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. Under Communication Channel. Click on Start to begin generating objects. Generating Objects for the Requisition Request Integration Scenario Context After making all the configuration settings in the wizard. After the object generation is complete. Procedure 1. and Interface Determination. you need to change the request type to StatusUpdateRequest in the Outbound Request Type field. The Multiplicity column displays the value "0. All rights reserved. In the Receiver Interfaces section of the Edit Interface Determination window. Configuring Interface Determination Settings for the Requisition Request Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. 3.ITEM | | BS_ASN. then click the Value List drop down and select Value List. In the Parameters tab.. Select the operation mapping IFM_InvStatUpdt_Item_2_cXML and click Apply. 3. Note If you created the channel by copying an existing channel. Save the interface determination settings. activate all the Change Lists containing the objects created and modified during the component setup. For more information about the cXML Adapter parameters.unbounded". 195 . Expand Interface Determination. Save the changes. Activating for the Requisition Request Integration Scenario Procedure Using the Change List tab on the main application screen. see cXML Adapter Parameters [page 391]. and then click |BS_SAPR3_50 | INVSTATUPDT. edit the other parameters. Procedure 1. 5. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. 2. Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings. 2. click the operation mapping value under the Operation Mapping column. 4. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. If required. Procedure 1. 4. To configure Request for Quotation: 1. 2. Configure the Integration Scenario. From the SAP NetWeaver PI main page. Activate the new configuration. select Integration Directory Integration Builder . the integration scenario loaded into the Integration Repository when the Design package is imported. For more information. In the Integration Builder menu. Select Process Integration Scenario. All the steps of a configuration scenario section must be completed to fully configure a scenario. Request for Quotation Integration Scenario You need to configure the integration scenario for the Request for Quotation transaction in the Integration Directory to be able to run the transaction. see the Ariba Sourcing Integration to SAP ERP. click the Name field. Note To completely enable creation and cancellation of sourcing requests the SAP ERP administrator must also install SAP ERP enhancements. Configure the Communication Channels. Transferring the Quotation Integration Scenario Context The first step to configure the integration scenario for the Request for Quotation transaction is to transfer to the Integration Directory. All rights reserved. In the first screen of the Transfer Model from ES Repository wizard. 3.Results This completes the configuration of the ISU transaction in SAP NetWeaver PI. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. select Tools Apply Model from ES Repository . then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_QuoteRequest_Receive Ariba Network Adapter for SAP NetWeaver Setup Guide 196 © 2015 SAP SE or an SAP affiliate company. and then login into the Configuration: Integration Builder application. 3. Configuring Integration Scenarios . 2. CI5 of ariba. Generate Configuration Objects. 197 . Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. About Configuring the Quotation Integration Scenario Context Once the Integration Scenario is selected. Select Model. Selecting the Model for the Scenario Procedure In the Model Configurator window. change the name of the scenario for the Integration Directory 6. the Model Configurator window appears. Configure Connections. click the Select Component View button. Click Continue. 3. Results Once the transfer is completed.com/xi/ASN/QuoteRequest ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. Assign Components. you must assign components to the application components of the selected integration scenario. All rights reserved. and then click Apply to select the unique component view that is selected by default. If required. you must configure it using the following steps: Procedure 1. 2.com 4. Click Finish. ○ Namespace: http://ariba. 4. Next Steps After selecting the component view. 5. Click on the row under the Communication Component column. 3. Select the communication component name BS_ASN. Next Steps After assigning components. 2. You must assign Communication Channels to set up the connections. click the Assign Component button. 8.Assigning Components for the Quotation Integration Scenario Procedure 1. In the Assign Components window. you must define sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. Configuring Integration Scenarios . 2. Select the communication component name BS_SAPR3_50. 7. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is present. 5. click the Configure Connections button. from the selection list and click Apply. then click on the Value List drop down and select Value List <F4. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. Click the New Communication Channel button (the icon at the top left). and then select Create Communication Channel with Template to start the Create Communication Channel wizard. then click on the Value List drop down and select Value List <F4. In the Model Configurator. Select the following Communication Channel Template: Ariba Network Adapter for SAP NetWeaver Setup Guide 198 © 2015 SAP SE or an SAP affiliate company. then click the Display Input Help drop down list and select Input Help. Click Continue. click the empty Communication Channel cell corresponding to BS_ASN in the Receiver Business System Components table. 4. add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4. from the selection list and click Apply. Click the Next Role button (the right arrow) to go to the next screen in the window. 6. Configure Connections for the Quotation Integration Scenario Procedure 1. 4. All rights reserved. and in the next page click the Name field. select the Business System Components for A2A tab to assign components for Ariba Network. Click the Save Settings button to save the changes. Note For Multi ERP implementation. In the Model Configurator. In the Connections from Component Assignment tab in the Configure Connection window. Click on the row under the Communication Component column. 3. you can create the communication channel by copy from a channel already configured. In the Create Configuration Object window. if required. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. CI5 of ariba. You can also simulate generation for test purposes. and Interface Determination. All rights reserved. 4. they will be reused and enhanced. 6. If they do already exist. After the object generation is complete. Procedure 1. click Apply to save the new configuration settings. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. In the Model Configurator. you must generate the objects. ○ Name: CCT_Quote_cXML_Receiver ○ Namespace: http://ariba. Click Continue.com/xi/ASN/QuoteRequest ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. Note The communication channels for SAP ERP Sender system are not required. click the Create Configuration Object button. make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select both the active check boxes – Receiver Determination. Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction. if required. 2. Click the Save Settings button to save the changes. modify the channel name to CC_QuoteRequest_cXML_Receiver. Generation creates the configuration objects if they do not yet exist. 7. Generating Objects for the Quotation Integration Scenario Context After making all the configuration settings in the wizard. 199 . Click on Start to begin generating objects. Close the log that is created without saving. Click the Activate All Connections button.com 5. and then click Finish. You can save it. and then click OK in the dialog box. 5. 3. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration.. Select the operation mapping IFM_REQOTE_ORDERS05_ARBA_RFQ_2_cXML and click Apply. In the Receiver Interfaces section of the Edit Interface Determination window.ORDERS05. In the Parameters tab. double-click |BS_ASN|CC_QuoteRequest_cXML_Receiver to open it.unbounded". you need to change the request type to QuoteRequest in the Outbound Request Type field. Save the changes. 2. 4. Under Communication Channel. All rights reserved. and then click BS_SAPR3_50 | | REQOTE. Configuring Interface Determination Setting for the Quotation Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. 2. or right-click and select Open. Ariba Network Adapter for SAP NetWeaver Setup Guide 200 © 2015 SAP SE or an SAP affiliate company. Note If you created the channel by copy from an existing channel. Procedure 1. Expand Interface Determination.Configuring Communication Channels for the Quotation Integration Scenario Context Configure the communication channel CC_QuoteRequest_cXML_Receiver under the AR_QuoteRequest_Receive Configuration Scenario. 3. click the operation mapping value under the Operation Mapping column. edit the other parameters. Configuring Integration Scenarios . Procedure 1. If required. 3. The Multiplicity column displays the value "0. then click the Value List drop down and select Value List./ARBA/RFQ | | BS_ASN. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings. Activate the new configuration. 3. Activating the Quotation Integration Scenario Procedure Using the Change List tab on the main application screen. 4. Results This completes the configuration of the Quote Request transaction in SAP NetWeaver PI. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. To configure Sourcing Award to Contract: 1. 2. Save the interface determination settings. Sourcing Award to Contract Integration You need to configure the integration scenario for Sourcing Award to Contract transaction in the Integration Directory to be able to run the transaction. All rights reserved. Configure the Communication Channels. 5. activate all the Change Lists containing the objects created and modified during the component setup. 201 . All the steps of a configuration scenario section must be completed to fully configure a scenario. Configure the Integration Scenario. Transferring the Sourcing Award to Contract Integration Scenario The first step to configure the integration scenario for the Sourcing Award to Contract transaction is to transfer to the Integration Directory. click the Name field. Click Finish. the integration scenario loaded into the Integration Repository when the Design package is imported. and then login into the Configuration: Integration Builder application. All rights reserved. If required. In the first screen of the Transfer Model from ES Repository wizard. In the Integration Builder menu. From the SAP NetWeaver PI main page. Procedure 1. Ariba Network Adapter for SAP NetWeaver Setup Guide 202 © 2015 SAP SE or an SAP affiliate company. the Model Configurator window appears. Click Continue. 3. Select Process Integration Scenario. 5. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_QuoteMessage_Send ○ Namespace: http://ariba.com/xi/ASN/QuoteMessage ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. select Integration Directory Integration Builder . Results Once the transfer is completed. then click the Display Input Help drop down list and select Input Help. 2. change the name of the scenario for the Integration Directory 6.com 4. select Tools Apply Model from ES Repository . CI5 of ariba. Configuring Integration Scenarios . Procedure 1. Assign Components. 203 . Selecting the Model The first integration scenario configuration step is to select a model. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. Select Model. All rights reserved. 2. 4.About Configuring the Sourcing Award to Contract Integration Scenario Context Once the Integration Scenario is tranferred. you must configure it using the following steps: Procedure 1. Click Select Component View in the Model Configurator. Click Apply to select the unique model that is selected by default. 2. Generate Configuration Objects. Configure Connections. Next Steps Assign components to the application components of the selected integration scenario. 3. Assigning Components to the Sourcing Award to Contract Integration Scenario The second integration scenario configuration step is to assign components. Procedure 1. click the Assign Component button. 8. Select the communication component name BS_FILE. 2. Click the Save Settings button to save the changes. Configuring Integration Scenarios . 3. Click on the row under the Communication Component column. from the selection list and click Apply. 6. In the Model Configurator. 5. In the Assign Components window. Select the communication component name BS_SAPR3_50. All rights reserved. select the Business System Components for A2A tab to assign components for Ariba Network. Next Steps Define sender/receiver relations for the individual connections in the Integration Scenario and specify Communication Channels that are relevant for the sender/receiver relations. then click on the Value List drop down and select Value List <F4. 7. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. then click on the Value List drop down and select Value List <F4. 4. Ariba Network Adapter for SAP NetWeaver Setup Guide 204 © 2015 SAP SE or an SAP affiliate company. Click the Next Role button (the right arrow) to go to the next screen in the window. Note For Multi ERP implementation. from the selection list and click Apply. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is present. add the multiple communication components defined for multiple SAP ERP systems by repeating the steps 3 and 4. Click on the row under the Communication Component column. In the Model Configurator. 3. CI5 of ariba. Select the following Communication Channel Template: ○ Name: CCT_Quote_cXML_Sender ○ Namespace: http://ariba. they are reused and enhanced. and then click OK in the dialog box. You can also simulate generation for test purposes. All rights reserved. Procedure 1. Click Continue. Click the Save Settings button to save the changes.com/xi/ASN/QuoteMessage ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER. Generation creates the configuration objects if they do not exist. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. 2. Click the New Communication Channel button (the icon at the top left). and in the next page click the Name field. click the empty Communication Channel cell corresponding to BS_FILE in the Receiver Business System Components table. you can create the communication channel by copy from a channel already configured. In the Connections from Component Assignment tab in the Configure Connection window. 4. 205 .Configuring Connections in the Sourcing Award to Contract Integration Scenario The third integration scenario configuration step is to configure connections. click the Configure Connections button. if required. Click Continue. If they already exist. modify the channel name to CC_File_QuoteMessage_Sender. 7. Next Steps Generate the objects.com 5. 6. and then click Finish. Tip If you have already created and configured a Sender channel for BS_FILE for another transaction. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. You must assign Communication Channels to set up the connections. then click the Display Input Help drop down list and select Input Help. Click the Activate All Connections button. Generating Objects for the Sourcing Award to Contract Integration Scenario The fourth integration scenario configuration step is to generate objects. Under Communication Channel. 4. Note If you created the channel by copy from an existing channel. double-click |BS_FILE|CC_File_QuoteMessage_Sender to open it. click the Create Configuration Object button. 5. Click on Start to begin generating objects. Configuring the Communication Channel for the Sourcing Award to Contract Integration Scenario Configure the communication channel CC_File_QuoteMessage_Sender under the AR_QuoteMessage_Send Configuration Scenario. Save your changes. When object generation is complete. click Apply to save the new configuration settings. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. or right- click and select Open. In the Parameters tab. A log file is created by this operation. In the Create Configuration Object window. 3. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. and Interface Determination. you need to change the request type to QuoteMessage in the Inbound Request Type field. 4. make the following settings: ○ General: Generation (select the radio button for this option) ○ Scope of Generation: Select both the active check boxes – Sender Determination. In the Model Configurator. 2. If required. Procedure 1. All rights reserved. Procedure 1. 2. Ariba Network Adapter for SAP NetWeaver Setup Guide 206 © 2015 SAP SE or an SAP affiliate company. edit the other parameters. or you can optionally save it if required for your needs. You can close the log file without saving it. 3. Configuring Integration Scenarios . Select the operation mapping IFM_cXML_2_ARBA_QUOTE and click Apply. and then click BS_FILE| | MIOut_Async_QuoteMessage_cXML | | BS_BS_SAPR3_50. 3. The Multiplicity column displays the value "0. Check the sequence for the value <Extrinsic name="DocumentType">Contract</Extrinsic> and add your condition. 2. In the Sender Interfaces section of the Edit Interface Determination window.unbounded".. Save the interface determination settings. This extrinsic sequence might vary based on the customization.Configuring the Interface Determination Settings for the Sourcing Award to Contract Integration Scenario Configure the interface determination settings to enable mapping enhancements. 4. Context Configuring the Interface Determination is a mandatory step if you need to configure the mappings. Expand Interface Determination. 5. Results Document flow occurs based on the extrinsic value when the qualifier is DocumentType: <Extrinsic name="DocumentType">Contract</Extrinsic>. then click the Value List drop down and select Value List. Procedure 1. Example /cXML/Message/QuoteMessage/QuoteMessageHeader/Extrinsic/Extrinsic[9] ≠ Contract AND /cXML/Message/QuoteMessage/QuoteMessageHeader/Extrinsic/Extrinsic[7] ≠ Contract Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. Select the operation mapping IFM_cXML_2_ARBA_CONTRACT and click Apply. 6. 207 . All rights reserved. click the operation mapping value under the Operation Mapping column. As the custom RFC call retrieves all the required data. Ariba Network requires the complete purchase order cXML. Change Purchase Order Implementation Redesigned This functionality is available for customers using Ariba Cloud Integration 4. Changes in SAP NetWeaver PI A new RFC mapping object MM_ORDCHG_ORDERS05_2_CDF_RFC_cXML_XSD is created. However. only one RFC call is performed from SAP NetWeaver PI to get all the data required to complete the PO cXML. When a change PO IDOC ORDERS05. the UDFs used in the original IDOC mapping have not been used. Enabling Change Purchase Order Redesign Changes in SAP ERP System A custom RFC called /ARBA/PO_GET_DETAIL is created that in turn calls the standard SAP provided BAPI BAPI_PO_GETDETAIL. activate all the Change Lists containing the objects created and modified during the component setup.0 and earlier. The RFC lookup API was designed to query only table at a time and as a result multiple RFC calls were performed for a single change purchase order. from SAP NetWeaver PI this custom RFC is called which in turn calls the BAPI BAPI_PO_GETDETAIL. These multiple RFC calls are expensive in case a high number of change POs are sent from the SAP ERP system.Activating the Sourcing Award to Contract Integration Scenario The final configuration step for supporting the QuoteMessage transaction in SAP NetWeaver PI is to activate your newly created scenario. A custom RFC is created to ensure that when a change PO is sent from the SAP ERP system. The custom RFC retrieves all the required data from SAP ERP and sends this data to the target cXML structure. Configuring Integration Scenarios . Therefore. an RFC lookup from SAP NetWeaver PI to SAP ERP was performed to get remaining line items and additional address data for ShipTo and Vendor to complete the purchase order cXML. The following UDFs are deprecated: ● callRfcReadTable ● copyRTItems ● setRTItemsField Ariba Network Adapter for SAP NetWeaver Setup Guide 208 © 2015 SAP SE or an SAP affiliate company.ORDCHG is sent from the SAP ERP system. The OOTB change purchase order IDOC sent from SAP ERP contained only line items that had changed. ● From the Change List tab on the main application screen. All rights reserved. Import the AribaNetworkAdapterSAPNetweaver. 3.tpz file into your SAP NetWeaver PI system. If you are using SAP NetWeaver PI 7.ariba. Click on the Signature tab and under Parameters. b. All rights reserved. ● getReadTableFieldValueWithCondition Implementing the Redesigned Change Purchase Order Transaction Procedure 1. in the Type column. Log in to Enterprise Services Builder. 2. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company. d.com. ● createFromReadTableFieldValues. perform the following sub steps: a.Design. Navigate to http://ariba. 4. c.zip file from connect. Download the AribaNetworkAdapterSAPNetWeaver_vCIX.com/xi/ASN/ChangedPurchaseOrder scenario. Configure the change purchase order scenario in the Integration Directory. 209 . Expand Message Mapping node and double-click MM_ORDCHG_ORDERS05_2_RFC_cXML_XSD. ● removeEmpty. click on the pull-down menu and select RFC from the Search Result and click Apply.3 or above. ● setRTItemsFieldIfExist ● setRelatedRTItemsField ● getRTUniqueValues ● buildRTConditionFromValuesList ● checkPODeleted ● getReadTableFieldValue. com and import them into your SAP ERP system. ● In SAP NetWeaver PI 7.3 single stack (Java only) instance. 6. specify the name of the RFC channel that points to the SAP ERP system from where you want to pull data into SAP NetWeaver PI. As a result. the ccBPM engine is not available. e. For the RFC_Lookup_Receiver parameter. 7.3 onwards) through the respective proxies instead of ccBPM's. Proxy Implementation for Outbound Transactions Ariba has deprecated the use of ccBPM engine to send outbound documents because of the following limitations: ● Performance of ccBPM is very slow in case of batch processing. All rights reserved. go to Interface Determination and click to change mode. g. Expand Operations Mappings node and double-click IFM_ORDCHG_ORDERS05_2_cXML. After you have configured the scenario in the integration directory. 5. Click the Parameters button and under Parameters. Save and activate the message mapping. ABAP proxies are implemented for the following outbound transactions: ● Invoice Status Update (ISU) ● Payment Proposal (PP) ● Receipt ● ERP-Initiated Invoice These outbound documents will be sent to SAP NetWeaver PI (version 7.ariba. click on the pull-down menu and select RFC from the Search Result and click Apply. Configuring Integration Scenarios . in the SAP ERP system. in the Type column. Ariba Network Adapter for SAP NetWeaver Setup Guide 210 © 2015 SAP SE or an SAP affiliate company. Download the relevant SAP transport requests from connect. f. Ensure that you have downloaded the latest SAP transport requests from connect. Ensure that you have downloaded the latest AribaNetworkAdapterSAPNetweaver. 211 .tpz file from connect. 2.com and imported it into your SAP NetWeaver PI system.com and imported them into your SAP ERP system. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios © 2015 SAP SE or an SAP affiliate company.Enabling Proxy Implementation for Outbound Transactions Procedure 1.ariba. All rights reserved.Design.ariba. This identifier. you can link them to a single Ariba Network account. each of the SAP ERP systems involved in the integration is identified by a unique identifier. All rights reserved. This feature allows all the documents from particular vendors to be routed to a single Ariba Network account and in the reverse direction.10.243" timestamp="2007-05-09T05:01:57-07:00"> Ariba Network Adapter for SAP NetWeaver Setup Guide 212 © 2015 SAP SE or an SAP affiliate company. the documents from Ariba Network will be routed to a particular SAP ERP instance. Buying organization or service provider accounts must be enabled for Multi-ERP implementation by Ariba Network Support. Document Routing Mechanism In the multi-ERP implementation scenario. Advanced Configuration Scenarios .13. to include or to retrieve this unique identifier from the cXML header: <cXML payloadID="1178712117116-1738314603425509122@10. Each document that passes through the integration will be transformed as follows. called the SystemID. This section describes the following topics: ● The mechanisms involved in the documents routing ● The configuration to setup integration with Ariba Network of multiple SAP ERP instances.Advanced Configuration Scenarios Linking Multiple SAP instances with Ariba Network [page 212] Configuring Supplier Quick Enablement [page 216] Customizing Data Mappings [page 216] Enabling Support for Attachments [page 218] Support for Proxy ByPass [page 225] Support for 2-Way Match [page 228] Using Endpoint Integration [page 228] Using the SAP NetWeaver PI KeyStore [page 230] PDF Invoice Copy Attachments [page 232] Integrating SAP ERP with the Ariba Spot Quote Solution [page 245] Integration of Catalog Data in SAP ERP and Ariba Network [page 250] Linking Multiple SAP instances with Ariba Network If your organization has more than one instance of SAP. corresponds to the logical system ID of the concerned SAP ERP instance. The required configuration sections will not be available for accounts that have not been enabled. The following figure shows the SystemID identifier location in outbound documents at the top and in inbound documents at the bottom: In the case of single-ERP implementation. All rights reserved. the SystemID identifier is located in different locations: ● For outbound documents. it is not processed and fails in the SAP NetWeaver PI integration with a System Error. the SystemID identifier is not inserted in the outgoing documents or expected in the incoming documents. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. 213 . it is located in the To element. In the case of multi-ERP implementation. it is located in the From element ● For inbound documents. <Header> <From> <Credential domain="NetworkID"> <Identity>AN50000000365</Identity> </Credential> <Credential domain="PrivateID"> <Identity>0000009999</Identity> </Credential> </From> <To> <Credential domain="NetworkID"> <Identity>AN51000000349</Identity> </Credential> <Credential domain="SystemID"> <Identity>T90CLNT090</Identity> </Credential> </To> Depending on the direction. if the SystemID is not found in an inbound document. For more information. Configuring the System Landscape Directory You must configure all your SAP ERP instances in the SLD as Technical and Business Systems. Configuring SAP ERP Connectivity The connectivity between all the SAP ERP instances and the SAP NetWeaver PI server has to be setup. For more information. All rights reserved. Configuring Integration Scenarios for Multiple ERPs The integration scenarios in the Integration Directory need to be parameterized in order to have the information on the systems and enable message routing. Advanced Configuration Scenarios . Configuring ValueMappings You must configure the following entries in the ValueMappings to enable the multi-ERP support for the integration: ● Enable the multi-ERP mode: Source: ● Agency: XI_Global ● Scheme: GlobalVariable ● Value: IsMultiERPModeEnabled Target: ● Agency: XI ● Scheme: GlobalVariable ● Value: true. see the “Defining Technical and Business System for SAP R/3” [page 64] section.Multi-ERP Configuration The multi-ERP implementation requires configuration on all three sides: SAP ERP. see the “About Configuring R/3 Connectivity” [page 67] section. SAP NetWeaver PI and Ariba Network. ● Configure the mappings between Business Systems and Logical System Names: Ariba Network Adapter for SAP NetWeaver Setup Guide 214 © 2015 SAP SE or an SAP affiliate company. see Configuring Receiver Determination Settings for the PayMeNow Integration Scenario [page 135]. All rights reserved. has to be configured for messages and calls routing. Note The Group Name is not required. The following table shows an example of values. 215 . see Configuring Receiver Determination Settings for the Ship Notice Integration Scenario [page 107]. For more information on setting up the receiver determination for Ship Notices. For more information on setting up the receiver determination for Pay Me Now.Source: ● Agency: LogSys_Source ● Scheme: Lookup ● Value: Logical System Name Target: ● Agency: BusSys_Target ● Scheme: Lookup ● Value: Business System Name. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. For more information on setting up the receiver determination for Invoice. Configuring Ariba Network for Multiple ERPs You must configure Ariba Network with the information about all the instances of SAP ERP involved in the integration and link it with the buyer account. see Configuring Receiver Determination Settings for the Invoice Integration Scenario [page 128]. Refer to the specific section for each transaction to setup the receiver determination rules: For more information on setting up the receiver determination for Order Confirmation. see Configuring Receiver Determination Settings for the Order Confirmation Integration Scenario [page 100]. as well as the scheduled scenarios. LogSys_Source BusSys_Target T90CLNT090 BS_SAP_46C T47CLNT800 BS_SAP_47 Setting up Receiver Determination Each inbound scenario. email address. the fax will be used as the default routing method. Fore more information on Ariba Network setup. All rights reserved. and fax number. of the Ariba Network Buyer Administration Guide. Advanced Configuration Scenarios . in “Configuration. For detailed steps to configure support for Multiple SAP instances. Buying organization or service provider accounts must be enabled for Quick Enablement by Ariba Network Support. Ariba Network uses this information to create the supplier’s account. They can create these accounts by specifying the supplier’s company information in a Correspondent element in the header of purchase orders sent to the supplier or invoices received from the supplier. For more information about configuring Ariba Network for Quick Enablement. see Linking Multiple SAP instances with Ariba Network [page 212]. The required configuration sections will not be available for accounts that have not been enabled.” of the Ariba Network Integration Guide. For details on how to link multiple SAP instances from Ariba Network. of the Ariba cXML Solutions Guide. The Quick Enablement functionality has the following limitations: ● If the information is not maintained for a particular vendor that is not referenced as a supplier in Ariba Network. Ariba Network Adapter for SAP NetWeaver supports the Supplier Quick Enablement functionality by providing the required supplier information. Quick Enablement is also supported for ERP-initiated invoice and payment proposal transactions. the purchase orders for this vendors forwarded to Ariba Network will be rejected. see the “Linking Multiple Business Applications” section. This information is retrieved from the Vendor Master Data. Note Buying organization or service provider accounts must be enabled for Multi-ERP implementation by Ariba Network Support. For more information about the Quick Enablement and the cXML. see the Ariba Network Integration Guide. Customizing Data Mappings The Ariba Network Adapter for SAP NetWeaver mapping workbooks are intended as sample only. see the Quick Enablement section. Configuring Supplier Quick Enablement Ariba Network Quick Enablement allows buying organizations and Invoice Conversion service providers to create new Ariba Network accounts on behalf of suppliers. in Chapter 3 “Document Addressing and Security”. Ariba Network Adapter for SAP NetWeaver Setup Guide 216 © 2015 SAP SE or an SAP affiliate company. see the Inviting an Unregistered Supplier section in Chapter 3 “Managing Supplier Relationships”. The buying organizations can customize mappings to suit their business needs. ● In case both routing information are available for a particular vendor. Ariba Network ignores the Correspondent element for accounts that have not been enabled. in the Purchase Order documents (transaction OrderRequest). 4. Click Ariba Network Adapter for SAP NetWeaver. Caution Do not change any object other than those listed in the table. Click Ariba Connect for On-Demand Solutions. Click Ariba Network Adapters. 217 . 5. click Data Transformation.In case of outbound transactions.ariba. the data is transformed from cXML to XML and then transferred to the ERP system. each buying organization lists requisitioners in cXML in a different way. the data is transformed from XML to cXML and then uploaded to Ariba Network. The following table lists the mapping objects for each transaction: Transaction Mapping Object ShipNotice MM_Custom_CDF_FulFill_XSD_AdvanceShipNotice_2_DESADV_DESADV01 Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. All future upgrades will be done using the Release Transfer Tool. Go to http://connect. Downloading Mapping Workbooks from Connect Procedure 1. To enable the customization to be retained when upgrading from an earlier version to a subsequent version of the Ariba Network Adapter for SAP NetWeaver. You as a buying organization can change the mapping of fields between XML and cXML according to your business requirements. you must make customizations only in the designated mapping objects. The Release Transfer Tool will migrate the customizations unchanged. In case of inbound transactions. For example. 2. If you do. Enabling Migration of Mapping Customization The mapping customization migration feature allows customization to be retained while upgrading to subsequent versions.ariba. These differences can be handled by customizing the mappings. All rights reserved.com. Under Integration Tools section. Results The mapping workbooks for all transactions are available in a ZIP file. You can download these mapping workbooks from connect. The information about how the fields have been mapped between XML and cXML files for both inbound and outbound transactions is available in mapping workbooks provided Ariba. upgrade may fail. 3.com and log in. To attach external files to a cXML document in a single envelope. Advanced Configuration Scenarios . JPEG. Ariba Network Adapter for SAP NetWeaver Setup Guide 218 © 2015 SAP SE or an SAP affiliate company. . and so on. Ariba Network supports attachments for the following transactions: ● Purchase Order ● Invoice ● Ship Notice ● Order Confirmation ● Service Entry Sheets The size of the attachments for both inbound and outbound documents cannot exceed 100 MB.DOC. For more information about attachments. which includes catalog files as attachments.. Attachments can addtionally have a payload up to 40 MB. use Multipurpose Internet Mail Extensions (MIME). Another example is the CatalogUploadRequest document. .Transaction Mapping Object ChangedPurchaseOrder MM_Custom_ORDCHG_ORDERS05_2_CDF_cXML_XSD ERPInvoice MM_Custom_Invoice_Intermediate_cXML_Item_2_cXML Invoice MM_Custom_CDF_InvoiceDetail_XSD_2_INVOIC_INVOIC02_INVOIC02 InvoiceStatusUpdate MM_Custom_InvoiceStatusUpdate_Item_2_cXML OrderConfirmation MM_Custom_CDF_FulFill_OC_XSD_2_ORDRSP_ORDERS05 PayMeNow MM_Custom_CDF_FulFill_XSD_PayMeNow_2_FIDCCH_FIDCCH01 PaymentProposal MM_Custom_PaymentProposal_Item_2_cXML PaymentRemittance MM_Custom_REMADV_PEXR2001_2_cXML PaymentRemittanceAdvice MM_Custom_CDF_PaymentRemittance_XSD_2_ACC_DOCUMENT_ACC_DOCUME NT01 PurchaseOrder MM_Custom_ORDERS_ORDERS05_2_CDF_cXML_XSD Receipt MM_Custom_MT_Intermediate_cXML_2_cXML ShipNotice against multiple pur­ MM_Custom_CDF_FulFill_XSD_AdvanceShipNotice_2_DESADV_DELVRY06 chase orders ’ Enabling Support for Attachments The cXML protocol supports the attachment of external files of any type to cXML documents. buyers sometimes need to clarify purchase orders with supporting memos. For example. All rights reserved.TXT. Attachments in cXML can be of any file type. or faxes. drawings. such as . Files referenced by cXML documents can reside either on a server accessible by the receiver or within an envelope that also includes the cXML documents themselves. The cXML document contains references to external parts sent within a multipart MIME envelope.PDF. see cXML User’s Guide and cXML Solutions Guide. SAP ERP buyers can send and receive attachments for both outbound and inbound documents from Ariba Network. Extended summarization of FI documents ● 1801529 . Ariba recommends that you specify maxMessages=1 in the adapter communication channel in the integration builder. the end-to-end integration for document attachments is only available for invoices and service entry sheets.Error message F5727 "Maximum number of items in FI reached" when release MM document to accounting ● 36353 . 4. 2. This mapping is similar to the mapping that is maintained in Ariba Network.000 line items (40 MB) payload. All rights reserved. see the following SAP Notes: ● 1779136 . Although this feature allows processing of all transactional documents through the PI mapping layer.AC interface: Summarizing FI documents Note 1.If you attempt to exceed the file attachment size of 100 MB or 10. 3. The mapping is as follows: ● application/pdf=pdf ● application/postscript=ai Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. This setting is based on the configuration that administrators specify on their ERP system. For more information on limitations and workaround. SAP ERP limits the maximum number of line items depending upon the document type. The attachments are part of the Comments element in the cXML file. ● The cXML adapter receives the XI message and processes the attachment in the format required by Ariba Network. 219 . Attachments for Outbound Documents The outbound documents sent from a configured Ariba Network Adapter to the cXML Adapter can have attachments. then the structure of the Comments element is as follows: <Comments> <Attachment> <URL> “Attachment URL”</URL> </Attachment> </Comments> The Ariba Network Adapter for SAP NetWeaver processes attachments in the outbound transactional documents before sending them to Ariba Network as follows: ● The SAP NetWeaver PI mapping layer allows access to attachments. Multiple attachments are permitted but the combined attachment size must not exceed 100 MB. SAP ERP and Ariba Network either prevent or reject the document with an error message. If a cXML document contains attachments. To avoid performance degradation when sending or receiving multiple documents with large attachments or payload. The cXML Adapter maintains a mapping of the content type and the corresponding file extensions for processing of attachments in outbound documents. When the cXML adapter downloads the attachments from Ariba Network. Buyers must ensure that the rule Your procurement application can download invoice attachments (MIME multipart messages) is enabled in Ariba Network . it checks the parameter settings specified for the document attachment before processing the attachment. ● The PI mapping layer processes the attachment and sends it as an XI message to the cXML adapter. do the following: ● Maintain a mapping of the content type and the corresponding file extensions in the cXML Adapter for processing attachments in outbound documents. the adapter tries to download the attachment from the HTTP location specified within the Attachment element in the cXML. appends the file extension.● video/x-msvideo=avi ● video/quicktime=mov ● video/mpeg=mpeg ● text/plain=txt ● text/html=html ● image/tiff=tiff ● image/jpeg=jpg ● image/gif=gif ● audio/x-wav=wav ● audio/basic=au ● application/x-troff=tr ● application/zip=zip ● text/xml=xml When an outbound document is sent to the cXML Adapter. then the cXML Adapter generates a random number as filename. Advanced Configuration Scenarios . If the content type matches. Ariba Network Adapter for SAP NetWeaver Setup Guide 220 © 2015 SAP SE or an SAP affiliate company. In Ariba Network. and uploads the cXML document to Ariba Network. This option is Authentication disabled by default. configure the following attachment related parameters: Parameter Description Bypass Proxy Server for Domains For more information. Active Attachment If enabled. see Attachments for Outbound Documents [page 219] ● In the communication channel for the outbound document. The cXML Adapter builds a MIME message and adds the attachment as a mime body part along with the content ID and content type of the attachment before uploading the cXML document to Ariba Network. Enabling Support for Attachments in Outbound Documents To send attachments in outbound documents. Attachment URL UseriD The user ID to be specified for HTTP authentication. the attachments section provides details about the all the attachments that are associated with a respective outbound document. HTTP authentication is enabled to access attachments. if the cXML Adapter receives the content type but does not receive the filename of the attachment. All rights reserved. the cXML Adapter generates a random number as filename and uploads the document to Ariba Network without a file extension and with the content type as application/octet-stream. which is the file extension corresponding to the content type. then the cXML Adapter matches the content type with the content type/file extension mapping it maintains. see Support for Proxy ByPass [page 225]. In the cXML message. If the content type does not match (or content type not available in the response message). For more information. Procedure 1. Parameter Description Attachment URL Password The password to be specified for HTTP authentication. 221 . Attachment URL UseriD and Attachment URL Password.class: TIF or PDF ○ Description: Portable Document Format ○ Application: SAPHTML 3. ensure that you have the following values: ○ Object Type: BUS2081 ○ Object Type: BUS2081 ○ Document Type: ZMMILOGINV ○ Link Status: X ○ Link Status: X ○ Storage system: MA ○ Link: TOA01 ○ Retention per: Blank or zero Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. you must enable the Active Attachment Authentication parameter and specify values for the authentication parameters. Configuring the SAP ArchiveLink for Storing and Assigning Attachments on the SAP ERP System Context Configure the SAP ArchiveLink for storing and assigning the attachments in invoices on the SAP ERP system. if HTTP authentication is required to access the attachments. Go to Tcode SPRO and then click SAP NetWeaver > Application Server > Basis Services > Archive Link > Basic Customizing. Specify the Send Attachments to Mapping option in the communication channel for the adapter. Specify the following: ○ Document Type: ZMMILOGINV ○ Description: Incoming invoice log. All rights reserved. For outbound documents. ○ Document Class: TIF or PDF 4. invoice verific. Edit the link to create a new document type and define the linkage between the document type and business object BUS2081. In the Display View “Links for Content Repositories: Details” page. 2. Edit the document class and specify the following: ○ Doc. Edit the document types and define a new document type for invoices. Attachment Processing Mode The mode of processing the attachments for outbound documents. If an error occurs when the cXML Adapter is downloading a document from the HTTP location. 6. Go to T code RZ10 for the latest version of the default profile. These stored attachments expire after 180 days and are not available online thereafter. Increase the time out setting for the parameter "HTTP_TIMEOUT" for category Runtime to 10000. Update the Extended Maintenance and increase the parameter value of "rdisp/max_wprun_time" to 5400. To prevent a PO with such attachments failing in Ariba Network. Advanced Configuration Scenarios . When the purchase order attachment URL contained special characters. images.Buyers must ensure that they do not encode "http://" in the URL for attachments. Go to the Parameters section. When Ariba Network receives a PO with attachments. Go to transaction SXMB_ADM. Go to transaction SMICM. ensure that the attachment URLs passed in the cXML to the cXML Adapter can be used directly. supporting memos. such as product specifications.Configuring Invoices and Service Entry Sheets to Support Large Attachments Context You must configure your SAP NetWeaver PI system to support the end-to-end integration in sending large attachments in invoices and service entry sheets. if any of the filenames of the attachments had blank spaces or special characters. they must ensure that the attachment URL is encoded using the UTF-8 compliant character set. and so on. Ariba Network reported an error and the PO processing failed in Ariba Network. Note Please note that this value goes back to 102400 after the system has rebooted. 3. Procedure 1. Note In a PO with attachments. 5. the document is not sent to Ariba Network and the cXML Adapter reports back an error to the originating system of the outbound document. 2. Change the parameter value of icm/HTTP/max_request_size_KB to "307200". Ariba Network either forwards the attachments to the respective suppliers or stores these attachments to allow online access for suppliers. Click to expand Integration Engine > Configuration. Purchase Orders with Attachments A purchase order (PO) document can have multiple attachments. This means that the URLs must be encoded if required before they are passed to the cXML Adapter. Ariba Network Adapter for SAP NetWeaver Setup Guide 222 © 2015 SAP SE or an SAP affiliate company. 7. All rights reserved. 8. 4. For more information.ariba. it receives the attachments in a MIME message.Attachments for Inbound Documents When the cXML Adapter downloads a document with attachments from Ariba Network.. see the BADI implementation for the BADI Definition INVOICE_UPDATE section. A sample Java map has been provided by Ariba that you can use. Note Although this feature allows processing of all transactional documents through the PI mapping layer. the end- to-end integration for document attachments is only available for invoices and service entry sheets. ● The cXML adapter sends the attachment as a message to the integration engine. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. implement a BADI for the BADI definition INVOICE_UPDATE in the customer's namespace to store and access attachments for invoices. Enabling Support for Attachments in Inbound documents You must do the following to send attachments in inbound documents: ● Configure the Attachment Processing Mode parameter and specify the Send Attachments to Mapping option in the communication channel for the adapter. the PI mapping layers maps it to the IDOC or RFC schema.. For inbound documents.zip on connect. see Configuring the SAP ArchiveLink for Storing and Assigning Attachments on the SAP ERP System [page 221]. All rights reserved. For invoices and service entry sheets.com. For more information. the attachment information is available in the IDOC.. ● Configure the SAP ArchiveLink for storing and assigning the attachments in invoices on the SAP ERP system. Attachment in service entry sheets are also supported. implement the method CHANGE_BEFORE_UPDATE and place the function module /ARBA/ ARCHIVE_IDOC_ATTACH inside the method.. This sample Java map is available in the AribaNetworkAdapterSAPNetweaver_vCI_X_FR. The following parameters must be sent to the function module: Parameter This parameter stores the. see PDF Invoice Copy Attachments [page 232]. ● To process attachments in invoices. ● For invoices. In the BADI. 223 . The Java mapping in the PI mapping layer reads the attachment from the message received and maps them to the target schema. For information on how the cXML Adapter processes the attachments. the SAP NetWeaver PI mapping layer receives the attachments and the cXML adapter sends the attachment as a message to the integration engine as follows: ● The SAP NetWeaver PI mapping layer receives the attachments. DOCNUM IDOC number that contains the attachment. The Java map is stored here: <root>/Archive/XI_Mapping_Services/javamappings/com/ ariba/asc/sap/netweaver/xiadapter/javamappings Name of Java file - InboundAttachmentHandlerSample. ● To read attachments in inbound documents received by the Ariba Network Adapter for SAP NetWeaver..java. customers must write a Java map. For example. fax. *Concatenate Invoice number with Fiscal year CONCATENATE s_rbkp_new-belnr s_rbkp_new-gjahr INTO l_objectid. Ariba Network Adapter for SAP NetWeaver Setup Guide 224 © 2015 SAP SE or an SAP affiliate company. c_ar_object TYPE saeobjart VALUE 'ZMMILOGINV'. ENDIF Invoices with Attachments An invoice can have multiple attachments such as delivery details. it prefixes the filename of the attachment with a unique random number. This allows the adapter to differentiate attachments within documents and attachments between documents. For example. it_return TYPE bapiret2_t. All rights reserved. emails. IF s_rbkp_new-sgtxt IS NOT INITIAL AND s_rbkp_new-bktxt EQ 'ARIBA_ASN'." OBJECT_ID The object ID (object identifier) for the SAP ArchiveLink. For example... Advanced Configuration Scenarios . Ariba Network adds these attachments to a mime message and sends the MIME message to the cXML Adapter for further processing. and so on. refresh it_return. Sample Code Example: CONSTANTS: c_archiv_id TYPE saearchivi VALUE 'MA'. DATA : l_objectid TYPE saeobjid. the cXML Adapter supports attachments of all file types that are supported by Ariba Network. RETURN (Table Parameter) Error details. for an invoice.Parameter This parameter stores the. For inbound documents. ARCHIV_ID Content repository identification. "MA". When the cXML Adapter downloads a document with attachments from Ariba Network. AR_OBJECT Document type for the SAP ArchiveLink. CLEAR l_objectid. BUS2081. This value is available only when there is an error in archiving or creating a link between the archived document. SAP_OBJECT The object type for the SAP ArchiveLink business object... c_sap_object TYPE saeanwdid VALUE 'BUS2081'. "ZMMILOGINV. the object ID would be the concatenation of the MIRO document number and fiscal year. CALL FUNCTION '/ARBA/ARCHIVE_IDOC_ATTACH' EXPORTING docnum = s_rbkp_new-sgtxt archiv_id = c_archiv_id ar_object = c_ar_object object_id = l_objectid sap_object = c_sap_object TABLES return = it_return. For example.. As attachments are normally stored on an internal domain/server that is within the firewall. customers do not want the adapter to use their proxy server to download and process attachments. 225 . if the truststore parameter is not configured. the document is not removed from the pending queue. As a result. the adapter by passes the proxy server to download and process attachments. However. An administrator can monitor the errors from the SXMB_MONI if a error occurs while processing attachments. maintain the ATTACHMENT_EMAIL_SEND parameter in the /ARBA/PARAM_TAB and specify the email addresses of the administrator that receives the email. However. then the adapter accesses these URLs and downloads attachments by going through the proxy server. If the truststore parameter is configured. Proxy ByPass allows you to configure a list of internal domains/servers that the adapter can access without using your proxy server to download and process attachments. then you must import the certificates of the HTTPS domains on which attachments are hosted and the Ariba certificate into the truststore file. In this case. Support for Proxy ByPass When a purchase order is sent from the SAP ERP system to Ariba Network Adapter for SAP NetWeaver. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. customers primarily use a proxy server to connect to domains/servers outside their firewall. In addition. The ERP administrator receives an email with details of the invoice number and attachment. the connection to the HTTPS domain is established using the truststore file or the default JRE cacert file. Managing Email Notifications To receive email notifications when there is an error during the attachment processing. when a purchase order with attachments is sent from the SAP ERP system. If the proxy server is configured for the purchase order transaction. then you must import the certificates of the HTTPS domains on which attachments are hosted and the Ariba certificate into the cacert keystore of the JRE. HTTPS Support for Attachment Processing Support for HTTPS protocol ensures that the adapter can download and process attachments that are hosted on a HTTPS domain/server. All rights reserved. Note The HTTPS support is enabled only for certificates available in the file system or JRE's cacert keystore. The cXML Adapter does not send a status update to Ariba Network and attempts to download the document again.If a error occurs when the cXML Adapter is downloading a document with attachments from Ariba Network. only basic authentication (Username and Password) is supported to download attachments hosted on a HTTPS domain/server. the attachments of the purchase order are represented as URLs that point to a storage location on an internal domain/server. The following graphic displays how the adapter by passes the proxy server to access attachments from the SAP Doc Server: ● You have enabled the proxy server configuration in the purchase order communication channel. Log on to your SAP NetWeaver system. All rights reserved. Advanced Configuration Scenarios . Procedure 1. Configuring Proxy Server ByPass for Attachment Processing Context You must configure the domains/servers that the adapter must bypass for downloading and processing attachments. Ariba Network Adapter for SAP NetWeaver Setup Guide 226 © 2015 SAP SE or an SAP affiliate company. ● In the communication channel for the purchase order transaction. you must specify a list of internal domain/ server names for the Bypass Proxy Server for Domains parameter under the Attachment Configuration section. Under the Attachment Configuration section.* .org .* . This message is logged only in the log file. 227 . For more information.Adapter bypasses the proxy server for the ariba.org and the sub domain xyz. " You may encounter an error such as “No Trusted To resolve this error. Save the changes. 3.org and all sub domains of schemas.org. ○ *.com. 2. Under Communication Channel.wiki.com . ○ xyz. and all sub domains of abc. For more information. This message is logged in the log file and an email notification is also sent with the error details to the config­ ured recipient.*.Adapter bypasses the proxy server for xyz. abc. ○ schemas. enter an internal domain/server name or a list of internal domain/server names that the adapter can access by bypassing the proxy server.*.*. Troubleshooting Proxy Server ByPass for Attachment Processing Some of the errors that you may encounter during attachment processing are as follows: Error/ Info Message Description "Http connection status for attachment This message is logged in the log file when the attachment processing fails as a result of incorrect HTTP connection status.wiki. ensure that you have imported the security certifi­ Certificate Found” cates into the cacert keystore or the truststore (if you have configured). In the Model Configurator.org .Adapter bypasses the proxy server for schemas. in the Bypass Proxy Server for Domains field.Adapter by passes the proxy server for all top level domains.com domain. open the communication channel for the purchase order transaction. javajee.org. Next Steps After you configure the proxy server bypass. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. “Domains configured to bypass proxy server” This info message indicates that the attachment is hosted on a domain that is configured for Proxy ByPass.org.com .). An email notifica­ download is incorrect: <status for URL: <url tion is also sent with the error details to the configured recipient. You can enter multiple domain/server names separated by a comma (. ○ abc. Some of the sample values for this field are as follows: ○ ariba.Adapter bypasses the proxy server for javajee.org. you must import the security certificates. ○ *. All rights reserved. see About Configuring Security Certificates [page 32].org. see Importing Security Certificates into the Java JRE Keystore [page 32] and Importing Security Certificates into the Java JRE TrustStore [page 33]. double-click the communication channel |BS_ASN| CC_PurchaseOrder_cXML_Receiver or right-click and select Open.Adapter by passes the proxy server for all top level domains and all sub domains of the top level domain 4. All rights reserved. When an invoice for this purchase order is sent by Ariba Network to Ariba Invoice Professional. all line items are flagged for a 2-way match. If yes.Support for 2-Way Match In the SAP ERP system. When your Ariba Network Adapter receives an outbound document from your ERP system. Establishing the 2-Way Match Flag in Your SAP ERP System When creating a purchase order in your SAP ERP system. the network adapter appends the endpoint information to the cXML and posts the document to Ariba Network. For example. then you must maintain the endpoint information in the Communication channel in SAP NetWeaver. Such line items are flagged for a 2-way match that includes only the purchase order and invoice during invoice reconciliation. when creating the cXML header for a purchase order. If you have configured an endpoint for your ERP system in Ariba Network. When a purchase order containing line items flagged for a 2-way match is sent from your SAP ERP system. by default. Ariba Invoice Professional user can reconcile the invoice by performing a 2-way match that includes the purchase order and the corresponding invoice. the adapter sends information about such line items to Ariba Network. along with the purchase order. your network adapter checks if the endpoint information is maintained in the communication channel in SAP NetWeaver. Advanced Configuration Scenarios . Using Endpoint Integration You can configure endpoints for outbound documents sent from your ERP system to Ariba Network. a user can create a purchase order by including line items that do not require a receipt. The Ariba Network Adapters allow data exchange between your ERP system and Ariba Network. then the network adapter includes the endpoint in the cXML header as follows: <Header> <From> <Credential domain="NetworkId"> <Identity>AN02000076701</Identity> </Credential> <Credential domain="EndPointID"> <Identity>ERPEndPoint1</Identity> </Credential> </From> <To> <Credential domain="NetworkID"> <Identity>AN02000076720</Identity> </Credential> </To> <Sender> <Credential domain="NetworkID"> <Identity>AN02000076701</Identity> <SharedSecret>welcome1a</ SharedSecret> Ariba Network Adapter for SAP NetWeaver Setup Guide 228 © 2015 SAP SE or an SAP affiliate company. This allows Ariba Network to send the corresponding invoices to the respective systems. In this case. open the communication channel relevant to the outbound transaction you are configuring. double-click the communication channel or right-click to open it. For example. 3. one for Ariba procurement solution and the other for the ERP system. when configuring the Purchase Order Integration Scenario. Enabling Endpoint Integration in SAP NetWeaver Procedure 1. double-click on |BS_ASN|CC_PuchaseOrder_cXML_Receiver to open it. ● If you want all your invoices to be sent to Ariba procurement solution. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. Using Endpoints for Integration The endpoints in Ariba Network manage and control the flow of data from Ariba Network to the various systems that are connected to it. in the Model Configurator under Communication Channel. In the Parameters tab. you can create and configure an endpoint accordingly. purchase orders can originate from both Ariba procurement system and the ERP system. You can create endpoints in Ariba Network according to your business requirements. you have Ariba procurement solution and an ERP system that integrate with Ariba Network. All rights reserved. Note You must set this only if you have configured an endpoint for your ERP system in Ariba Network. specify a value for the endpoint parameter. Save the changes. The endpoint in Ariba Network acts as a document routing placeholder that ensures documents from Ariba Network are sent to the desired system. 229 . You can create two endpoints. 2. </Credential> <UserAgent>Buyer</UserAgent> </Sender> </Header> <Request> <OrderRequest> ERPEndPoint1 is the value that you have configured in the communication channel in SAP NetWeaver. Example Scenarios ● In your system landscape. Under Communication Channel. In the Model Configurator. you can create keys and certificates in SAP NetWeaver and Ariba Network Adapter for SAP NetWeaver Setup Guide 230 © 2015 SAP SE or an SAP affiliate company. Therefore. it is sufficient to create only one endpoint with the same name for all three system IDs. For documents that are sent from Ariba Network to ERP. your network adapter checks if the endpoint information is maintained in the communication channel in SAP NetWeaver. All rights reserved. If yes.Endpoint Integration for Multiple ERP Systems Configure end points if you have multiple ERP system. Using the SAP NetWeaver PI KeyStore The server and client certificates that cXML Adapter uses to connect to Ariba Network must be stored in the SAP NetWeaver PI keystore. If you have enabled both multi-ERP (for multiple ERP systems) and endpoints in Ariba Network. Advanced Configuration Scenarios . As part of this functionality. then the network adapter includes the endpoint in the cXML header along with the system ID as illustrated below: Sample Code <Header> <From> <Credential domain="NetworkId"> <Identity>AN02000076701</Identity> </Credential> <Credential domain="SystemId"> <Identity>ARB2</Identity> </Credential> <Credential domain="EndPointID"> <Identity>ERPEndPoint1</Identity> </Credential> </From> <To> <Credential domain="NetworkID"> <Identity>AN02000076720</Identity> </Credential> </To> <Sender> <Credential domain="NetworkID"> <Identity>AN02000076701</Identity> <SharedSecret>welcome1a</ SharedSecret> </Credential> <UserAgent>Buyer</UserAgent> </Sender> </Header> <Request> <OrderRequest> ERPEndPoint1 is the value that you have configured in the communication channel in SAP NetWeaver and ARB2 is the System ID. You then have to create an endpoint for each system ID. then you must create system IDs corresponding to the different ERP systems that are there in your system landscape. When you have multiple ERP systems and you create a purchase order. SAP NetWeaver PI provides functionality to manage and administer authentication certificates and keystores. the network adapter uses the system ID to identify the ERP systems that must receive the respective documents. 4. For the KeyStore View parameter. enter the name of the view that contains the server certificate. see Configuring the cXML Adapter to Use the SAP NetWeaver PI Keystore [page 231]. All rights reserved. The cXML Adapter connects to Ariba Network by using certificates that are stored in the SAP NetWeaver PI Keystore as explained in the graphic below: Configuring the cXML Adapter to Use the SAP NetWeaver PI Keystore Procedure 1. 3. select Client certificate from the drop-down list. Open the required communication channel. 2. the cXML Adapter initializes and creates the Ariba Network TrustStoreView and KeystoreView (only if client certificate is selected) and uses the certificates to ensure a successful SSL handshake. you first need to create a view and then create the required keys and certificates under that view. In the communication channel for all the inbound and outbound transactions. you must get them signed by a trusted Certificate Authority (CA) to enable Ariba Network to successfully establish the SSL connection. for Trust Store View and KeyStore View (only if you are using client certificate). Therefore. for the Trust Store View parameter. After you have created the required certificates. For more information. The keys and certificates that you create in SAP NetWeaver Keystore are grouped bases on views. As a result. when SAP NetWeaver PI sends or receives documents to/from Ariba Network. based on the channel configuration. you must specify the names of the Views that store the Server certificate and Client certificate respectively.store them in the SAP NetWeaver PI Keystore. enter the name of the view that contains the client certificate. To use client certificate for authentication to Ariba Network buyer account. 231 . for Credential Mode. Under Authentication. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. invoice exception handlers or accounts payable personnel require a rendered format of the invoice data representing the supplier view of the invoice in Ariba Network.5. Ariba Customer Support must turn on PDF generations for your Ariba Network account by selecting the option Generate an invoice copy as a PDF attachment to the invoice. To enable this feature. Click Save. In addition. Repeat this configuration for all the inbound and outbound transactions. Note Accounts can be enabled for PDF invoice copy in the archive zip file (if you are archiving invoices) and as attachments to invoices. customers require a single message that contains the cXML invoice. a human readable representation of the invoice data (PDF Invoice Copy) and all supplier provided invoice attachments without storing any of these on the local file system. and therefore the option to send URLs to view attachments on Ariba Network is only Ariba Network Adapter for SAP NetWeaver Setup Guide 232 © 2015 SAP SE or an SAP affiliate company. This can be achieved by using an early archiving approach to store the human readable invoice copy and other supplier attachments. Enabling PDF Invoice Copy Attachment This feature is disabled by default. They can use the cXML invoice viewer. or wait until the invoice PDF is included in the invoice archive. See the Ariba Network Guide to Invoicing for a list of supported languages for PDF invoice copy. PDF Invoice Copy Attachments In many cases. complete and consistent invoice view across the supplier base is now available with every invoice for side-by-side comparison of the supplier invoice view with the buyer invoice view in their ERP system. This means a structured. To build the early archiving workflow in SAP NetWeaver PI. The invoicing rule “Allow suppliers to send invoice attachments” does not impact the PDF invoice copy attachment generation. Please have your Designated Support Contact log a service request and an Ariba Customer Support representative will follow up to complete the request. customers using a 3rd party AP workflow may need a human readable invoice copy and supplier provided attachments during the approval flow to ensure that the AP approver can review invoice data. 6. log into the Ariba Network account to view the invoice. All rights reserved. PDF invoice copy attachments ensures buying organizations can have their Ariba Network account enabled to generate a copy of the invoice in PDF format and attach it to the invoice. The invoice copy layout of the PDF attachment is very similar to the print layout. Advanced Configuration Scenarios . Language Support Ariba Network generates the PDF invoice copy attachment in the language of the supplier's locale (which is the preferred language configured for the account administrator). if the folder location in the SAP ERP system is .codec. you must provide a value for the Attachment Download Location parameter. PDF invoice copy. The value must be a location in the file system of your SAP ERP system where attachments need to be downloaded. All rights reserved. ● Use Shared File System – If you specify this value. and other attachments that are part of an invoice downloaded from Ariba Network. you must configure the following parameters depending on how you want to process the invoice data. then you have to use the Use Shared File System option. you must also provide a value for the Attachment Download Location parameter./home/usr/attachment then the mounted path in SAP NetWeaver PI must be . in addition to specifying a value for the Attachment Download Location parameter. you need to specify the machine name of your SAP ERP system and the Admin username and password to access your SAP ERP system. If PDF invoice copy generation is enabled in your Ariba Network account./home/usr/attachment.apache. For example. see Configuring the Attachment Processing Mode for PDF Invoice Copy Attachments [page 245]. File System Mode) For more information.Base64 and embeds the Base 64 string to the header part of the invoice cXML. Requirements In the communication channel for the invoice transaction.commons. Parameter Description Attachment Processing Mode You can specify the following values: ● Use Local File System – If you specify this value. all PDF invoice copy attachments are displayed as URLs. Mode) Store cXML Document (Optional) The cXML Adapter stores the invoice cXML file to the file system location you specified (only applicable for Local or Shared for the Attachment Download Location parameter. In addition. Attachment Download Location A location on the file system where the cXML Adapter must download PDF invoice copy (only applicable for File system and other attachments that are part of the invoice cXML.available for attachments added by the supplier. As a result. Note ● If SAP NetWeaver is running on Windows. This is the default option. The SAP service user must have Write permission to the mounted folder path in the SAP NetWeaver PI system and the SAP service user must have Delete Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. you must specify values for the following parameters: ○ Shared System Machine Name ○ Shared System Machine User ID ○ Shared System Machine Password ● Embedded In cXML – The cXML Adapter encodes the attachment contents to a Base 64 string using rg. 233 . The mounted folder path must be same to the actual folder path in the SAP ERP system.binary. ● If SAP NetWeaver is running on Linux and you want to use the Use Local File System. The cXML Adapter logs into the SAP ERP system and downloads the attachments in the file system location you specified. The value must be a location in the file system of your SAP ERP system that is mounted locally to a location in the file system of your SAP NetWeaver PI system. then you need to provide a value for the Attachment Download Location parameter. Not A Tax Invoice” to indicate that the cXML invoice remains the legal document. for example: kBAIGmcwmN502a7638191182029. All rights reserved. In this case. Using PDF Invoice Copy Attachments If your account has been enabled to generate PDF invoice copy attachments. For this invoice. you need to provide a value for the Attachment Download Location parameter. Data Flow Overview A PDF copy of the invoice data is automatically added as a MIME (Multipurpose Internet Mail Extension) attachment to the invoice cXML as follows: <InvoiceDetailRequestHeader> <Extrinsic name="invoicePDF"> <Attachment> <URL>cid:18040725. In addition. The file name for the PDF invoice copy attachment is a randomized file name. then you need to specify the machine name of your SAP ERP system and the Admin username and password to access your SAP ERP system. the provider or supplier is expected to include a PDF invoice copy as an invoice attachment if required. the Samba Server must be installed and configured in your SAP ERP system to accept NTLM authentication. ● If SAP NetWeaver is running on Linux and you want to use the Use Shared File System. the processing of attachments by the cXML Adapter depends on the value you specify for the Attachment Processing Mode Ariba Network Adapter for SAP NetWeaver Setup Guide 234 © 2015 SAP SE or an SAP affiliate company. permission to the folder path in the SAP ERP system. To ensure that the cXML Adapter can write to this shared location.org</URL> </Attachment> </Extrinsic> </InvoiceDetailRequestHeader> The PDF invoice copy includes the text “Copy of Invoice . the cXML Adapter downloads the attachments locally in the mounted [email protected] Processing of PDF Invoice Copy Attachments by the cXML Adapter When the cXML Adapter downloads an invoice with attachments from Ariba Network. The value must be a shared location in the file system of your SAP ERP system. PDF invoice copies are generated and attached to the following supplier-submitted invoice types: ● Invoices submitted through EDI or cXML that are not self-signed by the supplier ● Manually created PO-based or non-PO invoices ● Invoices created through CSV import ● Supplier self-signed invoices PDF copies of invoices are not generated for the Invoice Conversion Services (ICS) invoice. Advanced Configuration Scenarios . The URL is a unique content ID that the cXML Adapter assigns for each attachment. the cXML Adapter adds the Extrinsic invoicePDF to the header part of the invoice cXML and embeds the Base 64 string within this Extrinsic element. The cXML Adapter encodes the attachment contents to a Base 64 string using rg. Use Shared File System. See sample below.commons. The URL is prefixed with the word cid. In this case. All rights reserved. The adapter then adds the file URLs under the Extrinsic element tag with the attribute name as invoicePDF (for the PDF invoice copy) and SupplierAttachments (for other attachments) to the header part of the invoice cXML.Base64. URLs at header level ensure the integrity of a document if it is digitally signed. you have not provided any value for the Attachment Download Location field or the cXML Adapter does not have access to the storage location. During transformation. You must implement a BADI for the BADI definition INVOICE_UPDATE in the customer namespace to ensure that when the IDOC reaches the SAP ERP system. 3. The processing by the cXML Adapter for all these options is explained as follows: “Use Local File System” or “Use Shared File System” Option When the cXML Adapter downloads a document with attachments from Ariba Network. 2. Note The attachment processing can fail if for example.binary. 2. You can specify Use Local File system. In addition.parameter in the communication channel for the invoice transaction. Sends the modified invoice cXML to the mapping services for transformation in SAP NetWeaver PI. Generates a file URL for each attachment that indicates the location of the downloaded attachment. the file URLs are mapped to IDOC fields. Stores the PDF copy of the invoice and other attachments available in the MIME message to the file system location you specified for the Attachment Download Location parameter. Prefixes the filename of an attachment with the payload ID and a random number. or Embedded In cXML. If you selected Use Local File System or Use Shared File System. an exception is logged in the log file. The URLs are added to the header part because line level attachments are not supported in SAP ERP systems.apache. after downloading the invoice with attachments (PDF copy of the invoice and other supplier provided attachments) from Ariba Network: 1. 235 . For the PDF copy of the invoice. “Embedded In cXML” Option If you selected Embedded In cXML.codec. the following tasks can be performed: ○ Accesses the attachments from the location specified in the IDOC ○ Stores the attachments in the SAP Archive Link ○ Assigns the attachments to the invoice created in the ERP system To implement the BADI. This allows the adapter to differentiate attachments within documents and attachments between documents. 4. see BADI Implementation for the BADI Definition INVOICE_UPDATE. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. the cXML Adapter: 1. it receives the attachment in a MIME message. pdf”> Base64 encoded string AAgFBgcGBQgHBgcJCAgJDBQNDAsLDBgREg4UHRkeHhwZHBsgJC4nICIrI </data> </Attachment> <Attachment> <data contentType= “application/pdf” fileName = “YYY. and other attachments. The cXML Adapter sends the single cXML message that contains the cXML invoice. the Base 64 strings for all attachments are embedded within this extrinsic element within <data>.0" encoding="UTF-8"?><!DOCTYPE cXML …> <cXML timestamp=“…" payloadID="12345666…"> <Header>… <To> <Correspondent> <Extrinsic name= “invoicePDF”> <Attachment> <data contentType= “application/pdf” fileName = “ABC. Advanced Configuration Scenarios . ○ Early or late archiving of attachments is complete.3. ○ The cXML invoice itself (including the e-signature if signed) is archived.Base64. you need to build a custom workflow in SAP NetWeaver PI to ensure that: ○ The invoice is created in your ERP system.binary.commons. The cXML structure with the PDF copy of invoice and two supplier added attachments appears as follows: <?xml version="1. For other attachments from the supplier. To process this cXML message. All rights reserved. the cXML Adapter adds the Extrinsic SupplierAttachments to the header part of the invoice cXML and embeds the Base 64 string within this extrinsic element. If multiple attachments are there. Ariba Network Adapter for SAP NetWeaver Setup Guide 236 © 2015 SAP SE or an SAP affiliate company. Note You need to decode the Base 64 string using apache. ○ An email ID is configured to receive email notifications if attachment processing fails in your ERP system. ○ The attachments are deleted from the location where they were downloaded..pdf”> Base64 encoded string AAgFBgcGBQgHBgcJCAgJDBQNDAsLDBgREg4UHRkeHhwZHBsgJC4nICIrI </data> </Attachment> </Extrinsic> <Extrinsic name= “SupplierAttachments”> <Attachment> <data contentType= “application/pdf” fileName = “XXX.codec. PDF invoice copy attachment. ○ The attachments are assigned to the corresponding invoice..pdf”> Base64 encoded string AAgFBgcGBQgHBgcJCAgJDBQNDAsLDBgREg4UHRkeHhwZHBsgJC4nICIrI </data> </Attachment> </Extrinsic> </Correspondent> </To> </Header> <Request> <InvoiceDetailRequest> <InvoiceDetailRequestHeader … <Comments>… <Extrinsic name="… </InvoiceDetailRequestHeader> </Request> <ds:Signature xmlns:xades="… </cXML> 1.<data/> elements as displayed in the sample below. 2. segnam TYPE edi_segnam. TYPES : BEGIN OF ty_delete. The invoice number will be generated in this method in S_RBKP_NEW-BELNR. BADI Implementation for the BADI Definition INVOICE_UPDATE Write the below code in the method CHANGE_BEFORE_UPDATE. the attachment document is taken from the specified location and the same is stored in SAP Archive Link using function module SCMS_AO_FILE_CREATE. psgnum TYPE edi_psgnum. l_counter(4) TYPE c. doc TYPE char255. ************************************************************************************** This implementation is done to attach SAP Archive Link attachment to an invoice. The parameter to maintain the email id is INVOICE_EMAIL_SEND. l_lines TYPE i. l_machineinfo TYPE rfcsi.The configuration parameters for attachment processing mentioned in the Requirements sections Enabling PDF Invoice Copy Attachment [page 232] are also available for the Order Confirmation and Ship Notice transactions. l_doctype TYPE saedoktyp. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. As a result. docnum TYPE edi_docnum. All rights reserved. error TYPE char75. The TIF/PDF URL path is fetched from table EDID4 by passing the IDOC number. counter TYPE edi_clustc. TYPES : BEGIN OF ty_object. sdata TYPE edi_sdata. The attachment document is deleted from the source location immediately after the document is stored in SAP Archive link. If the document is not attached to the invoice. an email is sent to the email id maintained in /ARBA/PARAM_TAB. After getting the URL path. 237 . l_sapsystem TYPE string VALUE 'NONE'.'. The IDOC number is stored in S_RBKP_NEW-SGTXT. objectid TYPE saeobjid. END OF ty_documents. the document is assigned to the invoice using function module ARCHIV_CONNECTION_INSERT. ************************************************************************************** Types Declaration TYPES : BEGIN OF ty_path. l_filetype TYPE e1edkt1. END OF ty_error. END OF ty_delete. Once the attachment is stored. TYPES : BEGIN OF ty_error. TYPES : BEGIN OF ty_documents. l_idoc TYPE char70. objectid TYPE saeobjid. dtint2 TYPE edi_dtint2. doc TYPE char75. l_sep TYPE c VALUE '. END OF ty_path. *Data Declaration DATA : l_objectid TYPE saeobjid. END OF ty_object. the cXML Adapter processes attachments of these transactions similar to the manner in which it processes attachments of the invoice transaction. segnum TYPE idocdsgnum. filepath TYPE char255. t_deletefile. wa_path. wa_receivers. wa_deletefile TYPE ty_delete. l_filename TYPE char255. *Clearing variables. l_segment TYPE edi_segnam. l_doctype. t_filepath TYPE TABLE OF ty_path. wa_object TYPE ty_object. work areas and internal tables CLEAR : l_objectid. wa_param TYPE /ARBA/param_tab. t_receivers. wa_param. All rights reserved. *Internal table DATA : t_path TYPE TABLE OF ty_path. l_delimiter TYPE c. t_documents TYPE TABLE OF ty_documents. t_param TYPE TABLE OF /ARBA/param_tab. wa_extension TYPE string. t_packlist. wa_error TYPE ty_error. *Work area DATA : wa_path TYPE ty_path. l_pathname TYPE char255. t_deletefile TYPE TABLE OF ty_delete. wa_object. wa_deletefile. wa_message. t_extension TYPE TABLE OF string. t_extension. wa_receivers TYPE somlreci1. wa_packlist. t_packlist TYPE TABLE OF sopcklsti1. l_archiveid TYPE saearchivi VALUE 'MA'. wa_filepath. l_sap_object TYPE saeanwdid VALUE 'BUS2081'. wa_error. t_documents. Ariba Network Adapter for SAP NetWeaver Setup Guide 238 © 2015 SAP SE or an SAP affiliate company. l_idoc. l_machineinfo. *Clearing internal tables FREE : t_path. t_message. t_param. l_time TYPE char8. l_lines. wa_packlist TYPE sopcklsti1. wa_filepath TYPE ty_path. t_object TYPE TABLE OF ty_object. l_date TYPE char200. wa_documents. l_subject(200) TYPE c. t_object. l_doctype. *Email data declarations DATA : l_docdata TYPE sodocchgi1. t_error TYPE TABLE OF ty_error. wa_documents TYPE ty_documents. t_filepath. t_receivers TYPE TABLE OF somlreci1. l_phys_path TYPE char255. Advanced Configuration Scenarios . t_message TYPE STANDARD TABLE OF solisti1. t_error. wa_message TYPE solisti1. l_output TYPE char20. l_counter. l_documentid TYPE saeardoid. ENDLOOP. the file attachment location path need to be like * (\usr\sap). l_idoc = wa_filepath-sdata+0(70). *Taking Filepath into separate internal table. LOOP AT t_filepath INTO wa_filepath WHERE segnam = 'E1EDKT2' AND psgnum = l_segment. * The attachment location path which comes from SAP XI will be like * (/usr/sap). 239 . *Taking the Filepath's into a separate internal table FREE t_filepath[ ]. ENDIF. *Fetching the File Path from EDID4 SELECT docnum counter segnum segnam psgnum dtint2 sdata FROM edid4 INTO TABLE t_path WHERE docnum = s_rbkp_new-sgtxt AND segnam IN ('E1EDKT1'. c_windowsu TYPE char7 VALUE 'WINDOWS'. l_segment = wa_path-segnum. DELETE t_filepath WHERE segnam NE 'E1EDKT2'. CLEAR wa_documents. l_filetype = wa_path-sdata. *Taking E1EDKT1 into separate internal table SORT t_path BY segnam. *If IDOC number exists IF s_rbkp_new-sgtxt IS NOT INITIAL AND s_rbkp_new-bktxt EQ c_aribainvoice. IF wa_path-segnam = 'E1EDKT1'. ENDLOOP. LOOP AT t_documents INTO wa_documents. *Getting the ERP system machine details(Windows or Linux) CALL FUNCTION 'RFC_GET_SYSTEM_INFO' EXPORTING destination = l_sapsystem IMPORTING rfcsi_export = l_machineinfo. CONCATENATE wa_documents-filepath l_idoc INTO wa_documents-filepath. l_delimiter. IF l_filetype-tdid = '0' OR l_filetype-tdid = '1'. ENDIF. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. *If file path exists for the invoice IF t_path IS NOT INITIAL. CONSTANTS: c_windows TYPE char7 VALUE 'Windows'. This will contain forward slash. IF l_machineinfo-rfcopsys+0(7) = c_windows OR l_machineinfo-rfcopsys+0(7) = c_windowsu.'E1EDKT2'). APPEND wa_documents TO t_documents. t_filepath[] = t_path[ ]. SORT t_filepath BY segnum psgnum segnam. c_aribainvoice TYPE char9 VALUE 'ARIBA_ASN'. If the SAP ERP system * is Windows machine. l_idoc. LOOP AT t_path INTO wa_path. ENDIF. DELETE t_path WHERE segnam NE 'E1EDKT1'. All rights reserved. l_segment. *Clearing variables CLEAR:l_machineinfo. l_delimiter = '\'. CLEAR: l_filetype. DESCRIBE TABLE t_extension LINES l_lines. READ TABLE t_extension INTO wa_extension INDEX l_lines. *All backward slashes are replaced with forward slashes *in case of Windows machine. l_documentid. *If document is not stored in archivelink. *Getting the file format FREE t_extension. All rights reserved. *Concatenate Invoice number with Fiscal year CONCATENATE s_rbkp_new-belnr s_rbkp_new-gjahr INTO l_objectid. CLEAR: l_lines. l_filename. TRANSLATE l_doctype TO UPPER CASE. ELSE. IF sy-subrc <> 0. ENDIF. l_doctype. *IF sap ARCHIVE link DOCUMENT IS NOT ASSIGNED to invoice. *Splitting File path and File name PERFORM split_path IN PROGRAM oaall USING wa_documents-filepath l_pathname l_filename. the error *messages are populated into internal table wa_error-doc = wa_documents-filepath. *Passing document type l_doctype = wa_extension. *Splitting the file path SPLIT wa_documents-filepath AT l_sep INTO TABLE t_extension. REPLACE ALL OCCURRENCES OF '/' IN wa_documents-filepath WITH l_delimiter. IF l_delimiter = '\'. CONCATENATE l_delimiter wa_documents-filepath INTO wa_documents-filepath. CLEAR : l_pathname. *Assigning the Archive Link document to the invoice CALL FUNCTION 'ARCHIV_CONNECTION_INSERT' EXPORTING archiv_id = l_archiveid arc_doc_id = l_documentid ar_object = 'ZMMILOGINV' mandant = sy-mandt object_id = l_objectid sap_object = l_sap_object doc_type = l_doctype EXCEPTIONS error_connectiontable = 1 OTHERS = 2. the error Ariba Network Adapter for SAP NetWeaver Setup Guide 240 © 2015 SAP SE or an SAP affiliate company. *Function Module Stores files to Archive Link CALL FUNCTION 'SCMS_AO_FILE_CREATE' EXPORTING arc_id = l_archiveid file = l_filename path = l_pathname doc_type = l_doctype no_delete = 'X' IMPORTING doc_id = l_documentid EXCEPTIONS error_http = 1 error_archiv = 2 error_kernel = 3 error_config = 4 error_file = 5 OTHERS = 6. Advanced Configuration Scenarios . IF sy-subrc <> 0. APPEND wa_error TO t_error. CLEAR wa_error. wa_message-line = space. ENDLOOP. CONCATENATE 'Date:' l_output l_time sy-zonlo sy-datum+0(4) INTO l_date SEPARATED BY space. APPEND wa_message TO t_message. *Forming Body of the email message wa_message-line = text-003. APPEND wa_message TO t_message. ELSE. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. *Populating Date in the email message CLEAR l_date. *messages are populated into internal table wa_error-doc = wa_documents-filepath. l_docdata-obj_name = 'SAPRPT'. wa_message-line = l_date. All rights reserved. *Time Formatting CONCATENATE sy-uzeit+0(2) ':' sy-uzeit+2(2) ':' sy-uzeit+4(2) INTO l_time. 241 . *If attachment is not assigned to invoice. l_docdata-obj_descr = l_subject. ENDIF. l_docdata-doc_size = 1. CONCATENATE text-005 s_rbkp_new-belnr INTO l_date SEPARATED BY space. l_docdata-obj_langu = sy-langu. *getting email IDs from the /ARBA/PARAM_TAB SELECT * FROM /arba/param_tab INTO TABLE t_param WHERE name = 'INVOICE_EMAIL_SEND'. *Forming the subject of the email l_subject = text-002. APPEND wa_message TO t_message. ENDIF. CLEAR wa_error. APPEND wa_error TO t_error. CLEAR wa_message. wa_message-line = space. *Deleting the attachment file from the location after the *attachment is stored in archivelink and assigned to invoice DELETE DATASET wa_documents-filepath. *Converting date format CALL FUNCTION 'CONVERSION_EXIT_LDATE_OUTPUT' EXPORTING input = sy-datum IMPORTING output = l_output. ENDIF. APPEND wa_message TO t_message. l_docdata-sensitivty = 'F'. l_time. email *sent to the specified users IF t_error[ ] IS NOT INITIAL. wa_message-line = l_date. CLEAR wa_message. *Populating invoice document number with the email message CLEAR l_date. CLEAR wa_message. IF sy-subrc = 0. *Email Subject CLEAR : l_output. APPEND wa_message TO t_message. CLEAR wa_message. APPEND wa_message TO t_message. APPEND wa_message TO t_message. APPEND wa_message TO t_message. *Populating the attachment URL's which are not attached *to the invoice in the email message LOOP AT t_error INTO wa_error. wa_message-line = text-008. wa_message-line = wa_error-doc. APPEND wa_message TO t_message. wa_message-line = l_date. CLEAR wa_message. wa_packlist-doc_type = 'RAW'. wa_receivers-notif_del = 'X'. wa_packlist-body_start = 1. CLEAR wa_message. DESCRIBE TABLE t_message LINES wa_packlist-body_num. APPEND wa_receivers TO t_receivers. APPEND wa_message TO t_message. Advanced Configuration Scenarios . wa_message-line = text-007. APPEND wa_message TO t_message. CLEAR wa_message. *Populating the receipients LOOP AT t_param INTO wa_param. APPEND wa_message TO t_message. wa_receivers-notif_ndel = 'X'. * Populating the system ID CLEAR l_date. wa_packlist-head_start = 1. APPEND wa_packlist TO t_packlist. CLEAR wa_message. wa_receivers-receiver = wa_param-low. wa_message-line = space. ENDLOOP. wa_message-line = space. All rights reserved. CLEAR wa_message. APPEND wa_message TO t_message. *Calling function module to send email CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1' EXPORTING document_data = l_docdata put_in_outbox = 'X' commit_work = 'X' TABLES packing_list = t_packlist contents_txt = t_message receivers = t_receivers EXCEPTIONS too_many_receivers = 1 document_not_sent = 2 document_type_not_exist = 3 Ariba Network Adapter for SAP NetWeaver Setup Guide 242 © 2015 SAP SE or an SAP affiliate company. CLEAR wa_message. wa_message-line = text-006. ENDLOOP. wa_receivers-com_type = 'INT'. CLEAR wa_message. CLEAR wa_message. wa_receivers-rec_type = 'U'. CONCATENATE text-009 sy-sysid sy-mandt INTO l_date SEPARATED BY space. CLEAR wa_message. APPEND wa_message TO t_message. wa_message-line = space. wa_message-line = space. wa_packlist-head_num = 0. CLEAR wa_message. wa_packlist-transf_bin = space. In the Application field. 3. 243 . IF sy-subrc <> 0. ENDIF. 4. For example. Log on to your SAP ERP system. 8. ● Create a link between the standard business object and the new document type. ● Define a new document type for invoice. enter a description for the document class. 5. Click Save. All rights reserved. enter PDF. 7. Start transaction OAD2. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. In the Doc Class field. Defining a New Document Class for PDF Invoice Copy Attachments Procedure 1. 2. you must: ● Define a new document class. About Configuring Your SAP ERP System for PDF Invoice Copy Attachments To ensure that the PDF invoice copy attachment is processed in the SAP ERP system. SAPHTML. For example. In the Description field. enter the name of the application that will read the attached invoice PDF. ENDIF. Click New Entries. ENDIF. In the MIME type field. Portable Document Format. operation_no_authorization = 4 parameter_error = 5 x_error = 6 enqueue_error = 7 OTHERS = 8. ● Maintain values for INVOICE_EMAIL_SEND and ZDEL parameters. ENDIF. application/pdf. 6. Log on to your SAP ERP system. enter a long name for the document type. Click Save. All rights reserved. This ensures that when a failure occurs while storing the Ariba Network Adapter for SAP NetWeaver Setup Guide 244 © 2015 SAP SE or an SAP affiliate company. enter the document class that you created earlier. Type field. Create a Link Between the Standard Business Object and the New Document Type for Invoice Procedure 1. Advanced Configuration Scenarios . For example. enter bus2081 (Standard business object for incoming invoice). Field. enter the document type you created earlier. 4. Log on to your SAP ERP system. enter MA. 6. 3. In the Link Status field. In the Doc. In the Object Type field. enter a document type for invoices.Defining a New Document Type for Invoice Procedure 1. 2. enter 0. 3. ensure that the value of the Status field is X. PDF. 7. Start transaction OAC3. 8. 6. 10. 9. 5. 4. enter TOA01. You must ensure that the Status of the document type is active. In the Document type field.Class field. 2. In Doc. In the Storage system field. Start transaction OAC2. 5. 7. enter X. Maintaining the INVOICE_EMAIL_SEND Parameter Ariba recommends you to specify an email address or multiple email addresses as a value for the parameter INVOICE_EMAIL_SEND in the /ARBA/PARAM_TAB table. Note You can copy the standard document type for invoice called MMILOGINV and create a new document type starting with Z. In this case. Click Save. enter X. In the Long Name field. In the Status field. In the Link field. Click New Entries. In the Retention per. specify values for the relevant parameters. see Request for Quotation Integration Scenario [page 196]. see Configuring Quote Request and Quote Message Documents [page 318]. open the communication channel for the invoice transaction.attachments in the SAP Archive Link or assigning the attachments to the invoice. This ensures that once the BADI accesses the attachments from the file location.0 EHP0 or higher with PI 7. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. the attachments in the file location are deleted. You need to configure the integration scenario for the Request for Quotation transaction in the Integration Directory to be able to run Ariba Spot Quote transactions. double-click the communication channel |BS_ASN|CC_Invoice_cXML_Sender or right-click and select Open. 2. In the Model Configurator. 4. an email notification is sent to the specified email addresses. Log on to your SAP NetWeaver system. About SAP ERP and Ariba Spot Quote Integration The Ariba Network allows buying organizations to integrate their ERP systems with the Ariba Network for the purpose of creating Spot Quote events. Maintaining the ZDEL Parameter You need to specify the delete command for the ZDEL parameter by using transaction SM69. Under the Attachment Configuration section. Under Communication Channel. This enables you to manage quotes and purchase orders from within your ERP system with the added benefits of Ariba Sourcing award functionality and Ariba Network supplier research. Integrating SAP ERP with the Ariba Spot Quote Solution Support for SAP ERP integration with the Ariba Spot Quote solution is available in SAP ERP 6. All rights reserved. For more information about configuring the Request for Quotation integration scenarios. and assigns them to the invoice. Save the changes. For more information about configuring your SAP ERP for Quote Request and Quote Message cXML documents. Configuring the Attachment Processing Mode for PDF Invoice Copy Attachments Procedure 1.1 or higher. 3. 245 . stores them in the SAP Archive Link. Ariba matched. Spot Quotes are ideal for smaller events. Invited and matched suppliers receive notifications about the Spot Quote event from Ariba and can then respond directly to the RFQ event in Ariba Sourcing. The Ariba Spot Quote solution supports the ability to upload suppliers from your ERP system in to Ariba Network. Advanced Configuration Scenarios . where an RFQ event is created and published on Ariba Discovery. or Ariba suggested. for example an event with 3 to 4 suppliers. created through a direct integration between your ERP system and Ariba Network. Ariba sends the winning bid information back to the SAP ERP system and a purchase order is created in the SAP ERP system. Suppliers can either be invited as part of the Spot Quote event or matched through Ariba Discovery. For more information about the Ariba Spot Quote solution. Depending on how the Ariba Spot Quote template is configured. that allows you to build and publish tactical sourcing events with little to no action from project owners in Ariba Sourcing. Uploaded suppliers are invited to create an Ariba Network account through automated notifications. allowing you to quickly experience online sourcing without a substantial commitment of time or resources. Spot Quotes originate in a your ERP system and are sent across the Ariba Network to Ariba Sourcing. whether the suppliers are buyer invited. All rights reserved. users can create a request for quotation from a purchase requisition or from scratch. see the Ariba Spot Quote Administration Guide on [email protected] Quotes are automated request for quotations (RFQs). Ariba Network Adapter for SAP NetWeaver Setup Guide 246 © 2015 SAP SE or an SAP affiliate company. Using the RFQ Module in their SAP ERP system. supplier responses can automatically be sent back to the originating ERP system with no action from project owners or you can manually award suppliers directly in the Ariba Spot Quote solution. SAP ERP Integration Users can initiate an Ariba Spot Quote event from their SAP ERP system and receive winning bids back as SAP ERP purchase orders using the Ariba Network Adapter for SAP NetWeaver. The supplier matching type is tied to the document type and a value mapping must be maintained. from scratch. In this case. For example. you must maintain the following value mappings in the SAP NetWeaver PI system: ● Source Agency "RFQ_ERP" with scheme "VendorConfig" ● Target Agency "RFQ_XI" with scheme "VendorConfig" SAP ERP RFQ Process To create a Spot Quote event in Ariba. the PI does not send supplier information to Ariba and Ariba invites multiple suppliers in the vendor and public matching methods. If you want to invite multiple suppliers to your Ariba Spot Quote event. A new document type can be created for this purpose or an existing document type can be used. a purchase order cannot be created in your ERP system if the vendor does not exist in your ERP system. you can use the one time vendor functionality available in SAP ERP. SAP ERP Quote Message Process After a Spot Quote event ends. All rights reserved. Users select a supplier matching option. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. If the default Spot Quote transaction rule is not configured in Ariba Network Buyer. create an “Ariba Marketplace Vendor” and configure it to not send any vendor information in the Quote Request cXML document. To overcome the one vendor limitation. SAP ERP users create an RFQ in SAP ERP MM Standard RFQ Module. Utilizing the one time vendor functionality involves creating a one time vendor in SAP ERP and specifying the one time vendor ID in the PI configuration mapping. When the default Spot Quote transaction rule is configured to send the Quote Message cXML document to your ERP system. To overcome this issue. enter event open and close dates. 247 . Users can create RFQs in SAP ERP from a purchase requisition.One Vendor Limitation SAP ERP only supports the ability to invite one specific supplier using the invited supplier method. Ariba Network sends the Quote Message cXML document to your ERP system. purchase orders are created using the one time vendor ID and the address for the vendor who submitted the bid. One Time Vendors When you configure the default Spot Quote transaction rules in Ariba Network Buyer. or potentially from an existing ERP contract. The Quote Message cXML document is transformed and mapped to BAPI structures in SAP Netweaver PI and a purchase order is created through RFC. the Quote Message cXML document stays in the Ariba Network and is not sent to your ERP system. and specify line items with material groups and receiving plants. After the one time vendor ID is mapped in the PI configuration. you can create a vendor in SAP ERP to workaround the SAP ERP limitation. Ariba sends a Quote Message cXML document with the winning bid results back to SAP ERP. the system uses the "Ariba Market Place" vendor. All rights reserved. so the vendors on the purchase order and RFQ do not match and the RFQ reference is not stored on the purchase order. Advanced Configuration Scenarios ./nslg1 ● Object .Additional Data Validation When a purchase order is created in SAP ERP./ARBA/ASCADAPTER ● SubObject. The RFQ number is not stored on the purchase order because SAP ERP validates if the supplier on the RFQ and purchase order are the same. the quote number is stored on the purchase order as the reference document number. Logging for purchase order creation: ● TCode used. You can view the logs to verify that the supplier on the RFQ and purchase order are the same. In the approved and public vendor scenarios./ARBA/QUOTEMESSAGE The following is an example of the log for a successfully created purchase order: The following is an example of the log for a purchase order that receives a warning: Ariba Network Adapter for SAP NetWeaver Setup Guide 248 © 2015 SAP SE or an SAP affiliate company. Spot Quote functionality cannot be used in existing Ariba Sourcing realms.0 EHP0 or higher with PI 7. for the cXML Version parameter. You must run the configuration wizard for the new request types in order to create the communication channel. ● After Ariba sends back the bidding results. ● Quote attachments are not transferred to purchase orders. Users should create a Ariba Marketplace Vendor. ● The SAP ERP adapter only supports the ability to send the lead bid back to the ERP system and does not support the ability to send all bidding results to the ERP system. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. 249 . SAP ERP and Ariba Spot Quote Integration Requirements Ariba Spot Quote integration with SAP ERP requires SAP ERP 6.The following is an example of the log for a purchase order that receives an error: Enabling SAP ERP and Ariba Spot Quote Integration To enable Spot Quote functionality. To support the integration of RFQs and QuoteMessages. ● SAP ERP does not support the ability to add attachments to the RFQ line item level.1 or higher. that allows them to invite all approved vendors to the Ariba Spot Quote event. enter 1. Suppliers must be registered on the Ariba Commerce Cloud to participate in Spot Quote events. QuoteRequest and QuoteMessage. All rights reserved. please contact your Customer Success Manager or Account Manager for more information on the Ariba Spot Quote Solution. SAP ERP and Ariba Spot Quote Integration Limitations Ariba Spot Quote integration with SAP ERP has the following limitations: ● The SAP ERP adapter only supports the ability to invite one supplier through the Invited supplier case. have been introduced.2. In addition. users can only create purchase orders in SAP ERP. two new request types.025 or higher for RFQ and QuoteMessage transactions. The Ariba Spot Quote solution must be deployed in a new realm. In this case. Configuring Ariba Network Buyer Settings for Ariba Spot Quote In order for the Ariba Network to forward quotes from public suppliers.com.com/xi/ASN/QuoteMessage For more information. ● Ariba recommends not creating RFQs with service lines. Integration of Catalog Data in SAP ERP and Ariba Network When you upgrade to a higher version of the SAP transports. How to Handle cXML Document Errors for Ariba Spot Quote If the Quote Request cXML document fails in mapping. see the mapping worksheets on http://connect. When you enable the Spot Quote rule in the Ariba Network and the quote message supplier does not exist in your ERP system. All rights reserved.● One-time vendor option does not support purchase order automation.ariba. you must configure the default transaction rules in Ariba Network. the event will fail and Ariba will send an email notification to the ERP initiator. fix the error and resend the cXML document from the Ariba Network. Advanced Configuration Scenarios . About Integration of Catalog Data in SAP ERP and Ariba Network [page 251] Enabling the Integration of Catalog Data [page 251] Ariba Network Adapter for SAP NetWeaver Setup Guide 250 © 2015 SAP SE or an SAP affiliate company. the one time vendor specified in the ERP system is used for the transaction. When the rule is disabled. If changes are made in SAP ERP after the Spot Quote event is published. ● Ariba does not support the ability to make changes after the Spot Quote event is published. Messages Mapping for Ariba Spot Quote The following Ariba Spot Quote mapping namespaces are available: ● http://ariba.com/xi/ASN/QuoteRequest ● http://ariba. quote messages are not sent to your ERP system and they will fail in the Ariba Network. you must create a proper relationship with the supplier and then resend the quote message from the Ariba Network. ensure that you make the necessary changes on your NetWeaver PI and SAP ERP system. fix the error and republish the IDoc. If the Quote Message cXML document encounters an error. 7. 251 . Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. Enabling the Integration of Catalog Data This section details the requirements to integrate catalog data on the SAP ERP system. For more information on the shared secret authentication and client-based certification. All rights reserved. Using the /ARBA/BUYER_CATALOG_EXPORT program. Workflow [page 253] Using the Catalog Export Program [page 253] About Processing Purchase Information Records and Material Master Records [page 256] Uploading Catalog Changes Using Mediated Connectivity [page 259] Uploading Catalog Changes Using the Incremental Load [page 259] Maintaining Catalog Fields [page 259] Configuring Catalog Data Integration [page 260] About Integration of Catalog Data in SAP ERP and Ariba Network This feature is applicable for SAP NetWeaver PI 7.4 and all SAP ERP 6. or 7. buyers can integrate the catalog data using the following methods: ● Full and incremental load ● Mediated Connectivity Buyers can use the shared secret authentication or the client-based certification to integrate the catalog data from SAP ERP system to Ariba Network.3. See the Limitation section for functionalities that are not currently supported. see the Ariba Catalog Format Reference Guide in the Product Documentation > For Users section of the Learning Center.0 (EHP5 and higher versions). The CIF file contains both mandatory and optional fields that suppliers can use while maintaining the catalog files. Customers can extract the catalog data from the Purchase Information records and Materials Master records to create catalog items in a CIF file and send it to Ariba Network and Ariba Procurement Solution.31. For more information about the CIF files. Creating a catalog file from an SAP ERP system allows buyers to: ● Readily find items that are available and in stock directly from the SAP ERP system ● Prevent purchase orders from being canceled or put on hold due to unavailability of items ● Allow direct purchasing on the SAP ERP system ● Support creation of the CIF items in multiple languages The catalog data extracted from the Purchase Information records and Materials Master records are saved as catalog items in a CIF file. The Ariba Network Adapter for SAP NetWeaver allows buyers to integrate catalog data from an SAP ERP system to Ariba Network seamlessly. see the Ariba Network Adapter for SAP NetWeaver® Setup Guide. see the section. ● Enable the Use SAP Add on Suite option in the cXML Configuration. For more information. This is required to write the change documents for the classification data for a material master record. For more information.Prerequisite To upload the catalog CIF file for the full and incremental through the mediated connectivity. see the Ariba Network Integration Guide.Network. ● Extracting catalog items using the Direct Connectivity method is not available in this release. then a valid Secure Socket Layer (SSL) client certificate from one of Ariba Network's trusted Certificate Authorities is required. ● Buyers must ensure that they enable the option. ● Configure the shared secret authentication or the client-based certificate authentication. Advanced Configuration Scenarios .Catalog. The SAP ERP system does not validate or restrict the file size of the catalog file based on the file size required by Ariba Network. ● Ensure that the commodity codes and unit of measure that you maintain on the SAP ERP system must also exist on the Ariba Network and Ariba Procurement Solution. For more information see the section.DefaultMSCif on their Ariba Procurement Solution to support a multi-supplier catalog CIF file from Ariba Network. see About Configuring Security Certificates section in the Ariba Network Adapter for SAP NetWeaver Setup Guide. For information about multi-supplier CIF catalogs in Ariba Procurement Solution. For more information. Limitations The /ARBA/BUYER_CATALOG_EXPORT program does not support the following: ● Extracting images for catalog line items. see About Configuring Security Certificates section in the Ariba Network Adapter for SAP NetWeaver Setup Guide. Proxy Settings in SAP ERP . The supplier must have an active trading relationship with the buyer. ● Customers must validate and publish the catalog sent from the SAP ERP system from their Ariba Network account. see the Catalog Administration Guide for your Ariba Procurement Solution. ● Ensure that the file size of the catalog CIF file must not exceed the maximum file size supported by Ariba Network. ● If the Ariba Network supplier account is configured to use digital certificate authentication. Allow multi-supplier CIF and set the parameter System. see Configuring the Integration Directory for Catalogs [page 261]. Defining Authorizations for Running Ariba Network Transactions in the Ariba Network Adapter for SAP NetWeaver Setup Guide. ● Ensure that you define authorizations for running Ariba Network transactions. Ariba Network Adapter for SAP NetWeaver Setup Guide 252 © 2015 SAP SE or an SAP affiliate company. ● To extract the commodity code maintained in the characteristic value of a class that belongs to a specific class type in the Classification view of the Material Master record. For more information about creating a buyer-supplier relationship. in the Ariba Network Adapter for SAP NetWeaver Setup Guide. All rights reserved. ● Ensure that you configure the proxy setting for single and dual stack on your SAP ERP system. For more information. buyers must do the following: ● Ensure that the supplier for that you are uploading the catalog must exist on the Ariba Network and Ariba Procurement Solution. buyers must implement the SAP Note 65124. They must also validate the catalog based on the catalog rules specified on Ariba Procurement Solution. You must also configure the integration scenario for uploading catalogs. For more information see the Ariba Network Adapter for SAP NetWeaver Setup Guide. and the ABC material is also associated to the plant 3000. ● The /ARBA/BUYER_CATALOG_EXPORT program imports the catalog data from the Purchase Information records and Materials Master records to create a catalog CIF file. ● When you create a purchase information record at a purchasing organization level for a material. The newly extended plant information is not staged in the \ARBA\CHANGE_DOCS table. Use the T-code /nse38 to view the /ARBA/BUYER_CATALOG_EXPORT program that has the following fields: Field Name Description The following are the header fields in the catalog CIF file. ● The /ARBA/BUYER_CATALOG_EXPORT program extracts the Valuated Unrestricted-Use Stock at the plant- level by totaling up the quantity available at the storage location of the plant. the catalog file is sent directly to Ariba Network. the catalog CIF file is stored on the SAP application server. when you make a change and extend the same purchase information record having the purchasing organization level(3000) to the plant 3000. and the material is also associated to a plant. If you have specify the Test Run option and provide a file path. Workflow The following describes the workflow for creating a CIF catalog file using the /ARBA/BUYER_CATALOG_EXPORT program from your SAP ERP system: ● The buyer administrator runs the /ARBA/BUYER_CATALOG_EXPORT program on the SAP ERP system. the /ARBA/BUYER_CATALOG_EXPORT program only sends Unit Price of $20 and lead time as 2 that was previously staged in the \ARBA\CHANGE_DOCS table on the SAP ERP system. All rights reserved. Using the Catalog Export Program Buyers can create variants to run the /ARBA/BUYER_CATALOG_EXPORT program multiple times for the full and incremental load. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. If you do not specify the Test Run option and want to use the Mediated Connectivity option. 253 . and the same purchase information record is again extended to the plant. This information is stored in the \ARBA\CHANGE_DOCS table on the SAP ERP system. For example. Now. ● When the Ariba Network Full Subscription Synchronization task runs. The variants can have different catalog filters and options that are required while running the / ARBA/BUYER_CATALOG_EXPORT program. the newly extended information is not sent to Ariba Network. the catalog is uploaded into the Ariba Procurement Solution for buyers. ● The /ARBA/BUYER_CATALOG_EXPORT program creates the catalog CIF file and sends it to Ariba Network. If the information has been previously staged on the ERP system. The /ARBA/ BUYER_CATALOG_EXPORT program does not track the change made to the quantity. but not yet sent to Ariba Network. you have created a purchase information record at the purchasing organization level(3000) for Material ABC having a Unit Price of $20 and lead time as 2. you must ensure that you send the information to Ariba Network before you again extend the same purchase information record of the associated purchasing organization to the plant. SupplierId_Domain The domain for the supplierID. All rights reserved. Code Format The default commodity code system. Note You must ensure that you use the existing catalog subscription name for each incremental load you run for an existing catalog. All new versions of the catalog continue to have the same catalog subscription name. For example. Required field.Field Name Description Catalog Subscription Name The catalog subscription name is a unique identifier in Ariba for the catalog. You must specify the UNSPSC format. Required field and is case-sensitive. Comments The comments for the catalog. Currency The default currency for unit prices for the items in the catalog. Required field. Example: SUPPLIERID_DOMAIN:DUNS Required field. Default value: USD Required field. Required field. Charset The encoding and charset to convert the data in the CIF file. UTF-8. Catalog Filters Contains the following filters: ● Plant ● Purchase Organization ● Supplier ● Purchase Info Category ● Material Group ● Material Type ● Language Ariba Network Adapter for SAP NetWeaver Setup Guide 254 © 2015 SAP SE or an SAP affiliate company. Ensure that you specify the SupplierId_Domain that you maintain for the supplier on the Ariba Procurement Solution. United Nations Unit of Measure Select this option to send the catalog in the UNUOM format. Advanced Configuration Scenarios . Ensure that you do not change the existing name for the catalog subscription while running the full or incremental load. The /ARBA/BUYER_CATALOG_EXPORT program validates the file path that you specify. The stage table /ARBA/DOC_CHANGE is cleared only after the catalog items are sent to Ariba Network. The CIF file is downloaded on your SAP application server. Field Name Description Product Hierarchy OR Classification Code as Commodity Contains two options: Code ● Product Hierarchy: This option allows you to download the commodity code maintained in the product hierarchy field present in the basic data view of the material master on the SAP ERP system. If you use this option. Specify the directory path in the Dir Path for file download field. . ● Classification Code: Choose this option if you want to use the commodity code maintained in Classification view for the full or incremental load. For more information. you must also specify additional parameters. Ensure that the application server directory exists with the necessary permissions before running the catalog import. Ensure that you do not use this option the first time to create a new catalog subscription. ● Update Catalog subscription: Choose this option only when you want to update an existing catalog subscription entirely using the full load. Load Option Contains the following options: ● Full Load: Allows you to extract all the Purchase Information records and Materials Master records. You can run the full load more than one time. the stage table /ARBA/DOC_CHANGE continues to store the previous extracted data for the first run using the Test Run option. You can optionally specify the the date from that you require the records to be extracted from the SAP ERP system. Test Run You can choose one of the following: ● Select the Test Run option when you want to run the catalog and check the CIF file before it is sent to Ariba Network. ● Incremental Load: Allows you to extract only the changed or updated records. All rights reserved. 255 . see Specifying Parameters for Downloading Commodity Code [page 267]. Specify the Ariba Network ID of the buyer in the Ariba Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. ● Do not select the Test Run option if you choose to upload the CIF file using the mediated connectivity. A folder "Catalog" is automatically created to store the catalog file when you specify the Test Run option or send the files using mediated connectivity. When you run the incremental load subsequently. All rights reserved. see the catalog mapping worksheet.xlsx. customers must specify a corresponding value for the SPSC Code field in the BAdI / ARBA/BUYER_CATALOG_EXPORT. see Maintaining the /ARBA/ TEMP_DIRECTORY Parameter [page 266]. To support blank values in this field. While extracting data for an incremental load. Note If the file path is invalid. However. The following describes how the /ARBA/BUYER_CATALOG_EXPORT program processes the purchase information records and the material master records while extracting the data to create catalog item: ● Applicable to Full and Incremental Load ○ The /ARBA/BUYER_CATALOG_EXPORT program extracts catalog items only if the material has a valid purchase information record and the material has an associated plant. the /ARBA/ BUYER_CATALOG_EXPORT program displays an error. Advanced Configuration Scenarios . the catalog file containing blank values in the Product Hierarchy or Classification Code fields fail on Ariba Network as Ariba Network validates this field. About Processing Purchase Information Records and Material Master Records The /ARBA/BUYER_CATALOG_EXPORT program processes the purchase information records and the material master records while extracting the data to create catalog items in the CIF file. This is applicable for both the full and incremental load.Field Name Description Network Buyer ID field. these changes are recorded in the catalog CIF file. Catalog_SAP_Field_Mappings. When these records are flagged for deletion on the SAP ERP system. The file path for mediated connectivity must be maintained in the parameter /ARBA/ TEMP_DIRECTORY in the /ARBA/PARAM_TAB table. For more information. ● SAP ERP does not support deletion of the entire catalog file. . For more information on the catalog fields in the CIF file. As a result. you cannot delete an entire catalog from the SAP ERP system using the Ariba Network Adapter for SAP NetWeaver. Enter the email address of the buyer in the Email Notification to Buyer field. If you have a material only Ariba Network Adapter for SAP NetWeaver Setup Guide 256 © 2015 SAP SE or an SAP affiliate company. ● The SAP ERP system does not delete the catalog CIF files downloaded and saved on the SAP application server during test run. the /ARBA/BUYER_CATALOG_EXPORT program records all changes done to existing data for material master and purchase info records. Note ● The /ARBA/BUYER_CATALOG_EXPORT program does not validate the values in the Product Hierarchy or Classification Code fields. The column Delete in the CIF file contains the value T (True) to indicate that there has been a change to the catalog item on the SAP ERP system. the /ARBA/ BUYER_CATALOG_EXPORT program extracts the purchase information record for all the plants associated to the material in the CIF catalog. While running an incremental load. But this fails on Ariba Procurement Solution as the catalog item has already been deleted. ○ If the purchase information record information for a material is available at only the plant and purchasing organization level. ○ The catalog export program considers the material master record invalid when the From date field has a blank value or stores a date that is earlier than the date on which the record was previously extracted. ○ If you mark a purchase information record or material master record for deletion on the SAP ERP system and run the incremental load. ○ The /ARBA/BUYER_CATALOG_EXPORT program does not extract catalog items for a full load if the vendor material number (Supplier Part ID) maintained for a purchase information record is unavailable. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. ○ If there is a purchase information record only at the purchase organization level. or OB. and you create a purchase information record only at the header-level. the /ARBA/BUYER_CATALOG_EXPORT program considers only the newly entered value for the vendor material number and discards the earlier value you changed. the deleted catalog item is again sent to Ariba Procurement Solution. the catalog data extracted contains the purchase information record information only for the plant that is associated to the material. And the Purchasing View tab for the material has the following plant-specific material status: ○ 01 (Blocked for procurement/where house) OR ○ BP (Blocked for purchasing) OR ○ OB (obsolete materials) Note When a Full load is run. ○ When you associate a purchase information record to a purchasing organization and make changes the existing vendor material number (Supplier Part ID). BP. the catalog item for the purchase information record or material master record is marked for deletion on Ariba Procurement Solution system. All rights reserved. ○ When you create a purchase information record for a material. The /ARBA/BUYER_CATALOG_EXPORT program does not filter the vendor marked for block or delete. but do not specify a vendor material number. the /ARBA/ BUYER_CATALOG_EXPORT program does not consider this purchase information record for the catalog file. ○ The /ARBA/BUYER_CATALOG_EXPORT program does not extract the catalog item if the purchase information record is having only a material group-level. the /ARBA/BUYER_CATALOG_EXPORT program does not include the catalog item in the CIF file if the From date is invalid and the Purchasing View tab for the material has a plant- specific material status as 01. However. ○ The /ARBA/BUYER_CATALOG_EXPORT program extracts purchase information records and material master records that have vendors marked for block or delete. if you make changes to the same deleted catalog item on the SAP ERP system and run the incremental load. associated to a plant. This date is considered as the expiration date of the catalog item on the SAP ERP system. 257 . any purchase information records and materials master records marked for block or delete is processed as changes and the corresponding item in the CIF file is marked as T in the Delete column. the /ARBA/BUYER_CATALOG_EXPORT program does not consider the purchase information record as a catalog item while running the incremental load. ○ The Valid From date for the material is extracted from the Purchasing View on the SAP ERP system. ○ Purchase information records and Materials master records that have records marked for block or delete. ○ When you make changes to a specific field for a material record. Advanced Configuration Scenarios . ○ While running the incremental load. the /ARBA/ Ariba Network Adapter for SAP NetWeaver Setup Guide 258 © 2015 SAP SE or an SAP affiliate company. Note When you need to make changes to the vendor material number. the /ARBA/BUYER_CATALOG_EXPORT program processes the change as follows: If the catalog item for the material record is already available on Ariba Network. This Delete column for this catalog item does not store the "T" value. ○ When you extend a material master to a new Plant. This information is also not yet sent to Ariba Network. the /ARBA/BUYER_CATALOG_EXPORT program considers the changed and deleted catalog items to already exist in the Ariba procurement system. BP. The first change that you make to the vendor material number is always recorded as marked for deletion and the /ARBA/BUYER_CATALOG_EXPORT program does not consider any further changes. ○ If you delete the language for the material description. This Delete column for the catalog item contains “T” in the CIF file. The Item Description field is a mandatory field and if this is marked for delete. ○ You run the incremental load. ● Applicable to Incremental Load ○ The Flag for deletion option on the SAP ERP system is supported for the following levels: ○ Material or Plant level for material master records ○ Complete Info Record or purchasing organization level for purchase information records ○ When a buyer changes the Vendor Material number (Supplier Part Id) of a valid purchase information record for a material. Ariba Network automatically deletes the catalog item. As a result. This change is staged in the change table on SAP ERP system. This catalog item with the previously entered value is marked as “T” in the Delete column of the CIF file. The /ARBA/ BUYER_CATALOG_EXPORT program adds a new entry for the vendor material number (Supplier Part id) of a valid purchase information record for a material master. the /ARBA/BUYER_CATALOG_EXPORT program marks the description for the material item for deletion and sends the value “Deleted Language Record” in the Item Description field in the CIF file. the newly changed vendor material number is added as a new catalog item in the CIF file. ensure that you do not delete the language for the material description. the /ARBA/BUYER_CATALOG_EXPORT program considers the previously entered value of the vendor material number (Supplier Part ID) in the catalog CIF file. or OB. For example. you make a change to the vendor material number. ensure that you always run the incremental load first and then make the change to the vendor material number. The /ARBA/ BUYER_CATALOG_EXPORT program adds a new entry for the newly changed catalog item. ○ The /ARBA/BUYER_CATALOG_EXPORT program marks the catalog item as “T” in the Delete column of the CIF file if the From date date is blank and the Purchasing View tab for the material has a plant-specific material status as 01. this item is deleted from Ariba Network and Ariba Procurement Solution. If the language is deleted before you save the material master. ○ You make a change to a description field for a material record. Now. ○ Purchase information records that contains any changes to the vendor material number (Supplier Part ID) are still considered records with changes. and then make changes to the vendor material number for the same material record. All rights reserved. the /ARBA/BUYER_CATALOG_EXPORT program does not consider the changes to the vendor material number are not flagged for deletion when you run the incremental load. ○ For the same material record. Maintaining Catalog Fields To maintain the Ariba field names in the SAP ERP system. Ariba Network Adapter for SAP NetWeaver displays the SAP field name for the column on Ariba Network and the Ariba Procurement Solution. BUYER_CATALOG_EXPORT program marks the language for the newly created Plant for deletion. These new custom Ariba fields can be mapped to the SAP fields in the /ARBA/FL_MAP table. When you do not specify the Test Run option in the /ARBA/BUYER_CATALOG_EXPORT program. ● The CIF file created on the ERP system contains additional fields.If the file path is invalid. Uploading Catalog Changes Using the Incremental Load New values or changes done in the purchase information record or the material master records can be uploaded on Ariba Network and Ariba Procurement Solution. If you do not add this field. Ariba Account Administrator must first create these custom fields with the required Ariba field name on their Ariba Procurement Solution. Note You must ensure that you use the existing catalog subscription name for each incremental load you run for an existing catalog. For more information. see Maintaining the /ARBA/TEMP_DIRECTORY Parameter [page 266]. Buyers must specify the Ariba Network ID and email address of the buyer while specifying the conditions for uploading the CIF file using the mediated connectivity. When the record is sent as a catalog item to Ariba Network. and the corresponding Ariba field name to the /ARBA/FL_MAP table to have a preferred column name in the CIF files. The file path for mediated connectivity must be maintained in the parameter /ARBA/TEMP_DIRECTORY in the / ARBA/PARAM_TAB table. add the field. Uploading Catalog Changes Using Mediated Connectivity Buyer can choose to upload the CIF file using the mediated connectivity. Buyers must run the incremental load to upload the new values to an existing catalog . The CIF file is embedded as an attachment in the cXML and sent to Ariba Network.CIF file. this program uploads the CIF file using the mediated connectivity. its structure. Buyers can specify a date period while running the incremental load to download data that has been changed or newly during the date period. All rights reserved. 259 . You must maintain the Ariba field names for the following fields in the /ARBA/FL_MAP : Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. this catalog item for the material record fails. ● If you add catalog fields to the customized RFC structure. Ariba Network displays an error. see section that describes the fields in the /ARBA/BUYER_CATALOG_EXPORT program. For more information on the fields. Specify the values for the catalog CIF file. Standard. Field Name Description MATNR SAP ERP Material Number WERKS Plant EKORG Purchase Organization ESOKZ Purchase Info Category. 3. Creating the Catalog CIF File [page 260] Handling Errors [page 261] Configuring your SAP NetWeaver PI for Catalog Data Integration [page 261] Configuring your SAP ERP System for Catalog Data Integration [page 265] Creating the Catalog CIF File Context Run the /ARBA/BUYER_CATALOG_EXPORT program that allows you to extract the the Purchase Information records and Materials Master records and create a catalog CIF file. Click Execute. you must download the latest transport files. All rights reserved. Ariba Network Adapter for SAP NetWeaver Setup Guide 260 © 2015 SAP SE or an SAP affiliate company. configure your SAP NetWeaver PI. Subcontracting. Enter /ARBA/BUYER_CATALOG_EXPORT in the Program field. 2. Advanced Configuration Scenarios . 4. and SAP ERP systems. Go to the T-code /nse38. Pipeline and Consignment. Click Execute. LABST Valuated Unrestricted-Use Stock INFNR Purchase Information Record Configuring Catalog Data Integration To support creating a catalog CIF file for the Purchase Information records and Materials Master records. Procedure 1. 5. For example. All rights reserved.Handling Errors Buyers can use the transaction. Configuring the sender and receiver relations for individual connections. Assigning the model. The integration scenario is loaded into the Integration Repository when the design package is imported. Configuring the Integration Directory for Catalogs [page 261] Configuring the Integration Directory for Catalogs Buyers must configure the integration directory to integrate catalog data from an SAP ERP system to Ariba Network. SXMB_MONI to view the following errors: ● System errors that occurred while uploading the catalog data from the ERP system to the PI ● Errors while sending the catalog CIF file through the mediated connectivity Configuring your SAP NetWeaver PI for Catalog Data Integration Configure the integration scenario on your SAP NetWeaver PI for catalog data integration. Configuring the Integration Scenario involves the following steps: 1. 2. Generating the configuration objects. 4. 261 . Assigning the components. 3. Transferring Integration Scenario for Catalogs [page 261] Assigning the Model for Catalogs [page 262] Assigning Components for Catalogs [page 262] Configuring Sender and Receiver Relations for Individual Connections For Catalogs [page 263] Generate Objects for Catalogs [page 264] Configuring Communication Channels for Catalogs [page 264] Activating the Scenario for Catalogs [page 265] Transferring Integration Scenario for Catalogs Context The first step is to transfer the integration scenario to the Integration Builder. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. 2.com/xi/ASN/Catalog/ Software Component Version: ARBA_SUPPLIER_CONN_ADAPTER CI6 of ariba.Procedure 1. and then login to the Configuration: Integration Builder application. click the Assign Component button. and then click the Display Input Help pull-down menu and select Input Help. In the Integration Builder menu. select Tools Apply Model from ES Repository . click the Name field. Ariba Network Adapter for SAP NetWeaver Setup Guide 262 © 2015 SAP SE or an SAP affiliate company. In the Model Configurator window. All rights reserved. click the Select Component View button. Select the process integration scenario for the following transactions from the Enterprise Services Repository screen: Supplier ○ Catalog Name: AR_CatalogUpload Namespace: http://ariba. In the first screen of the Transfer Model from ES Repository wizard. After selecting the model. 2. Results Once the integration scenario transfer is completed. If required. 4. select the Business System Components for A2A tab to assign components for Ariba Network. and then click Apply to select the unique model that is selected by default. assign components to the application components for the selected integration scenario. the Model Configurator window appears.com 5. Select Process Integration Scenario. Assigning Components for Catalogs Procedure 1. In the Model Configurator. Click Finish. select Integration Directory Integration Builder . 6. Advanced Configuration Scenarios . In the Assign Components window. Assigning the Model for Catalogs Procedure 1. 2. change the name of the scenario for the Integration Directory. Click Continue. 7. From the SAP NetWeaver PI main page. 3. Note If you have multiple ERP systems. Click the Save Settings button. 4. Click the Next Role button (the right arrow) to go to the next screen on the window. Click Continue. click the Configure Connections button. from the selection list and click Apply. Select the communication component name for the business system for Ariba Network. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is available. 263 . 8. 2. 7. then click the Value List pull-down menu and select Value List <F4. from the selection list and click Apply. Click the row under the Communication Component column. Click the row under the Communication Component column. add the multiple communication components defined for your multiple SAP PI systems by repeating the Step 3 and 4. 6. Click the New Communication Channel button (the icon at the top left). and then select Create Communication Channel with Template to start the Create Communication Channel wizard. 5. then click the Value List pull-down menu and select Value List <F4. In the Connections from Component Assignment tab in the Configure Connection window. 3. You must assign Communication Channels to set up the connections. Click Finish. All rights reserved. click the Name field and then click the Display Input Help pull-down menu and select Input Help. 6. 5. You can also choose to modify the channel names. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. 3. On the next page. In the Model Configurator. Select the communication component name for the business system of your SAP PI system. 4. Click Continue. 8. click the empty Communication Channel cell corresponding to the business system for Ariba Network in the Receiver Business System Components table. Configuring Sender and Receiver Relations for Individual Connections For Catalogs Procedure 1.com/xi/ASN/Catalog/ Software Component Version: ARBA_SUPPLIER_CONN_ADAPTER CI6 of ariba.com 7. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. Select the Communication Channel Templates for the following transactions: Supplier ○ Catalogs Name: CCT_CatalogUpload_cXML_Receiver Namespace: http://ariba. Advanced Configuration Scenarios . Click on the Value List drop down and select Value List <F4. Click the Activate All Connections button. do the following: ○ Click Generation in the General section. Click Start to begin generating objects. 4. Generate Objects for Catalogs Procedure 1. click Apply to save the new configuration settings. If they already exist. click the Create Configuration Object button. The text box already contains an object name that you can use or modify. if required. 11. double-click the following communication channels to open it: Supplier ○ Catalogs |< Name of the Business System for Ariba Network |CCT_CatalogUpload_cXML_Receiver under the AR_CatalogUpload Configuration Scenario. 12. and Interface Determination check boxes in the Scope of Generation section. and then click OK. Tip If you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction. ○ Select the Receiver Determination. After the object generation is complete. You can save it. Select the CC_Proxy_Sender communication channel from the selection list and click Apply. click the empty Communication Channel cell corresponding to the business system of your ERP PI system in the Receiver Business System Components table. you can create the communication channel by copying from a channel that has already been configured. if required. Configuring Communication Channels for Catalogs Procedure 1. In the Connections from Component Assignment tab. 3. Generating the objects creates the configuration objects if they do not yet exist. Close the log that is created without saving. 5. Ariba Network Adapter for SAP NetWeaver Setup Guide 264 © 2015 SAP SE or an SAP affiliate company. Click Create New in the Change List for Generated Objects section. 2. In the Model Configurator. In the Create Configuration Object window. All rights reserved. In the Communication Channel list. You can also simulate generation for test purposes. Click the Save Settings button. 10. they are reused and enhanced. 9. Note If you created the channel by copying from an existing channel. 6. CatalogUploadRequest> in the Outbound Request Type field. Configuring your SAP ERP System for Catalog Data Integration Configure the your SAP ERP system for catalog data integration. 3. activate all the change lists containing the objects created and modified during the component setup. If required. All rights reserved. 4. In the Parameters tab. Results This completes the configuration of the outbound transactions in SAP NetWeaver PI.for example. 265 . edit the other parameters. set the parameters in the Authentication section to match your Ariba Network supplier account configuration. 5. you must change the request type for each of the transactions to the <Name of the transaction request . select the Use SAP Add on Suite check box. 2. Update the cXML version parameter to the latest applicable version. Activating the Scenario for Catalogs Procedure Using the Change List tab on the main application screen. Save the changes. Maintaining the /ARBA/TEMP_DIRECTORY Parameter [page 266] Adding Additional Catalog Fields [page 266] Specifying Parameters for Downloading Commodity Code [page 267] Customizing the Class Type in IMG [page 268] Using Customization [page 268] Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. Under the cXML Configuration section. If the file path is invalid.Maintaining the /ARBA/TEMP_DIRECTORY Parameter Context Maintain the parameter /ARBA/TEMP_DIRECTORY in the /ARBA/PARAM_TAB table if you are using the mediated connectivity to upload the catalog . Go to /ARBA/PARAM_TAB table. The /ARBA/BUYER_CATALOG_EXPORT program uses the file path you maintain in this parameter. Click Maintain. These additional Ariba fields can be mapped to the SAP fields in the /ARBA/FL_MAP table. Advanced Configuration Scenarios . Ariba Network Adapter for SAP NetWeaver Setup Guide 266 © 2015 SAP SE or an SAP affiliate company. The /ARBA/BUYER_CATALOG_EXPORT program validates the file path that you specify. Procedure 1. Adding Additional Catalog Fields Context To maintain the Ariba field names in the /ARBA/FL_MAP. 2. Choose table view /ARBA/FL_MAP. Note A folder "Catalog" is automatically created to store the catalog file.CIF file. Maintain the following values: ○ Variable Name: /ARBA/TEMP_DIRECTORY ○ Field Name Number 0 ○ INCL/EXCLI ○ Option EQ ○ Selection value File path to store the catalog . 2. buyers must first create these additional fields with the required Ariba field name on their Ariba Procurement Solution system. This is an optional task. 3. Start transaction SM30.CIF file. The Change View "Table to maintain mapping of SAP to Arib fields": Overview page appears. the /ARBA/ BUYER_CATALOG_EXPORT program displays an error. Procedure 1. All rights reserved. /ARBA/BUYER_CAT_CLASS and /ARBA/BUYER_CAT_INT_CHAR_NO. Maintain the following Characteristics Name maintained in CL01 transaction:for the characteristic value that must be extracted as the commodity code maintained in the Classification view for a particular class type and class. Maintain the following Class type in the classification view of material master: ○ Variable Name: /ARBA/BUYER_CAT_CLASS_TYPE ○ Field Name Number: 0 ○ INCL/EXCL: I ○ Option: EQ ○ Selection value: For example. CL125. 3. 001. ○ Variable Name: /ARBA/BUYER_CAT_INT_CHAR_NO ○ Field Name Number: 0 ○ INCL/EXCL: I Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios © 2015 SAP SE or an SAP affiliate company. Ensure that you must user or create a characteristic value of the CHAR data type. All rights reserved. The /ARBA/BUYER_CATALOG_EXPORT program displays an error if you do not maintain these parameters when specifying the Classification Code as Commodity Code option. 2. Select each of the following additional fields in the Field SAP column. Enter the corresponding Ariba field name in the Field Ariba column: ○ MATNR ○ WERKS ○ EKORG ○ ESOKZ ○ LABST ○ INFNR 5. Go to /ARBA/PARAM_TAB. Maintain the following Class in the classification view of material master: ○ Variable Name: /ARBA/BUYER_CAT_CLASS ○ Field Name Number: 0 ○ INCL/EXCL: I ○ Option: EQ ○ Selection value: For example. Specifying Parameters for Downloading Commodity Code Context If you use the commodity code maintained in Classification view for the full or incremental load. 4. Save the changes. 267 . you must maintain the /ARBA/BUYER_CAT_CLASS_TYPE. parameters in the /ARBA/PARAM_TAB. 4. Procedure 1. 4. Click Maintain Object types and Class types. 3. buyers must implement the SAP Note 65124. Ensure that the Chg.. Go to Tcode SPRO and then click SAP reference IMG. CH0023. Advanced Configuration Scenarios . All rights reserved. docs for Class is selected in the Classification section. Select Class Type 001 and click the Details button. Select the MARA option in the table and double click the Class Types folder. Buyers must also run the program RCCLUKA2 and set the "Multiple Objects Type Allowed” indicator. 5. Click Cross Application Components. Using Customization Customers can use the BAdI to customize the /ARBA/BUYER_CATALOG_EXPORT program. ○ Option: EQ ○ Selection value: For example. 9. 2. Click Classification System and then click Classes. Customizing the Class Type in IMG Context To extract the commodity code maintained in the characteristic value of a class that belongs to a specific class type in the Classification view of the Material Master record. Ensure that Change Docs check box is selected in the Classification section. This is required to write the change documents for the classification data for a material master record. Procedure 1. The interface /ARBA/IF_EXP_BUYER_CATALOG contains the following methods: ● MODIFY_PIR ● MODIFY_MATERIAL ● PUBLISH_CIF Ariba Network Adapter for SAP NetWeaver Setup Guide 268 © 2015 SAP SE or an SAP affiliate company. Double-click the Objects folder. 7. 8. Click the Object Table folder in the Data Structure tree view. 6. Configuring Your SAP ERP System Importing Custom Code [page 269] Configuring SAP [page 270] Proxy Settings in SAP ERP [page 294] Documentation of RFCs Within the SAP NetWeaver Adapter [page 298] Defining Authorizations for Running Ariba Network Transactions [page 298] Configuring Advanced Pricing Details [page 299] ABAP Programs for Outbound Transactions Implemented Using Proxies [page 299] Configuring Implicit Enhancements for Comments in Order Confirmations [page 300] Configuring Invoice Status Updates [page 301] Configuring Order Inquiries [page 304] Configuring Scheduling Agreement Releases [page 309] Configuring Ship Notices Against Multiple Purchase Orders [page 313] Configuring Returns and Corrections in Receipts [page 315] Configuring Quote Request and Quote Message Documents [page 318] Configuring Support for Line Level Hierarchies in Service Purchase Orders [page 321] Direct Invoicing of Purchase Order Service Items [page 325] Configuring Service Sheets [page 326] Configuring ERP-Initiated Invoices to Use the IDOC [page 331] Importing Custom Code The Ariba Network Adapter for SAP NetWeaver uses custom code to support ERP-initiated invoice, invoice status update, and payment proposal transactions. If you do not import the custom code for these transactions into your SAP instance, you are likely to encounter errors. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. All rights reserved. 269 Configuring SAP IDocs The following SAP IDoc configurations are required for using the sample data mappings: Transaction IDoc Basic Type Message Type Purchase Order (New and Change) ORDERS05 ORDERS Order Confirmation ORDERS05 ORDRSP Ship Notice DELVRY06 DESADV Invoice INVOIC02 INVOIC Remittance PEXR2001 REMADV Order Status Request ORDERS05 ORDERS ScheduleAgreementReleaseRequest DELFOR02 DELINS Configuring SAP The following steps pertain to the SAP ERP system and assume that you are familiar with your SAP application. If you need more information about how to perform a specific step, see the documentation for your SAP application. ● Configuring SAP for IDoc Transactions [page 271] ● Configuring the Partner Profile [page 271] ● Maintaining Condition Records for Outbound Transactions: POs [page 279] ● Making Additional Change PO Configurations [page 280] ● Maintaining Variants for Remittance [page 280] ● Making Additional Invoice Configurations [page 280] ● Making Additional Tax and Accrual Calculation Configurations [page 282] ● Maintaining Bank Key for the House Bank for Payment Remittance Advice [page 288] ● Making User Exit Enhancements to Support Shipping and Handling Charges [page 288] ● Maintaining Global Company Code [page 291] ● Configuration Related to Export of Requisitions from SAP ERP [page 292] ● Business AddIns [page 292] Ariba Network Adapter for SAP NetWeaver Setup Guide 270 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Configuring Your SAP ERP System Configuring SAP for IDoc Transactions Procedure 1. Use Transaction SM59 to create an RFC destination of type ERP. 2. Enter Target host, System Number, Getaway host, Getaway service on the Technical Settings tab, enter Language, Client, User, Password on the Logon/Security tab, and then save your entries. 3. Use Transaction WE21 to create a port. 4. Choose Transactional RFC and click Create. 5. Enter port, description and RFC destination details, and then save your entries. Configuring the Partner Profiles Buyers can specify the partner profile for each vendor or maintain the partner profile at a logical system level for all vendors. ● If you are using Ariba Cloud Integration Release 5.0 or lower, you can only maintain the partner profile for each vendor. ● If you are using Ariba Cloud Integration Release 6.0, you can maintain the partner profile for each vendor or maintain the partner profile at a logical system level for all vendors. Configuring the Partner Profile at Vendor-Level [page 271] Configuring the Partner Profile at Logical System-Level [page 275] Configuring the Partner Profile at Vendor-Level Buyers can specify the partner profile for each vendor. If you are using Ariba Cloud Integration Release 5.0 and lower, you can maintain the partner profile for each vendor. ● For New Purchase Order: 1. Use transaction WE20 to create a partner profile for a vendor. 2. Choose Partner type LI (Vendor) and click Create. 3. Enter partner (vendor) number, partner type (as LI) and appropriate Typ, Agent, and Lang. Save your entries. 4. Click Create outbound parameter (the green plus sign). 5. Enter Partner function, Message type, Receiver port (created in step 4 of the previous section) and Basic type. 6. On the message control tab, enter Application, Message type, and Process code. 7. Save your entries. ● Configure New and Change Purchase Orders using these parameters: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. All rights reserved. 271 Note Use the following Change Purchase Order partner profile parameters if you are using the Ariba Cloud Integration 5.0 and higher. Parameter Value Partner function VN Message type ORDERS IDoc type ORDERS05 Application EF Message type NEUS Process Code ME10 Change True (Checked) Retain the default selection, Transfer IDoc Immed., for the Output Mode parameter in the Outbound Options tab. ● Configure Change Purchase Order using these parameters: Note Use the following Change Purchase Order partner profile parameters if you are using the Ariba Cloud Integration 4.0 and lower.. Parameter Value Partner function VN Message type ORDCHG IDoc type ORDERS05 Application EF Message type NEUS Process Code ME11 Ariba Network Adapter for SAP NetWeaver Setup Guide 272 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Configuring Your SAP ERP System Parameter Value Change True Retain the default selection, Transfer IDoc Immed., for the Output Mode parameter in the Outbound Options tab. ● Configure Invoice using these inbound parameters: Parameter Value Partner function VN Message type INVOIC Process Code INVL Select Trigger immediately as the value for the Processing by Function Module parameter if you want real time processing. ● Configure Order Confirmation using these inbound parameters: Parameter Value Partner function VN Message type ORDRSP Process Code ORDR Select Trigger immediately as the value for the Processing by Function Module parameter. ● Configure Ship Notice with these inbound parameters: Parameter Value Partner function VN Message type DESADV Process Code DESA Select Trigger immediately as the value for the Processing by Function Module parameter if you want real time processing. ● Configure Outward Payment Remittance Advice with these outbound parameters: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. All rights reserved. 273 Parameter Value Partner function VN Message type REMADV IDoc Type PEXR2001 Retain the default selection, Transfer IDoc Immed., for the Output Mode parameter in the Outbound Options tab. Note You must also configure the bank in the partner profile for the remittance with the relevant port number. ● Configure Early Payment with these inbound parameters: Parameter Value Partner function VN Message type FIDCCH Process Code FICH Select Trigger immediately as the value for the Processing by Function Module parameter if you want real time processing. Note If you are using an SAP ERP version that is lower than the SAP ERP 6.0, EHP 6, ensure that you apply the SAP Note 1587217 (FI_DOCUMENT_CHANGE: EMPFB, XREF1_HD, XREF2_HD not changeable) before you run the PayMeNow program. The Ref.key(head) 1 'ARIBA_PMN' in the PI Mapping checks for invoices that have been fully approved when the PayMeNow program runs. When this key is enabled, Ariba Network Adapter for SAP NetWeaver does not send payment proposals that are fully processed and ready for payment to Ariba Network. Related Information Configuring the Partner Profile at Logical System-Level [page 275] Ariba Network Adapter for SAP NetWeaver Setup Guide 274 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Configuring Your SAP ERP System Configuring the Partner Profile at Logical System-Level If you are using Ariba Cloud Integration Release 6.0, you can maintain the partner profile for each vendor or maintain the partner profile at a logical system level for all vendors. SAP ERP buyers using Ariba Network Adapter for SAP NetWeaver can maintain SAP ERP partner profile for each vendor or maintain the partner profile at a logical system level for all vendors. This eliminates the buyer's need to maintain multiple IDOC messages exchanged between the SAP ERP system and the SAP PI layer for each vendor. Buyers can maintain the partner profile on a logical system level for the following transactional documents: Inbound Document Types ● Order Confirmation ● Invoice ● Ship Notice ● Pay Me Now Outbound Document Types ● Purchase Order ● Remittance ● Order Inquiry ● Schedule Agreement Release ● Quote Request. Configuring the Partner Profile on the SAP ERP System [page 275] Configuring the Partner Profile for Scheduling Agreement Releases [page 277] Configuring the Partner Profile for Invoices [page 278] Configuring the Partner Profile on the SAP ERP System Context Configure the partner profile at the logical system-level for all vendors. Procedure 1. Go to T-code BD54 to create a logical system. 2. Click New Entries. 3. In the Log.System column, enter the name of the logical system. Save the changes. 4. Go to T-code WE20 to create a partner profile. 5. Click the Create button. Create the partner profile as “Partner Type LS.” 6. Enter the logical system name in the Partner No. text box. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. All rights reserved. 275 7. Enter “LS” as the logical system in the Partn. Type text box. 8. In the Outbound parmtrs. and Inbound parmtrs sections, add the message type for each type of outbound and inbound transaction. 9. In the Partner profiles: Outbound parameters, ensure that you have the following values: Purchase Orders ○ Message Type: ORDERS ○ Partner No.: Name of the logical system ○ Partn. Type: LS (Logical system) ○ Partner Role: LS In the Outbound Options tab, ensure that you have the following values: ○ Receiver port: Name of the transactional RFC port ○ Transfer IDoc Immed.: Selected ○ Basic type: ORDERS05 In the Message Control tab, ensure that you have the following values in the table: ○ Application: EF ○ Message type: NEU ○ Process code: ME10 10. In the Partner profiles: Inbound parmtrs, add the required inbound transactions that you need. In the Partner profiles: Inbound parmtrs section, ensure that you have the following values for the inbound transaction: Ship Notice ○ Message Type: DESADV ○ Partner Role: LS Order Confirmation ○ Message Type: ORDRSP ○ Partner Role: LS Note You can add the LS partner roles for the other inbound transactions. 11. Start the NACE transaction. 12. Select application <EF>Purchase Order and click Condition records. 13. Click NEU as the output type. 14. Double-click the NEU output type and click Purchasing Output Determination: Doc. Type/Purch.Org/ Vendor. 15. Click Enter. Preserve the values for the purchase organization and vendor. 16. Specify the following in the Change Condition Record (New PO printout): Fast Change page: . ○ Vendor: The vendor ID ○ Funct: LS ○ Partner: The logical system created in Step 1. Ariba Network Adapter for SAP NetWeaver Setup Guide 276 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Configuring Your SAP ERP System EPH 2 and EPH 3. ○ If you are a customer using SAP ERP 6. ○ If you are a customer using SAP ERP 6.0. and you already have applied the SAP Note 1441799. 7. A new window appears. 2. Note ○ You must maintain the logical system name for the Invoice Status Update (ISU) in the /ARBA/ PARAM_TAB table. ○ If you are a customer using SAP ERP 6. ○ To maintain the logical system name for Remittances. Repeat Step 3 to 6 for the LPJ1 output type. ensure that to make the necessary source code changes and the assigned corrections. 3. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. Go back to the NACE transaction. you must make the necessary source code changes and the assigned corrections. Define the LS partner profile and maintain the following values: ○ Medium: EDI ○ Funct: LS ○ Name: Logical system 6. 8.0. Double-click the LPH1 output type. A new window appears. Procedure 1. Click EL application type and then click Output Types.0. All rights reserved. 10. Configuring the Partner Profile for Scheduling Agreement Releases Context Configure the partner profile on your ERP system for the LPJ1 and LPHI output types in scheduling agreement releases. 277 . Double-click the LPH1 output type. Start the NACE transaction. If you do not have the SAP Note. Click EL application type and then click Condition Records. EPH1. Click the Default values tab and maintain the following values: ○ Dispatch time: Send immediately (when saving the application) ○ Transmission Medium: EDI ○ Partner Function: LS ○ Communication strategy: To be left blank 5. A new window appears. you must apply the SAP Note 1441799 . EPH 7 and higher. You must ensure that you make the assigned corrections. 4. the SAP Note 1441799 is already applied. 9. then ensure that you make the assigned corrections.IDoc REMADV: Alternative partner category and partner number. Save the changes. 11.code name in the invoice: Enter the company code name.Type/Purch. ○ CoCd: Enter the company code. Configuring Your SAP ERP System . Ensure that you have the following values: ○ Partn. 13. Repeat Step 10 to 11 for the LPJ1 output type. Go to SPRO > MM > Logistic Invoice Verification > EDI > Assign Tax codes. Assign the tax codes. ○ Company Name: Enter the company name. ○ CoCd: Enter the company code. Procedure 1. Assign the program parameters. Type: LS ○ PartnerNo: Enter the logical system name created for the partner profile. Organization: Enter the purchase organization. ○ Tax type: Enter the tax type. Assign the partner to a company code. Ensure that you have the following values: ○ Partn. Go to SPRO > MM > Logistic Invoice Verification > EDI > Enter Program Parameters. Type: LS ○ PartnerNo: Enter the logical system name created for the partner profile. Purchase Organization and Vendor. Click Execute. ○ Purchasing Doc. Click Purchasing Output Determination: Doc. ○ Ctr: Enter a value. 2.Type (LPA or LP) used while creating the scheduling agreement release. ○ City: Enter the city. Maintain the following values:Purchasing Doc. ○ Comp. 12.Type: LPA ○ Purch. Ensure that you have the following values: ○ Partn.Type/Purch. Ariba Network Adapter for SAP NetWeaver Setup Guide 278 © 2015 SAP SE or an SAP affiliate company. 3. Configuring the Partner Profile for Invoices Context Configure to maintain the SAP ERP partner profile at a logical system level for invoices. ○ Vendor: Enter the vendor details. ○ Tax rate: Enter the tax rate. A new window appear.Org/Vendor and then click Enter. Go to SPRO > MM > Logistic Invoice Verification > EDI > Assign company code.Org/VendorDoc. All rights reserved. Type: LS ○ PartnerNo: Enter the logical system name created for the partner profile. maintain the condition record for message type NEUS and select Purchasing Output Determination: Document Type. create an entry as follows: ○ Medium ./ARBA/ENTRYSHEET_UPDATE ○ FORM routine .Creating an Output Type for the Entry Sheet Application Procedure 1. Choose Purchasing Output Determination: Purch. In the Processing routines section. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company.VN ○ Description . 2. and Time (4). Note If you also want to generate a printout./Vendor for EDI in the pop-up window and click the check button to enter. Save the entry. 279 . create an entry as follows: ○ Transmission Medium . 2. Org. Click save. in the screen enter output type NEUS and click Key combination. partner function (VN). Verify the values for vendor number. 3. Maintaining Condition Records for Outbound Transactions: POs Procedure 1.SEND_ENTRYSHEET_RESPONSE ○ Save the entry. Medium (6). 4. Start transaction NACE. 4. Using Tcode MN04 or NACE or NACR. Select application ES Entry Sheet and click Output types. In the Partner Functions section. 3. Partner number. Save the condition record.Vendor 5. All rights reserved.8 (Special Function) ○ Function .8 (Special Function) ○ Program . 5. Save the entry. Making Additional Change PO Configurations Procedure 1. You must also configure the company code. 4. maintain the variant for report RFFOEDI1. 3. Add new entries for condition type NEUS for Change Purchase Order with operation as 2.NB (for example) ○ Partner Function . Making Additional Invoice Configurations Configure tax types and tax codes using transaction code OBCD. Navigate to Tcode SPRO. and payment method to generate IDoc for EDI. 3. Maintaining Variants for Remittance For generating IDocs from F110. see the sample data mapping for InvoiceDetailRequest. Click the relevant output type. house bank. and in the SAP reference IMG navigate to Material Management Purchasing Messages Output control Messages Types Define Messages type for purchase order Fine – Tune control: Purchase order . In the main screen when you start the transaction NACE.Maintaining Condition Records for Outbound Transactions: Service Sheets Procedure 1.4 (when the application is saved) 6. select application ES Entry Sheet and click Condition records. For more information. Ariba Network Adapter for SAP NetWeaver Setup Guide 280 © 2015 SAP SE or an SAP affiliate company.1000 (for example) ○ Medium .8 (Special Function) ○ Date/Time . 2. Select Purchasing Output Determination: Document Type option. 2.VN ○ Partner Number . Configuring Your SAP ERP System . All rights reserved. Save the entry. Click on Condition records. Click the Execute button and maintain the following parameters by creating a new entry: ○ Document Type . . the invoice is created and stored through the IDOC. 281 . Type field. use this configuration path: ● SPRO > MM > Logistic Invoice Verification > EDI > Assign company code To assign program parameters.To assign the partner to a company code. Func­ Object Type Direc­ Type Type sion Type Code tion tion IDOC_INPUT_IN F INVO / INVOIC MM BUS208 2 VOIC_MRM IC02 ARB 1 A/ INV OIC E Navigate to transaction code WE82 and add the following entry: Message Type Basic Type Extension Release INVOIC INVOIC02 /ARBA/INVOICE 40A Configuring Invoices From Ariba Network When an ERP system receives invoices from Ariba Network. use this configuration path: ● SPRO > MM > Logistic Invoice Verification > Incoming Invoice > Activate Direct Posting to G/L Accounts and Material Accounts ● Set both parameters to “active” To configure how unplanned delivery costs are posted. use this configuration path: ● SPRO > MM > Logistic Invoice Verification > EDI > Enter Program Parameters To configure direct posting to general ledger accounts and material accounts. ensure that you have the following configuration: ● Go to TCode OBCE. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. To create and store invoices successfully in the IDOC. and edit the entry as follows: Function Module Function Basic Exten­ Message Message Msg. ● Create an entry at the vendor or logical system level in the Partn. use this configuration path: ● SPRO > MM > Logistic Invoice Verification > Incoming Invoice > Configure How Unplanned Delivery Costs are Posted ● Set the value for the Distribute among invoice items parameter to blank Maintaining IDOC Type Assignment to Function Module After you have imported SAP transports that contain objects related to the invoice transaction. perform the following activities: Navigate to transaction code WE57. All rights reserved. no document type is hard coded. Now.000%.pstg ky ○ G/L cr. for a particular tax code in the Self Assessment section for the tax type A/P Sales Tax 1 Use.pstng ky ○ Vend. if the tax rate is 60.pstng ky ○ Tax-ex. Ariba Network Adapter for SAP NetWeaver Setup Guide 282 © 2015 SAP SE or an SAP affiliate company. then the transaction key for this tax level is MW1 and the condition type is JP1U. ● Enter a value in the following fields in the Posting Details section: ○ G/L db. for a particular tax code. All rights reserved. it consists of a separate entry for accrual tax. In the ftxp transaction.memo doc. different tax levels are maintained using KTOSL (Transaction Key) and KSCHL (Condition Type) For example. Earlier document type RE was hard coded and as a result payment proposals were not getting pulled for document types other than RE.pstng ky ○ Vend. You must use /ARBA/PARAM_TAB table to store relevant document types that can be used in where condition of SELECT statements to retrieve required invoice documents. which contains the transaction key and the condition type.● Enter the partner number and company code. You must maintain these values in transaction SM30 by referring to the accrual condition settings for a particular tax code in the ftxp transaction. In addition to maintaining additional tax and accrual calculation configurations. When the function CALCULATE_TAX_FROM_GROSSAMOUNT returns the result table.type ○ Cred. In the case of multiple conditions for a single NAME you must change the value of FIELDNAME to form a composite key.deb. you can store values for other configuration parameters in the table /ARBA/PARAM_TAB.tax code ○ Invoice doc. You must maintain the following values in the /ARBA/PARAM_TAB table: NAME FIELDNAME SIGN OPTI LOW HIGH ACCRUAL_CONDITION_TYPE JP1U I EQ JP1U ACCRUAL_TRANSACTION_KEY MW1 I EQ MW1 ACCRUAL_TRANSACTION_KEY MW2 I EQ MW2 Note ● The values in this table are examples of a typical configuration and may vary depending on the SAP system configuration.type Making Additional Tax and Accrual Calculation Configurations Make the following configurations in the case of purchase order / non purchase order invoices having a tax code with full / partial accrual condition posted to different accounts. Configuring Your SAP ERP System . they are configurable using the field value pair in the custom table. ● These three parameters in the table are only used by the ERP CC INVOICE scheduled task.cred. As transaction key and condition type may vary from SAP system to system. and so I EQ 51. INVOICE_DOC_TYPE KR I EQ KR To store general document type for ERP-initiated invoices. and invoice status up­ date. and invoice status update. Note If you are using a Cloud Integration Release version earlier than Release 4. and so which are rejected. Status number of the Invoice IDOC US on. and invoice status update.71. 283 . INVOICE_DOC_OPTION I EQ XBLNR To send output invoice number as XBLNR for ERP-initiated invoices. To send the document reference number (XBLNR) as the output key field instead of BELNR. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. INVOICE_DOC_TYPE_FUL KZ I EQ KZ To store doc type required for full man­ L_MANUAL ual payment for invoice status update.0. if you do not main­ on. a new parameter is INVOICE_DOC_OPTION is added to /ARBA/PARAM_TAB because XBLNR is a non mandatory field. payment propos­ als. accounting document number (BELNR) was key field and was sent as the output invoice document number. You must set the INVOICE_DOC_OPTION to XBLNR to ensure that XBLNR is returned as the output invoice document number. earlier in the SAP system. INVOICE_DOC_TYPE_PAR KZ I EQ KZ TIAL INVOIC02_REJECT_STAT 51. The following table illustrates configuration parameters and their corresponding values: NAME FIELDNAME SIGN OPTI LOW HIGH DESCRIPTION ERPCC K~XBLNR I NE To filter XBLNR not having any value for ERP-initiated invoices. tain anything. 71.In addition. INVOICE_DOC_TYPE_PAR KA I EQ KA To store doc type required for partial TIAL payment for invoice status update. All rights reserved. then you must use the CHECK_XBLNR_EMPTY parameter. pay­ ment proposals. INVOICE_DOC_TYPE RE I EQ RE INVOICE_DOC_TYPE KA I EQ KA To store non-PO invoices created in the SAP ERP system and reversed or can­ celed using FB08(KA) and FI invoices (non-PO invoices)) INVOICE_DOC_TYPE_FUL ZP I EQ ZP To store doc type required for full auto­ L_AUTO matic payment for invoice status up­ date. the default value will be 51. payment propos­ als. du­ plicate entries for payment proposal and invoice status update are sent to Ariba Network if: ● An invoice is changed on 22.04. All rights reserved. If you do not maintain this parameter.04. NET_DISCOUNT_DAYS X I EQ X You need to maintain this parameter if you want to pay only on or after the due date without any discount. Vendor Text. Configuring Your SAP ERP System . Ariba Network Adapter for SAP NetWeaver Setup Guide 284 © 2015 SAP SE or an SAP affiliate company.NAME FIELDNAME SIGN OPTI LOW HIGH DESCRIPTION AVOID_DUPLICATE_ISU_ X I EQ X This ensures that duplicate entries for PP payment proposal and invoice status up­ date are not sent to Ariba Network. ● The PP and ISU for an invoice are already sent to Ariba Network and a user changes a field that does not affect the PP or ISU for example.2012 and the PP and ISU programs are run on the same date 22.2012 and the PP and ISU are sent to Ariba Network on 22. and runs the PP and ISU programs.2012.04. This ISU and PP will fail in Ariba Network because Invoice2 has not been sent to Ariba Network. if you had maintained 5 mi­ nutes as the value for this parameter. it will pick the ISU or PP for the invoice Invoice2 created at 10:20 A.M. and end beyond 10. To ensure that ISU and PP is not sent for an invoice that has not been sent to Ariba Network. you perform the following steps: Create an invoice Invoice1 at 10:05 A..M. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company.M. and ends at 10:15 A.M. 15. and ISU and PP is scheduled to start at 10:05 A. if current time (system time) is 10:20 A. the scheduled task does not pick the ISU or PP for the invoice Invoice2 created at 10:20 A. (Current time - 10:20 – 5 minutes).M. You must maintain the value of this pa­ (Text or Num­ so on rameter in minutes.M. then the end time for the ISU or PP changes to 10:15. NAME FIELDNAME SIGN OPTI LOW HIGH DESCRIPTION GRACE_TIME_ISU_PP Unique Value I EQ 5. As a result. Create an invoice Invoice2 at 10:20 A. Now.M.20 A.M. The number of mi­ ber) nutes you maintain for this parameter is subtracted from the current time (sys­ tem time) and that time becomes the end time for the ISU and PP scheduled tasks. All rights reserved. The input time for the ERPCC scheduled task is 10:00 A. 285 .10. you need to maintain a value for this parameter.M.M. For example. Assuming that the ERPCC scheduled task starts at 10:00 A. In the above example.M. the infor­ mation about the ERP-initiated in­ voices does not exist in the / ARBA_AN_ERPINV table and the ISU or PP scheduled task sends the Ariba Network Adapter for SAP NetWeaver Setup Guide 286 © 2015 SAP SE or an SAP affiliate company. ● If you have not enabled the ERP CC scheduled task and send ERP-initi­ ated invoices from your ERP sys­ tem. Configuring Your SAP ERP System . ERP CC scheduled task does not store information on the ERP-in­ itiated invoices in the / ARBA_AN_ERPINV table. The ISU and PP scheduled tasks proc­ esses invoices in the table / ARBA_AN_ERPINV as follows: ● If you have enabled the ERPCC scheduled task and send ERP-initi­ ated invoices from your ERP sys­ tem. you must provide the required value for this parameter. the scheduled tasks queries the / ARBA/AN_ERPINV table and sends the ISU and PP only for the invoices that are available in the table. To ensure that ISU and PP scheduled tasks can query the table. the ISU or PP scheduled task looks into the / ARBA_AN_ERPINV table to filter ERP-initiated invoices associated to the ISU or PP. When the InvoiceStatusUpdate (ISU) and Payment Proposal (PP) scheduled tasks run at their scheduled time. When you send an ISU or PP from your ERP system. All rights reserved. When you send an ISU or PP from your ERP system. In this case.NAME FIELDNAME SIGN OPTI LOW HIGH DESCRIPTION ERP_INV_PROCESSED_ST X I EQ X The invoices that you create in your SAP ATUS ERP system and send to Ariba Network are stored in the table /ARBA/ AN_ERPINV. ERPCC scheduled task stores information on the ERP-initiated in­ voices in the /ARBA/AN_ERPINV table. the ISU or PP scheduled task looks into the / ARBA/AN_ERPINV table and fil­ ters ERP-initiated invoices associ­ ated to the ISU or PP that are al­ ready sent to Ariba Network. Tax amount is not shown at the line item level. then the program does not return any records. However. you must maintain the value “ ” (blank) or do not maintain this parameter. All rights reserved. then the tax amount for each line item in BSET is retrieved and popu­ lated against each line item in the ERP- initiated invoice. If you maintain this parameter with the document types. then total tax for all line items is stored in the BSET table as a consolidated tax amount. If you maintain the value X for the this parameter. If you maintain single value for a parameter. you have not se­ lected the check box for the tax jurisdic­ tion procedure. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. the tax is also updated at the header level. you must specify a value for the FIELDNAME field for each new parameter value to ensure a unique record is formed. NAME FIELDNAME SIGN OPTI LOW HIGH DESCRIPTION Ariba Network-generated invoices associated to the ISU or PP to Ariba Network. In this case. The line item tax amount is added to the cor­ responding line item amount and the consolidated tax amount is added to the header level of the ERP-initiated invoice. the FIELDNAME field can be left blank. you have se­ lected the check box for the tax jurisdic­ tion procedure (see graphic below). 287 . In addition. Note In case INVOICE_DOC_OPTION is set to XBLNR and if XBLNR values for invoice documents are missing in the SAP system. then the ERP-initi­ ated invoice function module retrieves invoices for the document types main­ tained in INVOICE_DOC_TYPE table. TAX_AT_LINE X If in OBCO transaction. INVOICE_DOC_TYPE RE I EQ RE Stores doc types for the ERP-initiated in­ voice transaction. If in OBCO transaction. then the ERP-initiated invoice function module retrieves invoices for the speci­ fied document types. if you want to maintain multiple values for a parameter. If you do not main­ tain this parameter. then the tax is stored line-by-line in the BSET table. Making User Exit Enhancements to Support Shipping and Handling Charges /ARBA/Invoice is available as an extension of INVOIC02. These entries can be maintained in transaction FBZP. payment method. which is maintained for the payer company code for the payment method “E” and the remittance currency. Ariba Network Adapter for SAP NetWeaver Setup Guide 288 © 2015 SAP SE or an SAP affiliate company. The G/L Account for Cash Discount is derived using the Chart of account for the CoCd and the transaction key SKE. These entries can be maintained in transaction FBKP. and general ledger for the house bank to generate IDoc for Payment Remittance Advice. Note If entries are not maintained as mentioned in the preceding section. The G/L Account to be posted to is derived using the house bank.Maintaining Tax Jurisdiction Maintaining Bank Key for the House Bank for Payment Remittance Advice You must configure the bank key. Configuring Your SAP ERP System . All rights reserved. the IDoc post will fail as it will not be able to find the correct accounts to post to. lv_beznk TYPE mrm_rbkpv-beznk. * Shipping and Handling added as service lines on invoice needs to be * posted to G/L Directly. ls_e1edp02 TYPE e1edp02. MOVE-CORRESPONDING ls_/ARBA/ACCOUNT_DATA TO ls_cobl_mrm. * Derive the Default Tax Code and Tax Jurisdiction from the * configuration SELECT SINGLE mwskz_bnk txjcd_bnk FROM t169v INTO (e_rbkpv-mwskz_bnk. ls_e1edp04 TYPE e1edp04. 289 . To access the user exit. lv_beznk = ls_data_s01-summe.SUS-MM: Invoice with delivery costs * This is to post the Shipping and handling charges as unplanned * delivery cost at the header of the Invoice IF i_idoc_data-segnam = 'E1EDS01'. DATA: wa_edid4 TYPE edid4. lv_mwskz_bkn TYPE mwskz_mrm. Reading data from extension * segement IF i_idoc_data-segnam = '/ARBA/ACCOUNT_DATA'. ls_land1 TYPE land1. lv_wskto TYPE mrm_rbkpv-wskto. e_change = 'X'. To post to G/L account directly we need to * get this additional information regarding the accounting needs to * fetched in an extension segment. ls_sdata TYPE edi_sdata OCCURS 0. ls_data_s01 = i_idoc_data-sdata.To process the data sent in the IDoc. All rights reserved. DATA:ls_/ARBA/ACCOUNT_DATA TYPE /ARBA/ACCOUNT_DATA. and use the Enhancement name: MRMH0002 and Exit: EXIT_SAPLMRMH_014. IF ls_data_s01-sumid = '020'. e_rbkpv-beznk = lv_beznk. ENDIF. IF NOT ls_/ARBA/ACCOUNT_DATA IS INITIAL.ls_addrnum) FROM t001 Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. ls_txjcd TYPE txjcd. lv_mwskz TYPE edi5279_a. DATA: t_edid4 TYPE STANDARD TABLE OF edid4. ls_lifnr TYPE lifnr. * Determine Tax Jurisidction code * We need Tax Jurisidction code only for US so check the country from * the Company Code SELECT SINGLE land1 adrnr INTO (ls_land1. make the following changes in the User Exit provided by SAP. ENDIF. * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. navigate to the transaction SMOD. ls_data_k05 TYPE e1edk05. IF sy-subrc <> 0. ls_ebelen TYPE ebeln. ls_/ARBA/ACCOUNT_DATA = i_idoc_data-sdata. ENDIF. ls_cobl_mrm TYPE cobl_mrm. * Conversion exit for WBS Element CALL FUNCTION 'CONVERSION_EXIT_ABPSP_INPUT' EXPORTING input = ls_/ARBA/ACCOUNT_DATA-ps_psp_pnr IMPORTING output = ls_cobl_mrm-ps_psp_pnr EXCEPTIONS not_found = 1 OTHERS = 2. The following example code shows the changes made to the user exit: DATA: ls_data_s01 TYPE e1eds01. * SAP Note Note 800866 . ls_addrnum TYPE ad_addrnum. e_rbkpv-txjcd_bnk) WHERE bukrs = e_rbkpv-bukrs. * If taxcode is not sent we will derive using the values maintained in * OBCD. * If the country is US then get the Tax Jurisidction code * from Plant IF ls_land1 = 'US'. APPEND ls_cobl_mrm TO t_frseg-cobl_mrm. LOOP AT t_edid4 INTO wa_edid4. Configuring Your SAP ERP System . * Get the Po and fetch the payment term SELECT SINGLE zterm INTO e_rbkpv-zterm FROM ekko WHERE ebeln = ls_e1edp02-belnr. SELECT SINGLE sndprn INTO ls_lifnr FROM edidc WHERE docnum = i_idoc_data-docnum. ENDIF. To Avoid it retrieving the Payment term from * the PO line when present else get it from the Vendor data * Read the Reference data *SELECT sdata FROM edid4 INTO TABLE ls_sdata *WHERE docnum = i_idoc_data-docnum *AND segnam = 'E1EDP02' . ls_cobl_mrm-txjcd = ls_txjcd. due this * idoc posting fails. SELECT SINGLE txjcd INTO ls_cobl_mrm-txjcd FROM t001w WHERE werks = ls_/ARBA/ACCOUNT_DATA-werks. *READ TABLE t_edid4 INTO wa_edid4 INDEX 1. SELECT SINGLE mwskz INTO ls_cobl_mrm-mwskz FROM t076m WHERE parart = 'LI' AND konto = ls_lifnr AND mwart = ls_e1edp04-mwskz AND mwsatz = ls_e1edp04-msatz AND land1 = ls_land1. FREE: t_edid4. LOOP AT t_edid4 INTO wa_edid4. APPEND t_frseg. * SAP code try to get the PO number from the first line of t_frseg to * get payment term and hence determine the baseline date. WHERE bukrs = ls_/ARBA/ACCOUNT_DATA-bukrs. * If Tax Jurisidction code is not maintained at Plant level. ENDIF. FREE: t_edid4. * We are introducing additional lines before the PO lines in t_frseg. ENDIF. IF ls_e1edp02-qualf = '001'. ENDIF. ENDLOOP. *LOOP AT ls_sdata INTO ls_e1edp04. SELECT * FROM edid4 INTO TABLE t_edid4 WHERE docnum = i_idoc_data-docnum AND segnam = 'E1EDP04'. ENDIF. ENDLOOP. take it * from Company code level IF ls_cobl_mrm-txjcd IS INITIAL. *SELECT sdata FROM edid4 INTO TABLE ls_sdata *WHERE docnum = i_idoc_data-docnum *AND segnam = 'E1EDP04' . CLEAR ls_cobl_mrm-txjcd. SELECT * FROM edid4 INTO TABLE t_edid4 WHERE docnum = i_idoc_data-docnum AND segnam = 'E1EDP04'. SELECT SINGLE taxjurcode INTO ls_txjcd FROM adrc WHERE addrnumber = ls_addrnum. All rights reserved. ls_e1edp02 = wa_edid4-sdata. * if PO line is not present get the payment term from Vendor Master Ariba Network Adapter for SAP NetWeaver Setup Guide 290 © 2015 SAP SE or an SAP affiliate company. ls_e1edp04 = wa_edid4-sdata. IF ls_cobl_mrm-mwskz IS INITIAL. Ensure that the global company code value and the company code are same. e_change = 'X'. All rights reserved. *Passing IDOC Number IF i_idoc_data-segnam = 'E1EDK01'. e_change = 'X'. The following example code shows the changes made to the Exit EXIT_SAPLMRMH_015: *&-----------------------------------------------------------------* *& Include ZXM08U26 * *&-----------------------------------------------------------------* * move the data which needs to be posted directly to G/L account to * t_co structure and delete the same from t_frseg LOOP AT t_frseg. Assign this Global Company code to company code using transaction code OBB5. SELECT SINGLE sndprn INTO ls_lifnr FROM edidc WHERE docnum = i_idoc_data-docnum. e_rbkpv-sgtxt = i_idoc_data-docnum. Note The ABAP sample code in the two user exits EXIT_SAPLMRMH_014 and EXIT_SAPLMRMH_015 mentioned above expects the Shipping charges to be on a E1EDS01 020 segment of the invoice IDOC. Maintaining Global Company Code Maintain the global company code using transaction code OB72. e_change = 'X'. LOOP AT t_frseg-cobl_mrm INTO t_co. ENDIF. ENDLOOP. ENDLOOP. IF e_rbkpv-zterm IS INITIAL. IF NOT t_co[] IS INITIAL. e_change = 'X'. CLEAR t_frseg-cobl_mrm. DELETE t_frseg WHERE ebeln IS INITIAL AND ebelp IS INITIAL AND cobl_mrm IS NOT INITIAL. * Need to set the indicator auto tax calculation is not set. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. APPEND t_co. ENDIF. ENDIF. * Apply OSS Note 385756 e_rbkpv-xmwst = 'X'. SELECT SINGLE zterm INTO e_rbkpv-zterm FROM lfm1 WHERE lifnr = ls_lifnr. ENDIF. 291 . Configuring Your SAP ERP System . go to transaction SM30 and configure the /ARBA/REQPARAM table with the following: ● Order Type ● Purchase Requisition (optional when configuring for the first time) ● Date (optional when configuring for the first time) ● Time: (optional when configuring for the first time) Enable Proxy Configuration For more information.Configuration Related to Export of Requisitions from SAP ERP To ensure that the requisitions created in SAP ERP are exported to Ariba Network and in turn to Ariba procurement solutions. go to transaction SE38 and run or schedule the /ARBA/REQUISITION_EXPORT program. Ariba Network Adapter for SAP NetWeaver Setup Guide 292 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Business AddIns The following Business AddIns (BADIs) are available inside the programs that allow you to enhance the functionality as required. perform the following configuration activities: Configure /ARBA/REQPARAM Table In SAP ERP. Run/schedule the /ARBA/REQUISITION_EXPORT program In SAP ERP. see Proxy Settings in SAP ERP [page 294]. 0 and earlier. use this BADI to enhance the payment proposal transaction as required. This BADI is available only in Ariba Cloud Integration 4. Start transaction SE11. Implementing a BADI If you want to add a new field and send it to Ariba Network. 2. /ARBA/RECEIPT_UPDATE Available in the /ARBA/RECEIPT_PUBLISH program. To send this data to SAP NetWeaver PI. /ARBA/CHANGE_PO Available in the /ARBA/PO_GET_DETAIL function module. Use this BADI to en­ hance the receipt transaction as required. For Ariba Cloud Integration 6. Use this BADI to en­ hance the ERP-initiated invoice transaction as required. This BADI is available only in Ariba Cloud Integration 5. Start transaction SE19. After creating the implementation. Use this BADI to enhance the requisition transaction as required. /ARBA/INVOICE_UPDATE Available in the /ARBA/ERPINVOICE_EXPORT program.0. Change Purchase Orders are processed as part of the purchase order transaction. Starting Ariba Cloud Integration 5. The other two are available in the /ARBA/PO_SERVICE_INFO function module. 293 . write the required code inside the available methods. /ARBA/PP_UPDATE Available in the /ARBA/PAYPROPOSAL_EXPORT program. create an implementation for the definition /ARBA/PO_MODIFY.0 and earlier. For example. 3. /ARBA/PR_CHANGE Available in the /ARBA/REQUISITION_EXPORT program. Use this BADI to enhance the purchase order transaction as required. BADI Name Description /ARBA/PO_MODIFY Available in /ARBA/PO_ACCOUNTING_INFO and /ARBA/ PO_SERVICE_INFO function modules. /ARBA/ISU_UPDATE Available in the /ARBA/INVSTATUPDT_EXPORT program. All rights reserved. use the BADI /ARBA/BTE_INVSTATUPDT_EXPORT.0. Identify the structure in which you want to add a field. 1. you want to add a new field to the /ARBA/ EKPO structure. This BADI has the following methods: ● READ_PO_DATA ● SAVE_PO_DATA ● READ_SERVICE_PO_DATA ● SAVE_SERVICE_PO_DATA The first two methods are available in the /ARBA/ PO_ACCOUNTING_INFO function module. perform the following steps: 1. write the code inside the READ_PO_DATA method. Use this BADI to enhance the change PO transaction as required. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. To fetch data for the fields you added. use the SAVE_PO_DATA method to populate the output structures. open the structure and click Append Structure to create a new structure and add the required fields. Use this BADI to enhance the ISU transaction as required. 3. Expand Integration Engine -> Configuration.3 and above [page 294] Configuring Proxy Settings for Single Stack (Java only) Instances of SAP NetWeaver PI 7. 6. Save and activate the BADI. While configuring. enhance the custom mappings provided by Ariba. Start transaction SLDAPICUST. 5.system identifier) ○ SAPSLDAPI under TCP/IP Connections.3 and above Context If you are using SAP NetWeaver 7. ○ LCRSAPRFC under TCP/IP Connections.system identifier) under HTTP Connections to ABAP System. Enter SAP XI hostname. Start transaction SXMB_ADM. and password. To send this data to Ariba Network from SAP NetWeaver PI. then perform the below steps to configure proxy. Ariba Network Adapter for SAP NetWeaver Setup Guide 294 © 2015 SAP SE or an SAP affiliate company.2. Start Transaction SM59 and check if following configurations exist: ○ SAP_PROXY_ESR under HTTP Connections to External Server. where SID . Configuring Your SAP ERP System .1 or Dual Stack (ABAP and Java) Instances of SAP NetWeaver PI 7. Specify the program ID similar to the one created under Jco RFC destinations (SAPSLDAPI_<SID>.3 and above. port.1 or the dual stack (ABAP and Java) instance of SAP NetWeaver PI 7. 4.system identifier) 2. where SID . ○ XI_INTEGRATIONSERVER_<SID> (SID . Specify the program ID similar to the one created under Jco RFC destinations (LCRSAPRFC_<SID>. Click Integration Engine Configuration to edit global configuration data. XI user ID. Procedure 1. The below configuration is done in R/3 system. specify the RFC destination names accordingly. All rights reserved.3 and above [page 297] Configuring Proxy Settings for SAP NetWeaver 7. The RFC destination names vary from system to system.1 or Dual Stack (ABAP and Java) Instances of SAP NetWeaver PI 7. Proxy Settings in SAP ERP Related Information Configuring Proxy Settings for SAP NetWeaver 7. 3. 7. Under Global Configuration Data. 295 .dest://<XI_INTEGRATIONSERVER_PPI> (H Type RFC destination mentioned above) 9. Server .Runtime ○ Parameter . enter: ○ Role of Business System . Run SLDCHECK command in SAP R/3. Enter the following: ○ Category .IS_URL ○ Current Value . Click Specific Configuration. All rights reserved. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company.Application System ○ Corresponding Integ.dest://<XI_INTEGRATIONSERVER_PPI> (H Type RFC destination mentioned above) 8. All rights reserved. Configuring Your SAP ERP System .Results The PI server appears and displays the following: Ariba Network Adapter for SAP NetWeaver Setup Guide 296 © 2015 SAP SE or an SAP affiliate company. c. Enter SAP XI hostname. Under Global Configuration Data. c. and password. Configuring Proxy Settings for Single Stack (Java only) Instances of SAP NetWeaver PI 7. add AEX (PI Java Stack) server host name and port. 10. Under the Technical Settings tab. 9.3 and above Context If you are using the single stack (Java only) instance of SAP NetWeaver PI 7. XI user ID.Summary indicates that connection to XI is successful. In the Path Prefix field. Run SLDCHECK command in SAP R/3.3 or above. 297 . Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. Under the Logon & Security tab. enter: ○ Role of Business System . Create an HTTP destination to AEX of Type G (example: PI_AEX) as follows: a. 2. user must be assigned to role SAP_XI_REP_SERV_USER. In the Path Prefix field. 4. 8.Application System ○ Corresponding Integ.IS_URL ○ Current Value . b. 5. 6. b. Under the Technical Settings tab. Expand Integration Engine -> Configuration. then perform the following steps to configure proxy: Procedure 1. Click Specific Configuration and enter the following: ○ Category .dest://<PI_AEX> (G Type RFC destination mentioned above in step 2) Refer graphic in the dual stack configuration above. add AEX (PI Java Stack) server host name and port. 3. 7. enter /rep. Start transaction SLDAPICUST. Start Transaction SM59 and create RFC destination SAP_PROXY_ESR (Type G) under HTTP Connections to External Server. Click Integration Engine Configuration to edit global configuration data. user must be assigned to role SAP_XI_REP_SERV_USER. Start transaction SXMB_ADM.Runtime ○ Parameter . All rights reserved.dest://<PI_AEX> (G Type RFC destination mentioned above in step 2) Refer graphic in the dual stack configuration above. Server . Under the Logon & Security tab. enter /XISOAPAdapter/MessageServlet?ximessage=true. a. port. This user is assigned to the RFC communication channel in SAP NetWeaver PI. it must be assigned to a role in PFCG transaction code. All rights reserved. You must create the authorization object with the following details: ● Object name .com and search for content item 144118. However. RFC_NAME . then you can create the authorization object under that class. while assigning the authorization object to the role. an authorization object needs to be created in SAP ERP system and must be assigned to the RFC Communication Channel user. if you do not have an authorization object class specifically for Ariba. To access the documentation of RFCs. Note If you already have an authorization object class. Based on this information. then you need to define authorizations accordingly. log on to connect. RFC_TYPE . /ARBA/INVOICE_GET_DETAILS and other invoicing function modules must be assigned to users who are authorized to run the invoice transaction. In PFCG.Ariba Network Adapter Authorization Object. In your SAP ERP system. To define the required authorizations. However. select the check box FUGR for RFC_TYPE and for RFC_NAME./ARBA/RFC ● Description . invoice status update. Authorization Fields: 1. then first create an authorization object class /ARB before creating the authorization object. all SAP ERP users are authorized to execute all Ariba Network transactions. to meet your specific integration requirements. provide the names of the Ariba Network RFC function modules based on the user’s transaction level authorization. Defining Authorizations for Running Ariba Network Transactions By default.ariba. The documentation of RFCs provides details about the implementation of the RFCs for ERP-initiated invoice. Ariba Network Adapter for SAP NetWeaver Setup Guide 298 © 2015 SAP SE or an SAP affiliate company. Configuring Your SAP ERP System .Name of RFC to be protected Once the authorization object /ARBA/RFC is created.Type of RFC object to be protected 2. For example. ● Authorization Class – new /ARB or existing class. If the role exists for the RFC Communication Channel user.Documentation of RFCs Within the SAP NetWeaver Adapter During implementation. and payment proposal transactions. then assign the authorization object to the role directly or create a new role and profile and then assign the authorization object. you can enhance the RFCs provided by Ariba by adding customer exits and making changes to enhancement points. you can enhance your implementations by making changes as required. if you want that only selected users must be authorized to execute these transactions. create an authorization object by using transaction SU21. Therefore. and ERP-initiated invoice: Transaction Name ABAP Program Name ERP-Initiated Invoice /ARBA/ERPINVOICE_EXPORT Note This is available only for Ariba Cloud Integration Release 5. All rights reserved. ensure that you have maintained values for all the required parameters.0 and earlier. When a PO with advanced pricing details is exported from your SAP ERP system. 299 . these fields are added to the cXML and sent to Ariba Network. Payment Proposal /ARBA/PAYMENTPROPOSAL_EXPORT Receipt /ARBA/RECEIPT_PUBLISH Note To filter data. RFCs read the values that you maintain for the parameters in the /ARBA/PARAM_TAB. Unit Conversion Pricing allows unit of measure conversion in the pricing calculation. the user can specify advanced pricing details for a line item or multiple line items. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. Advanced pricing details includes: ● Quantity Based Pricing ● Unit Conversion Pricing Quantity based pricing allows the unit price of an item to be based on a different price unit quantity than 1. the following fields are added: ● PriceBasisQuantity ● PriceBasisQuantityUOM ● ConversionFactor ● PriceBasisQuantityDesc During transformation in SAP NetWeaver PI.payment proposal. in the IDOC. Advanced pricing details are also applicable for change purchase order and payments. when the unit of measure on the order differs from the pricing unit of measure. ABAP Programs for Outbound Transactions Implemented Using Proxies The following ABAP programs have been created by using the existing RFC code for the outbound transactions.Configuring Advanced Pricing Details While creating a PO in the SAP ERP system. receipt. Copy the following code and paste it into the top of the Include just below the comments. Click Repository Information System in the left panel. Click Display <-> Change to put the Include into change mode. 4. Procedure 1.. whereas these proxy programs will read date and time from a custom table /ARBA/PROXYPARAM that stores the start date and timestamp for three transactions. All rights reserved. Double-click the highlighted Include name in the Results list on the right panel. The receipt program now additionally: ● Pulls receipt document numbers from MKPF ● Filters documents to exclude the following: ○ Documents which are not of movement type 101 ○ Documents for vendors not stored in the table /ARBA/AN_VENDOR ● Fetches receipt data by using BAPI_GOODSMVT_GETDETAIL Configuring Implicit Enhancements for Comments in Order Confirmations Prerequisites The latest transport code must be installed in SAP ERP before creating this enhancement. which was earlier getting populated to RFC tables. 3. CALL METHOD /arba/cl_po_confirmation=>update_po_text Ariba Network Adapter for SAP NetWeaver Setup Guide 300 © 2015 SAP SE or an SAP affiliate company. 5. Log in to SAP ERP and navigate to transaction SE80. enter the access key information. You need to manually maintain the values in this table before the proxy programs are executed either manually or by the SAP Scheduler. 6. is populated to the proxy structures. If prompted for the developer access key. 2. 8. The data. 7. Double-click Includes. Select Program Library in the Object section of the left panel. This implicit enhancement allows you to process comments in order confirmations. 9. Enter ZXM06U02 in the Include name field. No change is made to the data processing logic. ERP-initiated invoice and PP and fiscal year and document number for the receipt transaction. The PI mappings then split the data into multiple cXML messages and send these cXML messages to Ariba Network through the cXML Adapter. Press F8 or click Execute. The proxy programs fetch data incrementally from the last date and time or document number (in case of receipts) maintained in the table and send that data to SAP NetWeaver PI in a batch. Configuring Your SAP ERP System .These above mentioned ABAP programs have been modified as follows: The existing RFC's take Start Date and Time as input parameters. 10. or parked invoices that have been deleted. the Invoice Status Update transaction does not change the status of the reversed invoices to "Reconciled" on the SAP system. The Business Transaction Events (BTE) has been created to process invoices created. 301 . Click Save. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. reconciled. canceled. reconciled. EXPORTING i_control = i_control is_ekko = order it_edidd = i_data[] CHANGING ct_status = i_status[]. All rights reserved. rejected. parked. invalid. Invoice Status Updates [page 301] Configuring the Invoice Status Update Transaction on your SAP ERP system [page 303] Invoice Status Updates Buyers using the Ariba Network Adapter for SAP NetWeaver can send and receive the statuses of invoices created on an SAP ERP system or Ariba Network when the status for invoices are updated on the SAP system. parked. reversed. parked. Buyers send StatusUpdateRequest documents to send status for invoices that are processing. or parked invoices that have been deleted on the SAP system. Buyers can send the following statuses for the parked invoices or the parked invoices that have been deleted to Ariba Network. paid. This is applicable only for customers using Cloud Integration Release version 3. paid. rejected.0 and earlier. or when payments are received on an SAP ERP system. and then click Activate to activate the changes. Configuring Invoice Status Updates Buyers can send Invoice Status Updates to Ariba Network to let suppliers know about the status of the invoice on the buyer's system. canceled. changed. Type Status Sent Comments Sent Parked invoices Processing Document Parked Parked invoices that have been deleted Rejected Document manually rejected/deleted Note When remittances have been reversed. parked invoices that have been deleted. The Invoice Status Update transaction processes invoices that are processed. paying. ● The BTE does not require the /ARBA/RFC authorization object. rejected. The BTE function module is activated when the invoices are created. All rights reserved. this authentication object is required when the /ARBA/BTE_INVSTATUPDT_EXPORT program runs the report containing the records to be sent to Ariba Network. Authorization Fields ● RFC_TYPE: Type of RFC object to be protected ● RFC_NAME: Name of RFC to be protected Ariba Network Adapter for SAP NetWeaver Setup Guide 302 © 2015 SAP SE or an SAP affiliate company.Requirements The Invoice Status Update transaction requires the same parameters that are applicable for the ISU batch program on your SAP system: Note The Invoice Status Update program (/ARBA/BTE_INVSTATUPDT_EXPORT) cannot be used along with the earlier version of the Invoice Status Update batch program (BTE_INVOICESTATUSUPDATE. parked. parked invoices that have been deleted. paid (partial or full payment). The following document types must be maintained in ARBA/PARAM_TAB: ● INVOICE_DOC_TYPE ● INVOICE_DOC_TYPE_FULL_AUTO ● INVOICE_DOC_TYPE_FULL_MANUAL ● INVOICE_DOC_TYPE_PARTIAL ● The Invoice Status Update transaction requires the same parameters that you set for the ISU batch program on your SAP system: ● The table /ARBA/AN_ISUINV stores information on the invoices are ready to be sent to Ariba Network. However. The authorization object contains the following details: ○ Object Name: /ARBA/RFC ○ Description: Ariba Network Adapter Authorization Object ○ Authorization Class: /ARB or existing class. reconciled. Buyers can only use one of the programs for invoice transactions. Configuring Your SAP ERP System . Limitations Ariba Network Adapter for SAP NetWeaver does not support processing of the MM and FI invoices that have been created on an SAP ERP system and have been parked. canceled. The Invoice Status Update transaction contains the following: ● A Business Transaction Events (BTE) has been associated to the 00005010 process module to send the statuses of invoices each time there is an update to invoices on the SAP ERP system. ● The function module /ARBA/BTE_INVOICESTATUSUPDATE processes invoices created or received on the SAP system. the Invoice Status Update transaction picks up invoices only for the document types maintained in /ARBA/PARAM_TAB. When the function module is run. CHANGE_PROCESS_BSAK Allows you to customize the existing structure details. ● If the INVOICE_DOC_OPTION parameter is maintained in /ARBA/PARAM_TAB. the Ariba Network Adapter for SAP NetWeaver picks up the invoices only when the ZLSPR – Payment Block Key field values have been changed: Note The ISU transaction does not use the GRACE_TIME_ISU_PP parameter. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. then Ariba Network Adapter for SAP NetWeaver sends the Reference Document number (XBLNR) as the invoiceID to Ariba Network. Ariba Network Adapter for SAP NetWeaver sends all corresponding documents (payment proposal. ● The Business AddIn (BADI) /ARBA/BTE_ISU_UPDATE is available in the BTE. the Ariba Network Adapter for SAP NetWeaver stores the invoices that are sent to Ariba Network in the /ARBA/AN_ERPINV table. remittances) associated to the cancelled MM invoice to Ariba Network. CHANGE_REJECTED Allows you to modify the rejected invoices. If you do not maintain this parameter. CHANGE_ISU_STATUS Allows you to modify the status updates for invoices.” Users must ensure that they clear the F1 documents using F-44. ● If you maintain the ERP_INV_PROCESSED_STATUS parameter. CHECK_CHANGED Allows you to modify the flag for check changes. SAP notifies users when an invoice is cancelled through the MR8M message. then the Ariba Network Adapter for SAP NetWeaver sends the invoice document number as the invoiceID to Ariba Network. the “Cancelled status is set based on the MM invoices. 303 . The following are the available methods: BADI Method Description CHANGE_PROCESS_BSIK Allows you to customize the existing structure details. “Please manually clear F1 document. CHANGE_PARTIALPAID Allows you to modify the details for partially paid invoices. Configuring the Invoice Status Update Transaction on your SAP ERP system Context Ensure that you import the necessary SAP transport requests into your SAP ERP system. CHANGE_INSERTTABLE Allows you to modify the inserted details in the invoice status update table. Note For a PO-based invoice. If the F1 documents remain. CHANGE_PARKED Allows you to modify the parked invoices. All rights reserved. ● If you maintain the AVOID_DUPLICATE_ISU_PP parameter and the BTE is triggered. of a customer. The Process Module 00005010.. Click the Active check box to select it. Save the changes. Ariba Network Adapter for SAP NetWeaver Setup Guide 304 © 2015 SAP SE or an SAP affiliate company. Configuring Your SAP ERP System .. 9. 8. Enter a new product name and description.. /ARBA/BTE_INVSTATUPDT_EXPORT.Procedure 1. 5. specify the newly created function module. see Importing the Design Package [page 313]. For example. 3.of a customer.. Go to the Transaction code FIBF. Go to the Transaction code FIBF. Go back to the previous page and click the Settings menu. 10. Click Execute. 2. click Products and then click . appears on the Business Transaction Events: Process Interface page. click Infosystem(Processes). All rights reserved. The function module product name must start with /ARBA/. On the Environment menu. 4. Specify the product ‘/ARBA/IS’. The function module must start with /ARBA/. For more information. 6. For the process module 00005010. 7. Configuring Order Inquiries This section contains the following topics: ● Configuring SAP IDOC for Order Inquiries [page 304] ● Configuring the Partner Profile [page 305] ● Maintaining Condition Records for Inquiries [page 307] ● Implementing a Custom Exit for the Order Inquiries Function Module [page 308] ● Support for Additional cXML Fields [page 308] Configuring SAP IDOC for Order Inquiries Context The following SAP IDOC configuration is required for using the sample data mapping: Transaction IDOC Basic Type Message Type OrderStatusRequest ORDERS05 ORDERS Configuring the IDOC transaction to support inquiries for purchase orders on your SAP ERP system involves the following steps: ● Installing the transports for the purchase order and change purchase order transaction. On the Settings menu. click Process Modules and then click . see Configuring the Partner Profile [page 271]. click the Add button and enter the following entries: ○ Partner Function: VN ○ Receiver Port: Configure the SAP PI system that sends the inquiries. 3. 2. see Configuring SAP IDOC for Order Inquiries [page 304]. 5. Client. ● Configuring the IDOC. 305 . see Configuring SAP IDOC for Order Inquiries [page 304]. System Number. Procedure 1. 5. ● Configuring the partner profile. Use Transaction SM59 to create an RFC destination of type ERP. Getaway host. 4. Expand the Partner type LI (Vendor) and choose the vendor that you want to configure the partner profile. ○ Partner Number: Corresponding Partner Number ○ Partner Type: LI ○ Partner Role: VN ○ Message Type: ORDERS ○ Receiver Port: Enter the SAP PI Receiver Port ○ Basic Type: ORDERS05 ○ Extension: /ARBA/ORDENQ ○ Message Type: ORDERS ○ Message Variant: OER ○ Message Function: OER 4. 2. Click the Add button in the table control. Click the Message Control tab. For more information. 3. Getaway service on the Technical Settings tab. Password on the Logon/Security tab. Choose Transactional RFC and click Create. and then save your entries. Enter the Language. Configuring the Partner Profile Procedure 1. For more information. Enter the Target host. 6. Use Transaction WE21 to create a port. Enter port. Enter the following values: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. All rights reserved. In the Outbound parameters table. User. description and RFC destination details. Use transaction WE20 to create a partner profile for a vendor. For more information on the IDOC. and then save your entries. click New Entries and enter the following values: Ariba Network Adapter for SAP NetWeaver Setup Guide 306 © 2015 SAP SE or an SAP affiliate company. Use the transaction WE57 to assign the function module to the logical message and IDOC Type. Use the transaction WE82 to assign the function module to the logical message and IDOC Type. Save your entries. Select Trigger immediately as the value for the Processing by Function Module parameter. All rights reserved.Application Message Type Process Code Change Indicator EF MAHN ME10 Blank EF MAHN ME10 x EF AUFB ME10 Blank EF AUFB ME10 x 7. Configuring Your SAP ERP System . if you want real time processing. 8. click New Entries and enter the following values: Parameter Value Function Module Name IDOC_OUTPUT_ORDERS Function Type FUNCTION MODULE Basic Type ORDERS05 Enhancement /ARBA/ORDENQ Message Type ORDERS Message Code OER Object Type BUS2012 Direction 1 10. To do this. 9. To do this. Click the Default Values tab and preserve the following values in the tab: ○ Despatch time: Send immediately ○ Transaction Medium: EDI ○ Partner function: VN 5.4 (when the application is saved) 11. Double click the output type: MAHN (Dunning) B. If you select the AUFB output type. 6. 7. Click EF as the application type and then click relevant output type. Click the General Data tab and select the Multiple issuing check box. select application <EF and click Condition records. 3. 2. You must perform this action. A new screen appears. Save the entries and go back to the main screen. 4. 8. A new screen appears. Save the entry. 9. All rights reserved. Preserve the values for the purchase organization and vendor. Double click the MAHN output type and click Purchasing Output Determination: Purch. 12.NB (for example) ○ Partner Function . In the main screen when you start the transaction NACE. 10.Org/Vendor for EDI.Results Parameter Value Message Type ORDERS Basic Type ORDERS05 Extension /ARBA/ORDENQ Maintaining Condition Records for Inquiries Procedure 1.VN ○ Partner Number . 307 . perform Step# 6 to 9.8 (Special Function) ○ Date/Time . Click EF as the application type and then click Condition records. Click the Execute button and maintain the following parameters for the vendor: ○ Document Type . Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company.1000 (for example) ○ Medium . Press Enter. Procedure 1. Create a new custom exit. All rights reserved. 5.Implementing a Custom Exit for the Order Inquiries Function Module Context The Function module /ARBA/ORDENQ_DETAILS is called from a custom exit MM06E001 . Click Enter. 6. This function module helps in picking up additional inquiry details. Go back and activate the user exit also. ZOR. Click Create. Support for Additional cXML Fields The standard IDOC /ARIBA/ORDENQ allows you to send additional information on inquiries to Ariba Network. 7. For example. You must execute the following steps to implement a custom exit. Copy and paste the following code: CALL FUNCTION '/ARBA/ORDENQ_DETAILS' EXPORTING xekko = xekko xlfa1 = xlfa1 xlfb1 = xlfb1 dobject = dobject TABLES int_edidd = int_edidd xekpo = xekpo xeket = xeket dekek_x = dekek_x dekeh = dekeh dsadr = dsadr dvbak = dvbak dvbap = dvbap dvbkd = dvbkd 8. Click the Activate button. 4. Go back and click the Components button and then double-click the enhancement name EXIT_SAPLEINM_002. Ariba Network Adapter for SAP NetWeaver Setup Guide 308 © 2015 SAP SE or an SAP affiliate company. 9. 2. Go to the CMOD transaction code.this is the user exit for EDI inbound and outbound purchasing documents. In the new screen that appears. double-click INCLUDE ZXM06U02 and click Enter. 3. Click the Enhancement Assignments button and then enter the user exit name “MM06E001”. Configuring Your SAP ERP System . ● Configuring the IDOC. For more information. ● /ARBA/ORDENQ_COMMENTS: Stores the comments sent in the OrderStatusRequestItem. see Scheduling Agreement Release Integration Scenario [page 153]. see Importing the Design Package [page 313]. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. Configuring the Partner Profile for Scheduling Agreement Releases [page 277]. The reminder level information is stored here. ● Configuring the partner profile. use the MM_Custom_ORDERS_ORDENQ_ARBA_2_CDF_FulFill_XSD mapping file. For more information see. For more information. ● ZARIBA_ORDENQ_DETAIL_EXT: Stores customized fields at the line item-level sent in the OrderStatusRequestItem. All rights reserved. 309 . ● ZARIBA_ORDENQ_HEADER_EXT: Stores customized fields at the header-level sent in the OrderStatusRequestHeader. Configuring Scheduling Agreement Releases This section contains the following topics: ● Configuring SAP IDOC for Scheduling Agreement Releases [page 310] ● Configuring the Partner Profile for Scheduling Agreement Releases [page 310] ● Maintaining Condition Records for Scheduling Agreement Releases [page 311] ● Implementing a Custom Exit for Scheduling Agreement Releases [page 311] ● Support for Additional cXML Fields [page 312] For more information on scheduling agreement releases. ● Mapping changes have been done in the IDOC to support the additional inquiry fields in the OrderStaturRequest cXML document: MM_ORDERS_ORDENQ_ARBA_2_CDF_FulFill_XSD To customize fields. You can also configure the partner profile at the logical system level. For more information. ● /ARBA/ORDENQDETAIL: Stores additional information on line items sent in the OrderStatusRequestItem.The following segments stores information on the following: ● /ARBA/ORDENQHEADER: Stores additional header-level details sent in the OrderStatusRequestHeader. Configuring the IDOC transaction for scheduling agreement releases on your SAP ERP system involves the following steps: ● Installing the transports for the scheduling agreement release transaction. see Configuring SAP IDOC for Scheduling Agreement Releases [page 310]. see Configuring the Partner Profile for Scheduling Agreement Releases [page 310]. On the message control tab. click the Add button and enter the following entries: ○ Receiver Port: Configure the SAP PI system that sends the scheduling agreement release.Configuring SAP IDOC for Scheduling Agreement Releases The following SAP IDOC configuration is required for using the sample data mapping: Transaction IDOC Basic Type Message Type ScheduleAgreementReleaseRequest DELFOR02 DELINS Configuring the Partner Profile for Scheduling Agreement Releases Procedure 1. ○ Partner Number: Corresponding Partner Number ○ Partner Type: LI ○ Partner Role: VN ○ Message Type: DELINS ○ Receiver Port: Enter the SAP PI Receiver Port ○ Basic Type: DELFOR02 ○ Extension: /ARBA/DELFOR02 4. Ariba Network Adapter for SAP NetWeaver Setup Guide 310 © 2015 SAP SE or an SAP affiliate company. Save your entries. Expand the Partner type LI (Vendor) and choose the vendor that you want to configure the partner profile. All rights reserved. enter the following: Application Message Type Process Code Change Indicator EL LPH1 ME14 Blank EL LPH1 ME14 x EL LPJ1 ME13 Blank EL LPJ1 ME13 x 5. 2. if you want real time processing. 3. In the Outbound parameters table. Configuring Your SAP ERP System . Select Trigger immediately as the value for the Processing by Function Module parameter. 6. Use transaction WE20 to create a partner profile for a vendor. Double click the LPH1 output type and click Purchasing Output Determination: Purch. Perform Step 6 to 9 with output type LPJ1 for the JIT Delivery Schedule. Preserve the values for the purchase organization and vendor.8 (Special Function) ○ Date/Time .4 (when the application is saved) 9. Press Enter. Implementing a Custom Exit for Scheduling Agreement Releases Context The Function module /ARBA/SARRELEASE is called from a custom exit MM06E001 .VN ○ Partner Number . select application EL Purch. All rights reserved.this is the user exits for EDI inbound and outbound purchasing documents. 3. You must execute the following steps to implement a custom exit. 10. 311 .Related Information Configuring the Partner Profile for Scheduling Agreement Releases [page 277] Maintaining Condition Records for Scheduling Agreement Releases Procedure 1. Save the entry. SchAgrReleaseEntry and click Condition records. Click on Condition records. 6. Double click the output type: LPH1 and LPJ1(Forecast and JIT) 4. This function module helps in picking up additional scheduling agreement release details.NB (for example) ○ Partner Function .1000 (for example) ○ Medium . 2.Org/Vendor for EDI. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. Click the Default Values tab and preserve the following values in the tab: ○ Despatch time: Send with Application own transaction ○ Transaction Medium: EDI ○ Partner function: VN 5. Click the Execute button and maintain the following parameters for the vendor: ○ Document Type . Click EL as the application type and then click relevant output type. 8. 7. In the main screen when you start the transaction NACE. 7. For example.MM06E001. Copy and paste the following code: CALL FUNCTION '/ARBA/SARELEASE' EXPORTING dekko = dekko dpekko = dpekko control_record_out = control_record_out dobject = dobject dlfa1 = dlfa1 dlfb1 = dlfb1 TABLES dekpo = dekpo dpekpo = dpekpo deket = deket dekek_x = dekek_x dekeh = dekeh desll = desll dint_edidd = dint_edidd. customize the following segment: ○ ‘ZARIBA_SARHEADER_EXT IDoc: Schedule Agreement Release Header Ariba Network Adapter for SAP NetWeaver Setup Guide 312 © 2015 SAP SE or an SAP affiliate company. double-click INCLUDE ZXM06U59 and click Enter. Go to the CMOD transaction code. Go back and click the Components button and then double-click the following enhancement names: ○ For Forecast Schedule: EXIT_SAPLEINM_019 ○ For JIT Schedule: EXIT_SAPLEINM_020 5. 4. 2. Support for Additional cXML Fields The existing IDOC DELINS. and material group) You can use the following customized IDOC segment to send any additional cXML fields: ● To send additional header fields to Ariba Network.Procedure 1. All rights reserved. Create a new custom exit. 8. 6. 3. You can use the following IDOC segments to support these additional cXML fields: ● To send additional header fields (vendor address and company code address details) to Ariba Network: ○ /ARBA/SARHEADER IDoc: Additional Header data ● To send additional line item details: ○ /ARBA/SARDETAIL IDoc: Additional item data ○ /ARBA/ACCOUNT IDoc: Accounting details (price unit. Click the Enhancement Assignments button and then enter the user exit name. Click Enter. Click Create. Configuring Your SAP ERP System . ZSAR. Click the Activate button. account category.DELFOR02 has been enhanced to send additional cXML fields for the Forecast Delivery Schedule or JIT Delivery Schedule information to Ariba Network. Go back and activate the user exit also. In the new screen that appears. customize the following segment: ○ ZARIBA_SARDETAIL_EXT IDoc: Schedule Agreement Release Item Configuring IDOC Metadata (Optional) This procedure allows you to preload the metadata of the IDOC documents exchanged by the IDOC adapter during configuration. If they are not. ● Configuring the partner profile. ● Configuring the IDOC. if you skip it. All rights reserved. click Metadata Create to add the same. For more information. Configuring Ship Notices Against Multiple Purchase Orders Configuring the IDOC transaction for ship notices against multiple purchase orders on your SAP ERP system involves the following steps: ● Installing the transports for the advanced ship notice transaction. 313 . ● To send item details. see Configuring SAP IDOC for Scheduling Agreement Releases [page 310]. seeImporting the Design Package [page 313]. Check and configure the IDOC Metadata parameters of the port to communicate with the SAP ERP system in SAP NetWeaver PI. Configuring the SAP IDOC for Ship Notices Against Multiple Purchase Orders Context The following SAP IDoc configuration is required for using the sample data mapping: Transaction IDoc Basic Type Message Type Ship Notice DELVRY06 DESADV Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. For more information. This is optional. is available. For more information. Check the IDOC Metadata in Metadata Overview for the IDOC Adapter to see if all the inbound IDOC DELFOR02. Refer to the transaction IDX2. see Configuring the Partner Profile or Ship Notices Against Multiple Purchase Orders [page 314]. the metadata information is downloaded and associated to the port the first time a given type of IDOC is exchanged. partner type (as LI) and appropriate Type. 2. 7. if you want real time processing and then click the Cancel Processing After Syntax Error check box. Enter port. click New Entries and enter the following values: Ariba Network Adapter for SAP NetWeaver Setup Guide 314 © 2015 SAP SE or an SAP affiliate company. 3. Configuring Your SAP ERP System . All rights reserved. 5. Save your entries. Configure Advance Ship Notice with the following inbound parameters: Parameter Value Partner function VN Message type DESADV Process Code DELS 8. User. 4. Use Transaction WE21 to create a port. Use Transaction SM59 to create an RFC destination of type ERP. and Process code. 10. 3. 6.Procedure 1. Use the transaction BD67 to assign the process code DELS to the function module IDOC_INPUT_DESADV1. Agent. Choose Transactional RFC and click Create. Use the transaction WE57 to assign the function module to the logical message and IDOC Type. Click Create inbound parameter (the green plus sign). 9. and Lang. Use transaction WE20 to create a partner profile for a vendor. Save your entries. and then save your entries. 5. To do this. Client. 2. System Number. Configuring the Partner Profile or Ship Notices Against Multiple Purchase Orders Procedure 1. Enter Partner Role. and then save your entries. Getaway service on the Technical Settings tab. Enter partner (vendor) number. Message type. Enter Target host. enter Language. description and RFC destination Configuring the SAP IDOC for Ship Notices Against Multiple Purchase Orders [page 313]details. Select Trigger immediately as the value for the Processing by Function Module parameter. Choose Partner type LI (Vendor) and click Create. Getaway host. Password on the Logon/Security tab. 4. All rights reserved. the metadata information will be downloaded and associated to the port. It is optional as. if you skip it. is available. 315 . If they are not. the first time a given type of IDoc is exchanged. click Metadata Create to add the same. Configuring Returns and Corrections in Receipts Configuring the receipt transaction to support returns and correction on your SAP ERP system involves the following steps: ● Installing the transports for the receipt transaction. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. For more information.Results Parameter Value Function module IDOC_INPUT_DESADV1 Function type Function Module Basic Type DELVRY06 Message Type DESADV Object Type BUS2015 Direction Inbound Description Delivery:Shipping notification Name Inbound delivery Configuring IDoc Metadata for Scheduling Agreement Releases (Optional) This procedure allows you to preload the metadata of the IDoc documents exchanged by the IDoc adapter during configuration. seeImporting the Design Package [page 313]. Check the IDoc Metadata in Metadata Overview for the IDoc Adapter to see if all the inbound IDOC DESADV06. Check and configure the IDoc Metadata parameters of the port to communicate with the SAP ERP system in SAP NetWeaver PI. Refer to the transaction IDX2. Configuring Your SAP ERP System . create the same variable and field name in an­ other row and increment the Number value to 2. For example. 161. but increment the Number value to 2. To create the 124 movement type. T AL GOODSRECEIP RETURN_MVT 1 EQ Can be left blank or you can specify the fol­ I lowing movement types: 122. 103. 104. see Receipt Integration Scenario for Corrections and Returns in Receipts [page 179]. For more information.● Configuring parameters in the ARBA/PARAM_TAB table. but increment the Number value to 2. create the same variable and field name in an­ other row and increment the Number value to 2. ● Maintaining condition records for returns and corrections in receipts. T To specify another movement type. see Maintaining Printer Default Values for Returns and Corrections in Receipts [page 318]. see Configuring Parameters in the ARBA/PARAM_TAB Table for Returns and Corrections in Receipts [page 316]. create another row con­ taining the same values. GOODSRECEIP RETURN_MVT_REVERSA 1 EQ Can be left blank or you can specify the 123 I movement type. you currently have the Selection Value as 101. For example. ● Maintaining default values for the printer. For more information. 124. create another row con­ taining the same values. To create the 103 movement type. see Maintaining Condition Records for Returns and Corrections in Receipts [page 317]. GOODSRECEIP RECEIPT_MVT_REVERS 1 EQ Can be left blank or you can specify the 102 I movement type. you currently have the Selection Value as 122. All rights reserved. T To specify another movement type. For more information. Configuring Parameters in the ARBA/PARAM_TAB Table for Returns and Corrections in Receipts Ensure that you maintain the following values for the parameters in the ARBA/PRAM_TAB table using Transaction code SM30: Variable Name Field Name Number INCL/ Option Selection Value EXCL GOODSRECEIP RECEIPT_MVT 1 EQ Can be left blank or you can specify the fol­ I lowing movement types: 101. For more information on sending and receiving corrections and returns in receipts. T L Ariba Network Adapter for SAP NetWeaver Setup Guide 316 © 2015 SAP SE or an SAP affiliate company. if you have selected 1 Individual Slip as the Print Version option in the Default Values tab. 8. Note ● You can leave the Selection Value field blank or specify a particular movement type. Double click Processing routines and enter the following values: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. only this particular movement type is considered while processing receipts containing returns and corrections. 7. ● If you enter a specific movement type in the Selection Value field. Double click the output type: WE03. Click ME as the application type and then select WE03 as the output type. choose one of the following values: ○ 1 Individual Slip ○ 2 Indiv. Maintaining Condition Records for Returns and Corrections in Receipts Procedure 1. In the main screen when you start the transaction NACE. A new screen appears. select application ME Inventory Management and click Condition records. Click ME Inventory Management as the application type and then click Condition records. 122. For example. Slip w Inspect Text ○ 3 Collective Slip ○ Partner function: Enter the partner number of the sender system. Note The Print Version option you select in the Default Values tab must match the value you select in the MIGO screen. the ERP system associates the 101. 317 . 3. Click the Default Values tab and preserve the following values in the tab: ○ Despatch time: 4 Send immediately (when saving the application) ○ Transmission Medium: 8 Special function ○ Partner function: LS 9. Click the Default Values tab and preserve the following values in the tab: ○ Trans. 6. and 123 movement types as the default values for fields maintained for the GoodReceipt variable. 2. 4. 5./Event Type: WE ○ In the Print Version. A new screen appears. you must select the same 1 Individual Slip in the MIGO screen. Double click the WE03 output type and click More Details. If you leave the value blank. All rights reserved. Save the entries and go back to the main screen. 102. Go to the Transaction code MIGO and MB01. For more information. ○ FORM routine: SEND_GOODSRECIPT_SAVED 10. Go to the Transaction code SU3. 11. For more information. All rights reserved. Maintaining Printer Default Values for Returns and Corrections in Receipts Procedure 1. ○ Program: /ARBA/RECEIPT_PUBLISH Note This program uses NACE configuration to publish the receipts in real-time.8 (Special Function) ○ Description . Press Enter.LS ○ Medium . For more information. 3. Configuring Quote Request and Quote Message Documents Configuring the IDOC transaction for the quote request and quote message on your SAP ERP system involves the following steps: ● Configuring your system for Quote Request documents. 2.X 5. ● Configuring the SAP NetWeaver PI. Save the entry. Configuring Your SAP ERP System . Save the entry. Click the Parameters tab and add the following entry for the user: ○ Parameter ID . seeConfiguring your System for Quote Request Documents [page 319].Logical system 12. Click the Execute button and maintain the following parameters for the partner function: ○ Function . see Configuring your System for Quote Message Documents [page 320]. click the pull-down arrow and select 3 Collective Slip for the printer. ● Configuring your system for Quote Message documents. Ariba Network Adapter for SAP NetWeaver Setup Guide 318 © 2015 SAP SE or an SAP affiliate company.NDR ○ Parameter Value . In the General tab. see Configuring SAP NetWeaver PI [page 321]. 4. For example. Go to the CMOD transaction code and create a new custom exit. supplier email. For example. In the new screen that appears. Go back and click the Components button and then double-click the following enhancement name “EXIT_SAPLEINM_002. 2. ZRFQ. For more information. 3. 6. see . New NetWeaver PI mapping contents transform the iDoc to a ‘Quote Request’ cXML message and the cXML message is sent to the Ariba Network. For more information. Copy and paste the following code: Sample Code CALL FUNCTION '/ARBA/RFQ_GET_DETAILS' EXPORTING ekko = xekko lfa1 = xlfa1 Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. All rights reserved.Configuring your System for Quote Request Documents The following configurations must be made to your system for Quote Request documents: ● Configure the IDoc Partner Profile. [page 319] ● Activate the Cutom Project. Activating the Custom Project Procedure 1. 4. [page 319] IDoc Partner Profile Configuration IDoc ORDERS05 has been extended as “/ARBA/RFQ” and includes attachment details and additional data required for mapping. and the change RFQ indicator. double-click “INCLUDE ZXM06U02” and click Enter. The following SAP IDoc configurations are required: ● IDoc Basic Type: ORDERS05 ● IDoc Extension Type: /ARBA/RFQ ● Message Type: REQOTE Activating the IDoc Extension To activate IDoc extension.” 5. enter the user exit name “MM06E001” and then click Enter. 319 . Click Create. Click the Enhancement Assignments button. see . you must create a custom project with Enhancement Assignment “MM06E001” and component “EXIT_SAPLEINM_002” and then activate the project. For example. Configuring Your SAP ERP System . Click the Activate button. The RFC does the following: ● Defaults missing information in the cXML. If not. RFC / ARIBA/QUOTE The RFC / ARIBA/QUOTE has been created.TCode . purchase organization. purchase group. Configuring your System for Quote Message Documents To create Quote Message documents. Ariba fetches the accounting information from the /ARBA/ PARAM_TAB table. which uses BAPI_PO_CREATE1 to create a purchase order for the awarded quote messages. ● To maintain this parameter . Ariba needs the following information: ● Company Code ● Purchase Organization ● Material Group Ariba fetches this information from the RFQ. object = dobject TABLES int_edidd = int_edidd 7.SM30 with table name “/ARBA/PARAM_TAB”. The table needs to be maintained as follows: Variable Name Field Name Number Include / Exclude Option Value QUOTE ACCTASSCAT 0 I EQ K QUOTE ASSET 0 I EQ 100 QUOTE COSTCENTER 0 I EQ 0000004120 QUOTE DOC_TYPE 0 I EQ NB QUOTE GL_ACCOUNT 0 I EQ 0000404000 QUOTE ONETIME_VEN­ 0 I EQ 0000003960 DOR QUOTE ORDER 0 I EQ 23122 QUOTE ORDER_TYPE 0 I EQ NB Ariba Network Adapter for SAP NetWeaver Setup Guide 320 © 2015 SAP SE or an SAP affiliate company. Ariba pulls account information from the requisition if the RFQ was created with reference to a requisition. Note The accounting logic does not apply if the RFQ has a material number. All rights reserved. 8. accounting information from the RFQ. Go back and activate the user exit also. company code. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. approvedVendorOnly. RFQ_ERP RFQ_XI RFQDummyVendor Indicates whether a vendor is an “Ariba Marketplace Ven­ dor”. Variable Name Field Name Number Include / Exclude Option Value QUOTE PLANT 0 I EQ 3000 QUOTE SUB_NUMBER 0 I EQ 44444 QUOTE WBS_ELEMENT 0 I EQ 3423 ● New NetWeaver PI mapping contents are developed to transform the ‘Quote Message’ cXML to /ARIBA/ QUOTE.invitatio­ nOnly. Configuring SAP NetWeaver PI The following SAP NetWeaver PI value mappings must be configured for Quote Request and Quote Message documents: Source Value Target Value Parameter Name Notes XI_Global XI IsMultiERPModeEnabled Indicates whether multi ERP is enabled or not. see Purchase Order [page 16]. LANG_ERP LANG_ISO ERP Language code Key value pair of ERP-ISO lan­ guage map. 321 . XI_Global XI DefaultLanguageCode Default language. public For more information about Quote Request and Quote Message documents. For more information on service purchase orders. RFQ_TYPE RFQ_ASN_TYPE ERP’s RFQ document type Key value parameter of ERP doc type with Ariba Network supported doc type . All rights reserved. Configuring Support for Line Level Hierarchies in Service Purchase Orders Ariba Network Adapter for SAP NetWeaver enables transmission of service purchase orders with service line- items in up to five levels of hierarchy (1 parent and 4 child levels) from SAP ERP to Ariba Network. see Integrating SAP ERP with the Ariba Spot Quote Solution [page 245]. Requirements To configure this feature a system administrator must do the following:: ● Reconfigure the SAP Partner Profile (WE20) to modify the configuration of service orders.0. ● The last service item in a hierarchy cannot be blank. change orders. All rights reserved. ● Hierarchies are not supported for Order Confirmations. they must be migrated to purchase order transactions instead. Configuring Implicit Enhancements for Change and Cancel Service Orders [page 323] Configuring Implicit Enhancements for New Service Orders [page 323] Ariba Network Adapter for SAP NetWeaver Setup Guide 322 © 2015 SAP SE or an SAP affiliate company. see Configuring Implicit Enhancements for New Service Orders [page 323]. Configuring Your SAP ERP System . Attempting to create a PO with a 5-level deep hierarchy when using EHP3 or lower generates an error message in PO Message tab. ● SAP ERP note 2020660 might require implementation if it is not already installed and errors are generated when changing or updating a PO. and Service Invoices. ● This feature requires SAP ERP 6. Ariba Network can display the full hierarchy for service lines. you must configure two implicit enhancement in SAP ERP. Service Sheets. Limitations The following limitations apply to the transmission of purchase orders with up to a 5-level deep hierarchy of service lines in Purchase Orders. and cancel service order with hierarchical information to the Ariba Network Adapter for SAP NetWeaver. For more information. change. Note You must remove previously existing change order configuration from your Ariba solutions. EHP 4 and greater. Backward Compatibility The hierarchical display of service line items necessitates changes in SAP ERP and the Ariba Network Adapter for SAP NetWeaver that affect how transmission of purchase orders. For more information see the SAP documentation. About Configuring Implicit Enhancements To enable SAP ERP to send correct new. ● Create an implicit enhancement for service order functionality in the SAP ERP system. and update orders are handled. These changes are not backward compatible with previous releases. If you also have change order transaction customizations and want to continue to use them. ● SAP ERP restrict a hierarchy to a maximum of 5 levels: each top-level service line-item can have up to four additional levels of nesting below the top-level item. Click Enhance in the application toolbar. navigate to transaction code SE38 .LEINMF0Q and click Display. Activate the enhancement and save it. and save the package to a transport request. Copy the following code: DATA: cl_PO_ChangeCancel TYPE REF TO /arba/cl_PO_ChangeCancel. 11. 10. 9. Enter a name and description for the enhancement and press Enter. CALL METHOD cl_PO_ChangeCancel->trigger_delete_po_idoc EXPORTING ebeln = h_ebeln CHANGING xdruvo = xdruvo. 8. Procedure 1. Configuring Implicit Enhancements for New Service Orders Context To enable SAP ERP to send new service order information to the Ariba Network Adapter for SAP NetWeaver. CREATE OBJECT cl_PO_ChangeCancel. Right-click the line and select Enhancement Implementation > Create. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. you must configure an implicit enhancement in SAP ERP. 3. Select SAPLEINM from the popup. In your SAP ERP system. 5. 4. press Enter. Click Edit > Enhancement Operations > Show Implicit Enhancement Options to display a line after the lesen-beleg form. 12. 7. 2. In the package popup.Configuring Implicit Enhancements for Change and Cancel Service Orders Context To enable SAP ERP to send the correct change and cancel order information to the Ariba Network Adapter for SAP NetWeaver. you must configure an implicit enhancement in SAP ERP. 6. All rights reserved. Paste the copied code into the Enhancement Implementation. 323 . Click Create Enhancement Implementation. specify your Z or Y package. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation. Double-click Perform. Configuring Your SAP ERP System . Click Code on the Enhancement popup to display Select or Create Enhancement ImplementationChoose Type of Enhancement. All rights reserved. Click Create Enhancement Implementation.IDOC_OUTPUT_ORDERS and click Display. cl_po_hierarchy TYPE REF TO /arba/cl_po_hierarchy. RETURN. Copy the following code: DATA: l_flag(5) TYPE c. 4. IF l_flag EQ c_true.Procedure 1. 12. 11. Choose Type ofEnter a name and description for the enhancement and press Enter. CALL METHOD cl_po_hierarchy->get_systemversion_ishierarchy EXPORTING ebeln = ekpo-ebeln et_edi_esll = edi_esll[] IMPORTING flag = l_flag CHANGING int_edidd = int_edidd[]. 10. ENDTRY. Click Enhance in the application toolbar. navigate to transaction code SE37 . 9. specify your Z or Y package. ls_idoc_status TYPE bdidocstat. 6. Click Edit > Enhancement Operations > Show Implicit Enhancement Options to display a line after the fill_srv_orders form. 8. In your SAP ERP system. and save the package to a transport request. 2. Ariba Network Adapter for SAP NetWeaver Setup Guide 324 © 2015 SAP SE or an SAP affiliate company. CATCH /arba/cx_appl_idoc INTO lx_appl_idoc. CALL METHOD cl_purchaseorder->fill_service_line_number EXPORTING packno = ekpo-packno IMPORTING et_edi_esll = edi_esll[]. MESSAGE e151(/arba/message) RAISING error_message_received. CREATE OBJECT cl_purchaseorder. ENDIF. CONSTANTS: c_true TYPE char4 VALUE 'true'. Right-click the line and select Enhancement Implementation > Create. lx_appl_idoc TYPE REF TO /arba/cx_appl_idoc. CREATE OBJECT cl_po_hierarchy. In the package popup. press Enter. CREATE OBJECT cl_po_hierarchy. Search for Perform fill_srv_orders. c_false(5) TYPE c VALUE 'false'. Select SAPLEINM from the popup. 5. cl_purchaseorder TYPE REF TO /arba/cl_purchaseorder. 3. TRY. 7. 14. Customers can implement the following methods for service sheets: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. Ariba Network Adapter for SAP NetWeaver does not process the taxes in the service sheets. ● Although the invoice for the service sheets contains taxes and other charges. 325 . Direct Invoicing of Purchase Order Service Items Buyers can directly invoice a purchase order having the service type items. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation. ● The PI adapter downloads these stored invoices with service type line items from Ariba Networkand sends them to the SAP ERP system. Copy the following code: IF l_flag EQ c_true. ● Ariba Network auto generates a service sheet for the invoice with service type line items. 17. ● The invoice is kept on hold as "Pending Approval" on Ariba Network until the auto-generated service sheet for the invoice containing service type line items is approved on the SAP ERP system. All rights reserved. see Implementing Customer Exits for Invoices with Service Type Line Items [page 326]. Right-click on the line just before the end of the fill_srv_orders form and select Enhancement Implementation > Create. Select the enhancement created and named in Step 10. 15. The invoice is added to the pending queue and can be downloaded. CALL METHOD cl_purchaseorder->create_parent_child_relation EXPORTING edi_esll = edi_esll[] CHANGING int_edidd = int_edidd[]. 16. 18. 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. The service sheet is then sent to the SAP ERP system. 13. Paste the copied code into the Enhancement Implementation. the approved status is sent to Ariba Network. The following customer exits support auto-generated service sheets for invoices containing service type line items: ○ EXIT_SAPLMRMH_011 ○ EXIT_SAPLMRMH_015 For more information on customer exits. ENDIF 19. Activate the enhancement and save it. Ariba Network Adapter for SAP NetWeaver processes invoices with service type line items created against purchase orders sent from Ariba Network as follows: ● Supplier create an invoice with service type line items against purchase orders. ● Once the service sheet is approved on the SAP ERP system. Activate the enhancement and save it. ○ Class /ARBA/CL_SES_INV_HIERARCHY contains the following methods: ○ MODIFY_IDOC_DATA – Use this method to modify the IDoc data container in the specific format. All rights reserved. 6. Create an SAP Enhancement project. Double-click EXIT_SAPLMRMH_011. Double-click INCLUDE . Ariba Network Adapter for SAP NetWeaver Setup Guide 326 © 2015 SAP SE or an SAP affiliate company. Configuring Service Sheets Buyers must configure their SAP ERP system to process service sheets created for purchase orders containing service type items. The program INCLUDE . Save the changes. 3. 7. Click Components. ○ Enter a description in the Short Text field. 2. Implementing Customer Exits for Invoices with Service Type Line Items [page 326] Specifying Time-Out Intervals for Processing Service Sheets [page 327] Implementing Enhancements for Service Sheets Created for New Purchase Orders [page 328] Implementing Enhancements for Service Sheets Created for Changed or Canceled Purchase Orders [page 330] Implementing Customer Exits for Invoices with Service Type Line Items Context Add customer exits to invoices with service type line items to make specific integration requirements. Procedure 1. Configuring Your SAP ERP System . Choose the package. Go to the transaction code CMOD. 8. If you already have an existing SAP project for enhancement MRMH0002. 5. 4. ZMRMH.ZXM08U22 appears. Click Enhancement assignments. ○ Click Create. The Create Object Directory Entry screen appears. Enter MRMH0002 in the Enhancement text box and then press Enter.ZXM08U22 in the Function Builder: Display EXIT_SAPLMRMH_011 page to create the program. 9. use the same project. ○ MODIFY_FRSEG – Use this method to modify FRSEG-WRBTR(Amount) in the invoice line item table. For example. The SAP Enhancements in Enhancement Project page <object name> appears. the SAP ERP system fails while processing multiple service sheets for the same purchase order service type item. Specify the time-out duration by adding the parameter to the /ARBA/PARAM_TAB table. Save the entries. This time-out duration ensures that no resources stay locked on the SAP ERP system. lo_badi->modify_frseg( CHANGING t_frseg = t_frseg[] t_co = t_co[] t_ma = t_ma[] e_rbkpv = e_rbkpv e_change = e_change ). 12. Click the Activate button to go back to the CMOD screen. CREATE OBJECT lo_badi. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. 327 . CREATE OBJECT lo_badi. 15. Enter the following code in the program INCLUDE-ZXM08U26: Source Code DATA: lo_badi TYPE REF TO /arba/cl_ses_inv_hierarchy. Ariba recommends that you specify a time-out duration. 11. Specifying Time-Out Intervals for Processing Service Sheets Context In some cases. Activate the customer exit in the CMOD screen. To prevent failures while processing multiple service sheets. Enter the following code in the program INCLUDE . lo_badi->modify_idoc_data( EXPORTING i_bukrs = i_bukrs i_lifnr = i_lifnr i_idoc_contrl = i_idoc_contrl IMPORTING e_bukrs = e_bukrs e_lifnr = e_lifnr e_change = e_change CHANGING t_idoc_data = t_idoc_data[] ).ZXM08U22: Source Code DATA: lo_badi TYPE REF TO /arba/cl_ses_inv_hierarchy. 13. All rights reserved. Repeat Steps 7 to 10 to create the customer exit for EXIT_SAPLMRMH_015. 14. 10. Go to the /ARBA/PARAM_TAB table. Enter the program name. IDOC_OUTPUT_ORDERS and click Display. Go to transaction SE37. Maintain the following values in the /ARBA/PARAM_TAB table: ○ Variable Name : /ARBA/ENTRYSHEET_CREATE ○ Field Name : TIMEOUT ○ Number : 0 ○ INCL/EXCL : I ○ Option : EQ ○ Selection Value: 100 Note This value depends on the time-out value required by the customer. 8. you must implement the following enhancement. All rights reserved. 9. Perform. The Function Builder: Display IDOC_OUTPUT_ORDERS page appears. 4. Go to Function Perform fill_srv_orders. 3. The ABAP Editor:Display Include LEINMF0Q page appears. Implementing Enhancements for Service Sheets Created for New Purchase Orders Context To send statuses for service sheets created against new purchase orders to Ariba Network. Procedure 1. Right-click on the line below the text FORM fill_srv_orders:. 7. Click Code on the Choose Enhancement Mode page. 2. On the Edit menu. 2. click Enhancement Implementation and then click Create. Go to Transaction SM30. Configuring Your SAP ERP System . 5. 6. Ariba Network Adapter for SAP NetWeaver Setup Guide 328 © 2015 SAP SE or an SAP affiliate company. The Select or Create Enhancement Implementation page appears. Select the SAPLEINM program in the Choose Main Program for LEINMF0Q page and click Choose. Click the Enhance button on the application toolbar. click Enhancement Operations and then click Show Implicit Enhancement Options.Procedure 1. Double-click the function. 3. The Package page appears. CONSTANTS: c_true TYPE char4 VALUE 'true'. RETURN. CATCH /arba/cx_appl_idoc INTO lx_appl_idoc. All rights reserved. ENDIF. Press Enter. MESSAGE e151(/arba/message) RAISING error_message_received. Specify the Z or Y package and press Enter to save it to a transport request. 329 . 10. 17. 14. CREATE OBJECT cl_po_hierarchy. cl_po_hierarchy TYPE REF TO /arba/cl_po_hierarchy. ENDTRY. 12. Copy and paste the following code in the Enhancement Implementation for the Class for the create purchase order interface: Source Code DATA: l_flag(5) TYPE c. CREATE OBJECT cl_po_hierarchy. The Create Enhancement Implementation page appears. 16. you can use the same custom enhancement. zcanceled_po. ls_idoc_status TYPE bdidocstat. CALL METHOD cl_purchaseorder->fill_service_line_number EXPORTING packno = ekpo-packno IMPORTING et_edi_esll = edi_esll[]. cl_purchaseorder TYPE REF TO /arba/cl_purchaseorder. click Enhancement Implementation and then click Create. TRY. c_false(5) TYPE c VALUE 'false'. For example. Click Code on the Choose Enhancement Mode page. lx_appl_idoc TYPE REF TO /arba/cx_appl_idoc. CALL METHOD CL_PURCHASEORDER->CREATE_PARENT_CHILD_RELATION Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. CREATE OBJECT cl_purchaseorder. 18. 13. 11. Copy and paste the following code in the Enhancement Implementation for the Class for the create purchase order interface: Source Code if l_flag EQ c_true. 15. Right-click on the line below the text FORM fill_srv_orders:. CALL METHOD cl_po_hierarchy->get_systemversion_ishierarchy EXPORTING ebeln = ekpo-ebeln et_edi_esll = edi_esll[] IMPORTING flag = l_flag CHANGING int_edidd = int_edidd[]. The Select or Create Enhancement Implementation page appears. Click the Create enhancement implementation button. IF l_flag EQ c_true. Enter a name and description. If you already have a custom enhancement. Or you can create a new enhancement implementation. Select the already created enhancement implementation that you created in Step 13. EXPORTING EDI_ESLL = edi_esll[] CHANGING INT_EDIDD = int_edidd[] . Configuring Your SAP ERP System . CREATE OBJECT cl_PO_ChangeCancel. Copy and paste the following code in the Enhancement Implementation for the Class for the Change or Cancel interface: Source Code DATA: cl_PO_ChangeCancel TYPE REF TO /arba/cl_PO_ChangeCancel. If you already have a custom enhancement. CALL METHOD cl_PO_ChangeCancel->trigger_delete_po_idoc EXPORTING ebeln = h_ebeln Ariba Network Adapter for SAP NetWeaver Setup Guide 330 © 2015 SAP SE or an SAP affiliate company. The Create Enhancement Implementation page appears. Specify the Z or Y package and press Enter to save it to a transport request. 5. 10. Or you can create a new enhancement implementation. zcanceled_po. Click Code on the Choose Enhancement Mode page. Implementing Enhancements for Service Sheets Created for Changed or Canceled Purchase Orders Context To send statuses for service sheets created against purchase orders that have been changed or canceled to Ariba Network. Enter the program name. 7. Go to transaction SE38. Select the SAPLEINM program in the Choose Main Program for LEINMF0Q page and click Choose. LEINMF0Q and click Display. 11. The Select or Create Enhancement Implementation page appears. 2. you can use the same custom enhancement. Procedure 1. Enter a name and description. On the Edit menu. Press Enter. 19. Click the Enhance button on the application toolbar. Activate the code. you must implement the following enhancement. All rights reserved. 12. click Enhancement Operations and then click Show Implicit Enhancement Options. click Enhancement Implementation and then click Create. 8. 6. Click the Create enhancement implementation button. The Package page appears. 9. The ABAP Editor:Display Include LEINMF0Q page appears. 3. 4. Right-click on the line below the text FORM lesen_beleg:. For example. endif. 13. Note You must maintain the tax code for MM invoices in the /ARBA/TAXCAT_MAP table to process the tax values in the invoices correctly. 331 . Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. Activate the code. CHANGING xdruvo = xdruvo. The tax code in the invoice that is sent to Ariba Network is blank Configuring the NACE Setting to Send ERS Invoices [page 331] Configuring the NACE Setting to Send Invoicing Plans [page 333] Configuring the NACE Setting to Send MIRO Invoices [page 334] Implementing the Customer Exit for MM Invoices [page 335] Implementing Routines to Prevent Creation of Duplicate MM IDOCs [page 336] Maintaining Partner Profiles [page 337] Configuring the FI Invoices [page 338] Setting Document Type Filters for FI Invoices [page 339] Maintaining Output Types for FI Invoices [page 340] Implementing the Customer Exit for FI Invoices [page 341] Handling Errors [page 342] Related Information ERP-Initiated Invoices Using the IDOC Transmission Method [page 23] Configuring the NACE Setting to Send ERS Invoices Context Configure the NACE setting to send the ERS (Evaluated Receipt Settlement) invoices using the IDOC. All rights reserved. Ariba Network Adapter for SAP NetWeaver does not process the tax code in the MM invoices. Configuring ERP-Initiated Invoices to Use the IDOC Configure your ERP system to can use the GSVERF03 IDOC to send MM invoices and the FIDCCP02 IDOC to send FI invoices. If the tax code does not exist in the /ARBA/TAXCAT_MAP table. 12. In the Partner profiles:Outbound parameters screen. 1000. ○ Partn. Select INS Output type for Invoice Plan and then click Processing routines. ○ Transfer IDoc Immed. ○ Medium: 6 ○ Date/Time: 4 11.: Select the radio button. ○ Basic type: GSVERF03 ○ Extension: /ARBA/ GSVERF03 ○ Cancel Processing After Syntax Error: Select the check box.: For example. ensure that you maintain the following entries: ○ Receiver port: Enter the name of the receiver port. Double-click to expand partner type LI node and then click the vendor. Vendor 1000. 1000 . Go to transaction code WE20 to maintain the partner profiles. ○ Name: Name of the vendor ○ Funct: VN ○ Partner: Vendor number. These values are also applicable for the Invoice Plan output type.: For example. 10. Select application MR and then click Output types. Ariba Network Adapter for SAP NetWeaver Setup Guide 332 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Add the EDI entry with the following values: ○ Medium: EDI ○ Program: RSNASTED ○ FORM routine: EDI_PROCESSING 6. 2. Click Partner functions link and add the following EDI entries: ○ Medium: EDI ○ Funct: VN ○ Name: Vendor 7. 3. Select ERS Output type for ERS invoices and then click Processing routines. 3000. 4. For example. 8. For example. Enter the following values in the Change Condition Records (ERS Procedure): Fast Change screen: ○ Vendor: For example. In the Partner Profiles screen. maintain the following values: ○ Partner No. Type: LI ○ Partner Role: VN ○ Message Type: GSVERF In the Outbound Options tab. Click Execute.Procedure 1. Go back to the NACE transaction and click Condition records. Vendor to maintain condition records. 13. maintain the following values: ○ Partner No. 14. Start transaction NACE. Double-click ERS output type and click CoCode. Maintain the partner profile for the vendor. 9. Vendor 1000. Configuring Your SAP ERP System . 5. 333 . ○ Partn. maintain the following values: ○ Partner Role: VN ○ Message Type: GSVERF 15. : 0 ○ Agent: 50010120 ○ Lang. Add the EDI entry with the following values: ○ Medium: EDI ○ Program: RSNASTED ○ FORM routine: EDI_PROCESSING 6. Select INS Output type for Invoice Plan and then click Processing routines. All rights reserved. section. Configuring the NACE Setting to Send Invoicing Plans Context Configure the NACE setting to send the Invoicing plans using the IDOC. Click Partner functions link and add the following EDI entries: ○ Medium: EDI ○ Funct: VN Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. 3. Procedure 1. Type: LI In the Post processing permitted agent tab. 4. Go to Message Control tab and maintain the following values: ○ Application: MR : Invoice Verification ○ Message Type: ERS : ERS Procedure ○ Process code: MRRL: ERS procedure for Logistics invoice verification Results This completes the configuration for the ERS invoices. maintain the following values: ○ Ty. Select ERS Output type for ERS invoice and then click Processing routines. 5. 2.: EN In the Outbound parmtrs. Start transaction NACE. Select application MR and then click Output types. Go back to the NACE transaction and click Condition records. 1000. Double-click to expand partner type LI node and then click the vendor. Maintain the partner profile for the vendor . ○ Funct: VN ○ Partner: 0000001000 ○ Medium: 6 ○ Date/Time: 4 12. All rights reserved. 9. 10. section. ○ Pack. 8. Go to transaction code WE20 to maintain the partner profiles. Click Execute. Enter the company code and invoicing party. For example. Pty: For example. 13. 11. Click Save. 14. Double-click INS output type and click Company Code/Invoicing to maintain condition records. ○ Basic type: GSVERF03 ○ Extension: /ARBA/ GSVERF03 ○ Cancel Processing After Syntax Error: Select the check box. Click Execute. Click the Message Control tab and add the following values: ○ Application: MR ○ Message type: INS ○ Process code: MRRL 17. ○ Name: Vendor 7. Configuring Your SAP ERP System . Enter the following values in the Outbound Options tab: ○ Receiver port: Enter the name of the receiver port. ○ Inv.: Select the radio button. Double-click the GSVERF message type in the Outbound parmtrs. Ariba Network Adapter for SAP NetWeaver Setup Guide 334 © 2015 SAP SE or an SAP affiliate company. Vendor 1000. Vendor 1000. Enter the following values in the Change Condition Records (Invoice Plan): Fast Change screen: ○ Company Code: Enter the company code. 16. For example. Size: 1 ○ Transfer IDoc Immed. Configuring the NACE Setting to Send MIRO Invoices Context Configure the NACE setting to send the MIRO invoices using the IDOC. 18. 15. Click Components. 4. Click MR0002 procedure in the Procedures table and then double-click the Control folder dialog structure. Implement the Customer exit as follows: ○ Go to the transaction code CMOD. The Change View "Procedures": Overview page appears. Enter MRMN0001 in the Enhancement text box and then click Enter. Double-click INCLUDE ZXMRNU01 in the Function Builder: Display EXIT_SAPLMRMN_001 page. 7. 335 . ZSUSMM1.Procedure 1. 3. Enter the following values: ○ Object: R3IR CMOD 2SUSMM1 ○ Package: Enter a name. All rights reserved. 3. 9. Click Enhancement assignments. 2. ○ Click Create. 6. For example. Procedure 1. 5. 2. The Create Object Directory Entry screen appears. Save the changes. ○ Enter a description in the Short Text field. Select application MR and then click Procedures. Double-click EXIT_SAPLMRMN_001. Enter the following code: Code Syntax /arba/cl_invoice_get_details=>invoice_get_details( Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. 4. ○ Enter a name. 8. Start transaction NACE. Add the following entries in the Reference Step Overview section on the Change View “Control”: Overview page: ○ Step: 30 ○ Counter: 0 ○ CTyp: ERS ○ Description: ERS Procedure Implementing the Customer Exit for MM Invoices Context Implement customer exits to make specific integration requirements to the transmission of MM invoices. 6. ○ Variable Name: INVOICE_DOC_OPTION ○ Field Name: To be left blank ○ Number: 0 (zero) ○ INCL/EXCL: I ○ Option: EQ ○ Selection value: XBLNR 14. To generate the access key. 11. Click the Activate button to go back to the CMOD screen. the MM invoices have duplicate IDOCs. 3. Scroll to the end and go to the routine number field. you must implement a routine. 10. Enter any routing number starting with 9. 904. 4. In some cases. 13. To send the XBLNR – reference document number as the Invoice ID to Ariba Network. 12. In the Application field. Activate the customer exit in the CMOD screen. Implementing Routines to Prevent Creation of Duplicate MM IDOCs Context The Ariba Network Adapter for SAP NetWeaver creates an FI IDOC each time an FI invoice is created on the SAP ERP system. To restrict the creation of duplicate MM IDOCs. Customer routines start with the number 9. 2. The Register Object page appears where you must enter the access key. 5. click Output control. Configuring Your SAP ERP System . On the Requirements menu. Save the entries. For example. enter MR and press Enter. All rights reserved. ○ Maintain the following parameter in the /ARBA/PARAM_TAB table. Ariba Network Adapter for SAP NetWeaver Setup Guide 336 © 2015 SAP SE or an SAP affiliate company. Ensure that you generate the access key for the routine to enable you to write add the ABAP code. Save the entries. Procedure 1. register the object in the SSCR (SAP Software Change Registration) by providing the object name. EXPORTING if_ident = if_ident is_data_ers = is_data_ers is_data_rap = is_data_rap is_data_kons = is_data_kons if_segnam = if_segnam CHANGING ct_idoc_data = ct_idoc_data[] ). Go to Transaction VOFM. do the following: ○ Go to transaction code SM30. 7. ENDIF. 10. Save the changes and click the Activate button. ○ Partn.: Enter the logical system for the SAP ERP system. A new ABAP editor page appears. Copy and paste the following code in the FORM KOBEV_<Routine Number>: Source Code DATA: lv_subrc TYPE subrc. 13. Click Continue. 12. In the Partner profiles: Outbound parameters screen. For example. 3. /arba/cl_invoice_get_details=>restrict_duplicate_idocs( EXPORTING t683s = t683s komkbmr = komkbmr CHANGING xnast = xnast[] cs_subrc = lv_subrc ). ensure that you maintain the following entries: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. 2. Maintaining Partner Profiles Context You must maintain the logical system profile for the outbound parameters if you use the IDOCs to process CC Invoices on the SAP ERP system. ○ Message Type: FIDCC2 In the Outbound Options tab. 9. Procedure 1. 337 . click Activate to activate the routine. sy-subrc = lv_subrc. Click the routine number in the Maintain: Requirements Output control page and then click then Source text button on the application tool bar. IF lv_subrc IS NOT INITIAL.. 1000. Press Enter. All rights reserved. 11. Double-click to expand partner type LS node and then click the vendor for that you want to maintain the partner profile. Enter the access key for the object. Go to transaction code WE20 to maintain the partner profiles. Click the Back button to go back and select the routine number on the Maintain: Requirements Output control page. 14. maintain the following values: ○ Partner No. On the Edit menu. 8. Type: LS ○ Partner Role: Specify the vendor. ○ End Date: Specify the end date. Ariba Network Adapter for SAP NetWeaver Setup Guide 338 © 2015 SAP SE or an SAP affiliate company. Click the Edit button and then click Create Model View . 10. Repeat Step 3 for the other Message Type: SYNCH. All rights reserved. Size: For example. Go to the transaction code BD82 to generate the partner profile for the FI transaction. Click the Trigger Immediately option in the Inb. 100 IDocs 9. Parameter section. Add the FIDCC2 message type and specify the sender and receiver system information.: Select the radio button. Click Continue. 8. Click Add Message Type. This creates the FIDCC2 and the SYNCH Message types as the Outbound Parameters at the logical system profile. For example. The Create Model View screen appears. Go to transaction BD64. ○ Start date: Specify the start date. ○ Transfer IDoc Immed. 4. Configuring the FI Invoices Context Add configuration for sending FI invoices using the BD64 transaction. ○ Technical name: Enter a technical name. please refer to Question 6 of the SAP Note 114814. ○ Basic type: FIDCCP02 ○ Extension: /ARBA/ FIDCCP02 ○ Cancel Processing After Syntax Error: Select the check box. Configuring Your SAP ERP System . 5. 7. Procedure 1. 6. 3. Click the Transfer IDoc immediately option in the Output Mode section. 4. Go to transaction code WE82 and link the FIDCC2 message type to the /ARBA/FIDCCP02 extension. ZFI. ○ Pack. Enter the following details: ○ Model View: ZFI ○ Partner System: Enter the system port for the partner system. If the FI invoices are getting cleared automatically. ○ Receiver port: Enter the name of the receiver port. Click Execute. 2. Enter the following values in the Create Model View screen: ○ Short text: Enter a description. 11. 2. Setting Document Type Filters for FI Invoices Context Maintain filters for FI invoices based on the document types. See Maintaining Partner Profiles [page 337] to create partner profiles. For example. Go to Transaction BD59. For example. 5. 3. 4. 339 . Verify these changes in the Outbound Options tab. Save the entries. All rights reserved. Go to Transaction BD95. Procedure 1.Results Ensure that the outbound parameters at the logical system profile have been created. Enter a name for E1FIKPF 1 XREF1_HD 378 20 the ALE object. 7. Add the following segment types. Field Offset IntLength Enter a name for E1FIKPF 1 BLART 20 2 the ALE object type. Click New Entries. The New Entries: Overview of Added Entries page appears. Add the following entries: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. ZXREF1_HD. Enter an object name in the ALE Object Type field for each of the following segment types: ALE Object Segm. Enter a name for E1FIKPF 1 BUKRS 0 6 the ALE object. BUKRS. For example. These filters can also be used to process purchase orders that do not have specific document types. 6. Click New Entries. Type No. BLART. The New Entries: Overview of Added Entries page appears. 8. Enter FIDCC2 in the Message Type field and press Enter. Click to expand it. 11.key (header) 1. Double-click Ref. For example. 20. ZXREF1_HD. If you do not maintain the output types in the /ARBA/ PARAM_TAB table. Go to Transaction BD64. KR. Add the document types that you want to filter for the FI invoices.Click Continue and save the BD64 entries. Ref. Ariba Network Adapter for SAP NetWeaver processes the FI invoices with the standard output type as ERS (Evaluated Receipt Settlement) invoices. and RE. Click Create Filter Group. However. Ensure that you create the routine before you maintain the output types in the NACE transaction. Click the Add button and add the global company codes for which the IDOC’s must be activated. the IDOC does not get generated for any of the FI invoices that you create on the SAP ERP system. and Document Type filter fields. Note If you maintain the company code instead of the global company code in the Global CoCde filter. T001 BUKRS_GLOB For example. Double-click the Data filter node. 19. Double-click Global CoCde. Enter the name of the ALE object type. BUKRS. 10. BKPF XREF1_HD For example. Click Edit and go to the model view FI. Configuring Your SAP ERP System . 14. The Filter group displays the Global CoCde. Ariba Network Adapter for SAP NetWeaver Setup Guide 340 © 2015 SAP SE or an SAP affiliate company. 9. All rights reserved. This is because the data filter specified has the company code entries instead of the global company code. 16. BLART. ALE Object Table Name Field Name Enter the name of the ALE object type. BKPF BLART For example. 17. the SAP ERP system displays a warning message. 15. 12.key (header) 1. Save the entries. Maintaining Output Types for FI Invoices Context Maintain the output types that you need for the FI invoices. Click the Add button and enter ISFIINVOICE in the Filter object type field. You can also save the changes. Double-click Document Type filter and then click the Add button. 13. 18. if you save the changes. Enter the name of the ALE object type. KZ. ○ Enter a description in the Short Text field. Click Enhancement assignments. Double-click EXIT_SAPLF050_001. 10. 6. Enter the routine number that you created in the Requirement field for the ERS condition type in the Reference Step Overview section on the Change View “Control”: Overview page. 3. 8. For example. Click the MR0004 procedure and repeat Step 6-7. ZFIDOC. 2. 5. 341 . 4. Click Procedures. Go to SM30. 7. Click Local Object. In the /ARBA/ PARAM_TAB table. 3. 5. Implementing the Customer Exit for FI Invoices Context Implement customer exits to make specific integration requirements to the transmission of FI invoices.Procedure 1. The SAP Enhancements in Enhancement Project page <object name> appears. Double-click INCLUDE ZX050U01 in the Function Builder: Display EXIT_SAPLF050_001 page. 8. 4. 6. Enter F050S004 in the Enhancement text box and then press Enter. ○ Click Create. Go to Transaction NACE. Repeat Step 5. The Change View "Procedures": Overview page appears. Select application MR and then click Procedures. Implement the Customer exit as follows: ○ Go to the transaction code CMOD. All rights reserved. The Change View “Control”: Overview page appears. The Create Object Directory Entry screen appears. Enter the following code: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System © 2015 SAP SE or an SAP affiliate company. 2. ○ Enter a name. 7. 9. Procedure 1. Save the changes. Click Components. Enter the following values: ○ Object: R3TR CMOD ZFIDOC ○ Package: Enter a name. maintain the new output types that you require for the FI invoice. Click MR0002 procedure in the Procedures table and then double-click the Control folder dialog structure. Enter the following code: Code Syntax /arba/cl_invoice_get_details=>fi_invoice_get_details( EXPORTING if_message_type = message_type CHANGING ct_idoc_data = idoc_data[] ct_idoc_control = idoc_control cs_boole = distribution ). Buyers can use the SLG1 T-code to view all messages in the application log on the SAP system. Click the Activate button to go back to the CMOD screen. Save the entries. Save the entries. Note When an IDOC is generated for an FI invoice. Ariba Network Adapter for SAP NetWeaver Setup Guide 342 © 2015 SAP SE or an SAP affiliate company. 17. You must maintain the Ariba tax codes. 12. 13. 19. All rights reserved. Activate the customer exit in the CMOD screen. To maintain the tax code. Configuring Your SAP ERP System . ○ Maintain the required tax codes in the /ARBA/TAXCAT_MAP table. Handling Errors Buyers can use the SLG1 transaction code to view all messages in the application log on the SAP system. Errors that occur while transmitting the MM and FI invoices in the Ariba Procurement Solution are stored in the SXMB_MONI if a system error occurs while sending the invoices from the ERP system to the PI. 18. Click the Activate button to go back to the CMOD screen. the Ariba Procurement Solution does not map the Distribution node. 11. Double-click INCLUDE ZX050U07 in the Function Builder: Display EXIT_SAPLF050_007 page. Code Syntax CALLMETHOD /arba/cl_invoice_get_details=>fi_get_line_amount EXPORTING message_type = message_type sap_segment_name = sap_segment_name sap_segment_data = sap_segment_data fi_document_header = fi_document_header fi_document_item = fi_document_item CHANGING cust_segment_name = cust_segment_name cust_segment_data = cust_segment_data. 15. do the following: ○ Go to transaction code SM30. 14. Double-click EXIT_SAPLF050_007. 16. 343 . All rights reserved. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. SAP Suite Add-On is developed by SAP to allow SAP ERP systems to connect to Ariba Network through SAP NetWeaver PI.Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On Overview [page 343] Installation Requirements for SAP Suite Add-On [page 346] Setting Up the cXML Adapter [page 347] Configuring Logging for the SAP Suite Add-On [page 350] Configuring the cXML Adapter [page 350] Configuring the System Landscape Directory [page 350] Configuring Transaction Processes [page 354] Configuring Integration Scenarios in the Integration Directory [page 356] Configuring the Integration Directory for Inbound Transactions [page 357] Configuring the Integration Directory for Outbound Transactions [page 364] Linking Multiple SAP Instances with Ariba Network [page 371] Testing the SAP NetWeaver for Suite Add-On Configuration [page 375] Understanding Error Handling [page 376] Monitoring the cXML Adapter from Runtime Workbench [page 379] Deploying the Project [page 380] Enabling Support for Attachments [page 381] Using Endpoints for Integration with SAP NetWeaver for SAP Suite Add-On [page 382] Using the SAP NetWeaver PI KeyStore [page 382] Overview The Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On is an add-on module for SAP business applications that enables integration between Ariba Network and SAP Suite Add-On component available in your SAP ERP system. Note The SAP Suite Add-On module generates documents in cXML format and therefore does not require ABAP transports. SAP ERP buyers and suppliers using Ariba Network Adapter for SAP NetWeaver integrated with SAP Suite Add-On and Ariba Network can now send and receive transactional documents through the PI layer or directly without the Ariba Integration Toolkit. For more information about cXML and Ariba Network. available from Connect (http://connect. and forwarding messages. which contains integration processes. SAP NetWeaver PI integrates the following components used by the Ariba Network Adapter for SAP NetWeaver and its modules: ● The Integration Engine is the central runtime component of the SAP NetWeaver PI Integration Server used for receiving. It uses adapters to connect the Integration Engine to SAP systems (RFC adapter) and external systems.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. refer to the following documents.java. It facilitates cross-system business processes. The following graphic illustrates how the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On enables the communication flow between Ariba Network and the SAP Suite Add-On. see the relevant section on the Sun Java web site (http:// www. For more information about the JCA specification.com ). and can be thought of as a library for SAP NetWeaver PI. SAP NetWeaver PI is a platform for process integration within SAP NetWeaver. which conforms to the J2EE Connector Architecture (JCA) specification. processing. and communication channels. ● The product and component definitions that are available in a CIM file.sun. All rights reserved. ● The Adapter Engine is a runtime component of the SAP NetWeaver PI Integration Server. it enables different versions of SAP and non-SAP systems from different vendors running on different platforms to communicate with each other. and implements the cXML transport protocol. 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.The Ariba Network Adapter for SAP NetWeaver runs on the SAP NetWeaver Process Integration (PI). ● The cXML Adapter. Ariba Network Adapter for SAP NetWeaver Setup Guide 344 © 2015 SAP SE or an SAP affiliate company. interface objects. In particular. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . All rights reserved. Configure the SAP Suite Add-On component. Configuring the System Landscape Directory. Testing the configuration. 3. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. 4.Supported Document Types The following transactions are supported as part of the Ariba Network integration with SAP Suite Add-On: Outbound Transactions for Buyers Inbound Transactions for Buyers Purchase Order Order Confirmation Change Purchase Order Ship Notice Goods Receipt Invoice Payment Proposal CC Invoice Receipt Request Pay Me Now Remittance Advice Service Entry Sheet Remittance Status Update Quote Message Service Entry Sheet Response Status Update Request Quote Request Outbound Transactions for Suppliers Inbound Transactions for Suppliers Order Confirmation Purchase/Sales Order Ship Notice Change Purchase Order Invoice Goods Receipt CC Invoice Payment Proposal Pay Me Now Receipt Request Service Entry Sheet Remittance Advice Quote Message Remittance Status Update Service Entry Sheet Response Status Update Request Quote Request Workflow for Configuring the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On Setting up the adapter involves the following high-level steps: 1. Setting up and configuring the cXML Adapter. 345 . Configuring transaction processes. 2. Verifying that all the software and connectivity requirements are in place. 5. 6. a secure protocol that encrypts communication before transmission. ● If the Ariba Network Buyer account is configured to use digital certificate authentication.1 SAP Netweaver PI 7. For more information about creating a supplier relationship.sap.com > SAP NetWeaver > SAP NetWeaver PI 7.ariba. “Configuration” in the Ariba Network Integration Guide. ● The Ariba Network’s Certificate Authorities certificates are stored in the SAP NetWeaver PI Keystore. see Chapter 4. For more information about obtaining a digital certificate. Ariba Connect (http://connect.Installation Requirements for SAP Suite Add-On Supported SAP Netweaver PI Versions The following table lists the Ariba Network Adapter for SAP NetWeaver versions and the supported SAP Netweaver PI versions that they can be deployed on: Ariba Network Adapter for SAP NetWeaver Version Supported SAP Netweaver PI Versions Cloud Integration 1 SAP Netweaver PI 7. ● 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). see the following SAP NetWeaver section on the SAP Service Marketplace: service. Installation Files To install the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On. ● An Ariba Network supplier relationship. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On .com).3 Cloud Integration 2 or higher SAP Netweaver PI 7. Ariba Network Adapter for SAP NetWeaver Setup Guide 346 © 2015 SAP SE or an SAP affiliate company. including an ANID-to-Private ID mapping. see the Ariba Network Buyer Administration Guide. For more detailed information about internet connectivity requirements.4 For information about the platforms that the SAP NetWeaver suite supports. see Ariba cXML Solutions Guide. see the cXML Adapter Parameters [page 391] section. For more information about how to enable secure communications through a proxy server. All rights reserved. The cXML Adapter uses the certificates stored in the SAP NetWeaver PI Keystore to connect to Ariba Network. see the Ariba Network Integration Guide.3 SAP Netweaver PI 7. For more information about configuring your Ariba Network Buyer account. you need the relevant archive file which is available on Ariba’s support interface. then a valid Secure Socket Layer (SSL) client certificate from one of Ariba Networks trusted Certificate Authorities is required. configured Ariba Network Buyer account.X > Availability.1 SAP Netweaver PI 7. Ariba Network Requirements Ensure that you have the following Ariba Network requirements before installing the Ariba Network Adapter for SAP NetWeaver: ● A valid. sca CacheCatalog. For details on downloading this guide. which conforms to the JCA specification and implements the cXML transport protocol. For more information about document transmission methods. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. This section contains the following topics: ● Understanding cXML Adapter Document Transmission ● Deploying the cXML Adapter ● Configuring the Log ● Configuring the cXML Adapter Understanding cXML Adapter Document Transmission Ariba Network exchanges business documents using the cXML (commerce eXtensible Markup Language) protocol. The Ariba Network Adapter for SAP NetWeaver initiates the cXML GetPending transaction to pull inbound business documents. cXML defines document formats and interaction processes designed for exchanging procurement- oriented information. AribaNetworkAdapterSAPNetweaver_vCI_1. The Ariba Network Adapter for SAP NetWeaver always uses HTTPS Post to send documents to Ariba Network. 347 . see Ariba Network Certification [page 380]. Ariba Network responds with a GetPendingResponse document that includes zero or more DataAvailableMessage elements containing the internal ID of any waiting documents.SoftwareCatalog.xml Setting Up the cXML Adapter The Ariba Network Adapter for SAP NetWeaver relies upon the cXML Adapter. The GetPending transaction is scheduled using the getPendingInterval parameter defined for each inbound transaction.zip Design and Integration configuration files AribaNetworkAdapterSAPNetweaver_SapAddOn. The archive ZIP files contain the following components: Product definition files AribaNetworkAdapterSAPNetweaver. The GetPending transaction allows the SAP ERP system to receive documents from Ariba Network through a data pull. All rights reserved.For example.xml CanonicalCatalog. see the Ariba Network Integration Guide.zip.tpz cXML Adapter and metadata definition files AribaNetworkAdapterSAPNetWeaver. 4. Place the SCA file in the specified location in the JSPM window. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . From SAP netweaver version PI7. After the SCA file is loaded.Deploying the cXML Adapter If your version of SAP netweaver PI is prior to PI 7. Deploying the cXML Adapter Using JSPM Context Use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI. On the Start Deployment tab. 8.ariba.com. For more information on how to install or upgrade using the SUM tool. contact your SAP systems administrator. Run the go. see Undeploying the Adapter using the Textconsole [page 349]. and click Next. Procedure 1. click Next to start the deployment. 3. D:\usr\sap\trans\EPS\in. For example. This starts the deployment of the cXML Adapter. Ariba Network Adapter for SAP NetWeaver Setup Guide 348 © 2015 SAP SE or an SAP affiliate company. Navigate to the JSPM tool directory *****\JSPM\go.bat. 5. 2. Note To upgrade to the latest version of the Ariba Network Adapter for SAP NetWeaver.3 EHP1. Click Next in the Specify Queue and Check Queue tabs. use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI. you must first undeploy the existing adapter and then deploy the latest version that you have downloaded from connect.3 EHP1 onwards you must use the SAP Software Update Manager (SUM) tool to deploy the adapter. 6. Note You cannot undeploy the adapter using the JSPM. 7. Click Exit after the deployment is completed. D:\usr\sap\NPI\DVEBMGS00\j2ee\\JSPM\go. Enter your user name and password to login. All rights reserved. 9. choose New Software Components.bat file to open the JSPM window. For information on how to undeploy the adapter.bat. For example. . Run the following at the telnet prompt: >undeploy name=com.sap.asc. version: 'null'.Undeploying the Adapter using the Textconsole Context You must use the textconsole script to undeploy the adapter.com on_undeploy_error=stop Undeploy Settings: ○ on_undeploy_error=stop ○ on_prerequisite_error=stop ○ workflow=normal If there is an offline undeployment.ra vendor=ariba.ra vendor=ariba.com on_deploy_error=stop Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. Login with the relevant admin user.netweaver.ra'.sap.asc.ariba.asc. version: '3. location: 'SAP AG'. please wait.ariba.ra'. software type: 'J2EE'.xiadapter.ariba..netweaver. Procedure 1. location: 'null'. Go to <SAP instance>\j2ee\console. 3.com'. All rights reserved. Telnet connection to host might be lost and the following message appears: Processing undeployment operation.com'. vendor: 'ariba.netweaver. The Telnet console appears.0.asc. status: 'Success'.sap. dependencies: '[]'' > Undeploying the Adapter using the Textconsole Procedure Run the following at the Telnet prompt: deploy name=com.netweaver. sda: 'name: 'com. description: ''. vendor: 'ariba.sh.bat or textconsole. 4.0000'.xiadapter. Run textconsole.ariba.xiadapter. 349 . name: 'com.1420051114090313.sap.xiadapter. 2. and then click Save Configuration in the toolbar. 5. All rights reserved. Configuring the System Landscape Directory Once you have installed the cXML Adapter. Select the node (package) com ariba asc . While configuring the communication channel for each outbound or inbound transaction. to set the logging level to log the complete adapter processing information.Configuring Logging for the SAP Suite Add-On Configure logging to send log entries for the cXML adapter to a separate file. 4. see the Communication Channels Configuration procedure for each scenario in the Configuring Integration Scenarios in the Integration Directory [page 356] section.sap. Change the severity level from Error to Info / Debug in the Severity drop-down list.util to set the logging level to log only the exchanged messages. Login to the SAP NetWeaver PI log administration section at http:// XI_hostname_server:XI_port/nwa/logs. This configuration is done at a later stage. during the configuration of Integration Scenarios in the Integration Directory. Click the Log Configuration link. but Ariba recommends that you change the log level to Info. see the Ariba Network Integration 1. The log level can remain Error when running in a production environment. 3. the Parameters tab has the System Type option to specify the system for the buyer or supplier connecting to the Ariba Network. Select Tracing Locations from the Show drop down list. The SAP System Landscape Directory is a central repository that holds the information on the Ariba Network Adapter for SAP NetWeaver Setup Guide 350 © 2015 SAP SE or an SAP affiliate company.cxml. 1. Configuring the cXML Adapter To allow the cXML adapter to run correctly. you must configure parameters for the Communication Channels for different business scenarios. or select CXMLSender under connector.com/se4aribanet10. see cXML Adapter Parameters [page 391]. 2. For a description of the parameters and instructions for how to configure retry attempts. For more details about how to create the Communication Channels. You can also find out about the version of the Ariba Network Adapter for SAP NetWeaver. you must then configure the System Landscape Directory (SLD) by importing the Ariba Network Adapter for SAP NetWeaver product definition and defining the systems involved in the integration. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . Note For additional information.0 for SAP Business Suite http:// help. and on which machines. under Software Catalog.1 8. 6. Click Browse and navigate to the location where the AribaNetworkAdapterSAPNetweaver. Click Administration. From the SAP NetWeaver PI main page. Select this file. 3.com ○ Version: CIX Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. Open the SLD Administration page. click Import. 7. All rights reserved. verify that the following component is available: ○ Vendor: ariba. You must make the following settings in the SLD: ● Import Ariba Network Product and Component definitions ● Define Technical and Business Landscape for Ariba Network ● Define Technical and Business Landscape for SAP ERP Importing Ariba Network Product and Component Definitions Import the product and component definitions of Ariba products that will work with SAP NetWeaver PI.systems and software in the customer environment. instances. 5. It consolidates the information about components actively available.com ○ Component: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CIX of ariba. 351 . The Ariba Network Adapter for SAP NetWeaver leverages all the advantages of the SLD in order to maintain the coherence of the system landscape: ● It is defined as a product and component expressed in Common Information Interface (CIM) format importable in the SLD ● It uses a configuration using technical and business systems involved in the Ariba Network integration and defined in the SLD. Click Import. click System Landscape Directory.zip is stored. click Products and verify that the following product is available: ○ Vendor: ariba. as a CIM file. To import product and component definitions: Procedure 1. and clients they are available. Under the Content section. 2. NW04.SoftwareCatalog.com ○ Product: ASN ○ Version: ASN. From the SAP NetWeaver PI main page. Next. 4. Select Business System from the main SLD page to open the Business System page. Click Finish. Ariba Network Adapter for SAP NetWeaver Setup Guide 352 © 2015 SAP SE or an SAP affiliate company. Click New Business System here to open the Business System Wizard. E. 3. Scroll down the list to select the product. To define the Business System for Ariba Network: Procedure 1. In the Wizard. defined earlier. Select Technical Systems from the main SLD page to open the Technical System page. is selected. 7.g. 2. To define the Technical System for Ariba Network: Procedure 1. ASN. set up the business system for the Ariba Network system using the Business System Wizard. Click New Technical System to open the Technical System Wizard. an 5. Specify the system details as follows: ○ System Name: Specify a user-defined system name here. 4. select Third-Party as the Technical System Type to set up a third-party (non-SAP) application such as Ariba Network. 6.g. Next Steps Next. You can also filter to select the product to associate. and then click Next. Defining Technical and Business System for Ariba Network Set up the technical system for the Ariba Network system using the Technical System Wizard. 2. All rights reserved. Ensure that the component ARBA_SUPPLIER_CONN_ADAPTER. E. Click Next. TS_ASN ○ Host Name: Enter a host name here. Associate the ASC Connector product and component to the system. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . and then click Add.Results The Ariba Network Adapter for SAP NetWeaver is now recognized by the Integration Repository and Directory. Define software product and components. NW04. TS_ASN. (Optional) Define additional application servers if required. Enter the business system name. and then click Next. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. In the Wizard. and then click Next. and click Next. Select the SAP ERP version installed on this technical system. BS_ASN. in the Name field. installed on the technical system. 9. Enter values in the Host Name and Instance Number fields for the Central Application Server. and click Add Application Server. All rights reserved. You can also filter to select the logon groups. as well all other products installed on the system. and Database Host Name fields. enter values in the AS ABAP name (SID).3. To specify the SAP ERP system details. and then click Next. select Third-Party as the technical system type to associate the business system with. You can filter to select the installed products and the software components. select AS ABAP as the Technical System Type. 6. Specify values in the Host Name and Instance Number columns in the Application Server List table. 8. In the Wizard. Specify a logon group for the Message Server by entering a value in the Logon Groups column and clicking Add Logon Groups to assign them. Enter values in the Client Number and Logical Client Name columns of the Client List table. and Message Server Port field.1 and the related component ARBA_SUPPLIER_CONN_ADAPTER. and then click Next. You can also filter to select the application server details. Click Finish. from the System field. Click Finish. Click Next. e. 7. Note The Logical System Name is not required. 6. 3. and then click Next. 5. Installation Number. 4.g. CIX of ariba. Select Technical System from the main SLD page to open the Technical System page. Defining the Technical System for SAP ERP Context Set up the technical system for the SAP ERP system using the Technical System Wizard. Select the technical system. Specify the installed products. Enter values in the Host Name. and then click Next. are selected. Click on New Technical System here to open the Technical System Wizard. 5. 2. 4. Make sure that the product ASN. 353 .com. Procedure 1. and then click Next. Define the Client. created in the previous procedure. Specify the Message Server and Central Application Server. 7. In the Wizard. and then click Next. 4. ● Configure the different transactions in the Integration Directory by importing the scenarios from the Integration Repository. Select Business System from the main SLD page to open the Business System page. Click New Business System here to open the Business System Wizard. 6. 7. 3. Select the products that must be supported by this business system from the ones available from the associated technical system. Defining the Business System for SAP ERP Procedure 1. for each supported transaction. BS_SAPR3_50. 2. In the case of application systems. 5. Select Application System as the Business System Role and select your SAP NetWeaver PI instance name from the Related Integration Server drop-down list to specify the integration server. and then click Next. ● Configure SAP NetWeaver PI connectivity to SAP ERP. Click Finish. Ariba Network Adapter for SAP NetWeaver Setup Guide 354 © 2015 SAP SE or an SAP affiliate company. Specify the installed products. Note The names for objects in the Directory used in the configuration procedures are examples provided for illustration. you must then: ● Import the design package containing the transactions supported by the Ariba Network Adapter for SAP NetWeaver. to associate it with the business system. specify the integration server. You may use them or replace them with names and format corresponding to your system environment. select AS ABAP as technical system type to associate the business system with. Select a client for the selected technical system from the Client drop down list. Enter the business system name.Next Steps Set up the business system for the SAP ERP system using the Business System Wizard. Configuring Transaction Processes Once you have installed the SLD. E. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . Select the technical system created in the previous procedure from the System drop down list. Select the role of the business system. and click Next. to install them in the business system. All rights reserved. 8. ● Configure the communication channels and the conditions for routing messages. and then click Next.g. option. Note The External SAP Add-On schema is http://ariba.tpz to the import directory on the SAP NetWeaver PI server. After the import completes. 4. D:\usr\sap\ARB\SYS\global\xi\repository_server\import. Assigning Business Systems in the Integration Directory Context The Integration Directory configuration of the Ariba Network Adapter for SAP NetWeaver uses the information on the Technical and Business systems from the SLD. For information about proxy configuration for outbound documents. 355 . All rights reserved.com/xi/ASN/AddOn/CommonBasis..tpz from the available files list.. 3. the component ARBA_SUPPLIER_CONN_ADAPTER CIX appears in the components list of the Integration Builder Design Tool. Open the Integration Builder: Design Tool from the SAP NetWeaver PI main page. select the Import Design objects. 5. see cXML Adapter Parameters [page 391]. You must assign the Business Systems defined and involved in the integration setup.Importing the Design Package Context The transport file AribaNetworkAdapterSAPNetweaver_SapAddOn. Select AribaNetworkAdapterSAPNetweaver_SapAddOn. and then click OK. Procedure 1. *****\SYS\global\xi\repository_server\import. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. 2.tpz contains the definition of the business scenarios. From the Tools menu. For example. The Adapter metadata is http://ariba. Copy the package file AribaNetworkAdapterSAPNetweaver_SapAddOn. Configuring SAP ERP Connectivity The inbound and outbound documents are exchanged between SAP NetWeaver PI and SAP ERP by using ABAP proxies.com/xi/ASCAdapter. from the list. Configuring Integration Scenarios in the Integration Directory This section describes how to import and configure the integration scenarios in the SAP NetWeaver PI Integration Directory for the supported transactions. Click on Continue in the first and second windows. Open the Configuration: Integration Builder from the PI main page. From the context menu for Business System. For more information about creating business systems. which has to be imported into the Integration Repository first. 2. Note If you have multiple ERP systems. Select Business Systems.4 dual stack (ABAP and Java) Ariba Network Adapter for SAP NetWeaver Setup Guide 356 © 2015 SAP SE or an SAP affiliate company.1 ● SAP NetWeaver PI 7. All rights reserved. if it is checked. see the Configuring the System Landscape Directory [page 350] section. navigate to Service Without Party Business System. Leave the Party field in the second window blank.3 dual stack (ABAP and Java) ● SAP NetWeaver PI 7.3 single stack (Java only) ● SAP NetWeaver PI 7.4 single stack (Java only) ● SAP NetWeaver PI 7. 7. 4. 5. you must select all the Business Systems representing your SAP ERP instances involved in the integration.Procedure 1. 6. In the third window. You can configure these transaction scenarios in the following SAP NetWeaver PI versions: ● SAP NetWeaver PI 7. The Integration Scenarios are part of the Design package. select Assign Business System to start the Assign Business System wizard. In the Objects tab of the Integration Builder. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . to avoid the creation of unnecessary channels. Click Finish. Click to clear the Create Communication Channel Automatically check box. Note Do not activate the Change Lists feature of Integration Builder Configuration Tool until all the configuration steps are completed. 3. select the business systems BS_ASN and BS_SAPR3_50 created earlier. Use an integration scenario from the Integration Repository as a template for configuring the corresponding transaction in the Integration Directory. Workflow for Configuring the Integration Scenario for Inbound And Outbound Transactions Configuring the integration scenarios for the outbound and inbound transactions involves the following steps: 1. Transfer the Integration Scenario from the Integration Repository Enterprise Service Builder to the Integration Directory Integration Builder . For more information, see: ○ Transferring the Integration Scenario for Inbound Transactions [page 357] ○ Transferring Integration Scenario for Outbound Transactions [page 364] 2. Configure the Integration Scenario. For more information, see: ○ About Configuring the Integration Scenario for Inbound Transactions [page 359] ○ About Configuring the Integration Scenario for Outbound Transactions [page 366] 3. Configure the Communication Channels. For more information, see: ○ Configuring Communication Channels for Inbound Transactions [page 362] ○ Configuring Communication Channels for Outbound Transactions [page 369] 4. Activate the integration scenario. For more information, see: ○ Activating the Scenario for Inbound Transactions [page 363] ○ Activating the Scenario for Outbound Transactions [page 370] Note ○ Ensure that the design package is imported into your system and ready before you run these steps. The following steps assume that the different Business Systems are defined in the SLD. For more information, see About Configuring the System Landscape Directory [page 343]. ○ All the steps of a configuration scenario section must be completed to fully configure a scenario. ○ If you are an existing customer, you must delete the existing Configuration scenario and rerun the steps for the configuration scenario. Configuring the Integration Directory for Inbound Transactions Transferring the Integration Scenario for Inbound Transactions Context The first step to configure the integration scenario is to transfer the integration scenario to the Integration Builder. The integration scenario is loaded into the Integration Repository when the design package is imported. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. All rights reserved. 357 Procedure 1. From the SAP NetWeaver PI main page, select Integration Directory Integration Builder , and then login to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select Tools Apply Model from ES Repository . 3. In the first screen of the Transfer Model from ES Repository wizard > Select Process Integration Scenario, click the Name field, and then click the Display Input Help pull-down menu and select Input Help. 4. Select the Process Integration Scenario for the following inbound transactions from the Enterprise Services Repository screen: Buyer ○ Order Confirmation Name: AR_AddOn_OrderConfirmation_Send Namespace: http://ariba.com/xi/ASN/AddOn/OrderConfirmation Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Ship Notice Name: AR_AddOn_AdvanceShipNotice_Send Namespace: http://ariba.com/xi/ASN/AddOn/AdvanceShipNotice Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Invoice Name: AR_AddOn_Invoice Namespace: http://ariba.com/xi/ASN/AddOn/Invoice Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Pay Me Now Name: AR__AddOn_PayMeNow_Send Namespace: http://ariba.com/xi/ASN/AddOn/PayMeNow Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Service Entry Sheet Name: AR_AddOn_ServiceEntrySheet_Send Namespace: http://ariba.com/xi/ASN/AddOn/ServiceEntrySheet Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ QuoteMessage Name: AR_AddOn_QuoteMessage_Send Namespace: http://ariba.com/xi/ASN/AddOn/QuoteMessage Software Component Version: ARIBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com Supplier ○ Sales Order Name: AR_AddOn_SalesOrder_Send Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com ○ Payment Remittances Name: AR_AddOn_PaymentRemittanceRequest_Send Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com 5. Click Continue. Ariba Network Adapter for SAP NetWeaver Setup Guide 358 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On 6. If required, change the name of the scenario for the Integration Directory. 7. Click Finish and then Close. Once the integration scenario transfer is completed, the Model Configurator window appears. About Configuring the Integration Scenario for Inbound Transactions Configuring the Integration Scenario involves the following steps: 1. Assigning the model. 2. Assigning the components. 3. Configuring the sender and receiver relations for individual connections. 4. Generating the configuration objects. Assigning the Model for Inbound Transactions Procedure 1. In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique model that is selected by default. 2. After selecting the model, assign components to the application components for the selected integration scenario. Assigning Components for Inbound Transactions Procedure 1. In the Model Configurator, click the Assign Component button. 2. In the Assign Components window, select the Business System Components for A2A tab to assign business systems for the integration scenario. 3. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is available. 4. Click the row under the Communication Component column, then click the Value List pull-down menu and select Value List <F4. Select the communication component name for the business system of your SAP PI system, from the selection list and click Apply. Note If you have multiple ERP systems, add the multiple communication components defined for your multiple SAP PI systems by repeating the Step 3 and 4. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. All rights reserved. 359 5. Click the Next Application Component button (the right arrow) to go to the next screen on the window. 6. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. 7. Click the row under the Communication Component column, then click the Value List pull-down menu and select Value List <F4. Select the communication component name for the business system for Ariba Network, from the selection list and click Apply. 8. Click the Save Settings button. Configuring Sender And Receiver Relations for Individual Connections for Inbound Transactions Procedure 1. In the Model Configurator, click the Configure Connections button. You must assign Communication Channels to set up the connections. 2. In the Connections from Component Assignment tab in the Configure Connection window, click the empty Communication Channel cell corresponding to the business system for Ariba Network in the Sender Business System Components table. 3. Click the New Communication Channel button (the icon at the top left), and then select Create Communication Channel with Template to start the Create Communication Channel wizard. 4. Click Continue. 5. On the next page, click the Name field and then click the Display Input Help pull-down menu and select Input Help. 6. Select the Communication Channel Templates for the following transactions: Buyer ○ Order Confirmation Name: CCT_AddOn_OrderConfirmation_cXML_Sender Namespace: http://ariba.com/xi/ASN/AddOn/OrderConfirmation Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Ship Notice Name: CCT_AddOn_AdvanceShipNotice_cXML_Sender Namespace: http://ariba.com/xi/ASN/AddOn/AdvanceShipNotice Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Invoice Name: CCT_AddOn_Invoice_cXML_Sender Namespace: http://ariba.com/xi/ASN/AddOn/Invoice Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Pay Me Now Name: CCT_AddOn_PayMenow_cXML_Sender Namespace: http://ariba.com/xi/ASN/AddOn/PayMeNow Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Service Entry Sheet Name: CCT_AddOn_ServiceEntrySheet_cXML_Sender Namespace: http://ariba.com/xi/ASN/AddOn/ServiceEntrySheet Ariba Network Adapter for SAP NetWeaver Setup Guide 360 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ QuoteMessage Name: CCT_AddOn_QuoteMessage_cXML_Sender Namespace: http://ariba.com/xi/ASN/AddOn/QuoteRequest Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com Supplier ○ Sales Order Name: CCT_AddOn_Supplier_SalesOrder_cXML_Sender Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com ○ Payment Remittances Name: CCT_AddOn_Supplier_PaymentRemittanceRequest_cXML_Sender Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com 7. Click Continue. 8. You can also choose to modify the channel names. Click Finish. Tip If you have already created and configured a Sender channel for the business system for Ariba Network in another transaction, you can create the communication channel by copying from a channel that has already been configured. 9. In the Connections from Component Assignment tab, click the empty Communication Channel cell corresponding to the business system of your ERP PI system in the Sender Business System Components table. 10. Click on the Value List drop down and select Value List <F4. Select the CC_Proxy_Sender communication channel from the selection list and click Apply. 11. Click the Activate All Connections button, and then click OK. 12. Click the Save Settings button. Generating Objects for Inbound Transactions Procedure 1. In the Model Configurator, click the Create Configuration Object button. 2. In the Create Configuration Object window, do the following: ○ Click Generation in the General section. ○ Select the Receiver Determination, and Interface Determination check boxes in the Scope of Generation section. 3. Click Create New in the Change List for Generated Objects section. The text box already contains an object name that you can use or modify. 4. Click Start to begin generating objects. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. All rights reserved. 361 5. After the object generation is complete, click Apply to save the new configuration settings. Close the log that is created without saving. You can save it, if required. Results Note ● Generating the objects creates the configuration objects if they do not yet exist. If they already exist, they are reused and enhanced, if required. You can also simulate generation for test purposes. ● Buyers can receive the same service entry sheets in multiple ERP systems, To do this, buyers must configure the integration scenario for service entry sheets and specify the Communication Component for each ERP system in the Receiver, Receiver Interfaces, and Outbound Processing tabs on the Edit Integrated Configuration page. ● In the Receiver tab, buyers must also specify the XPath option in the Condition field by selecting the logical system name corresponding to the business system for each ERP system. For example: (/descendant:cXML/Header/To/Credential/@domain = SystemID AND / descendant:cXML/Header/To/Credential/Identity = <Name of the logical business system> Configuring Communication Channels for Inbound Transactions Procedure 1. In the Communication Channel list, double-click the following communication channels to open it: Buyer ○ Order Confirmation |< Name of the Business System for Ariba Network> | CC_AddOn_OrderConfirmation_cXML_Sender ○ Ship Notice |< Name of the Business System for Ariba Network> | CC_AddOn_AdvanceShipNotice_cXML_Sender ○ Invoice |< Name of the Business System for Ariba Network> |CC_AddOn_Invoice_cXML_Sender ○ PayMeNow |< Name of the Business System for Ariba Network> | CC_PayMeNow_cXML_Sender ○ Service Entry Sheet |< Name of the Business System for Ariba Network> | CC_ServiceEntrySheet_cXML_Sender ○ Quote Message < Name of the Business System for Ariba Network> | CC_AddOn_QuoteMessage_cXML_Receiver. Ariba Network Adapter for SAP NetWeaver Setup Guide 362 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On Supplier ○ Sales Order |< Name of the Business System for Ariba Network>| CC_AddOn_Supplier_SalesOrder_cXML_Receiver | ○ Payment Remittance < Name of the Business System for Ariba Network> | CC_AddOn_Supplier_PaymentRemittanceRequest_cXML_Receiver 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network buyer account configuration. 3. Under the cXML Configuration section, select the Use SAP Add on Suite check box. Note If you created the channel by copying from an existing channel, you must change the request type for each of the transactions to the <Name of the transaction request - for example, Invoice> in the Inbound Request Type field. 4. If required, edit the other parameters. 5. Update the cXML version parameter to the latest applicable version. For more information about the cXML adapter parameters, see cXML Adapter Parameters [page 391]. 6. Save the changes. Activating the Scenario for Inbound Transactions Procedure Using the Change List tab on the main application screen, activate all the change lists containing the objects created and modified during the component setup. Results This completes the configuration of the inbound transactions in SAP NetWeaver PI. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. All rights reserved. 363 Configuring the Integration Directory for Outbound Transactions Transferring Integration Scenario for Outbound Transactions Context The first step is to transfer the integration scenario to the Integration Builder. The integration scenario is loaded into the Integration Repository when the design package is imported. Procedure 1. From the SAP NetWeaver PI main page, select Integration Directory Integration Builder , and then login to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select Tools Apply Model from ES Repository . 3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, and then click the Display Input Help pull-down menu and select Input Help. 4. Select the process integration scenario for the following transactions from the Enterprise Services Repository screen: Buyer: ○ Purchase Order Name: AR_AddOn_PurchaseOrder_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PurchaseOrder Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ CC Invoice Name: AR__AddOn_CCInvoice_Receive Namespace: http://ariba.com/xi/ASN/AddOn/ERPInvoice Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Proposal Name: AR__AddOn_PaymentProposal_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PaymentProposal Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Remittance Name: AR__AddOn_PaymentRemittance_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittance Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Remittance Status Update Name: AR__AddOn_PaymentRemittanceSUR_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittanceSUR Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com Ariba Network Adapter for SAP NetWeaver Setup Guide 364 © 2015 SAP SE or an SAP affiliate company. All rights reserved. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On com 5. 6.com/xi/ASN/AddOn/GoodsReceipt Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba. If required. ○ QuoteRequest Name: AR_AddOn_QuoteRequest_Receive Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com ○ Ship Notice Name: AR_AddOn_OutboundDeliveryNotification_Receive Namespace: http://ariba. 7. The Invoice Status Update Request is no longer available.com ○ Invoice Name: AR_AddOn_Invoice_Receive Namespace: http://ariba.com ○ ServiceUpdateResponse Name: AR_AddOn_StatusUpdateResponse_Receive Namespace: http://ariba. the Model Configurator window appears.com Supplier ○ Sales Order Confirmation Name: AR_AddOn_SalesOrderConfirmation_Receive Namespace: http://ariba. 365 .com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company.com Note Buyers must use the new StatusUpdateRequest to send and receive status on invoices and service entry sheets. Click Continue. ○ Receipts Name: AR_AddOn_GoodsReceipt_Receive Namespace: http://ariba. change the name of the scenario for the Integration Directory.com/xi/ASN/AddOn/StatusUpdateResquest Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba. Results Once the integration scenario transfer is completed.com/xi/ASN/AddOn/QuoteRequest Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba. All rights reserved. Click Finish. Click the row under the Communication Component column. 3. then click the Value List pull-down menu and select Value List <F4. click the Select Component View button. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . After selecting the model. Click the row under the Communication Component column. add the multiple communication components defined for your multiple SAP PI systems by repeating the Step 3 and 4. Assigning the components. 3. from the selection list and click Apply. 4. Click the Next Role button (the right arrow) to go to the next screen on the window. In the Model Configurator window. 5. In the Assign Components window. select the Business System Components for A2A tab to assign components for Ariba Network. click the Assign Component button. Assigning the model.About Configuring the Integration Scenario for Outbound Transactions Configuring the Integration Scenario involves the following steps: 1. 2. and then click Apply to select the unique model that is selected by default. Configuring the sender and receiver relations for individual connections. 2. In the Model Configurator. assign components to the application components for the selected integration scenario. 6. Select the communication component name for the business system of your SAP PI system. 2. 7. Assigning Components for Outbound Transactions Procedure 1. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is available. All rights reserved. Assigning the Model for Outbound Transactions Procedure 1. 4. then click the Value List pull-down menu and select Value List <F4. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. Note If you have multiple ERP systems. Select the communication component name for the business system for Ariba Network. Generating the configuration objects. Ariba Network Adapter for SAP NetWeaver Setup Guide 366 © 2015 SAP SE or an SAP affiliate company. from the selection list and click Apply. 4. In the Connections from Component Assignment tab in the Configure Connection window. 5. In the Model Configurator.com Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company.com/xi/ASN/AddOn/PaymentRemittance Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba. 6. 2.com/xi/ASN/AddOn/ERPInvoice Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba. Configuring Sender and Receiver Relations for Individual Connections For Outbound Transactions Procedure 1. You must assign Communication Channels to set up the connections.com/xi/ASN/AddOn/PaymentProposal Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Proposal Name: CCT_AddOn_PaymentProposal_cXML_Receiver Namespace: http://ariba.com/xi/ASN/AddOn/GoodsReceipt Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Remittance Status Update Name: CCT_AddOn_PaymentRemittanceSUR_cXML_Receiver Namespace: http://ariba. Select the Communication Channel Templates for the following transactions: Buyer ○ Purchase Order Name: CCT_AddOn_PurchaseOrder_cXML_Receiver Namespace: http://ariba. 367 . click the Name field and then click the Display Input Help pull-down menu and select Input Help.com ○ Payment Remittance Name: CCT_AddOn_PaymentRemittance_cXML_Receiver Namespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittanceSUR Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba. 3.8. On the next page.com ○ CC Invoice Name: CCT_AddOn_CCInvoice_cXML_Receiver Namespace: http://ariba. click the empty Communication Channel cell corresponding to the business system for Ariba Network in the Receiver Business System Components table. All rights reserved. Click the Save Settings button. and then select Create Communication Channel with Template to start the Create Communication Channel wizard. click the Configure Connections button. Click Continue.com ○ Receipts Name: CCT_AddOn_GoodsReceipt_cXML_Receiver Namespace: http://ariba.com/xi/ASN/AddOn/PurchaseOrder Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba. Click the New Communication Channel button (the icon at the top left). com/xi/ASN/AddOn/StatusUpdateResponse_Receive Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba. 2. do the following: Ariba Network Adapter for SAP NetWeaver Setup Guide 368 © 2015 SAP SE or an SAP affiliate company. You can also choose to modify the channel names. In the Connections from Component Assignment tab. In the Create Configuration Object window.com/xi/ASN/AddOn/QuoteRequest Software Component Version: ARIBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba. ○ ServiceUpdateResponse ○ Name: CCT_AddOn_StatusUpdateResponse_cXML_Receive Namespace: http://ariba.com ○ Ship Notice Name: CCT_AddOn_Supplier_OutboundDeliveryNotification_cXML_Receiver Namespace: http://ariba. 11. and then click OK. click the Create Configuration Object button.com ○ Invoices Name: CCT_AddOn_Supplier_Invoice_cXML_Receiver Namespace: http://ariba. Click the Activate All Connections button. 10.com ○ QuoteRequest Name: CCT_AddOn_QuoteRequest_cXML_Receiver Namespace: http://ariba. Tip If you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba. Click on the Value List drop down and select Value List <F4. All rights reserved. you can create the communication channel by copying from a channel that has already been configured. 8. In the Model Configurator. Generate Objects for Outbound Transactions Procedure 1.com 7.com Supplier ○ Sales Order Confirmation Name: CCT_Supplier_SalesOrderConfirmation_cXML_Receiver Namespace: http://ariba. Click Finish. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . 9. 12. click the empty Communication Channel cell corresponding to the business system of your ERP PI system in the Receiver Business System Components table. Click Continue. Click the Save Settings button.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba. Select the CC_Proxy_Receiver communication channel from the selection list and click Apply.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba. click Apply to save the new configuration settings. 3. You can also simulate generation for test purposes. Click Start to begin generating objects. If they already exist. ○ ERP Invoice |< Name of the Business System for Ariba Network | CCT_ERPInvoice_cXML_Receiver under the AR_ERPInvoice_Receive Configuration Scenario. 5. Generating the objects creates the configuration objects if they do not yet exist. All rights reserved. ○ Payment Remittance Status |< Name of the Business System for Ariba Network | CCT_PaymentRemittanceSUR_cXML_Receiver under the AR_PaymentRemittanceSUR_Receive Configuration Scenario. and Interface Determination check boxes in the Scope of Generation section. ○ Click Generation in the General section. After the object generation is complete. ○ Payment Proposal |< Name of the Business System for Ariba Network | CCT_PaymentProposal_cXML_Receiver under the AR_PaymentProposal_Receive Configuration Scenario. they are reused and enhanced. ○ Select the Receiver Determination. You can save it. In the Communication Channel list. 369 . 4. if required. if required. Close the log that is created without saving. double-click the following communication channels to open it: Buyer ○ Purchase Order |< Name of the Business System for Ariba Network | CC_AddOn_PurchaseOrder_cXML_Receiver under the AR_AddOn_PurchaseOrder_Receive Configuration Scenario. ○ Payment Remittance |< Name of the Business System for Ariba Network | CCT_PaymentRemittance_cXML_Receiver under the AR_PaymentRemittance_Receive Configuration Scenario. ○ Status Update Response Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. Configuring Communication Channels for Outbound Transactions Procedure 1. ○ Goods Receipt |< Name of the Business System for Ariba Network |CC_AddOn_GoodsReceipt_cXML_Receiver under the AR_AddOn_GoodsReceipt_Receive Configuration Scenario. Click Create New in the Change List for Generated Objects section. The text box already contains an object name that you can use or modify. All rights reserved. 5. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . Under the cXML Configuration section. Supplier ○ Sales Order Confirmation |< Name of the Business System for Ariba Network | CC_AddOn_Supplier_SalesOrderConfirmation_cXML_Receiver under the AR_AddOn_Supplier_SalesOrderConfirmation_cXML_Receive Configuration Scenario. ○ Quote Request |< Name of the Business System for Ariba Network | CC_AddOn_QuoteRequest_cXML_Receiver under the AR_AddOn_QuoteRequest_Receive Configuration Scenario. Activating the Scenario for Outbound Transactions Procedure Using the Change List tab on the main application screen. For more information about the cXML Adapter parameters.for example. set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. ○ Ship Notice |< Name of the Business System for Ariba Network | CC_AddOn_Supplier_OutboundDeliveryNotification_cXML_Receiver under the AR_AddOn_OutboundDeliveryNotification_cXML_Receive Configuration Scenario ○ Invoice |< Name of the Business System for Ariba Network | CC_AddOn_Supplier_Invoice_cXML_Receive under the AR_AddOn_Supplier_Invoice_cXML_Receive Configuration Scenario 2. Note If you created the channel by copying from an existing channel. |< Name of the Business System for Ariba Network | CC_AddOn_StatusUpdateResponse_cXML_Receiver under the AR_AddOn_StatusUpdateResponse_Receive Configuration Scenario. Update the cXML version parameter to the latest applicable version. In the Parameters tab. you must change the request type for each of the transactions to the <Name of the transaction request . If required. see cXML Adapter Parameters [page 391] 4. Save the changes. edit the other parameters. 3. activate all the change lists containing the objects created and modified during the component setup. 6. Ariba Network Adapter for SAP NetWeaver Setup Guide 370 © 2015 SAP SE or an SAP affiliate company. select the Use SAP Add on Suite check box. PaymentProposalRequest> in the Outbound Request Type field. Document Routing Mechanism If you have multiple ERP systems. The required configuration sections will not be available for accounts that have not been enabled. each of the SAP ERP systems involved in the integration is identified by a unique identifier. you can link them to a single Ariba Network account. This identifier. it is located in the To element. This section describes the following topics: ● The mechanisms involved in the documents routing ● The configuration to setup integration with Ariba Network of multiple SAP ERP instances. called the SystemID. it is located in the From element ● For inbound documents. corresponds to the logical system ID of the concerned SAP ERP instance. This allows all the documents from particular vendors to be routed to a single Ariba Network account and in the reverse direction.13. All rights reserved.10. Each document that passes through the integration will be transformed as follows. Linking Multiple SAP Instances with Ariba Network If your organization has more than one instance of SAP. to include or to retrieve this unique identifier from the cXML header: <cXML payloadID="[email protected]" timestamp="2007-05-09T05:01:57-07:00"> <Header> <From> <Credential domain="NetworkID"> <Identity>AN50000000365</Identity> </Credential> <Credential domain="PrivateID"> <Identity>0000009999</Identity> </Credential> </From> <To> <Credential domain="NetworkID"> <Identity>AN51000000349</Identity> </Credential> <Credential domain="SystemID"> <Identity>T90CLNT090</Identity> </Credential> </To> Depending on the direction. the documents from Ariba Network will be routed to a particular SAP ERP instance. 371 . the SystemID identifier is located in different locations: ● For outbound documents.Results This completes the configuration of the outbound transactions in SAP NetWeaver PI. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. Buying organization or service provider accounts must be enabled for multiple ERP systems by Ariba Network Support. All rights reserved. SAP NetWeaver PI and Ariba Network. Ariba Network Adapter for SAP NetWeaver Setup Guide 372 © 2015 SAP SE or an SAP affiliate company. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . the SAP Suite Add-On always sends the SystemID in ERP- outbound cXML documents.When you have multiple ERP systems. The following figure shows the SystemID identifier location in outbound documents at the top and in inbound documents at the bottom. the SystemID identifier is not inserted in the outgoing documents or expected in the incoming documents. Figure 2: SystemID identifier location in the message exchanges Multi-ERP Configuration The multi-ERP implementation requires configuration on all three sides: SAP ERP. However. use a valid XPath Expression / p1. you must configure a content-based routing in PI for the cXML attributes. 373 . Note When you configure your SAP Suite Add-On to support multiple instances of SAP. see Defining the Technical System for SAP ERP [page 353] and Defining the Business System for SAP ERP [page 354]. in Chapter 4 “Configuration”. Fore more information on Ariba Network setup. Note Buying organization or service provider accounts must be enabled for Multi-ERP implementation by Ariba Network Support. Configuring Integration Scenarios The integration scenarios in the Integration Directory need to be parameterized in order to have the information on the systems and enable message routing. Configuring Ariba Network You must configure Ariba Network with the information about all the instances of SAP ERP involved in the integration and link it with the Ariba Network buyer account.cXMLMessage/cXMLMessageContent/cXML that you insert manually in the Receiver Determination. To do this. of the Ariba Network Integration Guide. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. For more information. All rights reserved. see the “Linking Multiple Business Applications” section. see the Configuring SAP ERP Connectivity [page 355] section. For more information. The required configuration sections is not available for accounts that have not been enabled.Configuring the System Landscape Directory You must configure all your SAP ERP instances in the SLD as Technical and Business Systems. Configuring SAP ERP Connectivity The connectivity between all the SAP ERP instances and the SAP NetWeaver PI server has to be setup. The adapter maintains a profile cache that is updated every time the Profile transaction runs. it responds with a synchronous cXML document that contains one of the following status codes: ● 2xx. All rights reserved. the Ariba cXML Solutions Guide and the sample mapping tables. Profile Transaction When the cXML Adapter sends a ProfileRequest to Ariba Network. Note that there is no corresponding OrderResponse document. indicating that a transient error occurred. The Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On then re-sends the document with the same payload ID for the specified number of retry attempts. The remainder of this section discusses the transactions on a general level as they pertain to the Ariba Network Adapter for SAP NetWeaver. indicating that Ariba Network accepted the document. The cXML Adapter decodes the response to extract URLs for the various transactions and stores the values so that they can be used in subsequent transactions. ● 4xx. ● 5xx. Ariba Network then routes the purchase order to the appropriate supplier using the supplier’s preferred order routing method. the cXML Adapter runs the Profile transaction as a scheduled task every 24 hours. Ariba Network Adapter for SAP NetWeaver Setup Guide 374 © 2015 SAP SE or an SAP affiliate company. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On .Supported cXML Transactions The Ariba Network Adapter for SAP NetWeaver supports the following cXML transactions: ● OrderRequest ● ConfirmationRequest ● ShipNoticeRequest ● InvoiceDetailRequest ● StatusUpdateRequest For more detailed information about these transactions. see the cXML User’s Guide. Instead. the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On sends the cXML OrderRequest to Ariba Network. Ariba Network transmits a generic response. This interval can be configured at runtime. When the adapter sends an OrderRequest document to Ariba Network. it responds with a ProfileResponse indicating the cXML documents that it accepts and their respective URLs. indicating that a permanent error has occurred and has been logged. Purchase Order When a buying organization requests products or services through its SAP ERP system. By default. paying. You can also view the log files in the adapter log directory on SAP NetWeaver PI. Testing the SAP NetWeaver for Suite Add-On Configuration This section provides instructions for how to test your configuration. see Chapter 4.Invoice Invoices. Buyers send StatusUpdateRequest documents to set invoice status to processing. rejected. you must run test transactions to ensure that Ariba Network and your SAP ERP system are communicating properly in both directions. “Configuration” in the Ariba Network Integration Guide. InvoiceUpdateRequest documents can identify invoices in two possible ways: through either a DocumentReference or an InvoiceIDInfo element. and ship notices are downloaded by the cXML Adapter from Ariba Network using the pull document transmission methods described in cXML Adapter Parameters [page 391]. 375 . see the Understanding Error Handling [page 376] section. For more information about error handling. Before beginning. Invoice Status Update Invoice status updates are sent by buying organizations to inform Ariba Network and suppliers of the status of invoice reconciliation. paid. To troubleshoot any errors you encounter. see the Ariba Network Integration Guide. For more information about creating a supplier relationship. For more information. ● Run a getPending transaction by creating an invoice in Ariba Network and then sending it to your SAP Suite Add-On. see the Ariba cXML Solutions Guide. For more information about invoice status updates. Ariba Network posts the documents to the URL that suppliers return in their cXML ProfileResponse. you can use the PI Runtime Work Bench (from the web UI) and the Integration Engine Monitor (transaction SXMB_MONI from the SAP GUI) to track the exchanged messages. reconciled. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. Testing Processes After you have successfully deployed and configured the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On. be sure that you have at least one fully configured Ariba Network supplier relationship. All rights reserved. order confirmations. To test processes: ● Send a Purchase Order from your SAP Suite Add-On to Ariba Network. or invalid. In your SAP ERP system which has the SAP Suite Add-On installed. then the OrderRequest cXML is sent to SAP NetWeaver PI as the SAP Suite Add- On enables cXML from SAP ERP. The Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On on SAP NetWeaver PI then sends the XML message to Ariba Network. Understanding Error Handling The PI Runtime Work Bench and the Integration Engine Monitor (transaction SXMB_MONI) are used to track error messages and email notifications. Running a getPending Transaction for Testing Procedure 1. the inbound connection is working properly. 2. If it can be found in supplier's inbox. Verify that the messages are available in the SAP NetWeaver PI monitoring tools (PI Runtime Workbench and Integration Engine Monitor). Ariba Network Adapter for SAP NetWeaver Setup Guide 376 © 2015 SAP SE or an SAP affiliate company. create a purchase order.Sending a Purchase Order for Testing Procedure 1. If the system is working properly. and to notify users about errors in inbound processing (getPending transaction). Check to see that the invoice is created in your SAP ERP system. 3. All rights reserved. If the system is working properly. 3. Results If these two checks are successful. The following describe the error handling on the Integration server side: ● For simple transactions like Invoice: If an error occurs in the processing. Check to see that the new order is displayed in the inbox of the supplier. the message is logged as an error in the SXMB_MONI. Create a test invoice in Ariba Network. Verify that the messages are available in the SAP NetWeaver PI monitoring tools (PI Runtime Workbench and Integration Engine Monitor). 2. then the cXML Adapter downloads the Invoice from Ariba Network and sends the cXML to SAP ERP. and can be restarted (reprocessed). Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . Log on to Ariba Network as the supplier. the outbound connection is working properly. in the case of a connection issue there is no message. just a technical error in the communication layer. The adapter also sends an Email Notification in this case. The status code range 2xx denotes success.The following describe the error handling on the Adapter Engine side: ● For inbound messages (AN-> ERP). PI is not aware of any message. and 5xx denotes transient errors. In this case. see the Protocol Specification > Response section of Chapter 2 “cXML Basics” in the cXML User’s Guide. and if any exception occurs. Understanding Error and Status Codes The cXML Adapter notification emails include an Ariba Network Adapter for SAP NetWeaver error code. The response status code refers to the cXML error/status codes received from the server. The message can be resent for processing manually (in addition to the retry mechanism implemented by PI). in case of documents refused by Ariba Network). the Email notification is used to send an email when an error occurs (mainly connection issues). the adapter logs a detailed message. The following table describes the possible general error codes (Ariba Network Adapter for SAP NetWeaver error codes) in cXML adapter notifications: Table 2: Application Errors: Status Text Invalid Configuration Parameter. All rights reserved. transient errors. and a response status code.) ● For outbound messages (R3 -> ERP). Incorrect Client Certification ERR102 Authentication Failed on ASN ERR201 ASN Internal Server Error ERR202 Send cXML to AN Failed (Invalid Request) ERR203 Send cXML to AN Failed (Temporary Error) ERR204 Send cXML to AN Failed (Unrecoverable Error) ERR205 Get Profile Transaction Failed ERR301 Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. the sending operation initiated by PI is synchronous. which can be viewed with the RuntimeWork Bench. it is related to a message from PI. except that the message is more precise and includes the response from Ariba Network. For more information about the different cXML status codes that can be found in the notification emails. Trusted certificates not installed ERR101 properly. The email notification is identical. This is because during the pull (getPending). or permanent errors. (For example. if available (for example. The cXML status codes indicate success. 4xx denotes permanent errors. 377 . For a list of general error codes.Status Text Get Pending Transaction Failed ERR302 Outbound Transaction Failed ERR303 Invalid Outbound Message (PI -> ASN) ERR401 Invalid Inbound Message (ASN -> PI) ERR402 Duplicate Outbound Message ERR403 Duplicate Inbound Message ERR404 Outbound Message Type Inconsistent with Channel Definition ERR405 Inbound Message Type Inconsistent with Channel Definition ERR406 Can not find corresponding record in download config file ERR407 Table 3: Runtime Error: Status Text ERR501 Unexpected Error Table 4: ERP Errors: Status Text Configuration Load Failed ECC101 IO Error ECC102 Ariba Network Not Available ECC103 Understanding Email Notifications The following are the different parts of an error notification email: ● Date: The date and time of the error. and ERP Errors tables in the previous section. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . Ariba Network Adapter for SAP NetWeaver Setup Guide 378 © 2015 SAP SE or an SAP affiliate company. Runtime Error. All rights reserved. see the Application Errors. ● Error: The Ariba Network Adapter for SAP NetWeaver Error code. if the adapter stops downloading invoices from Ariba Network. the channel stops to run as indicated by the status on the user interface and no invoices are downloaded. ● [TimeStamp/PayloadID]: The timestamp and the payload of the response document. untrusted. like Unauthorized. like https://sevice. ● Transaction: The channel name corresponding to the transaction in which the error occurred.61. ● [Response Status Code]: The cXML response status code. An SAP NetWeaver administrator can start or stop channels from the Runtime Workbench as required without having the need to access the Integration Directory. All rights reserved.ariba. For a list of possible status messages. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. ● [Request URL]: The URL used for the request that failed. which can be one of the following: ○ A stack trace with the exception. For example. ● [Response Status Text]: The text corresponding to the cXML response status code. communication channels are created for each inbound and outbound transaction in the Integration Directory. the NetWeaver administrator needs to login to the Runtime Workbench and stop/start the respective channel.asp. the following sections will be available. These communication channels are displayed within the Runtime Workbench from where an SAP NetWeaver administrator can monitor these channels. if an administrator stops an inbound channel that downloads invoices from the Ariba Network. Monitoring the cXML Adapter from Runtime Workbench After you deploy the Ariba Network Adapter for SAP NetWeaver on SAP NetWeaver PI and configure the inbound and outbound transaction scenarios in the Integration Directory. Note If the cXML Adapter stops downloading documents from Ariba Network.126.com/service/ transaction/cxml. like 2007-09-04T17-23-29-07:00/1188951809740_498019780@10. like [CC_Invoice_cXML_Sender].10. like InvoiceDetailRequest/InvoiceDetailRequest. Please contact customer support with the Error Reference Number: ANERR-10000000000000000000972190 for more details. see the Protocol Specification > Response section of Chapter 2 “cXML Basics” in the cXML User’s Guide. 379 . an administrator must login to the Runtime Workbench and start the invoice communication channel to ensure that the adapter starts downloading invoices. In this case.● Error Detail: The error detail. if the request failed to reach Ariba Network. like 401. ● [Request Name/Type]: The name of the request and the type related to the transaction with the error. The problem could be one of the following: ○ Invalid. or no certificate ○ Posting to the wrong URL when your account is configured for certificate-based authentication. ● [Response Status Desc]: The cXML response description “Error:Invalid sender credentials”. if the response from Ariba Network contains an error code. and the response message from Ariba Network is not available ○ Details of the cXML response. For example. All rights reserved. see the SAP NetWeaver PI documentation. Go to (http://connect. For more information. SAP NetWeaver PI Integration Builder contains two parts: ● Design tool. Each tpz file works as a single unit within SAP NetWeaver PI Integration Builder. if you have multiple namespaces within a single Design tpz file. the Ariba Network Adapter for SAP NetWeaver is Ariba Network-certified. click Product Info Ariba Network Ariba Network.zip file. For example. 2. which contains interface objects and integration processes ● Configuration tool. 3. For more information about the certification process. and its connection to Ariba Network. Ariba Network Adapter for SAP NetWeaver Setup Guide 380 © 2015 SAP SE or an SAP affiliate company. click Supplier Connectivity to download the Supplier Connectivity. mapping objects and interface objects. see the Ariba Network Integration Guide. The design tpz file can contain one or more namespaces. Ariba Network Certification Ariba must certify any Ariba Network Adapter for SAP NetWeaver that works with Ariba Network. you must perform certification testing again to ensure that all processes work as expected. which contains business services and routing rules. Under Documentation in the new page.com ) and log in. which includes business services and routing rules. see the SAP NetWeaver PI documentation. The guide describes how to download certification files from Connect and provides instructions to guide you through the certification process.ariba. assuming that no other conditions are specified for these namespaces. You can build as many tpz files as you need for one project. For more information about how to export a tpz file. On the navigation panel on the left. Certification is the process by which Ariba’s Global Solutions Organization (GSO) inspects and approves the Ariba Network Adapter for SAP NetWeaver. Downloading the Ariba Network Integration Guide from Connect: Procedure 1. Once you have customized data mappings. the cXML documents it generates. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . which include the integration processes. all the namespaces will be imported and exported at the same time.Deploying the Project When you have customized your data mappings and tested all processes. you are ready to export and then import the project as two SAP NetWeaver PI Export files (tpz files) using SAP NetWeaver PI Integration Builder. The Configuration tpz file can contain one configuration scenario. In its default state. JPEG. Ariba Network supports attachments for the following transactions: ● Purchase Order ● Invoice ● Ship Notice ● Order Confirmation Limitations for Attachments The size of the attachments for both inbound and outbound documents cannot exceed 100 MB. the attachments are part of the Comments element in the cXML file as shown below: <Comments> <Attachment> <URL>Content ID of the Attachment</URL> </Attachment> </Comments> The attachment is embedded in the message sent from SAP Suite Add-On as a Base 64 string.TXT. To attach external files to a cXML document in a single envelope. which includes catalog files as attachments. The cXML document contains references to external parts sent within a multipart MIME envelope.pdf file from the downloaded ZIP file. decodes and adds the attachment to the MIME message. or faxes.4. and so on. . For example. All rights reserved. see the cXML User’s Guide and cXML Solutions Guide. Files referenced by cXML documents can reside either on a server accessible by the receiver or within an envelope that also includes the cXML documents themselves. use Multipurpose Internet Mail Extensions (MIME). Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. Another example is the CatalogUploadRequest document.. Attachments in cXML can be of any file type.PDF. Extract the IntegrationGuide. Attachments for Outbound Documents When an outbound document (purchase order) is sent from SAP Suite Add-On to the cXML Adapter with attachments. Enabling Support for Attachments Attachments Support in cXML The cXML protocol supports the attachment of external files of any type to cXML documents. and sends the MIME message to Ariba Network. The cXML Adapter converts the incoming message into a MIME message. .DOC. drawings. For more information about attachments. buyers sometimes need to clarify purchase orders with supporting memos. such as . 381 . Ariba Network either forwards the attachments to the respective suppliers or stores these attachments to allow online access for suppliers. All rights reserved. As part of this functionality. encodes the attachments. Ariba Network adds these attachments to a mime message and sends the MIME message to the cXML Adapter for further processing. and adds the attachments to the converted message. supporting memos. For information about configuring endpoints for integration. fax. it receives the attachments as part of a MIME message. SAP NetWeaver PI provides functionality to manage and administer authentication certificates and keystores. Using the SAP NetWeaver PI KeyStore The server and client certificates that cXML Adapter uses to connect to Ariba Network must be stored in the SAP NetWeaver PI keystore. the cXML Adapter supports attachments of all file types that are supported by Ariba Network. The cXML Adapter converts the cXML message to a message format that SAP Suite Add-On expects. Using Endpoints for Integration with SAP NetWeaver for SAP Suite Add-On The endpoints in Ariba Network manage and control the flow of data from Ariba Network to the various systems that are connected to it. Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On . The converted message is sent to SAP Suite Add-On through SAP NetWeaver PI. you can create keys and certificates in SAP NetWeaver and store them in the SAP NetWeaver PI Keystore.Purchase Orders with Attachments A purchase order (PO) document can have multiple attachments. you must get them signed by a trusted Certificate Authority (CA) to enable Ariba Network to successfully establish the SSL connection. or ASN) with attachments from Ariba Network. emails. see Using Endpoints for Integration [page 229]. and so on. Attachments for Inbound Documents Invoices with Attachments An invoice can have multiple attachments such as delivery details. The keys and certificates that you create in SAP NetWeaver Keystore are grouped bases on views. After you have created the required certificates. OC. Therefore. You can create endpoints in Ariba Network according to your business requirements. When Ariba Network receives a PO with attachments. images. These stored attachments expire after 180 days and are not available online thereafter. For inbound documents. you first need to create a view and then create the required keys and certificates under that view. and so on. The endpoint in Ariba Network acts as a document routing placeholder that ensures documents from Ariba Network are sent to the desired system. such as product specifications. Ariba Network Adapter for SAP NetWeaver Setup Guide 382 © 2015 SAP SE or an SAP affiliate company. When the cXML Adapter downloads an inbound document (invoice. Repeat this configuration for all the inbound and outbound transactions. To use client certificate for authentication to Ariba Network buyer account. for Trust Store View and KeyStore View (only if you are using client certificate). Under Authentication. for the Trust Store View parameter. the cXML Adapter initializes and creates the Ariba Network TrustStoreView and KeystoreView (only if client certificate is selected) and uses the certificates to ensure a successful SSL handshake. For more information. based on the channel configuration. Requirements In the communication channel for all the inbound and outbound transactions. enter the name of the view that contains the server certificate. 2. Open the required communication channel. enter the name of the view that contains the client certificate. 3. 4. for Credential Mode. when SAP NetWeaver PI sends or receives documents to/from Ariba Network. Configuring Communication Channels to Use SAP NetWeaver PI Keystore Procedure 1. All rights reserved. specify the names of the Views that store the Server certificate and Client certificate respectively. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On © 2015 SAP SE or an SAP affiliate company. 5. see Configuring Communication Channels to Use SAP NetWeaver PI Keystore [page 383]. For the KeyStore View parameter.As a result. select Client certificate from the drop-down list. 6. Click Save. 383 . Testing the Adapter . 2. Ariba Network Adapter for SAP NetWeaver Setup Guide 384 © 2015 SAP SE or an SAP affiliate company. All rights reserved. For more information about creating a supplier relationship.Testing the Adapter Testing the Configuration [page 384] Monitoring of the cXML Adapter [page 388] Deploying the Project [page 389] Testing the Configuration This section provides instructions on how to test your configuration. Testing Processes After you have successfully deployed and configured the Ariba Network Adapter for SAP NetWeaver. you should run test transactions to ensure that Ariba Network and your SAP ERP system are communicating properly in both directions. Before beginning. and then sends the cXML to Ariba Network. For more information about error handling. see the “Configuration” topic in the Ariba Network Integration Guide. Sending a Purchase Order for Testing Procedure 1. If the system is working properly. ● Run a getPending transaction by creating an invoice in Ariba Network and then sending it to your SAP system. To troubleshoot any errors you encounter. To test processes: ● Send a purchase order from your SAP system to Ariba Network. then the Purchase Order IDoc message is sent to SAP NetWeaver PI. In your SAP ERP system. Verify that the messages are available in the PI monitoring tools (PI Runtime Workbench and Integration Engine Monitor). you can use the PI Runtime Work Bench (from the web UI) and the Integration Engine Monitor (transaction SXMB_MONI from the SAP GUI) to track the exchanged messages. create a purchase order. You can also view the log files in the adapter log directory on SAP NetWeaver PI. see the “Understanding Error Handling” [page 385] section. be sure that you have at least one fully configured Ariba Network supplier relationship. The Ariba Network Adapter for SAP NetWeaver on SAP NetWeaver PI converts the IDoc to cXML. and can be restarted (reprocessed). (For example. just a technical error in the communication layer. the problem must be fixed. and if an error occurs. 3. Verify that the messages are available in the PI monitoring tools (PI Runtime Workbench and Integration Engine Monitor). and if any exception occurs. the outbound connection is working properly. 3. The message can be resent for processing manually (in addition Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter © 2015 SAP SE or an SAP affiliate company. Log on to Ariba Network as the supplier. 2. Create a test invoice in Ariba Network. in the case of a connection issue there is no message. and to notify users about errors in inbound processing (getPending transaction). In this case. the inbound connection is working properly. the sending operation initiated by PI is synchronous. it is related to a message from PI. The following describe the error handling on the adapter engine side: ● For inbound messages (AN-> ERP).) ● For outbound messages (ERP -> AN). which can be viewed with the RuntimeWork Bench. the message is logged as an error in the SXMB_MONI. PI is not aware of any message. then the Ariba Network Adapter for SAP NetWeaver downloads the Invoice from Ariba Network. This is because during the pull (getPending). Results If these two checks are successful. or a data retrieving error (RFC calls) occurs. it is logged in SXMB_MONI. this guarantees that the messages are processed only once. ● For complex/scheduled transactions (Receipt/PaymentProposal/InvoiceStatusUpdate): Messages are processed in batches. Understanding Error Handling The PI Runtime Work Bench and the Integration Engine Monitor (transaction SXMB_MONI) are used to track error messages and email notifications. Check to see that the new order is displayed in the inbox of the supplier. the adapter logs a detailed message. the processing is stopped with the timestamp of the last successfully processed message. Running a getPending Transaction for Testing Procedure 1. If it can be found in supplier's inbox. 385 . and then sends the IDoc to SAP ERP. the Email notification is used to send an email when an error occurs (mainly connection issues). All rights reserved. If the system is working properly. The following describe the error handling on the Integration server side: ● For simple transactions like Invoice: If an error occurs in the processing. converts the cXML to IDoc. Check to see that the invoice is accepted in your SAP ERP system. or if a mapping error. In this case. see the Protocol Specification > Response section of Chapter 2 “cXML Basics” in the cXML User’s Guide. to the retry mechanism implemented by PI). Incorrect Client Certification ERR102 Authentication Failed on ASN ERR201 ASN Internal Server Error ERR202 Send cXML to AN Failed (Invalid Request) ERR203 Send cXML to AN Failed (Temporary Error) ERR204 Send cXML to AN Failed (Unrecoverable Error) ERR205 Get Profile Transaction Failed ERR301 Get Pending Transaction Failed ERR302 Outbound Transaction Failed ERR303 Invalid Outbound Message (PI -> ASN) ERR401 Ariba Network Adapter for SAP NetWeaver Setup Guide 386 © 2015 SAP SE or an SAP affiliate company. Understanding Error and Status Codes The cXML Adapter notification emails include an Ariba Network Adapter for SAP NetWeaver error code. The email notification is identical. except that the message is more precise and includes the response from Ariba Network. and a response status code. The response status code refers to the cXML error/status codes received from the server. The status code range 2xx denotes success. For more information about the different cXML status codes that can be found in the notification emails. if available (for example. The cXML status codes indicate success. Trusted certificates not installed ERR101 properly. in case of documents refused by Ariba Network). The following table describes the possible general error codes (Ariba Network Adapter for SAP NetWeaver error codes) in cXML adapter notifications: Table 5: Application Errors: Status Text Invalid Configuration Parameter. and 5xx denotes transient errors. transient errors. The adapter also sends an Email Notification in this case. Testing the Adapter . All rights reserved. or permanent errors. 4xx denotes permanent errors. ● Error: The Ariba Network Adapter for SAP NetWeaver Error code. For a list of general error codes. the following sections will be available. if the response from Ariba Network contains an error code. Status Text Invalid Inbound Message (ASN -> PI) ERR402 Duplicate Outbound Message ERR403 Duplicate Inbound Message ERR404 Outbound Message Type Inconsistent with Channel Definition ERR405 Inbound Message Type Inconsistent with Channel Definition ERR406 Can not find corresponding record in download config file ERR407 Table 6: Runtime Error: Status Text ERR501 Unexpected Error Table 7: ERP Errors: Status Text Configuration Load Failed ECC101 IO Error ECC102 Ariba Network Not Available ECC103 Understanding Email Notifications The following are the different parts of an error notification email: ● Date: The date and time of the error. see the Application Errors. ● Error Detail: The error detail. ● Transaction: The channel name corresponding to the transaction in which the error occurred. In this case. like [CC_Invoice_cXML_Sender]. All rights reserved. if the request failed to reach Ariba Network. which can be one of the following: ○ A stack trace with the exception. Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter © 2015 SAP SE or an SAP affiliate company. and ERP Errors tables in the previous section. 387 . Runtime Error. and the response message from Ariba Network is not available ○ Details of the cXML response. like 2007-09-04T17-23-29-07:00/[email protected]. an administrator must login to the Runtime Workbench and start the invoice communication channel to ensure that the adapter starts downloading invoices.126.61. or no certificate ○ Posting to the wrong URL when your account is configured for certificate-based authentication. like InvoiceDetailRequest/InvoiceDetailRequest.com/service/ transaction/cxml. The problem could be one of the following: ○ Invalid. if a channel stops or is stuck in processing. the monitoring capability checks the status of the invoice channel. Testing the Adapter . For example. if invoices are not getting downloaded from Ariba Network.● [Request Name/Type]: The name of the request and the type related to the transaction with the error. the monitoring capability restarts the channel to ensure that the adapter can continue to download invoices from Ariba Network. the NetWeaver administrator needs to login to the Runtime Workbench and stop/start the respective channel. For example. Monitoring of the cXML Adapter The monitoring of the cXML Adapter includes a monitoring capability that continuously monitors the status of the deployed inbound and outbound channels (transactions). ● [Response Status Text]: The text corresponding to the cXML response status code. For example. if the adapter stops downloading invoices from Ariba Network. communication channels are created for each inbound and outbound transaction in the Integration Directory.10. Note If the cXML Adapter stops downloading documents from Ariba Network. ● [Response Status Desc]: The cXML response description “Error:Invalid sender credentials”. As part of this implementation. All rights reserved. like 401. like https://sevice. If the channel has stopped or is stuck in processing. An SAP NetWeaver administrator can start or stop channels from the Runtime Workbench as required without having the need to access the Integration Directory. Monitoring the cXML Adapter from Runtime Workbench After you deploy the Ariba Network Adapter for SAP NetWeaver on SAP NetWeaver PI and configure the inbound and outbound transaction scenarios in the Integration Directory. see the Protocol Specification > Response section of Chapter 2 “cXML Basics” in the cXML User’s Guide.ariba. like Unauthorized. ● [TimeStamp/PayloadID]: The timestamp and the payload of the response document. Please contact customer support with the Error Reference Number: ANERR-10000000000000000000972190 for more details. ● [Response Status Code]: The cXML response status code. if an administrator stops an inbound channel that downloads invoices from the Ariba Network. Ariba Network Adapter for SAP NetWeaver Setup Guide 388 © 2015 SAP SE or an SAP affiliate company. untrusted. These communication channels are displayed within the Runtime Workbench from where an SAP NetWeaver administrator can monitor these channels. ● [Request URL]: The URL used for the request that failed. the monitoring capability of the adapter is notified and it automatically restarts that channel without any manual intervention. For a list of possible status messages. the channel stops to run as indicated by the status on the user interface and no invoices are downloaded. and its connection to Ariba Network. You can build as many tpz files as you need for one project. see the Ariba Network Integration Guide.zip file.ariba. see the SAP NetWeaver PI documentation. For more information about how to export a tpz file. The guide describes how to download certification files from Connect and provides instructions to guide you through the certification process. All rights reserved. mapping objects and interface objects. you must perform certification testing again to ensure that all processes work as expected. all the namespaces will be imported and exported at the same time.Deploying the Project When you have customized your data mappings and tested all processes.com ) and log in. mapping objects and integration processes ● Configuration tool. the cXML documents it generates. 2. 3. On the navigation panel on the left. Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter © 2015 SAP SE or an SAP affiliate company. For more information. The design tpz file can contain one or more namespaces. which contains business services and routing rules. Downloading the Ariba Network Integration Guide from Connect Procedure 1. 389 . which contains interface objects. click Product Info Ariba Network Ariba Network. which include the integration processes. the Ariba Network Adapter for SAP NetWeaver is Ariba Network-certified. which includes business services and routing rules. Under Documentation in the new page. SAP NetWeaver PI Integration Builder contains two parts: ● Design tool. Go to (http://connect. For example. The Configuration tpz file can contain one configuration scenario. Certification is the process by which Ariba’s Global Solutions Organization (GSO) inspects and approves the Ariba Network Adapter for SAP NetWeaver. For more information about the certification process. Each tpz file works as a single unit within SAP NetWeaver PI Integration Builder. In its default state. Once you have customized data mappings. you are ready to export and then import the project as two SAP NetWeaver PI Export files (tpz files) using SAP NetWeaver PI Integration Builder. click Supplier Connectivity to download the Supplier Connectivity. assuming that no other conditions are specified for these namespaces. if you have multiple namespaces within a single Design tpz file. see the SAP NetWeaver PI documentation. Ariba Network Certification Ariba must certify any Ariba Network Adapter for SAP NetWeaver that works with Ariba Network. Extract the IntegrationGuide. Testing the Adapter .4. All rights reserved.pdf file from the downloaded ZIP file. Ariba Network Adapter for SAP NetWeaver Setup Guide 390 © 2015 SAP SE or an SAP affiliate company. This parameter is only required when Secret Password parameter credentialMode is set as Shared secret. inbound. Status required string Active/ Default value: Active Inactive Authentication Authentication method on Ariba Network. Common Parameters [page 391] Inbound Parameters [page 393] Outbound Parameters [page 395] Configuring Retry Attempts [page 395] Configuring Proxy Server Parameters [page 395] Common Parameters Parameter Name Usage Type Data Type Value Description Adapter Status Deployment mode of the adapter. depending on the credential domain selected. 391 . The Buyer's shared secret on Ariba Net­ Shared optional string work. Credential required string The value can be NetworkId. Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters © 2015 SAP SE or an SAP affiliate company. All rights reserved. Credential required string NetworkId/ Default value: NetworkId Domain NetworkUserI d/DUNS The Buyer's credential on Ariba Network. Mode required string Test/ Default value: Test Production The status of the adapter. Credential required string Shared Default value: Client certificate Mode secret/ Client certificate The domain for the Buyer's credential. NetworkUserId or DUNS. and outbound parameters for the cXML Adapter.cXML Adapter Parameters This section describes common. 018 or data definition to be used to generate the Version higher cXML documents exchanged with Ariba Network. A flag that specifies whether or not the vali­ Use XML optional boolean true/false dation is done on the exchanged cXML Validation documents according to the cXML dtds. This version number will be used in the DOCTYPE entity of the cXML docu­ ments. You can set a minimum value of one hour and the maximum value as 360 hours. cXML Configuration Ariba Network ID.2. All rights reserved. Specify the expiry time for a document in documentExp required integer minimum 1 hours after which the document can be re­ iryPeriod and max 360 sent from or to Ariba Network . In the production phase. Default value: 443 Indicates the name of the view that contains KeyStore required string all the keys/certificates required for authen­ View tication between the cXML Adapter and Ariba buyer. AN ID required string Default value: AN01000000001 A textual string representing the client sys­ User Agent required string tem that is conducting the cXML conversa­ tion. Email Notification Ariba Network Adapter for SAP NetWeaver Setup Guide 392 © 2015 SAP SE or an SAP affiliate company. Default value: Ariba SN Buyer Attribute needed for constructing cXML re­ Language required string en-US quest. When this option is enabled. The validation should be enabled during the in­ stallation/ customization phase to ensure that the exchanged cXML documents are compliant. the cXML Use SAP required boolean Adapter integrates Ariba Network with the Add on Suite SAP Suite AddOn component available in your SAP ERP system. Default value: en-US Base directory needed to run the adapter.Parameter Name Usage Type Data Type Value Description HTTPS port. Data required string Default value: D:/AribaDataDir Directory The version number of the cXML document cXML required string 1. the vali­ dation could have a negative impact on per­ formance. cXML Adapter Parameters . This parameter is only required Port required integer when parameter credentialMode is set as Client certificate. The default value is 24 hours. All rights reserved. Default value: false The email sender account. This parameter is User optional string only required when parameter emailAuthentication is set as true. The password for the email sending ac­ Password optional string count. Sender Name required string Default value: AribaSN Adapter Admin A flag that represents whether or not the Email required boolean true/false email server requires authentication for Authenticat ion sending email. Recipient required string Address The email account for email cc receiver. Use Email required boolean true/false Default value: false Notificatio ns The SMTP server IP address or host name.com/ service/transaction/ cxml. Inbound Parameters Parameter Usage Type Data Type Value Description Name cXML Configuration URL used to send ProfileRequest. CC Address optional string The description name for sender. Sender required string Address The email account for email receiver.ariba. SMTP required string Server Host The email account for sending email. This parameter is only required when parameter emailAuthentication is set as true.asp Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters © 2015 SAP SE or an SAP affiliate company. Parameter Name Usage Type Data Type Value Description A switch to turn on/off email notification. GetProfil required string Default value: https:// e URL certservice. 393 . the cXML adapter will wait for the number of minutes specified as the value for this parameter before ex­ iting. When the cXML Adapter is download­ Timeout required intege 5 minutes ing documents from Ariba Network. Inbound Request Type One of the following: The request type for Inbound. nt Default value: 0 Time to wait before sending the next StatusUpd required intege status update. ateReques r tRetryInt Default value: 0 erval (Minutes) The system ID for your ERP appli­ This parameter is required only if you SystemID optional string cation are using multiple ERP applications to for GetPendin connect to Ariba Network g The system ID for your ERP system must match the system ID configured in your Ariba Network buyer account. cXML Adapter Parameters . g r Interval Default value: 15 (Minutes) Max number of Documents that can Max required intege be received from the pending queue in Documents r in a single getPending request. All rights reserved. Inbound required string Default value: Request ConfirmationRequest ConfirmationRequest Type InvoiceDetailRequest ShipmentNoticeRequest PayMeNowRequest Ariba Network Adapter for SAP NetWeaver Setup Guide 394 © 2015 SAP SE or an SAP affiliate company. GetPendin Default value: 2 g Number of times the status update re­ StatusUpd required intege quest is to be retried if the first status ateReques r tRetryCou update request failed. e r Interval Default value: 60 (Minutes) Poll interval of getPendingRequest ex­ GetPendin required intege pressed in minutes. if r the connection is lost during the download. expressed in minutes.Parameter Usage Type Data Type Value Description Name Poll interval of profileRequest ex­ GetProfil required intege pressed in minutes. see the SAP NetWeaver Process Integration 7.ariba. Outbound required string Default value: OrderRequest Request Type OrderRequest ChangeOrderReques t InvoiceUpdateRequ est PaymentRequest PaymentRemittance Request Configuring Retry Attempts You can configure the interval and the number of times the adapter framework will attempt to resend a message to an adapter from the NetWeaver Administrator. For more information on how to configure a message to be retried. All rights reserved. 395 . The following methods of authentication on the proxy server are supported: ● Basic ● Digest ● NTLMv1 (Note that NTLMv2 is not supported) Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters © 2015 SAP SE or an SAP affiliate company. GetProfile URL required string Default value: https:// certservice. Configuring Proxy Server Parameters The Ariba Network Adapter for SAP NetWeaver can be configured to use Secure HyperText Transfer Protocol (HTTPS) through a proxy server. This includes the interval between retry attempts for outbound messages sent by SAP NetWeaver PI to the cXML adapter. Interval r (Minutes) Default value: 60 Outbound Request Type One of following: The request type for Outbound.Outbound Parameters Parameter Name Usage Type Data Type Value Description cXML Configuration URL used to send ProfileRequest. and the number of inbound documents sent by the cXML adapter to PI.1 documentation.com/ service/transaction/ cxml.asp Poll interval of profileRequest ex­ GetProfile required intege pressed in minutes. To enable secure communication through a proxy server. If None. cXML Adapter Parameters . Required for NTLM authentication only. The user name used for authentication. Username String Required for all three authentication methods. Password String Required for all three authentication methods. Note that NTLMv2 is not supported. Ariba Network Adapter for SAP NetWeaver Setup Guide 396 © 2015 SAP SE or an SAP affiliate company. All rights reserved. The password used for authentication. configure the following parameters for the cXML Adapter: Parameter Name Type Value Description Enables or disables the use of the proxy Use Proxy Server Boolean No (default) server for remote communication with Yes Ariba Network Host name or IP address of the proxy Proxy Server Host String server Port used by the proxy server to handle Proxy Server Port Integer secure communication Indicates the method used for authenti­ Proxy List None (default) cation on the proxy server. the Authentication Basic Method Digest proxy server does not require authenti­ NTLM cation. The domain to which the user identified Domain String by the Username parameter belongs. Ariba SAP Objects This appendix describes the SAP development objects provided by Ariba as part of the SAP integration. The SAP NetWeaver PI content is changed by importing the RFCs and ABAP objects renamed with the /ARBA/ namespace into SAP NetWeaver PI. All rights reserved. all the RFC and SAP objects have been renamed to /ARBA/ namespace. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects © 2015 SAP SE or an SAP affiliate company. The audience for this appendix includes: ● BASIS administrators who import Ariba’s SAP transports and need to see the list of objects they are importing. However. a new namespace called /ARBA/ is registered and all SAP objects delivered by Ariba are renamed from Z_<object name> to /ARBA/<object name>. For example. 397 .0. you can customize the code using the BADI hooks in the program that Ariba provides you for customization. As part of this certification. Note Starting Ariba Cloud Integration Release 1. You cannot edit the main code without an access key from the SAP marketplace. the function module called Z_ARIBA_INVOICE_STATUS_UPDATE is renamed to /ARBA/ INVOICE_STATUS_UPDATE. SAP Certification [page 397] /ARBA/COMMON_OBJECTS Package [page 398] /ARBA/PURCHASEORDER Package [page 400] /ARBA/CHANGEPURCHASEORDER Package [page 401] /ARBA/ERPINVOICE Package [page 402] /ARBA/INVOICESTATUSUPDATE Package [page 403] /ARBA/PAYMENTPROPOSAL Package [page 404] /ARBA/RECEIPT Package [page 405] /ARBA/REQUISITION Package [page 405] SAP Certification The SAP code delivered by Ariba is certified by SAP. ● ABAP developers who are responsible for customizing the Ariba SAP objects. Ariba SAP Objects . Function Groups and Modules The following are the function groups in the /ARBA/COMMON_OBJECTS package: Table 8: /ARBA/COMMON_OBJECTS Function Groups Function Group Description Lookup Function Modules /ARBA/LOOKUP Extended Table Maintenance (Generated) /ARBA/TABLE_MAIN Table 9: /ARBA/COMMON_OBJECTS Function Modules Function Module Description External access to R/3 tables via RFC /ARBA/RFC_READ_TABLE Retrieves pre-filtering restrictions /ARBA/PREFILTER_ADAPTER Ariba function to construct where condition /ARBA/WHERE_CONDITION_FILTER Payment Proposal ID for Orbian Integration /ARBA/ORBIAN_INFO_GETDETAIL Read BSIK and BKPF data /ARBA/READ_BSIK_BKPF Tables The following are the tables for the /ARBA/COMMON_OBJECTS package: Table 10: /ARBA/COMMON_OBJECTS Tables Table Description Ariba Network Vendor Table /ARBA/AN_VENDOR Ariba Network Adapter for SAP NetWeaver Setup Guide 398 © 2015 SAP SE or an SAP affiliate company. All rights reserved./ARBA/COMMON_OBJECTS Package The /ARBA/COMMON_OBJECTS package contains Ariba development objects for Ariba Network Adapter for SAP NetWeaver for SAP NetWeaver objects. ERP Invoice. 399 . PP. All rights reserved. You must maintain the following entries in the /ARBA/PARAM_TAB table using Transaction SM30: Variable Name Field Name Sign OPTION Select Value GROSS_INV_RECEIPT B~BLART I EQ RE NONPO_INVOICE B~BLART I EQ KR PAYMENT_POSTING BLART I EQ KP VENDOR_PAYMENT BLART I EQ KZ VENDOR_PAYMENT B~BLART I EQ KZ VENDOR_PAYMENT H~BLART I EQ KZ ACCRUAL_TAX_CONDITION MW1 I EQ MW1 ACCRUAL_TAX_CONDITION MW2 I EQ MW2 You must maintain the following entries in the /ARBA/AN_VENDOR table using Transaction SM30: Fieldname Value BUKRS 3000 LIFNR 1000 You must maintain the following entries in the /ARBA/TAXCAT_MAP table using Transaction SM30: Fieldname Value MWSKZ I1 TAX_CATEGORY Sales Tax Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects © 2015 SAP SE or an SAP affiliate company. Table Description Ariba table to store configurable parameters /ARBA/PARAM_TAB Stores invoices created in ERP and which are sent to AN /ARBA/AN_ERPINV Tables read by /ARBA/RFC_READ_TABLE Function Module /ARBA/LOOKUPTAB Table to store Proxy Parameters for ISU. and Receipts /ARBA/PROXYPARAM Note The ABAP function /ARBA/invoice_get_details is designed to use the vendors from the /ARBA/ AN_VENDOR table while selecting data for invoice details. Use the SM30 transaction to generate table maintenance objects to maintain records in this table. All rights reserved.Structures The following are the structures for the /ARBA/COMMON_OBJECTS package: Table 11: /ARBA/COMMON_OBJECTS Structures Structure Description Table Structure for "WHERE (itab)" Statement /ARBA/WTAB Structure to support RFC READ TABLE for Unicode Systems /ARBA/RFC_READ_TABLE /ARBA/PURCHASEORDER Package Function Group Description Purchase Order Adapter Objects /ARBA/PURCHASEORDER Function Module Name Description Accounting Information for PO /ARBA/PO_ACCOUNTING_INFO Service Purchase Order Details /ARBA/PO_SERVICE_INFO Structure Name Description /ARBA/EKKN Purchase Order Accounting Details /ARBA/EKKN_SERVICE Purchase Order Account Assignment Structure /ARBA/EKPO Purchase Order Line Item Details /ARBA/EKPO_SERVICE Service Line item Details /ARBA/ESKL Purchase Order Account Assignment Service Line /ARBA/ESLH Purchase Order Header Service Structure /ARBA/ESLL Purchase Order Service Line item Detail Table Type Description /ARBA/EKKN_SERVICE_T Table Type For Service Purchase Order Accounting Details /ARBA/EKKN_T Table Type For Purchase Order Accounting Detail Ariba Network Adapter for SAP NetWeaver Setup Guide 400 © 2015 SAP SE or an SAP affiliate company. Ariba SAP Objects . Table Type Description /ARBA/EKPO_SERVICE_T Table Type For Service Line Item Details /ARBA/EKPO_T Table Type For Purchase Order Line Item Detail /ARBA/ESKL_T Table Type . All rights reserved.Purchase Order Account Assignment Service Line /ARBA/ESLH_T Table Type For Purchase Order Header Service Structure /ARBA/ESLL_T Table Type For Purchase Order Service Line item Detail /ARBA/RFC_DB_FLD_T Table Type For Field Names /ARBA/TAB512_T Table Type for 512 Byte Field Structure /ARBA/CHANGEPURCHASEORDER Package Function Group Description Change Purchase Order /ARBA/CHANGEPURCHASEORDER Function Module Name Description Change Purchase Order Get Detail /ARBA/PO_GET_DETAIL Structure Name Description /ARBA/BAPIEKKOL Transfer Structure: Display/List: PO Header with Vendor Name /ARBA/BAPIEKPO Transfer Structure: Display/List PO Item /ARBA/BAPIEKKN Transfer Structure: Display/List: PO Account Assignment /ARBA/BAPIESKL Communication Structure: Account Assignment Values: Service Line /ARBA/BAPIESLL Communication Structure: Service Line Table Type Description /ARBA/BAPIEKET_T Purchase Order Schedule Lines /ARBA/BAPIEKKN_T Purchase Order Accounting Details Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects © 2015 SAP SE or an SAP affiliate company. 401 . Table Type Description /ARBA/BAPIEKPO_T Transfer Structure: Display/List PO Item /ARBA/BAPIESKL_T Service Purchase Order Account Assignment Details /ARBA/BAPIESLL_T Service Purchase Order Detail /ARBA/PO_ACCOUNT_T Ariba Purchase Order Accounting Details /ARBA/PO_ITEMS_T Ariba Purchase Order Items /ARBA/PO_SERVICEACCOUNT_T Purchase Order Service Account Details /ARBA/PO_SERVICEITEMS_T Ariba Service Purchase Order Item Detail /ARBA/ERPINVOICE Package Function Group Description /ARBA/ERPINVOICE ERP Invoice Adapter objects Function Module Name Description /ARBA/INVOICE_GET_DETAILS Ariba Invoice FI documents to AN Program Name Description /ARBA/ERPINVOICE_EXPORT ABAP proxy for Invoice Interface Table Name Description /ARBA/TAXCAT_MAP Ariba Tax code to Tax Category Map Structure Name Description /ARBA/INVOICE_HEADER_DETAILS Ariba ERP Initiated Invoice Header details /ARBA/INVOICE_LINE_DETAILS Ariba ERP Initiated Invoice line item details /ARBA/BSEG ERP Invoice Line Item Details /ARBA/BSIK ERP Invoice Header Details /ARBA/BSET Invoice Tax Data Table Type Description /ARBA/INVOICE_HEADER_DETAILS_T Invoice Header details Ariba Network Adapter for SAP NetWeaver Setup Guide 402 © 2015 SAP SE or an SAP affiliate company. Ariba SAP Objects . All rights reserved. All rights reserved. Table Type Description /ARBA/INVOICE_LINE_DETAILS_T Invoice line item details /ARBA/BSEG_T ERP Invoice Line Item Details /ARBA/BSIK_T Invoice Details /ARBA/BSET_T Invoice Tax Data /ARBA/INVOICESTATUSUPDATE Package Function Group Description /ARBA/INVOICESTATUSUPDATE Invoice Status Update function group Function Module Name Description /ARBA/INVOICE_STATUS_UPDATE Ariba Invoice status update Program Name Description /ARBA/INVSTATUPDT_EXPORT Program for Calling Invoice Status Update proxy Structure Name Description /ARBA/CONTROL_RECORD IDOC Control Record for Rejected Status Invoices /ARBA/DATA_RECORD IDOC Data Record for Rejected Status Invoices /ARBA/FULL_PAID_INVOICE Fully Paid Invoices /ARBA/INVOICE Invoice Detail Structure /ARBA/INVOICE_STATUS Structure for Invoice status update /ARBA/PARTIAL_PAYMENTS Partial Payment Details /ARBA/PARTIAL_PAID_INVOICE Partially Paid Invoice Details /ARBA/REVERSED_INVOICE Invoice Status Update Reversal Documents /ARBA/REVERSED_PAYMENTS Reversed Payments Details Table Type Description /ARBA/CONTROL_RECORD_T IDOC Control Record for Rejected Status Invoices /ARBA/DATA_RECORD_T IDOC Data Record for Rejected Status Invoices /ARBA/FULL_PAID_INVOICE_T Fully Paid Invoices /ARBA/INVOICE_T Invoice Detail Structure /ARBA/INVOICE_STATUS_T Structure for Invoice status update /ARBA/PARTIAL_PAYMENTS_T Partial Payment Details /ARBA/PARTIAL_PAID_INVOICE_T Partially Paid Invoice Details Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects © 2015 SAP SE or an SAP affiliate company. 403 . All rights reserved. Ariba SAP Objects .Table Type Description /ARBA/REVERSED_INVOICE_T Reversed Invoices /ARBA/REVERSED_PAYMENTS_T Reversed Payments /ARBA/PAYMENTPROPOSAL Package Function Group Description /ARBA/PAYMENTPROPOSAL Payment Proposal Adapter Objects Function Module Name Description /ARBA/PAYMENT_PROPOSAL Payment Proposal RFC Program Name Description /ARBA/PAYMENTPROPOSAL_EXPORT Payment Proposal Program (Proxy) Structure Name Description /ARBA/ACCOUNTINGDOCUMENT Payment Proposal Accounting Data /ARBA/PARTIALINVOICE Invoice Detail Structure For Payment Proposal Customer Exit /ARBA/PARTIALPAYMENTS Partial Payment Structure For Payment Proposal Customer Exit /ARBA/PAYMENTPROPOSAL Ariba Customer Exit for Payment Proposal Information /ARBA/PAYMENT_PROPOSAL Structure used in payment proposal RFC Ariba adapter /ARBA/PAYEE Structure for payment proposal payee /ARBA/PAYER Structure for payment proposal payer /ARBA/REC_BANK Payment Proposal Bank Details Table Type Description /ARBA/ACCOUNTINGDOCUMENT_T Payment Proposal Accounting Data /ARBA/PARTIALINVOICE_T Partial Invoice Details /ARBA/PARTIALPAYMENTS_T Payment Proposal Partial Payments /ARBA/PAYMENTPROPOSAL_T Payment Proposal /ARBA/PAYMENT_PROPOSAL_T Payment Proposal /ARBA/PAYEE_T Payment proposal payee /ARBA/PAYER_T Payment proposal payer /ARBA/REC_BANK_T Payment Proposal Bank Details Ariba Network Adapter for SAP NetWeaver Setup Guide 404 © 2015 SAP SE or an SAP affiliate company. All rights reserved./ARBA/RECEIPT Package Program Name Description /ARBA/RECEIPT_PUBLISH Proxy for Receipt Export Structure Name Description /ARBA/PO_DETAIL Ariba Purchase Order Detail Structure /ARBA/RECEIPT Ariba Material Document Structure Table Type Description /ARBA/PO_DETAIL_T Ariba Purchase Order Detail Structure /ARBA/RECEIPT_T Ariba Material Document /ARBA/GR_HEADER_T Goods Receipt Header /ARBA/GR_ITEMS_T Goods Receipt Items /ARBA/REQUISITION Package Function Group Description /ARBA/REQPARAM Extended Table Maintenance (Generated) Program Name Description /ARBA/REQUISITION_EXPORT Requisition Export (Proxy) Table Name Description /ARBA/REQPARAM Table to store Ariba Requisition Parameters Structure Name Description /ARBA/REQUISITION Requisition Details Table Type Description /ARBA/REQUISITION_T Requisition Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects © 2015 SAP SE or an SAP affiliate company. 405 . All rights reserved. Ariba updates the technical documentation for its On Demand solutions if ● software changes delivered in service packs or hot fixes require a documentation update to correctly reflect the new or changed functionality. tion Redesigned 4 December 2015 Configuring the In­ Updated the task with the results and example section. but critical documentation updates may be released at any time. Multiple Chapters Ariba Cloud Integration Release 6. terface Determina­ tion Settings for the Sourcing Award to Contract Integration Sce­ nario Configuring Implicit Updated the code in Step 12.0 ● Updated throughout for the Ariba Cloud Integration Release 6. ● the existing content is incorrect or user feedback indicated that important content is missing. Enhancements for New Service Or­ ders Ariba Network Adapter for SAP NetWeaver Setup Guide 406 © 2015 SAP SE or an SAP affiliate company. 2 October 2015 Integration of Cata­ ● Removed the limitation on transactional data that is no longer log Data in SAP applicable. Document Month/Year of Updated Chapter/ Short Description of Change Version Update Section 1 September 2015 n/a ● Reset revision history for Cloud Integration Release 6. Ariba reserves the right to update its technical documentation without prior notification.Revision History The following table provides a brief history of the updates to this guide. ERP and Ariba Net­ work Service Sheet and ● Updated the integration scenario for Service Sheet and Service Service Sheet Re­ Sheet Response.0.0 and earlier. sponse Integration Scenario 3 November 2015 Integration of Cata­ Updated section log Data in SAP ERP and Ariba Net­ work Change Purchase Updated the section as this is available only for customers using Order Implementa­ Ariba Cloud Integration 4. Revision History . Most documentation updates will be made available in the same week as the software service packs are released.0. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding.Important Disclaimers and Legal Information Coding Samples Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. Accessibility The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication. This is to ensure that the documentation remains comprehensible. does not apply in cases of wilful misconduct or gross negligence of SAP. SAP in particular disclaims any liability in relation to this document. however. Ariba Network Adapter for SAP NetWeaver Setup Guide Important Disclaimers and Legal Information © 2015 SAP SE or an SAP affiliate company. All links are categorized for transparency (see: http://help. and SAP shall not be liable for errors or damages caused by the usage of the Code. All rights reserved. If when referring to members of both sexes. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. or a gender-neutral noun (such as "sales person" or "working days") is used. SAP reserves the right to use the masculine form of the noun and pronoun. This disclaimer. 407 . the third-person singular cannot be avoided or a gender-neutral noun does not exist. Depending on the context. Gender-Neutral Language As far as possible. unless damages were caused by SAP intentionally or by SAP's gross negligence. this document does not result in any direct or indirect contractual obligations of SAP.sap. SAP does not warrant the correctness and completeness of the Code given herein. it is in no way intended to be a binding guideline on how to ensure accessibility of software products.com/disclaimer). These hyperlinks are intended to serve as a hint about where to find related information. however. Internet Hyperlinks The SAP documentation may contain hyperlinks to the Internet. Furthermore. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP documentation is gender neutral. the reader is addressed directly with "you". 285.199. 7. 7. and 8. Patents pending. 6. 6. 6.599. assumes no responsibility or liability for any errors or inaccuracies that may appear in the documentation.com/copyrights. Inc. They are provided under a license or other agreement containing restrictions on use and disclosure and are also protected by copyright.364.979.483. Ariba Sourcing solutions (On Demand and software) are protected by one or more of the following patents. as well as the Ariba solutions. 6.878.7.746. go to http://www. This documentation. 7.035. 7.574. 6.225. 7. in the United States and other countries.571. 6.577.com Copyright © 1996–2015 Ariba. Ariba. 7.223. 7.536.018. 6. 7. software and/or services described in it.018.238.165.061.283.989.299.451.383. 7. electronic.989. All rights reserved.230. Inc. 7.167.192. patent and/or other intellectual property laws. 6.980.714.395.564. contain proprietary information.050.752.S.249.936.230.634. 7. 6.317. For information regarding software or other intellectual property licensed from a third party.191. 6. Patent Nos.145.ariba. .324. 7. without the prior written permission of Ariba.147.114.117.577.223.511.584.cfm.010. Ariba and Ariba products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Ariba.296.137.001.682.043. 7.558. Inc.147.146.146. including without limitation: U.S. 6. and 8. 7. 6.998. 6.407. Certain Ariba products may include third party software or other intellectual property licensed from a third party.191.317. 6.852.408. Except as permitted by such agreement. 7.072.199.167. 7. Please see http://www. 6.com/legal/trademarks for additional trademark information and notices. 6. 7.285.815. 7.225. 7. 7.216.603.050.084. 7.657. 8. 7. mechanical or otherwise.146. 7. 8. 7.152.392.364. 7. 6.283.130.362. 6.331.499.401.499. 6. 7. Inc.682.192.392.408.216.444. no part of the document may be reproduced or transmitted in any form by any means.010.ariba. 7. 7.114. 7. 6.693.606.871. 7.035.871. The information contained in the documentation is subject to change without notice.283.939. 6. 7. 6.206.952. 7.047.277.ariba.511.230. 7. 6.152.www.318.536.878.072.461. Patent Nos.499. 6.362. Other Ariba product solutions are protected by one or more of the following patents: U.346.876.564.558. Patents pending.230.061. 6.283.085.747.439.952. 7.