Ariba Cloud Integration 6.0 Document Version: 4 – December 2015
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network
Content
Ariba Network Adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Data Flow and Data Element Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Supported cXML Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 cXML Adapter Document Transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Setting Up the Ariba Network Adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Configuring the Ariba Network Adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Installing the Network Adapter Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 About Configuring Security Certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Importing Security Certificates into the Java JRE Keystore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Importing Security Certificates into the Java JRE TrustStore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Installing Client Certificates on Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 About Deploying the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Deploying the cXML Adapter Using JSPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Upgrading the cXML Adapter Using JSPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Installing Additional Resources for the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Undeploying the cXML Adapter using the Textconsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Deploying the cXML Adapter Using the textconsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Setting Log Configuration Parameters for the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 About Configuring the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . 46 About Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver. . . . . . . . . . . . . . . . . . . 46 cXML Interfaces Supported in the Ariba Cloud Integration Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Features Available in the Ariba Cloud Integration Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Steps to Install the Ariba Network Adapter for SAP NetWeaver PI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Installing the SAP ERP Transports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Upgrading to a Higher Version of the Ariba Network Adapter for SAP NetWeaver Transports. . . . . . . . . 52 Changes Required on your SAP ERP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Changes Required on your SAP NetWeaver PI System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Migrating the Design Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Updating the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Content
Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Configuring SLD and Transaction Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 About Configuring the System Landscape Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Importing Ariba Network Product and Component Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Defining Technical and Business System for Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Defining the Business System for Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Defining Technical and Business System for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Defining the Business Landscape for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 About Configuring Transaction Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Importing the Design Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 About Configuring ERP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Assigning Business Systems in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Creating Communication Channels for ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Creating the IDoc Receiver Communication Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Creating the RFC Receiver Communication Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Configuring IDoc Metadata (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Configuring SAP NetWeaver PI Value Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Configuring Units of Measure (UOM) Code Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Configuring Language Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Configuring TimeZone Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Configuring Global Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 Configure the Mappings Between Business System and Logical System Names. . . . . . . . . . . . . . . . 76 Configuring Currency Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Maintaining the Value Mapping to Support Logical Systems in SAP NetWeaver PI. . . . . . . . . . . . . . . 78 Creating a New Value Mapping Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Configuring Integration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 About Configuring Integration Scenarios in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . 80 Configuring the Software Component Version for Communication Channel Templates . . . . . . . . . . . 82 Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Transferring the Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 About Configuring the Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Configuring Communication Channels for the Purchase Order Integration Scenario. . . . . . . . . . . . . 87 Configuring Interface Determination Settings for the Purchase Order Integration Scenario. . . . . . . . 88 Activating the Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Change Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Reconfiguring the SAP Partner Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 About Configuring Implicit Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Removing Change Order Configurations from Your Ariba Solution. . . . . . . . . . . . . . . . . . . . . . . . . . 93 Migrating Change Order Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Ariba Network Adapter for SAP NetWeaver Setup Guide Content
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
3
Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Transferring the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 About Configuring the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Configuring Communication Channels for the Order Confirmation Integration Scenario. . . . . . . . . . .99 Configuring Receiver Determination Settings for the Order Confirmation Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Configuring Interface Determination Settings for the Order Confirmation Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Activating the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Additional Configuration Tasks for the Order Confirmation Integration Scenario. . . . . . . . . . . . . . . 102 Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Transferring the Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 About Configuring the Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Configuring Communication Channels for the Ship Notice Integration Scenario. . . . . . . . . . . . . . . .106 Configuring Receiver Determination Settings for the Ship Notice Integration Scenario. . . . . . . . . . . 107 Configuring Interface Determination Settings for the Ship Notice Integration Scenario. . . . . . . . . . .108 Activating the Ship Notice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Ship Notice Integration Scenario to Support Creation of a Single Ship Notice Against Multiple Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Transferring the Ship Notice Integration Scenario for Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . 111 About Configuring the Ship Notice Integration Scenario for Multiple POs. . . . . . . . . . . . . . . . . . . . . 112 Configuring Communication Channels for the Ship Notice Integration Scenario with Multiple POs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Configuring Receiver Determination Settings for the Ship Notice Integration Scenario with Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 Configuring Interface Determination Settings for the Ship Notice Integration Scenario with Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Activating the Ship Notice Integration Scenario for Multiple POs. . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Configuring the Ship Notice Integration Scenario to Receive Ship Notices with Zero Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Service Sheet and Service Sheet Response Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Transferring Service Sheet and Service Sheet Response Scenarios. . . . . . . . . . . . . . . . . . . . . . . . .118 About Configuring the Service Sheet and Service Sheet Response Integration Scenarios. . . . . . . . . 119 Configuring Communication Channels for the Service Sheet and Service Sheet Response Integration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Activating the Service Sheet and Service Sheet Response Integration Scenarios. . . . . . . . . . . . . . . 122 Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 Transferring the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 About Configuring the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Configuring Communication Channels for the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . 127 Configuring Receiver Determination Settings for the Invoice Integration Scenario. . . . . . . . . . . . . . 128 Configuring Interface Determination Settings for the Invoice Integration Scenario. . . . . . . . . . . . . . 129
4
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Content
Activating the Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130 PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Transferring the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 About Configuring the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Configuring Communication Channels for the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . 134 Configuring Receiver Determination Settings for the PayMeNow Integration Scenario. . . . . . . . . . . 135 Configuring Interface Determination Settings for the PayMeNow Integration Scenario. . . . . . . . . . . 136 Activating the PayMeNow Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 Transferring the Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 About Configuring the Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . .139 Configuring Interface Determination Settings for the Payment Remittance Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Activating the Payment Remittance Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 Schedule Lines in Purchase Orders and Change Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Prerequisites to Enabling Schedule Lines in Purchase Orders from your SAP ERP System to Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Configuring the Purchase Order Integration Scenario to Support Schedule Lines. . . . . . . . . . . . . . .144 Blanket Purchase Order Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Configuring the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Transferring the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 About Configuring the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Configuring Communication Channels for the Order Inquiries Integration Scenario. . . . . . . . . . . . . 152 Configuring Interface Determination Settings for the Order Inquiries Integration Scenario. . . . . . . . 153 Activating the Order Inquiries Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 About Configuring the Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . 154 Configuring Communication Channels for the Scheduling Agreement Release Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Configuring Interface Determination Settings for the Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Activating the Scheduling Agreement Release Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . 159 Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160 Transferring the Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 About Configuring the Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . 161 Configuring Communication Channels for the Invoice Status Update Integration Scenario. . . . . . . . 165 Configuring Interface Determination Settings for the Invoice Status Update Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Activating the Invoice Status Update Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Canceling MIRO Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Ariba Network Adapter for SAP NetWeaver Setup Guide Content
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
5
Transferring the ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 About Configuring the ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . 168 Configuring Communication Channels for the ERP-Initiated Invoice Integration Scenario. . . . . . . . . 172 Configuring Interface Determination Settings for the ERP-Initiated Invoice Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 Activating the ERP-Initiated Invoice Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Receipt Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Transferring the Integration Scenario for Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 About Configuring the Integration Scenario for Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Configuring Communication Channels the Receipts Integration Scenario. . . . . . . . . . . . . . . . . . . . 177 Configuring Interface Determination Settings for the Receipts Integration Scenario. . . . . . . . . . . . . 178 Activating the Receipts Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178 Additional Receipts Integration Requirement for SAP NetWeaver 7.1 EHP1. . . . . . . . . . . . . . . . . . . 179 Receipt Integration Scenario for Corrections and Returns in Receipts. . . . . . . . . . . . . . . . . . . . . . . . . 179 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Data Flow Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 cXML Changes to Support Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Configuring the Receipt Integration Scenario to Support Returns and Corrections. . . . . . . . . . . . . . 182 Receipt Integration Scenario for Purchase Orders with Multiple Accounting Assignments. . . . . . . . . . . 182 Activating the MM Multiple Account Assignments Enterprise Business Function. . . . . . . . . . . . . . . 183 Adding the Code in the BADI Implementation for MM Multiple Account Assignments. . . . . . . . . . . . 184 Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Transferring the Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 About Configuring the Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Configuring Interface Determination Settings for the Payment Proposal Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Activating the Payment Proposal Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Enabling Quick Enablement for Payment Proposal Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . 190 Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Transferring the Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 About Configuring the Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . 192 Configuring Communication Channels for the Requisition Request Integration Scenario. . . . . . . . . 194 Configuring Interface Determination Settings for the Requisition Request Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Activating for the Requisition Request Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Request for Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196 Transferring the Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 About Configuring the Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Configuring Communication Channels for the Quotation Integration Scenario. . . . . . . . . . . . . . . . 200 Configuring Interface Determination Setting for the Quotation Integration Scenario. . . . . . . . . . . . 200 Activating the Quotation Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 Sourcing Award to Contract Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Content
Transferring the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . .202 About Configuring the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . 203 Configuring the Communication Channel for the Sourcing Award to Contract Integration Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Configuring the Interface Determination Settings for the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Activating the Sourcing Award to Contract Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . 208 Change Purchase Order Implementation Redesigned. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Enabling Change Purchase Order Redesign. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Implementing the Redesigned Change Purchase Order Transaction. . . . . . . . . . . . . . . . . . . . . . . .209 Proxy Implementation for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Enabling Proxy Implementation for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Advanced Configuration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Linking Multiple SAP instances with Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Document Routing Mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Multi-ERP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Configuring Supplier Quick Enablement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Customizing Data Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Downloading Mapping Workbooks from Connect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Enabling Migration of Mapping Customization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Enabling Support for Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Attachments for Outbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Attachments for Inbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Managing Email Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Support for Proxy ByPass. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 HTTPS Support for Attachment Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Configuring Proxy Server ByPass for Attachment Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Troubleshooting Proxy Server ByPass for Attachment Processing. . . . . . . . . . . . . . . . . . . . . . . . . 227 Support for 2-Way Match. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Using Endpoint Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Using Endpoints for Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229 Enabling Endpoint Integration in SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Endpoint Integration for Multiple ERP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Using the SAP NetWeaver PI KeyStore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Configuring the cXML Adapter to Use the SAP NetWeaver PI Keystore. . . . . . . . . . . . . . . . . . . . . . 231 PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Enabling PDF Invoice Copy Attachment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Using PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Processing of PDF Invoice Copy Attachments by the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . 234 BADI Implementation for the BADI Definition INVOICE_UPDATE. . . . . . . . . . . . . . . . . . . . . . . . . . 237 About Configuring Your SAP ERP System for PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . 243 Ariba Network Adapter for SAP NetWeaver Setup Guide Content
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
7
Defining a New Document Class for PDF Invoice Copy Attachments. . . . . . . . . . . . . . . . . . . . . . . . 243 Defining a New Document Type for Invoice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Create a Link Between the Standard Business Object and the New Document Type for Invoice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Maintaining the INVOICE_EMAIL_SEND Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Maintaining the ZDEL Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 Configuring the Attachment Processing Mode for PDF Invoice Copy Attachments. . . . . . . . . . . . . . 245 Integrating SAP ERP with the Ariba Spot Quote Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 About SAP ERP and Ariba Spot Quote Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 SAP ERP Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Enabling SAP ERP and Ariba Spot Quote Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 SAP ERP and Ariba Spot Quote Integration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249 SAP ERP and Ariba Spot Quote Integration Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Configuring Ariba Network Buyer Settings for Ariba Spot Quote. . . . . . . . . . . . . . . . . . . . . . . . . . 250 Messages Mapping for Ariba Spot Quote. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 How to Handle cXML Document Errors for Ariba Spot Quote. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Integration of Catalog Data in SAP ERP and Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250 About Integration of Catalog Data in SAP ERP and Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . 251 Enabling the Integration of Catalog Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Using the Catalog Export Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 About Processing Purchase Information Records and Material Master Records. . . . . . . . . . . . . . . 256 Uploading Catalog Changes Using Mediated Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Uploading Catalog Changes Using the Incremental Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Maintaining Catalog Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Configuring Catalog Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Configuring Your SAP ERP System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Importing Custom Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Configuring SAP IDocs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Configuring SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Configuring SAP for IDoc Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 Configuring the Partner Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271 Creating an Output Type for the Entry Sheet Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Maintaining Condition Records for Outbound Transactions: POs. . . . . . . . . . . . . . . . . . . . . . . . . . 279 Maintaining Condition Records for Outbound Transactions: Service Sheets. . . . . . . . . . . . . . . . . . 280 Making Additional Change PO Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Maintaining Variants for Remittance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Making Additional Invoice Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Making Additional Tax and Accrual Calculation Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Maintaining Bank Key for the House Bank for Payment Remittance Advice. . . . . . . . . . . . . . . . . . . 288 Making User Exit Enhancements to Support Shipping and Handling Charges. . . . . . . . . . . . . . . . . 288
8
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Content
Maintaining Global Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Configuration Related to Export of Requisitions from SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Business AddIns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Proxy Settings in SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Configuring Proxy Settings for SAP NetWeaver 7.1 or Dual Stack (ABAP and Java) Instances of SAP NetWeaver PI 7.3 and above. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Configuring Proxy Settings for Single Stack (Java only) Instances of SAP NetWeaver PI 7.3 and above. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Documentation of RFCs Within the SAP NetWeaver Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Defining Authorizations for Running Ariba Network Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Configuring Advanced Pricing Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 ABAP Programs for Outbound Transactions Implemented Using Proxies. . . . . . . . . . . . . . . . . . . . . . .299 Configuring Implicit Enhancements for Comments in Order Confirmations. . . . . . . . . . . . . . . . . . . . . 300 Configuring Invoice Status Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Invoice Status Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301 Configuring the Invoice Status Update Transaction on your SAP ERP system. . . . . . . . . . . . . . . . . 303 Configuring Order Inquiries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Configuring SAP IDOC for Order Inquiries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Configuring the Partner Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Maintaining Condition Records for Inquiries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Implementing a Custom Exit for the Order Inquiries Function Module. . . . . . . . . . . . . . . . . . . . . . .308 Support for Additional cXML Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Configuring Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Configuring SAP IDOC for Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Configuring the Partner Profile for Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . 310 Maintaining Condition Records for Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . 311 Implementing a Custom Exit for Scheduling Agreement Releases. . . . . . . . . . . . . . . . . . . . . . . . . . 311 Support for Additional cXML Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Configuring IDOC Metadata (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313 Configuring Ship Notices Against Multiple Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Configuring the SAP IDOC for Ship Notices Against Multiple Purchase Orders. . . . . . . . . . . . . . . . . 313 Configuring the Partner Profile or Ship Notices Against Multiple Purchase Orders. . . . . . . . . . . . . . 314 Configuring IDoc Metadata for Scheduling Agreement Releases (Optional). . . . . . . . . . . . . . . . . . . 315 Configuring Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Configuring Parameters in the ARBA/PARAM_TAB Table for Returns and Corrections in Receipts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Maintaining Condition Records for Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . . . 317 Maintaining Printer Default Values for Returns and Corrections in Receipts. . . . . . . . . . . . . . . . . . . 318 Configuring Quote Request and Quote Message Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Configuring your System for Quote Request Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Configuring your System for Quote Message Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Configuring SAP NetWeaver PI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Ariba Network Adapter for SAP NetWeaver Setup Guide Content
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
9
Configuring Support for Line Level Hierarchies in Service Purchase Orders. . . . . . . . . . . . . . . . . . . . . 321 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 About Configuring Implicit Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Direct Invoicing of Purchase Order Service Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325 Configuring Service Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Implementing Customer Exits for Invoices with Service Type Line Items. . . . . . . . . . . . . . . . . . . . . 326 Specifying Time-Out Intervals for Processing Service Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . .327 Implementing Enhancements for Service Sheets Created for New Purchase Orders. . . . . . . . . . . . 328 Implementing Enhancements for Service Sheets Created for Changed or Canceled Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Configuring ERP-Initiated Invoices to Use the IDOC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Configuring the NACE Setting to Send ERS Invoices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Configuring the NACE Setting to Send Invoicing Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Configuring the NACE Setting to Send MIRO Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Implementing the Customer Exit for MM Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Implementing Routines to Prevent Creation of Duplicate MM IDOCs . . . . . . . . . . . . . . . . . . . . . . . 336 Maintaining Partner Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Configuring the FI Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Setting Document Type Filters for FI Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339 Maintaining Output Types for FI Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 Implementing the Customer Exit for FI Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Handling Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On. . . . . . . . . . . . . . . . . . . . . . . . 343 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Installation Requirements for SAP Suite Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Setting Up the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .347 Understanding cXML Adapter Document Transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Deploying the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Deploying the cXML Adapter Using JSPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Undeploying the Adapter using the Textconsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Undeploying the Adapter using the Textconsole. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Configuring Logging for the SAP Suite Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Configuring the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350 Configuring the System Landscape Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Importing Ariba Network Product and Component Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 To import product and component definitions:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 Defining Technical and Business System for Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 To define the Technical System for Ariba Network:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 To define the Business System for Ariba Network:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Defining the Technical System for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Defining the Business System for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
10
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Content
Configuring Transaction Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Importing the Design Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Configuring SAP ERP Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Assigning Business Systems in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355 Configuring Integration Scenarios in the Integration Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 Workflow for Configuring the Integration Scenario for Inbound And Outbound Transactions. . . . . . .357 Configuring the Integration Directory for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Transferring the Integration Scenario for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . 357 About Configuring the Integration Scenario for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . 359 Assigning the Model for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Assigning Components for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Configuring Sender And Receiver Relations for Individual Connections for Inbound Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Generating Objects for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Configuring Communication Channels for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . 362 Activating the Scenario for Inbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363 Configuring the Integration Directory for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Transferring Integration Scenario for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 About Configuring the Integration Scenario for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . 366 Assigning the Model for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366 Assigning Components for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 Configuring Sender and Receiver Relations for Individual Connections For Outbound Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Generate Objects for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Configuring Communication Channels for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . 369 Activating the Scenario for Outbound Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Linking Multiple SAP Instances with Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Multi-ERP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Supported cXML Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 Testing the SAP NetWeaver for Suite Add-On Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 Sending a Purchase Order for Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Running a getPending Transaction for Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Understanding Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Understanding Error and Status Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Understanding Email Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Monitoring the cXML Adapter from Runtime Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 Deploying the Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Ariba Network Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Downloading the Ariba Network Integration Guide from Connect:. . . . . . . . . . . . . . . . . . . . . . . . . 380 Enabling Support for Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Attachments Support in cXML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Attachments for Outbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Ariba Network Adapter for SAP NetWeaver Setup Guide Content
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
11
Attachments for Inbound Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Using Endpoints for Integration with SAP NetWeaver for SAP Suite Add-On. . . . . . . . . . . . . . . . . . . . .382 Using the SAP NetWeaver PI KeyStore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Configuring Communication Channels to Use SAP NetWeaver PI Keystore. . . . . . . . . . . . . . . . . . . 383 Testing the Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Testing the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Sending a Purchase Order for Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Running a getPending Transaction for Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Understanding Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Monitoring of the cXML Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Monitoring the cXML Adapter from Runtime Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388 Deploying the Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Ariba Network Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Downloading the Ariba Network Integration Guide from Connect. . . . . . . . . . . . . . . . . . . . . . . . . . 389 cXML Adapter Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Common Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Inbound Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 Outbound Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 Configuring Retry Attempts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395 Configuring Proxy Server Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395 Ariba SAP Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 SAP Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 /ARBA/COMMON_OBJECTS Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 /ARBA/PURCHASEORDER Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 /ARBA/CHANGEPURCHASEORDER Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 /ARBA/ERPINVOICE Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .402 /ARBA/INVOICESTATUSUPDATE Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 /ARBA/PAYMENTPROPOSAL Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 /ARBA/RECEIPT Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 /ARBA/REQUISITION Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
12
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Content
Ariba Network Adapter for SAP NetWeaver
Overview [page 13] Data Flow and Data Element Mapping [page 14] Setting Up the Ariba Network Adapter for SAP NetWeaver [page 29]
Overview Unless otherwise stated, the information in this guide is applicable to the Ariba Network Adapter for SAP NetWeaver. For information on the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On, see Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On [page 13]. The Ariba Network Adapter for SAP NetWeaver is an add-on module for SAP business applications that enables integration between Ariba Network and your SAP ERP system. It allows your SAP ERP system to send and receive cXML (commerce eXtensible Markup Language) documents to and from Ariba Network by mapping data elements between IDoc and cXML documents. The Ariba Network Adapter for SAP NetWeaver runs on the SAP NetWeaver Process Integration (PI) component, and can be thought of as a library for SAP NetWeaver PI. This library includes integration processes and Java libraries that implement the cXML transport protocol and provide a set of facilities for resolving differences between SAP and Ariba Network. For more information about cXML and Ariba Network, refer to the following documents on Ariba Connect (http:// connect.ariba.com ): ● Ariba Network Integration Guide ● Ariba Network Buyer Administration Guide ● Ariba cXML Solutions Guide ● cXML User’s Guide The Ariba Network Adapter for SAP NetWeaver consists of the following: ● The design package in the SAP Netweaver PI component, which contains integration processes, interface objects, and mappings to convert IDoc to cXML and cXML to IDoc ● The cXML Adapter installed on the SAP Netweaver PI component, which conforms to the J2EE Connector Architecture (JCA) specification, and implements the cXML transport protocol For more information about the JCA specification, see the relevant section on the Sun Java web site (http:// www.java.sun.com ) ● SAP Transport files installed on the SAP ERP system. The Ariba Network Adapter for SAP NetWeaver Setup Guide (this document) illustrates the deployment and configuration processes of the Ariba Network Adapter integration package within SAP NetWeaver PI. The following graphic illustrates how the Ariba Network Adapter for SAP NetWeaver enables the communication flow between Ariba Network and the SAP ERP system. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
13
SAP NetWeaver PI is a platform for process integration within SAP NetWeaver. It facilitates cross-system business processes. In particular, it enables different versions of SAP and non-SAP systems from different vendors running on different platforms to communicate with each other. SAP NetWeaver PI integrates the following components used by the Ariba Network Adapter for SAP NetWeaver and its modules: ● The Business Process Engine is a runtime component of the SAP NetWeaver PI Integration Server. It processes the integration processes at runtime. ● The Integration Engine is the central runtime component of the SAP NetWeaver PI Integration Server used for receiving, processing, and forwarding messages. ● The Adapter Engine is a runtime component of the SAP NetWeaver PI Integration Server. It uses adapters to connect the Integration Engine to SAP systems (RFC adapter) and external systems.
Data Flow and Data Element Mapping The Ariba Network Adapter for SAP NetWeaver processes outbound and inbound cXML transactions. Outbound transactions flow from your SAP ERP system to Ariba Network; inbound transactions flow from Ariba Network to the SAP ERP system. The data elements, or fields, used by your SAP ERP system differ from the data elements used in cXML documents. The Ariba Network Adapter for SAP NetWeaver provides a mechanism for mapping field names and data from your SAP ERP system to those used by cXML and Ariba Network. The Ariba Network Adapter for SAP NetWeaver determines how data from your SAP ERP system populates a corresponding cXML document, and it performs two-way mapping: from your SAP ERP system to cXML, and from cXML to your SAP ERP system. The element mapping mechanism handles one-to-one, many-to-one, and one-to-many mapping scenarios.
14
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
Figure 1: Element Mapping Overview
The Ariba Network Adapter for SAP NetWeaver maintains a set of cross reference or mapping tables. These tables store the information necessary to translate values when sending or receiving cXML documents. It is likely that you will need to customize the mappings to suit the needs of your particular implementation. For more information about customization, see Customizing Data Mappings [page 216].
Supported cXML Interfaces The Ariba Network Adapter for SAP NetWeaver supports the following outbound and inbound cXML interfaces on the SAP NetWeaver PI: Outbound cXML Interfaces
Inbound cXML Interfaces
Order Request
Order Confirmation Request
Change Order Request
Ship Notice Request
Invoice Status Update Request
Invoice Detail Request
Payment Remittance Request
Pay Me Now
Payment Remittance Advice Request
Service Entry Request
Payment Proposal Request Receipt Request Requisition Request Quote Request Order Status Request Catalog Upload Request
For more detailed information about these cXML Interfaces, see the cXML User’s Guide, the Ariba cXML Solutions Guide and the sample mapping tables. The remainder of this section discusses the cXML Interfaces on a general level as they pertain to the Ariba Network Adapter for SAP NetWeaver.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
15
Profile Transaction When the Ariba Network Adapter for SAP NetWeaver sends a ProfileRequest to Ariba Network, it responds with a ProfileResponse indicating the cXML documents that it accepts and their respective URLs. The Ariba Network Adapter for SAP NetWeaver decodes the response to extract URLs for the various transactions and stores the values so that they can be used in subsequent transactions. By default, the Ariba Network Adapter for SAP NetWeaver runs the Profile transaction as a scheduled task every 24 hours. This interval can be configured at runtime. The adapter maintains a profile cache that is updated every time the Profile transaction runs.
Purchase Order When a buying organization requests products or services through its SAP ERP system, the Ariba Network Adapter for SAP NetWeaver maps the request to a cXML OrderRequest and sends it to Ariba Network. Ariba Network then routes the purchase order to the appropriate supplier using the supplier’s preferred order routing method. Note that there is no corresponding OrderResponse document. Instead, Ariba Network transmits a generic response. When the Ariba Network Adapter for SAP NetWeaver sends an OrderRequest document to Ariba Network, it responds with a synchronous cXML document that contains one of the following status codes: ● 2xx, indicating that Ariba Network accepted the document. ● 4xx, indicating that a permanent error has occurred and has been logged. ● 5xx, indicating that a transient error occurred. The Ariba Network Adapter for SAP NetWeaver then re-sends the document with the same payload ID for the specified number of retry attempts. Buyers can specify multiple delivery schedules for a line item in a purchase order or change purchase order that they send suppliers on Ariba Network. This allows buyers to specify multiple schedule lines for a line item that needs to be supplied repeatedly over a period of time. For more information, see Schedule Lines in Purchase Orders and Change Purchase Orders [page 143]. Buyers can also send a scheduling agreement release as a purchase order (release order) to a supplier when they require material or non-material items for an extended period of time. These scheduling agreement releases contain schedules lines with details on the line item, quantity, and the different delivery dates for an extended period of time. For more information, see Scheduling Agreement Release Integration Scenario [page 153].
Support for Service Purchase Orders Purchase orders with lines that specify category D are considered service purchase orders on Ariba Network. In the transformed OrderRequest document for a service purchase order, for all lines with category D, the ItemOut element includes a requiresServiceEntry=“yes” attribute. Suppliers must create service sheets for those lines to describe both services and material goods delivered for the order. Unplanned service lines must specify a maximum amount. SAP NetWeaver 7.3 or 7.4 and SAP ERP 6.0, EhP 4 and higher enables transmission of service purchase orders with service line-items in up to five levels of hierarchy (1 parent and 4 child levels) from SAP ERP to Ariba Network.
16
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
When a purchase order item of type service contains line items with a hierarchy, SAP ERP provides line item numbering information that reflects both a service item's parent and outline numbers and the service item number. The adapter transmits this information to Ariba Network for both purchases orders and change orders. Any changes or deletions made to a top-level service line or to the service items below a top level service line, including price and quantity limits, are transmitted to Ariba Network. For more information on configuring support for line level hierarchies in service purchase orders, see Configuring Support for Line Level Hierarchies in Service Purchase Orders [page 321].
Note Ariba Network does not support service lines in blanket purchase orders.
Support for Schedule Lines in Purchase Orders and Change Purchase Orders
You can specify multiple delivery schedules for a line item in a purchase order or change purchase order that you send suppliers on Ariba Network. This allows you to specify multiple schedule lines for a line item that needs to be supplied repeatedly over a period of time. Each line item can have different quantities and multiple delivery dates and time in a purchase order. To maintain the different delivery schedules for a line item correctly, each schedule line is numbered sequentially in the purchase order and sent to Ariba Network. When a purchase order containing changes to the schedule lines is sent to a supplier, the newly added, deleted, or edited schedule lines are highlighted in the change purchase order on Ariba Network. For more information, see Schedule Lines in Purchase Orders and Change Purchase Orders [page 143].
Order Confirmation Order confirmations are downloaded from Ariba Network to the Ariba Network Adapter for SAP NetWeaver using the pull document transmission method described in cXML Adapter Parameters [page 391]. For more information, see the Ariba Network Integration Guide. For more information on the order confirmation integration scenario, see Order Confirmation Integration Scenario [page 93].
Ship Notice Ship Notices are downloaded from Ariba Network to the Ariba Network Adapter for SAP NetWeaver using the pull document transmission methods described in cXML Adapter Parameters [page 391]. For more information, see the Ariba Network Integration Guide. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
17
Service Sheet A service sheet is created against a purchase order containing service type line items. Service sheet and service sheet response transactions are supported for SAP NetWeaver Versions 7.1 and 7.3. Service sheets are downloaded from Ariba Network to the Ariba Network Adapter for SAP NetWeaver using the pull document transmission method described in cXML Adapter Parameters [page 391]. For more information, see the Ariba Network Integration Guide. Buyers can receive service sheets containing the following: ● Service sheets with or without hierarchy ● Service sheets containing unplanned service lines. Buyer administrators can change quantity and unit price in the service sheets. To do this, the following is required in the purchase order with service type line items: ● In the Services tab, the Price Change Allowed check box must be enabled at the line item level for lines that support changes to the unit price. ● The Unlimited Overfulfillment option must be selected to support the quantity changes to line items. ● The Overfulf. Tolerance option must be selected. In the Limits tab, enter the expected value in the the Overall Limits must be specified to allow suppliers to add unplanned line items.
Note ● To support changes to unit price in service sheets, buyers must also enable the rule Allow suppliers to change the unit price on service sheets on Ariba Network. ● An integrated supplier can send accounting assignment information in the service sheets to a buyer using Ariba Invoice Professional and this is processed in the SAP ERP system. The accounting information available in the service sheets is used by the SAP ERP system. However, Ariba Network Adapter for SAP NetWeaver does not validate the accounting information available in service sheets against the account information. When a suppliers adds an ad-hoc line item containing the unit of measure(UOM), the Ariba Network Adapter for SAP NetWeaver does not processes the unit of measure correctly. The Unit of Measure field displays “***.” To avoid this, buyers must ensure that they set up the Unit of Measure configuration in the CUNI transaction on their SAP ERP system. For example, if the unit of measure used on the ERP system is PCE, buyers must maintain PCE as the internal unit of measure in the CUNI transaction. In some cases, the SAP ERP system fails while processing multiple service sheets for the same purchase order service type item. To prevent failures while processing multiple service sheets, Ariba recommends that you specify a time-out duration. For more information, see Specifying Time-Out Intervals for Processing Service Sheets [page 327]. SAP ERP buyers using Ariba Network Adapter for SAP NetWeaver can receive and process service sheets with up to five-levels hierarchy (one parent item and four child line items) created against purchase orders containing service type line items from Ariba Network. Suppliers must create service sheets containing only one parent line item from a purchase order with multiple service type line items. Service sheets against the purchase order with service type line items can have both planned and unplanned line items.These service sheets can also contain attachments.The service sheet must contain at least one-level service child line item in the hierarchical structure.
18
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
Direct Invoicing of Purchase Order Service Items The Ariba Network Adapter for SAP NetWeaver supports integration of the service sheets auto-generated on Ariba Network for the invoice containing service type line items created by the supplier and sent to the SAP ERP system. See Invoice [page 20] for more information. Prerequisite [page 19] Limitations [page 19]
Prerequisite To send and receive service sheets with hierarchy, buyer administrators must do the following: ● Apply the SAP Note 1832628 BAPI for service PO Entry Sheet and Contract: ESLL-EXTROW that supports the line numbers available in the service sheets received from Ariba Network to be maintained in the same numbered sequence on the SAP ERP system. ● Buyers must use the service-based invoicing functionality on the SAP ERP system. The GR based IV and S based IV indicator on the Invoice tab of the purchase order containing service lines. This option is required to create separate line items for each service line in the invoice created on the SAP ERP system. When a buyer enables only the GR based IV indicator, the quantity in the service sheet and invoices are not displayed in the Qty field as the quantity is aggregated. ● Apply the SAP Note 1090663 - EDI: Multiple reference to same purchase order item. This note is applicable only a buyer creates one invoice against multiple service sheets and the corresponding purchase order does not have the S based IV indicator enabled.
Limitations Ariba Network Adapter for SAP NetWeaver does not support the following: ● Taxes ● Charges and Allowances ● Shipping and Handling charges ● In the cXML for a service sheet sent from Ariba Network, the adapter does not support the operations = “update” and “Delete”. ● Although the service purchase order contains multiple line items, suppliers must create service sheets with only one parent line item. The SAP ERP system does not process service sheets containing more than one parent line item against a purchase order containing service type line items. ● Services sheets cannot contain adhoc line items (unplanned line items). Suppliers can add unplanned line items only if the buyers maintains a value in the “Overall Limit“ field in the service purchase order created on the SAP ERP system. However, the maximum amount allowed for unplanned line items on service sheets is based on the maximum amount allowed by buyer on Ariba Network and the Overall Limit maintained on the SAP ERP system. The maximum allowed limit to create invoices is based on the shipped or received quantity. ● The Final Entry indicator option specified in service sheets on the SAP ERP system is not supported on Ariba Network. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
19
● Ariba Network allows changes to unit of measure in service sheets, but SAP ERP does not support changes to the unit of measure in service sheets.
Invoice Invoices are downloaded from Ariba Network to the Ariba Network Adapter for SAP NetWeaver using the pull document transmission methods described in cXML Adapter Parameters [page 391]. For more information, see the Ariba Network Integration Guide.
Support for Non-PO Invoices and Credit Memos
In addition to PO-based invoices, invoice supports the following scenarios: ● Non-PO based invoice containing accounting information ● Header-level credit memos against purchase orders created on Ariba Network and then reconciled in the Ariba procurement solution. ● Header-level credit memos against non-POs created in the Ariba procurement solution.
Note ● To post non-PO invoices and credit memos to SAP, the segment, /ARBA/ACCOUNT_DATA, has been populated with data corresponding to the distribution (accounting information in cXML) data. ● To post this information to the General Ledger (G/L) account directly, you must implement a user exit. ● (For users upgrading from version 1.4 of the Ariba Network Adapter for SAP NetWeaver to version 10s2 only.) To post non-PO invoices successfully, you must delete and reload the IDoc metadata from the NetWeaver transaction IDX2 after the installation of the upgrade package. For more information on implementing the user exit, see cXML Adapter Parameters [page 391].
Support for Discounts in Invoices
Invoice supports the following discount scenarios: ● Discounts entered at the header and line-level on a PO based invoice ● Discounts entered at header and line-level on a non-PO based invoice ● Discounts entered at header and line on a line-level credit memo
Note As SAP does not have a provision to send the discount information, the discount amount is adjusted in the line amount.
20
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
Tax Handling for Different Types of Invoices Invoice supports the following tax handling scenarios: ● PO based invoices, PO based line-level credit memos, and header-level credit memos (either PO based or nonPO based) use the data in segments E1EDK04/E1EDP04 and query the OBCD transaction to determine the tax applicable. ● Non-PO based invoices, non-PO line-level credit memos, and shipping or handling lines with tax use the tax code sent as extrinsic in the cXML directly.
Enabling Support for Shipping and Handling Charges for Invoices Ariba Network Adapter for SAP NetWeaver supports the export of shipping and handling charges to SAP. This feature is supported in the following cases: ● Shipping and handling charges with taxes added as service lines Shipping and handling charges with taxes added as service lines is sent to SAP as direct posting to General Ledger (G/L) accounts. ● Shipping and handling charges added without any tax is sent in the Invoice Detail Summary only. Shipping and handling charges is added and sent to SAP as unplanned delivery cost. The IDoc type used for the Invoice transaction has been changed from the basic INVOICE02 to /ARBA/INVOICE to support the posting of shipping and handling charges with tax added as service lines. The segment, /ARBA/ACCOUNT_DATA, has been populated with data corresponding to the shipping and handling charges service lines with taxes. To post this information as mentioned above either to the G/L account directly or to unplanned delivery cost, a user exit must be implemented. For more information about implementing the user exit, see cXML Adapter Parameters [page 391].
Service Invoice Buyers can create invoices against purchase order containing service type line items. Suppliers create service invoices based on approved service sheets. The integration of service invoices between SAP ERP and Ariba Network is supported on SAP NetWeaver versions 7.1 and 7.3. SAP ERP buyers using Ariba Network Adapter for SAP NetWeaver can receive and process invoices with up to fivelevels hierarchy created against purchase orders containing service type line items from Ariba Network. These invoices can also contain attachments. Buyers can receive invoices containing the following: ● Invoices with or without hierarchy ● Invoices containing unplanned service lines.
Note The invoices must contain at least one-level service child line item in the hierarchical structure.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
21
Prerequisite To send and receive invoices with hierarchy, buyer administrators must do the following: ● Buyers must use the service-based invoicing functionality on the SAP ERP system. The GR based IV and S based IV indicator on the Invoice tab of the purchase order containing service lines. This option is required to create separate line items for each service line in the invoice created on the SAP ERP system. When a buyer enables only the GR based IV indicator, the quantity in the service sheet and invoices are not displayed in the Qty field as the quantity is aggregated. ● Apply the SAP Note 1090663 - EDI: Multiple reference to same purchase order item. This note is applicable only a buyer creates one invoice against multiple service sheets and the corresponding purchase order does not have the S based IV indicator enabled.
Summary Invoice The Ariba Network Adapter for SAP NetWeaver supports summary invoices for multiple purchase orders. Integrated suppliers can send summary invoices for multiple purchase order containing material items and nonmaterial purchase orders having the standard item category.
Note Ariba Network Adapter for SAP NetWeaver does not support summary invoices for service purchase orders. Summary Invoices created against multiple purchase orders contain the following: ● Multiple line items from multiple purchase orders ● Line items containing complete and partial quantities
Direct Invoicing of Purchase Order Service Items Buyers can directly invoice a purchase order having the service type items. The Ariba Network Adapter for SAP NetWeaver supports integration of the service sheets auto-generated on Ariba Network for the invoice containing service type line items created by the supplier and sent to the SAP ERP system. Auto-generated service sheets for invoices created against purchase orders with service type items contain the following: ● Line items with or without child items ● Line items with taxes For more information, see Direct Invoicing of Purchase Order Service Items [page 325] .
Prerequisite To receive invoices created against purchase order service lines, buyer administrators must use the service-based invoicing functionality on the SAP ERP system. The S.-Based IV indicator on the Invoice tab of the purchase order
22
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
containing service lines. This option is required to create separate line items for each service line in the invoice created on the SAP ERP system.
Limitations Although the invoice for the service sheets contains taxes and other charges, Ariba Network Adapter for SAP NetWeaver does not process the taxes in the service sheet.
ERP-Initiated Invoice Invoices created on an SAP ERP system is called an ERP-Initiated invoices or ERP CC invoices. These invoices created in SAP ERP are then uploaded to Ariba Network. Uploads can be scheduled either on a daily basis, or on a weekly basis. The Ariba Network Adapter for SAP NetWeaver also supports transmission of invoices that are created through self billing. Invoices are automatically created for purchase orders that have been marked for self-billing and also have a goods receipt created against the purchase order. SAP ERP buyers can send ERP-initiated or CC invoices from the SAP ERP system to Ariba Network using the IDOC transmission method. Customers can send SAP ERP MM and FI invoices using the IDOC. ERP-Initiated Invoices Using the IDOC Transmission Method [page 23] Enabling Quick Enablement for ERP-Initiated Invoices [page 25] ERP-Initiated Invoice with Cross Company Codes [page 26]
ERP-Initiated Invoices Using the IDOC Transmission Method SAP ERP buyers can send ERP-initiated or CC invoices from the SAP ERP system to Ariba Network using the IDOC transmission method. Buyers can send SAP ERP MM and FI invoices using the IDOC. Buyers can use the GSVERF03 IDOC to send MM invoices and the FIDCCP02 IDOC to send FI invoices. The Ariba Network Adapter for SAP NetWeaver also supports transmission of invoices that are created through self billing. Invoices are automatically created for purchase orders that have been marked for self-billing and also have a goods receipt created against the purchase order. You can use the IDOC method for the following: ● Transmission of invoices created through ERS(Evaluated Receipt Settlement) ● Transmission of manually created PO-based invoices against multiple purchase orders (Summary invoices) with single and multiple line items. The line-items can contain material, advanced pricing details, and unplanned delivery cost items ● Transmission of manually created non-PO invoices containing material, GL account, contract, internal order, WBS elements and cost center items ● Transmission of invoices created through the Invoice plan containing both periodic and partial items Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
23
● Transmission of credit memos for FI and MM invoices The following are the IDOC methods that customers can use to send ERP-initated invoices from SAP ERP systems: Type of Invoice
IDOC
Extended IDOC Type
ERS (Evaluated Receipt Settlement)/ MIRO/ MM
GSVERF03
/ARBA/GSVERF03
FI
FIDCCP02
/ARBA/FIDCCP02
The /ARBA/ GSVERF03 and /ARBA/ FIDCCP02 IDOC types have been enhanced to include new segments to get additional information on the Name, Street, and City for the vendor. Customers can customize and add segments to include additional information for vendors. Prerequisites for Using IDOCs for ERP-Initiated Invoices [page 24] Limitations Using the IDOCs [page 25]
Related Information ERP-Initiated Invoice Integration Scenario [page 167] Configuring ERP-Initiated Invoices to Use the IDOC [page 331]
Prerequisites for Using IDOCs for ERP-Initiated Invoices The following describes the prerequisites and changes that buyers must ensure while sending the ERP-initiated invoices using the IDOC transmission method:
Prerequisite To send ERP-initiated invoices through the IDOC, buyer administrators must do the following: ● Make the necessary configurations on their SAP ERP system and configure the integration scenario on their SAP PI. For more information, see ERP-Initiated Invoice Integration Scenario [page 167] and Configuring ERPInitiated Invoices to Use the IDOC [page 331] .
Backward Compatibility This feature is not compatible with the releases prior to Cloud Integration Release 6.0. Customers must ensure that they make the necessary changes to remove the previous ABAP proxy programs that were used to process the ERP-initiated invoices. Starting Ariba Cloud Integration Release 6.0, the ERP_INV_PROCESSED_STATUS parameter is no longer required for ERP-initiated invoices.
24
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
To use the IDOCs, you must specify the Transfer IDoc immediately option in the Output Mode section on the Generate Partner Profile page. If you are using the IDOC, you must ensure that you do not use the ERPINV_PROCESSES_CHK parameter.. Buyers must ensure that they make the necessary changes to remove the previous ABAP proxy programs to process the ERP-initiated invoices. The namespace http://ariba.com/xi/ASN/ERPInvoiceProxy no longer exists. Customers using Ariba Cloud Integration Release 5.0 and lower must continue to maintain the ERP_INV_PROCESSED_STATUS parameter for ERP-initiated invoices. To continue using the ABAP proxy program, you must ensure that you use the ERPINV_PROCESSES_CHK parameter. This parameter supports extracting all the ERP invoices that are stored in the /ARBA/AN_ERPINV table.
Limitations Using the IDOCs Ariba Procurement Solution integrated for SAP does not support the following while processing ERP-initiated invoices and FI invoices using the IDOC transmission method: ● Transmission of debit memos for FI and ERP-initiated invoices ● The
element is only sent when the invoice contains unplanned delivery cost. ● The SubTotal Amount field does not include the tax amount. Customers can use customer exits to include the tax amount in the Sub Total Amount field. ● Payment term values are not sent if the payment terms is "Immediate" with no tier discounts. ● The Email name element is no longer sent in the Contact element. ● Accounting information is no longer sent for FI and ERP-initiated invoices.
Enabling Quick Enablement for ERP-Initiated Invoices Quick enablement is supported for the ERP-initiated invoice transaction. As a result, when an ERP-initiated invoice is sent to Ariba Network, supplier enablement is initiated even if no relationship is maintained in Ariba Network for SAP Vendor and AN Vendor. Quick enablement is achieved by adding the Email ID to the relevant structures in SAP NetWeaver PI and the SAP ERP system.
Note Email ID must be maintained in Vendor Master and the same email ID is passed to SAP NetWeaver PI. To enable quick enablement, ensure that you have: ● Imported the AribaNetworkAdapterSAPNetweaver.Design.tpz file into your SAP NetWeaver PI system. ● Downloaded the relevant SAP transport requests from connect.ariba.com and imported them into your SAP ERP system.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
25
ERP-Initiated Invoice with Cross Company Codes You can create a PO-based or non PO-based ERP-initiated invoice with cross company codes. ● PO-based invoice You can create an ERP-initiated invoice with company codes that are different to the ones you specified in the corresponding PO. SAP restricts purchase orders and the related PO invoices to a single sending company code. However, it is possible to book the liability to a different paying company code. ● Non PO-based invoice You can create an ERP-initiated invoice with company codes that are different to the ones you specified for the vendor. In this case, the sending company codes may vary in addition to the paying company code.
Note The handling of shipping and freight charges is same for ERP-initiated invoices and ERP-initiated invoices with cross company codes. The planned and unplanned shipping charges are handled as follows: ● Planned shipping and freight charges are sent as a separate material line item. ● You can enter shipping and freight charges in the purchase order itself or while creating an ERP-initiated invoice. If you have not specified these chargers during the creation of the purchase order, you can specify these charges while creating the invoice. When you include these charges while creating an ERP-initiated invoice, then such charges are called unplanned shipping and freight charges. When you view such an invoice in Ariba Network, such unplanned shipping and freight charges are not displayed separately as a line item. Instead, the shipping and freight charges amount is added to the gross amount of the ERP-initiated invoice.
Limitations for Non PO-Based ERP-Initiated Invoice with Cross Company Codes For non PO-based ERP-initiated invoices, the tax amount is available at the header level only. This is a limitation on the SAP side.
Limitations for PO-Based ERP-Initiated Invoice with Cross Company Codes ● In SAP, you can create purchase orders that relate to a single sending company only. However, some companies have configured SAP to ensure that credit to a vendor account is performed using a separate paying company code. In this case, the SAP FI accounting document for vendor posting does not include information about the purchase order. Although, the reference to the PO ID may be useful, for performance reasons, Ariba has not added the logic to the RFC to send the purchase order number in the invoice. As a result, when you view such an invoice in Ariba Network: ○ The PO ID is not displayed as part of the invoice. ○ The quantity is displayed as 1 and unit price is displayed as being equal to the line amount.
Note The SAP RFC for ERP-initiated invoices, like the other SAP RFCs, is intended to accelerate your IT department’s effort in building appropriate integration between SAP and Ariba system. Therefore, if
26
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
your business process requires you to include the PO ID in the invoice, you must work with your IT department to add the appropriate logic to the RFC. ● When creating an ERP-initiated invoice in SAP, you can provide the tax amount for each line item. However, when you view such an invoice in Ariba Network, the tax is displayed at the header level as the sum of all the line item tax amounts. ● If you create an ERP-initiated invoice with multiple POs, then such an invoice is extracted and displayed as a non PO-based invoice and as a result, when you view such an invoice in Ariba Network: ○ The PO ID is not displayed as part of the invoice. ○ The invoice contains only one line item. ○ Quantity is displayed as 1. ○ Unit price and total invoice amount of the single line item are displayed as the invoice subtotal excluding freight and tax (if available at header level).
Note The data mapping workbook for the ERP-initiated invoice transaction is available in connect.ariba.com -> Ariba Network Adapters -> Ariba Network Adapter for SAP NetWeaver -> Under Integration Tools ->
Data
Transformation . Enabling ERP-Initiated Invoices with Cross Company Codes [page 27]
Enabling ERP-Initiated Invoices with Cross Company Codes To enable creation of an ERP-initiated invoice with cross company codes, you must import the relevant SAP transport provided by Ariba into your SAP ERP system. To do this, you must download the SAP transports (available in a ZIP file) from Connect (http://connect.ariba.com), open the ReadMe.txt that is available in the ZIP file, and check the transport number that is relevant and import it.
Invoice Status Update Invoice status updates are sent by buying organizations to inform Ariba Network and suppliers of the status of invoice reconciliation. Buyers send StatusUpdateRequest documents to set invoice status to processing, reconciled, paying, paid, rejected, invalid, parked or parked invoices that have been deleted. Ariba Network posts the documents to the URL that suppliers return in their cXML ProfileResponse. StatusUpdateRequest documents can identify invoices in two possible ways: through either a DocumentReference or an InvoiceIDInfo element. For more information about invoice status updates, see Configuring Invoice Status Updates [page 301] and the Ariba cXML Solutions Guide.
Receipt Requests The cXML ReceiptRequest document defines the receipt information of a purchase order or master agreement with item details. A receipt line is a ReceiptItem element with a receipt line details. Buyers generate receipts and Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
27
address them to suppliers. However, Ariba Network routes them to Ariba Invoice and Payment. When receipt data is successfully posted in Ariba Network, Buyers can see the receipts in their online Outbox.
Note The receipt records are retrieved from SAP ERP on the basis of the date the query to fetch the records was last run as well as the material document number.
Payment Remittance Request Buyers can send a PaymentRemittanceRequest to notify suppliers when payment is made.
Scheduled Payments and Dynamic Discounting Buying organizations use scheduled payments, that is, PaymentProposalRequest documents, to tell Ariba Network and their suppliers about planned payments. These documents list scheduled payment dates, discount amounts, and net amounts. Scheduled payments are used for information by default, but they can also be used for Dynamic Discounting. Dynamic Discounting allows buying organizations to pay suppliers early in exchange for discounts. Buying organizations send proposed payment information to Ariba Network in PaymentProposalRequest documents containing a special Extrinsic element called immediatePay. If suppliers choose schedule payments for early settlement, Ariba Network sends the scheduled payments back to the buying organization through the Ariba Network Adapter for SAP NetWeaver. Updated PaymentProposalRequest documents are then used to update the payment schedule and discount amount in the buying organization’s SAP system. For more information about scheduled payments, see the Ariba cXML Solutions Guide. For more information about Dynamic Discounting, see the Ariba Network Buyer’s Guide.
Payment Remittance Advice Request Payment Remittance Advice requests are sent by Ariba Network to notify suppliers and SAP about external payment made directly from Ariba Network. It sends PaymentRemittanceAdviceRequest documents to suppliers as well as SAP to create an accounting document.
cXML Adapter Document Transmission The Ariba Network Adapter for SAP NetWeaver always uses HTTPS Post to send documents to Ariba Network. The Ariba Network Adapter for SAP NetWeaver initiates the cXML GetPending transaction to pull inbound business documents. The GetPending transaction allows the SAP ERP system to receive documents from Ariba Network through a data pull.
28
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
The GetPending transaction is scheduled using the getPendingInterval parameter defined for each inbound transaction. Ariba Network responds with a GetPendingResponse document that includes zero or more DataAvailableMessage elements containing the internal ID of any waiting documents. For more information about document transmission methods, see the Ariba Network Integration Guide. For details on downloading this guide, see Downloading the Ariba Network Integration Guide from Connect [page 389].
Setting Up the Ariba Network Adapter for SAP NetWeaver Setting up the Ariba Network Adapter for SAP NetWeaver involves the following high-level steps: 1. Verifying that all the software and connectivity requirements are in place. For more information, see Installation Requirements [page 13]. 2. Setting up and configuring the cXML Adapter. For more information, see About Deploying the cXML Adapter [page 34]. 3. Configuring the System Landscape Directory. For more information, see About Configuring the System Landscape Directory [page 61]. 4. Configuring transaction processes. For more information, see About Configuring Transaction Processes [page 65]. 5. Configuring the SAP ERP system. For more information, see Configuring Your SAP ERP System [page 13]. 6. Testing the configuration. For more information, see Testing the Adapter [page 13].
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
29
Configuring the Ariba Network Adapter for SAP NetWeaver
Installation Requirements [page 30] About Configuring Security Certificates [page 32] About Deploying the cXML Adapter [page 34] About Configuring the cXML Adapter [page 45]
Installation Requirements Before you start up the set-up process verify that you have the required software and connectivity requirements. The information in this topic is applicable to the Ariba Network Adapter for SAP NetWeaver. For information on the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On, see Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On [page 30].
Supported SAP Netweaver PI Versions The following table lists the Ariba Network Adapter for SAP NetWeaver versions and the supported SAP Netweaver PI versions that they can be deployed on: Ariba Network Adapter for SAP NetWeaver Version
Supported SAP Netweaver PI Versions
Cloud Integration 1
SAP Netweaver PI 7.1 SAP Netweaver PI 7.3
Cloud Integration 2 or higher
SAP Netweaver PI 7.1 SAP Netweaver PI 7.3 SAP Netweaver PI 7.4
Supported SAP ERP Versions The Ariba Network Adapter for SAP NetWeaver supports SAP ERP versions starting with SAP ERP 6.0 up to SAP ERP 6.0 EHP 7. For information about the platforms that the SAP NetWeaver suite supports, see the following SAP NetWeaver section on the SAP Service Marketplace: service.sap.com > SAP NetWeaver > SAP NetWeaver PI 7.X > Availability.
30
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
Ariba Network Requirements
Ensure that you have the following Ariba Network requirements before installing the Ariba Network Adapter for SAP NetWeaver: ● A valid, configured Ariba Network Buyer account. For more information about configuring your Ariba Network Buyer account, see the Ariba Network Buyer Administration Guide. ● An Ariba Network supplier relationship, including an ANID-to-Private ID mapping. For more information about creating a supplier relationship, see the Ariba Network Integration Guide. ● If the Ariba Network Buyer account is configured to use digital certificate authentication, then a valid Secure Socket Layer (SSL) client certificate from one of Ariba Networks trusted Certificate Authorities is required. For more information, see About Configuring Security Certificates [page 32]. For more information about obtaining a digital certificate, see the Ariba cXML Solutions Guide. ● Ariba Network requires that all communication between the Ariba Network Adapter for SAP NetWeaver and Ariba Network travel over the internet using Secure HyperText Transfer Protocol (HTTPS), a secure protocol that encrypts communication before transmission. For more detailed information about internet connectivity requirements, see the Ariba Network Integration Guide. For more information about how to enable secure communications through a proxy server, see cXML Adapter Parameters [page 391]. ● The Ariba Network’s Certificate Authorities certificates are stored in the SAP NetWeaver PI Keystore. The cXML Adapter uses the certificates stored in the SAP NetWeaver PI Keystore to connect to Ariba Network.
Installing the Network Adapter Files Context
To install the Ariba Network Adapter for SAP NetWeaver, you need the relevant archive file which is available on Ariba’s support interface, Ariba Connect.
Procedure
1. Login to Ariba Connect (http://connect.ariba.com) and click the Download Software tab. 2. Click I Accept to accept the Ariba Software Access Agreement. 3. Select as the Product Line and the relevant Product Version. 4. Navigate to or search for the relevant file and click the download icon to download the archive file. 5. Import the relevant SAP transport requests into your SAP ERP system. 6. Import the AribaNetworkAdapterSAPNetweaver.Design.tpz file into your SAP NetWeaver PI system.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
31
Results The archive ZIP files contain the following components: Product definition files
AribaNetworkAdapterSAPNetweaver.SoftwareCatalog.zip
Mapping design and Integration configuration files
AribaNetworkAdapterSAPNetweaver.Design.tpz
cXML Adapter files
AribaNetworkAdapterSAPNetWeaver.sca
Metadata definition files
AribaNetworkAdapterSAPNetweaver.xml
Software catalog files
CacheCatalog.xml CanonicalCatalog.xml
SAP configuration transport files
The required SAP transport files.
About Configuring Security Certificates Install security certificates in a Java JRE keystore or truststore.
Related Information Importing Security Certificates into the Java JRE Keystore [page 32] Importing Security Certificates into the Java JRE TrustStore [page 33] Installing Client Certificates on Ariba Network [page 34]
Importing Security Certificates into the Java JRE Keystore Context If you did not configure the trustKeyStore parameter in the Channels.Config.properties file for the purchase order transaction, then you need to import the certificates of the domains on which attachments are hosted into your Java JRE keystore.
Procedure 1. On the system hosting the Ariba Network Adapter for SAP NetWeaver, determine the path for your Java home directory. Enter the following command from the command line:
32
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
echo $JAVA_HOME 2. Go to your JAVA_HOME/bin directory and issue the following command to determine the location of the keystore in your JAVA_HOME directory: keytool -list -keystore /jre/lib/security/cacerts The output from this command should list multiple certificates in the keystore. If the output does not list any certificates, then this is probably not the correct keystore. 3. Copy the required domain certificates to your JAVA_HOME/bin directory. 4. Set your working directory to your JAVA_HOME/bin directory. 5. Import each certificate. Enter the following command: keytool -import -trustcacerts -alias alias -file domain_certificate_file -keystore JAVA_HOME/jre/lib/security/cacerts Where: alias is a name, or alias, you want to use to refer to this certificate. domain_certificate_file is the name of the domain certificate file, such as sys123.cer. 6. The keytool utility prompts for you for the keystore password. Enter the password. 7. Repeat steps 5 and 6 for additional certificates that you need to import into the keystore.
Importing Security Certificates into the Java JRE TrustStore Context
If you configured the trustKeyStore parameter in the ChannelsConfig.properties file for the purchase order transaction, then you need to import the certificates of the domains on which attachments are hosted into your trustKeyStore file.
Procedure
1. On the command line, enter: keytool -import -trustcacerts -alias alias -file domain_certificate_file -keystore trustStore_path Where: alias is a name, or alias, you want to use to refer to this certificate. domain_certificate_file is the name of the domain certificate file, such as sys456.cer. trustStore_path the trustStore path configured for the purchase order communication channel. 2. Repeat the above step for additional certificates that you need to import into the truststore file.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
33
Installing Client Certificates on Ariba Network Context After you have imported the security certificates, you must configure your Ariba Network buyer account to store the client certificate.
Procedure 1. Obtain a signed digital certificate issued for the client. The certificate must be issued from a Certificate Authority (CA) trusted by Ariba. For a list of CAs trusted by Ariba or to add a CA to Ariba’s trusted CAs, contact your Ariba Support Representative. 2. Log in to your Ariba Network account. You must have the account administrator privileges to make this change. 3. ClickManage Profile in the upper left corner of the home dashboard. The Configuration page opens. Ariba Network displays the Configuration page 4. Click cXML Setup. 5. In the Authentication Method section, choose the Certificate authentication method from the Select an authentication method pull-down menu. 6. Copy the certificate, starting with "-----BEGIN CERTIFICATE-----" and ending with "-----END CERTIFICATE-----". Paste the signed client certificate into the Certificate text box. 7. You can also use a backup digital certificate. Ariba Network uses the backup certificate if your primary certificate becomes invalid. Backup certificates are useful when your primary certificate expires or when you need to perform certificate maintenance. 8. Click Save.
Note Digital certificates expire after a predetermined period of time. It is your responsibility to periodically obtain updated certificates from your certificate authority and install them on Ariba Network. You can also use a backup digital certificate. Ariba Network uses the backup certificate if your primary certificate becomes invalid. Backup certificates are useful when your primary certificate expires or when you need to perform certificate maintenance. 9. Click OK.
About Deploying the cXML Adapter The Ariba Network Adapter for SAP NetWeaver relies upon the cXML Adapter, which conforms to the JCA specification and implements the cXML transport protocol.
34
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
If your version of SAP netweaver PI is prior to PI 7.3 EHP1, use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI. From SAP netweaver version PI7.3 EHP1 onwards you must use the SAP Software Update Manager (SUM) tool to deploy the adapter. For more information on how to install or upgrade using the SUM tool, contact your SAP systems administrator.
Related Information Deploying the cXML Adapter Using JSPM [page 35] Upgrading the cXML Adapter Using JSPM [page 38] Installing Additional Resources for the cXML Adapter [page 42] Undeploying the cXML Adapter using the Textconsole [page 43] Deploying the cXML Adapter Using the textconsole [page 43]
Deploying the cXML Adapter Using JSPM Prerequisites In SAP NetWeaver PI, you have placed the .SCA file in the required location.
Procedure 1. Start JSPM.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
35
2. Enter your user name and password and click Log On.
3. Select Business Packages (advanced user only) and click Next.
4. Select the business package you want to deploy and click Next. The Queue status appears.
36
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
5. Click Start. The Deploy Queue screen appears.
The Completed screen appears.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
37
6. Click Exit.
Results The cXML Adapter is successfully deployed. You must start the cXML Adapter from the SAP NetWeaver Administrator console. You cannot undeploy the adapter using the JSPM. For information on how to undeploy the adapter, see Undeploying the cXML Adapter using the Textconsole [page 43].
Upgrading the cXML Adapter Using JSPM Procedure 1. Start JSPM.
38
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
2. Enter your user name and password and click Log On.
3. Select Single Support Packages and Patches (advanced user only) and click Next.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
39
4. Select the support package you want to apply and click Next. The Queue status appears.
40
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
5. Click Start. The Deploy Queue screen appears.
The Completed screen appears.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
41
6. Click Exit.
Results
The cXML Adapter is upgraded successfully.
Installing Additional Resources for the cXML Adapter Context
The validation engine uses the following files to resolve and identify the location of the DTDs related to the exchanged cXML documents: ● CacheCatalog.xml ● CanonicalCatalog.xml
Procedure
To install these files, copy the files to the following folder:Install_Root/etc/catalog/.
42
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
Undeploying the cXML Adapter using the Textconsole Context
You must use the textconsole script to undeploy the cXML adapter.
Procedure
1. Set your working directory to SAP_instance\j2ee\console. 2. Run textconsole.bat or textconsole.sh. The telnet console appears. 3. Login with the relevant admin user. 4. Enter the following command at the telnet prompt: >undeploy name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_undeploy_error=stop Undeploy Settings: ○ on_undeploy_error=stop ○ on_prerequisite_error=stop ○ workflow=normal If there is an offline undeployment, the telnet connection to host might be lost and the following message appears: Processing undeployment operation, please wait... name: 'com.ariba.asc.sap.netweaver.xiadapter.ra', vendor: 'ariba.com', location: 'null', version: 'null', status: 'Success', description: '', sda: 'name: 'com.ariba.asc.sap.netweaver.xiadapter.ra', vendor: 'ariba.com', location: 'SAP AG', version: '3.0.1420051114090313.0000', software type: 'J2EE', dependencies: '[]'' >
Deploying the cXML Adapter Using the textconsole Context
Run the following at the Telnet prompt: deploy name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_deploy_error=stop Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
43
For example: deploy /usr/sap/LP3/DVEBMGS00/j2ee/deployment/scripts/ AribaNetworkAdapterSAPNetweaver.sca name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_deploy_error=stop
Note To upgrade to the latest version of the Ariba Network Adapter for SAP NetWeaver, you must first undeploy the existing adapter and then deploy the latest version that you have downloaded from https://connect.ariba.com .
Setting Log Configuration Parameters for the cXML Adapter Context
Set log configuration parameters so that the cXML Adapter sends log entries to a separate file.
Procedure
1. Login to the SAP NetWeaver PI log administration section at http://XI_server_hostname/XI_port/nwa/logs. 2. Click the Log Configuration link. 3. Select Tracing Locations from the Show drop down list. 4. Select the node (package) com ariba asc , to set the logging level to log the complete adapter processing information, or select CXMLSender under connector.cxml.util to set the logging level to log only the exchanged messages. 5. Change the severity level from Error to Info / Debug in the Severity drop-down list, and then click Save Configuration in the toolbar.
Note The log level can remain Error when running in a production environment, but Ariba recommends that you change the log level to Info. You can also find out about the version of the Ariba Network Adapter for SAP NetWeaver.
44
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
About Configuring the cXML Adapter To allow the cXML adapter to run correctly, you must configure parameters for the Communication Channels for different business scenarios. This configuration is done at a later stage, during the configuration of Integration Scenarios in the Integration Directory. For more details about how to create the Communication Channels, see the Communication Channels Configuration procedure for each scenario in the Configuring Integration Scenarios [page 30] section. For a description of the parameters and instructions for how to configure retry attempts, see cXML Adapter Parameters [page 391].
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
45
Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
About Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver [page 46] cXML Interfaces Supported in the Ariba Cloud Integration Releases [page 47] Features Available in the Ariba Cloud Integration Releases [page 48] Steps to Install the Ariba Network Adapter for SAP NetWeaver PI [page 51] Installing the SAP ERP Transports [page 51] Upgrading to a Higher Version of the Ariba Network Adapter for SAP NetWeaver Transports [page 52]
About Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver To integrate the SAP NetWeaver PI with Ariba Network, Ariba recommends that you install a new version or upgrade to a higher version of Ariba Network Adapter for SAP NetWeaver. Starting Ariba Cloud Integration 6.0, all the transport files for Ariba Network Adapter for SAP NetWeaver have been merged to a single transport file for easier installation. Customers who are using versions prior to Ariba Cloud Integration 6.0 continue to install the different transport files available in the transport zip file. If you are a new customer, you must install the latest version of the transport files for Ariba Network Adapter for SAP NetWeaver. If you are existing customer, Ariba recommends that you upgrade to a higher version of the Ariba Cloud Integration. When you upgrade from an existing version of Ariba Cloud Integration to the latest version, ensure that you perform certain procedures to retain your existing settings or customization that you have on your current version of the Ariba Cloud Integration.
Prerequisites Ensure that you have all the necessary software and connectivity requirements before you install the Ariba Network Adapter for SAP NetWeaver.
Related Information Installation Requirements [page 30] Steps to Install the Ariba Network Adapter for SAP NetWeaver PI [page 51]
46
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
Upgrading to a Higher Version of the Ariba Network Adapter for SAP NetWeaver Transports [page 52]
cXML Interfaces Supported in the Ariba Cloud Integration Releases The following table shows a comparison of the supported cXML interfaces between Ariba Cloud Integration version 1.0 and version 6.0: Ariba Cloud Integration Release Version 1.0
Ariba Cloud Integration Release Version 6.0
Requisition
Requisition
Purchase Order
Purchase Order (Includes Change and Cancel Purchase Orders)
Change and Cancel Purchase Order Order Confirmation
Order Confirmation
Ship Notice
Ship Notice
Invoice
Invoice
ERP-Initiated Invoice
ERP-Initiated Invoice
Invoice Status Update
Invoice Status Update
Receipt
Receipt
Payment Proposal
Payment Proposal
Payment Remittance
Payment Remittance
Pay Me Now
Pay Me Now Request for Quotation Service Sheet Order Inquiry Scheduling Agreement Catalog
Related Information Supported cXML Interfaces [page 15]
Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
47
Features Available in the Ariba Cloud Integration Releases The following are the new features and changes introduced in the different Ariba Cloud Integration releases: Ariba Cloud
Ariba Cloud
Ariba Cloud
Ariba Cloud
Ariba Cloud
Ariba Cloud
Integration 1.0
Integration 2.0
Integration 3.0
Integration 4.0
Integration 5.0
The SAP code
Enhanced error
Support for
Support for Order
Support for
delivered by Ariba
messages for
Scheduling
Inquiries
sending RFQs from maintaining the
was certified by
Invoice Status
Agreement
SAP ERP to Ariba
partner profile for
SAP. As part of the
Update
Releases
Sourcing
each vendor or
certification, a new
documents.
Integration 6.0
Support for
maintain the
namespace
partner profile at a
called /ARBA/
logical system level
was registered and
for all vendors
all SAP objects delivered by Ariba were renamed from Z_
name> to /ARBA/ . The SAP NetWeaver PI content was changed by importing the RFCs and the ABAP objects were renamed with the /ARBA/
namespace into SAP NetWeaver PI. The namespace of
SAP NetWeaver PI
Support for
Support for
Support for Ariba
Support Invoice
invoice in the
7.4 Support for
Blanket Purchase
corrections and
Sourcing Award
Status Updates for
Orders
returns in Receipts
Integration
parked and deleted
AribaNetworkA Ariba Network dapterforSAPN
invoices
etWeaver.desi gn.tpz was changed from
http:// ariba.com/xi/ ASN/ZInvoice
48
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
Ariba Cloud
Ariba Cloud
Ariba Cloud
Ariba Cloud
Ariba Cloud
Ariba Cloud
Integration 1.0
Integration 2.0
Integration 3.0
Integration 4.0
Integration 5.0
The cXML adapter
Mapping
Support
Support line-level
Support line-level
requires the JSPM
enhancements to
integration for
hierarchies in
hierarchies in
(Java Support
support Supply
Outline
Service Purchase
Service Sheets and
Package Manager).
Chain
Agreements in SAP Orders
Integration 6.0
to http://
ariba.com/xi/ ASN/Invoice. ZINVOICE02 and ZACCOUNT_DATA were renamed to /
ARBA/INVOICE and /ARBA/
ACCOUNT _DATA respectively.
Invoices
Management Support for Order
Support for
Enhanced request
Support for change Support IDOCs for
Confirmation and
creation of a single
messages added
and cancel order
CC (ERP-Inititated)
rejection of the
ship notice against
to the cXML
transactions have
Invoices
entire purchase
multiple purchase
adapter:
been removed.
order.
orders
StatusUpdateRequ Change order est
transactions are processed as part
Note The previous
of the purchase order IDOC.
Invoice Status Update Request no longer exists. Buyers can now use the StatusUpdateR equest for both invoices and service entry sheets.
Ariba no longer
Support for
Invoice Status
Support all
Support line
uses the ccBPM
schedules lines in
Update use
releases of SAP
numbering in
engine.
purchase orders
Business
ERP 6.0 up to SAP
schedule lines
The following transactions are
Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
Transaction Events ERP 6.0 EhP7 (BTE) to process invoices created,
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
49
Ariba Cloud
Ariba Cloud
Ariba Cloud
Ariba Cloud
Ariba Cloud
Integration 1.0
Integration 2.0
Integration 3.0
Integration 4.0
Integration 5.0
supported using
changed, reversed,
the ABAP proxies:
canceled, or when
●
Integration 6.0
payments are
ERP-Initiated
received.
Invoice ●
Ariba Cloud
Invoice Status Update
●
Payment Proposal
●
Receipt
Payment
Support for SAP
Support for
Integration of
Remittance Advice
ERP Integration
purchase order
catalog data in
transaction is no
with Ariba Spot
confirmation
SAP ERP and Ariba
longer supported
Quote solution
options at the
Network
by the Ariba
header and line-
Network Adapter
item levels
for SAP NetWeaver.
ZARIBA_INV_AT
Support for large
Support summary
TACHDOC BADI
file attachments in
invoices
ZARIBA_INV_AT
invoices and
referencing
TACHDOC BADI
service sheets
multiple purchase orders and direct
support for PDF
invoicing of
copy of invoices.
purchase order service items Processing of attachments in the outbound transactional documents in the PI mapping layer before sending them to Ariba Network
50
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
Steps to Install the Ariba Network Adapter for SAP NetWeaver PI Context
Ensure that you perform the following steps to install the latest SAP NetWeaver adapter on your SAP NetWeaver PI system.
Procedure
1. Download the latest installation package. For more information, see Installing the Network Adapter Files [page 31]. 2. Ensure that you meet all the software and connectivity requirements. For more information, see the Installation Requirements [page 30] section. 3. Configure an Ariba Network account. For more information, see Installation Requirements [page 30]. 4. Configure the SAP ERP system. For more information, see Configuring Your SAP ERP System [page 269]. 5. Import the Design Package. For more information, see Importing the Design Package [page 66]. 6. Configure the System Landscape Directory. For more information, see About Configuring the System Landscape Directory [page 61]. 7. Configure the transaction processes. For more information, see About Configuring Transaction Processes [page 65]. 8. Configure the Integration Scenarios in the Integration Directory. For more information, see Configuring Integration Scenarios [page 80] . 9. Install and configure the cXML Adapter and Log mechanism. For more information, see About Deploying the cXML Adapter [page 34] and About Configuring the cXML Adapter [page 45]. 10. Test the configuration. For more information, see Testing the Adapter [page 384] .
Installing the SAP ERP Transports Context
You must install SAP ERP transports to integrate an Ariba Network application with SAP. The latest SAP ERP transports are available in AribaNetworkAdapterSAPNetweaver_vCIX.zip\SAPConfig\Trans. Place these files in the appropriate locations on your SAP instance.
Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
51
Procedure
1. Run the STMS transaction to install the transport files. 2. Specify the target client as the SAP instance client. 3. If the “Does not match component version” error occurs while importing the transport files that have a different software component that is not available in the target system, turn OFF the SP_TRANS_SYNC parameter: ○ Start Transaction STMS. ○ Go to the Systems Overview. ○ Double click the system identifier for which you want to add the parameter. ○ On the Transport Tool tab, click Change Mode. ○ Add SP_TRANS_SYNC to the parameter column. Set the value for the parameter to OFF. ○ Save and activate the parameter.
Upgrading to a Higher Version of the Ariba Network Adapter for SAP NetWeaver Transports When you upgrade to a higher version of the SAP transports, ensure that you make the necessary changes on your SAP NetWeaver PI and SAP ERP system. Changes Required on your SAP ERP Systems [page 52] Changes Required on your SAP NetWeaver PI System [page 54] Migrating the Design Objects [page 55] Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration [page 55] Updating the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration [page 56] Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration [page 57]
Changes Required on your SAP ERP Systems Context
The following changes are applicable when you upgrade from the Ariba Cloud Integration 1.0 to Ariba Cloud Integration 6.0.
52
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
Procedure
1. Import the Ariba Cloud Integration 6.0 transports. 2. If you want to use the new transactions, configure the necessary settings for the following transactions available in the Ariba Cloud Integration 6.0: ○ Order inquiry – For more information, see Configuring Order Inquiries [page 304]. ○ Scheduling Agreement - For more information, see Configuring Scheduling Agreement Releases [page 309]. ○ Service Sheet - For more information, see Configuring Service Sheets [page 326]. ○ Request for Quotation (Quote Request and Quote Message) - For more information, see Configuring Quote Request and Quote Message Documents [page 318]. ○ Catalog (Catalog Upload Request) - For more information, see Integration of Catalog Data in SAP ERP and Ariba Network [page 250]. 3. Ensure that you migrate the changes for the following BAdI manually. The BAdI is not automatically migrated when you upgrade to Ariba Cloud Integration 6.0. This is applicable only if you are using the BAdI for Ariba Cloud Integration 5.0 and earlier. ○ /ARBA/ISU_UPDATE Starting Ariba Cloud Integration 5.0, the Invoice Status Update BAdI definition has been changed to / ARBA/BTE_ISU_UPDATE. For more information see, Invoice Status Update Integration Scenario [page 160] and Configuring Invoice Status Updates [page 301]. 4. The following BAdIs are no longer available in Ariba Cloud Integration 6.0: ○ /ARBA/CHANGE_PO Ariba Cloud Integration 5.0 does not contain a separate IDOC and namespace for the Change Purchase Order transaction. In Ariba Cloud Integration 4.0 and earlier, change purchase orders and cancel purchase orders were handled differently from new purchase orders by the Ariba Network Adapter for SAP NetWeaver. With Ariba Cloud Integration 5.0, new purchase orders, change purchase order, and cancel purchase orders are now processed in the purchase order transaction. If you have existing change purchase order customizations, ensure that you manually move them to the purchase order transaction. For more information, see Change Purchase Order Integration Scenario [page 89]. ○ /ARBA/INVOICE_UPDATE Ariba Cloud Integration 6.0 no longer uses the proxy for ERP-Initiated Invoices. The ERP-Initiated Invoices now use the standard IDOC. To enhance the ERP-Initiated invoice transaction, you must use the standard BAdI, customer exits, and enhancements. For more information, see the ERPInitiated Invoice Integration Scenario [page 167] and Configuring ERP-Initiated Invoices to Use the IDOC [page 331]. ○ /ARBA/RECEIPT_UPDATE In Ariba Cloud Integration 4.0 and higher, the method READ_RECEIPT_DATA is no longer used. 5. Ensure that you make the following changes after you upgrade to the new version of the Ariba Cloud Integration: ○ Configure the Purchase Order transaction ○ Reconfigure the SAP Partner Profile to process change and cancel orders as variations on a standard purchase order. For more information, see Reconfiguring the SAP Partner Profile [page 90]. ○ Configure Implicit Enhancements for new purchase orders. For more information, see Configuring Implicit Enhancements for Change and Cancel Orders [page 91] . Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
53
○ Configure the SAP IDOC for ship notices (DELVRY06). For more information, see Configuring the SAP IDOC for Ship Notices Against Multiple Purchase Orders [page 313]. ○ Configure the Business Transaction Events (BTE) for the invoice status update transaction. For more information, see Configuring Invoice Status Updates [page 301]. ○ Configure the NACE transaction to publish receipts in real-time. For more information, see Maintaining Condition Records for Returns and Corrections in Receipts [page 317]. ○ Configure the SAP IDOC for ERP-Initiated Invoice transaction. For more information, see Configuring ERPInitiated Invoices to Use the IDOC [page 331].
Changes Required on your SAP NetWeaver PI System Context
Ensure that you make the following changes after you upgrade to the latest version of the desgin mapping objects on your SAP NetWeaver PI system.
Procedure
1. Ariba Cloud Integration 6.0 has new design mapping objects. If you are using an earlier version of Ariba Cloud Integration, ensure that you import the new design mapping objects. Ensure that you configure the integration scenarios for them. 2. If you have customizations done to the existing design mapping objects, you must migrate these design mapping objects. For more information, see section, Migrating the Design Objects [page 55].
Note Ensure that you manually make changes to your custom mappings that contain conflict. 3. You must upgrade your JCA Adapter. If your version of SAP Netweaver PI is lower than SAP PI 7.3 EHP1, use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI. If you are using the SAP Netweaver version PI7.3 EHP1 and higher, you must use the SAP Software Update Manager (SUM) tool to deploy the adapter. For more information on how to install or upgrade using the SUM tool, contact your SAP system administrator. For information on how to deploy the JSPM tool, see the section, Deploying the cXML Adapter Using JSPM [page 35].
Related Information
Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration [page 55]
54
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
Migrating the Design Objects Context After you have upgraded to the Ariba Cloud Integration 6.0, ensure that you migrate the design objects on your SAP NetWeaver PI system.
Procedure 1. Go to the Enterprise Services Builder. 2. On the Tools menu, click Transfer Design Objects. The Transfer Design Object wizard appears. 3. Click Continue. The Select Source and Target page appears. 4. Select the source of your existing Ariba Cloud Integration version in the Source field. 5. Select the target of the new Ariba Cloud Integration version in the Target field. 6. Click Continue. The Select Objects page appears. 7. Select the Active Version for Ariba Cloud Integration 6.0. 8. Select All Objects of Individual Namespaces in the Object Set field. ○ Choose this option if you are upgrading from the Ariba Cloud Integration version 1.0 to 6.0. Choosing this option prevents you from errors that occur due to the mismatch of the namespace changes when you upgrade to a higher version of Ariba Cloud Integration. 9. Ensure that you do not select the following namespaces while upgrading to a higher version of Ariba Cloud Integration: ○ http://ariba.com/xi/ASN/ChangedPurchaseOrder ○ http://ariba.com/xi/Requisition ○ http://ariba.com/xi/ASN/ERPInvoiceProxy ○ http://ariba.com/xi/ASN/AdvanceShipNotice 10. After you have completed transferring the design objects, ensure that you resolve the conflicts. For more information, see Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration [page 55].
Resolving the Conflicts on Upgrading from Lower Version to a Higher Version of Ariba Cloud Integration When you upgrade from a lower version to a higher version of the Ariba Cloud Integration, conflicts arise after transferring the design objects. This occurs due to changes that have been implemented in the newer version of the Ariba Cloud Integration. You can resolve the conflicts for the design objects by accepting the latest version (Active Version) of the Ariba Cloud Integration. Ensure that you manually make changes to your custom mappings that contain conflicts. Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
55
Related Information
Migrating the Design Objects [page 55]
Updating the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration Context
After upgrading to a higher version of the Ariba Cloud Integration, ensure that you update the integration scenarios for the new and existing transactions.
Procedure
1. Delete the following integration scenarios in Ariba Cloud Integration 1.0 : Integration Scenario
These needs to be deleted because…
Requisition
The namespace for this integration scenario has been changed in Ariba Cloud Integration 5.0.
ERPInvoiceProxy (ERP-Initiated invoices)
In Ariba Cloud Integration 6.0, ERP-Initiated Invoices use the standard IDOC instead of the proxy message.
Ship Notice
The IDoc Basic Type has been changed in Ariba Cloud Integration 4.0.
Change Purchase Order
The Change Purchase Order transaction is no longer available in Ariba Cloud Integration 5.0 and 6.0. Change purchase orders are processed as part of the purchase order integration.
2. Run the following integration scenarios again with the Software Component Version for the Ariba Cloud Integration 6.0: ○ Requisition ○ ERPInvoiceProxy ○ Ship Notice (ASN) 3. Edit the integration scenario for the remaining transactions that have been migrated to Ariba Cloud Integration 6.0. For each of the migrated transactions, choose the software component version for Ariba Cloud Integration 6.0. For more information, see Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration [page 57]. 4. Configure the integration scenarios for all the new transactions available in Ariba Cloud Integration 6.0. For more information, see Configuring Integration Scenarios [page 80].
56
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
Editing the Integration Scenarios after Upgrading to a Higher Version of Ariba Cloud Integration After you have upgraded to a higher version of the Ariba Cloud Integration, you must edit the integration scenario for each of the migrated transactions. Configuring the Communication Channel [page 57] Configuring the Receiver Determination [page 58] Configuring the Interface Determination [page 59] Configuring the Sender Agreement [page 59] Configuring the Receiver Agreement [page 60]
Configuring the Communication Channel Context You must edit the integration scenario for each of the migrated transactions. Ensure that you have the necessary options enabled for the Object Properties on the Software Component Version page that allows you to edit the communication channel.
Procedure 1. Go to the Configuration: Integration Builder to edit the communication channel for the Software Component Version. 2. Select the configuration scenario and open it. The Display Configuration Scenario page appears. 3. Click the Edit button. 4. Go to the ES Repository Model tab and click the Display Input Help button. The Select Process Integration Scenario from Enterprise Service Repository page appears. 5. Select the process integration scenario for the software component version for Ariba Cloud Integration 6.0. 6. Click Apply. 7. On the main Configuration: Integration Builder page, click the Objects tab. 8. Double-click the cXML communication channel to open it. 9. Click the Edit button. 10. In the Parameters tab, click the Display Input Help button in the Adapter Type field. The Choose Adapter Metadata page appears. 11. Choose the adapter metadata for Ariba Cloud Integration 6.0 in the Adapter Type field. 12. Click Apply. 13. In the Parameters tab, specify the System Type as “Buyer.” 14. Select the corresponding request type in the Inbound Request Type or Outbound Request Type field. Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
57
○ When you select the Outbound Request Type, choose one of the following DTDs in the cXML Configuration section: ○ Default value: cXML.dtd ○ Specify PaymentRemittance.dtd for PaymentProposalRequest, PaymentRemittanceStatusUpdateRequest, or PaymentRemittanceRequest. ○ Specify Fulfill.dtd for ReceiptRequest and OrderStatusRequest ○ Specify Quote.dtd for QuoteRequest ○ Specify InvoiceDetail.dtd for CopyRequest and Invoice InvoiceDetailRequest 15. Enter a value in the Credentials Field. 16. Save and activate the changes for the communication channel.
Configuring the Receiver Determination Context After you upgrade to the Ariba Cloud Integration 6.0, you must edit the Receiver Determination for each of the migrated transactions.
Procedure 1. Go to the Configuration: Integration Builder to edit the Receiver Determination for the Software Component Version. 2. Select the configuration scenario and open it. The Display Configuration Scenario page appears. 3. Click the Edit button. 4. Go to the ES Repository Model tab and click the Display Input Help button. The Select Process Integration Scenario from Enterprise Service Repository page appears. 5. Select the process integration scenario for the software component version for Ariba Cloud Integration 6.0. 6. Click Apply. 7. On the main Configuration: Integration Builder page, click the Objects tab. 8. Double-click to select the Receiver Determination for the integration scenario. 9. Click the Edit button. 10. Choose the software component version for the Ariba Cloud Integration 6.0. 11. Save and activate the changes.
58
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
Configuring the Interface Determination Context After you upgrade to the Ariba Cloud Integration 6.0, you must edit the Interface Determination for each of the migrated transactions.
Procedure 1. Go to the Configuration: Integration Builder to edit the Interface Determination for the Software Component Version. 2. Select the configuration scenario and open it. The Display Configuration Scenario page appears. 3. Click the Edit button. 4. Go to the ES Repository Model tab and click the Display Input Help button. The Select Process Integration Scenario from Enterprise Service Repository page appears. 5. Select the process integration scenario for the software component version for Ariba Cloud Integration 6.0. 6. Click Apply. 7. On the main Configuration: Integration Builder page, click the Objects tab. 8. Double-click to select the Interface Determination for the integration scenario. 9. Click the Edit button. 10. Choose the software component version of the Sender Interface for the Ariba Cloud Integration 6.0. 11. Click the Display Input Help button in the Operation Mapping column. 12. Select the operation mapping of software component version for Ariba Cloud Integration 6.0. 13. Save and activate the changes.
Configuring the Sender Agreement Context After you upgrade to the Ariba Cloud Integration 6.0, you must edit the Sender Agreement for each of the migrated transactions.
Procedure 1. Go to the Configuration: Integration Builder to edit the Sender Agreement for the Software Component Version. 2. Select the configuration scenario and open it. The Display Configuration Scenario page appears. Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
59
3. Click the Edit button. 4. Go to the ES Repository Model tab and click the Display Input Help button. The Select Process Integration Scenario from Enterprise Service Repository page appears. 5. Select the process integration scenario for the software component version for Ariba Cloud Integration 6.0. 6. Click Apply. 7. On the main Configuration: Integration Builder page, click the Objects tab. 8. Double-click to select the Receiver Determination for the integration scenario. 9. Click the Edit button. 10. Choose the software component version for the Ariba Cloud Integration 6.0. 11. Save and activate the changes.
Configuring the Receiver Agreement Context After you upgrade to the Ariba Cloud Integration 6.0, you must edit the Receiver Agreement for each of the migrated transactions.
Procedure 1. Go to the Configuration: Integration Builder to edit the Receiver Agreement for the Software Component Version. 2. Select the configuration scenario and open it. The Display Configuration Scenario page appears. 3. Click the Edit button. 4. Go to the ES Repository Model tab and click the Display Input Help button. The Select Process Integration Scenario from Enterprise Service Repository page appears. 5. Select the process integration scenario for the software component version for Ariba Cloud Integration 6.0. 6. Click Apply. 7. On the main Configuration: Integration Builder page, click the Objects tab. 8. Double-click to select the Receiver Determination for the integration scenario. 9. Click the Edit button. 10. Choose the software component version for the Ariba Cloud Integration 6.0. 11. Save and activate the changes.
60
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Installing and Upgrading the Ariba Network Adapter for SAP NetWeaver
Configuring SLD and Transaction Processes
About Configuring the System Landscape Directory [page 61] Importing Ariba Network Product and Component Definitions [page 62] Defining Technical and Business System for Ariba Network [page 63] Defining the Business System for Ariba Network [page 63] Defining Technical and Business System for SAP ERP [page 64] Defining the Business Landscape for SAP ERP [page 65] About Configuring Transaction Processes [page 65] Importing the Design Package [page 66] About Configuring ERP Connectivity [page 67] Assigning Business Systems in the Integration Directory [page 67] Creating Communication Channels for ERP [page 68] Creating the IDoc Receiver Communication Channel [page 68] Creating the RFC Receiver Communication Channel [page 69] Configuring IDoc Metadata (Optional) [page 70] Configuring SAP NetWeaver PI Value Mapping [page 71] Creating a New Value Mapping Table [page 79]
About Configuring the System Landscape Directory After you have installed the cXML Adapter, you configure the System Landscape Directory (SLD) by importing the Ariba Network Adapter for SAP NetWeaver product definition and defining the systems involved in the integration. The SAP System Landscape Directory is a central repository that holds the information on the systems and software in the customer environment. It consolidates the information about components actively available, and on which machines, instances, and clients they are available. The Ariba Network Adapter for SAP NetWeaver leverages all the advantages of the SLD in order to maintain the coherence of the system landscape: ● It is defined as a product and component expressed in Common Information Interface (CIM) format importable in the SLD ● It uses a configuration using technical and business systems involved in the Ariba Network integration and defined in the SLD. The information in this topic is applicable to the Ariba Network Adapter for SAP NetWeaver. For information on the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On, see Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On [page 61]. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
61
Related Information
Importing Ariba Network Product and Component Definitions [page 62] Defining Technical and Business System for Ariba Network [page 63] Defining Technical and Business System for SAP R/3 [page 64]
Importing Ariba Network Product and Component Definitions Context
Import the product and component definitions of Ariba products that will work with SAP NetWeaver PI, as a CIM file.
Procedure
1. From the PI main page, open the SLD Administration page. 2. Navigate to the Content section, and then click Import. 3. Select the AribaNetworkAdapterSAPNetweaver.SoftwareCatalog.zip by clicking on the Browse button, and then navigating to the file location. 4. Start the import. 5. In the Product Catalog, verify that the following product is available: ○ Vendor: ariba.com ○ Product: ASN ○ Version: NW04.1 6. Next, verify that the following component is available: ○ Vendor: ariba.com ○ Component: ARIBA_SUPPLIER_CONN_ADAPTER ○ Version: CIX
Results
The Ariba Network Adapter for SAP NetWeaver will now be recognized by the Integration Repository and Directory.
62
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
Defining Technical and Business System for Ariba Network Context Set up the technical system for the Ariba Network system using the Technical System Wizard.
Procedure 1. Select Technical Systems from the main SLD page to open the Technical System page. 2. Click New Technical System to open the Technical System Wizard. 3. In the Wizard, select Third-Party as the Technical System Type to set up a third-party (non-SAP) application such as Ariba Network, and then click Next. 4. Specify the system details as follows: ○ System Name: Specify a user-defined system name here. E.g. TS_ASN ○ Host Name: Enter a host name here. E.g. an 5. Click Next. 6. Associate the ASC Connector product and component to the system. Scroll down the list to select the product, ASN, defined earlier, and then click Add. You can also filter to select the product to associate. Ensure that the component ARIBA_SUPPLIER_CONN_ADAPTER, is selected. 7. Click Finish.
Next Steps Set up the business system for the Ariba Network system using the Business System Wizard.
Defining the Business System for Ariba Network Procedure 1. Select Business System from the main SLD page to open the Business System page. 2. Click New Business System here to open the Business System Wizard. 3. In the Wizard, select Third-Party as the technical system type to associate the business system with, and then click Next. 4. Select the technical system, TS_ASN, created in the previous procedure, from the System field, and then click Next. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
63
Note The Logical System Name is not required. 5. Enter the business system name, e.g. BS_ASN, in the Name field, and click Next. 6. Specify the installed products. Make sure that the product ASN, NW04.1 and the related component ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com, installed on the technical system, are selected, and then click Next. 7. Click Finish.
Defining Technical and Business System for SAP ERP Context Set up the technical system for the SAP ERP system using the Technical System Wizard.
Procedure 1. Select Technical System from the main SLD page to open the Technical System page. 2. Click on New Technical System here to open the Technical System Wizard. 3. In the Wizard, select AS ABAP as the Technical System Type, and then click Next. 4. To specify the SAP ERP system details enter values in the AS ABAP name (SID), Installation Number, and Database Host Name fields, and then click Next. 5. Specify the Message Server and Central Application Server. Enter values in the Host Name, and Message Server Port field. Specify a logon group for the Message Server by entering a value in the Logon Groups column and clicking Add Logon Groups to assign them. You can also filter to select the logon groups. Enter values in the Host Name and Instance Number fields for the Central Application Server, and then click Next. 6. (Optional) Define additional application servers if required. Specify values in the Host Name and Instance Number columns in the Application Server List table, and click Add Application Server. You can also filter to select the application server details. Click Next. 7. Define the Client. Enter values in the Client Number and Logical Client Name columns of the Client List table, and then click Next. The logical system name is required for enabling the communication using IDocs between the SAP NetWeaver PI and ERP systems and is used for routing documents in multi-ERP implementations. For more information about Multi-ERP implementations, see the “Linking Multiple SAP instances with Ariba Network” [page 212] section. 8. Define software product and components. Select the SAP ERP version installed on this technical system, as well all other products installed on the system. You can filter to select the installed products and the software components. 9. Click Finish.
64
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
Next Steps
Set up the business system for the SAP ERP system using the Business System Wizard.
Defining the Business Landscape for SAP ERP Procedure
1. Select Business System from the main SLD page to open the Business System page. 2. Click New Business System here to open the Business System Wizard. 3. In the Wizard, select AS ABAP as technical system type to associate the business system with, and then click Next. 4. Select the technical system created in the previous procedure from the System drop down list, to associate it with the business system. Select a client for the selected technical system from the Client drop down list, and then click Next. 5. Enter the business system name. E.g. BS_SAPR3_50, and click Next. 6. Specify the installed products. Select the products that must be supported by this business system from the ones available from the associated technical system, to install them in the business system, and then click Next. 7. Select the role of the business system. Select Application System as the Business System Role and select your SAP NetWeaver PI instance name from the Related Integration Server drop-down list to specify the integration server. In the case of application systems, specify the integration server. 8. Click Finish.
About Configuring Transaction Processes After you have installed the System Landscape Directory (SLD), you must: ● Import the design package containing the transactions supported by the Ariba Network Adapter for SAP NetWeaver. ● Configure SAP NetWeaver PI connectivity to ERP. ● Configure SAP NetWeaver PI value mapping to provide the global configuration, and supporting facilities such as IDoc Payload and standard code conversions. ● Configure the different transactions in the Integration Directory by importing the scenarios from the Integration Repository. ● Configure the communication channels and the conditions for routing messages, for each supported transaction. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
65
Note The names for objects in the Directory used in the configuration procedures are examples provided for illustration. You may use them or replace them with names and format corresponding to your system environment.
Related Information
Importing the Design Package [page 66] About Configuring ERP Connectivity [page 67] Configuring SAP NetWeaver PI Value Mapping [page 71]
Importing the Design Package Context
The transport file AribaNetworkAdapterSAPNetweaver.Design.tpz contains the definition of the business scenarios.
Procedure
1. Copy the package file AribaNetworkAdapterSAPNetweaver.Design.tpz to the import directory on the SAP NetWeaver PI server, *****\SYS\global\xi\repository_server\import. For example, D:\usr\sap\ARB\SYS\global\xi\repository_server\import. 2. Open the Enterprise Services Builder: Design Tool from the SAP NetWeaver PI main page. 3. From the Tools menu, select the Import Design objects... option. 4. If you are trying to install the Cloud Release version of the SAP PI Adapter on an SAP ERP 6.0 EHP6 or higher, ensure that you click to select the check box ‘Ignore Invalid Component Version’. You must also implement the changes specified in the SAP Note 1688610. 5. Select AribaNetworkAdapterSAPNetweaver.Design.tpz from the available files list, and then click OK. 6. After the import completes, the component ARIBA_SUPPLIER_CONN_ADAPTER, CIX appears in the components list of the Integration Builder Design Tool.
66
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
About Configuring ERP Connectivity Context To enable communication between SAP NetWeaver PI and SAP ERP using IDoc documents, we need to configure the following parameters on the SAP NetWeaver PI ABAP stack: ● Configure the RFC Destination. ● Configure the Port for the IDoc Adapter SAP NetWeaver PI connectivity to ERP.
Procedure 1. Using Transaction SM59, create an RFC destination of type ERP to connect to the SAP ERP system. 2. Using Transaction IDX1, create a Port for the new RFC destination. For example, for the SAP ERP system D47 client 800, you must use specify following parameters to create the port: ○ Port: SAPD47. ○ Client 800. ○ RFC Destination: Specify the destination created in SM59 here.
Note Enter the password in UPPER case.
Assigning Business Systems in the Integration Directory Context The Integration Directory configuration of the Ariba Network Adapter for SAP NetWeaver uses the information on the Technical and Business systems from the SLD. You must assign the Business Systems defined and involved in the integration setup.
Procedure 1. Open the Configuration: Integration Builder from the PI main page. 2. In the Objects tab of the Integration Builder, navigate to Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
Service Without Party
Business System.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
67
3. From the context menu for Business System, select Assign Business System to start the Assign Business System wizard. 4. Click on Continue in the first and second windows. Leave the Party field in the second window blank. 5. In the third window, Select Business Systems, select the business systems BS_ASN and BS_SAPR3_50 created earlier, from the list. For more information about creating business systems, see the “About Configuring the System Landscape Directory” [page 61] section.
Note In the case of Multi-ERP implementation, you must select all the Business Systems representing your SAP ERP instances involved in the integration. 6. Click to clear the Create Communication Channel Automatically check box, if it is checked, to avoid the creation of unwanted channels. 7. Click Finish.
Creating Communication Channels for ERP Create the communication channels used for ERP connectivity. You must create the IDoc Receiver and RFC Receiver communication channels from the Integration Builder to enable communication using IDocs and the RFC invocation on the remote SAP ERP system. These channels will be used by almost all the scenarios and are common to all of them. So, you only need to create them once, for each Business System corresponding to your SAP ERP.
Related Information Creating the IDoc Receiver Communication Channel [page 68] Creating the RFC Receiver Communication Channel [page 69] Configuring IDoc Metadata (Optional) [page 70]
Creating the IDoc Receiver Communication Channel Procedure 1. In the Objects tab of the Integration Builder, click Communication Channel. 2. From the context menu for Communication Channel select New. 3. In the Create Object window, specify CC_IDoc_Receiver as the name of the communication channel in the Communication Channel field.
68
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
4. Click the Communication Component field, then click the Display Input Help drop down list and select Input Help. In the following Choose Communication Component window, select a communication component, say BS_SAPR3_50, and click Apply. 5. Click Create 6. From the Parameters tab of the Edit Communication Channel window, click the Adapter Type field, then click the Display Input Help drop down list and select Input Help to display the list of adapter types. From the Choose Adapter Metadata window, select the following adapter, and then click Apply: ○ Name: IDoc ○ Namespace: http://sap.com/xi/XI/System ○ Software Component Version: SAP BASIS 7.10 7. After selecting the adapter, click the Receiver option, to select the corresponding type. 8. In the Adapter Engine field, select Integration Server or non-central Adapter Engine, depending on your configuration. 9. Edit the other parameters, to match your SAP R3 system (RFC Destination, Interface Version, Port, SAP Release). 10. Select the following options and leave the others unchecked: ○ Apply Control Record Values From Payload ○ Take Sender From Payload 11. Save and activate the communication channel.
Results
Note In the case of Multi-ERP implementation, you must create one CC_IDoc_Receiver channel per Business System, representing each of the SAP ERP instances involved in the integration.
Creating the RFC Receiver Communication Channel Procedure 1. In the Objects tab of the Integration Builder, navigate to BS_SAPR3_50
Service Without Party
Business System
Communication Channel .
2. From the context menu for Communication Channel, select New. 3. In the Create Object window, specify CC_RFC_Receiver as the name of the communication channel, in the Communication Channel field, and then click Create. 4. From the Parameters tab of the Edit Communication Channel window, click the icon next to the Adapter Type field to display the list of adapter types. From the adapter type list window, select the following adapter and click OK: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
69
○ Name: RFC ○ Namespace: http://sap.com/xi/XI/System ○ Software Component Version: SAP BASIS 7.10 5. After selecting the adapter, click the Receiver option, to select the corresponding type. 6. In the Adapter Engine field, select Integration Server or non-central Adapter Engine, depending on your configuration. 7. Edit the other parameters to match your SAP R3 system (Application Server, System Number, Authentication Mode, Logon User, Logon Password, Logon Language, Logon Client).
Note Enter the password in UPPER case. 8. Edit the Maximum Connections option according to the excepted load. 9. Save and activate the communication channel.
Note In the case of Multi-ERP implementation, you must create one CC_RFC_Receiver channel per Business System, representing each of the SAP ERP instances involved in the integration.
Configuring IDoc Metadata (Optional) Context
You can optionally preload the metadata of the IDoc documents exchanged by the IDoc adapter during configuration. If you skip do not preload metadata, the metadata information will be downloaded and associated to the port the first time a given type of IDoc is exchanged.
Procedure
1. Check and configure the IDoc Metadata parameters of the port to communicate with the SAP ERP system in SAP NetWeaver PI. 2. Refer to the transaction IDX2. Check the IDoc Metadata in Metadata Overview for the IDoc Adapter to see if all the inbound IDocs (ORDERS05, DESADV01, INVOIC02 and FIDCCH01) are there. If they are not, click Metadata
70
Create
to add them.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
Configuring SAP NetWeaver PI Value Mapping Configure SAP NetWeaver PI value mapping for supporting facilities such as IDoc Payload and standard code conversions. The information in this topic is applicable to the Ariba Network Adapter for SAP NetWeaver. For information on the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On, see Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On [page 61].
Related Information
Configuring Units of Measure (UOM) Code Mapping [page 71] Configuring Language Mapping [page 72] Configuring TimeZone Mapping [page 72] Configuring Global Variables [page 73] Configure the Mappings Between Business System and Logical System Names [page 76] Configuring Currency Mapping [page 77] Creating a New Value Mapping Table [page 79]
Configuring Units of Measure (UOM) Code Mapping As part of the transformation of documents from IDoc to cXML, or vice versa, certain codes, such as UOM, need to be mapped between different standards. This section provides the steps to configure these mappings. In the value mappings, use the following parameters for UOM transformation rules: ● Source Values: ○ Agency: UOM_ERP ○ Scheme: UOM ● Target Values: ○ Agency: UOM_ISO ○ Scheme: UOM Fill in the value set for UOM_ERP and UOM_ISO, to set up the transformation rules for Units of Measure. The following table shows examples of the respective value sets: UOM_ERP
UOM_ISO
PCE
C62
KGM
KGM
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
71
UOM_ERP
LT
UOM_ISO
LTR
Configuring Language Mapping In the value mappings, use the following parameters for language transformations rules: ● Source Values: ○ Agency: LANG_ERP ○ Scheme: Lang ● Target Values: ○ Agency: LANG_ISO (an example value of SAP ERP Business Systems) ○ Scheme: Lang Fill in the value set for UOM_ERP and UOM_ISO, to set up the transformation rules for languages. The following table shows examples of the respective value sets: LANG_ERP
LANG_ISO
D
de
E
en
F
fr
Configuring TimeZone Mapping In the value mappings, use the following parameters for TimeZone transformations for different Business Systems and for Ariba Network: ● Source Values: ○ Agency: XI_Global ○ Scheme: GlobalVariable ● Target Values: ○ Agency: BS_SAPR3 (an example value of SAP ERP Business Systems) ○ Scheme: TimeZone Fill in the values to set up the transformation rules for TimeZone.
72
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
The following table shows examples of the TimeZone transformation values: Agency
Scheme
Value
XI_Global
GlobalVariable
TimeZone
BS_SAPR3_50
TimeZone
05:45
Configuring Global Variables Because SAP NetWeaver PI acts as the integration platform between SAP ERP and Ariba Network, there are many parameters that are global for each of the supported scenarios. This section describes the steps to configure global variables. In the value mappings, use the following parameters for Global Variables: ● Source Values: ○ Agency: XI_Global ○ Scheme: GlobalVariable ● Target Values: ○ Agency: XI ○ Scheme: GlobalVariable Fill in the global variable table as appropriate for your system. SAP NetWeaver PI Global Variable
Example SAP NetWeaver PI Value
PaymentProposal StartDateTime
2006-10-09T12:13: 13
Group Name
BPMConfig
Description Use this timestamp when the timestamp file for the PaymentProposal transac tion is not configured or its date/time parameters are empty. (Use it for test and devel opment only and NOT for pro duction.)
InvoiceStatus UpdateStartDate Time
IsMultiERPModeEnabled
2006-10-09T12:13: 14
BPMConfig
Use this timestamp when the timestamp file for the
InvoiceStatusUpdate transaction is not configured or its date/time parameters are empty. (Use it for test and devel opment only and NOT for pro duction)
true/false
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
BPMConfig
Use this parameter to enable (true) or disable (false) the Multi-ERP support.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
73
SAP NetWeaver PI Global Variable
Example SAP NetWeaver PI Value
Group Name
Description
ReceiptStartDate Time
2006-10-09T12:13:15
BPMConfig
Use this timestamp when the timestamp file for the Receipt transaction is not configured or its date/time parameters are empty. (Use it for test and devel opment only and NOT for pro duction.)
TimeZone
-08:00 or +05:30
BPMConfig
Use this parameter label to con figure time zones in each of the configured SAP R3 Business Systems. Configure the value in the format -HH:mm or +HH:mm. You must configure the value for this parameter in each agency representing the SAP R3 Busi ness System.
SAPExternalPaymen t Method
C
BPMConfig
Use this parameter to set the payment method used in exter nal payment. This must be a valid method defined in SAP. Set this parameter if you are using the
PaymentRemittanceAdvic e transaction. SAPAccountingDocT ype
SA
BPMConfig
Use this parameter to set the SAP accounting document type.
SAPUserName
BPMConfig
Use this parameter to set the SAP user name.
OrbianPaymentMethod
O
BPMConfig
Use this parameter to set the Orbian payment method.
OrbianPaymentMethod Description
Orbian
BPMConfig
Use this parameter to provide a description for the Orbian pay ment method.
R3LS
T90CLNT090
BPMConfig
Use this parameter to set the default SAP ERP logical system ID. Set this parameter if you are using the
PaymentRemittanceAdvic e transaction in a single ERP in stallation, where it is not manda tory to configure the System ID in the Ariba Network Buyer Ac count. In such cases, the Sys tem ID will be obtained from this parameter.
74
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
SAP NetWeaver PI Global Variable
Example SAP NetWeaver PI Value
Group Name
Description
BusinessSystem
BS_SAPR3_50
Lookup
Use the name of the Business System in cases that involve a Single ERP configuration.
Communication Channel
RFC_Lookup_Receiver
Lookup
This denotes the name of the communication channel to be used by the Lookup API in the mapping. Configure this param eter with a value that indicates the RFC Receiver Communica tion Channel configured for all the SAP R3 Business Services in your Configuration Directory.
SNDPRT
LI_SND
SAPEDIDC
This denotes a constant used for the IDoc control field SNDPRT.
SNDPFC
LF_SND
SAPEDIDC
This denotes a constant used for the IDoc control field SNDPFC.
DefaultLanguageCode
EN
BPMConfig
If the PO Idoc message from the SAP ERP system does not con tain a value for the language code, then the value of this pa rameter will be used to populate the target cXML.
PurchaseOrderDocTypes
NB
BPMConfig
This variable must contain the value for the SAP document type for purchase orders. NB is the default doctype in the SAP system. However, customers can have a different doc type as signed to their purchase orders.
Note If you want to maintain multi ple doc types for purchase orders, you must specify NB, NA,AS in the Value for XI field. BlanketOrderDocType
LP
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
BPMConfig
This variable must contain the value for the SAP document type for blanket orders. LP is the default doctype in the SAP sys tem. However, customers can have a different doc type as signed to their blanket orders.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
75
SAP NetWeaver PI Global Variable
Example SAP NetWeaver PI Value
ISU_ERP_INV_Canceled canceled/rejected _Rejected_Status
Group Name
Description In the SAP ERP system, when an invoice fails to get created, the status code 423 and status
rejected are sent to Ariba Network. However, if a user can cels an invoice in SAP ERP sys tem, then the status code 200 and status canceled instead of rejected are sent to Ariba Network. If you are an existing customer and want to continue using the
canceled status when an in voice is canceled in the SAP ERP system, then you are not re quired to make any changes as the default value of this variable is set to canceled. However, if you want to send the rejected status when a user cancels an invoice in the SAP ERP system, then you must set the value of this variable to rejected.
Note New customers are recom mended to set the value of this variable to rejected. DefaultRequesterEmailID
The email ID of the requester in the SAP ERP system.
DefaultPreparerEmailID
The email ID of the preparer in the SAP ERP system.
Configure the Mappings Between Business System and Logical System Names In the value mappings, use the following parameters to configure the mappings between business systems and logical systems. Source: ● Agency: LogSys_Source ● Scheme: Lookup
76
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
● Value: Logical System Name Target: ● Agency: BusSys_Target ● Scheme: Lookup ● Value: Business System Name
Note The Group Name is not required. The following table shows an example of values. LogSys_Source
BusSys_Target
T90CLNT090
BS_SAP_46C
T47CLNT800
BS_SAP_47
Note In the case of Multi-ERP implementation, additional value mappings need to be defined. For more information, see the “Linking Multiple SAP instances with Ariba Network” [page 212] section.
Configuring Currency Mapping You can configure the currency precision maintained in the TURX table on your SAP NetWeaver PI system. By default, the precision for currencies is two decimal places. For example, when a purchase order is created, the EKPO table is updated with the purchase order information. If the currency for one of the line items is 10.00000, the value stored in the EKPO table is 100000.00. Currencies having more than two decimal places show the NETPR value adjusted to two decimal places incorrectly. To maintain precision in currencies correctly, you must preserve the value mappings for currencies in the TCURX table. Enter the values for the following parameters: Source Values: Agency: ERP_Currency Scheme: Currency Target Values: Agency: Currency_Precision Scheme: Currency
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
77
Here is an example of how the precision for currencies are maintained: Value for Currency_Precision
Values for the ERP_Currency
Group Name
0
JPY
Currency
5
USDN
Currency
3
PKT
Currency
0
TWD
Currency
Maintaining the Value Mapping to Support Logical Systems in SAP NetWeaver PI Context
To process documents through the logical system, maintain the value mapping for the logical system in the SAP NetWeaver PI.
Procedure
1. In the Tools menu, click Value Mapping. 2. In the Display Value Mapping window enter the Agency and Scheme values for the source and target in the respective fields, as follows: Agency
Scheme
Value
XI_Global
GlobalVariable
IsLogicalSystemEnabled
XI
GlobalVariable
yes
3. Specify the logical system name as follows: Agency
Scheme
Value
XI_Global
GlobalVariable
Name of the logical system
XI
GlobalVariable
R3PartnerProfileLS
4. (Mandatory if you are a buyer using multiple ERP systems) In the Display Value Mapping Agencies page, map the logical system to the system ID of the multiple ERP systems (business systems) with the following values:
78
Agency
Scheme
Value For SystemIDFrom_cXML
SystemIDFrom_cXML
Lookup
System ID of the ERP system
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
Agency
Scheme
Value For
Group Name
SenderPartner_LogicalSystem
SenderPartner_LogicalSyste Lookup m
Name of the logical system
SystemIDFrom_cXML
Creating a New Value Mapping Table Context Create a new value mapping table if the Agency/Scheme is not available.
Procedure 1. In the Tools menu, click Value Mapping. 2. In the Display Value Mapping window enter the Agency and Scheme values for the source and target in the respective fields, as follows: ○ Source Values For Agency: UOM_ERP Scheme: UOM ○ Target Values For Agency: UOM_ISO Scheme: UOM 3. Click Display. 4. Click the Change/Edit button to bring the table into Edit Mode. 5. Click on the ‘+’ icon to add the Value Mappings.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring SLD and Transaction Processes
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
79
Configuring Integration Scenarios
About Configuring Integration Scenarios in the Integration Directory [page 80] Purchase Order Integration Scenario [page 82] Change Purchase Order Integration Scenario [page 89] Order Confirmation Integration Scenario [page 93] Ship Notice Integration Scenario [page 102] Ship Notice Integration Scenario to Support Creation of a Single Ship Notice Against Multiple Purchase Orders [page 109] Service Sheet and Service Sheet Response Integration Scenario [page 117] Invoice Integration Scenario [page 123] PayMeNow Integration Scenario [page 130] Payment Remittance Integration Scenario [page 137] Schedule Lines in Purchase Orders and Change Purchase Orders [page 143] Blanket Purchase Order Integration Scenario [page 144] Order Inquiries Integration Scenario [page 146] Scheduling Agreement Release Integration Scenario [page 153] Invoice Status Update Integration Scenario [page 160] ERP-Initiated Invoice Integration Scenario [page 167] Receipt Integration Scenario [page 173] Receipt Integration Scenario for Corrections and Returns in Receipts [page 179] Receipt Integration Scenario for Purchase Orders with Multiple Accounting Assignments [page 182] Payment Proposal Integration Scenario [page 184] Requisition Request Integration Scenario [page 190] Request for Quotation Integration Scenario [page 196] Sourcing Award to Contract Integration [page 201] Change Purchase Order Implementation Redesigned [page 208] Proxy Implementation for Outbound Transactions [page 210]
About Configuring Integration Scenarios in the Integration Directory This section describes how to import and configure the integration scenarios in the SAP NetWeaver PI Integration Directory for the supported transactions. Use an integration scenario from the Integration Repository as a
80
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
template for configuring the corresponding transaction in the Integration Directory. The Integration Scenarios are part of the Design package, which has to be imported into the Integration Repository first. If you are using a SAP NetWeaver PI version that is higher than SAP BASIS 7.10, then you must ensure that you edit the software component version for the communication channel template to avoid receiving the following error: "Software component version with name SAP BASIS 7.10 not found. See error log for details." For more information, see Configuring the Software Component Version for Communication Channel Templates [page 82].
Note Do not activate the Change Lists feature of Integration Builder Configuration Tool until all the configuration steps are completed. Configure the Integration Scenarios for the following inbound transactions: ● Order Confirmation Integration Scenario [page 93] ● Configuring and Activating the Ship Notice Integration Scenario [page 102] ● Configuring and Activating the Ship Notice Integration Scenario to Support Creation of a Single Ship Notice Against Multiple Purchase Orders [page 109] ● Service Sheet and Service Sheet Response Integration Scenario [page 117] ● Invoice Integration Scenario [page 123] ● PayMeNow Integration Scenario [page 130] Configure the Integration Directory for the following outbound transactions: ● Purchase Order Integration Scenario [page 82] ● Change Purchase Order Integration Scenario [page 89] ● Change Purchase Order Implementation Redesigned [page 208] ● Schedule Lines in Purchase Orders and Change Purchase Orders [page 143] ● Blanket Purchase Order Integration Scenario [page 144] ● Order Inquiries Integration Scenario [page 146] ● Scheduling Agreement Release Integration Scenario [page 153] ● Payment Remittance Integration Scenario [page 137] ● Invoice Status Update Integration Scenario [page 160] ● ERP-Initiated Invoice Integration Scenario [page 167] ● Configuring and Activating the Receipt Integration Scenario [page 173] ● Payment Proposal Integration Scenario [page 184] ● Requisition Request Integration Scenario [page 190] ● Request for Quotation Integration Scenario [page 196] Configuring the Software Component Version for Communication Channel Templates [page 82]
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
81
Configuring the Software Component Version for Communication Channel Templates Context If you are using a SAP NetWeaver PI version that is higher than SAP BASIS 7.10, then you must ensure that you edit the communication channel template to avoid receiving an error. Important: Ensure that you have the necessary options enabled for the Object Properties on the Software Component Version page that allows you to edit the communication channel template.
Procedure 1. Go to the Enterprise Service Builder and edit each of the communication channel templates for the http:// ariba.com/xi/ASN/CommonBasis Software Component Version: ○ CCT_IDOC_RECEIVER ○ CCT_RFC_LOOKUP_RECEIVER 2. Double click the required communication channel template. The Display Communication Channel Template page appears. 3. In the Parameters tab, click the Display Input Help button in the Adapter Type field. The Choose Adapter Metadata page appears. 4. Choose the common Basis version for each of the communication channel templates. 5. Double click each of the following communication channel template. The Display Software Component Version page appears. Software Component Version
Communication Channel
Adapter Type
Namespace
Template
ARIBA_SUPPLIER_CONN _ADAPTER CIX of ariba.com
CCT_RFC_Lookup_Rece iver
RFC
http:// ariba.com/xi/ASN/ CommonBasis
ARIBA_SUPPLIER_CONN _ADAPTER CIX of ariba.com
CCT_IDoc_Receiver
IDOC
http:// ariba.com/xi/ASN/ CommonBasis
Purchase Order Integration Scenario You need to configure the integration scenario for the Purchase Order transaction in the Integration Directory to be able to run the transaction for new purchase orders, changed purchase orders, and canceled purchase orders. All the steps of a configuration scenario section must be completed to fully configure a scenario. When a buyer manually specifies the delivery address, Ariba Network Adapter for SAP NetWeaver processes the manually entered values in the delivery address field as follows:
82
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
● If a buyer manually selected the address ID, customer ID, or vendor ID in the Delivery Address tab, and then edited the existing values of the address, Ariba Network Adapter for SAP NetWeaver sends the newly saved delivery address as the ShipTo address in the purchase order. The delivery address stored on the SAP ERP system for the address ID, customer ID, or vendor ID is not sent in the change purchase order. For example, if a buyer selected the address ID, edited the street address, and saved the changes, Ariba Network Adapter for SAP NetWeaver sends the newly edited street address as part of the Shipto address in the purchase order. ● If a buyer manually entered the delivery address to include the following fields in the Delivery Address tab, Ariba Network Adapter for SAP NetWeaver sends the associated delivery address as the ShipTo address in the purchase order: ○ Address ID in the Address field ○ Customer ID in the Customer field ○ Vendor ID in the Vendor field ● If the buyer has only the plant address and does not have the storage location in the purchase order, Ariba Network Adapter for SAP NetWeaver sends the plant address as the ShipTo address. ● If the buyer has both the plant and storage location in the line item and the storage location address is maintained in the ox09 on the SAP ERP system, Ariba Network Adapter for SAP NetWeaver sends the storage location address as the shipTo address.
Note If a buyer entered the street address as the delivery address for certain countries, the street address then contains the street name and the house number instead of the house number and street. In some cases, Ariba Network Adapter for SAP NetWeaver processes the name field from the Name_text field instead of Name1. Ariba recommends that customers use the BADI customization in these cases.
Mapping Limitations The Purchase Order transaction has the following mapping limitations: ● Time Zone is hard coded to Pacific time zone ● Bill-to and Ship-to addresses in SAP purchase orders behave as follows: If all purchase order lines have the same ship-to address, then: ● The ship-to address appears at the header level in cXML/Ariba Network ● The ship-to address does not appear at the line level in cXML/Ariba Network ● The bill-to address in the header matches the ship-to address If purchase order lines have different ship-to addresses, then: ● Ship-to addresses do not appear at the header level in cXML/Ariba Network ● Ship-to addresses appear at the line level in cXML/Ariba Network ● The bill-to address in the header matches the ship-to address in the first line ● The shipping information is not supported.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
83
Workflow
Note Ensure that the Design package is imported into your system and ready before you run these steps. The following steps assume that the different Business Systems are defined in the SLD. For more information about configuring the SLD, see the “About Configuring the System Landscape Directory” [page 61] section. To configure purchase orders: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario. 3. Configure the Communication Channels. 4. Activate the new configuration.
Transferring the Purchase Order Integration Scenario Context
The first step to configure the integration scenario for the Purchase Order transaction is to transfer to the Integration Directory, the integration scenario loaded into the Integration Repository when the Design package is imported.
Procedure
1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_PurchaseOrder_Receive ○ Namespace: http://ariba.com/xi/ASN/PurchaseOrder ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory 6. Click Finish.
84
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Results Once the transfer is completed, the Model Configurator window appears.
About Configuring the Purchase Order Integration Scenario After the Integration Scenario is selected, you configure it using the following steps. 1. Assign the Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects.
Selecting the Model for the Scenario Procedure In the Model Configurator window, click the Select Component View button and then click Apply to select the unique model that is selected by default.
Next Steps After selecting the model, you must assign components to the application components of the selected integration scenario.
Assigning Components for the Purchase Order Integration Scenario Procedure 1. In the Model Configurator, click the Assign Component button. 2. In the Assign Components window, select the Business System Components for A2A tab to assign components for Ariba Network. 3. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. 4. Click on the row under the Communication Component column, then click on the Value List drop down and select Value List
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
85
Note For Multi ERP implementation, add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4. 5. Click the Next Role button (the right arrow) to go to the next screen in the window. 6. Click 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
Next Steps
After assigning components, 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 Purchase Order Integration Scenario 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 BS_ASN in the Receiver 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, and in the next page click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Communication Channel Template: ○ Name: CCT_PurchaseOrder_cXML_Receiver ○ Namespace: http://ariba.com/xi/ASN/PurchaseOrder ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 5. Click Continue, modify the channel name to CC_PurchaseOrder_cXML_Receiver, and then click Finish.
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.
86
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Note The communication channels for SAP ERP Sender system are not required. 6. Click the Activate All Connections button, and then click OK in the dialog box. 7. Click the Save Settings button to save the changes.
Generating Objects for the Purchase Order 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, click 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 both the active check boxes – Receiver Determination, and Interface Determination. 3. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. 4. Click on 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 Purchase Order Integration Scenario Context
Configure the communication channel CC_PuchaseOrder_cXML_Receiver under the AR_PurchaseOrder_Receive Configuration Scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
87
Procedure 1. Under Communication Channel, double-click |BS_ASN|CC_PuchaseOrder_cXML_Receiver to open it, or right-click and select Open. 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration.
Note If you created the channel by copy from an existing channel, you need to change the request type to OrderRequest in the Outbound 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 Interface Determination Settings for the Purchase Order Integration Scenario Context Configure the interface determination settings to enable mapping enhancements.
Procedure 1. Expand Interface Determination, and then click |BS_SAPR3_50 | ORDERS.ORDERS05 | | 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_ORDERS_ORDERS05_2_cXML 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.
88
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Activating the Purchase Order Integration Scenario Context Using the Change List tab on the main application screen, activate all the Change Lists containing the objects created and modified during the component setup. This completes the configuration of the Purchase Order transaction in SAP NetWeaver PI.
Change Purchase Order Integration Scenario You must configure the integration scenario for the Purchase Order transaction in the Integration Directory to be able to run the change purchase order transaction. The Change Purchase Order Integration scenario and the http://ariba.com/xi/ASN/ChangedPurchaseOrder namespace no longer exists. Change purchase orders are now subsumed into IDoc processing for purchase orders.
Note This change in functionality does not affect how the adapter processes new purchase orders. Enhancements to change and cancel purchase order processing are not backward compatible with previous releases. ● Changes Required for New Customers New customers must do the following: ○ Must make one-time configuration changes to SAP ERP implicit enhancements, and for change and cancel purchase orders. ○ Must set up SAP ERP Partner Profiles. ● 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). ○ Make one-time configuration changes to SAP ERP implicit enhancements for change and cancel purchase orders. ○ Must remove their old change order configuration from their Ariba solutions. It is no longer needed. ○ Customers who also employ change order transaction customizations must migrate those customizations to their purchase order transaction customizations. For more information on the purchase order integration scenario, see Purchase Order Integration Scenario [page 82] .
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. All rights reserved.
89
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.
Procedure 1. Go to transaction WE20 to modify an existing partner profile. 2. Choose Partner type LI (Vendor), select a vendor, and click Edit. 3. Select Message Type ORDERS and doublie-click.. 4. Click on Insert Row (the green + sign) and enter the following parameters. 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. Retain the default selection, Transfer IDoc Immed., for the Output Mode parameter in the Outbound Options tab. 6. Save your changes.
90
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
About Configuring Implicit Enhancements To enable SAP ERP to send correct new, change, and cancel purchase order information to the Ariba Network Adapter for SAP NetWeaver, you must configure two SAP ERP implicit enhancements..
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, you must configure an implicit enhancement in SAP ERP.
Procedure 1. In your SAP ERP system, navigate to transaction code SE38 - LEINMF0Q and click Display. 2. Select SAPLEINM from the popup. 3. Click Enhance in the application toolbar. 4. Click Edit > Enhancement Operations > Show Implicit Enhancement Options to display a line after the lesen-beleg form. 5. Right-click the line and select Enhancement Implementation > Create. 6. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation. 7. Click Create Enhancement Implementation. 8. Enter a name and description for the enhancement and press Enter. 9. In the package popup, specify your Z or Y package, press Enter, and save the package to a transport request. 10. Copy the following code: DATA: cl_PO_ChangeCancel TYPE REF TO /arba/cl_PO_ChangeCancel. CREATE OBJECT cl_PO_ChangeCancel. CALL METHOD cl_PO_ChangeCancel->trigger_delete_po_idoc EXPORTING ebeln = h_ebeln CHANGING xdruvo = xdruvo. 11. Paste the copied code into the Enhancement Implementation. 12. Activate the enhancement and save it.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
91
Configuring Implicit Enhancements for New Purchase Orders To enable SAP ERP to send new purchase order information to the Ariba Network Adapter for SAP NetWeaver, you must configure an implicit enhancement in SAP ERP.
Procedure 1. In your SAP ERP system, navigate to transaction code SE37 - IDOC_OUTPUT_ORDERS and click Display. 2. Search for Perform fill_srv_orders. 3. Double-click Perform. 4. Select SAPLEINM from the popup. 5. Click Enhance in the application toolbar. 6. Click Edit > Enhancement Operations > Show Implicit Enhancement Options to display a line after the fill_srv_orders form. 7. Right-click the line and select Enhancement Implementation > Create. 8. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation. 9. Click Create Enhancement Implementation. 10. Enter a name and description for the enhancement and press Enter. 11. In the package popup, specify your Z or Y package, press Enter, and save the package to a transport request. 12. Copy the following code: DATA: 1_flag(5) TYPE c, cl_purchaseorder TYPE REF TO /arba/cl_purchaseorder, cl_po_hierarchy TYPE REF TO /arba/cl_po_hierarchy, ls_idoc_status TYPE bdidocstat, lx_appl_idoc TYPE REF TO /arba/cx_appl_idoc. CONSTANTS: c_true TYPE char4 VALUE 'true', c_false(5) TYPE c VALUE 'false'. CREATE OBJECT cl_purchaseorder. CREATE OBJECT cl_po_hierarchy. TRY. CREATE OBJECT cl_po_hierarchy. CALL METHOD cl_po_hierarchy->getsystemversion_ishierarchy EXPORTING ebeln = ekpo-ebeln et_edi_esll = edi_esll[1] IMPORTING flag = l_flag CHANGING int_edidd = int_edidd[1]. CATCH /arba/cx_appl_idoc INTO lx_appl_idoc. MESSAGE e151(/arba/message) RAISING error_message_received. RETURN. ENDTRY. IF l_flag EQ c_true. CALL METHOD cl_purchaseorder->fill_service_line_number EXPORTING packno = ekpo-packno IMPORTING
92
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
ENDIF
et_edi_esll
= edi_esll[].
13. Paste the copied code into the Enhancement Implementation. 14. Activate the enhancement and save it. 15. Right-click below the last line in the fill_srv_orders form and select Enhancement Implementation > Create. 16. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation 17. Select the enhancement created and named in Step 10. 18. Copy the following code: IF l_flag EQ c_true. CALL METHOD cl_purchaseorder->create_parent_child_relation EXPORTING edi_esll = edi_esll[] CHANGING int_edidd = int_edidd[]. ENDIF 19. Activate the enhancement and save it.
Removing Change Order Configurations from Your Ariba Solution Ariba Network Adapter for SAP NetWeaver provides change and cancel order enhancements that no longer make use of previously existing change order configurations in your Ariba solution. You must remove them. To remove your previously existing change order configuration, please have your Designated Support Contact log a service request, and an Ariba Customer Support representative will follow up to complete the request.
Migrating Change Order Customizations If you employ change and cancel order transaction customizations in your Ariba solutions, the customizations must be migrated to your purchase order transaction instead. To migrate your customizations, please have your Designated Support Contact log a service request, and an Ariba Customer Support representative will follow up to complete the request.
Order Confirmation Integration Scenario The Ariba Network Adapter for SAP NetWeaver supports receiving order confirmations from Ariba Network for the following: ● Confirmation or rejection of entire purchase order items that contain service line items. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
93
● Confirmation of orders with or without delivery dates at the header or line-level. ● Confirmation of orders containing partially confirmed, rejected, and back-ordered line items. ● Confirmation of orders containing line items with multiple schedule lines (delivery dates). ● Comments at the header and line-item levels.
Note A PO item that contains service line items can only be confirmed or rejected in its entirety, not at the individual service line-item level. If a delivery date is provided in Ariba Network when creating a confirmation request, the delivery date is derived from the confirmationRequestt cXML. Otherwise the delivery date is determined from the corresponding PO item. You must configure the integration scenario for the Order Confirmation transaction in the Integration Directory to be able to run the transaction. All the steps of a configuration scenario section must be completed to fully configure a scenario. The SAP ERP administrator must configure the SAP ERP system to collect order confirmations for purchase orders and to support comments. To configure SAP ERP enhancements for comment support, see Configuring Implicit Enhancements for Comments in Order Confirmations [page 300] .
Mapping Limitations The Order Confirmation transaction has the following mapping limitations: ● Order confirmations are stated at the purchase order line-item level only. SAP does not support header level purchase order confirmation. With the exception of unit price and backordered delivery date, purchase order line items cannot be overwritten. ● A new order confirmation completely overwrites prior confirmations against a purchase order line-item. Suppliers must resend the entire confirmation picture for the relevant purchase order line. ● Delivery date is always required at 'ConfirmationStatus' in the input cXML document if the header level and line level statues are 'Backordered'. Delivery date is required at 'ConfirmationStatus' level if header level statuses are 'detail' and 'except'. ● In the cXML for an order confirmation sent from Ariba Network, the adapter does not support the operation = “update” and type = “allDetail”. ● Only order confirmations for the purchase orders that are pulled from ERP using the OrderRequest transaction is supported. ● Ariba Network Adapter for SAP NetWeaver does not support order confirmations for service purchase orders at the line-item level. ● The IDoc fails when an order confirmation only contains partially rejected line items. For example, if the quantity for a line item is 100, you cannot partially reject only 50 units for that line item. You can partially accept 50 units and also partially reject or back order the remaining 50 units for the line item. You must ensure that you maintain the Overdelivery Tolerance and Underdelivery Tolerance limits for the line item. However, Ariba Network Adapter for SAP NetWeaver supports order confirmations that are partially accepted, rejected, or back ordered for a line item. For example, if the quantity for a line item is 100, you can partially accept 50 units and also partially back order or reject the remaining 50 units for the line item. ● Purchase orders containing service items may only be confirmed at the outline item level. ● Purchase orders containing a combination of service and material items may only be confirmed at the header level.
94
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
● When purchase orders contains advanced pricing details, the unit conversion value from Ariba Network to SAP is not supported. ● The cXML header-level except status for order confirmations created in Ariba Network is not supported. ● Partial rejection of a line item in an order confirmation is not supported. Full rejection of an item in an order confirmation sets the deletion flag on the item in SAP.
Workflow
The following is a description of the end-to-end workflow for order confirmation: 1. A buyer creates a purchase order in the SAP ERP that may or may not include service line-items, and may or may not include line items with multiple delivery dates. 2. In Ariba Network a supplier receives the purchase order and creates an order confirmations based on the purchase order. The confirmation order can contain comments at the header and line-items levels. 3. Ariba Network sends the confirmation order to the SAP PI system as a ConfirmationRequest cXML document. 4. The SAP PI system maps the ConfirmationRequest to an ORDRSP.ORDERS05 IDoc and sends it to the SAP ERP system. 5. SAP ERP processes the order confirmation, and the original purchase order is updated with the confirmation information received from Ariba Network. To configure the Order Confirmation: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario. 3. Configure the Communication Channels. 4. Activate the new configuration.
Note Ensure that the design is imported into your system and ready before you run these steps. The following steps assume that the different Business Systems are defined in the SLD. For more information about configuring the SLD, see the “About Configuring the System Landscape Directory” [page 61] section.
Transferring the Order Confirmation Integration Scenario Context
The first step to configure the integration scenario for the Order Confirmation transaction is to transfer to the Integration Directory, the integration scenario loaded into the Integration Repository when the design is imported.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
95
Procedure
1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, and then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_OrderConfirmation_Send ○ Namespace: http://ariba.com/xi/ASN/OrderConfirmation ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory. 6. Click Finish.
Results
Once the transfer is completed, the Model Configurator window appears.
About Configuring the Order Confirmation Integration Scenario Once the Integration Scenario is selected, you must configure it using the following steps: 1. Assign the Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects.
Selecting the Model for the Scenario Procedure
In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default.
96
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Next Steps After selecting the component view, you must assign components to the application components of the selected integration scenario.
Assigning Components for the Order Confirmation Integration Scenario Procedure 1. In the Model Configurator, click the Assign Component button. 2. In the Assign Components window, select the Business System Components for A2A tab to assign components for Ariba Network. 3. Click on the Insert Line button ('+') to add a component entry in the table if no component entry line is present. 4. Click on the row under the Communication Component column, then click on the Value List drop down and select Value List
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 Order Confirmation Integration Scenario Procedure 1. In the Model Configurator, select Configure Connections. 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. All rights reserved.
97
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. 4. Click Continue, and in the next page click the Name field, then click the Display Input Help drop down list and select Input Help. 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, CIX of ariba.com. 5. Click Continue, modify the channel name to CC_OrderConfirmation_cXML_Sender, and then click Finish.
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. 6. In the Connections from Component 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. The IDoc receiver Communication Channel needs to be created once for each Business System corresponding to your SAP R3 instance. 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. For Multi ERP implementation, repeat the steps 6, and 7 for all the entries of the Business Systems corresponding to your SAP ERP instances.
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. 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 Order Confirmation 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.
98
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Procedure
1. In the Model Configurator, click 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 Order Confirmation Integration Scenario Context
Configure the communication channel CC_OrderConfirmation_cXML_Sender under the AR_OrderConfirmation_Send Configuration Scenario:
Procedure
1. Under Communication Channel, double-click |BS_ASN|CC_OrderConfirmation_cXML_Sender to open it, or right-click and select Open. 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. If required, edit the other parameters. For more information about the cXML Adapter parameters see cXML Adapter Parameters [page 391].
Note If you created the channel by copy from an existing channel, you need to change the request type to ConfirmationRequest in the Inbound Request Type field. 3. Save the changes.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
99
Configuring Receiver Determination Settings for the Order Confirmation Integration Scenario Context Configure the receiver determination settings manually, for the receiver MIOut_Async_OrderConfirmation_cXML under the AR_OrderConfirmation_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_OrderConfirmation_cXML. 2. In the Configured Receivers section of the Edit Receiver Determination window, click the Add button to add a new line. 3. Click on 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 on 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/To/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 on 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/To/Credential/Identity. ○ This path should be displayed in the XPath Expression field. ○ 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.
100
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
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 Order Confirmation Integration Scenario Context
Configure the interface determination settings to enable mapping enhancements.
Procedure
1. Expand Interface Determination, and then click |BS_SAPR3_50 | ORDRSP.ORDERS05 | | 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_ORDRSP_ORDERS05 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.
Activating the Order Confirmation 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
101
Results This completes the configuration of the Order Confirmation transaction in SAP NetWeaver PI.
Additional Configuration Tasks for the Order Confirmation Integration Scenario ● In an Order Confirmation, if the supplier changed the unit price and delivery date, to ensure that the IDOC is able to post the data to SAP ERP system, you must apply SAP Notes, 109273 and 456127. ● To ensure no error is reported when order confirmations with rejected line items are posted to SAP ERP, you must apply SAP Note 890812 on your SAP ERP system.
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. All the steps of a configuration scenario section must be completed to fully configure a scenario.
Mapping Limitations The Ship Notice transaction has the following mapping limitations: ● Only the 'new' operation is supported; 'update' and 'delete' operations are not supported. ● Delivery Date is required ● Only shipment notices for the Purchase Orders that are pulled from SAP using OrderRequest transaction are supported for this release.
Workflow
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 Ship Notice: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory.
102
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
2. Configure the Integration Scenario. 3. Configure the Communication Channels. 4. Activate the new configuration.
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, 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 login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, and then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_AdvanceShipNotice_Send ○ Namespace: http://ariba.com/xi/ASN/AdvanceShipNotice ○ 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 on Finish.
Results Once the transfer is completed, the Model Configurator window appears.
About Configuring the Ship Notice Integration Scenario Once the Integration Scenario is selected, you must configure it using the following sequence of steps: 1. Assign the Model. 2. Assign Components. 3. Configure Connections. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
103
4. Generate Configuration Objects.
Selecting the Model for the Scenario Procedure
In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default.
Next Steps
After selecting the component view, you must assign components to the application components of the selected integration scenario.
Assigning Components for the Ship Notice 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 . 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 service entry in the table 7. Click on the row under the Communication Component column, then click on the Value List drop down and select Value List . Select the communication component name BS_SAPR3_50 from the selection list and click Apply. For Multi ERP implementation add the multiple business services defined for your multiple SAP R/3 systems by repeating the steps 6 and 7. 8. Click the Save Settings button to save the changes.
104
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Next Steps After 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 Ship Notice Integration Scenario 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 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. 4. Click Continue, and in the next page click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Communication Channel Template: ○ Name: CCT_AdvanceShipNotice_cXML_Sender ○ Namespace: http://ariba.com/xi/ASN/AdvanceShipNotice ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com. 5. Click Continue, modify the channel name to CC_AdvanceShipNotice_cXML_Sender, and then click Finish. 6. In the Connections from Component 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. The IDoc receiver Communication Channel needs to be created once for each Business System corresponding to your SAP ERP. 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 ERP Business System from the selection list. For Multi ERP implementation, repeat the steps 6, and 7 for all the entries of the Business Systems corresponding to your SAP ERP instances.
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.
Note The communication channels for SAP ERP Sender system are not required. 8. Click on Apply to save the changes. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
105
Generating Objects for the Ship Notice 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, click 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, close the wizard and click Apply in the pop up window, 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 Ship Notice Integration Scenario Context Configure the communication channel CC_AdvanceShipNotice_cXML_Sender under the AR_AdvanceShipNotice_Send Configuration Scenario:
Procedure 1. Under Communication Channel, double-click |BS_ASN|CC_AdvanceShipNotice_cXML_Sender to open it, or right-click and select Open. 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration.
Note If you created the channel by copy from an existing channel, you need to change the request type to ShipmentNoticeRequest in the Inbound Request Type field.
106
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
If required, adapt 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 Ship Notice Integration Scenario Context Configure the receiver determination settings manually, for the receiver MIOut_Async_AdvanceShipNotice_cXML under the AR_AdvanceShipNotice_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_AdvanceShipNotice_cXML. 2. In the Configured Receivers section of the Edit Receiver Determination window, click the Add button to add a new line. 3. Click on 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 on 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/To/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 on 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/To/Credential/Identity. ○ This path should be displayed in the XPath Expression field. ○ 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
107
○ 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 Ship Notice Integration Scenario Context Configure the interface determination settings to enable mapping enhancements.
Procedure 1. Expand Interface Determination, and then click |BS_SAPR3_50 | DESADV.DESADV01 | | 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_DESADV_DESADV01 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.
108
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Activating the Ship Notice 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 Ship Notice transaction is now ready for execution.
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. 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_DELVRY06 supports ship notices for multiple purchase orders. You must download and import the necessary mapping changes in your SAP PI system. You must also configure your SAP R/3 system to accept ship notices against multiple POs. For more information, see Configuring Ship Notices Against Multiple Purchase Orders [page 313].
Note If you are an existing customer and want to use this feature, you must delete the existing configuration scenario using the old namespace http://ariba.com/xi/ASN/AdvanceShipNotice and reconfigure the Configuration scenario with the new model for the namespace 'http://ariba.com/xi/ASN/ AdvanceShipNotice_DELVRY06'.
Limitations Ariba Network Adapter for SAP NetWeaver does not support ship notices against non-POs. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
109
To receive ship notices with zero quantities, you must also configure you SAP ERP system to specify the ‘No dialog’ option in the Checks for zero quantity page. For more information, see Configuring the Ship Notice Integration Scenario to Receive Ship Notices with Zero Quantities [page 117].
If you are using customized business processes, you must configure the following second PI mapping: ‘MM_Custom_CDF_FulFill_XSD_AdvanceShipNotice_2_DESADV_DELVRY06’.
Workflow
Configuring the ship notice integration scenario to support multiple POs 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 Ship Notice Integration Scenario for Multiple POs [page 111]. 2. Configure the Integration Scenario. For more information, see About Configuring the Ship Notice Integration Scenario for Multiple POs [page 112]. 3. Configure the Communication Channels. For more information, see Configuring Communication Channels for the Ship Notice Integration Scenario with Multiple POs [page 114]. 4. Configure the Interface Determination. For more information, see Configuring Interface Determination Settings for the Ship Notice Integration Scenario with Multiple POs [page 116]. 5. Activate the integration scenario. For more information, see Activating the Ship Notice Integration Scenario for Multiple POs [page 117]. 6. Configure to receive ship notices with zero quantities. For more information, see Configuring the Ship Notice Integration Scenario to Receive Ship Notices with Zero Quantities [page 117].
110
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
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. ○ 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.
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. The integration scenario is loaded into the Integration Repository when the design package is imported.
Procedure
1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard > Select Process Integration Scenario, click the Name field, and then click the Display Input Help pull-down menu and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_AdvanceShipNotice_DELVERY06_Send ○ Namespace: http://ariba.com/xi/ASN/AdvanceShipNotice_DELVRY06 ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba.com. 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory 6. Click Finish.
Results
Once the integration scenario transfer is completed, the Model Configurator window appears. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
111
About Configuring the Ship Notice Integration Scenario for Multiple POs Configuring the Integration Scenario involves the following steps: 1. Selecting the model. 2. Assigning the components. 3. Configuring the sender and receiver relations for individual connections. 4. Generating the configuration objects.
Selecting the Model for the Ship Notice Integration Scenario with Multiple POs 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 the Ship Notice Integration Scenario with Multiple POs Procedure 1. In the Model Configurator, click the Assign Component button. 2. In the Assign Components window, select the Business System Components for A2A tab to assign components for Ariba Network. 3. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is available. 4. Click the row under the Communication Component column, then click the Value List pull-down menu and select Value List . Select the communication component name of the business system for Ariba Network 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 the Insert Line button ('+') to add a service entry in the table. 7. Click the row under the Communication Component column, then click the Value List pull-down menu and select Value List
112
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Configuring Sender and Receiver Relations for Individual Connections for the Ship Notice Integration Scenario with Multiple POs 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 name of 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. Select the following Communication Channel Template: ○ Name: CCT_AdvanceShipNotice_DELVRY06_cXML_Sender ○ Namespace: http://ariba.com/xi/ASN/AdvanceShipNotice_DELVRY06 ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba.com. 6. Click Continue, modify the channel name to CC_AdvanceShipNotice_cXML_Sender, and then click Finish. 7. In the Connections from Component Assignment tab in the Configure Connection window, 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. The IDoc receiver Communication Channel needs to be created once for each Business System corresponding to your SAP ERP. If a Communication Channel already exists, you can continue to use it. 8. Select the communication channel CC_IDoc_Receiver corresponding to the SAP ERP Business System from the selection list. If you have multiple ERP systems, repeat Step# 6 and 7 for all the entries of the Business Systems corresponding to your SAP ERP instances.
Tip If you have already created and configured a Receiver channel name for the business system in Ariba Network for another transaction, you can create the communication channel by copying from a channel that has already been configured.
Note The communication channels for SAP ERP Sender system are not required. 9. Click Apply to save the changes.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
113
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. If they already exist, they are reused and enhanced, if required. You can also simulate generation for test purpose
Procedure 1. In the Model Configurator, click the Create Configuration Object button. 2. In the Create Configuration Objects dialog box, 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. Select Create New in the Change List for Generated Objects section. The text box already contains an object name that you can use or modify. 4. Click Start to begin generating objects. 5. After the object generation is complete, click Apply to save the new configuration settings. Close the log that is created without saving. You can save it, if required.
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. In the Communication Channel list, double-click
|< Name of the Business System for Ariba Network
|
CC_AdvanceShipNotice_cXML_Sender to open it. 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. If required, edit the other parameters.
114
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Note If you created the channel by copying from an existing channel, you must change the request type to ShipmentNoticeRequest in the Inbound Request Type field. 3. Update the cXML version parameter to the 1.2.025 version. 4. Save and activate the changes.
Configuring Receiver Determination Settings for the Ship Notice Integration Scenario with Multiple POs Context Configure the receiver determination settings manually, for the receiver MIOut_Async_AdvanceShipNotice_cXML under the AR_AdvanceShipNotice_DELVRY_06_Send integration scenario. Retain the default settings for the other receivers.
Note This configuration is required only if you have multiple ERP systems.
Procedure 1. Expand Receiver Determination, and then click
|< Name of the Business System for Ariba Network
|
MIOut_Async_AdvanceShipNotice_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/To/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/To/Credential/Identity. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
115
○ This path should be displayed in the XPath Expression field. ○ 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 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. For example. T90CLNT090. 6. Click OK to close the Condition Editor. 7. Click the icon next to the Communication Component field to start the Choose Communication Component window, and select the Communication Component corresponding to the Logical System Name you specified in the Condition.
Note If you have multiple ERP systems, repeat the Step# 2 to 7 for all your SAP ERP instances. 8. Save the Receiver Determination settings.
Configuring Interface Determination Settings for the Ship Notice Integration Scenario with Multiple POs Context
Configure the interface determination settings to enable mapping enhancements.
Procedure
1. Expand Interface Determination, and then click
|< Name of the Business System for SAP ERP
|
DESADV.DELVRY06 | | < Name of the Business System for Ariba Network . 2. In the Receiver Interfaces section of the Edit Interface Determination window, click the operation mapping value under the Operation Mapping column, then click the Value List pull-down menu and select Value List. 3. Select the operation mapping IFM_cXML_2_DESADV_DELVRY06 and click Apply. 4. The Multiplicity column displays the value "0..unbounded". 5. Save and activate the interface determination settings.
Note Configuring the Interface Determination is a mandatory step if you must configure the mappings.
116
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Activating the Ship Notice Integration Scenario for Multiple POs 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 Ship Notice transaction.
Configuring the Ship Notice Integration Scenario to Receive Ship Notices with Zero Quantities Procedure 1. Go to the transaction code “0vlp”. 2. Click Position and then enter “ELN” as the Item category. 3. Double-click the Item category “ELN”. The Checks for zero quantity window appears. 4. Select the No dialog option.
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.
Note Ensure that the Design package is imported into your system and ready before you run these steps. The following steps assume that the different Business Systems are defined in the SLD. For more information about configuring the SLD, see About Configuring the System Landscape Directory [page 61]. To configure the service sheet transaction: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
117
3. Configure the Communication Channels. 4. Activate the new configuration.
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, the integration scenario loaded into the Integration Repository when the Design package is imported.
Procedure
1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen for the Service Sheet transaction: ○ Name: AR_ServiceEntrySheet_Send ○ Namespace: http://ariba.com/xi/ASN/ServiceEntrySheet ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba.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.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory 6. Click Finish. 7. Click Close.
Results After the transfer is completed, the Model Configurator window appears.
118
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
About Configuring the Service Sheet and Service Sheet Response Integration Scenarios Once the Integration Scenario is selected, you must configure it using the following steps: 1. Assign the Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects.
Selecting the Model for the Scenario Procedure In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default.
Next Steps After selecting the component view, 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. 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 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 . Select the communication component name BS_BS_ERPERFLNX1 (sample value) from the selection list and click Apply.
Note For Multi ERP implementation, add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
119
5. Click the Next Application Component button (the right arrow) to go to the next screen in the window. 6. Click 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 . Select the communication component name BS_ASN (sample value), from the selection list and click Apply. 8. Click the Save Settings button to save the changes.
Next Steps After assigning components, 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. 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, click the empty Communication Channel cell corresponding to < Name of 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, and in the next page click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Communication Channel Template for the Service Sheet transaction: ○ Name: CCT_ServiceEntrySheet_cXML_Sender ○ Namespace: http://ariba.com/xi/ASN/ServiceEntrySheet ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba.com Select the following Communication Channel Template for the Service Sheet Response transaction: ○ Name: CCT_ServiceEntrySheetResponseProxy_cXML_Receiver ○ Namespace: http://ariba.com/xi/ASN/ServiceEntrySheetResponseProxy ○ Software Component Version: ARBA_SUPPLIER_CONN_ADAPT CIx of ariba.com 5. Click Continue, modify the channel names to CC_ServiceEntrySheet_cXML_Sender and CC_ServiceEntrySheetResponseProxy_cXML_Receiver, and then click Finish.
Tip If you have already created and configured a Receiver channel for | for another transaction, you can create the communication channel by copying from an already configured channel.
120
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
6. In the Connections from Component Assignment tab, click the empty Communication Channel cell corresponding to BS_ERPERFLNX1 in the Receiver Business System Components table. 7. Click on the Value List drop down and select Value List . Select the CC_Proxy_Receiver communication channel from the selection list and click Apply. 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 Service Sheet and Service Sheet Response Integration Scenarios 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, click the Create Configuration Object button. 2. In the Create Configuration Objects window, make the following settings: ○ Under General, select the Generation option. ○ Scope of Generation: Select both the active check boxes – Receiver Determination, and Interface Determination. 3. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. 4. Click on Start to begin generating objects. 5. After the object generation is complete, close the log that is created without saving. You can save it, if required. 6. Click Apply to save the new configuration settings.
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. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
121
Procedure
1. In the Objects tab on the right side, double-click the following to open it, or right-click and select Open: Service Sheet 1. <|Name of the Business System for Ariba Network>|<|CCT_ServiceEntrySheet_cXML_Sender Service Sheet Response 1. <|Name of the Business System for Ariba Network>|<| CCT_ServiceEntrySheetResponseProxy_cXML_Receiver 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network buyer account configuration.
Note If you created the channel by copying an existing channel, you need to change the request type to ServiceEntryRequest in the Inbound Request Type field. 3. Specify values for the other parameters as required.
Note For the cXML Version parameter, enter 1.2.025 or higher for service sheet and service sheet response transactions respectively. To ensure that attachments in service sheets are processed by the adapter and sent to SAP ERP, in the communication channel for the service sheet transaction, you must select Embedded in cXML option for the Attachment Processing Mode parameter. 4. Save the changes.
Activating the Service Sheet and Service Sheet Response Integration Scenarios 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 service sheet and service sheet response transactions in SAP NetWeaver PI.
122
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Invoice Integration Scenario You must configure the integration scenario for the Invoice transaction in the Integration Directory to be able to run the transaction. All the steps of a configuration scenario section must be completed to fully configure a scenario.
Recommendations When you receive invoices from suppliers with the PST, GST, QST, and HST tax rates, Ariba Network Adapter for SAP NetWeaver recommends the following: ● When suppliers create an invoice on Ariba Network, it is mandatory to enter the tax information. When no tax is applicable to the invoice line, a zero percent tax should be entered. If the tax information is not provided then the IDOC posting fails with the error “Enter a tax code in item.” ● The tax segments at the header and line-item level in the IDOC must be equal to the number of tax segments available in the cXML file. ● It is mandatory to maintain the tax type and tax rate for a partner in the OBCD transaction. For both the header and line-item level tax, when an Invoice IDOC is sent to ERP, it does a look up to transaction OBCD and based on the partner, tax type, and tax rate, and gets the right tax code to be used for invoice posting.
Mapping Limitations The Invoice transaction has the following mapping limitations: ● Invoice ID must be unique for a supplier ○ 'Standard' type invoices and credit memos are supported ○ Only 'standard' type invoices for the Purchase Orders that are pulled from ERP using OrderRequest transaction are supported for this release. ● The following information is not supported: ○ Header Invoice (debit memo) ○ Information Only Invoice ○ Cancel/Delete Invoice ○ Payment Terms ○ Subsequent Credit ○ Period information ○ Deposit amount ○ Tax: 'VAT recoverable' feature
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
123
Workflow
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 Invoice integration 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.
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, the integration scenario loaded into the Integration Repository when the design is imported.
Procedure
1. From the SAP NetWeaver PI main page, select the Integration Directory login into Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, and then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_Invoice_Invoic02 ○ Namespace: http://ariba.com/xi/ASN/Invoice ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com. 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory 6. Click on Finish.
124
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Results Once the transfer is completed, the Model Configurator window appears.
About Configuring the Invoice Integration Scenario Once the Integration Scenario is selected, you must configure it using the following steps: 1. Assign the Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects.
Selecting the Model for the Scenario Procedure In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default.
Next Steps After selecting the component view, you must assign components to the application components of the selected integration scenario.
Assigning Components for the Invoice 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 . 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. All rights reserved.
125
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 service entry in the table 7. Click on the row under the Communication Component column, then click on the Value List drop down and select Value List . Select the communication component name BS_SAPR3_50 from the selection list and click Apply. 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.
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 Invoice Integration Scenario 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 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. 4. Click on Continue, and in the next page click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Communication Channel Template: ○ Name: CCT_Invoice_cXML_Sender ○ Namespace: http://ariba.com/xi/ASN/Invoice ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com. 5. Click Continue, modify the channel name to CC_Invoice_cXML_Sender, and then click Finish. 6. In the Connections from Component 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. The IDoc receiver Communication Channel needs to be created once for each Business System corresponding to your SAP ERP. 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. If a Communication Channel already exists you need to use it. 7. Select the communication channel CC_IDoc_Receiver corresponding to the SAP ERP Business System from the selection list. For Multi ERP implementation, repeat the steps 6 and 7 for all the entries of the Business Systems corresponding to your SAP ERP instances.
126
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
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.
Note The communication channels for SAP ERP Sender system are not required. 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 Invoice 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, click 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 Invoice Integration Scenario Context Configure the communication channel CC_Invoice_cXML_Sender under the AR_Invoice_Send Configuration Scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
127
Procedure 1. Under Communication Channel, double-click |BS_ASN|CC_Invoice_cXML_Sender to open it, or right-click and select Open. 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration.
Note If you created the channel by copy from an existing channel, you need to change the request type to InvoiceDetailRequest in the Inbound Request Type field. If required, adapt 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 Invoice Integration Scenario Context Configure the receiver determination settings manually, for the receiver MIOut_Async_Invoice_Invoic02_cXML under the AR_Invoice_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_Invoice_ZInvoic02_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/To/Credential/@domain. ○ This path should be displayed in the XPath Expression field. ○ Click OK to return to the Expression Editor.
128
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
○ 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/To/Credential/Identity. This path should be displayed in the XPath Expression field.
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 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 OK to close the Condition Editor. 7. Click the icon next to the Communication Component field to start the Choose Communication Component window, and select the Communication Component corresponding to the Logical System Name you specified in the Condition.
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 Invoice Integration Scenario Context Configure the interface determination settings to enable mapping enhancements.
Procedure 1. Expand Interface Determination, and then click | BS_ASN | | BS_SAPR3_50 | INVOIC.INVOIC02.INVOIC02. 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_INVOIC_INVOICE02_INVOIC02 and click Apply. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
129
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.
130
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide 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 login to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, and then click the Display Input Help 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 . 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 . 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.
132
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Next Steps After 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.
134
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide 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.
136
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide 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
Workflow
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 cXML Adapter Parameters [page 391] section. To configure the Payment Remittance: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario. 3. Configure the Communication Channels. 4. Activate the new configuration.
Transferring the 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, the integration scenario loaded into the Integration Repository when the design is imported.
Procedure
1. From the SAP NetWeaver PI main page, select the Integration Directory login into Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, and then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_PaymentRemittance_Receive ○ Namespace: http://ariba.com/xi/ASN/PaymentRemittance ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com. 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory. 6. Click on Finish.
138
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Results
Once the transfer is completed, the Model Configurator window appears.
About Configuring the Payment Remittance Integration Scenario Once the Integration Scenario is selected, you must configure it using the following steps: 1. Select Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects. 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. After selecting the model, you must assign components to the application components of the selected integration scenario.
Assigning Components for the Payment Remittance 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
Note For Multi ERP implementation add the multiple business services defined for your multiple SAP ERP systems by repeating the steps 3 and 4. 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
139
7. Click on the row under the Communication Component column, then click on the Value List drop down and select Value List
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 Payment Remittance Integration Scenario 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 BS_ASN in the Receiver 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 In case 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 click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Communication Channel Template: ○ Name: CCT_PaymentRemittance_cXML_Receiver ○ Namespace: http://ariba.com/xi/ASN/PaymentRemittance ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com. 5. Click Continue, modify the channel name to CC_PaymentRemittance_cXML_Receiver, and then click Finish.
Note The communication channels for SAP ERP Sender system are not required. 6. Click on Apply to save the changes.
140
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Generating Objects for the Payment Remittance 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, click 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 both the active check boxes – Receiver Determination, and Interface Determination. 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 Payment Remittance Integration Scenario Context
Configure the communication channel CC_PaymentRemittance_cXML_Receiver under the AR_PaymentRemittance_Receive Configuration Scenario:
Procedure
1. Under Communication Channel, select |BS_ASN{CC_PaymentRemittance_cXML_Receiver. 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 Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
141
Note If you created the channel by copy from an existing channel, you need to change the request type to PaymentRemittanceRequest. 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 Interface Determination Settings for the Payment Remittance Integration Scenario Context
Configure the interface determination settings to enable mapping enhancements.
Procedure
1. Expand Interface Determination, and then click | BS_SAPR3_50 | REMADV.PEXR2001 | | 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_REMADV_PEXR2001_2_cXML 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.
Activating the Payment Remittance 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.
142
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Results This completes the configuration of the Payment Remittance transaction in SAP NetWeaver PI.
Schedule Lines in Purchase Orders and Change Purchase Orders You can specify multiple delivery schedules for a line item in a purchase order or change purchase order that you send suppliers on Ariba Network. This allows you to specify multiple schedule lines for a line item that needs to be supplied repeatedly over a period of time. Each line item can have different quantities and multiple delivery dates and time in a purchase order. 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. 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. The mappings for the schedule lines are stored in: / ns0:Messages/ns0:Message2/cXML/Request/OrderRequest/ItemOut/ScheduleLine/@lineNumberl. When a purchase order containing changes to the schedule lines is sent to a supplier, the newly added, deleted, or edited schedule lines are highlighted in the change purchase order on Ariba Network. 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. Purchase orders containing more than 50 schedule lines for a line item fail on Ariba Network. ● You can send purchase orders containing schedule lines to suppliers that can view them. However, suppliers cannot create order confirmations, ship notices, and invoices for each of the schedule lines on Ariba Network.
Prerequisites to Enabling Schedule Lines in Purchase Orders from your SAP ERP System to Ariba Network Procedure 1. Download the latest AribaNetworkAdapterSAPNetweaver_vCI_x_FR.zip from connect.ariba.com. 2. Import the AribaNetworkAdapterSAPNetweaver.Design.tpz file into your SAP NetWeaver PI system. 3. Import the relevant SAP transport requests into your SAP ERP system.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
143
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. The following steps assume that the different Business Systems are defined in the SLD. ● All the steps of the 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. ● Ensure that you make the necessary changes to the cXML Version parameter in the Communication Channel.
Note In SAP ERP and Ariba Network Adapter for SAP NetWeaver Purchase and Change Orders are now processed using the same internal mechanisms. For more information about the streamlining and merging of Change Order processing into Purchase Order processing, see Change Purchase Order Integration Scenario [page 89] as well as the links to Purchase Order configuration in the following steps.
Procedure
1. Transfer the Integration Scenario from the Integration Directory
Integration Repository
Enterprise Service Builder
to the
Integration Builder . For more information, see:
○ Transferring the Purchase Order Integration Scenario [page 84] 2. Configure the Integration Scenario. For more information, see: ○ About Configuring the Purchase Order Integration Scenario [page 85] 3. Configure the Communication Channels for Purchase and Change Orders. For more information, see: ○ : Configuring Communication Channels for the Purchase Order Integration Scenario [page 87] 4. Configure the Interface Determination. For more information, see: ○ Configuring Interface Determination Settings for the Purchase Order Integration Scenario [page 88] 5. Activate the integration scenario. For more information, 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. The blanket purchase order or the change blanket purchase order contain line items that specify the item category B (Limit) only. Additionally, the blanket purchase order also includes the Validity Start (cXML
144
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
field:effectiveDate) and Validity End (cXML field:expirationDate) details for Ariba Network to successfully process blanket purchase orders. You can also create a blanket purchase order having line items that specify the item category B against a single or multiple outline agreements (OLA). The cXML blanket purchase orders sent to Ariba Network contains the value orderType=“blanket”. Suppliers can use these purchase orders of type “blanket” to create order confirmation and ship notices on Ariba Network. Ariba Network Adapter for SAP NetWeaver processes purchase orders containing line items that specify any other item category as regular purchase orders. Ariba Network rejects purchase orders having line items that specify different categories. This feature has the following limitations: ● You cannot create a blanket purchase order for services. ● The SAP ERP system allows you to create a purchase order with line items having different types of item categories. For example, you can create a single purchase order having line items that specify item category B (Limit), D (services), C (standard) and approve the same in the SAP ERP system. However, 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. 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. ● 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 following steps assume that the different Business Systems are defined in the SLD. 1. Transfer the Integration Scenario from the
Integration Repository
Enterprise Service Builder
to the
Integration Directory Integration Builder . For more information, see Transferring the Purchase Order Integration Scenario [page 84], 2. Configure the Integration Scenario. For more information, see About Configuring the Purchase Order Integration Scenario [page 85]. 3. Configure the Communication Channels. For more information, see Configuring Communication Channels for the Purchase Order Integration Scenario [page 87]. 4. Configure the Interface Determination. For more information, see Configuring Interface Determination Settings for the Purchase Order Integration Scenario [page 88]. 5. Activate the integration scenario. For more information, see Activating the Purchase Order Integration Scenario [page 89].
Note ● 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
145
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, they specify the number of days on which suppliers must receive reminders. When suppliers do not confirm or deliver items against the purchase order within the stipulated time, they receive these reminders. These reminders are called Inquiries. Buyers using the Ariba Network Adapter for SAP NetWeaver can send an order inquiry and request information on the following: ● Delivery schedule for materials ordered against line items for an entire purchase order ● Delivery date for line items having schedule lines ● Reminder on the outstanding line items ● Overall status of line items or the purchase order ● Additional comments Suppliers can respond to these inquiries with an order confirmation or a response to the inquiry raised against line items in the purchase order. After the supplier responds to the inquiry, Ariba Network Adapter for SAP NetWeaver does not send reminders to suppliers on Ariba Network. This feature allows both buyers and suppliers to collaborate and handle processing of purchase orders efficiently.
Note ● Order Inquiries is supported in SAP NetWeaver PI 7.1, 7.3 and 7.4 for Java only or Java and ABAP stack (single or dual stack). ● Buyers can also send inquiries for change purchase orders. ● Buyers can create up to three reminders for a purchase order in an SAP system. 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, 2014 and specifies reminders to be sent to a supplier if they do not confirm the purchase order or deliver items against this delivery date. A buyer specifies two reminders: Reminder 1 having 2 days and Reminder 2 having 3 days. ● The supplier on Ariba Network receives the purchase order. If the supplier does not confirm the purchase order or delivery items by July 12, 2014, an inquiry (Reminder 1) is sent to the supplier. ● Suppliers can do one of the following: ○ Confirm the entire purchase order: The supplier creates an order confirmation on Ariba Network that is sent to the buyer.
146
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
○ Responds to the inquiry on a line item. The supplier responds to the inquiry and the same is sent to the buyer. ● If the supplier still fails to confirm the order by July 15, 2014, another inquiry (Reminder 2) is sent to the supplier. After the supplier responds to the inquiry, they do not receive reminders from the buyer’s ERP system.
Order Inquiry Output Types and Reminders
Buyers can create two output types for an order inquiry: ● MAHN (Dunning) ● AUFB (Dunning Order Confirmation) Buyers can set reminders using the transaction code ME91F. This generates the MAHN output type of order inquiry. The Ariba Network Adapter for SAP NetWeaver calculates the date programmatically before sending reminders to the suppliers. The reminders are calculated as follows: ● If the calculated date is less than the current date, the reminder code is populated as zero {MAHNZ]. ● If the calculated date is more than the current date, the actual reminder code is populated by taking the value from EKET-MAHNZ. ME92F is the transaction code to send reminders by specifying the number of days in the confirmation control key SPRO setting, This generates the AUFB output type of order inquiry.
The SO10 transaction code stores the reminder text. Based on the reminder level, the associated text is picked up and sent to the supplier. The /ARBA/PARAM_TAB stores the reminder text with the variable name ORDERENQUIRY. For example: Variable Name
Field Name
Number
Option
Selection Value
ORDERENQUIRY
DUNNING1
I
EQ
ZMM_DUNNING1
ORDERENQUIRY
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. All rights reserved.
147
Variable Name
Field Name
Number
Option
Selection Value
ORDERENQUIRY
DUNNING_OC
I
EQ
ZMM_DUNNING_OC
ORDERENQUIRY
PUR Ø>d¢ço¨V!{x¨³aüÃÆä1ˆ¿¶~é"¼Ç²ª EGORY
AB
Note PURCHASE_ORDER_CATEGORY must be maintained and a value provided for it to prevent order inquiry failure. The Reminder text is populated in /ARBA/ORDENQ_COMMENTS.
Note ● The namespace for order inquiries is http://ariba.com/xi/ASN/OrderEnquiry. ● The CDF_Fulfill_XSD structure contains changes to support order inquiries. ● The Ariba Network Adapter for SAP NetWeaver sends inquiries only for line items that contain reminders.
Configuring the Order Inquiries Integration Scenario Prerequisites You must download the latest AribaNetworkAdapterSAPNetweaver_vCI_x_FR.zip from connect.ariba.com. Ensure that you import the AribaNetworkAdapterSAPNetweaver.Design.tpz file into your SAP NetWeaver PI System and transports in your ERP systems. 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.
Procedure 1. Transfer the Integration Scenario from the
Integration Repository
Enterprise Service Builder
to the
Integration Directory Integration Builder . For more information, see Transferring the Order Inquiries Integration Scenario [page 149]. 2. Configure the Integration Scenario. For more information, see About Configuring the Order Inquiries Integration Scenario [page 149]. 3. Configure the Communication Channels. For more information, see Configuring Communication Channels for the Order Inquiries Integration Scenario [page 152]. 4. Configure the Interface Determination. For more information, see Configuring Interface Determination Settings for the Order Inquiries Integration Scenario [page 153]. 5. Activate the integration scenario. For more information, see Activating the Order Inquiries Integration Scenario [page 153].
148
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Note All the steps of a configuration scenario section must be completed to fully configure a scenario.
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. 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 in to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then log
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. 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.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory. 6. Click Finish.
Results After the integration scenario transfer is completed, the Model Configurator window appears.
About Configuring the Order Inquiries Integration Scenario Configuring the Integration Scenario involves the following steps: 1. Selecting the model. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
149
2. Assigning the components. 3. Configuring the sender and receiver relations for individual connections. 4. Generating the configuration objects.
Selecting the Model for the Scenario Procedure In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default.
Next Steps After selecting the component view, you must assign components to the application components of the selected integration scenario.
Assigning Components for the Order Inquiries 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 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
Note If you have multiple ERP systems, add the multiple communication components defined for your multiple SAP ERP systems by repeating the Step 3 and 4. 5. Click the Next Role button (the right arrow) to go to the next screen on the window. 6. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. 7. Click the row under the Communication Component column, then click the Value List pull-down menu and select Value List
150
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Configuring the Sender and Receiver Relations for Individual Connections for the Order Inquiries Integration Scenario 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 Receiver 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. Select the following Communication Channel Template: ○ Name: CCT_OrderEnquiry_cXML_Receiver ○ Namespace: http://ariba.com/xi/ASN/OrderEnquiry ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba.com 6. Click Continue, modify the channel name to CC_OrderEnquiry_cXML_Receiver, and then click Finish.
Tip If you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction, you can create the communication channel by copying from a channel that has already been configured.
Note The communication channels for SAP ERP Sender system are not required. 7. Click the Activate All Connections button, and then click OK. 8. Click the Save Settings button.
Generating Objects for the Order Inquiries Integration Scenario Context
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.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
151
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. 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 Order Inquiries Integration Scenario Context
Configure the communication channel CC_OrderEnquiry_cXML_Receiver under the AR_OrderEnquiry_Receive Configuration Scenario.
Procedure
1. In the Communication Channel list, double-click CC_OrderEnquiry_cXML_Receiver
|< Name of the Business System for Ariba Network
|
to open it.
2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network buyer account configuration.
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. If required, edit the other parameters. 3. Update the cXML version parameter to the 1.2.026 version. 4. Save the changes.
152
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Configuring Interface Determination Settings for the Order Inquiries Integration Scenario Procedure 1. Expand Interface Determination, and then click
|< Name of the Business System for SAP ERP
|
ORDERS05./ARBA/ORDERS05 | | < Name of the Business System for Ariba Network . 2. In the Receiver Interfaces section of the Edit Interface Determination window, click the operation mapping value under the Operation Mapping column. Then click the Value List pull-down menu and select Value List. 3. Select the operation mapping IFM_ORDERS_ORDENQ_ARBA_2_cXML and click Apply. 4. The Multiplicity column displays the value “0..unbounded”. 5. Save and activate the interface determination settings.
Note Configuring the Interface Determination is a mandatory step if you must configure the mappings.
Activating the Order Inquiries 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 component setup.
Results This completes the configuration of the purchase order transaction to support inquiries on SAP NetWeaver PI.
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. These scheduling agreement releases contain schedules lines with details on the line item, quantity, and the different delivery dates for an extended period of time. The scheduling agreement releases do not contain any pricing information. You can create either a Forecast Delivery Schedule or JIT (Just-in-time) Delivery Schedule against a scheduling agreement release that contain schedule lines with delivery dates for different quantities for the line item. A Forecast Delivery Schedule contains schedule lines for line items required over a longer period of time, spanning Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
153
multiple weeks or months. A JIT Delivery Schedule contains line items required over a shorter period of time, spanning multiple days or even times in a day. Suppliers receive these scheduling agreement releases as a release purchase order (orderType=“release”) containing a single line item with schedule lines. Suppliers can use this release purchase order to create ship notices for the line item based on the different delivery dates and specified quantities on Ariba Network.
Note ● You must upgrade to the cXML version 1.2.026 and configure your SAP R/3 system to send scheduling agreement releases. Ensure that you make the necessary changes to the cXML Version parameter in the Communication Channel. However, support for this feature and the cXML version 1.2.026 will be made available as part of the Ariba Network 2014 August release. Please contact your Ariba Account Manager for more information on integration services. ● You can create a Forecast Delivery Schedule or JIT Delivery Schedule against only one line item in a scheduling agreement release. ● The OrderRequestHeader element has the attribute type="new" for a new scheduling agreement. Any updates to the same scheduling agreement contains the attribute type="update" and the Release Number is incremental by 1 for each subsequent version. ● You can create CC invoices against scheduling agreements.
Limitations ● You cannot create a scheduling agreement release containing more than one line item. ● Suppliers cannot create order confirmations or invoices against a scheduling agreement release. However, suppliers can create ship notices for line items having the Commitment Level as “Firm." ● The quantity of the line items in the scheduling agreement must be the sum of the quantities for the line items having the Commitment Level as “Firm.” The line item quantity must not be the sum of all the schedule lines.
About Configuring the Scheduling Agreement Release Integration Scenario Configuring the scheduling agreement release integration scenario 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 Scheduling Agreement Release Integration Scenario [page 155], 2. Configure the Integration Scenario. For more information on , see Configuring the Integration Scenario [page 156]. 3. Configure the Communication Channels. For more information, see Configuring Communication Channels for the Scheduling Agreement Release Integration Scenario [page 158]. 4. Configure the Interface Determination. For more information, see Configuring Interface Determination Settings for the Scheduling Agreement Release Integration Scenario [page 159]. 5. Activate the integration scenario. For more information, see Activating the Scheduling Agreement Release Integration Scenario [page 159].
154
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
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. ○ All the steps of a configuration scenario section must be completed to fully configure a scenario. ○ To configure scheduling agreement releases on your SAP ERP system, see Configuring Scheduling Agreement Releases [page 309].
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. 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 in to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then log
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. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_ScheduleAgreementRelease_Receive ○ Namespace: http://ariba.com/xi/ASN/ScheduleAgreementRelease ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory. 6. Click Finish.
Results
After the integration scenario transfer is completed, the Model Configurator window appears. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
155
Configuring the Integration Scenario Configuring the Integration Scenario involves the following steps: 1. Selecting the model. 2. Assigning the components. 3. Configuring the sender and receiver relations for individual connections. 4. Generating the configuration objects.
Selecting the Model for the Scenario Procedure In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default.
Next Steps After selecting the component view, you must assign components to the application components of the selected integration scenario.
Assigning Components for the Scheduling Agreement Release 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 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
Note If you have multiple ERP systems, add the multiple communication components defined for your multiple SAP ERP systems by repeating the Step 3 and 4. 5. Click the Next Role button (the right arrow) to go to the next screen on the window.
156
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
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
Configuring the Sender and Receiver Relations for Individual Connections for the Scheduling Agreement Release Integration Scenario 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 Receiver 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. Select the following Communication Channel Template: ○ Name: CCT_ScheduleAgreementRelease_cXML_Receiver ○ Namespace: http://ariba.com/xi/ASN/ScheduleAgreementRelease ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIx of ariba.com 6. Click Continue, modify the channel name to CC_ScheduleAgreementRelease_cXML_Receiver, and then click Finish.
Tip If you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction, you can create the communication channel by copying from a channel that has already been configured.
Note The communication channels for SAP ERP Sender system are not required. 7. Click the Activate All Connections button, and then click OK. 8. Click the Save Settings button.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
157
Generating Objects for the Scheduling Agreement Release Integration Scenario Context 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.
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. 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 Scheduling Agreement Release Integration Scenario Context Configure the communication channel CC_ScheduleAgreementRelease_cXML_Receiver under the AR_ScheduleAgreementRelease_Receive Configuration Scenario.
Procedure
1. In the Communication Channel list, double-click CC_ScheduleAgreementRelease_cXML_Receiver
|< Name of the Business System for Ariba Network
|
to open it.
2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration.
158
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Note If you created the channel by copying from an existing channel, you must change the request type to SchedulAgreementReleaseRequest in the Outbound Request Type field. If required, edit the other parameters. 3. Update the cXML version parameter to the 1.2.026 version. 4. Save the changes.
Configuring Interface Determination Settings for the Scheduling Agreement Release Integration Scenario Context Configure the interface determination settings to enable mapping enhancements.
Procedure
1. Expand Interface Determination, and then click
|< Name of the Business System for SAPR3
|
DELINS.DELFOR02./ARBA/DELFOR02 | | < Name of the Business System for Ariba Network . 2. In the Receiver Interfaces section of the Edit Interface Determination window, click the operation mapping value under the Operation Mapping column. Then click the Value List pull-down menu and select Value List. 3. Select the operation mapping IFM_DELINS_DELFOR02_ARBA_2_cXML and click Apply. 4. The Multiplicity column displays the value “0..unbounded”. 5. Save and activate the interface determination settings.
Note Configuring the Interface Determination is a mandatory step if you must configure the mappings.
Activating the Scheduling Agreement Release 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 component setup. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
159
Results This completes the configuration of the scheduling agreement transactions in SAP NetWeaver PI.
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.
Limitation When the task to import the status update for invoices is executed, it returns the status of all invoices for which the status was updated on that particular date. The task does not consider the time when it imports the status update. For example, assume that the task is executed at 12.00 P.M and imports the status for 10 invoices. Now, if the task is executed again at 5.00 P.M. on the same date, it must import the status for only those invoices that were updated after 12.00 P.M. However, the task imports the status update for all the invoices including the invoices for which the status has already been imported.
Workflow
Note Ensure that the Design package is imported into your system and ready before you run these steps. The following steps assume that the different Business Systems are defined in the SLD. For more information, see About Configuring the System Landscape Directory [page 61]. To configure the Invoice Status Update transaction: 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.
160
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
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, the integration scenario loaded into the Integration Repository when the Design package is imported.
Procedure
1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_InvoiceStatusUpdate_ReceiveProxy ○ Namespace: http://ariba.com/xi/ASN/InvoiceStatusUpdateProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory 6. Click Finish.
Results
Once the transfer is completed, the Model Configurator window appears.
About Configuring the Invoice Status Update Integration Scenario Once the Integration Scenario is selected, you must configure it using the following steps: 1. Select 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.
161
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 Invoice Status Update 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
Note For Multi ERP implementation, add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4. 5. Click the Next Role button (the right arrow) to go to the next screen in the window. 6. Click 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
162
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Next Steps After assigning components, 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 Invoice Status Update Integration Scenario Procedure 1. In the Model Configurator, click the Configure Connections button. You must assign Communication Channels to set up the connections.
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.3 onwards. This is required for the other transactions, ERP-initiated invoice, receipts, requisition request, and payment proposal. See the graphic below for details:
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 Receiver 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, and in the next page click the Name field, 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.com/xi/ASN/InvoiceStatusUpdateProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
163
5. Click Continue, modify the channel name to CC_InvoiceStatusUpdateProxy_cXML_Receiver, and then click Finish.
Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction, you can create the communication channel by copying from an already configured channel.
Note The communication channels for SAP ERP Sender system are not required. 6. Click the Activate All Connections button, and then click OK in the dialog box. 7. Click the Save Settings button to save the changes.
Generating Objects for the Invoice Status Update 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, click 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 both the active check boxes – Receiver Determination, and Interface Determination. 3. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. 4. Click on 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.
164
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
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.
Procedure 1. Under Communication Channel, double-click |BS_ASN|CC_InvoiceStatusUpdateProxy_cXML_Receiver to open it, or right-click and select Open. 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration.
Note If you created the channel by copying an existing channel, you need to change the request type to StatusUpdateRequest in the Outbound 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 Interface Determination Settings for the Invoice Status Update Integration Scenario Context Configure the interface determination settings to enable mapping enhancements.
Procedure 1. Expand Interface Determination, and then click |BS_SAPR3_50 | INVSTATUPDT.ITEM | | 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_InvStatUpdt_Item_2_cXML and click Apply. 4. The Multiplicity column displays the value "0..unbounded". Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
165
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 Status Update 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 component setup.
Results This completes the configuration of the ISU transaction in SAP NetWeaver PI.
Canceling MIRO Invoices Context In some cases, you might want to cancel or reverse an invoice sent through MIRO that has already been sent to a supplier. To do this, you must cancel the MIRO invoice and its accounting documents. If you cancel only the MIRO invoice and run the ISU scheduled task, the ISU processes the MIRO invoice, but returns the status as “Processing” as the accounting-related documents still exists for the MIRO task.
Procedure 1. Cancel the MIRO invoice in the T-code MR8M. 2. Cancel the accounting documents associated to the MIRO invoice in the T-Code F-44. 3. Run the ISU scheduled task.
Results The ISU scheduled task picks up the MIRO invoices with the status as “Canceled” and sends it to the supplier.
166
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
ERP-Initiated Invoice Integration Scenario You need to configure the integration scenario for the ERP-initiated invoice transaction in the Integration Directory to be able to run the transaction. All the steps of a configuration scenario section must be completed to fully configure a scenario.
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 61]. To configure the ERP-initiated invoice transaction: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario. 3. Configure the Communication Channels. 4. Activate the new configuration.
Transferring the 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, the integration scenario loaded into the Integration Repository when the design package is imported.
Procedure 1. From the SAP NetWeaver PI main page, select Integration Directory in to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then log
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. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_ERPInvoice_Receive ○ Namespace: http://ariba.com/xi/ASN/ERPInvoice ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIX of ariba.com
Note If you are using Ariba Cloud Integration Release 5.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. All rights reserved.
167
○ Name: AR_ERPInvoice_ReceiveProxy ○ Namespace: http://ariba.com/xi/ASN/ERPInvoiceProxy 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory. 6. Click Finish.
Results
Once the transfer is completed, the Model Configurator window appears.
About Configuring the ERP-Initiated Invoice Integration Scenario Once the Integration Scenario is selected, you must configure it using the following steps: 1. Selecting the model. 2. Assigning the components. 3. Configuring the sender and receiver relations for individual connections. 4. Generating the configuration objects.
Selecting the Model for the Scenario Procedure
In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default.
Next Steps
After selecting the component view, you must assign components to the application components of the selected integration scenario.
168
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Assigning Components for the ERP-Initiated Invoice Integration Scenario Context Prior to assigning components, you must transfer the ERP-initated invoice integration scenario and select the model for the 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 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 . Select the communication component name of the business system for Ariba Network, from the selection list and click Apply.
Note If you have multiple ERP systems, add the multiple communication components defined for your multiple SAP ERP systems by repeating the Step 3 and 4. 5. Click the Next Role button (the right arrow) to go to the next screen on the window. 6. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. 7. Click the row under the Communication Component column, then click the Value List pull-down menu and select Value List . Select the communication component name of the business system for your SAP ERP system from the selection list and click Apply. 8. Click the Save Settings button.
Next Steps After assigning components, 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.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
169
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, you must assign components for the integration scenario.
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 Receiver 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. Select the following Communication Channel Template: ○ Name: CCT_ERPInvoice_cXML_Receiver ○ Namespace: http://ariba.com/xi/ASN/ERPInvoice ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER CIX of ariba.com
Note If you are using the Ariba Cloud Integration Release 5.0 and earlier, specify the following: ○ Name: CCT_ERPInvoiceProxy_cXML_Receiver ○ Namespace: http://ariba.com/xi/ASN/ERPInvoiceProxy 6. Click Continue, modify the channel name to CCT_ERPInvoice_cXML_Receiver, and then click Finish.
Note If you are using the Ariba Cloud Integration Release 5.0 and earlier, specify the channel name as CC_ERPInvoiceProxy_cXML_Receiver . 7. In the Connections from Component Assignment tab in the Configure Connection window, 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. The IDoc receiver Communication Channel needs to be created once for each Business System corresponding to your SAP ERP. If a Communication Channel already exists, you can continue to use it. 8. Select the communication channel CC_IDoc_Sender corresponding to the SAP ERP Business System from the selection list. If you have multiple ERP systems, repeat Step 6 and 7 for all the entries of the Business Systems corresponding to your SAP ERP instances.
170
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Tip If you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction, you can create the communication channel by copying from a channel that has already been configured.
Note The communication channels for SAP ERP Sender system are not required. 9. Click the Activate All Connections button, and then click OK. 10. Click the Save Settings button.
Generating Objects for the ERP-Initiated Invoice Integration Scenario Context Prior to generating the objects, you should have configured sender and receiver relations for the integration scenario. 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.
Procedure 1. In the Model Configurator, click 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 both the active check boxes – Receiver Determination, and Interface Determination. 3. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. 4. Click on 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.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
171
Configuring Communication Channels for the ERP-Initiated Invoice Integration Scenario Context Prior to configuring the communication channels, you must configure the sender and receiver relations for the individual connections. If you are using Ariba Cloud Integration Release 5.0 and earlier, configure the communication channel CC_ERPInvoiceProxy_cXML_Receiver under the AR_ERPInvoice_ReceiveProxy Configuration Scenario.
Procedure 1. In the Communication Channel list, double-click
|< Name of the Business System for Ariba Network
|
CCT_ERPInvoice_cXML_Receiver to open it. If you are using the Ariba Cloud Integration Release 5.0 and earlier, specify CC_ERPInvoiceProxy_cXML_Receiver. 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network buyer account configuration.
Note If you created the channel by copying from an existing channel, you must change the request type to InvoiceCopyRequestin the Outbound Request Type field. If required, edit the other parameters. 3. Update the cXML version parameter to the 1.2.026 version. If you are using the Ariba Cloud Integration Release 5.0 and earlier, specify 1.2.025 version. 4. Save the changes.
Configuring Interface Determination Settings for the ERPInitiated Invoice Integration Scenario Context Configure the interface determination settings to enable mapping enhancements. Prior to configuring the interface determination setting, you must assign communication channels for the integration scenario.
172
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Procedure
1. Expand Interface Determination, and then click
|< Name of the Business System for SAP ERP
|
MIIn_Async_ERPInvoice_cXML | | < Name of the Business System for Ariba Network . If you are using the Ariba Cloud Integration Release 5.0 and earlier, specify INV.CXML.ITEM. 2. In the Receiver Interfaces section of the Edit Interface Determination window, click the operation mapping value under the Operation Mapping column. Then click the Value List pull-down menu and select Value List. 3. Select the operation mapping IFM_FIDCCP_FIDCCP02_ARBA_2_cXML and click Apply. If you are using the Ariba Cloud Integration Release 5.0 and earlier, choose IFM_Inv_cXML_Item_2_cXML. 4. The Multiplicity column displays the value “0..unbounded”. 5. Save and activate the interface determination settings. 6. Repeat Step 3 to 5 for the operation mapping IFM_GSVERF_GSVERF03_ARBA_2_cXML.
Note Configuring the Interface Determination is a mandatory step if you must configure the mappings.
Activating the ERP-Initiated 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 component setup.
Results
This completes the configuration of the ERP-initiated invoice transaction in SAP NetWeaver PI.
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. All the steps of a configuration scenario section must be completed to fully configure a scenario. To send and receive corrections and returns in receipts, see Receipt Integration Scenario for Corrections and Returns in Receipts [page 179]. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
173
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 cXML Adapter Parameters [page 391].
Workflow Configuring the receipt integration scenario involves the following steps: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. For more information, see Transferring the Integration Scenario for Receipts [page 174]. 2. Configure the Integration Scenario. For more information, see About Configuring the Integration Scenario for Receipts [page 175]. 3. Configure the Communication Channels. For more information, see Configuring Communication Channels the Receipts Integration Scenario [page 177], 4. Activate the new configuration. For more information, see Activating the Receipts Integration Scenario [page 178].
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. ○ All the steps of a configuration scenario section must be completed to fully configure a scenario.
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. The integration scenario is loaded into the Integration Repository when the design package is imported.
Procedure 1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen:
174
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
○ Name: AR_Receipt_Receive_Proxy ○ Namespace: http://ariba.com/xi/ASN/ReceiptProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory 6. Click Finish.
Results
After the integration scenario transfer is completed, the Model Configurator window appears.
About Configuring the Integration Scenario for Receipts Once the Integration Scenario is selected, you must configure it using the following steps: 1. Select the Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects.
Selecting the Model for the Scenario Procedure
In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default.
Next Steps
After selecting the component view, you must assign components to the application components of the selected integration scenario.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
175
Assigning Components for the Receipts 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 the row under the Communication Component column, then click the Value List pull-down menu and select Value List
Note If you have multiple ERP systems, add the multiple communication components defined for your multiple SAP ERP systems by repeating the Step# 3 and 4. 5. Click the Next Role button (the right arrow) to go to the next screen on the window. 6. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. 7. Click the row under the Communication Component column, then click the Value List pull-down menu and select Value List
Configuring Connections for the Receipts Integration Scenario 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 Receiver 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. Select the following Communication Channel Template: ○ Name: CCT_ERPReceiptProxy_cXML_Receiver ○ Namespace: http://ariba.com/xi/ASN/ReceiptProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 6. Click Continue, modify the channel name to CC_ERPReceiptProxy_cXML_Receiver, and then click Finish.
176
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Tip If you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction, you can create the communication channel by copying from a channel that has already been configured.
Note The communication channels for SAP ERP Sender system are not required. 7. Click the Activate All Connections button, and then click OK in the dialog box. 8. Click the Save Settings button.
Generating Objects for the Receipts Integration Scenario Context 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
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 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 the Receipts Integration Scenario Context Configure the communication channel CC_ERPReceiptProxy_cXML_Receiver under the AR_Receipt_Receive_Proxy Configuration Scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
177
Procedure 1. Under Communication Channel, double-click CC_ERPReceiptProxy_cXML_Receiver
|B Name of the Business System for Ariba Network
|
to open it.
2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. 3. If you created the channel by copying an existing channel, you need to change the request type to ReceiptRequest in the Outbound Request Type field. If required, edit the other parameters. 4. Update the cXML version parameter to the 1.2.025 version. 5. Specify the Fulfill.dtd in the DTD field. 6. Save the changes.
Configuring Interface Determination Settings for the Receipts Integration Scenario Context Configure the interface determination settings to enable mapping enhancements.
Procedure 1. Expand Interface Determination, and then click |BS_SAPR3_50 | RECEIPT | | 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_Receipt_cXML 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.
Activating the Receipts 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 component setup.
178
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Results This completes the configuration of the receipt transaction in SAP NetWeaver PI.
Additional Receipts Integration Requirement for SAP NetWeaver 7.1 EHP1 Note If you are using SAP NetWeaver 7.1 EHP1, then to ensure that receipts are pulled from your SAP ERP system, you must implement SAP note 1811043. You also need to create and execute a new program Z_1811043_ADJUST_EXTRACTOR in your SAP PI system. The source code of the program is provided in the SAP Note. Create the program in SE38 and execute the same.
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. The cXML ReceiptRequest document sent to suppliers on Ariba Network contains detailed information on the number of goods returned, received, or any corrections made against them. The type attribute in the ReceiptItem stores the “Received” or “Returned” values. A negative value in the line item quantity denotes that there was a correction to the items received or returned. The following movement types support returns and corrections in receipts: ● 101, 103, and 105 to send received quantities ● 102 to send corrections on the received quantity ● 122, 124, and 161 to send returned quantities ● 123 to send corrections on the returned quantities Buyers and suppliers on Ariba Network can view the details on the returns and corrections for line items in the purchase order on the purchase order details and the order history pages. Based on the information in the receipt, the purchase order header status displays if the goods were fully received or partially received. The line items in
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
179
the purchase order on Ariba Network also display the number of items received or returned. For example, here is how items are calculated as received or returned: Line Item Quantity Contains
Receipt Type
Indicates the items have been....
Positive value
Received
Received
Negative value
Received
Corrected against the received quantity
Positive value
Returned
Returned
Negative value
Returned
Corrected against the returned quantity
Note Buyers can create receipts only for standard purchase orders.
Requirements You must have the cXML version 1.2.025 and configure your SAP system to send receipts with returns and corrections against purchase orders. Ensure that you make the necessary changes to the cXML Version parameter in the Communication Channel.
Limitations When you send or receive receipts with corrections and returns, the receipt integration has the following limitations: ● Buyers cannot create receipts for blanket purchase orders. ● Ariba Network Adapter for SAP NetWeaver does not support receipts created prior to Cloud Integration Release 4.0 for returns and corrections. The existing /ARBA/RECEIPT_EXPORT program is no longer used to process receipts that contain returns and corrections.
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
180
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
● 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: ○ ○ ○ ○
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. You must import the CDF_Fulfill_XSD structure that contains the type attribute in the ReceiptItem element. ○ The type attribute stores information on the returns and corrections in receipts. The existing quantity attribute supports positive and negative values while specifying returns and corrections in receipts. ● Buyers can create receipts against multiple purchase orders. ● 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. All rights reserved.
181
Configuring the Receipt Integration Scenario to Support Returns and Corrections Procedure 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. For more information, see Transferring the Integration Scenario for Receipts [page 174]. 2. Configure the Integration Scenario. For more information, see About Configuring the Integration Scenario for Receipts [page 175]. 3. Configure the Communication Channels. For more information, see Configuring Communication Channels the Receipts Integration Scenario [page 177], 4. Activate the new configuration. For more information, see Activating the Receipts Integration Scenario [page 178].
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. 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. For example, you specify which account assignment object is to be charged using the account assignment category. To send multiple receipts for purchase orders with multiple accounting assignments, you must perform the following tasks: 1. Activate the MM Multiple Account Assignments enterprise business function 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]
182
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
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.
Procedure
1. Go to Tcode SPRO and then in the SAP reference IMG navigate to
SAP Customizing Implementation Guide
Activate Business Functions . 2. Select the business function LOG_MM_MAA_1 and click Activate Changes. 3. Click Save.
Results
Now, when you create a purchase requisition or purchase order, the following changes apply: ● For the account assignment category that you have enabled with multiple account assignment functionality, 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. The check box GR non-valuated is now not active. ● Under the Account Assignment tab of the purchase order line item, you can enter amounts into the account assignment lines. ● You can use the multiple account assignment functionality for delivery costs. For example, if you enter a freight condition cost on the line item of a purchase order, the cost of freight applied to split product items is proportional to the cost of the split product items.
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. All rights reserved.
183
Adding the Code in the BADI Implementation for MM Multiple Account Assignments Add the following code, under the method GOODS_RECEIPTS_BDCDATA: DATA : t_ekkn type table of ekkn, wa_ekkn type ekkn, wa_gritems type /ARBA/GOODS_RECEIPTS_ITEM. DATA : lv_rec type I. clear : lv_rec,wa_gritems. refresh : t_ekkn. READ TABLE gritems INTO wa_gritems index 1. select * from ekkn into table t_ekkn where ebeln = wa_gritems-ebeln and ebelp = itemnumber. DESCRIBE TABLE t_ekkn LINES lv_rec. if t_ekkn[] is not INITIAL and lv_rec GT 1. loop at t_ekkn into wa_ekkn. PERFORM fill_bdc_table IN PROGRAM /ARBA/SAPLGOODSRECEIPTS_CREATE USING: 'X' 'SAPMM07M' '0210'. PERFORM fill_bdc_table IN PROGRAM /ARBA/SAPLGOODSRECEIPTS_CREATE USING: '' 'bdc_okcode' '/0'. endloop. endif.
Next Steps
Run the program /ARBA/CR_GR_CREATE to verify that the receipts are posted accurately to SAP ERP.
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. All the steps of a configuration scenario section must be completed to fully configure a scenario.
184
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
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 cXML Adapter Parameters [page 391]. To configure the payment proposal transaction: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario. 3. Configure the Communication Channels. 4. Activate the new configuration.
Transferring the 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, the integration scenario loaded into the Integration Repository when the Design package is imported.
Procedure
1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_PaymentProposal_Receive_Proxy ○ Namespace: http://ariba.com/xi/ASN/PaymentProposalProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory 6. Click Finish.
Results Once the transfer is completed, the Model Configurator window appears. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
185
About Configuring the Payment Proposal Integration Scenario Once the Integration Scenario is selected, you must configure it using the following steps: 1. Select Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects. 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. After selecting the model, you must assign components to the application components of the selected integration scenario.
Assigning Components for the Payment Proposal 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
Note For Multi ERP implementation, add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4. 5. Click the Next Role button (the right arrow) to go to the next screen in the window. 6. Click 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
186
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Next Steps After assigning components, 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 Payment Proposal Integration Scenario 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 BS_ASN in the Receiver 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, and in the next page click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Communication Channel Template: ○ Name: CCT_PaymentProposalProxy_cXML_Receiver ○ Namespace: http://ariba.com/xi/ASN/PaymentProposalProxy ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 5. Click Continue, modify the channel name to CC_PaymentProposalProxy_cXML_Receiver, and then click Finish.
Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction, you can create the communication channel by copying from an already configured channel.
Note The communication channels for SAP ERP Sender system are not required. 6. Click the Activate All Connections button, and then click OK in the dialog box. 7. Click the Save Settings button to save the changes.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
187
Generating Objects for the Payment Proposal 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, click 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 both the active check boxes – Receiver Determination, and Interface Determination. 3. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. 4. Click on 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 Payment Proposal Integration Scenario Context Configure the communication channel CC_PaymentProposalProxy_cXML_Receiver under the AR_PaymentProposal_Receive_Proxy Configuration Scenario.
Procedure 1. Under Communication Channel, double-click |BS_ASN|CC_PaymentProposalProxy_cXML_Receiver to open it, or right-click and select Open. 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration.
Note If you created the channel by copying an existing channel, you need to change the request type to PaymentProposalRequest in the Outbound Request Type field.
188
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
If required, edit the other parameters. For more information about the cXML Adapter parameters, see cXML Adapter Parameters [page 391]. 3. Specify the PaymentRemittance.dtd in the DTD field. 4. Save the changes.
Configuring Interface Determination Settings for the Payment Proposal Integration Scenario Context Configure the interface determination settings to enable mapping enhancements.
Procedure 1. Expand Interface Determination, and then click |BS_SAPR3_50 | PAYMENTPROPOSAL.ITEM | | 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_PaymentProposal_Item_2_cXML 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.
Activating the Payment Proposal 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 component setup.
Results This completes the configuration of the payment proposal transaction in SAP NetWeaver PI. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
189
Note ● In the production environment, for an invoice with a payment block, the payment proposal for this invoice is sent as Hold to Ariba Network. If a user removes the payment block for the invoice, then the payment proposal is again sent as New to Ariba Network. However, this payment proposal is rejected by Ariba Network. To ensure that the payment proposal is not rejected by Ariba Network, the Extrinsic @name=Ariba.relaxedOperationCheck, which is part of the mappings, must be set with the required value. ● SAP NetWeaver PI can be installed as single stack (Java only) or dual stack (ABAP and Java) from version 7.3 onwards. If you are configuring the above mentioned integration scenarios in the single stack Java only instance, as part of generation of objects, the Config wizard generates only one object called Integrated Configuration. However, in case of dual stack instance, as part of generation of objects, the Config wizard generates four objects, Receiver Determination, Interface Determination, Receiver Agreement, and Sender Agreement. For information on the ABAP programs created for the above mentioned outbound transactions, see cXML Adapter Parameters [page 391]. You also need configure proxy in your SAP ERP system. For more information, see cXML Adapter Parameters [page 391].
Enabling Quick Enablement for Payment Proposal Transactions Quick enablement is supported for the payment proposal transaction. As a result, when a payment proposal is sent to Ariba Network, supplier enablement is initiated even if no relationship is maintained in Ariba Network for SAP Vendor and AN Vendor. Quick enablement is achieved by adding the Email ID to the relevant structures in SAP NetWeaver PI and the SAP ERP system. To enable quick enablement, ensure that you have: ● Imported the AribaNetworkAdapterSAPNetweaver.Design.tpz file into your SAP NetWeaver PI system. ● Downloaded the relevant SAP transport requests from connect.ariba.com and imported them into your SAP ERP system.
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. All the steps of a configuration scenario section must be completed to fully configure a scenario.
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 61].
190
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
To configure the requisition request transaction: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario. 3. Configure the Communication Channels. 4. Activate the new configuration.
Transferring the Requisition Request Integration Scenario Context The first step to configure the integration scenario for the ISU transaction is to transfer to the Integration Directory, the integration scenario loaded into the Integration Repository when the Design package is imported.
Procedure 1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_Requisition_Request ○ Namespace: http://ariba.com/xi/ASN/Requisition ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory 6. Click Finish.
Results Once the transfer is completed, the Model Configurator window appears.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
191
About Configuring the Requisition Request Integration Scenario Once the Integration Scenario is selected, you must configure it using the following steps: 1. Assign the Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects.
Selecting the Model for the Scenario Procedure In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default.
Next Steps After selecting the component view, you must assign components to the application components of the selected integration scenario.
Assigning Components for the Requisition Request 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
Note For Multi ERP implementation, add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4.
192
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
5. Click the Next Role button (the right arrow) to go to the next screen in the window. 6. Click 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
Next Steps After assigning components, 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 Requisition Request Integration Scenario 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 BS_ASN in the Receiver 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, and in the next page click the Name field, 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.com/xi/ASN/Requisition ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com 5. Click Continue, modify the channel name to CC_InvoiceStatusUpdateProxy_cXML_Receiver, and then click Finish.
Tip If you have already created and configured a Receiver channel for BS_ASN for another transaction, you can create the communication channel by copying from an already configured channel.
Note The communication channels for SAP ERP Sender system are not required. 6. Click the Activate All Connections button, and then click OK in the dialog box. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
193
7. Click the Save Settings button to save the changes.
Generating Objects for the Requisition Request 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, click 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 both the active check boxes – Receiver Determination, and Interface Determination. 3. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. 4. Click on 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 Requisition Request Integration Scenario Context Configure the communication channel CC_InvoiceStatusUpdateProxy_cXML_Receiver under the AR_InvoiceStatusUpdate_ReceiveProxy Configuration Scenario.
Procedure 1. Under Communication Channel, double-click |BS_ASN|CC_InvoiceStatusUpdateProxy_cXML_Receiver to open it, or right-click and select Open.
194
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration.
Note If you created the channel by copying an existing channel, you need to change the request type to StatusUpdateRequest in the Outbound 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 Interface Determination Settings for the Requisition Request Integration Scenario Context Configure the interface determination settings to enable mapping enhancements.
Procedure 1. Expand Interface Determination, and then click |BS_SAPR3_50 | INVSTATUPDT.ITEM | | 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_InvStatUpdt_Item_2_cXML 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.
Activating for the Requisition Request 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 component setup. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
195
Results This completes the configuration of the ISU transaction in SAP NetWeaver PI.
Request for Quotation Integration Scenario You need to configure the integration scenario for the Request for Quotation transaction in the Integration Directory to be able to run the transaction. All the steps of a configuration scenario section must be completed to fully configure a scenario. To configure Request for Quotation: 1. Transfer the Integration Scenario from the Integration Repository to the Integration Directory. 2. Configure the Integration Scenario. 3. Configure the Communication Channels. 4. Activate the new configuration.
Note To completely enable creation and cancellation of sourcing requests the SAP ERP administrator must also install SAP ERP enhancements. For more information, see the Ariba Sourcing Integration to SAP ERP.
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, the integration scenario loaded into the Integration Repository when the Design package is imported.
Procedure
1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_QuoteRequest_Receive
196
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
○ Namespace: http://ariba.com/xi/ASN/QuoteRequest ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CI5 of ariba.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory 6. Click Finish.
Results Once the transfer is completed, the Model Configurator window appears.
About Configuring the Quotation Integration Scenario Context Once the Integration Scenario is selected, you must configure it using the following steps:
Procedure 1. Select Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects.
Selecting the Model for the Scenario Procedure In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique component view that is selected by default.
Next Steps After selecting the component view, you must assign components to the application components of the selected integration scenario. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
197
Assigning Components for the Quotation 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
Note For Multi ERP implementation, add the multiple communication components defined for your multiple SAP ERP systems by repeating the steps 3 and 4. 5. Click the Next Role button (the right arrow) to go to the next screen in the window. 6. Click 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
Next Steps After assigning components, 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.
Configure Connections for the Quotation Integration Scenario 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 BS_ASN in the Receiver 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, and in the next page click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Communication Channel Template:
198
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
○ Name: CCT_Quote_cXML_Receiver ○ Namespace: http://ariba.com/xi/ASN/QuoteRequest ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CI5 of ariba.com 5. Click Continue, modify the channel name to CC_QuoteRequest_cXML_Receiver, and then click Finish.
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.
Note The communication channels for SAP ERP Sender system are not required. 6. Click the Activate All Connections button, and then click OK in the dialog box. 7. Click the Save Settings button to save the changes.
Generating Objects for the Quotation 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, click 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 both the active check boxes – Receiver Determination, and Interface Determination. 3. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. 4. Click on 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.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
199
Configuring Communication Channels for the Quotation Integration Scenario Context Configure the communication channel CC_QuoteRequest_cXML_Receiver under the AR_QuoteRequest_Receive Configuration Scenario.
Procedure 1. Under Communication Channel, double-click |BS_ASN|CC_QuoteRequest_cXML_Receiver to open it, or right-click and select Open. 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration.
Note If you created the channel by copy from an existing channel, you need to change the request type to QuoteRequest in the Outbound Request Type field. If required, edit the other parameters. 3. Save the changes.
Configuring Interface Determination Setting for the Quotation Integration Scenario Context Configure the interface determination settings to enable mapping enhancements.
Procedure 1. Expand Interface Determination, and then click BS_SAPR3_50 | | REQOTE.ORDERS05./ARBA/RFQ | | 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_REQOTE_ORDERS05_ARBA_RFQ_2_cXML and click Apply. 4. The Multiplicity column displays the value "0..unbounded".
200
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
5. Save the interface determination settings.
Note Configuring the Interface Determination is a mandatory step if you need to configure the mappings.
Activating the Quotation 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 component setup.
Results This completes the configuration of the Quote Request transaction in SAP NetWeaver PI.
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 the steps of a configuration scenario section must be completed to fully configure a scenario. To configure Sourcing Award to Contract: 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 Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
201
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, the integration scenario loaded into the Integration Repository when the Design package is imported.
Procedure 1. From the SAP NetWeaver PI main page, select Integration Directory login into the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Process Integration Scenario from the Enterprise Services Repository screen: ○ Name: AR_QuoteMessage_Send ○ Namespace: http://ariba.com/xi/ASN/QuoteMessage ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CI5 of ariba.com 4. Click Continue. 5. If required, change the name of the scenario for the Integration Directory 6. Click Finish.
Results Once the transfer is completed, the Model Configurator window appears.
202
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
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. Select Model. 2. Assign Components. 3. Configure Connections. 4. Generate Configuration Objects.
Selecting the Model The first integration scenario configuration step is to select a model.
Procedure 1. Click Select Component View in the Model Configurator. 2. Click Apply to select the unique model that is selected by default.
Next Steps Assign components to the application components of the selected integration scenario.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
203
Assigning Components to the Sourcing Award to Contract Integration Scenario The second integration scenario configuration step is to assign components.
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
Note For Multi ERP implementation, add the multiple communication components defined for multiple SAP ERP systems by repeating the steps 3 and 4. 5. Click the Next Role button (the right arrow) to go to the next screen in the window. 6. Click 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
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.
204
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Configuring Connections in the Sourcing Award to Contract Integration Scenario The third integration scenario configuration step is to configure connections.
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 BS_FILE in the Receiver 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, and in the next page click the Name field, then click the Display Input Help drop down list and select Input Help. Select the following Communication Channel Template: ○ Name: CCT_Quote_cXML_Sender ○ Namespace: http://ariba.com/xi/ASN/QuoteMessage ○ Software Component Version: ARIBA_SUPPLIER_CONN_ADAPTER, CI5 of ariba.com 5. Click Continue, modify the channel name to CC_File_QuoteMessage_Sender, and then click Finish.
Tip If you have already created and configured a Sender channel for BS_FILE for another transaction, you can create the communication channel by copy from a channel already configured. 6. Click the Activate All Connections button, and then click OK in the dialog box. 7. Click the Save Settings button to save the changes.
Next Steps Generate the objects. Generation creates the configuration objects if they do not exist. If they already exist, they are reused and enhanced, if required. You can also simulate generation for test purposes.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
205
Generating Objects for the Sourcing Award to Contract Integration Scenario The fourth integration scenario configuration step is to generate objects.
Procedure 1. In the Model Configurator, click 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 both the active check boxes – Sender Determination, and Interface Determination. 3. Select the Create New radio button under Change List for Generated Objects and use the proposed name or modify it. 4. Click on Start to begin generating objects. 5. When object generation is complete, click Apply to save the new configuration settings. A log file is created by this operation. You can close the log file without saving it, or you can optionally save it if required for your needs.
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.
Procedure 1. Under Communication Channel, double-click |BS_FILE|CC_File_QuoteMessage_Sender to open it, or rightclick and select Open. 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration.
Note If you created the channel by copy from an existing channel, you need to change the request type to QuoteMessage in the Inbound Request Type field. 3. If required, edit the other parameters. 4. Save your changes.
206
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Configuring the Interface Determination Settings for the Sourcing Award to Contract Integration Scenario Configure the interface determination settings to enable mapping enhancements.
Context
Configuring the Interface Determination is a mandatory step if you need to configure the mappings.
Procedure
1. Expand Interface Determination, and then click BS_FILE| | MIOut_Async_QuoteMessage_cXML | | BS_BS_SAPR3_50. 2. In the Sender 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_ARBA_CONTRACT and click Apply. 4. Select the operation mapping IFM_cXML_2_ARBA_QUOTE and click Apply. 5. The Multiplicity column displays the value "0..unbounded". 6. Save the interface determination settings.
Results
Document flow occurs based on the extrinsic value when the qualifier is DocumentType: Contract . This extrinsic sequence might vary based on the customization. Check the sequence for the value Contract and add your condition.
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. All rights reserved.
207
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. ● From the Change List tab on the main application screen, activate all the Change Lists containing the objects created and modified during the component setup.
Change Purchase Order Implementation Redesigned This functionality is available for customers using Ariba Cloud Integration 4.0 and earlier. The OOTB change purchase order IDOC sent from SAP ERP contained only line items that had changed. However, Ariba Network requires the complete purchase order cXML. 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 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. These multiple RFC calls are expensive in case a high number of change POs are sent from the SAP ERP system. A custom RFC is created to ensure that when a change PO is sent from the SAP ERP system, only one RFC call is performed from SAP NetWeaver PI to get all the data required to complete the PO cXML.
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. When a change PO IDOC ORDERS05.ORDCHG is sent from the SAP ERP system, from SAP NetWeaver PI this custom RFC is called which in turn calls the BAPI BAPI_PO_GETDETAIL. The custom RFC retrieves all the required data from SAP ERP and sends this data to the target cXML structure.
Changes in SAP NetWeaver PI A new RFC mapping object MM_ORDCHG_ORDERS05_2_CDF_RFC_cXML_XSD is created. As the custom RFC call retrieves all the required data, the UDFs used in the original IDOC mapping have not been used. The following UDFs are deprecated: ● callRfcReadTable ● copyRTItems ● setRTItemsField
208
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
● setRTItemsFieldIfExist ● setRelatedRTItemsField ● getRTUniqueValues ● buildRTConditionFromValuesList ● checkPODeleted ● getReadTableFieldValue, ● createFromReadTableFieldValues, ● removeEmpty, ● getReadTableFieldValueWithCondition
Implementing the Redesigned Change Purchase Order Transaction Procedure 1. Download the AribaNetworkAdapterSAPNetWeaver_vCIX.zip file from connect.ariba.com. 2. Import the AribaNetworkAdapterSAPNetweaver.Design.tpz file into your SAP NetWeaver PI system. 3. Configure the change purchase order scenario in the Integration Directory. 4. If you are using SAP NetWeaver PI 7.3 or above, perform the following sub steps: a. Log in to Enterprise Services Builder. b. Navigate to http://ariba.com/xi/ASN/ChangedPurchaseOrder scenario. c. Expand Message Mapping node and double-click MM_ORDCHG_ORDERS05_2_RFC_cXML_XSD. d. Click on the Signature tab and under Parameters, in the Type column, click on the pull-down menu and select RFC from the Search Result and click Apply.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
209
e. Save and activate the message mapping. f. Expand Operations Mappings node and double-click IFM_ORDCHG_ORDERS05_2_cXML. g. Click the Parameters button and under Parameters, in the Type column, click on the pull-down menu and select RFC from the Search Result and click Apply. 5. After you have configured the scenario in the integration directory, go to Interface Determination and click to change mode.
6. For the RFC_Lookup_Receiver parameter, 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. 7. Download the relevant SAP transport requests from connect.ariba.com and import them into your SAP ERP system.
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. ● In SAP NetWeaver PI 7.3 single stack (Java only) instance, the ccBPM engine is not available. As a result, in the SAP ERP system, 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.3 onwards) through the respective proxies instead of ccBPM's.
210
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Integration Scenarios
Enabling Proxy Implementation for Outbound Transactions Procedure 1. Ensure that you have downloaded the latest AribaNetworkAdapterSAPNetweaver.Design.tpz file from connect.ariba.com and imported it into your SAP NetWeaver PI system. 2. Ensure that you have downloaded the latest SAP transport requests from connect.ariba.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. All rights reserved.
211
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, you can link them to a single Ariba Network account. This feature allows all the documents from particular vendors to be routed to a single Ariba Network account and in the reverse direction, the documents from Ariba Network will be routed to a particular SAP ERP instance. Buying organization or service provider accounts must be enabled for Multi-ERP implementation by Ariba Network Support. The required configuration sections will not be available for accounts that have not been enabled. This section describes the following topics: ● The mechanisms involved in the documents routing ● The configuration to setup integration with Ariba Network of multiple SAP ERP instances.
Document Routing Mechanism In the multi-ERP implementation scenario, each of the SAP ERP systems involved in the integration is identified by a unique identifier. This identifier, called the SystemID, corresponds to the logical system ID of the concerned SAP ERP instance. Each document that passes through the integration will be transformed as follows, to include or to retrieve this unique identifier from the cXML header:
212
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
AN50000000365 0000009999 AN51000000349 T90CLNT090 Depending on the direction, the SystemID identifier is located in different locations: ● For outbound documents, it is located in the From element ● For inbound documents, it is located in the To element. The following figure shows the SystemID identifier location in outbound documents at the top and in inbound documents at the bottom:
In the case of single-ERP implementation, the SystemID identifier is not inserted in the outgoing documents or expected in the incoming documents. In the case of multi-ERP implementation, if the SystemID is not found in an inbound document, it is not processed and fails in the SAP NetWeaver PI integration with a System Error.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
213
Multi-ERP Configuration The multi-ERP implementation requires configuration on all three sides: SAP ERP, SAP NetWeaver PI and Ariba Network.
Configuring the System Landscape Directory You must configure all your SAP ERP instances in the SLD as Technical and Business Systems. For more information, see the “Defining Technical and Business System for SAP R/3” [page 64] section.
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, see the “About Configuring R/3 Connectivity” [page 67] section.
Configuring Integration Scenarios for Multiple ERPs The integration scenarios in the Integration Directory need to be parameterized in order to have the information on the systems and enable message routing.
Configuring ValueMappings You must configure the following entries in the ValueMappings to enable the multi-ERP support for the integration: ● Enable the multi-ERP mode: Source: ● Agency: XI_Global ● Scheme: GlobalVariable ● Value: IsMultiERPModeEnabled Target: ● Agency: XI ● Scheme: GlobalVariable ● Value: true. ● Configure the mappings between Business Systems and Logical System Names:
214
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
Source: ● Agency: LogSys_Source ● Scheme: Lookup ● Value: Logical System Name Target: ● Agency: BusSys_Target ● Scheme: Lookup ● Value: Business System Name.
Note The Group Name is not required. The following table shows an example of values. LogSys_Source
BusSys_Target
T90CLNT090
BS_SAP_46C
T47CLNT800
BS_SAP_47
Setting up Receiver Determination
Each inbound scenario, as well as the scheduled scenarios, has to be configured for messages and calls routing. 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]. For more information on setting up the receiver determination for Ship Notices, see Configuring Receiver Determination Settings for the Ship Notice Integration Scenario [page 107]. For more information on setting up the receiver determination for Invoice, see Configuring Receiver Determination Settings for the Invoice Integration Scenario [page 128]. For more information on setting up the receiver determination for Pay Me Now, see Configuring Receiver Determination Settings for the PayMeNow Integration Scenario [page 135].
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. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
215
Note Buying organization or service provider accounts must be enabled for Multi-ERP implementation by Ariba Network Support. The required configuration sections will not be available for accounts that have not been enabled. Fore more information on Ariba Network setup, see the “Linking Multiple Business Applications” section, in “Configuration,” of the Ariba Network Integration Guide.
Configuring Supplier Quick Enablement Ariba Network Quick Enablement allows buying organizations and Invoice Conversion service providers to create new Ariba Network accounts on behalf of suppliers. They can create these accounts by specifying the supplier’s company information in a Correspondent element in the header of purchase orders sent to the supplier or invoices received from the supplier. Ariba Network uses this information to create the supplier’s account. Quick Enablement is also supported for ERP-initiated invoice and payment proposal transactions. Ariba Network Adapter for SAP NetWeaver supports the Supplier Quick Enablement functionality by providing the required supplier information, email address, and fax number, in the Purchase Order documents (transaction OrderRequest). This information is retrieved from the Vendor Master Data. The Quick Enablement functionality has the following limitations: ● If the information is not maintained for a particular vendor that is not referenced as a supplier in Ariba Network, the purchase orders for this vendors forwarded to Ariba Network will be rejected. ● In case both routing information are available for a particular vendor, the fax will be used as the default routing method. Buying organization or service provider accounts must be enabled for Quick Enablement by Ariba Network Support. Ariba Network ignores the Correspondent element for accounts that have not been enabled. For more information about the Quick Enablement and the cXML, see the Quick Enablement section, in Chapter 3 “Document Addressing and Security”, of the Ariba cXML Solutions Guide. For more information about configuring Ariba Network for Quick Enablement, see the Inviting an Unregistered Supplier section in Chapter 3 “Managing Supplier Relationships”, of the Ariba Network Buyer Administration Guide. For detailed steps to configure support for Multiple SAP instances, see Linking Multiple SAP instances with Ariba Network [page 212]. For details on how to link multiple SAP instances from Ariba Network, see the Ariba Network Integration Guide.
Customizing Data Mappings The Ariba Network Adapter for SAP NetWeaver mapping workbooks are intended as sample only. The buying organizations can customize mappings to suit their business needs.
216
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
In case of outbound transactions, the data is transformed from XML to cXML and then uploaded to Ariba Network. In case of inbound transactions, the data is transformed from cXML to XML and then transferred to the ERP system. The information about how the fields have been mapped between XML and cXML files for both inbound and outbound transactions is available in mapping workbooks provided Ariba. You can download these mapping workbooks from connect.ariba.com. You as a buying organization can change the mapping of fields between XML and cXML according to your business requirements. For example, each buying organization lists requisitioners in cXML in a different way. These differences can be handled by customizing the mappings.
Downloading Mapping Workbooks from Connect Procedure 1. Go to http://connect.ariba.com and log in. 2. Click Ariba Connect for On-Demand Solutions. 3. Click Ariba Network Adapters. 4. Click Ariba Network Adapter for SAP NetWeaver. 5. Under Integration Tools section, click Data Transformation.
Results The mapping workbooks for all transactions are available in a ZIP file.
Enabling Migration of Mapping Customization The mapping customization migration feature allows customization to be retained while upgrading to subsequent versions. All future upgrades will be done using the Release Transfer Tool. To enable the customization to be retained when upgrading from an earlier version to a subsequent version of the Ariba Network Adapter for SAP NetWeaver, you must make customizations only in the designated mapping objects. The Release Transfer Tool will migrate the customizations unchanged.
Caution Do not change any object other than those listed in the table. If you do, upgrade may fail. The following table lists the mapping objects for each transaction: Transaction
Mapping Object
ShipNotice
MM_Custom_CDF_FulFill_XSD_AdvanceShipNotice_2_DESADV_DESADV01
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
217
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 chase orders
MM_Custom_CDF_FulFill_XSD_AdvanceShipNotice_2_DESADV_DELVRY06 ’
Enabling Support for Attachments The cXML protocol supports the attachment of external files of any type to cXML documents. For example, buyers sometimes need to clarify purchase orders with supporting memos, drawings, or faxes. Another example is the CatalogUploadRequest document, which includes catalog files as attachments. Files referenced by cXML documents can reside either on a server accessible by the receiver or within an envelope that also includes the cXML documents themselves. To attach external files to a cXML document in a single envelope, use Multipurpose Internet Mail Extensions (MIME). The cXML document contains references to external parts sent within a multipart MIME envelope. SAP ERP buyers can send and receive attachments for both outbound and inbound documents from Ariba Network. For more information about attachments, see cXML User’s Guide and cXML Solutions Guide. Attachments in cXML can be of any file type, such as .DOC, .PDF, .TXT., JPEG, and so on. Ariba Network supports attachments for the following transactions: ● Purchase Order ● Invoice ● Ship Notice ● Order Confirmation ● Service Entry Sheets The size of the attachments for both inbound and outbound documents cannot exceed 100 MB. Attachments can addtionally have a payload up to 40 MB.
218
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
If you attempt to exceed the file attachment size of 100 MB or 10,000 line items (40 MB) payload, SAP ERP and Ariba Network either prevent or reject the document with an error message. SAP ERP limits the maximum number of line items depending upon the document type. For more information on limitations and workaround, see the following SAP Notes: ● 1779136 - Extended summarization of FI documents ● 1801529 - Error message F5727 "Maximum number of items in FI reached" when release MM document to accounting ● 36353 - AC interface: Summarizing FI documents
Note 1. Buyers must ensure that the rule Your procurement application can download invoice attachments (MIME multipart messages) is enabled in Ariba Network . 2. Multiple attachments are permitted but the combined attachment size must not exceed 100 MB. 3. Although this feature allows processing of all transactional documents through the PI mapping layer, the end-to-end integration for document attachments is only available for invoices and service entry sheets. 4. To avoid performance degradation when sending or receiving multiple documents with large attachments or payload, Ariba recommends that you specify maxMessages=1 in the adapter communication channel in the integration builder.
Attachments for Outbound Documents The outbound documents sent from a configured Ariba Network Adapter to the cXML Adapter can have attachments. The attachments are part of the Comments element in the cXML file. If a cXML document contains attachments, then the structure of the Comments element is as follows: “Attachment URL” 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. ● The PI mapping layer processes the attachment and sends it as an XI message to the cXML adapter. ● The cXML adapter receives the XI message and processes the attachment in the format required by Ariba Network. This setting is based on the configuration that administrators specify on their ERP system. When the cXML adapter downloads the attachments from Ariba Network, it checks the parameter settings specified for the document attachment before processing the attachment. The cXML Adapter maintains a mapping of the content type and the corresponding file extensions for processing of attachments in outbound documents. This mapping is similar to the mapping that is maintained in Ariba Network. 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. All rights reserved.
219
● 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, the adapter tries to download the attachment from the HTTP location specified within the Attachment element in the cXML. In the cXML message, if the cXML Adapter receives the content type but does not receive the filename of the attachment, then the cXML Adapter matches the content type with the content type/file extension mapping it maintains. If the content type matches, then the cXML Adapter generates a random number as filename, appends the file extension, which is the file extension corresponding to the content type, and uploads the cXML document to Ariba Network. If the content type does not match (or content type not available in the response message), 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. The cXML Adapter builds a MIME message and adds the attachment as a mime body part along with the content ID and content type of the attachment before uploading the cXML document to Ariba Network. In Ariba Network, the attachments section provides details about the all the attachments that are associated with a respective outbound document.
Enabling Support for Attachments in Outbound Documents To send attachments in outbound documents, 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. For more information, see Attachments for Outbound Documents [page 219] ● In the communication channel for the outbound document, configure the following attachment related parameters: Parameter
Description
Bypass Proxy Server for Domains
For more information, see Support for Proxy ByPass [page 225].
Active Attachment Authentication
If enabled, HTTP authentication is enabled to access attachments. This option is disabled by default.
Attachment URL UseriD
The user ID to be specified for HTTP authentication.
220
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
Parameter
Description
Attachment URL Password
The password to be specified for HTTP authentication.
Attachment Processing Mode
The mode of processing the attachments for outbound documents. Specify the Send Attachments to Mapping option in the communication channel for the adapter.
For outbound documents, if HTTP authentication is required to access the attachments, you must enable the Active Attachment Authentication parameter and specify values for the authentication parameters, Attachment URL UseriD and Attachment URL Password.
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.
Procedure 1. Go to Tcode SPRO and then click SAP NetWeaver > Application Server > Basis Services > Archive Link > Basic Customizing. 2. Edit the document class and specify the following: ○ Doc.class: TIF or PDF ○ Description: Portable Document Format ○ Application: SAPHTML 3. Edit the document types and define a new document type for invoices. Specify the following: ○ Document Type: ZMMILOGINV ○ Description: Incoming invoice log. invoice verific. ○ Document Class: TIF or PDF 4. Edit the link to create a new document type and define the linkage between the document type and business object BUS2081. In the Display View “Links for Content Repositories: Details” page, ensure that you have the following values: ○ Object Type: BUS2081 ○ Object Type: BUS2081 ○ Document Type: ZMMILOGINV ○ Link Status: X ○ Link Status: X ○ Storage system: MA ○ Link: TOA01 ○ Retention per: Blank or zero Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
221
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.
Procedure 1. Go to transaction SXMB_ADM. 2. Click to expand Integration Engine > Configuration. 3. Increase the time out setting for the parameter "HTTP_TIMEOUT" for category Runtime to 10000. 4. Go to transaction SMICM. 5. Go to the Parameters section. 6. Change the parameter value of icm/HTTP/max_request_size_KB to "307200".
Note Please note that this value goes back to 102400 after the system has rebooted. 7. Go to T code RZ10 for the latest version of the default profile. 8. Update the Extended Maintenance and increase the parameter value of "rdisp/max_wprun_time" to 5400.
Purchase Orders with Attachments A purchase order (PO) document can have multiple attachments, such as product specifications, images, supporting memos, and so on. When Ariba Network receives a PO with attachments, Ariba Network either forwards the attachments to the respective suppliers or stores these attachments to allow online access for suppliers. These stored attachments expire after 180 days and are not available online thereafter. If an error occurs when the cXML Adapter is downloading a document from the HTTP location, the document is not sent to Ariba Network and the cXML Adapter reports back an error to the originating system of the outbound document.
Note In a PO with attachments, if any of the filenames of the attachments had blank spaces or special characters, Ariba Network reported an error and the PO processing failed in Ariba Network. To prevent a PO with such attachments failing in Ariba Network, ensure that the attachment URLs passed in the cXML to the cXML Adapter can be used directly. This means that the URLs must be encoded if required before they are passed to the cXML Adapter. When the purchase order attachment URL contained special characters, they must ensure that the attachment URL is encoded using the UTF-8 compliant character set.Buyers must ensure that they do not encode "http://" in the URL for attachments.
222
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
Attachments for Inbound Documents When the cXML Adapter downloads a document with attachments from Ariba Network, it receives the attachments in a MIME message. For information on how the cXML Adapter processes the attachments, see PDF Invoice Copy Attachments [page 232]. For inbound documents, 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. ● The cXML adapter sends the attachment as a message to the integration engine. The Java mapping in the PI mapping layer reads the attachment from the message received and maps them to the target schema. For invoices and service entry sheets, the PI mapping layers maps it to the IDOC or RFC schema. ● For invoices, the attachment information is available in the IDOC. Attachment in service entry sheets are also supported.
Note Although this feature allows processing of all transactional documents through the PI mapping layer, the endto-end integration for document attachments is only available for invoices and service entry sheets.
Enabling Support for Attachments in Inbound documents You must do the following to send attachments in inbound documents: ● Configure the Attachment Processing Mode parameter and specify the Send Attachments to Mapping option in the communication channel for the adapter. ● Configure the SAP ArchiveLink for storing and assigning the attachments in invoices on the SAP ERP system. For more information, see Configuring the SAP ArchiveLink for Storing and Assigning Attachments on the SAP ERP System [page 221]. ● To read attachments in inbound documents received by the Ariba Network Adapter for SAP NetWeaver, customers must write a Java map. A sample Java map has been provided by Ariba that you can use. This sample Java map is available in the AribaNetworkAdapterSAPNetweaver_vCI_X_FR.zip on connect.ariba.com. The Java map is stored here: /Archive/XI_Mapping_Services/javamappings/com/ ariba/asc/sap/netweaver/xiadapter/javamappings Name of Java file InboundAttachmentHandlerSample.java. ● To process attachments in invoices, implement a BADI for the BADI definition INVOICE_UPDATE in the customer's namespace to store and access attachments for invoices. For more information, see the BADI implementation for the BADI Definition INVOICE_UPDATE section. In the BADI, implement the method CHANGE_BEFORE_UPDATE and place the function module /ARBA/ ARCHIVE_IDOC_ATTACH inside the method. The following parameters must be sent to the function module: Parameter
This parameter stores the......
DOCNUM
IDOC number that contains the attachment.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
223
Parameter
This parameter stores the......
ARCHIV_ID
Content repository identification. For example, "MA".
AR_OBJECT
Document type for the SAP ArchiveLink. For example, "ZMMILOGINV."
OBJECT_ID
The object ID (object identifier) for the SAP ArchiveLink. For example, for an invoice, the object ID would be the concatenation of the MIRO document number and fiscal year.
SAP_OBJECT
The object type for the SAP ArchiveLink business object. For example, BUS2081.
RETURN (Table Parameter)
Error details. This value is available only when there is an error in archiving or creating a link between the archived document.
Sample Code Example: CONSTANTS: c_archiv_id TYPE saearchivi VALUE 'MA', c_ar_object TYPE saeobjart VALUE 'ZMMILOGINV', c_sap_object TYPE saeanwdid VALUE 'BUS2081'. DATA : l_objectid TYPE saeobjid, it_return TYPE bapiret2_t. IF s_rbkp_new-sgtxt IS NOT INITIAL AND s_rbkp_new-bktxt EQ 'ARIBA_ASN'. CLEAR l_objectid. refresh it_return. *Concatenate Invoice number with Fiscal year CONCATENATE s_rbkp_new-belnr s_rbkp_new-gjahr INTO l_objectid. CALL FUNCTION '/ARBA/ARCHIVE_IDOC_ATTACH' EXPORTING docnum = s_rbkp_new-sgtxt archiv_id = c_archiv_id ar_object = c_ar_object object_id = l_objectid sap_object = c_sap_object TABLES return = it_return. ENDIF
Invoices with Attachments An invoice can have multiple attachments such as delivery details, emails, fax, and so on. Ariba Network adds these attachments to a mime message and sends the MIME message to the cXML Adapter for further processing. For inbound documents, the cXML Adapter supports attachments of all file types that are supported by Ariba Network. When the cXML Adapter downloads a document with attachments from Ariba Network, it prefixes the filename of the attachment with a unique random number. This allows the adapter to differentiate attachments within documents and attachments between documents.
224
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
If a error occurs when the cXML Adapter is downloading a document with attachments from Ariba Network, the document is not removed from the pending queue. The cXML Adapter does not send a status update to Ariba Network and attempts to download the document again.
Managing Email Notifications To receive email notifications when there is an error during the attachment processing, maintain the ATTACHMENT_EMAIL_SEND parameter in the /ARBA/PARAM_TAB and specify the email addresses of the administrator that receives the email. The ERP administrator receives an email with details of the invoice number and attachment. An administrator can monitor the errors from the SXMB_MONI if a error occurs while processing attachments.
Support for Proxy ByPass When a purchase order is sent from the SAP ERP system to Ariba Network Adapter for SAP NetWeaver, the attachments of the purchase order are represented as URLs that point to a storage location on an internal domain/server. If the proxy server is configured for the purchase order transaction, then the adapter accesses these URLs and downloads attachments by going through the proxy server. However, customers primarily use a proxy server to connect to domains/servers outside their firewall. As attachments are normally stored on an internal domain/server that is within the firewall, customers do not want the adapter to use their proxy server to download and process attachments. 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. As a result, when a purchase order with attachments is sent from the SAP ERP system, the adapter by passes the proxy server to download and process attachments.
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. In this case, the connection to the HTTPS domain is established using the truststore file or the default JRE cacert file. If the truststore parameter is configured, then you must import the certificates of the HTTPS domains on which attachments are hosted and the Ariba certificate into the truststore file. However, if the truststore parameter is not configured, then you must import the certificates of the HTTPS domains on which attachments are hosted and the Ariba certificate into the cacert keystore of the JRE.
Note The HTTPS support is enabled only for certificates available in the file system or JRE's cacert keystore. In addition, only basic authentication (Username and Password) is supported to download attachments hosted on a HTTPS domain/server.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
225
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. ● 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.
Configuring Proxy Server ByPass for Attachment Processing Context
You must configure the domains/servers that the adapter must bypass for downloading and processing attachments.
Procedure
1. Log on to your SAP NetWeaver system.
226
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
2. In the Model Configurator, open the communication channel for the purchase order transaction. Under Communication Channel, double-click the communication channel |BS_ASN| CC_PurchaseOrder_cXML_Receiver or right-click and select Open. 3. Under the Attachment Configuration section, in the Bypass Proxy Server for Domains field, enter an internal domain/server name or a list of internal domain/server names that the adapter can access by bypassing the proxy server. You can enter multiple domain/server names separated by a comma (,). Some of the sample values for this field are as follows: ○ ariba.com - Adapter bypasses the proxy server for the ariba.com domain. ○ xyz.wiki.org - Adapter bypasses the proxy server for xyz.org and the sub domain xyz.wiki.org. ○ schemas.*.org - Adapter bypasses the proxy server for schemas.org and all sub domains of schemas.org. ○ abc.*.org, javajee.com - Adapter bypasses the proxy server for javajee.com, abc.org, and all sub domains of abc.org. ○ *.* - Adapter by passes the proxy server for all top level domains. ○ *.*.* - Adapter by passes the proxy server for all top level domains and all sub domains of the top level domain 4. Save the changes.
Next Steps After you configure the proxy server bypass, you must import the security certificates. For more information, see About Configuring Security Certificates [page 32].
Troubleshooting Proxy Server ByPass for Attachment Processing Some of the errors that you may encounter during attachment processing are as follows: Description
Error/ Info Message "Http connection status for attachment download is incorrect:
for URL:
This message is logged in the log file when the attachment processing fails as a result of incorrect HTTP connection status. An email notifica tion is also sent with the error details to the configured recipient.
" You may encounter an error such as “No Trusted Certificate Found”
To resolve this error, ensure that you have imported the security certifi cates into the cacert keystore or the truststore (if you have configured). For more information, see Importing Security Certificates into the Java JRE Keystore [page 32] and Importing Security Certificates into the Java JRE TrustStore [page 33]. This message is logged in the log file and an email notification is also sent with the error details to the config ured recipient.
“Domains configured to bypass proxy server”
This info message indicates that the attachment is hosted on a domain that is configured for Proxy ByPass. This message is logged only in the log file.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
227
Support for 2-Way Match In the SAP ERP system, a user can create a purchase order by including line items that do not require a receipt. Such line items are flagged for a 2-way match that includes only the purchase order and invoice during invoice reconciliation. When a purchase order containing line items flagged for a 2-way match is sent from your SAP ERP system, along with the purchase order, the adapter sends information about such line items to Ariba Network. When an invoice for this purchase order is sent by Ariba Network to Ariba Invoice Professional, Ariba Invoice Professional user can reconcile the invoice by performing a 2-way match that includes the purchase order and the corresponding invoice.
Establishing the 2-Way Match Flag in Your SAP ERP System When creating a purchase order in your SAP ERP system, by default, all line items are flagged for a 2-way match.
Using Endpoint Integration You can configure endpoints for outbound documents sent from your ERP system to Ariba Network. The Ariba Network Adapters allow data exchange between your ERP system and Ariba Network. If you have configured an endpoint for your ERP system in Ariba Network, then you must maintain the endpoint information in the Communication channel in SAP NetWeaver. When your Ariba Network Adapter receives an outbound document from your ERP system, the network adapter appends the endpoint information to the cXML and posts the document to Ariba Network. For example, when creating the cXML header for a purchase order, your network adapter checks if the endpoint information is maintained in the communication channel in SAP NetWeaver. If yes, then the network adapter includes the endpoint in the cXML header as follows:
AN02000076701 ERPEndPoint1
AN02000076720 AN02000076701 welcome1a SharedSecret>
228
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
Buyer
ERPEndPoint1 is the value that you have configured in the communication channel in SAP NetWeaver.
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. The endpoint in Ariba Network acts as a document routing placeholder that ensures documents from Ariba Network are sent to the desired system. You can create endpoints in Ariba Network according to your business requirements.
Example Scenarios
● In your system landscape, you have Ariba procurement solution and an ERP system that integrate with Ariba Network. In this case, purchase orders can originate from both Ariba procurement system and the ERP system. You can create two endpoints, one for Ariba procurement solution and the other for the ERP system. This allows Ariba Network to send the corresponding invoices to the respective systems. ● If you want all your invoices to be sent to Ariba procurement solution, you can create and configure an endpoint accordingly.
Enabling Endpoint Integration in SAP NetWeaver Procedure
1. In the Model Configurator, open the communication channel relevant to the outbound transaction you are configuring. Under Communication Channel, double-click the communication channel or right-click to open it. For example, when configuring the Purchase Order Integration Scenario, in the Model Configurator under Communication Channel, double-click on |BS_ASN|CC_PuchaseOrder_cXML_Receiver to open it. 2. In the Parameters tab, specify a value for the endpoint parameter. 3. Save the changes.
Note You must set this only if you have configured an endpoint for your ERP system in Ariba Network.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
229
Endpoint Integration for Multiple ERP Systems Configure end points if you have multiple ERP system. If you have enabled both multi-ERP (for multiple ERP systems) and endpoints in Ariba Network, then you must create system IDs corresponding to the different ERP systems that are there in your system landscape. You then have to create an endpoint for each system ID. For documents that are sent from Ariba Network to ERP, the network adapter uses the system ID to identify the ERP systems that must receive the respective documents. Therefore, it is sufficient to create only one endpoint with the same name for all three system IDs. When you have multiple ERP systems and you create a purchase order, your network adapter checks if the endpoint information is maintained in the communication channel in SAP NetWeaver. If yes, then the network adapter includes the endpoint in the cXML header along with the system ID as illustrated below:
Sample Code
AN02000076701 ARB2 ERPEndPoint1
AN02000076720 AN02000076701 welcome1a SharedSecret> Buyer ERPEndPoint1 is the value that you have configured in the communication channel in SAP NetWeaver and ARB2 is the System ID.
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. SAP NetWeaver PI provides functionality to manage and administer authentication certificates and keystores. As part of this functionality, you can create keys and certificates in SAP NetWeaver and
230
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
store them in the SAP NetWeaver PI Keystore. The keys and certificates that you create in SAP NetWeaver Keystore are grouped bases on views. Therefore, you first need to create a view and then create the required keys and certificates under that view. After you have created the required certificates, you must get them signed by a trusted Certificate Authority (CA) to enable Ariba Network to successfully establish the SSL connection. As a result, when SAP NetWeaver PI sends or receives documents to/from Ariba Network, based on the channel configuration, the cXML Adapter initializes and creates the Ariba Network TrustStoreView and KeystoreView (only if client certificate is selected) and uses the certificates to ensure a successful SSL handshake. In the communication channel for all the inbound and outbound transactions, for Trust Store View and KeyStore View (only if you are using client certificate), you must specify the names of the Views that store the Server certificate and Client certificate respectively. For more information, see Configuring the cXML Adapter to Use the SAP NetWeaver PI Keystore [page 231]. 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. Open the required communication channel. 2. Under Authentication, for the Trust Store View parameter, enter the name of the view that contains the server certificate. 3. To use client certificate for authentication to Ariba Network buyer account, for Credential Mode, select Client certificate from the drop-down list. 4. For the KeyStore View parameter, enter the name of the view that contains the client certificate. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
231
5. Click Save. 6. Repeat this configuration for all the inbound and outbound transactions.
PDF Invoice Copy Attachments In many cases, invoice exception handlers or accounts payable personnel require a rendered format of the invoice data representing the supplier view of the invoice in Ariba Network. They can use the cXML invoice viewer, log into the Ariba Network account to view the invoice, or wait until the invoice PDF is included in the invoice archive. In addition, customers using a 3rd party AP workflow may need a human readable invoice copy and supplier provided attachments during the approval flow to ensure that the AP approver can review invoice data. This can be achieved by using an early archiving approach to store the human readable invoice copy and other supplier attachments. To build the early archiving workflow in SAP NetWeaver PI, customers require a single message that contains the cXML invoice, a human readable representation of the invoice data (PDF Invoice Copy) and all supplier provided invoice attachments without storing any of these on the local file system. PDF invoice copy attachments ensures buying organizations can have their Ariba Network account enabled to generate a copy of the invoice in PDF format and attach it to the invoice. The invoice copy layout of the PDF attachment is very similar to the print layout. This means a structured, complete and consistent invoice view across the supplier base is now available with every invoice for side-by-side comparison of the supplier invoice view with the buyer invoice view in their ERP system.
Language Support Ariba Network generates the PDF invoice copy attachment in the language of the supplier's locale (which is the preferred language configured for the account administrator). See the Ariba Network Guide to Invoicing for a list of supported languages for PDF invoice copy.
Enabling PDF Invoice Copy Attachment This feature is disabled by default. To enable this feature, Ariba Customer Support must turn on PDF generations for your Ariba Network account by selecting the option Generate an invoice copy as a PDF attachment to the invoice. Please have your Designated Support Contact log a service request and an Ariba Customer Support representative will follow up to complete the request.
Note Accounts can be enabled for PDF invoice copy in the archive zip file (if you are archiving invoices) and as attachments to invoices. The invoicing rule “Allow suppliers to send invoice attachments” does not impact the PDF invoice copy attachment generation, and therefore the option to send URLs to view attachments on Ariba Network is only
232
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
available for attachments added by the supplier. If PDF invoice copy generation is enabled in your Ariba Network account, all PDF invoice copy attachments are displayed as URLs.
Requirements In the communication channel for the invoice transaction, you must configure the following parameters depending on how you want to process the invoice data, PDF invoice copy, and other attachments that are part of an invoice downloaded from Ariba Network. Parameter
Description
Attachment Processing Mode
You can specify the following values: ●
Use Local File System – If you specify this value, you must also provide a value for the Attachment Download Location parameter. This is the default option.
●
Use Shared File System – If you specify this value, in addition to specifying a value for the Attachment Download Location parameter, you must specify values for the following parameters:
●
○
Shared System Machine Name
○
Shared System Machine User ID
○
Shared System Machine Password
Embedded In cXML – The cXML Adapter encodes the attachment contents to a Base 64 string using rg.apache.commons.codec.binary.Base64 and embeds the Base 64 string to the header part of the invoice cXML.
Attachment Download Location (only applicable for File system Mode)
A location on the file system where the cXML Adapter must download PDF invoice copy and other attachments that are part of the invoice cXML.
Store cXML Document (Optional) (only applicable for Local or Shared File System Mode)
The cXML Adapter stores the invoice cXML file to the file system location you specified for the Attachment Download Location parameter.
For more information, see Configuring the Attachment Processing Mode for PDF Invoice Copy Attachments [page 245].
Note ● If SAP NetWeaver is running on Windows, then you have to use the Use Shared File System option. As a result, you need to specify the machine name of your SAP ERP system and the Admin username and password to access your SAP ERP system. In addition, you must provide a value for the Attachment Download Location parameter. The value must be a location in the file system of your SAP ERP system where attachments need to be downloaded. The cXML Adapter logs into the SAP ERP system and downloads the attachments in the file system location you specified. ● If SAP NetWeaver is running on Linux and you want to use the Use Local File System, then you need to provide a value for the Attachment Download Location parameter. The value must be a location in the file system of your SAP ERP system that is mounted locally to a location in the file system of your SAP NetWeaver PI system. The mounted folder path must be same to the actual folder path in the SAP ERP system. For example, if the folder location in the SAP ERP system is - /home/usr/attachment then the mounted path in SAP NetWeaver PI must be - /home/usr/attachment. 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. All rights reserved.
233
permission to the folder path in the SAP ERP system. In this case, the cXML Adapter downloads the attachments locally in the mounted path. ● If SAP NetWeaver is running on Linux and you want to use the Use Shared File System, then you need to specify the machine name of your SAP ERP system and the Admin username and password to access your SAP ERP system. In addition, you need to provide a value for the Attachment Download Location parameter. The value must be a shared location in the file system of your SAP ERP system. To ensure that the cXML Adapter can write to this shared location, the Samba Server must be installed and configured in your SAP ERP system to accept NTLM authentication.
Using PDF Invoice Copy Attachments If your account has been enabled to generate PDF invoice copy attachments, PDF invoice copies are generated and attached to the following supplier-submitted invoice types: ● Invoices submitted through EDI or cXML that are not self-signed by the supplier ● Manually created PO-based or non-PO invoices ● Invoices created through CSV import ● Supplier self-signed invoices PDF copies of invoices are not generated for the Invoice Conversion Services (ICS) invoice. For this invoice, the provider or supplier is expected to include a PDF invoice copy as an invoice attachment if required.
Data Flow Overview A PDF copy of the invoice data is automatically added as a MIME (Multipurpose Internet Mail Extension) attachment to the invoice cXML as follows: cid:[email protected] The PDF invoice copy includes the text “Copy of Invoice - Not A Tax Invoice” to indicate that the cXML invoice remains the legal document. The file name for the PDF invoice copy attachment is a randomized file name, for example: kBAIGmcwmN502a7638191182029.pdf
Processing of PDF Invoice Copy Attachments by the cXML Adapter When the cXML Adapter downloads an invoice with attachments from Ariba Network, the processing of attachments by the cXML Adapter depends on the value you specify for the Attachment Processing Mode
234
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
parameter in the communication channel for the invoice transaction. You can specify Use Local File system, Use Shared File System, or Embedded In cXML. The processing by the cXML Adapter for all these options is explained as follows:
“Use Local File System” or “Use Shared File System” Option When the cXML Adapter downloads a document with attachments from Ariba Network, it receives the attachment in a MIME message. If you selected Use Local File System or Use Shared File System, the cXML Adapter: 1. Stores the PDF copy of the invoice and other attachments available in the MIME message to the file system location you specified for the Attachment Download Location parameter. 2. Prefixes the filename of an attachment with the payload ID and a random number. This allows the adapter to differentiate attachments within documents and attachments between documents.
Note The attachment processing can fail if for example, you have not provided any value for the Attachment Download Location field or the cXML Adapter does not have access to the storage location. In this case, an exception is logged in the log file. 3. Generates a file URL for each attachment that indicates the location of the downloaded attachment. The URL is a unique content ID that the cXML Adapter assigns for each attachment. The URL is prefixed with the word cid. The adapter then adds the file URLs under the Extrinsic element tag with the attribute name as invoicePDF (for the PDF invoice copy) and SupplierAttachments (for other attachments) to the header part of the invoice cXML. The URLs are added to the header part because line level attachments are not supported in SAP ERP systems. In addition, URLs at header level ensure the integrity of a document if it is digitally signed. 4. Sends the modified invoice cXML to the mapping services for transformation in SAP NetWeaver PI. During transformation, the file URLs are mapped to IDOC fields. You must implement a BADI for the BADI definition INVOICE_UPDATE in the customer namespace to ensure that when the IDOC reaches the SAP ERP system, the following tasks can be performed: ○ Accesses the attachments from the location specified in the IDOC ○ Stores the attachments in the SAP Archive Link ○ Assigns the attachments to the invoice created in the ERP system To implement the BADI, see BADI Implementation for the BADI Definition INVOICE_UPDATE.
“Embedded In cXML” Option If you selected Embedded In cXML, after downloading the invoice with attachments (PDF copy of the invoice and other supplier provided attachments) from Ariba Network: 1. The cXML Adapter encodes the attachment contents to a Base 64 string using rg.apache.commons.codec.binary.Base64. 2. For the PDF copy of the invoice, the cXML Adapter adds the Extrinsic invoicePDF to the header part of the invoice cXML and embeds the Base 64 string within this Extrinsic element. See sample below. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
235
3. For other attachments from the supplier, the cXML Adapter adds the Extrinsic SupplierAttachments to the header part of the invoice cXML and embeds the Base 64 string within this extrinsic element. If multiple attachments are there, the Base 64 strings for all attachments are embedded within this extrinsic element within ... elements as displayed in the sample below. The cXML structure with the PDF copy of invoice and two supplier added attachments appears as follows: … Base64 encoded string AAgFBgcGBQgHBgcJCAgJDBQNDAsLDBgREg4UHRkeHhwZHBsgJC4nICIrI Base64 encoded string AAgFBgcGBQgHBgcJCAgJDBQNDAsLDBgREg4UHRkeHhwZHBsgJC4nICIrI Base64 encoded string AAgFBgcGBQgHBgcJCAgJDBQNDAsLDBgREg4UHRkeHhwZHBsgJC4nICIrI … 1. The cXML Adapter sends the single cXML message that contains the cXML invoice, PDF invoice copy attachment, and other attachments. 2. To process this cXML message, you need to build a custom workflow in SAP NetWeaver PI to ensure that: ○ The invoice is created in your ERP system. ○ Early or late archiving of attachments is complete. ○ The attachments are assigned to the corresponding invoice. ○ The attachments are deleted from the location where they were downloaded. ○ The cXML invoice itself (including the e-signature if signed) is archived. ○ An email ID is configured to receive email notifications if attachment processing fails in your ERP system.
Note You need to decode the Base 64 string using apache.commons.codec.binary.Base64.
236
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
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. As a result, the cXML Adapter processes attachments of these transactions similar to the manner in which it processes attachments of the invoice transaction.
BADI Implementation for the BADI Definition INVOICE_UPDATE Write the below code in the method CHANGE_BEFORE_UPDATE. ************************************************************************************** This implementation is done to attach SAP Archive Link attachment to an invoice. The invoice number will be generated in this method in S_RBKP_NEW-BELNR. The IDOC number is stored in S_RBKP_NEW-SGTXT. The TIF/PDF URL path is fetched from table EDID4 by passing the IDOC number. After getting the URL path, the attachment document is taken from the specified location and the same is stored in SAP Archive Link using function module SCMS_AO_FILE_CREATE. Once the attachment is stored, the document is assigned to the invoice using function module ARCHIV_CONNECTION_INSERT. The attachment document is deleted from the source location immediately after the document is stored in SAP Archive link. If the document is not attached to the invoice, an email is sent to the email id maintained in /ARBA/PARAM_TAB. The parameter to maintain the email id is INVOICE_EMAIL_SEND. ************************************************************************************** Types Declaration TYPES : BEGIN OF ty_path, docnum TYPE edi_docnum, counter TYPE edi_clustc, segnum TYPE idocdsgnum, segnam TYPE edi_segnam, psgnum TYPE edi_psgnum, dtint2 TYPE edi_dtint2, sdata TYPE edi_sdata, END OF ty_path. TYPES : BEGIN OF ty_documents, filepath TYPE char255, END OF ty_documents. TYPES : BEGIN OF ty_object, objectid TYPE saeobjid, END OF ty_object. TYPES : BEGIN OF ty_error, error TYPE char75, doc TYPE char255, END OF ty_error. TYPES : BEGIN OF ty_delete, objectid TYPE saeobjid, doc TYPE char75, END OF ty_delete. *Data Declaration DATA : l_objectid TYPE saeobjid, l_doctype TYPE saedoktyp, l_counter(4) TYPE c, l_filetype TYPE e1edkt1, l_idoc TYPE char70, l_lines TYPE i, l_sep TYPE c VALUE '.', l_sapsystem TYPE string VALUE 'NONE', l_machineinfo TYPE rfcsi, Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
237
l_pathname TYPE char255, l_filename TYPE char255, l_phys_path TYPE char255, l_archiveid TYPE saearchivi VALUE 'MA', l_documentid TYPE saeardoid, l_sap_object TYPE saeanwdid VALUE 'BUS2081', l_segment TYPE edi_segnam. *Internal table DATA : t_path TYPE TABLE OF ty_path, t_filepath TYPE TABLE OF ty_path, t_documents TYPE TABLE OF ty_documents, t_object TYPE TABLE OF ty_object, t_extension TYPE TABLE OF string, t_error TYPE TABLE OF ty_error, t_packlist TYPE TABLE OF sopcklsti1, t_message TYPE STANDARD TABLE OF solisti1, t_receivers TYPE TABLE OF somlreci1, t_param TYPE TABLE OF /ARBA/param_tab, t_deletefile TYPE TABLE OF ty_delete. *Work area DATA : wa_path TYPE ty_path, wa_filepath TYPE ty_path, wa_documents TYPE ty_documents, wa_object TYPE ty_object, wa_extension TYPE string, wa_error TYPE ty_error, wa_packlist TYPE sopcklsti1, wa_message TYPE solisti1, wa_receivers TYPE somlreci1, wa_param TYPE /ARBA/param_tab, wa_deletefile TYPE ty_delete. *Clearing variables, work areas and internal tables CLEAR : l_objectid, l_doctype, wa_path, wa_filepath, wa_documents, wa_object, l_counter, l_idoc, l_lines, l_doctype, wa_error, wa_packlist, wa_message, wa_receivers, wa_param, wa_deletefile, l_machineinfo. *Clearing internal tables FREE : t_path, t_filepath, t_documents, t_object, t_extension, t_error, t_packlist, t_message, t_receivers, t_param, t_deletefile. *Email data declarations DATA : l_docdata TYPE sodocchgi1, l_subject(200) TYPE c, l_output TYPE char20, l_time TYPE char8, l_date TYPE char200, l_delimiter TYPE c.
238
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
CONSTANTS: c_windows TYPE char7 VALUE 'Windows', c_windowsu TYPE char7 VALUE 'WINDOWS', c_aribainvoice TYPE char9 VALUE 'ARIBA_ASN'. *If IDOC number exists IF s_rbkp_new-sgtxt IS NOT INITIAL AND s_rbkp_new-bktxt EQ c_aribainvoice. *Fetching the File Path from EDID4 SELECT docnum counter segnum segnam psgnum dtint2 sdata FROM edid4 INTO TABLE t_path WHERE docnum = s_rbkp_new-sgtxt AND segnam IN ('E1EDKT1','E1EDKT2'). *Taking the Filepath's into a separate internal table FREE t_filepath[ ]. t_filepath[] = t_path[ ]. SORT t_filepath BY segnum psgnum segnam. DELETE t_filepath WHERE segnam NE 'E1EDKT2'. *Taking E1EDKT1 into separate internal table SORT t_path BY segnam. DELETE t_path WHERE segnam NE 'E1EDKT1'. *If file path exists for the invoice IF t_path IS NOT INITIAL. LOOP AT t_path INTO wa_path. CLEAR: l_filetype, l_segment, l_idoc. IF wa_path-segnam = 'E1EDKT1'. l_filetype = wa_path-sdata. l_segment = wa_path-segnum. ENDIF. IF l_filetype-tdid = '0' OR l_filetype-tdid = '1'. LOOP AT t_filepath INTO wa_filepath WHERE segnam = 'E1EDKT2' AND psgnum = l_segment. l_idoc = wa_filepath-sdata+0(70). CONCATENATE wa_documents-filepath l_idoc INTO wa_documents-filepath. ENDLOOP. *Taking Filepath into separate internal table. APPEND wa_documents TO t_documents. CLEAR wa_documents. ENDIF. ENDLOOP. *Clearing variables CLEAR:l_machineinfo, l_delimiter. *Getting the ERP system machine details(Windows or Linux) CALL FUNCTION 'RFC_GET_SYSTEM_INFO' EXPORTING destination = l_sapsystem IMPORTING rfcsi_export = l_machineinfo. * The attachment location path which comes from SAP XI will be like * (/usr/sap). This will contain forward slash. If the SAP ERP system * is Windows machine, the file attachment location path need to be like * (\usr\sap). IF l_machineinfo-rfcopsys+0(7) = c_windows OR l_machineinfo-rfcopsys+0(7) = c_windowsu. l_delimiter = '\'. ENDIF. LOOP AT t_documents INTO wa_documents. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
239
CLEAR : l_pathname, l_filename, l_documentid. *Getting the file format FREE t_extension. CLEAR: l_lines, l_doctype. *Splitting the file path SPLIT wa_documents-filepath AT l_sep INTO TABLE t_extension. DESCRIBE TABLE t_extension LINES l_lines. READ TABLE t_extension INTO wa_extension INDEX l_lines. *Passing document type l_doctype = wa_extension. TRANSLATE l_doctype TO UPPER CASE. *Concatenate Invoice number with Fiscal year CONCATENATE s_rbkp_new-belnr s_rbkp_new-gjahr INTO l_objectid. *All backward slashes are replaced with forward slashes *in case of Windows machine. IF l_delimiter = '\'. REPLACE ALL OCCURRENCES OF '/' IN wa_documents-filepath WITH l_delimiter. CONCATENATE l_delimiter wa_documents-filepath INTO wa_documents-filepath. ENDIF. *Splitting File path and File name PERFORM split_path IN PROGRAM oaall USING wa_documents-filepath l_pathname l_filename. *Function Module Stores files to Archive Link CALL FUNCTION 'SCMS_AO_FILE_CREATE' EXPORTING arc_id = l_archiveid file = l_filename path = l_pathname doc_type = l_doctype no_delete = 'X' IMPORTING doc_id = l_documentid EXCEPTIONS error_http = 1 error_archiv = 2 error_kernel = 3 error_config = 4 error_file = 5 OTHERS = 6. IF sy-subrc <> 0. *If document is not stored in archivelink, the error *messages are populated into internal table wa_error-doc = wa_documents-filepath. APPEND wa_error TO t_error. CLEAR wa_error. ELSE. *Assigning the Archive Link document to the invoice CALL FUNCTION 'ARCHIV_CONNECTION_INSERT' EXPORTING archiv_id = l_archiveid arc_doc_id = l_documentid ar_object = 'ZMMILOGINV' mandant = sy-mandt object_id = l_objectid sap_object = l_sap_object doc_type = l_doctype EXCEPTIONS error_connectiontable = 1 OTHERS = 2. IF sy-subrc <> 0. *IF sap ARCHIVE link DOCUMENT IS NOT ASSIGNED to invoice, the error
240
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
*messages are populated into internal table wa_error-doc = wa_documents-filepath. APPEND wa_error TO t_error. CLEAR wa_error. ELSE. *Deleting the attachment file from the location after the *attachment is stored in archivelink and assigned to invoice DELETE DATASET wa_documents-filepath. ENDIF. ENDIF. ENDLOOP. ENDIF. *If attachment is not assigned to invoice, email *sent to the specified users IF t_error[ ] IS NOT INITIAL. *getting email IDs from the /ARBA/PARAM_TAB SELECT * FROM /arba/param_tab INTO TABLE t_param WHERE name = 'INVOICE_EMAIL_SEND'. IF sy-subrc = 0. *Email Subject CLEAR : l_output, l_time. *Converting date format CALL FUNCTION 'CONVERSION_EXIT_LDATE_OUTPUT' EXPORTING input = sy-datum IMPORTING output = l_output. *Time Formatting CONCATENATE sy-uzeit+0(2) ':' sy-uzeit+2(2) ':' sy-uzeit+4(2) INTO l_time. *Forming the subject of the email l_subject = text-002. l_docdata-doc_size = 1. l_docdata-obj_langu = sy-langu. l_docdata-obj_name = 'SAPRPT'. l_docdata-obj_descr = l_subject. l_docdata-sensitivty = 'F'. *Forming Body of the email message wa_message-line = text-003. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message. *Populating Date in the email message CLEAR l_date. CONCATENATE 'Date:' l_output l_time sy-zonlo sy-datum+0(4) INTO l_date SEPARATED BY space. wa_message-line = l_date. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message. *Populating invoice document number with the email message CLEAR l_date. CONCATENATE text-005 s_rbkp_new-belnr INTO l_date SEPARATED BY space. wa_message-line = l_date. APPEND wa_message TO t_message. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
241
CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = text-006. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message. *Populating the attachment URL's which are not attached *to the invoice in the email message LOOP AT t_error INTO wa_error. wa_message-line = wa_error-doc. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message. ENDLOOP. wa_message-line = text-007. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = space. APPEND wa_message TO t_message. CLEAR wa_message. wa_message-line = text-008. APPEND wa_message TO t_message. CLEAR wa_message. * Populating the system ID CLEAR l_date. CONCATENATE text-009 sy-sysid sy-mandt INTO l_date SEPARATED BY space. wa_message-line = l_date. APPEND wa_message TO t_message. CLEAR wa_message. wa_packlist-transf_bin = space. wa_packlist-head_start = 1. wa_packlist-head_num = 0. wa_packlist-body_start = 1. DESCRIBE TABLE t_message LINES wa_packlist-body_num. wa_packlist-doc_type = 'RAW'. APPEND wa_packlist TO t_packlist. *Populating the receipients LOOP AT t_param INTO wa_param. wa_receivers-receiver = wa_param-low. wa_receivers-rec_type = 'U'. wa_receivers-com_type = 'INT'. wa_receivers-notif_del = 'X'. wa_receivers-notif_ndel = 'X'. APPEND wa_receivers TO t_receivers. ENDLOOP. *Calling function module to send email CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1' EXPORTING document_data = l_docdata put_in_outbox = 'X' commit_work = 'X' TABLES packing_list = t_packlist contents_txt = t_message receivers = t_receivers EXCEPTIONS too_many_receivers = 1 document_not_sent = 2 document_type_not_exist = 3
242
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
operation_no_authorization parameter_error x_error enqueue_error OTHERS IF sy-subrc <> 0. ENDIF. ENDIF. ENDIF. ENDIF.
= = = = =
4 5 6 7 8.
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, you must: ● Define a new document class. ● Define a new document type for invoice. ● Create a link between the standard business object and the new document type. ● Maintain values for INVOICE_EMAIL_SEND and ZDEL parameters.
Defining a New Document Class for PDF Invoice Copy Attachments Procedure 1. Log on to your SAP ERP system. 2. Start transaction OAD2. 3. Click New Entries. 4. In the Doc Class field, enter PDF. 5. In the Description field, enter a description for the document class. For example, Portable Document Format. 6. In the MIME type field, application/pdf. 7. In the Application field, enter the name of the application that will read the attached invoice PDF. For example, SAPHTML. 8. Click Save.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
243
Defining a New Document Type for Invoice Procedure 1. Log on to your SAP ERP system. 2. Start transaction OAC2. 3. In the Doc. Type field, enter a document type for invoices.
Note You can copy the standard document type for invoice called MMILOGINV and create a new document type starting with Z. In this case, ensure that the value of the Status field is X. You must ensure that the Status of the document type is active. 4. In the Long Name field, enter a long name for the document type. 5. In Doc.Class field, enter the document class that you created earlier. For example, PDF. 6. In the Status field, enter X. 7. Click Save.
Create a Link Between the Standard Business Object and the New Document Type for Invoice Procedure 1. Log on to your SAP ERP system. 2. Start transaction OAC3. 3. Click New Entries. 4. In the Object Type field, enter bus2081 (Standard business object for incoming invoice). 5. In the Document type field, enter the document type you created earlier. 6. In the Link Status field, enter X. 7. In the Storage system field, enter MA. 8. In the Link field, enter TOA01. 9. In the Retention per. Field, enter 0. 10. Click Save.
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. This ensures that when a failure occurs while storing the
244
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
attachments in the SAP Archive Link or assigning the attachments to the invoice, an email notification is sent to the specified email addresses.
Maintaining the ZDEL Parameter You need to specify the delete command for the ZDEL parameter by using transaction SM69. This ensures that once the BADI accesses the attachments from the file location, stores them in the SAP Archive Link, and assigns them to the invoice, the attachments in the file location are deleted.
Configuring the Attachment Processing Mode for PDF Invoice Copy Attachments Procedure 1. Log on to your SAP NetWeaver system. 2. In the Model Configurator, open the communication channel for the invoice transaction. Under Communication Channel, double-click the communication channel |BS_ASN|CC_Invoice_cXML_Sender or right-click and select Open. 3. Under the Attachment Configuration section, specify values for the relevant parameters. 4. Save the changes.
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.0 EHP0 or higher with PI 7.1 or higher. You need to configure the integration scenario for the Request for Quotation transaction in the Integration Directory to be able to run Ariba Spot Quote transactions. For more information about configuring the Request for Quotation integration scenarios, see Request for Quotation Integration Scenario [page 196]. For more information about configuring your SAP ERP for Quote Request and Quote Message cXML documents, see Configuring Quote Request and Quote Message Documents [page 318].
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. 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. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
245
Spot Quotes are automated request for quotations (RFQs), created through a direct integration between your ERP system and Ariba Network, that allows you to build and publish tactical sourcing events with little to no action from project owners in Ariba Sourcing. Spot Quotes are ideal for smaller events, for example an event with 3 to 4 suppliers, allowing you to quickly experience online sourcing without a substantial commitment of time or resources. Spot Quotes originate in a your ERP system and are sent across the Ariba Network to Ariba Sourcing, where an RFQ event is created and published on Ariba Discovery. Suppliers can either be invited as part of the Spot Quote event or matched through Ariba Discovery. 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. Depending on how the Ariba Spot Quote template is configured, 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.
The Ariba Spot Quote solution supports the ability to upload suppliers from your ERP system in to Ariba Network. Uploaded suppliers are invited to create an Ariba Network account through automated notifications, whether the suppliers are buyer invited, Ariba matched, or Ariba suggested. For more information about the Ariba Spot Quote solution, see the Ariba Spot Quote Administration Guide on Help@Ariba.
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. Using the RFQ Module in their SAP ERP system, users can create a request for quotation from a purchase requisition or from scratch. Ariba sends the winning bid information back to the SAP ERP system and a purchase order is created in the SAP ERP system.
246
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
One Vendor Limitation SAP ERP only supports the ability to invite one specific supplier using the invited supplier method. If you want to invite multiple suppliers to your Ariba Spot Quote event, you can create a vendor in SAP ERP to workaround the SAP ERP limitation. For example, create an “Ariba Marketplace Vendor” and configure it to not send any vendor information in the Quote Request cXML document. In this case, the PI does not send supplier information to Ariba and Ariba invites multiple suppliers in the vendor and public matching methods. To overcome the one vendor limitation, you must maintain the following value mappings in the SAP 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, SAP ERP users create an RFQ in SAP ERP MM Standard RFQ Module. Users can create RFQs in SAP ERP from a purchase requisition, from scratch, or potentially from an existing ERP contract. Users select a supplier matching option, enter event open and close dates, and specify line items with material groups and receiving plants. The supplier matching type is tied to the document type and a value mapping must be maintained. A new document type can be created for this purpose or an existing document type can be used.
SAP ERP Quote Message Process After a Spot Quote event ends, Ariba sends a Quote Message cXML document with the winning bid results back to SAP ERP. The Quote Message cXML document is transformed and mapped to BAPI structures in SAP Netweaver PI and a purchase order is created through RFC.
One Time Vendors When you configure the default Spot Quote transaction rules in Ariba Network Buyer, Ariba Network sends the Quote Message cXML document to your ERP system. If the default Spot Quote transaction rule is not configured in Ariba Network Buyer, the Quote Message cXML document stays in the Ariba Network and is not sent to your ERP system. When the default Spot Quote transaction rule is configured to send the Quote Message cXML document to your ERP system, a purchase order cannot be created in your ERP system if the vendor does not exist in your ERP system. To overcome this issue, you can use the one time vendor functionality available in SAP ERP. Utilizing the one time vendor functionality involves creating a one time vendor in SAP ERP and specifying the one time vendor ID in the PI configuration mapping. After the one time vendor ID is mapped in the PI configuration, purchase orders are created using the one time vendor ID and the address for the vendor who submitted the bid. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
247
Additional Data Validation When a purchase order is created in SAP ERP, the quote number is stored on the purchase order as the reference document number. The RFQ number is not stored on the purchase order because SAP ERP validates if the supplier on the RFQ and purchase order are the same. In the approved and public vendor scenarios, the system uses the "Ariba Market Place" vendor, so the vendors on the purchase order and RFQ do not match and the RFQ reference is not stored on the purchase order. You can view the logs to verify that the supplier on the RFQ and purchase order are the same. Logging for purchase order creation: ● TCode used- /nslg1 ● Object - /ARBA/ASCADAPTER ● SubObject- /ARBA/QUOTEMESSAGE The following is an example of the log for a successfully created purchase order:
The following is an example of the log for a purchase order that receives a warning:
248
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
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, please contact your Customer Success Manager or Account Manager for more information on the Ariba Spot Quote Solution. The Ariba Spot Quote solution must be deployed in a new realm, Spot Quote functionality cannot be used in existing Ariba Sourcing realms. Suppliers must be registered on the Ariba Commerce Cloud to participate in Spot Quote events.
SAP ERP and Ariba Spot Quote Integration Requirements Ariba Spot Quote integration with SAP ERP requires SAP ERP 6.0 EHP0 or higher with PI 7.1 or higher. To support the integration of RFQs and QuoteMessages, two new request types, QuoteRequest and QuoteMessage, have been introduced. You must run the configuration wizard for the new request types in order to create the communication channel. In addition, for the cXML Version parameter, enter 1.2.025 or higher for RFQ and QuoteMessage transactions.
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. Users should create a Ariba Marketplace Vendor, that allows them to invite all approved vendors to the Ariba Spot Quote event. ● SAP ERP does not support the ability to add attachments to the RFQ line item level. ● 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. ● After Ariba sends back the bidding results, users can only create purchase orders in SAP ERP. ● Quote attachments are not transferred to purchase orders. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
249
● One-time vendor option does not support purchase order automation. ● Ariba does not support the ability to make changes after the Spot Quote event is published. If changes are made in SAP ERP after the Spot Quote event is published, the event will fail and Ariba will send an email notification to the ERP initiator. ● Ariba recommends not creating RFQs with service lines.
Configuring Ariba Network Buyer Settings for Ariba Spot Quote In order for the Ariba Network to forward quotes from public suppliers, you must configure the default transaction rules in Ariba Network. When you enable the Spot Quote rule in the Ariba Network and the quote message supplier does not exist in your ERP system, the one time vendor specified in the ERP system is used for the transaction. When the rule is disabled, quote messages are not sent to your ERP system and they will fail in the Ariba Network. In this case, you must create a proper relationship with the supplier and then resend the quote message from the Ariba Network.
Messages Mapping for Ariba Spot Quote The following Ariba Spot Quote mapping namespaces are available: ● http://ariba.com/xi/ASN/QuoteRequest ● http://ariba.com/xi/ASN/QuoteMessage For more information, see the mapping worksheets on http://connect.ariba.com.
How to Handle cXML Document Errors for Ariba Spot Quote If the Quote Request cXML document fails in mapping, fix the error and republish the IDoc. If the Quote Message cXML document encounters an error, fix the error and resend the cXML document from the Ariba Network.
Integration of Catalog Data in SAP ERP and Ariba Network When you upgrade to a higher version of the SAP transports, ensure that you make the necessary changes on your NetWeaver PI and SAP ERP system. About Integration of Catalog Data in SAP ERP and Ariba Network [page 251] Enabling the Integration of Catalog Data [page 251]
250
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
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.3, 7.31, or 7.4 and all SAP ERP 6.0 (EHP5 and higher versions). The Ariba Network Adapter for SAP NetWeaver allows buyers to integrate catalog data from an SAP ERP system to Ariba Network seamlessly. Customers can extract the catalog data from the Purchase Information records and Materials Master records to create catalog items in a CIF file and send it to Ariba Network and Ariba Procurement Solution. 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 CIF file contains both mandatory and optional fields that suppliers can use while maintaining the catalog files. For more information about the CIF files, see the Ariba Catalog Format Reference Guide in the Product Documentation > For Users section of the Learning Center. Using the /ARBA/BUYER_CATALOG_EXPORT program, buyers can integrate the catalog data using the following methods: ● Full and incremental load ● Mediated Connectivity Buyers can use the shared secret authentication or the client-based certification to integrate the catalog data from SAP ERP system to Ariba Network. For more information on the shared secret authentication and client-based certification, see the Ariba Network Adapter for SAP NetWeaver® Setup Guide.
Enabling the Integration of Catalog Data This section details the requirements to integrate catalog data on the SAP ERP system. See the Limitation section for functionalities that are not currently supported. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
251
Prerequisite
To upload the catalog CIF file for the full and incremental through the mediated connectivity, buyers must do the following: ● Ensure that the supplier for that you are uploading the catalog must exist on the Ariba Network and Ariba Procurement Solution. The supplier must have an active trading relationship with the buyer. For more information about creating a buyer-supplier relationship, see the Ariba Network Integration Guide. ● Customers must validate and publish the catalog sent from the SAP ERP system from their Ariba Network account. They must also validate the catalog based on the catalog rules specified on Ariba Procurement Solution. ● 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. ● Buyers must ensure that they enable the option, Allow multi-supplier CIF and set the parameter System.Catalog.Network.DefaultMSCif on their Ariba Procurement Solution to support a multi-supplier catalog CIF file from Ariba Network. For information about multi-supplier CIF catalogs in Ariba Procurement Solution, see the Catalog Administration Guide for your Ariba Procurement Solution. ● If the Ariba Network supplier account is configured to use digital certificate authentication, then a valid Secure Socket Layer (SSL) client certificate from one of Ariba Network's trusted Certificate Authorities is required. For more information, see About Configuring Security Certificates section in the Ariba Network Adapter for SAP NetWeaver Setup Guide. ● Enable the Use SAP Add on Suite option in the cXML Configuration. For more information, see About Configuring Security Certificates section in the Ariba Network Adapter for SAP NetWeaver Setup Guide. You must also configure the integration scenario for uploading catalogs. For more information, see Configuring the Integration Directory for Catalogs [page 261]. ● Configure the shared secret authentication or the client-based certificate authentication. For more information see the Ariba Network Adapter for SAP NetWeaver Setup Guide. ● Ensure that you configure the proxy setting for single and dual stack on your SAP ERP system. For more information see the section, Proxy Settings in SAP ERP , in the Ariba Network Adapter for SAP NetWeaver Setup Guide. ● Ensure that you define authorizations for running Ariba Network transactions. For more information, see the section, Defining Authorizations for Running Ariba Network Transactions in the Ariba Network Adapter for SAP NetWeaver Setup Guide. ● To extract the commodity code maintained in the characteristic value of a class that belongs to a specific class type in the Classification view of the Material Master record, buyers must implement the SAP Note 65124. This is required to write the change documents for the classification data for a material master record. ● Ensure that the file size of the catalog CIF file must not exceed the maximum file size supported by Ariba Network. 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.
Limitations
The /ARBA/BUYER_CATALOG_EXPORT program does not support the following: ● Extracting images for catalog line items. ● Extracting catalog items using the Direct Connectivity method is not available in this release.
252
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
● The /ARBA/BUYER_CATALOG_EXPORT program extracts the Valuated Unrestricted-Use Stock at the plantlevel by totaling up the quantity available at the storage location of the plant. The /ARBA/ BUYER_CATALOG_EXPORT program does not track the change made to the quantity. ● When you create a purchase information record at a purchasing organization level for a material, and the material is also associated to a plant, you must ensure that you send the information to Ariba Network before you again extend the same purchase information record of the associated purchasing organization to the plant. If the information has been previously staged on the ERP system, and the same purchase information record is again extended to the plant, the newly extended information is not sent to Ariba Network. For example, you have created a purchase information record at the purchasing organization level(3000) for Material ABC having a Unit Price of $20 and lead time as 2, and the ABC material is also associated to the plant 3000. This information is stored in the \ARBA\CHANGE_DOCS table on the SAP ERP system, but not yet sent to Ariba Network. Now, when you make a change and extend the same purchase information record having the purchasing organization level(3000) to the plant 3000, the /ARBA/BUYER_CATALOG_EXPORT program only sends Unit Price of $20 and lead time as 2 that was previously staged in the \ARBA\CHANGE_DOCS table on the SAP ERP system. The newly extended plant information is not staged in the \ARBA\CHANGE_DOCS table.
Workflow The following describes the workflow for creating a CIF catalog file using the /ARBA/BUYER_CATALOG_EXPORT program from your SAP ERP system: ● The buyer administrator runs the /ARBA/BUYER_CATALOG_EXPORT program on the SAP ERP system. ● The /ARBA/BUYER_CATALOG_EXPORT program imports the catalog data from the Purchase Information records and Materials Master records to create a catalog CIF file. ● The /ARBA/BUYER_CATALOG_EXPORT program creates the catalog CIF file and sends it to Ariba Network. If you have specify the Test Run option and provide a file path, the catalog CIF file is stored on the SAP application server. If you do not specify the Test Run option and want to use the Mediated Connectivity option, the catalog file is sent directly to Ariba Network. ● When the Ariba Network Full Subscription Synchronization task runs, the catalog is uploaded into the Ariba Procurement Solution for buyers.
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. The variants can have different catalog filters and options that are required while running the / ARBA/BUYER_CATALOG_EXPORT program. 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.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
253
Field Name
Catalog Subscription Name
Description
The catalog subscription name is a unique identifier in Ariba for the catalog. Ensure that you do not change the existing name for the catalog subscription while running the full or incremental load. All new versions of the catalog continue to have the same catalog subscription name.
Note You must ensure that you use the existing catalog subscription name for each incremental load you run for an existing catalog. Required field. Currency
The default currency for unit prices for the items in the catalog. Default value: USD Required field.
Charset
The encoding and charset to convert the data in the CIF file. For example, UTF-8. Required field and is case-sensitive.
Code Format
The default commodity code system. You must specify the UNSPSC format. Required field.
Comments
The comments for the catalog.
SupplierId_Domain
The domain for the supplierID. Ensure that you specify the SupplierId_Domain that you maintain for the supplier on the Ariba Procurement Solution. Example: SUPPLIERID_DOMAIN:DUNS Required field.
United Nations Unit of Measure
Select this option to send the catalog in the UNUOM format. Required field.
Catalog Filters
254
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Contains the following filters: ●
Plant
●
Purchase Organization
●
Supplier
●
Purchase Info Category
●
Material Group
●
Material Type
●
Language
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
Field Name
Description
Product Hierarchy OR Classification Code as Commodity Code
Contains two options:
Load Option
Test Run
●
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. .
●
Classification Code: Choose this option if you want to use the commodity code maintained in Classification view for the full or incremental load. If you use this option, you must also specify additional parameters. For more information, see Specifying Parameters for Downloading Commodity Code [page 267].
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.
●
Update Catalog subscription: Choose this option only when you want to update an existing catalog subscription entirely using the full load. Ensure that you do not use this option the first time to create a new catalog subscription.
●
Incremental Load: Allows you to extract only the changed or updated records. You can optionally specify the the date from that you require the records to be extracted from the SAP ERP system.
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. The CIF file is downloaded on your SAP application server. Ensure that the application server directory exists with the necessary permissions before running the catalog import. When you run the incremental load subsequently, the stage table /ARBA/DOC_CHANGE continues to store the previous extracted data for the first run using the Test Run option. The stage table /ARBA/DOC_CHANGE is cleared only after the catalog items are sent to Ariba Network. Specify the directory path in the Dir Path for file download field. The /ARBA/BUYER_CATALOG_EXPORT program validates the file path that you specify. 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.
●
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
Do not select the Test Run option if you choose to upload the CIF file using the mediated connectivity. Specify the Ariba Network ID of the buyer in the Ariba
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
255
Field Name
Description
Network Buyer ID field. Enter the email address of the buyer in the Email Notification to Buyer field. The file path for mediated connectivity must be maintained in the parameter /ARBA/
TEMP_DIRECTORY in the /ARBA/PARAM_TAB table. For more information, see Maintaining the /ARBA/ TEMP_DIRECTORY Parameter [page 266].
Note If the file path is invalid, the /ARBA/ BUYER_CATALOG_EXPORT program displays an error. .
Note ● The /ARBA/BUYER_CATALOG_EXPORT program does not validate the values in the Product Hierarchy or Classification Code fields. However, the catalog file containing blank values in the Product Hierarchy or Classification Code fields fail on Ariba Network as Ariba Network validates this field. To support blank values in this field, customers must specify a corresponding value for the SPSC Code field in the BAdI / ARBA/BUYER_CATALOG_EXPORT. ● SAP ERP does not support deletion of the entire catalog file. As a result, you cannot delete an entire catalog from the SAP ERP system using the Ariba Network Adapter for SAP NetWeaver. ● The SAP ERP system does not delete the catalog CIF files downloaded and saved on the SAP application server during test run. This is applicable for both the full and incremental load. For more information on the catalog fields in the CIF file, see the catalog mapping worksheet, Catalog_SAP_Field_Mappings.xlsx.
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. While extracting data for an incremental load, the /ARBA/BUYER_CATALOG_EXPORT program records all changes done to existing data for material master and purchase info records. When these records are flagged for deletion on the SAP ERP system, these changes are recorded in the catalog CIF file. The column Delete in the CIF file contains the value T (True) to indicate that there has been a change to the catalog item on the SAP ERP system. The following describes how the /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. If you have a material only
256
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
associated to a plant, and you create a purchase information record only at the header-level, the /ARBA/ BUYER_CATALOG_EXPORT program does not consider this purchase information record for the catalog file. ○ The Valid From date for the material is extracted from the Purchasing View on the SAP ERP system. This date is considered as the expiration date of the catalog item on the SAP ERP system. ○ The catalog export program considers the material master record invalid when the From date field has a blank value or stores a date that is earlier than the date on which the record was previously extracted. And the Purchasing View tab for the material has the following plant-specific material status: ○ 01 (Blocked for procurement/where house) OR ○ BP (Blocked for purchasing) OR ○ OB (obsolete materials)
Note When a Full load is run, 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 plantspecific material status as 01, BP, or OB. ○ If there is a purchase information record only at the purchase organization level, the /ARBA/ BUYER_CATALOG_EXPORT program extracts the purchase information record for all the plants associated to the material in the CIF catalog. ○ If the purchase information record information for a material is available at only the plant and purchasing organization level, the catalog data extracted contains the purchase information record information only for the plant that is associated to the material. ○ The /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 extract catalog items for a full load if the vendor material number (Supplier Part ID) maintained for a purchase information record is unavailable. ○ When you associate a purchase information record to a purchasing organization and make changes the existing vendor material number (Supplier Part ID), the /ARBA/BUYER_CATALOG_EXPORT program considers only the newly entered value for the vendor material number and discards the earlier value you changed. ○ When you create a purchase information record for a material, but do not specify a vendor material number, the /ARBA/BUYER_CATALOG_EXPORT program does not consider the purchase information record as a catalog item while running the incremental load. ○ If you mark a purchase information record or material master record for deletion on the SAP ERP system and run the incremental load, the catalog item for the purchase information record or material master record is marked for deletion on Ariba Procurement Solution system. However, if you make changes to the same deleted catalog item on the SAP ERP system and run the incremental load, the deleted catalog item is again sent to Ariba Procurement Solution. But this fails on Ariba Procurement Solution as the catalog item has already been deleted. ○ Purchase information records and Materials master records that have records marked for block or delete. While running an incremental load, any purchase information records and materials master records marked for block or delete is processed as changes and the corresponding item in the CIF file is marked as T in the Delete column. ○ The /ARBA/BUYER_CATALOG_EXPORT program extracts purchase information records and material master records that have vendors marked for block or delete. The /ARBA/BUYER_CATALOG_EXPORT program does not filter the vendor marked for block or delete.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
257
○ If you delete the language for the material description, 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. This Delete column for the catalog item contains “T” in the CIF file. As a result, this item is deleted from Ariba Network and Ariba Procurement Solution. The Item Description field is a mandatory field and if this is marked for delete, Ariba Network automatically deletes the catalog item. ● Applicable to Incremental Load ○ The Flag for deletion option on the SAP ERP system is supported for the following levels: ○ Material or Plant level for material master records ○ Complete Info Record or purchasing organization level for purchase information records ○ When a buyer changes the Vendor Material number (Supplier Part Id) of a valid purchase information record for a material, the /ARBA/BUYER_CATALOG_EXPORT program considers the previously entered value of the vendor material number (Supplier Part ID) in the catalog CIF file. This catalog item with the previously entered value is marked as “T” in the Delete column of the CIF file. The /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. ○ Purchase information records that contains any changes to the vendor material number (Supplier Part ID) are still considered records with changes. The first change that you make to the vendor material number is always recorded as marked for deletion and the /ARBA/BUYER_CATALOG_EXPORT program does not consider any further changes. ○ While running the incremental load, the /ARBA/BUYER_CATALOG_EXPORT program considers the changed and deleted catalog items to already exist in the Ariba procurement system. 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, BP, or OB. ○ When you make changes to a specific field for a material record, and then make changes to the vendor material number for the same material record, the /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 example, ○ You make a change to a description field for a material record. This change is staged in the change table on SAP ERP system. This information is also not yet sent to Ariba Network. ○ For the same material record, you make a change to the vendor material number. ○ You run the incremental load. Now, the /ARBA/BUYER_CATALOG_EXPORT program processes the change as follows: If the catalog item for the material record is already available on Ariba Network, the newly changed vendor material number is added as a new catalog item in the CIF file. This Delete column for this catalog item does not store the "T" value.
Note When you need to make changes to the vendor material number, ensure that you always run the incremental load first and then make the change to the vendor material number. ○ When you extend a material master to a new Plant, ensure that you do not delete the language for the material description. If the language is deleted before you save the material master, the /ARBA/
258
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
BUYER_CATALOG_EXPORT program marks the language for the newly created Plant for deletion. When the record is sent as a catalog item to Ariba Network, this catalog item for the material record fails.
Uploading Catalog Changes Using Mediated Connectivity Buyer can choose to upload the CIF file using the mediated connectivity. When you do not specify the Test Run option in the /ARBA/BUYER_CATALOG_EXPORT program, this program uploads the CIF file using the mediated connectivity. The CIF file is embedded as an attachment in the cXML and sent to Ariba Network. Buyers must specify the Ariba Network ID and email address of the buyer while specifying the conditions for uploading the CIF file using the mediated connectivity. The file path for mediated connectivity must be maintained in the parameter /ARBA/TEMP_DIRECTORY in the / ARBA/PARAM_TAB table. For more information, see Maintaining the /ARBA/TEMP_DIRECTORY Parameter [page 266].If the file path is invalid, Ariba Network displays an error.
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. Buyers must run the incremental load to upload the new values to an existing catalog .CIF file. Buyers can specify a date period while running the incremental load to download data that has been changed or newly during the date period.
Note You must ensure that you use the existing catalog subscription name for each incremental load you run for an existing catalog.
Maintaining Catalog Fields To maintain the Ariba field names in the SAP ERP system, Ariba Account Administrator must first create these custom fields with the required Ariba field name on their Ariba Procurement Solution. These new custom Ariba fields can be mapped to the SAP fields in the /ARBA/FL_MAP table. ● If you add catalog fields to the customized RFC structure, add the field, its structure, and the corresponding Ariba field name to the /ARBA/FL_MAP table to have a preferred column name in the CIF files. If you do not add this field, Ariba Network Adapter for SAP NetWeaver displays the SAP field name for the column on Ariba Network and the Ariba Procurement Solution. ● The CIF file created on the ERP system contains additional fields. 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. All rights reserved.
259
Field Name
Description
MATNR
SAP ERP Material Number
WERKS
Plant
EKORG
Purchase Organization
ESOKZ
Purchase Info Category. For example, Standard, Subcontracting, Pipeline and Consignment.
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, you must download the latest transport files, configure your SAP NetWeaver PI, and SAP ERP systems. 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.
Procedure
1. Go to the T-code /nse38. 2. Enter /ARBA/BUYER_CATALOG_EXPORT in the Program field. 3. Click Execute. 4. Specify the values for the catalog CIF file. For more information on the fields, see section that describes the fields in the /ARBA/BUYER_CATALOG_EXPORT program. 5. Click Execute.
260
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
Handling Errors Buyers can use the transaction, 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 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. 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. 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. The integration scenario is loaded into the Integration Repository when the design package is imported. Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
261
Procedure 1. From the SAP NetWeaver PI main page, select Integration Directory login to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, and then click the Display Input Help pull-down menu and select Input Help. 4. Select the process integration scenario for the following transactions from the Enterprise Services Repository screen: Supplier ○ Catalog Name: AR_CatalogUpload Namespace: http://ariba.com/xi/ASN/Catalog/ Software Component Version: ARBA_SUPPLIER_CONN_ADAPTER CI6 of ariba.com 5. Click Continue. 6. If required, change the name of the scenario for the Integration Directory. 7. Click Finish.
Results Once the integration scenario transfer is completed, the Model Configurator window appears.
Assigning the Model for Catalogs 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 Catalogs 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.
262
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
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
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. 5. Click the Next Role button (the right arrow) to go to the next screen on the window. 6. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. 7. Click the row under the Communication Component column, then click the Value List pull-down menu and select Value List
Configuring Sender and Receiver Relations for Individual Connections For Catalogs 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 Receiver 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: Supplier ○ Catalogs Name: CCT_CatalogUpload_cXML_Receiver Namespace: http://ariba.com/xi/ASN/Catalog/ Software Component Version: ARBA_SUPPLIER_CONN_ADAPTER CI6 of ariba.com 7. Click Continue. 8. You can also choose to modify the channel names. Click Finish.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
263
Tip If you have already created and configured a Receiver channel for the business system for Ariba Network in another transaction, you can create the communication channel by copying from a channel that has already been configured. 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 Receiver Business System Components table. 10. Click on the Value List drop down and select Value List
Generate Objects for Catalogs 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. 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. 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.
Configuring Communication Channels for Catalogs Procedure 1. In the Communication Channel list, double-click the following communication channels to open it: Supplier ○ Catalogs |< Name of the Business System for Ariba Network under the AR_CatalogUpload Configuration Scenario.
264
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
|CCT_CatalogUpload_cXML_Receiver
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network supplier account configuration. 3. Under the cXML Configuration section, select the Use SAP Add on Suite check box.
Note If you created the channel by copying from an existing channel, you must change the request type for each of the transactions to the in the Outbound Request Type field. 4. Update the cXML version parameter to the latest applicable version. 5. If required, edit the other parameters. 6. Save the changes.
Activating the Scenario for Catalogs Procedure
Using the Change List tab on the main application screen, activate all the change lists containing the objects created and modified during the component setup.
Results
This completes the configuration of the outbound transactions in SAP NetWeaver PI.
Configuring your SAP ERP System for Catalog Data Integration Configure the your SAP ERP system for catalog data integration. 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. All rights reserved.
265
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 .CIF file. The /ARBA/BUYER_CATALOG_EXPORT program uses the file path you maintain in this parameter.
Procedure 1. Go to /ARBA/PARAM_TAB table. 2. Maintain the following values: ○ Variable Name: /ARBA/TEMP_DIRECTORY ○ Field Name Number 0 ○ INCL/EXCLI ○ Option EQ ○ Selection value File path to store the catalog .CIF file.
Note A folder "Catalog" is automatically created to store the catalog file. The /ARBA/BUYER_CATALOG_EXPORT program validates the file path that you specify. If the file path is invalid, the /ARBA/ BUYER_CATALOG_EXPORT program displays an error.
Adding Additional Catalog Fields Context To maintain the Ariba field names in the /ARBA/FL_MAP, buyers must first create these additional fields with the required Ariba field name on their Ariba Procurement Solution system. These additional Ariba fields can be mapped to the SAP fields in the /ARBA/FL_MAP table. This is an optional task.
Procedure 1. Start transaction SM30. 2. Choose table view /ARBA/FL_MAP. 3. Click Maintain. The Change View "Table to maintain mapping of SAP to Arib fields": Overview page appears.
266
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
4. 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. Save the changes.
Specifying Parameters for Downloading Commodity Code Context If you use the commodity code maintained in Classification view for the full or incremental load, you must maintain the /ARBA/BUYER_CAT_CLASS_TYPE, /ARBA/BUYER_CAT_CLASS and /ARBA/BUYER_CAT_INT_CHAR_NO. parameters in the /ARBA/PARAM_TAB. The /ARBA/BUYER_CATALOG_EXPORT program displays an error if you do not maintain these parameters when specifying the Classification Code as Commodity Code option.
Procedure 1. Go to /ARBA/PARAM_TAB. 2. Maintain the following Class type in the classification view of material master: ○ Variable Name: /ARBA/BUYER_CAT_CLASS_TYPE ○ Field Name Number: 0 ○ INCL/EXCL: I ○ Option: EQ ○ Selection value: For example, 001. 3. Maintain the following Class in the classification view of material master: ○ Variable Name: /ARBA/BUYER_CAT_CLASS ○ Field Name Number: 0 ○ INCL/EXCL: I ○ Option: EQ ○ Selection value: For example, CL125. 4. Maintain the following Characteristics Name maintained in CL01 transaction:for the characteristic value that must be extracted as the commodity code maintained in the Classification view for a particular class type and class. Ensure that you must user or create a characteristic value of the CHAR data type. ○ Variable Name: /ARBA/BUYER_CAT_INT_CHAR_NO ○ Field Name Number: 0 ○ INCL/EXCL: I Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
267
○ Option: EQ ○ Selection value: For example, CH0023.
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, buyers must implement the SAP Note 65124. This is required to write the change documents for the classification data for a material master record. Buyers must also run the program RCCLUKA2 and set the "Multiple Objects Type Allowed” indicator.
Procedure
1. Go to Tcode SPRO and then click SAP reference IMG. 2. Click Cross Application Components. 3. Click Classification System and then click Classes. 4. Click Maintain Object types and Class types. 5. Click the Object Table folder in the Data Structure tree view. 6. Select the MARA option in the table and double click the Class Types folder. 7. Select Class Type 001 and click the Details button. 8. Ensure that Change Docs check box is selected in the Classification section. 9. Double-click the Objects folder. Ensure that the Chg. docs for Class is selected in the Classification section..
Using Customization Customers can use the BAdI to customize the /ARBA/BUYER_CATALOG_EXPORT program. The interface /ARBA/IF_EXP_BUYER_CATALOG contains the following methods: ● MODIFY_PIR ● MODIFY_MATERIAL ● PUBLISH_CIF
268
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Advanced Configuration Scenarios
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
Purchase Order (New and Change)
Order Confirmation
Ship Notice
Invoice
Remittance
Order Status Request
ScheduleAgreementReleaseRequest
Message Type
ORDERS05
ORDERS
ORDERS05
ORDRSP
DELVRY06
DESADV
INVOIC02
INVOIC
PEXR2001
REMADV
ORDERS05
ORDERS
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]
270
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Configuring 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 Partner function
Message type
IDoc type
Value
VN
ORDERS
ORDERS05
Application
Message type
Process Code
Change
EF
NEUS
ME10
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 Partner function
Message type
IDoc type
Application
Message type
Process Code
272
Value
VN
ORDCHG
ORDERS05
EF
NEUS
ME11
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Parameter Change
Value
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 Partner function
Message type
Process Code
Value
VN
INVOIC
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 Partner function
Message type
Process Code
Value
VN
ORDRSP
ORDR
Select Trigger immediately as the value for the Processing by Function Module parameter. ● Configure Ship Notice with these inbound parameters: Parameter Partner function
Message type
Process Code
Value
VN
DESADV
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 Partner function
Message type
IDoc Type
Value
VN
REMADV
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 Partner function
Message type
Process Code
Value
VN
FIDCCH
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]
274
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Configuring the 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 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.
276
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Note ○ You must maintain the logical system name for the Invoice Status Update (ISU) in the /ARBA/ PARAM_TAB table. ○ To maintain the logical system name for Remittances, you must apply the SAP Note 1441799 - IDoc REMADV: Alternative partner category and partner number. ○ If you are a customer using SAP ERP 6.0, EPH1, ensure that to make the necessary source code changes and the assigned corrections. ○ If you are a customer using SAP ERP 6.0, EPH 2 and EPH 3, and you already have applied the SAP Note 1441799, then ensure that you make the assigned corrections. If you do not have the SAP Note, you must make the necessary source code changes and the assigned corrections. ○ If you are a customer using SAP ERP 6.0, EPH 7 and higher, the SAP Note 1441799 is already applied. You must ensure that you make the assigned corrections.
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.
Procedure 1. Start the NACE transaction. 2. Click EL application type and then click Output Types. A new window appears. 3. Double-click the LPH1 output type. A new window appears. 4. Click the Default values tab and maintain the following values: ○ Dispatch time: Send immediately (when saving the application) ○ Transmission Medium: EDI ○ Partner Function: LS ○ Communication strategy: To be left blank 5. Define the LS partner profile and maintain the following values: ○ Medium: EDI ○ Funct: LS ○ Name: Logical system 6. Save the changes, 7. Repeat Step 3 to 6 for the LPJ1 output type. 8. Go back to the NACE transaction. 9. Click EL application type and then click Condition Records. A new window appears. 10. Double-click the LPH1 output type. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
277
11. Click Purchasing Output Determination: Doc.Type/Purch.Org/Vendor and then click Enter. A new window appear. 12. Maintain the following values:Purchasing Doc.Type/Purch.Org/VendorDoc.Type (LPA or LP) used while creating the scheduling agreement release, Purchase Organization and Vendor. Click Execute. ○ Purchasing Doc.Type: LPA ○ Purch. Organization: Enter the purchase organization. ○ Vendor: Enter the vendor details. 13. Repeat Step 10 to 11 for the LPJ1 output type.
Configuring the Partner Profile for Invoices Context
Configure to maintain the SAP ERP partner profile at a logical system level for invoices.
Procedure
1. Assign the partner to a company code. Go to SPRO > MM > Logistic Invoice Verification > EDI > Assign company code. Ensure that you have the following values: ○ Partn. Type: LS ○ PartnerNo: Enter the logical system name created for the partner profile. ○ Comp.code name in the invoice: Enter the company code name. ○ CoCd: Enter the company code. 2. Assign the program parameters. Go to SPRO > MM > Logistic Invoice Verification > EDI > Enter Program Parameters. Ensure that you have the following values: ○ Partn. Type: LS ○ PartnerNo: Enter the logical system name created for the partner profile. ○ CoCd: Enter the company code. ○ Company Name: Enter the company name. ○ City: Enter the city. 3. Assign the tax codes. Go to SPRO > MM > Logistic Invoice Verification > EDI > Assign Tax codes. Ensure that you have the following values: ○ Partn. Type: LS ○ PartnerNo: Enter the logical system name created for the partner profile. ○ Tax type: Enter the tax type. ○ Tax rate: Enter the tax rate. ○ Ctr: Enter a value.
278
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Creating an Output Type for the Entry Sheet Application Procedure 1. Start transaction NACE. 2. Select application ES Entry Sheet and click Output types. 3. In the Processing routines section, create an entry as follows: ○ Transmission Medium - 8 (Special Function) ○ Program - /ARBA/ENTRYSHEET_UPDATE ○ FORM routine - SEND_ENTRYSHEET_RESPONSE ○ Save the entry. 4. In the Partner Functions section, create an entry as follows: ○ Medium - 8 (Special Function) ○ Function - VN ○ Description - Vendor 5. Save the entry.
Maintaining Condition Records for Outbound Transactions: POs Procedure 1. Using Tcode MN04 or NACE or NACR, in the screen enter output type NEUS and click Key combination. 2. Choose Purchasing Output Determination: Purch. Org./Vendor for EDI in the pop-up window and click the check button to enter. 3. Verify the values for vendor number, partner function (VN), Partner number, Medium (6), and Time (4). 4. Click save.
Note If you also want to generate a printout, maintain the condition record for message type NEUS and select Purchasing Output Determination: Document Type. Save the condition record.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
279
Maintaining Condition Records for Outbound Transactions: Service Sheets Procedure 1. In the main screen when you start the transaction NACE, select application ES Entry Sheet and click Condition records. 2. Click the relevant output type. 3. Click on Condition records. 4. Select Purchasing Output Determination: Document Type option. 5. Click the Execute button and maintain the following parameters by creating a new entry: ○ Document Type - NB (for example) ○ Partner Function - VN ○ Partner Number - 1000 (for example) ○ Medium - 8 (Special Function) ○ Date/Time - 4 (when the application is saved) 6. Save the entry.
Making Additional Change PO Configurations Procedure 1. Navigate to Tcode SPRO, and in the SAP reference IMG navigate to Messages
Output control
Messages Types
Material Management
Define Messages type for purchase order
Purchasing Fine – Tune
control: Purchase order . 2. Add new entries for condition type NEUS for Change Purchase Order with operation as 2. 3. Save the entry.
Maintaining Variants for Remittance For generating IDocs from F110, maintain the variant for report RFFOEDI1. You must also configure the company code, house bank, and payment method to generate IDoc for EDI.
Making Additional Invoice Configurations Configure tax types and tax codes using transaction code OBCD. For more information, see the sample data mapping for InvoiceDetailRequest.
280
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
.To assign the partner to a company code, use this configuration path: ● SPRO > MM > Logistic Invoice Verification > EDI > Assign company code To assign program parameters, use this configuration path: ● SPRO > MM > Logistic Invoice Verification > EDI > Enter Program Parameters To configure direct posting to general ledger accounts and material accounts, use this configuration path: ● SPRO > MM > Logistic Invoice Verification > Incoming Invoice > Activate Direct Posting to G/L Accounts and Material Accounts ● Set both parameters to “active” To configure how unplanned delivery costs are posted, 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, and edit the entry as follows: Function Module
Function Type
IDOC_INPUT_IN VOIC_MRM
F
Basic Type
INVO IC02
Exten sion
/ ARB A/ INV OIC E
Message Type
Message Code
INVOIC
Msg. Func tion
Object Type
MM
Direc tion
BUS208 1
2
Navigate to transaction code WE82 and add the following entry: Message Type
INVOIC
Basic Type
INVOIC02
Extension
/ARBA/INVOICE
Release
40A
Configuring Invoices From Ariba Network When an ERP system receives invoices from Ariba Network, the invoice is created and stored through the IDOC. To create and store invoices successfully in the IDOC, ensure that you have the following configuration: ● Go to TCode OBCE. ● Create an entry at the vendor or logical system level in the Partn. Type field. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
281
● Enter the partner number and company code. ● Enter a value in the following fields in the Posting Details section: ○ G/L db.pstg ky ○ G/L cr.pstng ky ○ Vend.deb.pstng ky ○ Vend.cred.pstng ky ○ Tax-ex.tax code ○ Invoice doc.type ○ Cred.memo doc.type
Making Additional Tax and Accrual Calculation Configurations Make the following configurations in the case of purchase order / non purchase order invoices having a tax code with full / partial accrual condition posted to different accounts. In the ftxp transaction, for a particular tax code, different tax levels are maintained using KTOSL (Transaction Key) and KSCHL (Condition Type) For example, for a particular tax code in the Self Assessment section for the tax type A/P Sales Tax 1 Use, if the tax rate is 60.000%, then the transaction key for this tax level is MW1 and the condition type is JP1U. When the function CALCULATE_TAX_FROM_GROSSAMOUNT returns the result table, it consists of a separate entry for accrual tax, which contains the transaction key and the condition type. As transaction key and condition type may vary from SAP system to system, they are configurable using the field value pair in the custom table. You must maintain the following values in the /ARBA/PARAM_TAB table: NAME
FIELDNAME
SIGN
OPTI
LOW
ACCRUAL_CONDITION_TYPE
JP1U
I
EQ
JP1U
ACCRUAL_TRANSACTION_KEY
MW1
I
EQ
MW1
ACCRUAL_TRANSACTION_KEY
MW2
I
EQ
MW2
HIGH
Note ● The values in this table are examples of a typical configuration and may vary depending on the SAP system configuration. 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 the case of multiple conditions for a single NAME you must change the value of FIELDNAME to form a composite key. ● These three parameters in the table are only used by the ERP CC INVOICE scheduled task. In addition to maintaining additional tax and accrual calculation configurations, you can store values for other configuration parameters in the table /ARBA/PARAM_TAB. Earlier document type RE was hard coded and as a result payment proposals were not getting pulled for document types other than RE. Now, no document type is hard coded. 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.
282
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
In addition, earlier in the SAP system, accounting document number (BELNR) was key field and was sent as the output invoice document number. To send the document reference number (XBLNR) as the output key field instead of BELNR, a new parameter is INVOICE_DOC_OPTION is added to /ARBA/PARAM_TAB because XBLNR is a non mandatory field. You must set the INVOICE_DOC_OPTION to XBLNR to ensure that XBLNR is returned as the output invoice document number. The following table illustrates configuration parameters and their corresponding values: NAME
FIELDNAME
SIGN
OPTI
ERPCC
K~XBLNR
I
NE
LOW
HIGH
DESCRIPTION To filter XBLNR not having any value for ERP-initiated invoices, payment propos als, and invoice status update.
Note If you are using a Cloud Integration Release version earlier than Release 4.0, then you must use the CHECK_XBLNR_EMPTY parameter.
INVOICE_DOC_OPTION
I
EQ
XBLNR
To send output invoice number as
XBLNR for ERP-initiated invoices, pay ment proposals, and invoice status up date. To store general document type for ERP-initiated invoices, payment propos als, and invoice status update.
INVOICE_DOC_TYPE
KR
I
EQ
KR
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 L_AUTO
ZP
I
EQ
ZP
To store doc type required for full auto matic payment for invoice status up date.
INVOICE_DOC_TYPE_FUL L_MANUAL
KZ
I
EQ
KZ
To store doc type required for full man ual payment for invoice status update.
INVOICE_DOC_TYPE_PAR TIAL
KA
I
EQ
KA
To store doc type required for partial payment for invoice status update.
INVOICE_DOC_TYPE_PAR TIAL
KZ
I
EQ
KZ
INVOIC02_REJECT_STAT US
51, 71, and so on.
I
EQ
51,71, and so on.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Status number of the Invoice IDOC which are rejected. if you do not main tain anything, the default value will be 51.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
283
NAME
FIELDNAME
SIGN
OPTI
LOW
AVOID_DUPLICATE_ISU_ PP
X
I
EQ
X
HIGH
DESCRIPTION This ensures that duplicate entries for payment proposal and invoice status up date are not sent to Ariba Network. If you do not maintain this parameter, du plicate entries for payment proposal and invoice status update are sent to Ariba Network if: ●
An invoice is changed on 22.04.2012 and the PP and ISU are sent to Ariba Network on 22.04.2012 and the PP and ISU programs are run on the same date 22.04.2012.
●
The PP and ISU for an invoice are already sent to Ariba Network and a user changes a field that does not affect the PP or ISU for example, Vendor Text, and runs the PP and
ISU programs. NET_DISCOUNT_DAYS
284
X
I
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
EQ
X
You need to maintain this parameter if you want to pay only on or after the due date without any discount.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
NAME
FIELDNAME
SIGN
OPTI
LOW
HIGH
GRACE_TIME_ISU_PP
Unique Value (Text or Num ber)
I
EQ
5,10, 15, so on
DESCRIPTION You must maintain the value of this pa rameter in minutes. The number of mi 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. For example, you perform the following steps: Create an invoice Invoice1 at 10:05 A.M. The input time for the ERPCC scheduled task is 10:00 A.M. Assuming that the ERPCC scheduled task starts at 10:00 A.M. and ends at 10:15 A.M. Create an invoice Invoice2 at 10:20 A.M. Now, if current time (system time) is 10:20 A.M. and ISU and PP is scheduled to start at 10:05 A.M. and end beyond 10.20 A.M., it will pick the ISU or PP for the invoice Invoice2 created at 10:20 A.M. This ISU and PP will fail in Ariba Network because Invoice2 has not been sent to Ariba Network. To ensure that ISU and PP is not sent for an invoice that has not been sent to Ariba Network, you need to maintain a value for this parameter. In the above example, if you had maintained 5 mi nutes as the value for this parameter, then the end time for the ISU or PP changes to 10:15.M. (Current time 10:20 – 5 minutes). As a result, the scheduled task does not pick the ISU or
PP for the invoice Invoice2 created at 10:20 A.M.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
285
NAME
FIELDNAME
SIGN
OPTI
LOW
ERP_INV_PROCESSED_ST ATUS
X
I
EQ
X
HIGH
DESCRIPTION The invoices that you create in your SAP ERP system and send to Ariba Network are stored in the table /ARBA/
AN_ERPINV. When the InvoiceStatusUpdate (ISU) and Payment Proposal (PP) scheduled tasks run at their scheduled time, the scheduled tasks queries the /
ARBA/AN_ERPINV table and sends the ISU and PP only for the invoices that are available in the table. To ensure that ISU and PP scheduled tasks can query the table, you must provide the required value for this parameter. The ISU and PP scheduled tasks 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, ERPCC scheduled task stores information on the ERP-initiated in voices in the /ARBA/AN_ERPINV table. When you send an ISU or PP from your ERP system, 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. ●
If you have not enabled the ERP CC scheduled task and send ERP-initi ated invoices from your ERP sys tem, ERP CC scheduled task does not store information on the ERP-in itiated invoices in the / ARBA_AN_ERPINV table. When you send an ISU or PP from your ERP system, the ISU or PP scheduled task looks into the / ARBA_AN_ERPINV table to filter ERP-initiated invoices associated to the ISU or PP. In this case, 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
286
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
NAME
FIELDNAME
SIGN
OPTI
LOW
HIGH
DESCRIPTION Ariba Network-generated invoices associated to the ISU or PP to Ariba Network.
INVOICE_DOC_TYPE
RE
TAX_AT_LINE
X
I
EQ
RE
Stores doc types for the ERP-initiated in voice transaction. If you maintain this parameter with the document types, then the ERP-initiated invoice function module retrieves invoices for the speci fied document types. If you do not main tain this parameter, then the ERP-initi ated invoice function module retrieves invoices for the document types main tained in INVOICE_DOC_TYPE table. If in OBCO transaction, you have se lected the check box for the tax jurisdic tion procedure (see graphic below), then the tax is stored line-by-line in the BSET table. If you maintain the value X for the this parameter, then the tax amount for each line item in BSET is retrieved and popu lated against each line item in the ERPinitiated invoice. In addition, the tax is also updated at the header level. If in OBCO transaction, you have not se lected the check box for the tax jurisdic tion procedure, then total tax for all line items is stored in the BSET table as a consolidated tax amount. In this case, you must maintain the value “ ” (blank) or do not maintain this parameter. The line item tax amount is added to the cor responding line item amount and the consolidated tax amount is added to the header level of the ERP-initiated invoice. Tax amount is not shown at the line item level.
If you maintain single value for a parameter, the FIELDNAME field can be left blank. However, if you want to maintain multiple values for a parameter, you must specify a value for the FIELDNAME field for each new parameter value to ensure a unique record is formed.
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 program does not return any records.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
287
Maintaining Tax Jurisdiction
Maintaining Bank Key for the House Bank for Payment Remittance Advice You must configure the bank key, payment method, and general ledger for the house bank to generate IDoc for Payment Remittance Advice. The G/L Account to be posted to is derived using the house bank, which is maintained for the payer company code for the payment method “E” and the remittance currency. These entries can be maintained in transaction FBZP. The G/L Account for Cash Discount is derived using the Chart of account for the CoCd and the transaction key SKE. These entries can be maintained in transaction FBKP.
Note If entries are not maintained as mentioned in the preceding section, the IDoc post will fail as it will not be able to find the correct accounts to post to.
Making User Exit Enhancements to Support Shipping and Handling Charges /ARBA/Invoice is available as an extension of INVOIC02.
288
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
To process the data sent in the IDoc, make the following changes in the User Exit provided by SAP. To access the user exit, navigate to the transaction SMOD, and use the Enhancement name: MRMH0002 and Exit: EXIT_SAPLMRMH_014. The following example code shows the changes made to the user exit: DATA: ls_data_s01 TYPE e1eds01, lv_beznk TYPE mrm_rbkpv-beznk, lv_wskto TYPE mrm_rbkpv-wskto, ls_data_k05 TYPE e1edk05, lv_mwskz TYPE edi5279_a, lv_mwskz_bkn TYPE mwskz_mrm. DATA:ls_/ARBA/ACCOUNT_DATA TYPE /ARBA/ACCOUNT_DATA, ls_cobl_mrm TYPE cobl_mrm, ls_sdata TYPE edi_sdata OCCURS 0, ls_lifnr TYPE lifnr, ls_ebelen TYPE ebeln, ls_e1edp02 TYPE e1edp02, ls_e1edp04 TYPE e1edp04, ls_land1 TYPE land1, ls_txjcd TYPE txjcd, ls_addrnum TYPE ad_addrnum. DATA: t_edid4 TYPE STANDARD TABLE OF edid4. DATA: wa_edid4 TYPE edid4. * SAP Note Note 800866 - SUS-MM: Invoice with delivery costs * This is to post the Shipping and handling charges as unplanned * delivery cost at the header of the Invoice IF i_idoc_data-segnam = 'E1EDS01'. ls_data_s01 = i_idoc_data-sdata. IF ls_data_s01-sumid = '020'. lv_beznk = ls_data_s01-summe. e_rbkpv-beznk = lv_beznk. * Derive the Default Tax Code and Tax Jurisdiction from the * configuration SELECT SINGLE mwskz_bnk txjcd_bnk FROM t169v INTO (e_rbkpv-mwskz_bnk, e_rbkpv-txjcd_bnk) WHERE bukrs = e_rbkpv-bukrs. ENDIF. e_change = 'X'. ENDIF. * Shipping and Handling added as service lines on invoice needs to be * posted to G/L Directly. To post to G/L account directly we need to * get this additional information regarding the accounting needs to * fetched in an extension segment. Reading data from extension * segement IF i_idoc_data-segnam = '/ARBA/ACCOUNT_DATA'. ls_/ARBA/ACCOUNT_DATA = i_idoc_data-sdata. IF NOT ls_/ARBA/ACCOUNT_DATA IS INITIAL. MOVE-CORRESPONDING ls_/ARBA/ACCOUNT_DATA TO ls_cobl_mrm. * Conversion exit for WBS 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. IF sy-subrc <> 0. * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. ENDIF. * Determine Tax Jurisidction code * We need Tax Jurisidction code only for US so check the country from * the Company Code SELECT SINGLE land1 adrnr INTO (ls_land1,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. All rights reserved.
289
WHERE bukrs = ls_/ARBA/ACCOUNT_DATA-bukrs. * If the country is US then get the Tax Jurisidction code * from Plant IF ls_land1 = 'US'. CLEAR ls_cobl_mrm-txjcd. SELECT SINGLE txjcd INTO ls_cobl_mrm-txjcd FROM t001w WHERE werks = ls_/ARBA/ACCOUNT_DATA-werks. * If Tax Jurisidction code is not maintained at Plant level, take it * from Company code level IF ls_cobl_mrm-txjcd IS INITIAL. SELECT SINGLE taxjurcode INTO ls_txjcd FROM adrc WHERE addrnumber = ls_addrnum. ls_cobl_mrm-txjcd = ls_txjcd. ENDIF. ENDIF. * If taxcode is not sent we will derive using the values maintained in * OBCD. IF ls_cobl_mrm-mwskz IS INITIAL. *SELECT sdata FROM edid4 INTO TABLE ls_sdata *WHERE docnum = i_idoc_data-docnum *AND segnam = 'E1EDP04' . FREE: t_edid4. SELECT * FROM edid4 INTO TABLE t_edid4 WHERE docnum = i_idoc_data-docnum AND segnam = 'E1EDP04'. SELECT SINGLE sndprn INTO ls_lifnr FROM edidc WHERE docnum = i_idoc_data-docnum. *READ TABLE t_edid4 INTO wa_edid4 INDEX 1. *LOOP AT ls_sdata INTO ls_e1edp04. LOOP AT t_edid4 INTO wa_edid4. ls_e1edp04 = wa_edid4-sdata. SELECT SINGLE mwskz INTO ls_cobl_mrm-mwskz FROM t076m WHERE parart = 'LI' AND konto = ls_lifnr AND mwart = ls_e1edp04-mwskz AND mwsatz = ls_e1edp04-msatz AND land1 = ls_land1. ENDLOOP. ENDIF. APPEND ls_cobl_mrm TO t_frseg-cobl_mrm. APPEND t_frseg. ENDIF. * We are introducing additional lines before the PO lines in t_frseg. * SAP code try to get the PO number from the first line of t_frseg to * get payment term and hence determine the baseline date, due this * idoc posting fails. To Avoid it retrieving the Payment term from * the PO line when present else get it from the Vendor data * Read the Reference data *SELECT sdata FROM edid4 INTO TABLE ls_sdata *WHERE docnum = i_idoc_data-docnum *AND segnam = 'E1EDP02' . FREE: t_edid4. SELECT * FROM edid4 INTO TABLE t_edid4 WHERE docnum = i_idoc_data-docnum AND segnam = 'E1EDP04'. LOOP AT t_edid4 INTO wa_edid4. ls_e1edp02 = wa_edid4-sdata. IF ls_e1edp02-qualf = '001'. * Get the Po and fetch the payment term SELECT SINGLE zterm INTO e_rbkpv-zterm FROM ekko WHERE ebeln = ls_e1edp02-belnr. ENDIF. ENDLOOP. * if PO line is not present get the payment term from Vendor Master
290
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
IF e_rbkpv-zterm IS INITIAL. SELECT SINGLE sndprn INTO ls_lifnr FROM edidc WHERE docnum = i_idoc_data-docnum. SELECT SINGLE zterm INTO e_rbkpv-zterm FROM lfm1 WHERE lifnr = ls_lifnr. ENDIF. e_change = 'X'. ENDIF. *Passing IDOC Number IF i_idoc_data-segnam = 'E1EDK01'. e_rbkpv-sgtxt = i_idoc_data-docnum. e_change = 'X'. ENDIF. The following example code shows the changes made to the Exit EXIT_SAPLMRMH_015: *&-----------------------------------------------------------------* *& Include ZXM08U26 * *&-----------------------------------------------------------------* * move the data which needs to be posted directly to G/L account to * t_co structure and delete the same from t_frseg LOOP AT t_frseg. LOOP AT t_frseg-cobl_mrm INTO t_co. APPEND t_co. e_change = 'X'. ENDLOOP. CLEAR t_frseg-cobl_mrm. ENDLOOP. IF NOT t_co[] IS INITIAL. DELETE t_frseg WHERE ebeln IS INITIAL AND ebelp IS INITIAL AND cobl_mrm IS NOT INITIAL. ENDIF. * Need to set the indicator auto tax calculation is not set. * Apply OSS Note 385756 e_rbkpv-xmwst = 'X'. e_change = 'X'.
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. Assign this Global Company code to company code using transaction code OBB5. Ensure that the global company code value and the company code are same.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
291
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, perform the following configuration activities:
Configure /ARBA/REQPARAM Table In SAP ERP, go to transaction SM30 and configure the /ARBA/REQPARAM table with the following: ● Order Type ● Purchase Requisition (optional when configuring for the first time) ● Date (optional when configuring for the first time) ● Time: (optional when configuring for the first time)
Enable Proxy Configuration For more information, see Proxy Settings in SAP ERP [page 294].
Run/schedule the /ARBA/REQUISITION_EXPORT program In SAP ERP, go to transaction SE38 and run or schedule the /ARBA/REQUISITION_EXPORT program.
Business AddIns The following Business AddIns (BADIs) are available inside the programs that allow you to enhance the functionality as required.
292
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
BADI Name
Description
/ARBA/PO_MODIFY
Available in /ARBA/PO_ACCOUNTING_INFO and /ARBA/
PO_SERVICE_INFO function modules. Use this BADI to enhance the purchase order transaction as required. This BADI has the following methods: ●
READ_PO_DATA
●
SAVE_PO_DATA
●
READ_SERVICE_PO_DATA
●
SAVE_SERVICE_PO_DATA The first two methods are available in the /ARBA/
PO_ACCOUNTING_INFO function module. The other two are available in the /ARBA/PO_SERVICE_INFO function module. /ARBA/CHANGE_PO
Available in the /ARBA/PO_GET_DETAIL function module. Use this BADI to enhance the change PO transaction as required. This BADI is available only in Ariba Cloud Integration 4.0 and earlier. Starting Ariba Cloud Integration 5.0, Change Purchase Orders are processed as part of the purchase order transaction.
/ARBA/INVOICE_UPDATE
Available in the /ARBA/ERPINVOICE_EXPORT program. Use this BADI to en hance the ERP-initiated invoice transaction as required.
/ARBA/ISU_UPDATE
Available in the /ARBA/INVSTATUPDT_EXPORT program. This BADI is available only in Ariba Cloud Integration 5.0 and earlier. For Ariba Cloud Integration 6.0, use the BADI /ARBA/BTE_INVSTATUPDT_EXPORT. Use this BADI to enhance the ISU transaction as required.
/ARBA/PP_UPDATE
Available in the /ARBA/PAYPROPOSAL_EXPORT program. use this BADI to enhance the payment proposal transaction as required.
/ARBA/RECEIPT_UPDATE
Available in the /ARBA/RECEIPT_PUBLISH program. Use this BADI to en hance the receipt transaction as required.
/ARBA/PR_CHANGE
Available in the /ARBA/REQUISITION_EXPORT program. Use this BADI to enhance the requisition transaction as required.
Implementing a BADI If you want to add a new field and send it to Ariba Network, perform the following steps: 1. Identify the structure in which you want to add a field. For example, you want to add a new field to the /ARBA/ EKPO structure. 2. Start transaction SE11, open the structure and click Append Structure to create a new structure and add the required fields. 3. Start transaction SE19, create an implementation for the definition /ARBA/PO_MODIFY. After creating the implementation, write the required code inside the available methods. 1. To fetch data for the fields you added, write the code inside the READ_PO_DATA method. To send this data to SAP NetWeaver PI, use the SAVE_PO_DATA method to populate the output structures. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
293
2. Save and activate the BADI. 3. To send this data to Ariba Network from SAP NetWeaver PI, enhance the custom mappings provided by Ariba.
Proxy Settings in SAP ERP Related Information
Configuring Proxy Settings for SAP NetWeaver 7.1 or Dual Stack (ABAP and Java) Instances of SAP NetWeaver PI 7.3 and above [page 294] Configuring Proxy Settings for Single Stack (Java only) Instances of SAP NetWeaver PI 7.3 and above [page 297]
Configuring Proxy Settings for SAP NetWeaver 7.1 or Dual Stack (ABAP and Java) Instances of SAP NetWeaver PI 7.3 and above Context If you are using SAP NetWeaver 7.1 or the dual stack (ABAP and Java) instance of SAP NetWeaver PI 7.3 and above, then perform the below steps to configure proxy. The below configuration is done in R/3 system. The RFC destination names vary from system to system. While configuring, specify the RFC destination names accordingly.
Procedure 1. Start Transaction SM59 and check if following configurations exist: ○ SAP_PROXY_ESR under HTTP Connections to External Server. ○ XI_INTEGRATIONSERVER_ (SID - system identifier) under HTTP Connections to ABAP System. ○ LCRSAPRFC under TCP/IP Connections. Specify the program ID similar to the one created under Jco RFC destinations (LCRSAPRFC_, where SID - system identifier) ○ SAPSLDAPI under TCP/IP Connections. Specify the program ID similar to the one created under Jco RFC destinations (SAPSLDAPI_, where SID - system identifier) 2. Start transaction SLDAPICUST. 3. Enter SAP XI hostname, port, XI user ID, and password. 4. Start transaction SXMB_ADM. 5. Expand Integration Engine -> Configuration. 6. Click Integration Engine Configuration to edit global configuration data.
294
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
7. Under Global Configuration Data, enter: ○ Role of Business System - Application System ○ Corresponding Integ. Server - dest:// (H Type RFC destination mentioned above) 8. Click Specific Configuration.
Enter the following: ○ Category - Runtime ○ Parameter - IS_URL ○ Current Value - dest:// (H Type RFC destination mentioned above) 9. Run SLDCHECK command in SAP R/3.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
295
Results The PI server appears and displays the following:
296
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Summary indicates that connection to XI is successful.
Configuring Proxy Settings for Single Stack (Java only) Instances of SAP NetWeaver PI 7.3 and above Context
If you are using the single stack (Java only) instance of SAP NetWeaver PI 7.3 or above, then perform the following steps to configure proxy:
Procedure
1. Start Transaction SM59 and create RFC destination SAP_PROXY_ESR (Type G) under HTTP Connections to External Server. a. Under the Technical Settings tab, add AEX (PI Java Stack) server host name and port. b. In the Path Prefix field, enter /rep. c. Under the Logon & Security tab, user must be assigned to role SAP_XI_REP_SERV_USER. 2. Create an HTTP destination to AEX of Type G (example: PI_AEX) as follows: a. Under the Technical Settings tab, add AEX (PI Java Stack) server host name and port. b. In the Path Prefix field, enter /XISOAPAdapter/MessageServlet?ximessage=true. c. Under the Logon & Security tab, user must be assigned to role SAP_XI_REP_SERV_USER. 3. Start transaction SXMB_ADM. 4. Expand Integration Engine -> Configuration. 5. Click Integration Engine Configuration to edit global configuration data. 6. Under Global Configuration Data, enter: ○ Role of Business System - Application System ○ Corresponding Integ. Server - dest:// (G Type RFC destination mentioned above in step 2) Refer graphic in the dual stack configuration above. 7. Click Specific Configuration and enter the following: ○ Category - Runtime ○ Parameter - IS_URL ○ Current Value - dest:// (G Type RFC destination mentioned above in step 2) Refer graphic in the dual stack configuration above. 8. Start transaction SLDAPICUST. 9. Enter SAP XI hostname, port, XI user ID, and password. 10. Run SLDCHECK command in SAP R/3. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
297
Documentation of RFCs Within the SAP NetWeaver Adapter During implementation, to meet your specific integration requirements, you can enhance the RFCs provided by Ariba by adding customer exits and making changes to enhancement points. The documentation of RFCs provides details about the implementation of the RFCs for ERP-initiated invoice, invoice status update, and payment proposal transactions. Based on this information, you can enhance your implementations by making changes as required. To access the documentation of RFCs, log on to connect.ariba.com and search for content item 144118.
Defining Authorizations for Running Ariba Network Transactions By default, all SAP ERP users are authorized to execute all Ariba Network transactions. However, if you want that only selected users must be authorized to execute these transactions, then you need to define authorizations accordingly. To define the required authorizations, an authorization object needs to be created in SAP ERP system and must be assigned to the RFC Communication Channel user. This user is assigned to the RFC communication channel in SAP NetWeaver PI. In your SAP ERP system, create an authorization object by using transaction SU21.
Note If you already have an authorization object class, then you can create the authorization object under that class. However, if you do not have an authorization object class specifically for Ariba, then first create an authorization object class /ARB before creating the authorization object. You must create the authorization object with the following details: ● Object name - /ARBA/RFC ● Description - Ariba Network Adapter Authorization Object. ● Authorization Class – new /ARB or existing class. Authorization Fields: 1. RFC_TYPE - Type of RFC object to be protected 2. RFC_NAME - Name of RFC to be protected Once the authorization object /ARBA/RFC is created, it must be assigned to a role in PFCG transaction code. If the role exists for the RFC Communication Channel user, then assign the authorization object to the role directly or create a new role and profile and then assign the authorization object. In PFCG, while assigning the authorization object to the role, select the check box FUGR for RFC_TYPE and for RFC_NAME, provide the names of the Ariba Network RFC function modules based on the user’s transaction level authorization. For example, /ARBA/INVOICE_GET_DETAILS and other invoicing function modules must be assigned to users who are authorized to run the invoice transaction.
298
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Configuring Advanced Pricing Details While creating a PO in the SAP ERP system, the user can specify advanced pricing details for a line item or multiple line items. Advanced pricing details includes: ● Quantity Based Pricing ● Unit Conversion Pricing Quantity based pricing allows the unit price of an item to be based on a different price unit quantity than 1. Unit Conversion Pricing allows unit of measure conversion in the pricing calculation, when the unit of measure on the order differs from the pricing unit of measure. When a PO with advanced pricing details is exported from your SAP ERP system, in the IDOC, the following fields are added: ● PriceBasisQuantity ● PriceBasisQuantityUOM ● ConversionFactor ● PriceBasisQuantityDesc During transformation in SAP NetWeaver PI, these fields are added to the cXML and sent to Ariba Network. Advanced pricing details are also applicable for change purchase order and payments.
ABAP Programs for Outbound Transactions Implemented Using Proxies The following ABAP programs have been created by using the existing RFC code for the outbound transactions.payment proposal, receipt, and ERP-initiated invoice: Transaction Name
ABAP Program Name
ERP-Initiated Invoice
/ARBA/ERPINVOICE_EXPORT
Note This is available only for Ariba Cloud Integration Release 5.0 and earlier. Payment Proposal
/ARBA/PAYMENTPROPOSAL_EXPORT
Receipt
/ARBA/RECEIPT_PUBLISH
Note To filter data, RFCs read the values that you maintain for the parameters in the /ARBA/PARAM_TAB. Therefore, ensure that you have maintained values for all the required parameters.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
299
These above mentioned ABAP programs have been modified as follows: The existing RFC's take Start Date and Time as input parameters, 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, ERP-initiated invoice and PP and fiscal year and document number for the receipt transaction. You need to manually maintain the values in this table before the proxy programs are executed either manually or by the SAP Scheduler. The proxy programs fetch data incrementally from the last date and time or document number (in case of receipts) maintained in the table and send that data to SAP NetWeaver PI in a batch. The PI mappings then split the data into multiple cXML messages and send these cXML messages to Ariba Network through the cXML Adapter. No change is made to the data processing logic. The data, which was earlier getting populated to RFC tables, is populated to the proxy structures. The receipt program now additionally: ● Pulls receipt document numbers from MKPF ● Filters documents to exclude the following: ○ Documents which are not of movement type 101 ○ Documents for vendors not stored in the table /ARBA/AN_VENDOR ● Fetches receipt data by using BAPI_GOODSMVT_GETDETAIL
Configuring Implicit Enhancements for Comments in Order Confirmations Prerequisites The latest transport code must be installed in SAP ERP before creating this enhancement. This implicit enhancement allows you to process comments in order confirmations.
Procedure 1. Log in to SAP ERP and navigate to transaction SE80. 2. Click Repository Information System in the left panel. 3. Select Program Library in the Object section of the left panel. 4. Double-click Includes. 5. Enter ZXM06U02 in the Include name field. 6. Press F8 or click Execute. 7. Double-click the highlighted Include name in the Results list on the right panel. 8. Click Display <-> Change to put the Include into change mode.. If prompted for the developer access key, enter the access key information. 9. Copy the following code and paste it into the top of the Include just below the comments. CALL METHOD /arba/cl_po_confirmation=>update_po_text
300
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
EXPORTING i_control is_ekko it_edidd CHANGING ct_status
= i_control = order = i_data[] = i_status[].
10. Click Save, and then click Activate to activate the changes.
Configuring Invoice Status Updates Buyers can send Invoice Status Updates to Ariba Network to let suppliers know about the status of the invoice on the buyer's system. Buyers send StatusUpdateRequest documents to send status for invoices that are processing, reconciled, paying, paid, rejected, invalid, parked, or parked invoices that have been deleted. Invoice Status Updates [page 301] Configuring the Invoice Status Update Transaction on your SAP ERP system [page 303]
Invoice Status Updates Buyers using the Ariba Network Adapter for SAP NetWeaver can send and receive the statuses of invoices created on an SAP ERP system or Ariba Network when the status for invoices are updated on the SAP system. The Invoice Status Update transaction processes invoices that are processed, paid, reconciled, rejected, canceled, parked, or parked invoices that have been deleted on the SAP system. The Business Transaction Events (BTE) has been created to process invoices created, changed, reversed, canceled, parked, parked invoices that have been deleted, or when payments are received on an SAP ERP system. Buyers can send the following statuses for the parked invoices or the parked invoices that have been deleted to Ariba Network. Type
Status Sent
Comments Sent
Parked invoices
Processing
Document Parked
Parked invoices that have been deleted
Rejected
Document manually rejected/deleted
Note When remittances have been reversed, the Invoice Status Update transaction does not change the status of the reversed invoices to "Reconciled" on the SAP system. This is applicable only for customers using Cloud Integration Release version 3.0 and earlier.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
301
Requirements
The Invoice Status Update transaction requires the same parameters that are applicable for the ISU batch program on your SAP system:
Note The Invoice Status Update program (/ARBA/BTE_INVSTATUPDT_EXPORT) cannot be used along with the earlier version of the Invoice Status Update batch program (BTE_INVOICESTATUSUPDATE. Buyers can only use one of the programs for invoice transactions.
Limitations
Ariba Network Adapter for SAP NetWeaver does not support processing of the MM and FI invoices that have been created on an SAP ERP system and have been parked. The Invoice Status Update transaction contains the following: ● A Business Transaction Events (BTE) has been associated to the 00005010 process module to send the statuses of invoices each time there is an update to invoices on the SAP ERP system. The BTE function module is activated when the invoices are created, paid (partial or full payment), reconciled, rejected, canceled, parked, parked invoices that have been deleted. When the function module is run, the Invoice Status Update transaction picks up invoices only for the document types maintained in /ARBA/PARAM_TAB. The following document types must be maintained in ARBA/PARAM_TAB: ● INVOICE_DOC_TYPE ● INVOICE_DOC_TYPE_FULL_AUTO ● INVOICE_DOC_TYPE_FULL_MANUAL ● INVOICE_DOC_TYPE_PARTIAL ● The Invoice Status Update transaction requires the same parameters that you set for the ISU batch program on your SAP system: ● The table /ARBA/AN_ISUINV stores information on the invoices are ready to be sent to Ariba Network. ● The function module /ARBA/BTE_INVOICESTATUSUPDATE processes invoices created or received on the SAP system. ● The BTE does not require the /ARBA/RFC authorization object. However, this authentication object is required when the /ARBA/BTE_INVSTATUPDT_EXPORT program runs the report containing the records to be sent to Ariba Network. The authorization object contains the following details: ○ Object Name: /ARBA/RFC ○ Description: Ariba Network Adapter Authorization Object ○ Authorization Class: /ARB or existing class. Authorization Fields ● RFC_TYPE: Type of RFC object to be protected ● RFC_NAME: Name of RFC to be protected
302
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
● If you maintain the AVOID_DUPLICATE_ISU_PP parameter and the BTE is triggered, the Ariba Network Adapter for SAP NetWeaver picks up the invoices only when the ZLSPR – Payment Block Key field values have been changed:
Note The ISU transaction does not use the GRACE_TIME_ISU_PP parameter. ● If the INVOICE_DOC_OPTION parameter is maintained in /ARBA/PARAM_TAB, then Ariba Network Adapter for SAP NetWeaver sends the Reference Document number (XBLNR) as the invoiceID to Ariba Network. If you do not maintain this parameter, then the Ariba Network Adapter for SAP NetWeaver sends the invoice document number as the invoiceID to Ariba Network. ● If you maintain the ERP_INV_PROCESSED_STATUS parameter, the Ariba Network Adapter for SAP NetWeaver stores the invoices that are sent to Ariba Network in the /ARBA/AN_ERPINV table. ● The Business AddIn (BADI) /ARBA/BTE_ISU_UPDATE is available in the BTE. The following are the available methods: BADI Method
Description
CHANGE_PROCESS_BSIK
Allows you to customize the existing structure details.
CHANGE_PROCESS_BSAK
Allows you to customize the existing structure details.
CHANGE_PARTIALPAID
Allows you to modify the details for partially paid invoices.
CHANGE_ISU_STATUS
Allows you to modify the status updates for invoices.
CHANGE_INSERTTABLE
Allows you to modify the inserted details in the invoice status update table.
CHECK_CHANGED
Allows you to modify the flag for check changes.
CHANGE_REJECTED
Allows you to modify the rejected invoices.
CHANGE_PARKED
Allows you to modify the parked invoices.
Note For a PO-based invoice, the “Cancelled status is set based on the MM invoices. SAP notifies users when an invoice is cancelled through the MR8M message, “Please manually clear F1 document.” Users must ensure that they clear the F1 documents using F-44. If the F1 documents remain, Ariba Network Adapter for SAP NetWeaver sends all corresponding documents (payment proposal, remittances) associated to the cancelled MM invoice to Ariba Network.
Configuring the Invoice Status Update Transaction on your SAP ERP system Context
Ensure that you import the necessary SAP transport requests into your SAP ERP system. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
303
Procedure 1. Go to the Transaction code FIBF. 2. On the Environment menu, click Infosystem(Processes). 3. Click Execute. The Process Module 00005010, appears on the Business Transaction Events: Process Interface page. 4. Go to the Transaction code FIBF. 5. On the Settings menu, click Products and then click ...of a customer. 6. Enter a new product name and description. The function module product name must start with /ARBA/. 7. Click the Active check box to select it. 8. Go back to the previous page and click the Settings menu, click Process Modules and then click ...of a customer. 9. For the process module 00005010, specify the newly created function module. The function module must start with /ARBA/. For example, /ARBA/BTE_INVSTATUPDT_EXPORT. Specify the product ‘/ARBA/IS’. 10. Save the changes.
Configuring Order Inquiries This section contains the following topics: ● Configuring SAP IDOC for Order Inquiries [page 304] ● Configuring the Partner Profile [page 305] ● Maintaining Condition Records for Inquiries [page 307] ● Implementing a Custom Exit for the Order Inquiries Function Module [page 308] ● Support for Additional cXML Fields [page 308]
Configuring SAP IDOC for Order Inquiries Context The following SAP IDOC configuration is required for using the sample data mapping: Transaction
OrderStatusRequest
IDOC Basic Type
ORDERS05
Message Type
ORDERS
Configuring the IDOC transaction to support inquiries for purchase orders on your SAP ERP system involves the following steps: ● Installing the transports for the purchase order and change purchase order transaction. For more information, see Importing the Design Package [page 313].
304
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
● Configuring the IDOC. For more information, see Configuring SAP IDOC for Order Inquiries [page 304]. ● Configuring the partner profile. For more information, see Configuring the Partner Profile [page 271].
Procedure
1. Use Transaction SM59 to create an RFC destination of type ERP. 2. Enter the Target host, System Number, Getaway host, Getaway service on the Technical Settings tab. Enter the Language, Client, User, Password on the Logon/Security tab, and then save your entries. 3. Use Transaction WE21 to create a port. 4. Choose Transactional RFC and click Create. 5. Enter port, description and RFC destination details, and then save your entries. For more information on the IDOC, see Configuring SAP IDOC for Order Inquiries [page 304].
Configuring the Partner Profile Procedure
1. Use transaction WE20 to create a partner profile for a vendor. 2. Expand the Partner type LI (Vendor) and choose the vendor that you want to configure the partner profile. 3. In the Outbound parameters table, click the Add button and enter the following entries: ○ Partner Function: VN ○ Receiver Port: Configure the SAP PI system that sends the inquiries. ○ Partner Number: Corresponding Partner Number ○ Partner Type: LI ○ Partner Role: VN ○ Message Type: ORDERS ○ Receiver Port: Enter the SAP PI Receiver Port ○ Basic Type: ORDERS05 ○ Extension: /ARBA/ORDENQ ○ Message Type: ORDERS ○ Message Variant: OER ○ Message Function: OER 4. Click the Message Control tab. 5. Click the Add button in the table control. 6. Enter the following values:
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
305
Application
Message Type
Process Code
Change Indicator
EF
MAHN
ME10
Blank
EF
MAHN
ME10
x
EF
AUFB
ME10
Blank
EF
AUFB
ME10
x
7. Select Trigger immediately as the value for the Processing by Function Module parameter, if you want real time processing. 8. Save your entries. 9. Use the transaction WE57 to assign the function module to the logical message and IDOC Type. To do this, click New Entries and enter the following values: Parameter
Value
Function Module Name
IDOC_OUTPUT_ORDERS
Function Type
FUNCTION MODULE
Basic Type
ORDERS05
Enhancement
/ARBA/ORDENQ
Message Type
ORDERS
Message Code
OER
Object Type
BUS2012
Direction
1
10. Use the transaction WE82 to assign the function module to the logical message and IDOC Type. To do this, click New Entries and enter the following values:
306
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Results
Parameter Message Type
Basic Type
Extension
Value
ORDERS
ORDERS05
/ARBA/ORDENQ
Maintaining Condition Records for Inquiries Procedure
1. In the main screen when you start the transaction NACE, select application records.
and click Condition
2. Click EF as the application type and then click relevant output type. A new screen appears. 3. Double click the output type: MAHN (Dunning) B. A new screen appears. 4. Click the Default Values tab and preserve the following values in the tab: ○ Despatch time: Send immediately ○ Transaction Medium: EDI ○ Partner function: VN 5. Click the General Data tab and select the Multiple issuing check box. You must perform this action. 6. Save the entries and go back to the main screen. 7. Click EF as the application type and then click Condition records. 8. Double click the MAHN output type and click Purchasing Output Determination: Purch.Org/Vendor for EDI. 9. Press Enter. Preserve the values for the purchase organization and vendor. 10. Click the Execute button and maintain the following parameters for the vendor: ○ Document Type - NB (for example) ○ Partner Function - VN ○ Partner Number - 1000 (for example) ○ Medium - 8 (Special Function) ○ Date/Time - 4 (when the application is saved) 11. Save the entry. 12. If you select the AUFB output type, perform Step# 6 to 9.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
307
Implementing a Custom Exit for the Order Inquiries Function Module Context The Function module /ARBA/ORDENQ_DETAILS is called from a custom exit MM06E001 - this is the user exit for EDI inbound and outbound purchasing documents. You must execute the following steps to implement a custom exit. This function module helps in picking up additional inquiry details.
Procedure 1. Go to the CMOD transaction code. Create a new custom exit. For example, ZOR. 2. Click Create. 3. Click the Enhancement Assignments button and then enter the user exit name “MM06E001”. 4. Click Enter. 5. Go back and click the Components button and then double-click the enhancement name EXIT_SAPLEINM_002. 6. In the new screen that appears, double-click INCLUDE ZXM06U02 and click Enter. 7. Copy and paste the following code: CALL FUNCTION '/ARBA/ORDENQ_DETAILS' 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. 9. Go back and activate the user exit also.
Support for Additional cXML Fields The standard IDOC /ARIBA/ORDENQ allows you to send additional information on inquiries to Ariba Network.
308
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
The following segments stores information on the following: ● /ARBA/ORDENQHEADER: Stores additional header-level details sent in the OrderStatusRequestHeader. ● ZARIBA_ORDENQ_HEADER_EXT: Stores customized fields at the header-level sent in the OrderStatusRequestHeader. ● /ARBA/ORDENQDETAIL: Stores additional information on line items sent in the OrderStatusRequestItem. The reminder level information is stored here. ● /ARBA/ORDENQ_COMMENTS: Stores the comments sent in the OrderStatusRequestItem. ● ZARIBA_ORDENQ_DETAIL_EXT: Stores customized fields at the line item-level sent in the OrderStatusRequestItem. ● Mapping changes have been done in the IDOC to support the additional inquiry fields in the OrderStaturRequest cXML document: MM_ORDERS_ORDENQ_ARBA_2_CDF_FulFill_XSD To customize fields, use the MM_Custom_ORDERS_ORDENQ_ARBA_2_CDF_FulFill_XSD mapping file.
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, see Scheduling Agreement Release Integration Scenario [page 153]. 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. For more information, see Importing the Design Package [page 313]. ● Configuring the IDOC. For more information, see Configuring SAP IDOC for Scheduling Agreement Releases [page 310]. ● Configuring the partner profile. For more information, see Configuring the Partner Profile for Scheduling Agreement Releases [page 310]. You can also configure the partner profile at the logical system level. For more information see, Configuring the Partner Profile for Scheduling Agreement Releases [page 277].
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
309
Configuring SAP IDOC for Scheduling Agreement Releases The following SAP IDOC configuration is required for using the sample data mapping: Transaction
IDOC Basic Type
ScheduleAgreementReleaseRequest
DELFOR02
Message Type
DELINS
Configuring the Partner Profile for Scheduling Agreement Releases Procedure
1. Use transaction WE20 to create a partner profile for a vendor. 2. Expand the Partner type LI (Vendor) and choose the vendor that you want to configure the partner profile. 3. In the Outbound parameters table, click the Add button and enter the following entries: ○ Receiver Port: Configure the SAP PI system that sends the scheduling agreement release. ○ Partner Number: Corresponding Partner Number ○ Partner Type: LI ○ Partner Role: VN ○ Message Type: DELINS ○ Receiver Port: Enter the SAP PI Receiver Port ○ Basic Type: DELFOR02 ○ Extension: /ARBA/DELFOR02 4. On the message control tab, 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. Select Trigger immediately as the value for the Processing by Function Module parameter, if you want real time processing. 6. Save your entries.
310
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Related Information Configuring the Partner Profile for Scheduling Agreement Releases [page 277]
Maintaining Condition Records for Scheduling Agreement Releases Procedure 1. In the main screen when you start the transaction NACE, select application EL Purch. SchAgrReleaseEntry and click Condition records. 2. Click EL as the application type and then click relevant output type. 3. Double click the output type: LPH1 and LPJ1(Forecast and JIT) 4. Click the Default Values tab and preserve the following values in the tab: ○ Despatch time: Send with Application own transaction ○ Transaction Medium: EDI ○ Partner function: VN 5. Click on Condition records. 6. Double click the LPH1 output type and click Purchasing Output Determination: Purch.Org/Vendor for EDI. 7. Press Enter. Preserve the values for the purchase organization and vendor. 8. Click the Execute button and maintain the following parameters for the vendor: ○ Document Type - NB (for example) ○ Partner Function - VN ○ Partner Number - 1000 (for example) ○ Medium - 8 (Special Function) ○ Date/Time - 4 (when the application is saved) 9. Save the entry. 10. Perform Step 6 to 9 with output type LPJ1 for the JIT Delivery Schedule.
Implementing a Custom Exit for Scheduling Agreement Releases Context The Function module /ARBA/SARRELEASE is called from a custom exit MM06E001 - this is the user exits for EDI inbound and outbound purchasing documents. You must execute the following steps to implement a custom exit. This function module helps in picking up additional scheduling agreement release details. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
311
Procedure 1. Go to the CMOD transaction code. Create a new custom exit. For example, ZSAR. 2. Click Create. 3. Click the Enhancement Assignments button and then enter the user exit name- MM06E001. Click Enter. 4. 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. In the new screen that appears, double-click INCLUDE ZXM06U59 and click Enter. 6. 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. 7. Click the Activate button. 8. Go back and activate the user exit also.
Support for Additional cXML Fields The existing IDOC DELINS.DELFOR02 has been enhanced to send additional cXML fields for the Forecast Delivery Schedule or JIT Delivery Schedule information to Ariba Network. You can use the following IDOC segments to support these additional cXML fields: ● To send additional header fields (vendor address and company code address details) to Ariba Network: ○ /ARBA/SARHEADER IDoc: Additional Header data ● To send additional line item details: ○ /ARBA/SARDETAIL IDoc: Additional item data ○ /ARBA/ACCOUNT IDoc: Accounting details (price unit, account category, and material group) You can use the following customized IDOC segment to send any additional cXML fields: ● To send additional header fields to Ariba Network, customize the following segment: ○ ‘ZARIBA_SARHEADER_EXT IDoc: Schedule Agreement Release Header
312
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
● To send item details, 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. This is optional; if you skip it, the metadata information is downloaded and associated to the port the first time a given type of IDOC is exchanged. Check and configure the IDOC Metadata parameters of the port to communicate with the SAP ERP system in SAP NetWeaver PI. Refer to the transaction IDX2. Check the IDOC Metadata in Metadata Overview for the IDOC Adapter to see if all the inbound IDOC DELFOR02, is available. If they are not, click
Metadata
Create
to add
the same.
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. For more information, seeImporting the Design Package [page 313]. ● Configuring the IDOC. For more information, see Configuring SAP IDOC for Scheduling Agreement Releases [page 310]. ● Configuring the partner profile. For more information, see Configuring the Partner Profile or Ship Notices Against Multiple Purchase Orders [page 314].
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 Ship Notice
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
IDoc Basic Type
DELVRY06
Message Type
DESADV
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
313
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 Configuring the SAP IDOC for Ship Notices Against Multiple Purchase Orders [page 313]details, and then save your entries.
Configuring the Partner Profile or Ship Notices Against Multiple Purchase Orders Procedure 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 Type, Agent, and Lang. Save your entries. 4. Click Create inbound parameter (the green plus sign). 5. Enter Partner Role, Message type, and Process code. 6. Save your entries. 7. Configure Advance Ship Notice with the following inbound parameters: Parameter
Value
Partner function
VN
Message type
DESADV
Process Code
DELS
8. Select Trigger immediately as the value for the Processing by Function Module parameter, if you want real time processing and then click the Cancel Processing After Syntax Error check box. 9. Use the transaction BD67 to assign the process code DELS to the function module IDOC_INPUT_DESADV1. 10. Use the transaction WE57 to assign the function module to the logical message and IDOC Type. To do this, click New Entries and enter the following values:
314
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Results
Parameter Function module
Function type
Basic Type
Message Type
Object Type
Direction
Description
Name
Value
IDOC_INPUT_DESADV1
Function Module
DELVRY06
DESADV
BUS2015
Inbound
Delivery:Shipping notification
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. It is optional as, if you skip it, the metadata information will be downloaded and associated to the port, the first time a given type of IDoc is exchanged. Check and configure the IDoc Metadata parameters of the port to communicate with the SAP ERP system in SAP NetWeaver PI. Refer to the transaction IDX2. Check the IDoc Metadata in Metadata Overview for the IDoc Adapter to see if all the inbound IDOC DESADV06, is available. If they are not, click same.
Metadata
Create
to add the
Configuring Returns and Corrections in Receipts Configuring the receipt transaction to support returns and correction on your SAP ERP system involves the following steps: ● Installing the transports for the receipt transaction. For more information, seeImporting 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. All rights reserved.
315
● Configuring parameters in the ARBA/PARAM_TAB table. For more information, see Configuring Parameters in the ARBA/PARAM_TAB Table for Returns and Corrections in Receipts [page 316]. ● Maintaining condition records for returns and corrections in receipts. For more information, see Maintaining Condition Records for Returns and Corrections in Receipts [page 317]. ● Maintaining default values for the printer. For more information, see Maintaining Printer Default Values for Returns and Corrections in Receipts [page 318]. For more information on sending and receiving corrections and returns in receipts, see Receipt Integration Scenario for Corrections and Returns in Receipts [page 179].
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
GOODSRECEIP T
RECEIPT_MVT
1
INCL/ EXCL
I
Option
Selection Value
EQ
Can be left blank or you can specify the fol lowing movement types: 101, 103, 104. To specify another movement type, create the same variable and field name in an other row and increment the Number value to 2. For example, you currently have the Selection Value as 101. To create the 103 movement type, create another row con taining the same values, but increment the Number value to 2.
GOODSRECEIP T
RECEIPT_MVT_REVERS 1 AL
GOODSRECEIP T
RETURN_MVT
1
I
I
EQ
Can be left blank or you can specify the 102 movement type.
EQ
Can be left blank or you can specify the fol lowing movement types: 122, 124, 161. To specify another movement type, create the same variable and field name in an other row and increment the Number value to 2. For example, you currently have the Selection Value as 122. To create the 124 movement type, create another row con taining the same values, but increment the Number value to 2.
GOODSRECEIP T
316
RETURN_MVT_REVERSA 1 L
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
I
EQ
Can be left blank or you can specify the 123 movement type.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Note ● You can leave the Selection Value field blank or specify a particular movement type. If you leave the value blank, the ERP system associates the 101, 102, 122, and 123 movement types as the default values for fields maintained for the GoodReceipt variable. ● If you enter a specific movement type in the Selection Value field, only this particular movement type is considered while processing receipts containing returns and corrections.
Maintaining Condition Records for Returns and Corrections in Receipts Procedure
1. In the main screen when you start the transaction NACE, select application ME Inventory Management and click Condition records. 2. Click ME as the application type and then select WE03 as the output type. A new screen appears. 3. Double click the output type: WE03. A new screen appears. 4. Click the Default Values tab and preserve the following values in the tab: ○ Trans./Event Type: WE ○ In the Print Version, choose one of the following values: ○ 1 Individual Slip ○
2
Indiv. Slip w Inspect Text
○
3
Collective Slip
○ Partner function: Enter the partner number of the sender system.
Note The Print Version option you select in the Default Values tab must match the value you select in the MIGO screen. For example, if you have selected 1 Individual Slip as the Print Version option in the Default
Values
tab, you must select the same 1 Individual Slip in the MIGO screen.
5. Save the entries and go back to the main screen. 6. Click ME Inventory Management as the application type and then click Condition records. 7. Double click the WE03 output type and click More Details. 8. 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. 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. All rights reserved.
317
○ Program: /ARBA/RECEIPT_PUBLISH
Note This program uses NACE configuration to publish the receipts in real-time. ○ FORM routine: SEND_GOODSRECIPT_SAVED 10. Press Enter. 11. Click the Execute button and maintain the following parameters for the partner function: ○ Function - LS ○ Medium - 8 (Special Function) ○ Description - Logical system 12. Save the entry.
Maintaining Printer Default Values for Returns and Corrections in Receipts Procedure
1. Go to the Transaction code MIGO and MB01. 2. In the General tab, click the pull-down arrow and select 3 Collective Slip for the printer. 3. Go to the Transaction code SU3. 4. Click the Parameters tab and add the following entry for the user: ○ Parameter ID - NDR ○ Parameter Value - X 5. Save the entry.
Configuring Quote Request and Quote Message Documents Configuring the IDOC transaction for the quote request and quote message on your SAP ERP system involves the following steps: ● Configuring your system for Quote Request documents. For more information, seeConfiguring your System for Quote Request Documents [page 319]. ● Configuring your system for Quote Message documents. For more information, see Configuring your System for Quote Message Documents [page 320]. ● Configuring the SAP NetWeaver PI. For more information, see Configuring SAP NetWeaver PI [page 321].
318
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Configuring your System for Quote Request Documents The following configurations must be made to your system for Quote Request documents: ● Configure the IDoc Partner Profile. For more information, see . [page 319] ● Activate the Cutom Project. For more information, see . [page 319]
IDoc Partner Profile Configuration IDoc ORDERS05 has been extended as “/ARBA/RFQ” and includes attachment details and additional data required for mapping. For example, supplier email, and the change RFQ indicator. New NetWeaver PI mapping contents transform the iDoc to a ‘Quote Request’ cXML message and the cXML message is sent to the Ariba Network. The following SAP IDoc configurations are required: ● IDoc Basic Type: ORDERS05 ● IDoc Extension Type: /ARBA/RFQ ● Message Type: REQOTE
Activating the IDoc Extension To activate IDoc extension, you must create a custom project with Enhancement Assignment “MM06E001” and component “EXIT_SAPLEINM_002” and then activate the project.
Activating the Custom Project Procedure 1. Go to the CMOD transaction code and create a new custom exit. For example, ZRFQ. 2. Click Create. 3. Click the Enhancement Assignments button, enter the user exit name “MM06E001” and then click Enter. 4. Go back and click the Components button and then double-click the following enhancement name “EXIT_SAPLEINM_002.” 5. In the new screen that appears, double-click “INCLUDE ZXM06U02” and click Enter. 6. Copy and paste the following code:
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.
319
object = dobject TABLES int_edidd = int_edidd 7. Click the Activate button. 8. Go back and activate the user exit also.
Configuring your System for Quote Message Documents To create Quote Message documents, Ariba needs the following information: ● Company Code ● Purchase Organization ● Material Group Ariba fetches this information from the RFQ. Ariba pulls account information from the requisition if the RFQ was created with reference to a requisition. If not, Ariba fetches the accounting information from the /ARBA/ PARAM_TAB table.
Note The accounting logic does not apply if the RFQ has a material number.
RFC / ARIBA/QUOTE The RFC / ARIBA/QUOTE has been created, which uses BAPI_PO_CREATE1 to create a purchase order for the awarded quote messages. The RFC does the following: ● Defaults missing information in the cXML. For example, purchase organization, company code, purchase group, accounting information from the RFQ. ● To maintain this parameter - TCode - 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 DOR
0
I
EQ
0000003960
QUOTE
ORDER
0
I
EQ
23122
QUOTE
ORDER_TYPE
0
I
EQ
NB
320
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
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.
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.
XI_Global
XI
DefaultLanguageCode
Default language.
LANG_ERP
LANG_ISO
ERP Language code
Key value pair of ERP-ISO lan guage map.
RFQ_ERP
RFQ_XI
RFQDummyVendor
Indicates whether a vendor is an “Ariba Marketplace Ven dor”.
RFQ_TYPE
RFQ_ASN_TYPE
ERP’s RFQ document type
Key value parameter of ERP doc type with Ariba Network supported doc type - invitatio nOnly, approvedVendorOnly, public
For more information about Quote Request and Quote Message documents, see Integrating SAP ERP with the Ariba Spot Quote Solution [page 245].
Configuring Support for Line Level Hierarchies in Service Purchase Orders Ariba Network Adapter for SAP NetWeaver enables transmission of service purchase orders with service lineitems in up to five levels of hierarchy (1 parent and 4 child levels) from SAP ERP to Ariba Network. For more information on service purchase orders, see Purchase Order [page 16].
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
321
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. ● Create an implicit enhancement for service order functionality in the SAP ERP system. For more information, see Configuring Implicit Enhancements for New Service Orders [page 323].
Backward Compatibility The hierarchical display of service line items necessitates changes in SAP ERP and the Ariba Network Adapter for SAP NetWeaver that affect how transmission of purchase orders, change orders, and update orders are handled. These changes are not backward compatible with previous releases.
Note You must remove previously existing change order configuration from your Ariba solutions. If you also have change order transaction customizations and want to continue to use them, they must be migrated to purchase order transactions instead.
Limitations The following limitations apply to the transmission of purchase orders with up to a 5-level deep hierarchy of service lines in Purchase Orders. ● This feature requires SAP ERP 6.0, EHP 4 and greater. Attempting to create a PO with a 5-level deep hierarchy when using EHP3 or lower generates an error message in PO Message tab. ● SAP ERP restrict a hierarchy to a maximum of 5 levels: each top-level service line-item can have up to four additional levels of nesting below the top-level item. Ariba Network can display the full hierarchy for service lines. ● Hierarchies are not supported for Order Confirmations, Service Sheets, and Service Invoices. ● The last service item in a hierarchy cannot be blank. ● SAP ERP note 2020660 might require implementation if it is not already installed and errors are generated when changing or updating a PO. For more information see the SAP documentation.
About Configuring Implicit Enhancements To enable SAP ERP to send correct new, change, and cancel service order with hierarchical information to the Ariba Network Adapter for SAP NetWeaver, you must configure two implicit enhancement in SAP ERP. Configuring Implicit Enhancements for Change and Cancel Service Orders [page 323] Configuring Implicit Enhancements for New Service Orders [page 323]
322
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Configuring Implicit Enhancements for Change and Cancel Service Orders Context
To enable SAP ERP to send the correct change and cancel order information to the Ariba Network Adapter for SAP NetWeaver, you must configure an implicit enhancement in SAP ERP.
Procedure
1. In your SAP ERP system, navigate to transaction code SE38 - LEINMF0Q and click Display. 2. Select SAPLEINM from the popup. 3. Click Enhance in the application toolbar. 4. Click Edit > Enhancement Operations > Show Implicit Enhancement Options to display a line after the lesen-beleg form. 5. Right-click the line and select Enhancement Implementation > Create. 6. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation. 7. Click Create Enhancement Implementation. 8. Enter a name and description for the enhancement and press Enter. 9. In the package popup, specify your Z or Y package, press Enter, and save the package to a transport request. 10. Copy the following code: DATA: cl_PO_ChangeCancel TYPE REF TO /arba/cl_PO_ChangeCancel. CREATE OBJECT cl_PO_ChangeCancel. CALL METHOD cl_PO_ChangeCancel->trigger_delete_po_idoc EXPORTING ebeln = h_ebeln CHANGING xdruvo = xdruvo. 11. Paste the copied code into the Enhancement Implementation. 12. Activate the enhancement and save it.
Configuring Implicit Enhancements for New Service Orders Context
To enable SAP ERP to send new service order information to the Ariba Network Adapter for SAP NetWeaver, you must configure an implicit enhancement in SAP ERP. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
323
Procedure 1. In your SAP ERP system, navigate to transaction code SE37 - IDOC_OUTPUT_ORDERS and click Display. 2. Search for Perform fill_srv_orders. 3. Double-click Perform. 4. Select SAPLEINM from the popup. 5. Click Enhance in the application toolbar. 6. Click Edit > Enhancement Operations > Show Implicit Enhancement Options to display a line after the fill_srv_orders form. 7. Right-click the line and select Enhancement Implementation > Create. 8. Click Code on the Enhancement popup to display Select or Create Enhancement ImplementationChoose Type of Enhancement. 9. Click Create Enhancement Implementation. 10. Choose Type ofEnter a name and description for the enhancement and press Enter. 11. In the package popup, specify your Z or Y package, press Enter, and save the package to a transport request. 12. Copy the following code: DATA: l_flag(5) cl_purchaseorder cl_po_hierarchy ls_idoc_status lx_appl_idoc
TYPE TYPE TYPE TYPE TYPE
c, REF TO /arba/cl_purchaseorder, REF TO /arba/cl_po_hierarchy, bdidocstat, REF TO /arba/cx_appl_idoc.
CONSTANTS: c_true TYPE char4 VALUE 'true', c_false(5) TYPE c VALUE 'false'. CREATE OBJECT cl_purchaseorder. CREATE OBJECT cl_po_hierarchy. TRY.
CREATE OBJECT cl_po_hierarchy. CALL METHOD cl_po_hierarchy->get_systemversion_ishierarchy EXPORTING ebeln = ekpo-ebeln et_edi_esll = edi_esll[] IMPORTING flag = l_flag CHANGING int_edidd = int_edidd[].
CATCH /arba/cx_appl_idoc INTO lx_appl_idoc. MESSAGE e151(/arba/message) RAISING error_message_received. RETURN. ENDTRY. IF l_flag EQ c_true. CALL METHOD cl_purchaseorder->fill_service_line_number EXPORTING packno = ekpo-packno IMPORTING et_edi_esll = edi_esll[]. ENDIF.
324
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
13. Paste the copied code into the Enhancement Implementation. 14. Activate the enhancement and save it. 15. Right-click on the line just before the end of the fill_srv_orders form and select Enhancement Implementation > Create. 16. Click Code on the Choose Type of Enhancement popup to display Select or Create Enhancement Implementation. 17. Select the enhancement created and named in Step 10. 18. Copy the following code: IF l_flag EQ c_true. CALL METHOD cl_purchaseorder->create_parent_child_relation EXPORTING edi_esll = edi_esll[] CHANGING int_edidd = int_edidd[]. ENDIF 19. Activate the enhancement and save it.
Direct Invoicing of Purchase Order Service Items Buyers can directly invoice a purchase order having the service type items. The Ariba Network Adapter for SAP NetWeaver supports integration of the service sheets auto-generated on Ariba Network for the invoice containing service type line items created by the supplier and sent to the SAP ERP system. Ariba Network Adapter for SAP NetWeaver processes invoices with service type line items created against purchase orders sent from Ariba Network as follows: ● Supplier create an invoice with service type line items against purchase orders. ● Ariba Network auto generates a service sheet for the invoice with service type line items. The service sheet is then sent to the SAP ERP system. ● The invoice is kept on hold as "Pending Approval" on Ariba Network until the auto-generated service sheet for the invoice containing service type line items is approved on the SAP ERP system. ● Once the service sheet is approved on the SAP ERP system, the approved status is sent to Ariba Network. The invoice is added to the pending queue and can be downloaded. ● The PI adapter downloads these stored invoices with service type line items from Ariba Networkand sends them to the SAP ERP system. ● Although the invoice for the service sheets contains taxes and other charges, Ariba Network Adapter for SAP NetWeaver does not process the taxes in the service sheets. The following customer exits support auto-generated service sheets for invoices containing service type line items: ○ EXIT_SAPLMRMH_011 ○ EXIT_SAPLMRMH_015 For more information on customer exits, see Implementing Customer Exits for Invoices with Service Type Line Items [page 326]. Customers can implement the following methods for service sheets: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
325
○ Class /ARBA/CL_SES_INV_HIERARCHY contains the following methods: ○ MODIFY_IDOC_DATA – Use this method to modify the IDoc data container in the specific format. ○ MODIFY_FRSEG – Use this method to modify FRSEG-WRBTR(Amount) in the invoice line item table.
Configuring Service Sheets Buyers must configure their SAP ERP system to process service sheets created for purchase orders containing service type items. Implementing Customer Exits for Invoices with Service Type Line Items [page 326] Specifying Time-Out Intervals for Processing Service Sheets [page 327] Implementing Enhancements for Service Sheets Created for New Purchase Orders [page 328] Implementing Enhancements for Service Sheets Created for Changed or Canceled Purchase Orders [page 330]
Implementing Customer Exits for Invoices with Service Type Line Items Context Add customer exits to invoices with service type line items to make specific integration requirements.
Procedure 1. Go to the transaction code CMOD. 2. Create an SAP Enhancement project. For example, ZMRMH. If you already have an existing SAP project for enhancement MRMH0002, use the same project. ○ Click Create. ○ Enter a description in the Short Text field. 3. Click Enhancement assignments. The Create Object Directory Entry screen appears. 4. Choose the package. 5. Save the changes. The SAP Enhancements in Enhancement Project page appears. 6. Enter MRMH0002 in the Enhancement text box and then press Enter. 7. Click Components. 8. Double-click EXIT_SAPLMRMH_011. The program INCLUDE - ZXM08U22 appears. 9. Double-click INCLUDE - ZXM08U22 in the Function Builder: Display EXIT_SAPLMRMH_011 page to create the program.
326
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
10. Enter the following code in the program INCLUDE - ZXM08U22:
Source Code DATA: lo_badi TYPE REF TO /arba/cl_ses_inv_hierarchy. CREATE OBJECT lo_badi. lo_badi->modify_idoc_data( EXPORTING i_bukrs = i_bukrs i_lifnr = i_lifnr i_idoc_contrl = i_idoc_contrl IMPORTING e_bukrs = e_bukrs e_lifnr = e_lifnr e_change = e_change CHANGING t_idoc_data = t_idoc_data[] ). 11. Repeat Steps 7 to 10 to create the customer exit for EXIT_SAPLMRMH_015. 12. Enter the following code in the program INCLUDE-ZXM08U26:
Source Code DATA: lo_badi TYPE REF TO /arba/cl_ses_inv_hierarchy. CREATE OBJECT lo_badi. lo_badi->modify_frseg( CHANGING t_frseg = t_frseg[] t_co = t_co[] t_ma = t_ma[] e_rbkpv = e_rbkpv e_change = e_change ). 13. Save the entries. 14. Click the Activate button to go back to the CMOD screen. 15. Activate the customer exit in the CMOD screen.
Specifying Time-Out Intervals for Processing Service Sheets Context In some cases, the SAP ERP system fails while processing multiple service sheets for the same purchase order service type item. To prevent failures while processing multiple service sheets, Ariba recommends that you specify a time-out duration. This time-out duration ensures that no resources stay locked on the SAP ERP system. Specify the time-out duration by adding the parameter to the /ARBA/PARAM_TAB table.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
327
Procedure 1. Go to Transaction SM30. 2. Go to the /ARBA/PARAM_TAB table. 3. Maintain the following values in the /ARBA/PARAM_TAB table: ○ Variable Name : /ARBA/ENTRYSHEET_CREATE ○ Field Name : TIMEOUT ○ Number : 0 ○ INCL/EXCL : I ○ Option : EQ ○ Selection Value: 100
Note This value depends on the time-out value required by the customer.
Implementing Enhancements for Service Sheets Created for New Purchase Orders Context To send statuses for service sheets created against new purchase orders to Ariba Network, you must implement the following enhancement.
Procedure 1. Go to transaction SE37. 2. Enter the program name, IDOC_OUTPUT_ORDERS and click Display. The Function Builder: Display IDOC_OUTPUT_ORDERS page appears. 3. Go to Function Perform fill_srv_orders. 4. Double-click the function, Perform. 5. Select the SAPLEINM program in the Choose Main Program for LEINMF0Q page and click Choose. The ABAP Editor:Display Include LEINMF0Q page appears. 6. Click the Enhance button on the application toolbar. 7. On the Edit menu, click Enhancement Operations and then click Show Implicit Enhancement Options. 8. Right-click on the line below the text FORM fill_srv_orders:, click Enhancement Implementation and then click Create. 9. Click Code on the Choose Enhancement Mode page. The Select or Create Enhancement Implementation page appears.
328
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
10. Click the Create enhancement implementation button. The Create Enhancement Implementation page appears. 11. If you already have a custom enhancement, you can use the same custom enhancement. Or you can create a new enhancement implementation. Enter a name and description. For example, zcanceled_po. 12. Press Enter. The Package page appears. 13. Specify the Z or Y package and press Enter to save it to a transport request. 14. Copy and paste the following code in the Enhancement Implementation for the Class for the create purchase order interface:
Source Code DATA: l_flag(5) TYPE c, cl_purchaseorder TYPE REF TO /arba/cl_purchaseorder, cl_po_hierarchy TYPE REF TO /arba/cl_po_hierarchy, ls_idoc_status TYPE bdidocstat, lx_appl_idoc TYPE REF TO /arba/cx_appl_idoc. CONSTANTS: c_true TYPE char4 VALUE 'true', c_false(5) TYPE c VALUE 'false'. CREATE OBJECT cl_purchaseorder. CREATE OBJECT cl_po_hierarchy. TRY. CREATE OBJECT cl_po_hierarchy. CALL METHOD cl_po_hierarchy->get_systemversion_ishierarchy EXPORTING ebeln = ekpo-ebeln et_edi_esll = edi_esll[] IMPORTING flag = l_flag CHANGING int_edidd = int_edidd[]. CATCH /arba/cx_appl_idoc INTO lx_appl_idoc. MESSAGE e151(/arba/message) RAISING error_message_received. RETURN. ENDTRY. IF l_flag EQ c_true. CALL METHOD cl_purchaseorder->fill_service_line_number EXPORTING packno = ekpo-packno IMPORTING et_edi_esll = edi_esll[]. ENDIF. 15. Right-click on the line below the text FORM fill_srv_orders:, click Enhancement Implementation and then click Create. 16. Click Code on the Choose Enhancement Mode page. The Select or Create Enhancement Implementation page appears. 17. Select the already created enhancement implementation that you created in Step 13. 18. Copy and paste the following code in the Enhancement Implementation for the Class for the create purchase order interface:
Source Code if l_flag EQ c_true. CALL METHOD CL_PURCHASEORDER->CREATE_PARENT_CHILD_RELATION
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
329
EXPORTING EDI_ESLL = edi_esll[] CHANGING INT_EDIDD = int_edidd[] . endif. 19. Activate the code.
Implementing Enhancements for Service Sheets Created for Changed or Canceled Purchase Orders Context To send statuses for service sheets created against purchase orders that have been changed or canceled to Ariba Network, you must implement the following enhancement.
Procedure 1. Go to transaction SE38. 2. Enter the program name, LEINMF0Q and click Display. 3. Select the SAPLEINM program in the Choose Main Program for LEINMF0Q page and click Choose. The ABAP Editor:Display Include LEINMF0Q page appears. 4. Click the Enhance button on the application toolbar. 5. On the Edit menu, click Enhancement Operations and then click Show Implicit Enhancement Options. 6. Right-click on the line below the text FORM lesen_beleg:, click Enhancement Implementation and then click Create. 7. Click Code on the Choose Enhancement Mode page. The Select or Create Enhancement Implementation page appears. 8. Click the Create enhancement implementation button. The Create Enhancement Implementation page appears. 9. If you already have a custom enhancement, you can use the same custom enhancement. Or you can create a new enhancement implementation. Enter a name and description. For example, zcanceled_po. 10. Press Enter. The Package page appears. 11. Specify the Z or Y package and press Enter to save it to a transport request. 12. Copy and paste the following code in the Enhancement Implementation for the Class for the Change or Cancel interface:
Source Code DATA: cl_PO_ChangeCancel TYPE REF TO /arba/cl_PO_ChangeCancel. CREATE OBJECT cl_PO_ChangeCancel. CALL METHOD cl_PO_ChangeCancel->trigger_delete_po_idoc EXPORTING ebeln = h_ebeln
330
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
CHANGING xdruvo = xdruvo. 13. Activate the code.
Configuring ERP-Initiated Invoices to Use the IDOC Configure your ERP system to can use the GSVERF03 IDOC to send MM invoices and the FIDCCP02 IDOC to send FI invoices.
Note You must maintain the tax code for MM invoices in the /ARBA/TAXCAT_MAP table to process the tax values in the invoices correctly. If the tax code does not exist in the /ARBA/TAXCAT_MAP table, Ariba Network Adapter for SAP NetWeaver does not process the tax code in the MM invoices. The tax code in the invoice that is sent to Ariba Network is blank Configuring the NACE Setting to Send ERS Invoices [page 331] Configuring the NACE Setting to Send Invoicing Plans [page 333] Configuring the NACE Setting to Send MIRO Invoices [page 334] Implementing the Customer Exit for MM Invoices [page 335] Implementing Routines to Prevent Creation of Duplicate MM IDOCs [page 336] Maintaining Partner Profiles [page 337] Configuring the FI Invoices [page 338] Setting Document Type Filters for FI Invoices [page 339] Maintaining Output Types for FI Invoices [page 340] Implementing the Customer Exit for FI Invoices [page 341] Handling Errors [page 342]
Related Information ERP-Initiated Invoices Using the IDOC Transmission Method [page 23]
Configuring the NACE Setting to Send ERS Invoices Context Configure the NACE setting to send the ERS (Evaluated Receipt Settlement) invoices using the IDOC. Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
331
Procedure 1. Start transaction NACE. 2. Select application MR and then click Output types. 3. Select ERS Output type for ERS invoices and then click Processing routines. 4. Select INS Output type for Invoice Plan and then click Processing routines. 5. Add the EDI entry with the following values: ○ Medium: EDI ○ Program: RSNASTED ○ FORM routine: EDI_PROCESSING 6. Click Partner functions link and add the following EDI entries: ○ Medium: EDI ○ Funct: VN ○ Name: Vendor 7. Go back to the NACE transaction and click Condition records. 8. Double-click ERS output type and click CoCode, Vendor to maintain condition records. These values are also applicable for the Invoice Plan output type. 9. Click Execute. 10. Enter the following values in the Change Condition Records (ERS Procedure): Fast Change screen: ○ Vendor: For example, 3000. ○ Name: Name of the vendor ○ Funct: VN ○ Partner: Vendor number. ○ Medium: 6 ○ Date/Time: 4 11. Go to transaction code WE20 to maintain the partner profiles. Maintain the partner profile for the vendor. For example, Vendor 1000. 12. Double-click to expand partner type LI node and then click the vendor. For example, Vendor 1000. 13. In the Partner profiles:Outbound parameters screen, maintain the following values: ○ Partner No.: For example, 1000. ○ Partn. Type: LI ○ Partner Role: VN ○ Message Type: GSVERF In the Outbound Options tab, ensure that you maintain the following entries: ○ Receiver port: Enter the name of the receiver port. ○ Transfer IDoc Immed.: Select the radio button. ○ Basic type: GSVERF03 ○ Extension: /ARBA/ GSVERF03 ○ Cancel Processing After Syntax Error: Select the check box. 14. In the Partner Profiles screen, maintain the following values: ○ Partner No.: For example, 1000 .
332
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
○ Partn. Type: LI In the Post processing permitted agent tab, maintain the following values: ○ Ty. : 0 ○ Agent: 50010120 ○ Lang.: EN In the Outbound parmtrs. section, maintain the following values: ○ Partner Role: VN ○ Message Type: GSVERF 15. Go to Message Control tab and maintain the following values: ○ Application: MR : Invoice Verification ○ Message Type: ERS : ERS Procedure ○ Process code: MRRL: ERS procedure for Logistics invoice verification
Results This completes the configuration for the ERS invoices.
Configuring the NACE Setting to Send Invoicing Plans Context Configure the NACE setting to send the Invoicing plans using the IDOC.
Procedure 1. Start transaction NACE. 2. Select application MR and then click Output types. 3. Select ERS Output type for ERS invoice and then click Processing routines. 4. Select INS Output type for Invoice Plan and then click Processing routines. 5. Add the EDI entry with the following values: ○ Medium: EDI ○ Program: RSNASTED ○ FORM routine: EDI_PROCESSING 6. Click Partner functions link and add the following EDI entries: ○ Medium: EDI ○ Funct: VN Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
333
○ Name: Vendor 7. Go back to the NACE transaction and click Condition records. 8. Double-click INS output type and click Company Code/Invoicing to maintain condition records. 9. Enter the company code and invoicing party. 10. Click Execute. 11. Enter the following values in the Change Condition Records (Invoice Plan): Fast Change screen: ○ Company Code: Enter the company code. ○ Inv. Pty: For example, 1000. ○ Funct: VN ○ Partner: 0000001000 ○ Medium: 6 ○ Date/Time: 4 12. Click Execute. 13. Go to transaction code WE20 to maintain the partner profiles. 14. Maintain the partner profile for the vendor . For example, Vendor 1000. Double-click to expand partner type LI node and then click the vendor. For example, Vendor 1000. 15. Double-click the GSVERF message type in the Outbound parmtrs. section. 16. Click the Message Control tab and add the following values: ○ Application: MR ○ Message type: INS ○ Process code: MRRL 17. Enter the following values in the Outbound Options tab: ○ Receiver port: Enter the name of the receiver port. ○ Pack. Size: 1 ○ Transfer IDoc Immed.: Select the radio button. ○ Basic type: GSVERF03 ○ Extension: /ARBA/ GSVERF03 ○ Cancel Processing After Syntax Error: Select the check box. 18. Click Save.
Configuring the NACE Setting to Send MIRO Invoices Context Configure the NACE setting to send the MIRO invoices using the IDOC.
334
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Procedure 1. Start transaction NACE. 2. Select application MR and then click Procedures. The Change View "Procedures": Overview page appears. 3. Click MR0002 procedure in the Procedures table and then double-click the Control folder dialog structure. 4. Add the following entries in the Reference Step Overview section on the Change View “Control”: Overview page: ○ Step: 30 ○ Counter: 0 ○ CTyp: ERS ○ Description: ERS Procedure
Implementing the Customer Exit for MM Invoices Context Implement customer exits to make specific integration requirements to the transmission of MM invoices.
Procedure 1. Implement the Customer exit as follows: ○ Go to the transaction code CMOD. ○ Enter a name. For example, ZSUSMM1. ○ Click Create. ○ Enter a description in the Short Text field. 2. Click Enhancement assignments. The Create Object Directory Entry screen appears. 3. Enter the following values: ○ Object: R3IR CMOD 2SUSMM1 ○ Package: Enter a name. 4. Save the changes. 5. Enter MRMN0001 in the Enhancement text box and then click Enter. 6. Click Components. 7. Double-click EXIT_SAPLMRMN_001. 8. Double-click INCLUDE ZXMRNU01 in the Function Builder: Display EXIT_SAPLMRMN_001 page. 9. Enter the following code:
Code Syntax /arba/cl_invoice_get_details=>invoice_get_details( Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
335
EXPORTING if_ident is_data_ers is_data_rap is_data_kons if_segnam CHANGING ct_idoc_data
= = = = =
if_ident is_data_ers is_data_rap is_data_kons if_segnam
= ct_idoc_data[] ).
10. Save the entries. 11. Click the Activate button to go back to the CMOD screen. 12. Activate the customer exit in the CMOD screen. 13. To send the XBLNR – reference document number as the Invoice ID to Ariba Network, do the following: ○ Go to transaction code SM30. ○ Maintain the following parameter in the /ARBA/PARAM_TAB table. ○ Variable Name: INVOICE_DOC_OPTION ○ Field Name: To be left blank ○ Number: 0 (zero) ○ INCL/EXCL: I ○ Option: EQ ○ Selection value: XBLNR 14. Save the entries.
Implementing Routines to Prevent Creation of Duplicate MM IDOCs Context The Ariba Network Adapter for SAP NetWeaver creates an FI IDOC each time an FI invoice is created on the SAP ERP system. In some cases, the MM invoices have duplicate IDOCs. To restrict the creation of duplicate MM IDOCs, you must implement a routine.
Procedure 1. Go to Transaction VOFM. 2. On the Requirements menu, click Output control. 3. Scroll to the end and go to the routine number field. 4. Enter any routing number starting with 9. For example, 904. Customer routines start with the number 9. 5. In the Application field, enter MR and press Enter. The Register Object page appears where you must enter the access key. 6. Ensure that you generate the access key for the routine to enable you to write add the ABAP code. To generate the access key, register the object in the SSCR (SAP Software Change Registration) by providing the object name.
336
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
7. Enter the access key for the object. 8. Click Continue. 9. Click the routine number in the Maintain: Requirements Output control page and then click then Source text button on the application tool bar. 10. Press Enter. A new ABAP editor page appears. 11. Copy and paste the following code in the FORM KOBEV_:
Source Code DATA: lv_subrc TYPE subrc. /arba/cl_invoice_get_details=>restrict_duplicate_idocs( EXPORTING t683s = t683s komkbmr = komkbmr CHANGING xnast = xnast[] cs_subrc = lv_subrc ). IF lv_subrc IS NOT INITIAL. sy-subrc = lv_subrc. ENDIF. 12. Save the changes and click the Activate button. 13. Click the Back button to go back and select the routine number on the Maintain: Requirements Output control page. 14. On the Edit menu, click Activate to activate the routine.
Maintaining Partner Profiles Context You must maintain the logical system profile for the outbound parameters if you use the IDOCs to process CC Invoices on the SAP ERP system..
Procedure 1. Go to transaction code WE20 to maintain the partner profiles. 2. Double-click to expand partner type LS node and then click the vendor for that you want to maintain the partner profile. 3. In the Partner profiles: Outbound parameters screen, maintain the following values: ○ Partner No.: Enter the logical system for the SAP ERP system. For example, 1000. ○ Partn. Type: LS ○ Partner Role: Specify the vendor. ○ Message Type: FIDCC2 In the Outbound Options tab, ensure that you maintain the following entries: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
337
○ Receiver port: Enter the name of the receiver port. ○ Transfer IDoc Immed.: Select the radio button. ○ Basic type: FIDCCP02 ○ Extension: /ARBA/ FIDCCP02 ○ Cancel Processing After Syntax Error: Select the check box. 4. Repeat Step 3 for the other Message Type: SYNCH.
Configuring the FI Invoices Context
Add configuration for sending FI invoices using the BD64 transaction. If the FI invoices are getting cleared automatically, please refer to Question 6 of the SAP Note 114814.
Procedure
1. Go to transaction BD64. 2. Click the Edit button and then click Create Model View . The Create Model View screen appears. 3. Enter the following values in the Create Model View screen: ○ Short text: Enter a description. ○ Technical name: Enter a technical name. For example, ZFI. ○ Start date: Specify the start date. ○ End Date: Specify the end date. 4. Click Add Message Type. 5. Add the FIDCC2 message type and specify the sender and receiver system information. 6. Click Continue. 7. Go to transaction code WE82 and link the FIDCC2 message type to the /ARBA/FIDCCP02 extension. 8. Go to the transaction code BD82 to generate the partner profile for the FI transaction. Enter the following details: ○ Model View: ZFI ○ Partner System: Enter the system port for the partner system. ○ Pack. Size: For example, 100 IDocs 9. Click the Transfer IDoc immediately option in the Output Mode section. 10. Click the Trigger Immediately option in the Inb. Parameter section. 11. Click Execute. This creates the FIDCC2 and the SYNCH Message types as the Outbound Parameters at the logical system profile.
338
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Results
Ensure that the outbound parameters at the logical system profile have been created. Verify these changes in the Outbound Options tab. See Maintaining Partner Profiles [page 337] to create partner profiles.
Setting Document Type Filters for FI Invoices Context
Maintain filters for FI invoices based on the document types. These filters can also be used to process purchase orders that do not have specific document types.
Procedure
1. Go to Transaction BD59. 2. Enter FIDCC2 in the Message Type field and press Enter. 3. Click New Entries. The New Entries: Overview of Added Entries page appears. 4. Add the following segment types. Enter an object name in the ALE Object Type field for each of the following segment types: ALE Object
Segm. Type
No.
Field
Offset
IntLength
E1FIKPF Enter a name for the ALE object type. For example, BLART.
1
BLART
20
2
Enter a name for the ALE object. For example, BUKRS.
E1FIKPF
1
BUKRS
0
6
Enter a name for the ALE object. For example, ZXREF1_HD.
E1FIKPF
1
XREF1_HD
378
20
5. Save the entries. 6. Go to Transaction BD95. 7. Click New Entries. The New Entries: Overview of Added Entries page appears. 8. Add the following entries:
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
339
ALE Object
Table Name
Field Name
Enter the name of the ALE object type. For example, BLART.
BKPF
BLART
Enter the name of the ALE object type. For example, BUKRS.
T001
BUKRS_GLOB
Enter the name of the ALE object type. For example, ZXREF1_HD.
BKPF
XREF1_HD
9. Save the entries. 10. Go to Transaction BD64. 11. Click Edit and go to the model view FI. Click to expand it. 12. Double-click the Data filter node. 13. Click Create Filter Group. The Filter group displays the Global CoCde, Ref.key (header) 1, and Document Type filter fields. 14. Double-click Global CoCde. 15. Click the Add button and add the global company codes for which the IDOC’s must be activated.
Note If you maintain the company code instead of the global company code in the Global CoCde filter, the SAP ERP system displays a warning message. You can also save the changes. However, if you save the changes, the IDOC does not get generated for any of the FI invoices that you create on the SAP ERP system. This is because the data filter specified has the company code entries instead of the global company code. 16. Double-click Ref.key (header) 1. 17. Click the Add button and enter ISFIINVOICE in the Filter object type field. 18. Double-click Document Type filter and then click the Add button. 19. Add the document types that you want to filter for the FI invoices. For example, KR, KZ, and RE. 20.Click Continue and save the BD64 entries.
Maintaining Output Types for FI Invoices Context Maintain the output types that you need for the FI invoices. If you do not maintain the output types in the /ARBA/ PARAM_TAB table, Ariba Network Adapter for SAP NetWeaver processes the FI invoices with the standard output type as ERS (Evaluated Receipt Settlement) invoices. Ensure that you create the routine before you maintain the output types in the NACE transaction.
340
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Procedure 1. Go to SM30. 2. In the /ARBA/ PARAM_TAB table, maintain the new output types that you require for the FI invoice. 3. Go to Transaction NACE. 4. Click Procedures. 5. Select application MR and then click Procedures. The Change View "Procedures": Overview page appears. 6. Click MR0002 procedure in the Procedures table and then double-click the Control folder dialog structure. The Change View “Control”: Overview page appears. 7. Enter the routine number that you created in the Requirement field for the ERS condition type in the Reference Step Overview section on the Change View “Control”: Overview page. 8. Repeat Step 5. Click the MR0004 procedure and repeat Step 6-7.
Implementing the Customer Exit for FI Invoices Context Implement customer exits to make specific integration requirements to the transmission of FI invoices.
Procedure 1. Implement the Customer exit as follows: ○ Go to the transaction code CMOD. ○ Enter a name. For example, ZFIDOC. ○ Click Create. ○ Enter a description in the Short Text field. 2. Click Enhancement assignments. The Create Object Directory Entry screen appears. 3. Click Local Object. 4. Enter the following values: ○ Object: R3TR CMOD ZFIDOC ○ Package: Enter a name. 5. Save the changes. The SAP Enhancements in Enhancement Project page appears. 6. Enter F050S004 in the Enhancement text box and then press Enter. 7. Click Components. 8. Double-click EXIT_SAPLF050_001. 9. Double-click INCLUDE ZX050U01 in the Function Builder: Display EXIT_SAPLF050_001 page. 10. Enter the following code: Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
341
Code Syntax CALLMETHOD /arba/cl_invoice_get_details=>fi_get_line_amount EXPORTING message_type = message_type sap_segment_name = sap_segment_name sap_segment_data = sap_segment_data fi_document_header = fi_document_header fi_document_item = fi_document_item CHANGING cust_segment_name = cust_segment_name cust_segment_data = cust_segment_data. 11. Save the entries. 12. Click the Activate button to go back to the CMOD screen. 13. Double-click EXIT_SAPLF050_007. 14. Double-click INCLUDE ZX050U07 in the Function Builder: Display EXIT_SAPLF050_007 page. 15. Enter the following code:
Code Syntax /arba/cl_invoice_get_details=>fi_invoice_get_details( EXPORTING if_message_type = message_type CHANGING ct_idoc_data = idoc_data[] ct_idoc_control = idoc_control cs_boole = distribution ). 16. Save the entries. 17. Click the Activate button to go back to the CMOD screen. 18. Activate the customer exit in the CMOD screen. 19. You must maintain the Ariba tax codes. To maintain the tax code, do the following: ○ Go to transaction code SM30. ○ Maintain the required tax codes in the /ARBA/TAXCAT_MAP table.
Note When an IDOC is generated for an FI invoice, the Ariba Procurement Solution does not map the Distribution node.
Handling Errors Buyers can use the SLG1 transaction code to view all messages in the application log on the SAP system. Errors that occur while transmitting the MM and FI invoices in the Ariba Procurement Solution are stored in the SXMB_MONI if a system error occurs while sending the invoices from the ERP system to the PI. Buyers can use the SLG1 T-code to view all messages in the application log on the SAP system.
342
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Configuring Your SAP ERP System
Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
Overview [page 343] Installation Requirements for SAP Suite Add-On [page 346] Setting Up the cXML Adapter [page 347] Configuring Logging for the SAP Suite Add-On [page 350] Configuring the cXML Adapter [page 350] Configuring the System Landscape Directory [page 350] Configuring Transaction Processes [page 354] Configuring Integration Scenarios in the Integration Directory [page 356] Configuring the Integration Directory for Inbound Transactions [page 357] Configuring the Integration Directory for Outbound Transactions [page 364] Linking Multiple SAP Instances with Ariba Network [page 371] Testing the SAP NetWeaver for Suite Add-On Configuration [page 375] Understanding Error Handling [page 376] Monitoring the cXML Adapter from Runtime Workbench [page 379] Deploying the Project [page 380] Enabling Support for Attachments [page 381] Using Endpoints for Integration with SAP NetWeaver for SAP Suite Add-On [page 382] Using the SAP NetWeaver PI KeyStore [page 382]
Overview The Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On is an add-on module for SAP business applications that enables integration between Ariba Network and SAP Suite Add-On component available in your SAP ERP system. SAP Suite Add-On is developed by SAP to allow SAP ERP systems to connect to Ariba Network through SAP NetWeaver PI. SAP ERP buyers and suppliers using Ariba Network Adapter for SAP NetWeaver integrated with SAP Suite Add-On and Ariba Network can now send and receive transactional documents through the PI layer or directly without the Ariba Integration Toolkit.
Note The SAP Suite Add-On module generates documents in cXML format and therefore does not require ABAP transports.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
343
The Ariba Network Adapter for SAP NetWeaver runs on the SAP NetWeaver Process Integration (PI), and can be thought of as a library for SAP NetWeaver PI. This library includes integration processes and Java libraries that implement the cXML transport protocol and provide a set of facilities for resolving differences between SAP and Ariba Network. For more information about cXML and Ariba Network, refer to the following documents, available from Connect (http://connect.ariba.com ): ● Ariba Network Integration Guide ● Ariba Network Buyer Administration Guide ● Ariba cXML Solutions Guide ● cXML User’s Guide The Ariba Network Adapter for SAP NetWeaver consists of the following: ● The design package, which contains integration processes, interface objects, and communication channels. ● The cXML Adapter, which conforms to the J2EE Connector Architecture (JCA) specification, and implements the cXML transport protocol. For more information about the JCA specification, see the relevant section on the Sun Java web site (http:// www.java.sun.com ). ● The product and component definitions that are available in a CIM file. The following graphic illustrates how the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On enables the communication flow between Ariba Network and the SAP Suite Add-On.
SAP NetWeaver PI is a platform for process integration within SAP NetWeaver. It facilitates cross-system business processes. In particular, it enables different versions of SAP and non-SAP systems from different vendors running on different platforms to communicate with each other. SAP NetWeaver PI integrates the following components used by the Ariba Network Adapter for SAP NetWeaver and its modules: ● The Integration Engine is the central runtime component of the SAP NetWeaver PI Integration Server used for receiving, processing, and forwarding messages. ● The Adapter Engine is a runtime component of the SAP NetWeaver PI Integration Server. It uses adapters to connect the Integration Engine to SAP systems (RFC adapter) and external systems.
344
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
Supported Document Types
The following transactions are supported as part of the Ariba Network integration with SAP Suite Add-On: Outbound Transactions for Buyers
Inbound Transactions for Buyers
Purchase Order
Order Confirmation
Change Purchase Order
Ship Notice
Goods Receipt
Invoice
Payment Proposal
CC Invoice
Receipt Request
Pay Me Now
Remittance Advice
Service Entry Sheet
Remittance Status Update
Quote Message
Service Entry Sheet Response Status Update Request Quote Request Outbound Transactions for Suppliers
Inbound Transactions for Suppliers
Order Confirmation
Purchase/Sales Order
Ship Notice
Change Purchase Order
Invoice
Goods Receipt
CC Invoice
Payment Proposal
Pay Me Now
Receipt Request
Service Entry Sheet
Remittance Advice
Quote Message
Remittance Status Update Service Entry Sheet Response Status Update Request Quote Request
Workflow for Configuring the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
Setting up the adapter involves the following high-level steps: 1. Verifying that all the software and connectivity requirements are in place. 2. Setting up and configuring the cXML Adapter. 3. Configuring the System Landscape Directory. 4. Configuring transaction processes. 5. Configure the SAP Suite Add-On component. 6. Testing the configuration. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
345
Installation Requirements for SAP Suite Add-On Supported SAP Netweaver PI Versions The following table lists the Ariba Network Adapter for SAP NetWeaver versions and the supported SAP Netweaver PI versions that they can be deployed on: Ariba Network Adapter for SAP NetWeaver Version
Supported SAP Netweaver PI Versions
Cloud Integration 1
SAP Netweaver PI 7.1 SAP Netweaver PI 7.3
Cloud Integration 2 or higher
SAP Netweaver PI 7.1 SAP Netweaver PI 7.3 SAP Netweaver PI 7.4
For information about the platforms that the SAP NetWeaver suite supports, see the following SAP NetWeaver section on the SAP Service Marketplace: service.sap.com > SAP NetWeaver > SAP NetWeaver PI 7.X > Availability.
Ariba Network Requirements Ensure that you have the following Ariba Network requirements before installing the Ariba Network Adapter for SAP NetWeaver: ● A valid, configured Ariba Network Buyer account. For more information about configuring your Ariba Network Buyer account, see the Ariba Network Buyer Administration Guide. ● An Ariba Network supplier relationship, including an ANID-to-Private ID mapping. For more information about creating a supplier relationship, see Chapter 4, “Configuration” in the Ariba Network Integration Guide. ● If the Ariba Network Buyer account is configured to use digital certificate authentication, then a valid Secure Socket Layer (SSL) client certificate from one of Ariba Networks trusted Certificate Authorities is required. For more information about obtaining a digital certificate, see Ariba cXML Solutions Guide. ● Ariba Network requires that all communication between the Ariba Network Adapter for SAP NetWeaver and Ariba Network travel over the internet using Secure HyperText Transfer Protocol (HTTPS), a secure protocol that encrypts communication before transmission. For more detailed information about internet connectivity requirements, see the Ariba Network Integration Guide. For more information about how to enable secure communications through a proxy server, see the cXML Adapter Parameters [page 391] section. ● The Ariba Network’s Certificate Authorities certificates are stored in the SAP NetWeaver PI Keystore. The cXML Adapter uses the certificates stored in the SAP NetWeaver PI Keystore to connect to Ariba Network.
Installation Files To install the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On, you need the relevant archive file which is available on Ariba’s support interface, Ariba Connect (http://connect.ariba.com).
346
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
For example, AribaNetworkAdapterSAPNetweaver_vCI_1.zip. The archive ZIP files contain the following components: Product definition files
AribaNetworkAdapterSAPNetweaver.SoftwareCatalog.zip
Design and Integration configuration files
AribaNetworkAdapterSAPNetweaver_SapAddOn.tpz
cXML Adapter and metadata definition files
AribaNetworkAdapterSAPNetWeaver.sca CacheCatalog.xml CanonicalCatalog.xml
Setting Up the cXML Adapter The Ariba Network Adapter for SAP NetWeaver relies upon the cXML Adapter, which conforms to the JCA specification and implements the cXML transport protocol. This section contains the following topics: ● Understanding cXML Adapter Document Transmission ● Deploying the cXML Adapter ● Configuring the Log ● Configuring the cXML Adapter
Understanding cXML Adapter Document Transmission Ariba Network exchanges business documents using the cXML (commerce eXtensible Markup Language) protocol. cXML defines document formats and interaction processes designed for exchanging procurementoriented information. The Ariba Network Adapter for SAP NetWeaver always uses HTTPS Post to send documents to Ariba Network. The Ariba Network Adapter for SAP NetWeaver initiates the cXML GetPending transaction to pull inbound business documents. The GetPending transaction allows the SAP ERP system to receive documents from Ariba Network through a data pull. The GetPending transaction is scheduled using the getPendingInterval parameter defined for each inbound transaction. Ariba Network responds with a GetPendingResponse document that includes zero or more DataAvailableMessage elements containing the internal ID of any waiting documents. For more information about document transmission methods, see the Ariba Network Integration Guide. For details on downloading this guide, see Ariba Network Certification [page 380].
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
347
Deploying the cXML Adapter If your version of SAP netweaver PI is prior to PI 7.3 EHP1, use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI. From SAP netweaver version PI7.3 EHP1 onwards you must use the SAP Software Update Manager (SUM) tool to deploy the adapter. For more information on how to install or upgrade using the SUM tool, contact your SAP systems administrator.
Deploying the cXML Adapter Using JSPM Context
Use the Java Support Package Manager (JSPM) tool to deploy the cXML Adapter on SAP NetWeaver PI.
Note You cannot undeploy the adapter using the JSPM. For information on how to undeploy the adapter, see Undeploying the Adapter using the Textconsole [page 349].
Note To upgrade to the latest version of the Ariba Network Adapter for SAP NetWeaver, you must first undeploy the existing adapter and then deploy the latest version that you have downloaded from connect.ariba.com.
Procedure
1. Navigate to the JSPM tool directory *****\JSPM\go.bat. For example, D:\usr\sap\NPI\DVEBMGS00\j2ee\\JSPM\go.bat. 2. Run the go.bat file to open the JSPM window. 3. Enter your user name and password to login. 4. Place the SCA file in the specified location in the JSPM window, and click Next. For example, D:\usr\sap\trans\EPS\in. 5. On the Start Deployment tab, choose New Software Components. 6. After the SCA file is loaded, click Next to start the deployment. 7. Click Next in the Specify Queue and Check Queue tabs. 8. This starts the deployment of the cXML Adapter. 9. Click Exit after the deployment is completed.
348
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
Undeploying the Adapter using the Textconsole Context
You must use the textconsole script to undeploy the adapter.
Procedure
1. Go to \j2ee\console. 2. Run textconsole.bat or textconsole.sh. The Telnet console appears. 3. Login with the relevant admin user. 4. Run the following at the telnet prompt: >undeploy name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_undeploy_error=stop Undeploy Settings: ○ on_undeploy_error=stop ○ on_prerequisite_error=stop ○ workflow=normal If there is an offline undeployment, Telnet connection to host might be lost and the following message appears: Processing undeployment operation, please wait... name: 'com.ariba.asc.sap.netweaver.xiadapter.ra', vendor: 'ariba.com', location: 'null', version: 'null', status: 'Success', description: '', sda: 'name: 'com.ariba.asc.sap.netweaver.xiadapter.ra', vendor: 'ariba.com', location: 'SAP AG', version: '3.0.1420051114090313.0000', software type: 'J2EE', dependencies: '[]'' >
Undeploying the Adapter using the Textconsole Procedure
Run the following at the Telnet prompt: deploy name=com.ariba.asc.sap.netweaver.xiadapter.ra vendor=ariba.com on_deploy_error=stop
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
349
Configuring Logging for the SAP Suite Add-On Configure logging to send log entries for the cXML adapter to a separate file. The log level can remain Error when running in a production environment, but Ariba recommends that you change the log level to Info. You can also find out about the version of the Ariba Network Adapter for SAP NetWeaver. 1. Login to the SAP NetWeaver PI log administration section at http:// XI_hostname_server:XI_port/nwa/logs. 2. Click the Log Configuration link. 3. Select Tracing Locations from the Show drop down list. 4. Select the node (package) com ariba asc , to set the logging level to log the complete adapter processing information, or select CXMLSender under connector.cxml.util to set the logging level to log only the exchanged messages. 5. Change the severity level from Error to Info / Debug in the Severity drop-down list, and then click Save Configuration in the toolbar.
Note For additional information, see the Ariba Network Integration 1.0 for SAP Business Suite http:// help.sap.com/se4aribanet10.
Configuring the cXML Adapter To allow the cXML adapter to run correctly, you must configure parameters for the Communication Channels for different business scenarios. This configuration is done at a later stage, during the configuration of Integration Scenarios in the Integration Directory. While configuring the communication channel for each outbound or inbound transaction, the Parameters tab has the System Type option to specify the system for the buyer or supplier connecting to the Ariba Network. For more details about how to create the Communication Channels, see the Communication Channels Configuration procedure for each scenario in the Configuring Integration Scenarios in the Integration Directory [page 356] section. For a description of the parameters and instructions for how to configure retry attempts, see cXML Adapter Parameters [page 391].
Configuring the System Landscape Directory Once you have installed the cXML Adapter, you must then configure the System Landscape Directory (SLD) by importing the Ariba Network Adapter for SAP NetWeaver product definition and defining the systems involved in the integration. The SAP System Landscape Directory is a central repository that holds the information on the
350
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
systems and software in the customer environment. It consolidates the information about components actively available, and on which machines, instances, and clients they are available. The Ariba Network Adapter for SAP NetWeaver leverages all the advantages of the SLD in order to maintain the coherence of the system landscape: ● It is defined as a product and component expressed in Common Information Interface (CIM) format importable in the SLD ● It uses a configuration using technical and business systems involved in the Ariba Network integration and defined in the SLD. You must make the following settings in the SLD: ● Import Ariba Network Product and Component definitions ● Define Technical and Business Landscape for Ariba Network ● Define Technical and Business Landscape for SAP ERP
Importing Ariba Network Product and Component Definitions Import the product and component definitions of Ariba products that will work with SAP NetWeaver PI, as a CIM file.
To import product and component definitions: Procedure 1. From the SAP NetWeaver PI main page, click System Landscape Directory. 2. Click Administration. 3. Open the SLD Administration page. 4. Under the Content section, click Import. 5. Click Browse and navigate to the location where the AribaNetworkAdapterSAPNetweaver.SoftwareCatalog.zip is stored. Select this file. 6. Click Import. 7. From the SAP NetWeaver PI main page, under Software Catalog, click Products and verify that the following product is available: ○ Vendor: ariba.com ○ Product: ASN ○ Version: ASN, NW04.1 8. Next, verify that the following component is available: ○ Vendor: ariba.com ○ Component: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CIX of ariba.com ○ Version: CIX Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
351
Results The Ariba Network Adapter for SAP NetWeaver is now recognized by the Integration Repository and Directory.
Defining Technical and Business System for Ariba Network Set up the technical system for the Ariba Network system using the Technical System Wizard.
To define the Technical System for Ariba Network: Procedure 1. Select Technical Systems from the main SLD page to open the Technical System page. 2. Click New Technical System to open the Technical System Wizard. 3. In the Wizard, select Third-Party as the Technical System Type to set up a third-party (non-SAP) application such as Ariba Network, and then click Next. 4. Specify the system details as follows: ○ System Name: Specify a user-defined system name here. E.g. TS_ASN ○ Host Name: Enter a host name here. E.g. an 5. Click Next. 6. Associate the ASC Connector product and component to the system. Scroll down the list to select the product, ASN, defined earlier, and then click Add. You can also filter to select the product to associate. Ensure that the component ARBA_SUPPLIER_CONN_ADAPTER, is selected. 7. Click Finish.
Next Steps Next, set up the business system for the Ariba Network system using the Business System Wizard.
To define the Business System for Ariba Network: Procedure 1. Select Business System from the main SLD page to open the Business System page. 2. Click New Business System here to open the Business System Wizard.
352
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
3. In the Wizard, select Third-Party as the technical system type to associate the business system with, and then click Next. 4. Select the technical system, TS_ASN, created in the previous procedure, from the System field, and then click Next.
Note The Logical System Name is not required. 5. Enter the business system name, e.g. BS_ASN, in the Name field, and click Next. 6. Specify the installed products. Make sure that the product ASN, NW04.1 and the related component ARBA_SUPPLIER_CONN_ADAPTER, CIX of ariba.com, installed on the technical system, are selected, and then click Next. 7. Click Finish.
Defining the Technical System for SAP ERP Context Set up the technical system for the SAP ERP system using the Technical System Wizard.
Procedure 1. Select Technical System from the main SLD page to open the Technical System page. 2. Click on New Technical System here to open the Technical System Wizard. 3. In the Wizard, select AS ABAP as the Technical System Type, and then click Next. 4. To specify the SAP ERP system details, enter values in the AS ABAP name (SID), Installation Number, and Database Host Name fields, and then click Next. 5. Specify the Message Server and Central Application Server. Enter values in the Host Name, and Message Server Port field. Specify a logon group for the Message Server by entering a value in the Logon Groups column and clicking Add Logon Groups to assign them. You can also filter to select the logon groups. Enter values in the Host Name and Instance Number fields for the Central Application Server, and then click Next. 6. (Optional) Define additional application servers if required. Specify values in the Host Name and Instance Number columns in the Application Server List table, and click Add Application Server. You can also filter to select the application server details. Click Next. 7. Define the Client. Enter values in the Client Number and Logical Client Name columns of the Client List table, and then click Next. 8. Define software product and components. Select the SAP ERP version installed on this technical system, as well all other products installed on the system. You can filter to select the installed products and the software components. 9. Click Finish. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
353
Next Steps Set up the business system for the SAP ERP system using the Business System Wizard.
Defining the Business System for SAP ERP Procedure 1. Select Business System from the main SLD page to open the Business System page. 2. Click New Business System here to open the Business System Wizard. 3. In the Wizard, select AS ABAP as technical system type to associate the business system with, and then click Next. 4. Select the technical system created in the previous procedure from the System drop down list, to associate it with the business system. Select a client for the selected technical system from the Client drop down list, and then click Next. 5. Enter the business system name. E.g. BS_SAPR3_50, and click Next. 6. Specify the installed products. Select the products that must be supported by this business system from the ones available from the associated technical system, to install them in the business system, and then click Next. 7. Select the role of the business system. Select Application System as the Business System Role and select your SAP NetWeaver PI instance name from the Related Integration Server drop-down list to specify the integration server. In the case of application systems, specify the integration server. 8. Click Finish.
Configuring Transaction Processes Once you have installed the SLD, you must then: ● Import the design package containing the transactions supported by the Ariba Network Adapter for SAP NetWeaver. ● Configure SAP NetWeaver PI connectivity to SAP ERP. ● Configure the different transactions in the Integration Directory by importing the scenarios from the Integration Repository. ● Configure the communication channels and the conditions for routing messages, for each supported transaction.
Note The names for objects in the Directory used in the configuration procedures are examples provided for illustration. You may use them or replace them with names and format corresponding to your system environment.
354
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
Importing the Design Package Context The transport file AribaNetworkAdapterSAPNetweaver_SapAddOn.tpz contains the definition of the business scenarios.
Procedure 1. Copy the package file AribaNetworkAdapterSAPNetweaver_SapAddOn.tpz to the import directory on the SAP NetWeaver PI server, *****\SYS\global\xi\repository_server\import. For example, D:\usr\sap\ARB\SYS\global\xi\repository_server\import. 2. Open the Integration Builder: Design Tool from the SAP NetWeaver PI main page. 3. From the Tools menu, select the Import Design objects... option. 4. Select AribaNetworkAdapterSAPNetweaver_SapAddOn.tpz from the available files list, and then click OK. 5. After the import completes, the component ARBA_SUPPLIER_CONN_ADAPTER CIX appears in the components list of the Integration Builder Design Tool.
Note The External SAP Add-On schema is http://ariba.com/xi/ASN/AddOn/CommonBasis. The Adapter metadata is http://ariba.com/xi/ASCAdapter.
Configuring SAP ERP Connectivity The inbound and outbound documents are exchanged between SAP NetWeaver PI and SAP ERP by using ABAP proxies. For information about proxy configuration for outbound documents, see cXML Adapter Parameters [page 391].
Assigning Business Systems in the Integration Directory Context The Integration Directory configuration of the Ariba Network Adapter for SAP NetWeaver uses the information on the Technical and Business systems from the SLD. You must assign the Business Systems defined and involved in the integration setup. Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
355
Procedure 1. Open the Configuration: Integration Builder from the PI main page. 2. In the Objects tab of the Integration Builder, navigate to
Service Without Party
Business System.
3. From the context menu for Business System, select Assign Business System to start the Assign Business System wizard. 4. Click on Continue in the first and second windows. Leave the Party field in the second window blank. 5. In the third window, Select Business Systems, select the business systems BS_ASN and BS_SAPR3_50 created earlier, from the list. For more information about creating business systems, see the Configuring the System Landscape Directory [page 350] section.
Note If you have multiple ERP systems, you must select all the Business Systems representing your SAP ERP instances involved in the integration. 6. Click to clear the Create Communication Channel Automatically check box, if it is checked, to avoid the creation of unnecessary channels. 7. Click Finish.
Configuring Integration Scenarios in the Integration Directory This section describes how to import and configure the integration scenarios in the SAP NetWeaver PI Integration Directory for the supported transactions. Use an integration scenario from the Integration Repository as a template for configuring the corresponding transaction in the Integration Directory. The Integration Scenarios are part of the Design package, which has to be imported into the Integration Repository first.
Note Do not activate the Change Lists feature of Integration Builder Configuration Tool until all the configuration steps are completed. You can configure these transaction scenarios in the following SAP NetWeaver PI versions: ● SAP NetWeaver PI 7.1 ● SAP NetWeaver PI 7.3 single stack (Java only) ● SAP NetWeaver PI 7.3 dual stack (ABAP and Java) ● SAP NetWeaver PI 7.4 single stack (Java only) ● SAP NetWeaver PI 7.4 dual stack (ABAP and Java)
356
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
Workflow for Configuring the Integration Scenario for Inbound And Outbound Transactions Configuring the integration scenarios for the outbound and inbound transactions involves the following steps: 1. Transfer the Integration Scenario from the Integration Directory
Integration Repository
Enterprise Service Builder
to the
Integration Builder . For more information, see:
○ Transferring the Integration Scenario for Inbound Transactions [page 357] ○ Transferring Integration Scenario for Outbound Transactions [page 364] 2. Configure the Integration Scenario. For more information, see: ○ About Configuring the Integration Scenario for Inbound Transactions [page 359] ○ About Configuring the Integration Scenario for Outbound Transactions [page 366] 3. Configure the Communication Channels. For more information, see: ○ Configuring Communication Channels for Inbound Transactions [page 362] ○ Configuring Communication Channels for Outbound Transactions [page 369] 4. Activate the integration scenario. For more information, see: ○ Activating the Scenario for Inbound Transactions [page 363] ○ Activating the Scenario for Outbound Transactions [page 370]
Note ○ Ensure that the design package is imported into your system and ready before you run these steps. The following steps assume that the different Business Systems are defined in the SLD. For more information, see About Configuring the System Landscape Directory [page 343]. ○ All the steps of a configuration scenario section must be completed to fully configure a scenario. ○ If you are an existing customer, you must delete the existing Configuration scenario and rerun the steps for the configuration scenario.
Configuring the Integration Directory for Inbound Transactions Transferring the Integration Scenario for Inbound Transactions Context
The first step to configure the integration scenario is to transfer the integration scenario to the Integration Builder. The integration scenario is loaded into the Integration Repository when the design package is imported.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
357
Procedure
1. From the SAP NetWeaver PI main page, select Integration Directory login to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard > Select Process Integration Scenario, click the Name field, and then click the Display Input Help pull-down menu and select Input Help. 4. Select the Process Integration Scenario for the following inbound transactions from the Enterprise Services Repository screen: Buyer ○ Order Confirmation Name: AR_AddOn_OrderConfirmation_Send Namespace: http://ariba.com/xi/ASN/AddOn/OrderConfirmation Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Ship Notice Name: AR_AddOn_AdvanceShipNotice_Send Namespace: http://ariba.com/xi/ASN/AddOn/AdvanceShipNotice Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Invoice Name: AR_AddOn_Invoice Namespace: http://ariba.com/xi/ASN/AddOn/Invoice Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Pay Me Now Name: AR__AddOn_PayMeNow_Send Namespace: http://ariba.com/xi/ASN/AddOn/PayMeNow Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Service Entry Sheet Name: AR_AddOn_ServiceEntrySheet_Send Namespace: http://ariba.com/xi/ASN/AddOn/ServiceEntrySheet Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ QuoteMessage Name: AR_AddOn_QuoteMessage_Send Namespace: http://ariba.com/xi/ASN/AddOn/QuoteMessage Software Component Version: ARIBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com Supplier ○ Sales Order Name: AR_AddOn_SalesOrder_Send Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com ○ Payment Remittances Name: AR_AddOn_PaymentRemittanceRequest_Send Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com 5. Click Continue.
358
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
6. If required, change the name of the scenario for the Integration Directory. 7. Click Finish and then Close. Once the integration scenario transfer is completed, the Model Configurator window appears.
About Configuring the Integration Scenario for Inbound Transactions Configuring the Integration Scenario involves the following steps: 1. Assigning the model. 2. Assigning the components. 3. Configuring the sender and receiver relations for individual connections. 4. Generating the configuration objects.
Assigning the Model for Inbound Transactions Procedure 1. In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique model that is selected by default. 2. After selecting the model, assign components to the application components for the selected integration scenario.
Assigning Components for Inbound Transactions Procedure 1. In the Model Configurator, click the Assign Component button. 2. In the Assign Components window, select the Business System Components for A2A tab to assign business systems for the integration scenario. 3. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is available. 4. Click the row under the Communication Component column, then click the Value List pull-down menu and select Value List
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
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
360
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
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
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 =
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.
362
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
Supplier ○ Sales Order |< Name of the Business System for Ariba Network>| CC_AddOn_Supplier_SalesOrder_cXML_Receiver | ○ Payment Remittance < Name of the Business System for Ariba Network> | CC_AddOn_Supplier_PaymentRemittanceRequest_cXML_Receiver 2. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network buyer account configuration. 3. Under the cXML Configuration section, select the Use SAP Add on Suite check box.
Note If you created the channel by copying from an existing channel, you must change the request type for each of the transactions to the in the Inbound Request Type field. 4. If required, edit the other parameters. 5. Update the cXML version parameter to the latest applicable version. For more information about the cXML adapter parameters, see cXML Adapter Parameters [page 391]. 6. Save the changes.
Activating the Scenario for Inbound Transactions Procedure Using the Change List tab on the main application screen, activate all the change lists containing the objects created and modified during the component setup.
Results This completes the configuration of the inbound transactions in SAP NetWeaver PI.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
363
Configuring the Integration Directory for Outbound Transactions Transferring Integration Scenario for Outbound Transactions Context The first step is to transfer the integration scenario to the Integration Builder. The integration scenario is loaded into the Integration Repository when the design package is imported.
Procedure 1. From the SAP NetWeaver PI main page, select Integration Directory login to the Configuration: Integration Builder application. 2. In the Integration Builder menu, select
Tools
Integration Builder , and then
Apply Model from ES Repository .
3. In the first screen of the Transfer Model from ES Repository wizard, Select Process Integration Scenario, click the Name field, and then click the Display Input Help pull-down menu and select Input Help. 4. Select the process integration scenario for the following transactions from the Enterprise Services Repository screen: Buyer: ○ Purchase Order Name: AR_AddOn_PurchaseOrder_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PurchaseOrder Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ CC Invoice Name: AR__AddOn_CCInvoice_Receive Namespace: http://ariba.com/xi/ASN/AddOn/ERPInvoice Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Proposal Name: AR__AddOn_PaymentProposal_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PaymentProposal Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Remittance Name: AR__AddOn_PaymentRemittance_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittance Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Remittance Status Update Name: AR__AddOn_PaymentRemittanceSUR_Receive Namespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittanceSUR Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com
364
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
○ Receipts Name: AR_AddOn_GoodsReceipt_Receive Namespace: http://ariba.com/xi/ASN/AddOn/GoodsReceipt Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ ServiceUpdateResponse Name: AR_AddOn_StatusUpdateResponse_Receive Namespace: http://ariba.com/xi/ASN/AddOn/StatusUpdateResquest Software Component Version: ARBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com
Note Buyers must use the new StatusUpdateRequest to send and receive status on invoices and service entry sheets. The Invoice Status Update Request is no longer available. ○ QuoteRequest Name: AR_AddOn_QuoteRequest_Receive Namespace: http://ariba.com/xi/ASN/AddOn/QuoteRequest Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com Supplier ○ Sales Order Confirmation Name: AR_AddOn_SalesOrderConfirmation_Receive Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com ○ Ship Notice Name: AR_AddOn_OutboundDeliveryNotification_Receive Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com ○ Invoice Name: AR_AddOn_Invoice_Receive Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com 5. Click Continue. 6. If required, change the name of the scenario for the Integration Directory. 7. Click Finish.
Results Once the integration scenario transfer is completed, the Model Configurator window appears.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
365
About Configuring the Integration Scenario for Outbound Transactions Configuring the Integration Scenario involves the following steps: 1. Assigning the model. 2. Assigning the components. 3. Configuring the sender and receiver relations for individual connections. 4. Generating the configuration objects.
Assigning the Model for Outbound Transactions Procedure 1. In the Model Configurator window, click the Select Component View button, and then click Apply to select the unique model that is selected by default. 2. After selecting the model, assign components to the application components for the selected integration scenario.
Assigning Components for Outbound Transactions Procedure 1. In the Model Configurator, click the Assign Component button. 2. In the Assign Components window, select the Business System Components for A2A tab to assign components for Ariba Network. 3. Click the Insert Line button ('+') to add a component entry in the table if no component entry line is available. 4. Click the row under the Communication Component column, then click the Value List pull-down menu and select Value List
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. 5. Click the Next Role button (the right arrow) to go to the next screen on the window. 6. Click the Insert Line button (’+’) to add a component entry in the table if no component entry line is available. 7. Click the row under the Communication Component column, then click the Value List pull-down menu and select Value List
366
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
8. Click the Save Settings button.
Configuring Sender and Receiver Relations for Individual Connections For Outbound Transactions Procedure 1. In the Model Configurator, click the Configure Connections button. You must assign Communication Channels to set up the connections. 2. In the Connections from Component Assignment tab in the Configure Connection window, click the empty Communication Channel cell corresponding to the business system for Ariba Network in the Receiver 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 ○ Purchase Order Name: CCT_AddOn_PurchaseOrder_cXML_Receiver Namespace: http://ariba.com/xi/ASN/AddOn/PurchaseOrder Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ CC Invoice Name: CCT_AddOn_CCInvoice_cXML_Receiver Namespace: http://ariba.com/xi/ASN/AddOn/ERPInvoice 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/PaymentProposal Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Payment Remittance Name: CCT_AddOn_PaymentRemittance_cXML_Receiver Namespace: http://ariba.com/xi/ASN/AddOn/PaymentRemittance 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.com/xi/ASN/AddOn/PaymentRemittanceSUR Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ Receipts Name: CCT_AddOn_GoodsReceipt_cXML_Receiver Namespace: http://ariba.com/xi/ASN/AddOn/GoodsReceipt Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.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. All rights reserved.
367
○ ServiceUpdateResponse ○ Name: CCT_AddOn_StatusUpdateResponse_cXML_Receive Namespace: http://ariba.com/xi/ASN/AddOn/StatusUpdateResponse_Receive Software Component Version: ARIBA_SUPPLIER_SUITE_ADDON_CONN_ADAPTER CIX of ariba.com ○ QuoteRequest Name: CCT_AddOn_QuoteRequest_cXML_Receiver Namespace: http://ariba.com/xi/ASN/AddOn/QuoteRequest Software Component Version: ARIBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com Supplier ○ Sales Order Confirmation Name: CCT_Supplier_SalesOrderConfirmation_cXML_Receiver Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com ○ Ship Notice Name: CCT_AddOn_Supplier_OutboundDeliveryNotification_cXML_Receiver Namespace: http://ariba.com/xi/ASN/AddOn/ Software Component Version: ARBA_SUPPLIER_ADDON_CONN_ADAPTER CI5 of ariba.com ○ Invoices Name: CCT_AddOn_Supplier_Invoice_cXML_Receiver 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 Receiver channel for the business system for Ariba Network in another transaction, you can create the communication channel by copying from a channel that has already been configured. 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 Receiver Business System Components table. 10. Click on the Value List drop down and select Value List
Generate Objects for Outbound Transactions Procedure 1. In the Model Configurator, click the Create Configuration Object button. 2. In the Create Configuration Object window, do the following:
368
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
○ 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. 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. 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.
Configuring Communication Channels for Outbound Transactions Procedure
1. In the Communication Channel list, 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. ○ ERP Invoice |< Name of the Business System for Ariba Network the AR_ERPInvoice_Receive Configuration Scenario.
| CCT_ERPInvoice_cXML_Receiver under
○ Payment Proposal |< Name of the Business System for Ariba Network | CCT_PaymentProposal_cXML_Receiver under the AR_PaymentProposal_Receive Configuration Scenario. ○ Payment Remittance |< Name of the Business System for Ariba Network
|
CCT_PaymentRemittance_cXML_Receiver under the AR_PaymentRemittance_Receive Configuration Scenario. ○ Payment Remittance Status |< Name of the Business System for Ariba Network
|
CCT_PaymentRemittanceSUR_cXML_Receiver under the AR_PaymentRemittanceSUR_Receive Configuration Scenario. ○ Goods Receipt |< Name of the Business System for Ariba Network |CC_AddOn_GoodsReceipt_cXML_Receiver under the AR_AddOn_GoodsReceipt_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. All rights reserved.
369
|< Name of the Business System for Ariba Network
|
CC_AddOn_StatusUpdateResponse_cXML_Receiver under the AR_AddOn_StatusUpdateResponse_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. 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. ○ 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. In the Parameters tab, set the parameters in the Authentication section to match your Ariba Network Buyer account configuration. 3. Under the cXML Configuration section, select the Use SAP Add on Suite check box.
Note If you created the channel by copying from an existing channel, you must change the request type for each of the transactions to the in the Outbound Request Type field. For more information about the cXML Adapter parameters, see cXML Adapter Parameters [page 391] 4. Update the cXML version parameter to the latest applicable version. 5. If required, edit the other parameters. 6. Save the changes.
Activating the Scenario for Outbound Transactions Procedure
Using the Change List tab on the main application screen, activate all the change lists containing the objects created and modified during the component setup.
370
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
Results This completes the configuration of the outbound transactions in SAP NetWeaver PI.
Linking Multiple SAP Instances with Ariba Network If your organization has more than one instance of SAP, you can link them to a single Ariba Network account. This allows all the documents from particular vendors to be routed to a single Ariba Network account and in the reverse direction, the documents from Ariba Network will be routed to a particular SAP ERP instance. Buying organization or service provider accounts must be enabled for multiple ERP systems by Ariba Network Support. The required configuration sections will not be available for accounts that have not been enabled. This section describes the following topics: ● The mechanisms involved in the documents routing ● The configuration to setup integration with Ariba Network of multiple SAP ERP instances.
Document Routing Mechanism If you have multiple ERP systems, each of the SAP ERP systems involved in the integration is identified by a unique identifier. This identifier, called the SystemID, corresponds to the logical system ID of the concerned SAP ERP instance. Each document that passes through the integration will be transformed as follows, to include or to retrieve this unique identifier from the cXML header: AN50000000365 0000009999 AN51000000349 T90CLNT090 Depending on the direction, the SystemID identifier is located in different locations: ● For outbound documents, it is located in the From element ● For inbound documents, it is located in the To element. 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.
371
When you have multiple ERP systems, the SystemID identifier is not inserted in the outgoing documents or expected in the incoming documents. However, the SAP Suite Add-On always sends the SystemID in ERPoutbound cXML documents. The following figure shows the SystemID identifier location in outbound documents at the top and in inbound documents at the bottom.
Figure 2: SystemID identifier location in the message exchanges
Multi-ERP Configuration The multi-ERP implementation requires configuration on all three sides: SAP ERP, SAP NetWeaver PI and Ariba Network.
372
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
Configuring the System Landscape Directory
You must configure all your SAP ERP instances in the SLD as Technical and Business Systems. For more information, see Defining the Technical System for SAP ERP [page 353] and Defining the Business System for SAP ERP [page 354].
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, see the Configuring SAP ERP Connectivity [page 355] section.
Configuring Integration Scenarios
The integration scenarios in the Integration Directory need to be parameterized in order to have the information on the systems and enable message routing.
Note When you configure your SAP Suite Add-On to support multiple instances of SAP, you must configure a content-based routing in PI for the cXML attributes. To do this, use a valid XPath Expression / p1.cXMLMessage/cXMLMessageContent/cXML that you insert manually in the Receiver Determination.
Configuring Ariba Network
You must configure Ariba Network with the information about all the instances of SAP ERP involved in the integration and link it with the Ariba Network buyer account.
Note Buying organization or service provider accounts must be enabled for Multi-ERP implementation by Ariba Network Support. The required configuration sections is not available for accounts that have not been enabled. Fore more information on Ariba Network setup, see the “Linking Multiple Business Applications” section, in Chapter 4 “Configuration”, of the Ariba Network Integration Guide.
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.
373
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, the Ariba cXML Solutions Guide and the sample mapping tables. The remainder of this section discusses the transactions on a general level as they pertain to the Ariba Network Adapter for SAP NetWeaver.
Profile Transaction When the cXML Adapter sends a ProfileRequest to Ariba Network, it responds with a ProfileResponse indicating the cXML documents that it accepts and their respective URLs. 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. By default, the cXML Adapter runs the Profile transaction as a scheduled task every 24 hours. This interval can be configured at runtime. The adapter maintains a profile cache that is updated every time the Profile transaction runs.
Purchase Order When a buying organization requests products or services through its SAP ERP system, the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On sends the cXML OrderRequest to Ariba Network. Ariba Network then routes the purchase order to the appropriate supplier using the supplier’s preferred order routing method. Note that there is no corresponding OrderResponse document. Instead, Ariba Network transmits a generic response. When the adapter sends an OrderRequest document to Ariba Network, it responds with a synchronous cXML document that contains one of the following status codes: ● 2xx, indicating that Ariba Network accepted the document. ● 4xx, indicating that a permanent error has occurred and has been logged. ● 5xx, indicating that a transient error occurred. The Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On then re-sends the document with the same payload ID for the specified number of retry attempts.
374
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
Invoice Invoices, order confirmations, 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]. For more information, see the Ariba Network Integration Guide.
Invoice Status Update Invoice status updates are sent by buying organizations to inform Ariba Network and suppliers of the status of invoice reconciliation. Buyers send StatusUpdateRequest documents to set invoice status to processing, reconciled, paying, paid, rejected, or invalid. Ariba Network posts the documents to the URL that suppliers return in their cXML ProfileResponse. InvoiceUpdateRequest documents can identify invoices in two possible ways: through either a DocumentReference or an InvoiceIDInfo element. For more information about invoice status updates, see the Ariba cXML Solutions Guide.
Testing the SAP NetWeaver for Suite Add-On Configuration This section provides instructions for how to test your configuration. To troubleshoot any errors you encounter, 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. You can also view the log files in the adapter log directory on SAP NetWeaver PI. For more information about error handling, see the Understanding Error Handling [page 376] section. Before beginning, be sure that you have at least one fully configured Ariba Network supplier relationship. For more information about creating a supplier relationship, see Chapter 4, “Configuration” in the Ariba Network Integration Guide.
Testing Processes After you have successfully deployed and configured the Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On, you must run test transactions to ensure that Ariba Network and your SAP ERP system are communicating properly in both directions. To test processes: ● Send a Purchase Order from your SAP Suite Add-On to Ariba Network. ● Run a getPending transaction by creating an invoice in Ariba Network and then sending it to your SAP Suite Add-On. 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.
375
Sending a Purchase Order for Testing Procedure 1. In your SAP ERP system which has the SAP Suite Add-On installed, create a purchase order. If the system is working properly, then the OrderRequest cXML is sent to SAP NetWeaver PI as the SAP Suite AddOn 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. 2. Verify that the messages are available in the SAP NetWeaver PI monitoring tools (PI Runtime Workbench and Integration Engine Monitor). 3. Log on to Ariba Network as the supplier. Check to see that the new order is displayed in the inbox of the supplier. If it can be found in supplier's inbox, the outbound connection is working properly.
Running a getPending Transaction for Testing Procedure 1. Create a test invoice in Ariba Network. If the system is working properly, then the cXML Adapter downloads the Invoice from Ariba Network and sends the cXML to SAP ERP. 2. Verify that the messages are available in the SAP NetWeaver PI monitoring tools (PI Runtime Workbench and Integration Engine Monitor). 3. Check to see that the invoice is created in your SAP ERP system.
Results If these two checks are successful, the inbound connection is working properly.
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, and to notify users about errors in inbound processing (getPending transaction). The following describe the error handling on the Integration server side: ● For simple transactions like Invoice: If an error occurs in the processing, the message is logged as an error in the SXMB_MONI, and can be restarted (reprocessed).
376
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
The following describe the error handling on the Adapter Engine side: ● For inbound messages (AN-> ERP), the Email notification is used to send an email when an error occurs (mainly connection issues). This is because during the pull (getPending), PI is not aware of any message. (For example, in the case of a connection issue there is no message, just a technical error in the communication layer.) ● For outbound messages (R3 -> ERP), the sending operation initiated by PI is synchronous, and if any exception occurs, it is related to a message from PI. In this case, the adapter logs a detailed message, which can be viewed with the RuntimeWork Bench. The message can be resent for processing manually (in addition to the retry mechanism implemented by PI). The adapter also sends an Email Notification in this case. The email notification is identical, except that the message is more precise and includes the response from Ariba Network, if available (for example, in case of documents refused by Ariba Network).
Understanding Error and Status Codes The cXML Adapter notification emails include an Ariba Network Adapter for SAP NetWeaver error code, and a response status code. The response status code refers to the cXML error/status codes received from the server. The cXML status codes indicate success, transient errors, or permanent errors. The status code range 2xx denotes success, 4xx denotes permanent errors, and 5xx denotes transient errors. For more information about the different cXML status codes that can be found in the notification emails, see the Protocol Specification > Response section of Chapter 2 “cXML Basics” in the cXML User’s Guide. The following table describes the possible general error codes (Ariba Network Adapter for SAP NetWeaver error codes) in cXML adapter notifications: Table 2: Application Errors: Status
ERR101
ERR102
ERR201
ERR202
ERR203
ERR204
ERR205
ERR301
Text
Invalid Configuration Parameter. Trusted certificates not installed properly. Incorrect Client Certification
Authentication Failed on ASN
ASN Internal Server Error
Send cXML to AN Failed (Invalid Request)
Send cXML to AN Failed (Temporary Error)
Send cXML to AN Failed (Unrecoverable Error)
Get Profile Transaction Failed
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.
377
Status
ERR302
ERR303
ERR401
ERR402
ERR403
ERR404
ERR405
ERR406
ERR407
Text
Get Pending Transaction Failed
Outbound Transaction Failed
Invalid Outbound Message (PI -> ASN)
Invalid Inbound Message (ASN -> PI)
Duplicate Outbound Message
Duplicate Inbound Message
Outbound Message Type Inconsistent with Channel Definition
Inbound Message Type Inconsistent with Channel Definition
Can not find corresponding record in download config file
Table 3: Runtime Error: Status
Text
ERR501
Unexpected Error
Table 4: ERP Errors: Status
ECC101
ECC102
ECC103
Text
Configuration Load Failed
IO Error
Ariba Network Not Available
Understanding Email Notifications The following are the different parts of an error notification email: ● Date: The date and time of the error. ● Error: The Ariba Network Adapter for SAP NetWeaver Error code. For a list of general error codes, see the Application Errors, Runtime Error, and ERP Errors tables in the previous section.
378
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
● Error Detail: The error detail, which can be one of the following: ○ A stack trace with the exception, if the request failed to reach Ariba Network, and the response message from Ariba Network is not available ○ Details of the cXML response, if the response from Ariba Network contains an error code. In this case, the following sections will be available. ● Transaction: The channel name corresponding to the transaction in which the error occurred, like [CC_Invoice_cXML_Sender]. ● [Request Name/Type]: The name of the request and the type related to the transaction with the error, like InvoiceDetailRequest/InvoiceDetailRequest. ● [Request URL]: The URL used for the request that failed, like https://sevice.ariba.com/service/ transaction/cxml.asp. ● [TimeStamp/PayloadID]: The timestamp and the payload of the response document, like 2007-09-04T17-23-29-07:00/[email protected] . ● [Response Status Code]: The cXML response status code, like 401. For a list of possible status messages, see the Protocol Specification > Response section of Chapter 2 “cXML Basics” in the cXML User’s Guide. ● [Response Status Text]: The text corresponding to the cXML response status code, like Unauthorized. ● [Response Status Desc]: The cXML response description “Error:Invalid sender credentials”. The problem could be one of the following: ○ Invalid, untrusted, or no certificate ○ Posting to the wrong URL when your account is configured for certificate-based authentication. Please contact customer support with the Error Reference Number: ANERR-10000000000000000000972190 for more details.
Monitoring the cXML Adapter from Runtime Workbench After you deploy the Ariba Network Adapter for SAP NetWeaver on SAP NetWeaver PI and configure the inbound and outbound transaction scenarios in the Integration Directory, communication channels are created for each inbound and outbound transaction in the Integration Directory. These communication channels are displayed within the Runtime Workbench from where an SAP NetWeaver administrator can monitor these channels. An SAP NetWeaver administrator can start or stop channels from the Runtime Workbench as required without having the need to access the Integration Directory. For example, if an administrator stops an inbound channel that downloads invoices from the Ariba Network, the channel stops to run as indicated by the status on the user interface and no invoices are downloaded.
Note If the cXML Adapter stops downloading documents from Ariba Network, the NetWeaver administrator needs to login to the Runtime Workbench and stop/start the respective channel. For example, if the adapter stops downloading invoices from Ariba Network, an administrator must login to the Runtime Workbench and start the invoice communication channel to ensure that the adapter starts downloading invoices.
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.
379
Deploying the Project When you have customized your data mappings and tested all processes, you are ready to export and then import the project as two SAP NetWeaver PI Export files (tpz files) using SAP NetWeaver PI Integration Builder. SAP NetWeaver PI Integration Builder contains two parts: ● Design tool, which contains interface objects and integration processes ● Configuration tool, which contains business services and routing rules. For more information, see the SAP NetWeaver PI documentation. The design tpz file can contain one or more namespaces, which include the integration processes, mapping objects and interface objects. The Configuration tpz file can contain one configuration scenario, which includes business services and routing rules. You can build as many tpz files as you need for one project. For more information about how to export a tpz file, see the SAP NetWeaver PI documentation. Each tpz file works as a single unit within SAP NetWeaver PI Integration Builder. For example, if you have multiple namespaces within a single Design tpz file, all the namespaces will be imported and exported at the same time, assuming that no other conditions are specified for these namespaces.
Ariba Network Certification Ariba must certify any Ariba Network Adapter for SAP NetWeaver that works with Ariba Network. Certification is the process by which Ariba’s Global Solutions Organization (GSO) inspects and approves the Ariba Network Adapter for SAP NetWeaver, the cXML documents it generates, and its connection to Ariba Network. In its default state, the Ariba Network Adapter for SAP NetWeaver is Ariba Network-certified. Once you have customized data mappings, you must perform certification testing again to ensure that all processes work as expected. For more information about the certification process, see the Ariba Network Integration Guide. The guide describes how to download certification files from Connect and provides instructions to guide you through the certification process.
Downloading the Ariba Network Integration Guide from Connect: Procedure 1. Go to (http://connect.ariba.com
) and log in.
2. On the navigation panel on the left, click
Product Info
Ariba Network
Ariba Network.
3. Under Documentation in the new page, click Supplier Connectivity to download the Supplier Connectivity.zip file.
380
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
4. Extract the IntegrationGuide.pdf file from the downloaded ZIP file.
Enabling Support for Attachments Attachments Support in cXML The cXML protocol supports the attachment of external files of any type to cXML documents. For example, buyers sometimes need to clarify purchase orders with supporting memos, drawings, or faxes. Another example is the CatalogUploadRequest document, which includes catalog files as attachments. Files referenced by cXML documents can reside either on a server accessible by the receiver or within an envelope that also includes the cXML documents themselves. To attach external files to a cXML document in a single envelope, use Multipurpose Internet Mail Extensions (MIME). The cXML document contains references to external parts sent within a multipart MIME envelope. For more information about attachments, see the cXML User’s Guide and cXML Solutions Guide. Attachments in cXML can be of any file type, such as .DOC, .PDF, .TXT., JPEG, and so on. 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.
Attachments for Outbound Documents When an outbound document (purchase order) is sent from SAP Suite Add-On to the cXML Adapter with attachments, the attachments are part of the Comments element in the cXML file as shown below: Content ID of the Attachment The attachment is embedded in the message sent from SAP Suite Add-On as a Base 64 string. The cXML Adapter converts the incoming message into a MIME message, decodes and adds the attachment to the MIME message, and sends the MIME message to Ariba Network. 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.
381
Purchase Orders with Attachments A purchase order (PO) document can have multiple attachments, such as product specifications, images, supporting memos, and so on. When Ariba Network receives a PO with attachments, Ariba Network either forwards the attachments to the respective suppliers or stores these attachments to allow online access for suppliers. These stored attachments expire after 180 days and are not available online thereafter.
Attachments for Inbound Documents Invoices with Attachments An invoice can have multiple attachments such as delivery details, emails, fax, and so on. Ariba Network adds these attachments to a mime message and sends the MIME message to the cXML Adapter for further processing. For inbound documents, the cXML Adapter supports attachments of all file types that are supported by Ariba Network. When the cXML Adapter downloads an inbound document (invoice, OC, or ASN) with attachments from Ariba Network, it receives the attachments as part of a MIME message. The cXML Adapter converts the cXML message to a message format that SAP Suite Add-On expects, encodes the attachments, and adds the attachments to the converted message. The converted message is sent to SAP Suite Add-On through SAP NetWeaver PI.
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. The endpoint in Ariba Network acts as a document routing placeholder that ensures documents from Ariba Network are sent to the desired system. You can create endpoints in Ariba Network according to your business requirements. For information about configuring endpoints for integration, see Using Endpoints for Integration [page 229].
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. SAP NetWeaver PI provides functionality to manage and administer authentication certificates and keystores. As part of this functionality, you can create keys and certificates in SAP NetWeaver and store them in the SAP NetWeaver PI Keystore. The keys and certificates that you create in SAP NetWeaver Keystore are grouped bases on views. Therefore, you first need to create a view and then create the required keys and certificates under that view. After you have created the required certificates, you must get them signed by a trusted Certificate Authority (CA) to enable Ariba Network to successfully establish the SSL connection.
382
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba Network Adapter for SAP NetWeaver for SAP Suite Add-On
As a result, when SAP NetWeaver PI sends or receives documents to/from Ariba Network, based on the channel configuration, the cXML Adapter initializes and creates the Ariba Network TrustStoreView and KeystoreView (only if client certificate is selected) and uses the certificates to ensure a successful SSL handshake.
Requirements In the communication channel for all the inbound and outbound transactions, for Trust Store View and KeyStore View (only if you are using client certificate), specify the names of the Views that store the Server certificate and Client certificate respectively. For more information, see Configuring Communication Channels to Use SAP NetWeaver PI Keystore [page 383].
Configuring Communication Channels to Use SAP NetWeaver PI Keystore Procedure 1. Open the required communication channel. 2. Under Authentication, for the Trust Store View parameter, enter the name of the view that contains the server certificate. 3. To use client certificate for authentication to Ariba Network buyer account, for Credential Mode, select Client certificate from the drop-down list. 4. For the KeyStore View parameter, enter the name of the view that contains the client certificate. 5. Click Save. 6. Repeat this configuration for all the inbound and outbound transactions.
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.
383
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. To troubleshoot any errors you encounter, 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. You can also view the log files in the adapter log directory on SAP NetWeaver PI. For more information about error handling, see the “Understanding Error Handling” [page 385] section. Before beginning, be sure that you have at least one fully configured Ariba Network supplier relationship. For more information about creating a supplier relationship, see the “Configuration” topic in the Ariba Network Integration Guide.
Testing Processes After you have successfully deployed and configured the Ariba Network Adapter for SAP NetWeaver, you should run test transactions to ensure that Ariba Network and your SAP ERP system are communicating properly in both directions. To test processes: ● Send a purchase order from your SAP system to Ariba Network. ● Run a getPending transaction by creating an invoice in Ariba Network and then sending it to your SAP system.
Sending a Purchase Order for Testing Procedure 1. In your SAP ERP system, create a purchase order. If the system is working properly, then the Purchase Order IDoc message is sent to SAP NetWeaver PI. The Ariba Network Adapter for SAP NetWeaver on SAP NetWeaver PI converts the IDoc to cXML, and then sends the cXML to Ariba Network. 2. Verify that the messages are available in the PI monitoring tools (PI Runtime Workbench and Integration Engine Monitor).
384
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter
3. Log on to Ariba Network as the supplier. Check to see that the new order is displayed in the inbox of the supplier. If it can be found in supplier's inbox, the outbound connection is working properly.
Running a getPending Transaction for Testing Procedure 1. Create a test invoice in Ariba Network. If the system is working properly, then the Ariba Network Adapter for SAP NetWeaver downloads the Invoice from Ariba Network, converts the cXML to IDoc, and then sends the IDoc to SAP ERP. 2. Verify that the messages are available in the PI monitoring tools (PI Runtime Workbench and Integration Engine Monitor). 3. Check to see that the invoice is accepted in your SAP ERP system.
Results If these two checks are successful, the inbound connection is working properly.
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, and to notify users about errors in inbound processing (getPending transaction). The following describe the error handling on the Integration server side: ● For simple transactions like Invoice: If an error occurs in the processing, or if a mapping error, or a data retrieving error (RFC calls) occurs, the message is logged as an error in the SXMB_MONI, and can be restarted (reprocessed). ● For complex/scheduled transactions (Receipt/PaymentProposal/InvoiceStatusUpdate): Messages are processed in batches, and if an error occurs, it is logged in SXMB_MONI; the processing is stopped with the timestamp of the last successfully processed message. In this case, the problem must be fixed; this guarantees that the messages are processed only once. The following describe the error handling on the adapter engine side: ● For inbound messages (AN-> ERP), the Email notification is used to send an email when an error occurs (mainly connection issues). This is because during the pull (getPending), PI is not aware of any message. (For example, in the case of a connection issue there is no message, just a technical error in the communication layer.) ● For outbound messages (ERP -> AN), the sending operation initiated by PI is synchronous, and if any exception occurs, it is related to a message from PI. In this case, the adapter logs a detailed message, which can be viewed with the RuntimeWork Bench. The message can be resent for processing manually (in addition Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
385
to the retry mechanism implemented by PI). The adapter also sends an Email Notification in this case. The email notification is identical, except that the message is more precise and includes the response from Ariba Network, if available (for example, in case of documents refused by Ariba Network).
Understanding Error and Status Codes The cXML Adapter notification emails include an Ariba Network Adapter for SAP NetWeaver error code, and a response status code. The response status code refers to the cXML error/status codes received from the server. The cXML status codes indicate success, transient errors, or permanent errors. The status code range 2xx denotes success, 4xx denotes permanent errors, and 5xx denotes transient errors. For more information about the different cXML status codes that can be found in the notification emails, see the Protocol Specification > Response section of Chapter 2 “cXML Basics” in the cXML User’s Guide. The following table describes the possible general error codes (Ariba Network Adapter for SAP NetWeaver error codes) in cXML adapter notifications: Table 5: Application Errors: Status
ERR101
ERR102
ERR201
ERR202
ERR203
ERR204
ERR205
ERR301
ERR302
ERR303
ERR401
386
Text
Invalid Configuration Parameter. Trusted certificates not installed properly. Incorrect Client Certification
Authentication Failed on ASN
ASN Internal Server Error
Send cXML to AN Failed (Invalid Request)
Send cXML to AN Failed (Temporary Error)
Send cXML to AN Failed (Unrecoverable Error)
Get Profile Transaction Failed
Get Pending Transaction Failed
Outbound Transaction Failed
Invalid Outbound Message (PI -> ASN)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter
Status
ERR402
ERR403
ERR404
ERR405
ERR406
ERR407
Text
Invalid Inbound Message (ASN -> PI)
Duplicate Outbound Message
Duplicate Inbound Message
Outbound Message Type Inconsistent with Channel Definition
Inbound Message Type Inconsistent with Channel Definition
Can not find corresponding record in download config file
Table 6: Runtime Error: Status
Text
ERR501
Unexpected Error
Table 7: ERP Errors: Status
ECC101
ECC102
ECC103
Text
Configuration Load Failed
IO Error
Ariba Network Not Available
Understanding Email Notifications The following are the different parts of an error notification email: ● Date: The date and time of the error. ● Error: The Ariba Network Adapter for SAP NetWeaver Error code. For a list of general error codes, see the Application Errors, Runtime Error, and ERP Errors tables in the previous section. ● Error Detail: The error detail, which can be one of the following: ○ A stack trace with the exception, if the request failed to reach Ariba Network, and the response message from Ariba Network is not available ○ Details of the cXML response, if the response from Ariba Network contains an error code. In this case, the following sections will be available. ● Transaction: The channel name corresponding to the transaction in which the error occurred, like [CC_Invoice_cXML_Sender]. Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
387
● [Request Name/Type]: The name of the request and the type related to the transaction with the error, like InvoiceDetailRequest/InvoiceDetailRequest. ● [Request URL]: The URL used for the request that failed, like https://sevice.ariba.com/service/ transaction/cxml.asp. ● [TimeStamp/PayloadID]: The timestamp and the payload of the response document, like 2007-09-04T17-23-29-07:00/[email protected] . ● [Response Status Code]: The cXML response status code, like 401. For a list of possible status messages, see the Protocol Specification > Response section of Chapter 2 “cXML Basics” in the cXML User’s Guide. ● [Response Status Text]: The text corresponding to the cXML response status code, like Unauthorized. ● [Response Status Desc]: The cXML response description “Error:Invalid sender credentials”. The problem could be one of the following: ○ Invalid, untrusted, or no certificate ○ Posting to the wrong URL when your account is configured for certificate-based authentication. Please contact customer support with the Error Reference Number: ANERR-10000000000000000000972190 for more details.
Monitoring of the cXML Adapter The monitoring of the cXML Adapter includes a monitoring capability that continuously monitors the status of the deployed inbound and outbound channels (transactions). As part of this implementation, if a channel stops or is stuck in processing, the monitoring capability of the adapter is notified and it automatically restarts that channel without any manual intervention. For example, if invoices are not getting downloaded from Ariba Network, the monitoring capability checks the status of the invoice channel. If the channel has stopped or is stuck in processing, the monitoring capability restarts the channel to ensure that the adapter can continue to download invoices from Ariba Network.
Monitoring the cXML Adapter from Runtime Workbench After you deploy the Ariba Network Adapter for SAP NetWeaver on SAP NetWeaver PI and configure the inbound and outbound transaction scenarios in the Integration Directory, communication channels are created for each inbound and outbound transaction in the Integration Directory. These communication channels are displayed within the Runtime Workbench from where an SAP NetWeaver administrator can monitor these channels. An SAP NetWeaver administrator can start or stop channels from the Runtime Workbench as required without having the need to access the Integration Directory. For example, if an administrator stops an inbound channel that downloads invoices from the Ariba Network, the channel stops to run as indicated by the status on the user interface and no invoices are downloaded.
Note If the cXML Adapter stops downloading documents from Ariba Network, the NetWeaver administrator needs to login to the Runtime Workbench and stop/start the respective channel. For example, if the adapter stops downloading invoices from Ariba Network, an administrator must login to the Runtime Workbench and start the invoice communication channel to ensure that the adapter starts downloading invoices.
388
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter
Deploying the Project When you have customized your data mappings and tested all processes, you are ready to export and then import the project as two SAP NetWeaver PI Export files (tpz files) using SAP NetWeaver PI Integration Builder. SAP NetWeaver PI Integration Builder contains two parts: ● Design tool, which contains interface objects, mapping objects and integration processes ● Configuration tool, which contains business services and routing rules. For more information, see the SAP NetWeaver PI documentation. The design tpz file can contain one or more namespaces, which include the integration processes, mapping objects and interface objects. The Configuration tpz file can contain one configuration scenario, which includes business services and routing rules. You can build as many tpz files as you need for one project. For more information about how to export a tpz file, see the SAP NetWeaver PI documentation. Each tpz file works as a single unit within SAP NetWeaver PI Integration Builder. For example, if you have multiple namespaces within a single Design tpz file, all the namespaces will be imported and exported at the same time, assuming that no other conditions are specified for these namespaces.
Ariba Network Certification Ariba must certify any Ariba Network Adapter for SAP NetWeaver that works with Ariba Network. Certification is the process by which Ariba’s Global Solutions Organization (GSO) inspects and approves the Ariba Network Adapter for SAP NetWeaver, the cXML documents it generates, and its connection to Ariba Network. In its default state, the Ariba Network Adapter for SAP NetWeaver is Ariba Network-certified. Once you have customized data mappings, you must perform certification testing again to ensure that all processes work as expected. For more information about the certification process, see the Ariba Network Integration Guide. The guide describes how to download certification files from Connect and provides instructions to guide you through the certification process.
Downloading the Ariba Network Integration Guide from Connect Procedure 1. Go to (http://connect.ariba.com
) and log in.
2. On the navigation panel on the left, click
Product Info
Ariba Network
Ariba Network.
3. Under Documentation in the new page, click Supplier Connectivity to download the Supplier Connectivity.zip file. Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
389
4. Extract the IntegrationGuide.pdf file from the downloaded ZIP file.
390
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Testing the Adapter
cXML Adapter Parameters
This section describes common, inbound, and outbound parameters for the cXML Adapter. Common Parameters [page 391] Inbound Parameters [page 393] Outbound Parameters [page 395] Configuring Retry Attempts [page 395] Configuring Proxy Server Parameters [page 395]
Common Parameters Parameter Name
Usage Type
Data Type
Value
Description
Adapter Status
Mode
required
string
Test/ Production
Status
required
string
Active/ Inactive
Credential Mode
required
string
Shared secret/ Client certificate
Credential Domain
required
string
NetworkId/ NetworkUserI d/DUNS
Credential
required
string
Deployment mode of the adapter. Default value: Test
The status of the adapter. Default value: Active
Authentication Authentication method on Ariba Network. Default value: Client certificate
The domain for the Buyer's credential. Default value: NetworkId
The Buyer's credential on Ariba Network. The value can be NetworkId,
NetworkUserId or DUNS, depending on the credential domain selected.
Shared Secret Password
optional
Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters
string
The Buyer's shared secret on Ariba Net work. This parameter is only required when parameter credentialMode is set as Shared secret.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
391
Parameter Name
Port
Usage Type
required
Data Type
Value
Description HTTPS port. This parameter is only required when parameter credentialMode is set
integer
as Client certificate. Default value: 443
KeyStore View
Indicates the name of the view that contains all the keys/certificates required for authen tication between the cXML Adapter and Ariba buyer.
required
string
AN ID
required
string
User Agent
required
string
Language
required
string
Data Directory
required
string
cXML Version
required
string
1.2.018 or higher
Use XML Validation
optional
boolean
true/false
Use SAP Add on Suite
required
boolean
documentExp iryPeriod
required
integer
cXML Configuration Ariba Network ID. Default value: AN01000000001 A textual string representing the client sys tem that is conducting the cXML conversa tion. Default value: Ariba SN Buyer
en-US
Attribute needed for constructing cXML re quest. Default value: en-US Base directory needed to run the adapter. Default value: D:/AribaDataDir
The version number of the cXML document data definition to be used to generate the cXML documents exchanged with Ariba Network. This version number will be used in the DOCTYPE entity of the cXML docu ments. A flag that specifies whether or not the vali dation is done on the exchanged cXML documents according to the cXML dtds. The validation should be enabled during the in stallation/ customization phase to ensure that the exchanged cXML documents are compliant. In the production phase, the vali dation could have a negative impact on per formance. When this option is enabled, the cXML Adapter integrates Ariba Network with the SAP Suite AddOn component available in your SAP ERP system.
minimum 1 and max 360
Specify the expiry time for a document in hours after which the document can be re sent from or to Ariba Network . The default value is 24 hours. You can set a minimum value of one hour and the maximum value as 360 hours.
Email Notification
392
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters
Parameter Name
Usage Type
Data Type
Value
Use Email Notificatio ns
required
boolean
SMTP Server Host
required
string
Sender Address
required
string
Recipient Address
required
string
CC Address
optional
string
Sender Name
required
string
Description
true/false
A switch to turn on/off email notification. Default value: false
The SMTP server IP address or host name.
The email account for sending email.
The email account for email receiver.
The email account for email cc receiver.
The description name for sender. Default value: AribaSN Adapter
Admin Email Authenticat ion
required
boolean
User
optional
string
Password
optional
string
true/false
A flag that represents whether or not the email server requires authentication for sending email. Default value: false The email sender account. This parameter is only required when parameter emailAuthentication is set as true. The password for the email sending ac count. This parameter is only required when parameter emailAuthentication is set as true.
Inbound Parameters Parameter Name
Usage Type
Data Type
Value
Description
cXML Configuration
GetProfil e URL
required
string
Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters
URL used to send ProfileRequest. Default value: https://
certservice.ariba.com/ service/transaction/ cxml.asp
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
393
Parameter Name
Usage Type
Data Type
Value
Description
GetProfil e Interval (Minutes)
required
intege r
Poll interval of profileRequest ex pressed in minutes. Default value: 60
GetPendin g Interval (Minutes)
required
intege r
Poll interval of getPendingRequest ex pressed in minutes. Default value: 15
Max Documents in GetPendin g
required
intege r
StatusUpd ateReques tRetryCou nt
required
intege r
StatusUpd ateReques tRetryInt erval (Minutes)
required
intege r
SystemID for GetPendin g
optional
string
Max number of Documents that can be received from the pending queue in a single getPending request. Default value: 2
Number of times the status update re quest is to be retried if the first status update request failed. Default value: 0 Time to wait before sending the next status update, expressed in minutes. Default value: 0
The system ID for your ERP appli cation
This parameter is required only if you are using multiple ERP applications to connect to Ariba Network The system ID for your ERP system must match the system ID configured in your Ariba Network buyer account.
Timeout
required
intege r
5 minutes
When the cXML Adapter is download ing documents from Ariba Network, if the connection is lost during the download, the cXML adapter will wait for the number of minutes specified as the value for this parameter before ex iting.
Inbound Request Type
Inbound Request Type
394
required
string
One of the following:
ConfirmationRequest InvoiceDetailRequest ShipmentNoticeRequest PayMeNowRequest
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
The request type for Inbound. Default value:
ConfirmationRequest
Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters
Outbound Parameters Parameter Name
Usage Type
Data Type
Value
Description
cXML Configuration
GetProfile URL
required
URL used to send ProfileRequest. Default value: https://
string
certservice.ariba.com/ service/transaction/ cxml.asp GetProfile Interval (Minutes)
required
intege r
required
string
Poll interval of profileRequest ex pressed in minutes. Default value: 60
Outbound Request Type
Outbound Request Type
One of following:
OrderRequest ChangeOrderReques t InvoiceUpdateRequ est PaymentRequest PaymentRemittance Request
The request type for Outbound. Default value: OrderRequest
Configuring Retry Attempts You can configure the interval and the number of times the adapter framework will attempt to resend a message to an adapter from the NetWeaver Administrator. This includes the interval between retry attempts for outbound messages sent by SAP NetWeaver PI to the cXML adapter, and the number of inbound documents sent by the cXML adapter to PI. For more information on how to configure a message to be retried, see the SAP NetWeaver Process Integration 7.1 documentation.
Configuring Proxy Server Parameters The Ariba Network Adapter for SAP NetWeaver can be configured to use Secure HyperText Transfer Protocol (HTTPS) through a proxy server. The following methods of authentication on the proxy server are supported: ● Basic ● Digest ● NTLMv1 (Note that NTLMv2 is not supported) Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
395
To enable secure communication through a proxy server, configure the following parameters for the cXML Adapter: Parameter Name
Type
Value
No (default) Yes
Description Enables or disables the use of the proxy server for remote communication with Ariba Network
Use Proxy Server
Boolean
Proxy Server Host
String
Host name or IP address of the proxy server
Proxy Server Port
Integer
Port used by the proxy server to handle secure communication
Proxy Authentication Method
List
None (default) Basic Digest NTLM
Indicates the method used for authenti cation on the proxy server. If None, the proxy server does not require authenti cation. Note that NTLMv2 is not supported.
Username
String
The user name used for authentication. Required for all three authentication methods.
Password
String
The password used for authentication. Required for all three authentication methods.
Domain
String
The domain to which the user identified by the Username parameter belongs. Required for NTLM authentication only.
396
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide cXML Adapter Parameters
Ariba SAP Objects
This appendix describes the SAP development objects provided by Ariba as part of the SAP integration. The audience for this appendix includes: ● BASIS administrators who import Ariba’s SAP transports and need to see the list of objects they are importing. ● ABAP developers who are responsible for customizing the Ariba SAP objects. SAP Certification [page 397] /ARBA/COMMON_OBJECTS Package [page 398] /ARBA/PURCHASEORDER Package [page 400] /ARBA/CHANGEPURCHASEORDER Package [page 401] /ARBA/ERPINVOICE Package [page 402] /ARBA/INVOICESTATUSUPDATE Package [page 403] /ARBA/PAYMENTPROPOSAL Package [page 404] /ARBA/RECEIPT Package [page 405] /ARBA/REQUISITION Package [page 405]
SAP Certification The SAP code delivered by Ariba is certified by SAP. As part of this certification, a new namespace called /ARBA/ is registered and all SAP objects delivered by Ariba are renamed from Z_ to /ARBA/. For example, the function module called Z_ARIBA_INVOICE_STATUS_UPDATE is renamed to /ARBA/ INVOICE_STATUS_UPDATE. The SAP NetWeaver PI content is changed by importing the RFCs and ABAP objects renamed with the /ARBA/ namespace into SAP NetWeaver PI.
Note Starting Ariba Cloud Integration Release 1.0, all the RFC and SAP objects have been renamed to /ARBA/ namespace. You cannot edit the main code without an access key from the SAP marketplace. However, you can customize the code using the BADI hooks in the program that Ariba provides you for customization.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
397
/ARBA/COMMON_OBJECTS Package The /ARBA/COMMON_OBJECTS package contains Ariba development objects for Ariba Network Adapter for SAP NetWeaver for SAP NetWeaver objects.
Function Groups and Modules The following are the function groups in the /ARBA/COMMON_OBJECTS package: Table 8: /ARBA/COMMON_OBJECTS Function Groups Function Group
/ARBA/LOOKUP
/ARBA/TABLE_MAIN
Description Lookup Function Modules
Extended Table Maintenance (Generated)
Table 9: /ARBA/COMMON_OBJECTS Function Modules Description
Function Module
External access to R/3 tables via RFC
/ARBA/RFC_READ_TABLE
Retrieves pre-filtering restrictions
/ARBA/PREFILTER_ADAPTER
/ARBA/WHERE_CONDITION_FILTER
/ARBA/ORBIAN_INFO_GETDETAIL
Ariba function to construct where condition
Payment Proposal ID for Orbian Integration
Read BSIK and BKPF data
/ARBA/READ_BSIK_BKPF
Tables The following are the tables for the /ARBA/COMMON_OBJECTS package: Table 10: /ARBA/COMMON_OBJECTS Tables Table
Description
/ARBA/AN_VENDOR
398
Ariba Network Vendor Table
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects
Table
Description Ariba table to store configurable parameters
/ARBA/PARAM_TAB
Stores invoices created in ERP and which are sent to AN
/ARBA/AN_ERPINV
Tables read by /ARBA/RFC_READ_TABLE Function Module
/ARBA/LOOKUPTAB
Table to store Proxy Parameters for ISU, PP, ERP Invoice, and Receipts
/ARBA/PROXYPARAM
Note The ABAP function /ARBA/invoice_get_details is designed to use the vendors from the /ARBA/ AN_VENDOR table while selecting data for invoice details. Use the SM30 transaction to generate table maintenance objects to maintain records in this table. You must maintain the following entries in the /ARBA/PARAM_TAB table using Transaction SM30: Variable Name
Field Name
Sign
OPTION
Select Value
GROSS_INV_RECEIPT
B~BLART
I
EQ
RE
NONPO_INVOICE
B~BLART
I
EQ
KR
PAYMENT_POSTING
BLART
I
EQ
KP
VENDOR_PAYMENT
BLART
I
EQ
KZ
VENDOR_PAYMENT
B~BLART
I
EQ
KZ
VENDOR_PAYMENT
H~BLART
I
EQ
KZ
ACCRUAL_TAX_CONDITION
MW1
I
EQ
MW1
ACCRUAL_TAX_CONDITION
MW2
I
EQ
MW2
You must maintain the following entries in the /ARBA/AN_VENDOR table using Transaction SM30: Fieldname
Value
BUKRS
3000
LIFNR
1000
You must maintain the following entries in the /ARBA/TAXCAT_MAP table using Transaction SM30: Fieldname
Value
MWSKZ
I1
TAX_CATEGORY
Sales Tax
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
399
Structures The following are the structures for the /ARBA/COMMON_OBJECTS package: Table 11: /ARBA/COMMON_OBJECTS Structures Structure
/ARBA/WTAB
/ARBA/RFC_READ_TABLE
Description Table Structure for "WHERE (itab)" Statement
Structure to support RFC READ TABLE for Unicode Systems
/ARBA/PURCHASEORDER Package Function Group
/ARBA/PURCHASEORDER
Function Module Name
/ARBA/PO_ACCOUNTING_INFO
/ARBA/PO_SERVICE_INFO
Description Purchase Order Adapter Objects
Description Accounting Information for PO
Service Purchase Order Details
Structure Name
Description
/ARBA/EKKN
Purchase Order Accounting Details
/ARBA/EKKN_SERVICE
Purchase Order Account Assignment Structure
/ARBA/EKPO
Purchase Order Line Item Details
/ARBA/EKPO_SERVICE
Service Line item Details
/ARBA/ESKL
Purchase Order Account Assignment Service Line
/ARBA/ESLH
Purchase Order Header Service Structure
/ARBA/ESLL
Purchase Order Service Line item Detail
Table Type
Description
/ARBA/EKKN_SERVICE_T
Table Type For Service Purchase Order Accounting Details
/ARBA/EKKN_T
Table Type For Purchase Order Accounting Detail
400
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects
Table Type
Description
/ARBA/EKPO_SERVICE_T
Table Type For Service Line Item Details
/ARBA/EKPO_T
Table Type For Purchase Order Line Item Detail
/ARBA/ESKL_T
Table Type - Purchase Order Account Assignment Service Line
/ARBA/ESLH_T
Table Type For Purchase Order Header Service Structure
/ARBA/ESLL_T
Table Type For Purchase Order Service Line item Detail
/ARBA/RFC_DB_FLD_T
Table Type For Field Names
/ARBA/TAB512_T
Table Type for 512 Byte Field Structure
/ARBA/CHANGEPURCHASEORDER Package Function Group
/ARBA/CHANGEPURCHASEORDER
Function Module Name
/ARBA/PO_GET_DETAIL
Description Change Purchase Order
Description Change Purchase Order Get Detail
Structure Name
Description
/ARBA/BAPIEKKOL
Transfer Structure: Display/List: PO Header with Vendor Name
/ARBA/BAPIEKPO
Transfer Structure: Display/List PO Item
/ARBA/BAPIEKKN
Transfer Structure: Display/List: PO Account Assignment
/ARBA/BAPIESKL
Communication Structure: Account Assignment Values: Service Line
/ARBA/BAPIESLL
Communication Structure: Service Line
Table Type
Description
/ARBA/BAPIEKET_T
Purchase Order Schedule Lines
/ARBA/BAPIEKKN_T
Purchase Order Accounting Details
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
401
Table Type
Description
/ARBA/BAPIEKPO_T
Transfer Structure: Display/List PO Item
/ARBA/BAPIESKL_T
Service Purchase Order Account Assignment Details
/ARBA/BAPIESLL_T
Service Purchase Order Detail
/ARBA/PO_ACCOUNT_T
Ariba Purchase Order Accounting Details
/ARBA/PO_ITEMS_T
Ariba Purchase Order Items
/ARBA/PO_SERVICEACCOUNT_T
Purchase Order Service Account Details
/ARBA/PO_SERVICEITEMS_T
Ariba Service Purchase Order Item Detail
/ARBA/ERPINVOICE Package Function Group
Description
/ARBA/ERPINVOICE
ERP Invoice Adapter objects
Function Module Name
Description
/ARBA/INVOICE_GET_DETAILS
Ariba Invoice FI documents to AN
Program Name
Description
/ARBA/ERPINVOICE_EXPORT
ABAP proxy for Invoice Interface
Table Name
Description
/ARBA/TAXCAT_MAP
Ariba Tax code to Tax Category Map
Structure Name
Description
/ARBA/INVOICE_HEADER_DETAILS
Ariba ERP Initiated Invoice Header details
/ARBA/INVOICE_LINE_DETAILS
Ariba ERP Initiated Invoice line item details
/ARBA/BSEG
ERP Invoice Line Item Details
/ARBA/BSIK
ERP Invoice Header Details
/ARBA/BSET
Invoice Tax Data
Table Type
Description
/ARBA/INVOICE_HEADER_DETAILS_T
Invoice Header details
402
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects
Table Type
Description
/ARBA/INVOICE_LINE_DETAILS_T
Invoice line item details
/ARBA/BSEG_T
ERP Invoice Line Item Details
/ARBA/BSIK_T
Invoice Details
/ARBA/BSET_T
Invoice Tax Data
/ARBA/INVOICESTATUSUPDATE Package Function Group
Description
/ARBA/INVOICESTATUSUPDATE
Invoice Status Update function group
Function Module Name
Description
/ARBA/INVOICE_STATUS_UPDATE
Ariba Invoice status update
Program Name
Description
/ARBA/INVSTATUPDT_EXPORT
Program for Calling Invoice Status Update proxy
Structure Name
Description
/ARBA/CONTROL_RECORD
IDOC Control Record for Rejected Status Invoices
/ARBA/DATA_RECORD
IDOC Data Record for Rejected Status Invoices
/ARBA/FULL_PAID_INVOICE
Fully Paid Invoices
/ARBA/INVOICE
Invoice Detail Structure
/ARBA/INVOICE_STATUS
Structure for Invoice status update
/ARBA/PARTIAL_PAYMENTS
Partial Payment Details
/ARBA/PARTIAL_PAID_INVOICE
Partially Paid Invoice Details
/ARBA/REVERSED_INVOICE
Invoice Status Update Reversal Documents
/ARBA/REVERSED_PAYMENTS
Reversed Payments Details
Table Type
Description
/ARBA/CONTROL_RECORD_T
IDOC Control Record for Rejected Status Invoices
/ARBA/DATA_RECORD_T
IDOC Data Record for Rejected Status Invoices
/ARBA/FULL_PAID_INVOICE_T
Fully Paid Invoices
/ARBA/INVOICE_T
Invoice Detail Structure
/ARBA/INVOICE_STATUS_T
Structure for Invoice status update
/ARBA/PARTIAL_PAYMENTS_T
Partial Payment Details
/ARBA/PARTIAL_PAID_INVOICE_T
Partially Paid Invoice Details
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
403
Table Type
Description
/ARBA/REVERSED_INVOICE_T
Reversed Invoices
/ARBA/REVERSED_PAYMENTS_T
Reversed Payments
/ARBA/PAYMENTPROPOSAL Package Function Group
Description
/ARBA/PAYMENTPROPOSAL
Payment Proposal Adapter Objects
Function Module Name
Description
/ARBA/PAYMENT_PROPOSAL
Payment Proposal RFC
Program Name
Description
/ARBA/PAYMENTPROPOSAL_EXPORT
Payment Proposal Program (Proxy)
Structure Name
Description
/ARBA/ACCOUNTINGDOCUMENT
Payment Proposal Accounting Data
/ARBA/PARTIALINVOICE
Invoice Detail Structure For Payment Proposal Customer Exit
/ARBA/PARTIALPAYMENTS
Partial Payment Structure For Payment Proposal Customer Exit
/ARBA/PAYMENTPROPOSAL
Ariba Customer Exit for Payment Proposal Information
/ARBA/PAYMENT_PROPOSAL
Structure used in payment proposal RFC Ariba adapter
/ARBA/PAYEE
Structure for payment proposal payee
/ARBA/PAYER
Structure for payment proposal payer
/ARBA/REC_BANK
Payment Proposal Bank Details
Table Type
Description
/ARBA/ACCOUNTINGDOCUMENT_T
Payment Proposal Accounting Data
/ARBA/PARTIALINVOICE_T
Partial Invoice Details
/ARBA/PARTIALPAYMENTS_T
Payment Proposal Partial Payments
/ARBA/PAYMENTPROPOSAL_T
Payment Proposal
/ARBA/PAYMENT_PROPOSAL_T
Payment Proposal
/ARBA/PAYEE_T
Payment proposal payee
/ARBA/PAYER_T
Payment proposal payer
/ARBA/REC_BANK_T
Payment Proposal Bank Details
404
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects
/ARBA/RECEIPT Package Program Name
Description
/ARBA/RECEIPT_PUBLISH
Proxy for Receipt Export
Structure Name
Description
/ARBA/PO_DETAIL
Ariba Purchase Order Detail Structure
/ARBA/RECEIPT
Ariba Material Document Structure
Table Type
Description
/ARBA/PO_DETAIL_T
Ariba Purchase Order Detail Structure
/ARBA/RECEIPT_T
Ariba Material Document
/ARBA/GR_HEADER_T
Goods Receipt Header
/ARBA/GR_ITEMS_T
Goods Receipt Items
/ARBA/REQUISITION Package Function Group
Description
/ARBA/REQPARAM
Extended Table Maintenance (Generated)
Program Name
Description
/ARBA/REQUISITION_EXPORT
Requisition Export (Proxy)
Table Name
Description
/ARBA/REQPARAM
Table to store Ariba Requisition Parameters
Structure Name
Description
/ARBA/REQUISITION
Requisition Details
Table Type
Description
/ARBA/REQUISITION_T
Requisition
Ariba Network Adapter for SAP NetWeaver Setup Guide Ariba SAP Objects
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
405
Revision History
The following table provides a brief history of the updates to this guide. Ariba updates the technical documentation for its On Demand solutions if ● software changes delivered in service packs or hot fixes require a documentation update to correctly reflect the new or changed functionality; ● the existing content is incorrect or user feedback indicated that important content is missing. Ariba reserves the right to update its technical documentation without prior notification. Most documentation updates will be made available in the same week as the software service packs are released, but critical documentation updates may be released at any time. Document Version
Month/Year of Update
Updated Chapter/ Section
1
September 2015
n/a Multiple Chapters
Short Description of Change
●
Reset revision history for Cloud Integration Release 6.0.
Ariba Cloud Integration Release 6.0 ●
Updated throughout for the Ariba Cloud Integration Release 6.0.
2
3
4
October 2015
November 2015
December 2015
Integration of Cata log Data in SAP ERP and Ariba Net work
●
Removed the limitation on transactional data that is no longer applicable.
Service Sheet and Service Sheet Re sponse Integration Scenario
●
Updated the integration scenario for Service Sheet and Service Sheet Response.
Integration of Cata Updated section log Data in SAP ERP and Ariba Net work Change Purchase Order Implementa tion Redesigned
Updated the section as this is available only for customers using Ariba Cloud Integration 4.0 and earlier.
Configuring the In terface Determina tion Settings for the Sourcing Award to Contract Integration Sce nario
Updated the task with the results and example section.
Configuring Implicit Updated the code in Step 12. Enhancements for New Service Or ders
406
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Ariba Network Adapter for SAP NetWeaver Setup Guide Revision History
Important Disclaimers and Legal Information
Coding Samples Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.
Accessibility The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).
Ariba Network Adapter for SAP NetWeaver Setup Guide Important Disclaimers and Legal Information
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
407
www.ariba.com
Copyright © 1996–2015 Ariba, Inc. All rights reserved. This documentation, as well as the Ariba solutions, software and/or services described in it, contain proprietary information. They are provided under a license or other agreement containing restrictions on use and disclosure and are also protected by copyright, patent and/or other intellectual property laws. Except as permitted by such agreement, no part of the document may be reproduced or transmitted in any form by any means, electronic, mechanical or otherwise, without the prior written permission of Ariba, Inc. Ariba, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in the documentation. The information contained in the documentation is subject to change without notice. Ariba and Ariba products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Ariba, Inc. in the United States and other countries. Please see http://www.ariba.com/legal/trademarks for additional trademark information and notices. Ariba Sourcing solutions (On Demand and software) are protected by one or more of the following patents, including without limitation: U.S. Patent Nos. 6,199,050; 6,216,114; 6,223,167; 6,230,146; 6,230,147; 6,285,989; 6,408,283; 6,499,018; 6,564,192; 6,871,191; 6,952,682; 7,010,511; 7,072,061; 7,130,815; 7,146,331; 7,152,043;7,225,152; 7,277,878; 7,249,085; 7,283,979; 7,283,980; 7,296,001; 7,346,574; 7,383,206; 7,395,238; 7,401,035; 7,407,035; 7,444,299; 7,483,852; 7,499,876; 7,536,362; 7,558,746; 7,558,752; 7,571,137; 7,599,878; 7,634,439; 7,657,461; 7,693,747; 8,364,577; and 8,392,317. Patents pending. Other Ariba product solutions are protected by one or more of the following patents: U.S. Patent Nos. 6,199,050, 6,216,114, 6,223,167, 6,230,146, 6,230,147, 6,285,989, 6,408,283, 6,499,018, 6,564,192, 6,584,451, 6,606,603, 6,714,939, 6,871,191, 6,952,682, 7,010,511, 7,047,318, 7,072,061, 7,084,998; 7,117,165; 7,225,145; 7,324,936; 7,536,362; 8,364,577; and 8,392,317. Patents pending. Certain Ariba products may include third party software or other intellectual property licensed from a third party. For information regarding software or other intellectual property licensed from a third party, go to http://www.ariba.com/copyrights.cfm.