Sap Ariba Cloud Integration Gateway Migration Guide 1g205o

CONFIDENTIAL 2018-09

© 2018 SAP SE or an SAP company. All rights reserved.

SAP Ariba Cloud Integration Gateway migration guide For buyers 2018.09

THE BEST RUN

Content

1

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1

ed systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 SAP ERP and SAP S/4HANA systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Add-on for SAP ERP and SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Software components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 ed languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

2

ed SAP Ariba Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3

High-level steps about migrating from Ariba cloud integration adapter to SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4

Prerequisites for migrating transactions to SAP Ariba Cloud Integration Gateway. . . . . . . . . . 13

4.1

Securing inbound data transfer from SAP Ariba Cloud Integration Gateway to the on-premise SAP ERP system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.2

Maintaining certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.3

Prerequisite for migrating master data and catalog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Removing data from specific database tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 How to deactivate event type linkages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 How to remove the HR-CA event linkages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.4

Prerequisites for migrating the invoice status update transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.5

Prerequisites for migrating the product activity message transaction. . . . . . . . . . . . . . . . . . . . . . . . 17

4.6

Prerequisites for migrating the purchase order transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.7

Prerequisites for migrating the advance payment transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.8

Prerequisites for migrating the product activity message transaction. . . . . . . . . . . . . . . . . . . . . . . . 18 How to remove a BAdI implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

5

Migrating to SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5.1

About migrating data from the /ARBA/ database table to the ARBCIG_ database table. . . . . . . . . . . 20 How to migrate data to the new database table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

5.2

About migrating the configurations of transactions from SAP ERP to SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 How to migrate the configurations of transactions from SAP ERP to SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

5.3

About migrating SAP Ariba BAdIs to SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . . . .27

5.4

About SAP Ariba BAdIs you want to migrate manually to SAP Ariba Cloud Integration Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5.5

What's Next?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

How to migrate SAP Ariba BAdIs to SAP Ariba Cloud Integration Gateway. . . . . . . . . . . . . . . . . .30

2

CONFIDENTIAL

SAP Ariba Cloud Integration Gateway migration guide Content

6

Post-migration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

6.1

ing attachments and comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

6.2

Modifying partner profile settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 How to modify partner profile settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

6.3

Configuring event linkages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

6.4

Configuring logical ports and service names for transactions performed using web services proxies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

6.5

Migrating advanced ship notice, dispatch delivery notification, and component ship notice transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

6.6

Creating a table to map values of pricing condition parameters in SAP Ariba Cloud Integration Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

7

Modifications to transactions ed by Ariba Network. . . . . . . . . . . . . . . . . . . . . . . . . . . 41

7.1

Purchase order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 How to remove the implicit enhancement for configuring new purchase orders. . . . . . . . . . . . . . 43 Code used in INCLUDE ZXM06U02 for the existing integration. . . . . . . . . . . . . . . . . . . . . . . . . 45 Code used in INCLUDE ZXM06U33 for the existing integration. . . . . . . . . . . . . . . . . . . . . . . . . .45

7.2

Scheduling agreement release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Code used in INCLUDE ZXM06U59 and INCLUDE ZXM06U60 for the existing integration. . . . . . 46

7.3

Order confirmation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Code used in INCLUDE ZXM06U19 for the existing integration. . . . . . . . . . . . . . . . . . . . . . . . . . 47 Code used in INCLUDE ZXM06U20 for the existing integration. . . . . . . . . . . . . . . . . . . . . . . . . 48

7.4

Invoice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Code used in INCLUDE ZXM08U22 for the existing integration. . . . . . . . . . . . . . . . . . . . . . . . . .49 Code used in INCLUDE ZXM08U25 for the existing integration. . . . . . . . . . . . . . . . . . . . . . . . . .50 Code used in INCLUDE ZXM08U26 for the existing integration. . . . . . . . . . . . . . . . . . . . . . . . . .52

7.5

ERP-initiated invoice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Code used in INCLUDE /ARBA/INCL_INVOICE_GET_DETAILS for the existing integration. . . . . . 55 Code used in INCLUDE ZX050U01 for the existing integration. . . . . . . . . . . . . . . . . . . . . . . . . . 56 Code used in INCLUDE ZX050U07 for the existing integration. . . . . . . . . . . . . . . . . . . . . . . . . . 56

7.6

Invoice status update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

7.7

Payment proposal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

7.8

Payment remittance request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 How to implement the customer exit for payment remittance to fill data into custom segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

7.9

Remittance advice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

7.10

Service sheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

7.11

Service sheet response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

7.12

Liability transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

7.13

Component consumption request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

7.14

Component acknowledgment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

7.15

Ship notice request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63


CONFIDENTIAL

3

7.16

Product activity message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

7.17

Product replenishment message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

8

Modifications to transactions ed by SAP Ariba Strategic Sourcing solutions. . . . . . . . 65

8.1

Request for quotation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Code used in INCLUDE ZXM06U02 for the existing integration. . . . . . . . . . . . . . . . . . . . . . . . . .67 Code used in INCLUDE ZXM06U33 for the existing integration. . . . . . . . . . . . . . . . . . . . . . . . . .68

9

Modifications to transactions ed by SAP Ariba Procurement solutions. . . . . . . . . . . . 69

9.1

Purchase order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

9.2

Goods receipt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

9.3

Service entry sheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

9.4

Invoice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

9.5

Advance payment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

9.6

Payment remittance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

10

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

11

Revision history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4

CONFIDENTIAL


1

Introduction

As an existing customer, you can use Ariba Network adapter for SAP NetWeaver to integrate Ariba Network and SAP Ariba Strategic Sourcing solutions with SAP ERP or SAP S/4HANA systems. You can also use SAP Ariba Procurement solutions integrated with SAP ERP or SAP S/4HANA. SAP Ariba Cloud Integration Gateway is an alternative method to integrate Ariba Network, SAP Ariba Strategic Sourcing solutions, and SAP Ariba Procurement solutions with SAP ERP or SAP S/4HANA. SAP Ariba Cloud Integration Gateway is a self-service gateway that provides a simple and efficient integration solution. You can configure SAP Ariba Cloud Integration Gateway in your environment as: ● a common integration solution for integrating Ariba Network, SAP Ariba Strategic Sourcing solutions, and SAP Ariba Procurement solutions with SAP ERP or SAP S/4HANA. This helps you avoid using multiple integration solutions. ● an integration solution that you can use along with the existing integration solutions in your environment SAP Ariba Cloud Integration Gateway offers the following technical benefits: ● s the configuration on the basis of the core ERP capabilities ● s certificate-based or basic name and based authentication for connectivity ● Offers tools such as: ○ Transformation Tool to transform and data ○ Schema Validation Tool to easy validation and ensure accuracy and acceptability of data ○ Transaction Tracker to search and track transaction status ○ Test Central to help s perform self-test before moving to a production environment SAP Ariba Cloud Integration Gateway offers the following functional benefits: ● Simplifies integration by using a guidance-based setup ● Reduces the integration deployment time ● Provides an integrated test framework to various scenarios configured in the system ● Facilitates smoother upgrade of the solution ● Aligns with SAP standard software delivery processes by ing through the SAP Service Marketplace and by addressing issues with standard SAP Notes and correction instructions ● Uses the single sign-on functionality to enable buyers to access their SAP Ariba Cloud Integration Gateway from their Ariba Network If you have decided to integrate SAP Ariba solutions with SAP ERP or SAP S/4HANA systems, we recommend you to use SAP Ariba Cloud Integration Gateway as the integration mechanism. If you have already used other solutions to integrate SAP Ariba solutions with SAP ERP or SAP S/4HANA systems, you can choose to do one of the following: ● Migrate all the transactions of SAP Ariba solutions, master data, and catalog to SAP Ariba Cloud Integration Gateway and configure them for integrating to SAP ERP or SAP S/4HANA. ● Migrate designated transactions, master data (optional), and catalog (optional) to SAP Ariba Cloud Integration Gateway and configure them for integrating to SAP ERP or SAP S/4HANA. The transactions that you have not migrated to SAP Ariba Cloud Integration Gateway will remain integrated with your SAP

SAP Ariba Cloud Integration Gateway migration guide Introduction

CONFIDENTIAL

5

ERP or SAP S/4HANA using the existing integration solutions. This enables you to use SAP Ariba Cloud Integration Gateway as an integration mechanism in addition to the existing integration solutions. To use SAP Ariba Cloud Integration Gateway, you must first determine the transactions and the SAP Ariba BAdIs that you want to integrate using SAP Ariba Cloud Integration Gateway. Then, you must migrate them from SAP Ariba cloud integration adapter to one of the following SAP Ariba Cloud Integration Gateway addons: ● SAP Ariba Cloud Integration Gateway, add-on for SAP ERP ● SAP Ariba Cloud Integration Gateway, add-on for SAP S/4HANA This document addresses s and provides information about the prerequisites, tasks, and the configurations required to successfully migrate transactions from SAP Ariba cloud integration adapter to SAP Ariba Cloud Integration Gateway. After you complete the migration of the required transactions, proceed with the tasks to integrate SAP ERP or SAP S/4HANA with Ariba Network, SAP Ariba Procurement solutions, and SAP Ariba Strategic Sourcing solutions using SAP Ariba Cloud Integration Gateway. The following table provides information about related guides to help you with the integration: Document

Location

SAP Ariba Cloud Integration Gateway overview guide

SAP Help Portal

Contains all the details you need for an overview of SAP Ariba Cloud Integration Gateway and ed transac tions. SAP Ariba Cloud Integration Gateway installation guide

SAP Help Portal

Contains all the details you need for installation of SAP ERP and SAP S/4HANA add-on and for setting up SAP Ariba Cloud Integration Gateway. SAP Ariba Cloud Integration Gateway configuration guide

SAP Help Portal

Contains all the details you need for setting up the Ariba Net work integration in your SAP ERP or SAP S/4HANA system.

1.1

ed systems

The following section lists the ed systems and the ed software in this release of SAP Ariba Cloud Integration Gateway.

SAP ERP and SAP S/4HANA systems The following versions of SAP ERP and SAP S/4HANA systems are currently ed: ● SAP ERP (SAP_BASIS 700 SP27 is the SAP Basis version for all the following SAP ERP versions)

6

CONFIDENTIAL


SAP EHP0 for SAP ERP 6.0 (SAP_APPL 600 SP22) SAP EHP2 for SAP ERP 6.0 (SAP_APPL 602 SP12) SAP EHP3 for SAP ERP 6.0 (SAP_APPL 603 SP11) SAP EHP4 for SAP ERP 6.0 (SAP_APPL 604 SP12) SAP EHP5 for SAP ERP 6.0 (SAP_APPL 605 SP09) SAP EHP6 for SAP ERP 6.0 with non-HANA database (SAP_APPL 606 SP05) SAP EHP6 for SAP ERP 6.0 with HANA database (SAP_APPL 606 Minimum ed version) SAP EHP7 for SAP ERP 6.0 (SAP_APPL 617 Minimum ed version) SAP EHP8 for SAP ERP 6.0 (SAP_APPL 618 Minimum ed version) ● SAP S/4HANA ○ SAP S/4HANA, on-premise edition 1709 ○ SAP S/4HANA, on-premise edition 1610 ○ SAP S/4HANA, on-premise edition 1511

Add-on for SAP ERP and SAP S/4HANA The following add-ons for your SAP ERP and SAP S/4HANA systems are ed: ● SAP ERP SAP Ariba Cloud Integration Gateway, add-on for SAP ERP ● SAP S/4HANA SAP Ariba Cloud Integration Gateway, add-on for SAP S/4HANA

Software components Install the appropriate software component for your SAP ERP or SAP S/4HANA system: ● SAP ERP SAP Ariba Cloud Integration Gateway 1.0, add-on for SAP ERP ○ SAP Ariba Cloud Integration Gateway 1.0, add-on for SAP (ARBCI1 100) - Use for EHP0 to EHP8 ○ Ariba Cloud Integration for SAP ERP EHP4 to EHP8. V.1 (ARBCI2 100) - Use for EHP 4 to EHP8 ○ Ariba Cloud Integration for RETAIL. Version 1.0 (ARBCIGR 100) - Use for EHP 0 to EHP8  Note ○ Before you install the Ariba Cloud Integration for RETAIL. Version 1.0 (ARBCIGR 100) software component, you must install the following software packages: ○ ARBCI1 100 SP01 (Software package specific to SAP Ariba) ○ EA-RETAIL EHP0 SP22 (Enterprise software package) ○ Use ARBCI2 100 if you want to use SAP Ariba Sourcing or SAP Ariba Contracts ● SAP S/4HANA: SAP Ariba Cloud Integration Gateway 1.0, add-on for S/4HANA ○ ARIBA CLOUD INT FOR S/4HANA 1.0 (ARBCI1 10S) ○ ARIBA CLOUD INT FOR S/4HANA 1.0 (ARBCI2 10S)


CONFIDENTIAL

7

○ ARIBA CLOUD INT FOR S/4HANA 1.0 (ARBCIGR 10S)

ed languages The add-ons for SAP ERP and SAP S/4HANA systems are available only in English.

8

CONFIDENTIAL


2

ed SAP Ariba Solutions

SAP Ariba Cloud Integration Gateway s the following SAP Ariba cloud solutions with SAP ERP and SAP S/4HANA: Ariba Network

SAP Ariba Invoice Management

SAP Ariba Buying

SAP Ariba Buying and Invoicing

SAP Ariba Buying, multi-ERP edition

SAP Ariba Catalog

SAP Ariba Sourcing

SAP Ariba Contract Invoicing

SAP Ariba Collaborative Sourcing

SAP Ariba Strategic Sourcing Suite

SAP Ariba Commerce Automation

SAP Ariba Contracts

SAP Ariba Discounting

SAP Ariba Supply Chain Collaboration

SAP Ariba Cloud Integration Gateway does not the following SAP Ariba solutions: ● Integration with Ariba Network ○ Payment remittance using payment integration toolkit ● Integration with SAP Ariba Strategic Sourcing solutions ○ Bill of Materials integration ● Integration with SAP Ariba Procurement solutions ○ File channel transactional data integration for SAP Ariba Procurement solutions ○ Payment Remittance ○ Expense report  Note ○ SAP Ariba Cloud Integration Gateway s the integration of Purchase Information Records. However, this integration will be fully functional as part of an SAP Ariba Application release.

SAP Ariba Cloud Integration Gateway migration guide ed SAP Ariba Solutions

CONFIDENTIAL

9

3

High-level steps about migrating from Ariba cloud integration adapter to SAP Ariba Cloud Integration Gateway

Perform the activities described in the following table in the same order in the SAP ERP or SAP S/4HANA environment for migrating transactions of Ariba Network, SAP Ariba Procurement solutions, and SAP Ariba Strategic Sourcing solutions to SAP Ariba Cloud Integration Gateway. Activity

Environment

Description

Enable SAP Ariba Cloud Integration

SAP Ariba solutions

For more information, see the Configur

Gateway

ing your Ariba Network to ac cess SAP Ariba Cloud Integration Gate way chapter in the SAP Ariba Cloud In tegration Gateway installation guide.

SAP Cloud Connector 

SAP ERP or SAP S/4HANA

tor, you can it from SAP De

Note

velopment Tools

You must use either SAP Cloud Connector or a reverse proxy to se cure the inbound data transfer to the on-premise SAP ERP system. Use SAP Cloud Connector if you have not configured a reverse proxy between SAP Ariba Cloud Integra tion Gateway and SAP ERP to se cure the inbound data transfer.

Install and configure SAP Cloud Con nector 

If you want to use SAP Cloud Connec

For more information, see the Configur ing the SAP Cloud Connector chapter in the SAP Ariba Cloud Integration Gate way installation guide.


For more information about installing and configuring SAP Cloud Connector,

Note

Do this activity only if you have not configured a reverse proxy to se cure the inbound data transfer to the on-premise SAP ERP system.

see the Configuring the SAP Cloud Con nector section in the SAP Ariba Cloud Integration Gateway installation guide. Also, see Securing inbound data trans fer from SAP Ariba Cloud Integration Gateway to the on-premise SAP ERP system [page 13]

10

CONFIDENTIAL

SAP Ariba Cloud Integration Gateway migration guide High-level steps about migrating from Ariba cloud integration adapter to SAP Ariba Cloud Integration Gateway

Activity

Environment

Description

the add-on for SAP ERP or


You can the following add-

SAP S/4HANA

ons from the SAP Software Center on the SAP Service Marketplace at:https://.sap.com/swdc ●

:

SAP Ariba Cloud Integration Gate way, add-on for SAP ERP

●

SAP Ariba Cloud Integration Gate way, add-on for SAP S/4HANA

For more information, see the Installing and configuring the add-on for SAP ERP and SAP S/4HANA chapter in the SAP Ariba Cloud Integration Gateway instal lation guide. Install and configure the add-on


For more information about installing and configuring the SAP Ariba Cloud In tegration Gateway, add-on for SAP ERP or SAP S/4HANA, see the Installing and configuring the add-on for SAP ERP and SAP S/4HANA chapter in the SAP Ariba Cloud Integration Gateway installation guide.

Do the prerequisite tasks before you mi SAP ERP or SAP S/4HANA

For more information, see Prerequisites

grate the transactions of SAP Ariba sol

for migrating transactions to SAP Ariba

utions, master data, and catalog from

Cloud Integration Gateway [page 13]

the existing integration solutions to SAP Ariba Cloud Integration Gateway. 

Note

If you are planning a partial migra tion of data to SAP Ariba Cloud In tegration Gateway, do the prerequi site tasks for the transactions, master data, and catalog that you want to migrate. For example, if you are planning to migrate only the in voice status update transaction to SAP Ariba Cloud Integration Gate way, perform the prerequisite task described in the Prerequisites for migrating the invoice status update transaction [page 17] section. You do not have to do any other prereq uisite tasks.


CONFIDENTIAL

11

Activity

Environment

Description

Run the report to migrate SAP Ariba


For more information, see the following topics:

data from the /ARBA/ database table to the new ARBCIG_ database table

●

About migrating data from the / ARBA/ database table to the ARB CIG_ database table [page 20]

●

How to migrate data to the new da tabase table [page 24]

Run the report to migrate the configu-


rations of designated transactions from


SAP ERP to SAP Ariba Cloud Integra

●

tion Gateway

About migrating the configurations of transactions from SAP ERP to SAP Ariba Cloud Integration Gate way [page 25]

●

How to migrate the configurations of transactions from SAP ERP to SAP Ariba Cloud Integration Gate way [page 26]

Run the report to migrate the imple


mentations of SAP Ariba Business Add-


in (BAdI) information available in your

●

environment

About migrating SAP Ariba BAdIs to SAP Ariba Cloud Integration Gateway [page 27]

●

How to migrate SAP Ariba BAdIs to SAP Ariba Cloud Integration Gate way [page 30]

Manually migrate the required SAP


Ariba BAdIs (optional)

For more information, see About SAP Ariba BAdIs you want to migrate man ually to SAP Ariba Cloud Integration Gateway [page 32]

Perform the post-migration tasks and the additional configurations

12

CONFIDENTIAL


For more information, see Post-migra tion tasks [page 33].


4

Prerequisites for migrating transactions to SAP Ariba Cloud Integration Gateway

This chapter describes the tasks that you must do before you migrate the transactions of Ariba Network, SAP Ariba Strategic Sourcing solutions, and SAP Ariba Procurement solutions from the existing integration solutions to SAP Ariba Cloud Integration Gateway.  Note The prerequisites for the transactions described in the following sections apply only if you want to migrate the integration of those transactions to SAP Ariba Cloud Integration Gateway. If you want to continue with the integration of a transaction using Ariba Network adapter for SAP NetWeaver, you must avoid the prerequisite for that transcation.

4.1

Securing inbound data transfer from SAP Ariba Cloud Integration Gateway to the on-premise SAP ERP system

You can use SAP Cloud Connector or a reverse proxy to secure inbound data transfer to the on-premise SAP ERP system. SAP Cloud Connector or a reverse proxy ensures secure communication from SAP Ariba Cloud Integration Gateway to the on-premise SAP ERP system. For more information, see: ● https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/ 14567e1c8618433c9f003e70f0681141.html ● Configuring the SAP Cloud Connector chapter in the SAP Ariba Cloud Integration Gateway installation guide

4.2

Maintaining certificates

You must maintain certificates in the SAP ERP or SAP S/4HANA systems before you migrate the configurations of transactions to SAP Ariba Cloud Integration Gateway. Maintaining certificates is a prerequisite for running the migration reports that enables you to migrate the configurations of transactions to SAP Ariba Cloud Integration Gateway. To maintain certificates, you must run the spro transaction code and navigate to Integration with Other mySAP.com Components

SAP Reference IMG

SAP Ariba Cloud Integration Gateway

Global

Settings . For more information, see the How to maintain certificates section in the SAP Ariba Cloud Integration Gateway installation guide.

SAP Ariba Cloud Integration Gateway migration guide Prerequisites for migrating transactions to SAP Ariba Cloud Integration Gateway

CONFIDENTIAL

13

4.3

Prerequisite for migrating master data and catalog

Before you migrate master data and catalog for SAP Ariba Procurement solutions and SAP Ariba Strategic Sourcing solutions, you must deactivate the event type linkages and remove the HR-CA event type linkages.

Related Information Removing data from specific database tables [page 14] How to deactivate event type linkages [page 14] How to remove the HR-CA event linkages [page 16]

4.3.1 Removing data from specific database tables Before you migrate to SAP Ariba Cloud Integration Gateway, you must remove data from the following database tables from SAP ERP. You must also ensure that the table is empty. ● If you are planning to migrate database tables for master data for the SAP Ariba Procurement solutions or the SAP Ariba Strategic Sourcing solutions, remove data from the /ARBA/CHANGE_DOC table. ● If you are planning to migrate database tables for catalogs for the SAP Ariba Procurement solutions or the SAP Ariba Strategic Sourcing solutions, remove data from the /ARBA/DOC_CHANGE database table.

4.3.2 How to deactivate event type linkages Context The following master data events are connected to object types with the /ARBA/ namespace. As part of using SAP Ariba Cloud Integration Gateway for integration, the namespace of the objects is changed from /ARBA/ to ARBCIG_. You cannot use these events in SAP Ariba Cloud Integration Gateway without updating the namespace of the object types to ARBCIG_. Migrating these events to SAP Ariba Cloud Integration Gateway would cause data clogging. To avoid data clogging, deactivate these event type linkages before you migrate master data and catalog to SAP Ariba Cloud Integration Gateway. After you successfully migrate to SAP Ariba Cloud Integration Gateway, you can configure new event linkages connected to object types with the ARBCIG_ namespace. For more information, see Configuring event linkages [page 37].  Note You can view all the active event types in the Change View "Event Type Linkages": Overview page. However, you should deactivate only the event types that are described in the following table:

14

CONFIDENTIAL


Object category

Object type

Event

Receiver type

Type Linkage Active

BO

/ARBA/0012

COSTCENTER

CHANGE

X

CREATE

X

DELETE

X

CHANGED BO

/ARBA/0012

COSTCENTERCRE ATED

BO

/ARBA/0012

COSTCENTERDE LETED

BO

/ARBA/1001

CREATED

CHANGE

X

BO

/ARBA/1006

CREATED

CREATE

X

BO

/ARBA/1006

VIEWCREATED

CREATE

X

BO

/ARBA/1022

ASSETCHANGED

CHANGE

X

BO

/ARBA/1022

ASSETCREATED

CREATE

X

BO

/ARBA/1022

ASSETDELETED

DELETE

X

BO

/ARBA/3006

CHANGEGL

CHANGE

X

BO

/ARBA/3006

CREATEGL

CREATE

X

BO

/ARBA/3006

DELETEGL

DELETE

X

BO

/ARBA/3060

ONCREATE

CREATE

X

BO

/ARBA/3060

STATUSCHANGED

CHANGE

X

BO

/ARBA/3060

UPDATED CHANGE

CHANGE

X

BO

/ARBA/LFA1

VENDORCHANGED

CHANGE

X

BO

/ARBA/LFA1

VENDORCREATED

CREATE

X

BO

/ARBA/LFA1

VENDORDELETED

DELETE

X

BO

/ARBA/

CLONED

_CHANGE

X

BO

BUS1001

CREATED

CHANGE

X

BO

BUS1001006

VIEWCREATED

CREATE

X

BO

BUS3003

STARTVEEKPLA

CHANGE

X

CREATE

X

MATNRDEL BO

BUS3003

STARTVENDOR MATNRDEL


CONFIDENTIAL

15

Object category

Object type

Event

Receiver type

Type Linkage Active

BO

BUS3060

STATUSCHANGED

CHANGE

X

Procedure 1. On the SAP Easy Access page, run the swetypv transaction code. 2. On the Change View "Event Type Linkages": Overview page, select each of the events listed in the table in this topic and double-click Type linkage active against it. 3. On the Change View "Event Type Linkages": Details page, in the Linkage Setting (Event Receiver) section, uncheck Linkage Activated and click Save.

4.3.3 How to remove the HR-CA event linkages Context Before you migrate master data and catalogs, you must remove the linkages of the following HR-CA event types:  Note You can view all the active event types in the Change View "Event Type Linkages": Overview page. However, you should deactivate only the event types that are described in the following table:

Object type

Function mod

OT

text

IT

Updat

SeqNo

Obj. type

ule

P

Person

0001

UPD

0

BUS1065

/ARBA/ HRPM_CHANG E_DOCS

P

Person

0002

UPD

0

PERSDATINT


P

Person

0105

DEL

0

EMPLCOMM


P

16

Person

CONFIDENTIAL

0105

INS

0

EMPLCOMM



Object type

Function mod

OT

text

IT

Updat

SeqNo

Obj. type

ule

P

Person

0105

UPD

0

EMPLCOMM


Procedure 1. On the SAP Easy Access page, run the SWEHR3 transaction code. 2. On the Change View "HR-CA Event Linkage for Customer": Overview page, select each of the events listed in the table in this topic and click Delete. 3. Click Save.

4.4

Prerequisites for migrating the invoice status update transaction

Before you migrate the invoice status update transaction of Ariba Network to SAP Ariba Cloud Integration Gateway, you must process the existing data in the /ARBA/AN_ISUINV database table and ensure that the table is empty.

Related Information Invoice status update [page 57]

4.5

Prerequisites for migrating the product activity message transaction

Before you migrate the product activity message transaction that Ariba Network s to SAP Ariba Cloud Integration Gateway, remove the implementation of the MB_DOCUMENT_BADI BAdI.

Related Information Product activity message [page 63]


CONFIDENTIAL

17

4.6

Prerequisites for migrating the purchase order transaction

Before you migrate the purchase order transaction that the SAP Ariba Procurement solutions to SAP Ariba Cloud Integration Gateway, you must run the Purchase Order Header Status Pull report.

Related Information Purchase order [page 69]

4.7

Prerequisites for migrating the advance payment transaction

Before you migrate the advance payment transaction that the SAP Ariba Procurement solutions to SAP Ariba Cloud Integration Gateway, you must remove the existing implementations of the advance payment transaction that is integrated with the SAP ERP or SAP S/4HANA systems. After you migrate to SAP Ariba Cloud Integration Gateway, you can configure this transaction again. You must also remove the implementation of the BADI_ACC_DOCUMENT BAdI. For more information, see the Configuring advance payment in SAP ERP and SAP S/4HANA section in the SAP Ariba Cloud Integration Gateway configuration guide.

Related Information Advance payment [page 72] How to remove a BAdI implementation [page 19]

4.8

Prerequisites for migrating the product activity message transaction

Before you migrate the product activity message transaction to SAP Ariba Cloud Integration Gateway, you must remove the BAdI implementation in which the /ARBA/CL_IM_PROA_PUBLISH class has been used. You must also remove or deactivate the implementation of the MB_BADI_RAISE_A2A BAdI. For more information, see How to remove a BAdI implementation [page 19]

18

CONFIDENTIAL


4.8.1 How to remove a BAdI implementation Context To remove the BAdI implementation, perform the following steps:

Procedure 1. Run the SE24 transaction. 2. In the Objective type field of the Class Builder: Initial Screen, enter the name of the implementation class. For example, enter /ARBA/CL_IM_PROA_PUBLISH to remove the BAdI implementation that uses the / ARBA/CL_IM_PROA_PUBLISH class and click Use of class-interface. 3. In the Where-Used List Class/Interface dialog box, select the following and click Execute: ○ Business Add-ins ○ Enhancement Implementation ○ Enhancement Spots 4. Get the used list of the implementation class and get the name of the BAdI that is implemented using this class. For example, from the used list of the /ARBA/CL_IM_PROA_PUBLISH implementation class , get the name of the BAdI. 5. Run the SE19 transaction and enter the name of the enhancement implementation. 6. Click Change and get the BAdI name. For example, MB_DOCUMENT_BADI. 7. Run the SE18 transaction and in the BAdI Name field, enter the BAdI definition name. For example, enter MB_DOCUMENT_BADI. 8. On the menu bar, click

Enhancement Implementation

Overview

.

9. In the dialog box that lists the implementations for the BAdI, double-click the required implementation name. For example, for the MB_DOCUMENT_BADI BAdI, double-click ZMB_DOCUMENT_BADI. 10. Click Display <-> Change. 11. Click Deactivate.


CONFIDENTIAL

19

5

Migrating to SAP Ariba Cloud Integration Gateway

This chapter helps you perform migration from Ariba Network adapter for SAP NetWeaver to SAP Ariba Cloud Integration Gateway. It has information on the migration reports that you must run after you run SAP upgrade.  Note You must first run the standard SAP upgrade program. Then, you must run the three migration reports in the order mentioned in the following table: Order to run reports

Report name

Purpose

Step 1

Migrate SAP Ariba data to new

To migrate data from the /ARBA/ da

database tables

tabase table to the new ARBCIG_ da tabase table.

Step 2

Migrate transaction setups to SAP

To migrate the configurations of desig

Ariba Cloud Integration Gateway

nated transactions from SAP ERP to SAP Ariba Cloud Integration Gateway.

Step 3

Migrate customer-implemented SAP

To migrate Business Add-in (BAdI) in

Ariba BAdIs

formation from SAP ERP to SAP Ariba Cloud Integration Gateway.

5.1

About migrating data from the /ARBA/ database table to the ARBCIG_ database table

As part of integrating SAP ERP or SAP S/4HANA with Ariba Network, SAP Ariba Procurement solutions, and SAP Ariba Strategic Sourcing solutions using SAP Ariba Cloud Integration Gateway, the namespace of the existing database tables has been changed from /ARBA/ to ARBCIG_. In SAP ERP, the new database tables with the ARBCIG_ namespace have been created. Now, you must migrate data from the database tables with / ARBA/ namespace to the new tables with ARBCIG_ namespace. When you select the checkbox for Ariba Network, SAP Ariba Procurement solutions, and SAP Ariba Strategic Sourcing solutions, you can view the list of transactions under each category for which you want to migrate associated database tables. The first checkbox in each category is for migrating the general tables for that category. They are the following: ● General Tables for Ariba Network ● General Tables for SAP Ariba Procurement ● General Tables for SAP Ariba Strategic Sourcing

20

CONFIDENTIAL

SAP Ariba Cloud Integration Gateway migration guide Migrating to SAP Ariba Cloud Integration Gateway

The checkboxes for general tables appear selected by default. This indicates that the data from the general tables is migrated after you press the Execute button. This migration occurs even if you have not selected any transactions in that category. The data in the general tables is required for all the transactions, which include the transactions that do not require a specific database table to function. The following table lists the existing database tables with /ARBA/ namespace and their corresponding new tables with ARBCIG_ namespace: Existing table

New table

/ARBA/FL_MAP

ARBCIG_FIELDMAP

/ARBA/AUTH_PARAM

ARBCIG_AUTHPARAM

/ARBA/FIELD_MAP

ARBCIG_FIELDMAP

/ARBA/INCR_DTTIM

ARBCIG_INCRDTTIM

/ARBA/SYSTID_MAP

ARBCIG_SYSTIDMAP

/ARBA/TVARV

ARBCIG_TVARV

/ARBA/USR_GRP

ARBCIG_USR_GRP

/ARBA/LAST_CONTR

ARBCIG_LASTCONTR

/ARBA/P2P_VENDOR

ARBCIG_P2PVENDOR

/ARBA/TAXCAT_MAP

ARBCIG_TAXCATMAP

/ARBA/AN_VENDOR

ARBCIG_AN_VENDOR

/ARBA/PARAM_TAB

ARBCIG_TVARV

/ARBA/GR

ARBCIG_GOODSRT

/ARBA/PROXYPARAM

ARBCIG_PRXYPARAM

/ARBA/FUNDER

ARBCIG_FUNDER

/ARBA/PROA_LOG

ARBCIG_PROA_LOG

/ARBA/PROA_TRIGG

ARBCIG_PROATRIGG

RBKP

ARBCIG_INVHISTRY

/ARBA/PIR_CD_MAP

ARBCIG_COND_MAP

/ARBA/PO_HISTORY

ARBCIG_POHISTORY

/ARBA/RFQ_TEXTS

ARBCIG_RFQTEXTS

/ARBA/REQPARAM

ARBCIG_REQPARAM


CONFIDENTIAL

21

Existing table

New table

/ARBA/PR_HISTORY

ARBCIG_PRHISTORY

ESSR

ARBCIG_SES

To migrate data to the new database tables, you can use the Migrate SAP Ariba data to new database tables report. This report also enables you to migrate data to the database tables for master data and catalog. Under Shared data, you can select Master data or Catalog, or both as required and migrate the database tables associated with them to the ARBCIG_ tables.  Note The Migrate SAP Ariba data to new database tables report displays only the transactions that require specific database tables to function. In the SAP Ariba Procurement solutions category, you can use filters to select a specific set of transactions and migrate the data for them to SAP Ariba Cloud Integration Gateway. These filters help you improve efficiency of migration by avoid migrating data pertaining to all transaction to SAP Ariba Cloud Integration Gateway. The following table lists the transactions that you can select in each category: Solution

Transactions

Filters

Ariba Network

Requisition

No filters

Invoice status update Payment proposal ERP-CC invoice Liability transfer Product activity message SAP Ariba Procurement solutions

Requisition

SAP Purchase Requisition Numbers filter by a specific range of requisitions

Purchase order 

Note

SAP Purchase Order Number filter by a specific range of purchase orders

Along with migrating purchase or der header status to SAP Ariba Cloud Integration Gateway, you must migrate the goods receipt and the payment export request transactions as well.

22

CONFIDENTIAL


Solution

Transactions Service entry sheet

Filters ●

Service Entry Sheet Number filter by a specific range of service entry sheet numbers

●

External Entry Sheet Number filter by a specific external entry sheet number

Contracts Goods receipt

No filters Creation Date filter by the date of crea tion of the goods receipt.

Payment export request



Note

For all the following filters, except the Document Header Text filter, you can select multiple values us ing the Multiple selection option. ●

Document Number filter by a spe cific range of document numbers

●

Fiscal Year filter by one or more fiscal years that applies to the pay ment export requests

●

Document Type filter by one or more document types

●

Created Date filter by the date of creation of the payment export re quests

●

Company Code filter by the com pany code

●

Invoicing Party filter by the party for which the payment export re quest has been created

●

Origin of a Logistics IV Doc filter by the origin of logistics invoice verification document

●

Invoice Document Status filter by the status of the payment export request record

●

Created By filter by the resource who created the transaction.

●

Document Header Text filter by the document header text

SAP Ariba Strategic Sourcing solutions


Purchase information record

No filters

CONFIDENTIAL

23

Solution

Transactions

Filters

Quote message

For the complete list of all the ed transactions that belong to Ariba Network, SAP Ariba Procurement solutions, and SAP Ariba Strategic Sourcing solutions, see the following topics in the SAP Ariba Cloud Integration Gateway Overview Guide: ● Transactions for Ariba Network ● Transactions for SAP Ariba Procurement solutions ● Transactions for SAP Ariba Sourcing and SAP Ariba Contracts For more information about how to configure the ed transactions, see the SAP Ariba Cloud Integration Gateway Configuration Guide.

5.1.1 How to migrate data to the new database table Prerequisites Run the standard SAP upgrade program.

Context The Migrate SAP Ariba data to new database tables report is the first migration report that you run after completing the standard SAP upgrade. This report enables you to migrate data from the database tables with the /ARBA/ namespace to the new tables with the ARBCIG_ namespace.

Procedure 1. In the SAP Easy Access screen, run the arbcig_migration transaction code. 2. In the SAP Easy Access SAP Ariba Migration: Add on screen, under SAP menu, double-click Migrate SAP Ariba data to new database tables. 3. In the Migrate SAP Ariba data to new database tables screen, do the following and click Execute: 1. Under Select one or more transactions to migrate the corresponding data, select the checkboxes for Ariba Network, SAP Ariba Procurement solutions, and SAP Ariba Strategic Sourcing solutions and select the transactions for which you want to migrate associated database tables. 2. Under Shared data, select Master Data, or Catalog, or both as required.

24

CONFIDENTIAL


5.2

About migrating the configurations of transactions from SAP ERP to SAP Ariba Cloud Integration Gateway

After you migrate data from the /ARBA/ database table to the ARBCIG_ database table in your SAP ERP system, you can migrate the configurations of certain transactions from your SAP ERP system to SAP Ariba Cloud Integration Gateway. You can migrate parameters and database tables associated with the designated transactions from Ariba Network SAP Ariba Procurement solutions and SAP Ariba Strategic Sourcing solutions.  Note Before you run this report, you must maintain certificates in your SAP system. For more information, see Maintaining certificates [page 13] The following table lists the details of the parameters that you can migrate from SAP ERP to SAP Ariba Cloud Integration Gateway: SAP Ariba Cloud Inte gration Gateway field Solution

Transaction

SAP parameter name

SAP field name

name

Quote automation

Quote message

QUOTE

COSTCENTER

Cost Center

QUOTE

GL_

G/L

QUOTE

ASSET

Asset

QUOTE

SUB_NUMBER

Asset Subnumber

QUOTE

ORDER

Order

QUOTE

WBS_ELEMENT

WBS Element

QUOTE

ACCTASSCAT

Assignment

(ed by Ariba Network)

Category QUOTE

DOC_TYPE

Quote Document Type

QUOTE

ONETIME_VENDOR

Quote Automation Vendor ID

QUOTE

PLANT

Quote Automation Plant

SAP Ariba Procure

Requisition

ment solutions

/ARBA/

SAP Document Type

PURREQ_DOC_TYP Purchase order

BAPI_PO_CRE

SAP Document Type

ATE_DOC_TYPE


CONFIDENTIAL

25

SAP Ariba Cloud Inte gration Gateway field Solution

Transaction

SAP parameter name

SAP field name

name

BAPI_PO_CRE

SAP CC Document

ATE_ERP_DOC_TYPE

Type

/ARBA/

Header Text ID

HEADER_TEXT_ID

Invoice

/ARBA/ITEM_TEXT_ID

Item Text ID

/ARBA/

SAP Document Type

INVOICE_DOC_TYPE

The following table lists the details of the database tables that you can migrate from SAP ERP to SAP Ariba Cloud Integration Gateway: SAP Ariba Cloud Integration Solution

Transaction

Database table name

Gateway lookup table name

/ARBA/TAX_CHECK

TaxOnCompanyCode

Purchase order

/ARBA/COND_MAP

ProcurementConditionType

Invoice

/ARBA/WHT_TYPE

WithholdingTaxMap

SAP Ariba Procurement solu Requisition tions

The Migrate transaction setups to SAP Ariba Cloud Integration Gateway report helps you migrate parameters and database table information to SAP Ariba Cloud Integration Gateway. When you run this report for the first time, you must authenticate yourself to SAP Ariba Cloud Integration Gateway using your SOA Manager credentials. You do not need to authenticate for the subsequent migration of parameters and database tables to SAP Ariba Cloud Integration Gateway.

5.2.1 How to migrate the configurations of transactions from SAP ERP to SAP Ariba Cloud Integration Gateway Prerequisites ● Maintain certificates before you run this report For more information, see Maintaining certificates [page 13] ● Run the Migrate SAP Ariba data to new database tables report before you run this report. For more information, see How to migrate data to the new database table [page 24]

26

CONFIDENTIAL


Context The Migrate transaction setups to SAP Ariba Cloud Integration Gateway report enables you to migrate the configurations of designated transactions from your SAP ERP system to SAP Ariba Cloud Integration Gateway.

Procedure 1. In SAP Easy Access screen, run the ARBCIG_MIGRATION transaction code. 2. In the SAP Easy Access SAP Ariba Migration: Add on screen, under SAP menu, double-click Migrate transaction setups to SAP Ariba Cloud Integration Gateway. 3. In the Migrate transaction setups to SAP Ariba Cloud Integration Gateway screen, do the following and click Execute. 1. Under Authenticate on SAP Ariba Cloud Integration Gateway using SOA Manager credentials, enter your SOA Manager details required to authenticate yourself to SAP Ariba Cloud Integration Gateway. This includes your SOA Manager name, , proxy host name, and port number to connect to the proxy host. 2. Specify whether you are connecting to the test installation or the production installation of SAP Ariba Cloud Integration Gateway. We recommend that you migrate parameters and database tables of transactions to a test installation of SAP Ariba Cloud Integration Gateway before you migrate them to the production installation. 3. Under Select one or more transactions to migrate the corresponding setups, select the solution and select the transactions that you want to migrate to SAP Ariba Cloud Integration Gateway.

5.3

About migrating SAP Ariba BAdIs to SAP Ariba Cloud Integration Gateway

SAP Ariba BAdIs that customers have implemented in their environment contain the configurations specific to their environment. After you migrate the setups of transactions from SAP ERP to SAP Ariba Cloud Integration Gateway, you can proceed to migrate these customer-implemented SAP Ariba BAdIs to SAP Ariba Cloud Integration Gateway. A customer-implemented SAP Ariba BAdI contains one or more BAdI implementations. Each of these BAdI implementations contains one or more methods. Migrating these BAdIs to SAP Ariba Cloud Integration Gateway includes the following manual steps: ● List the active SAP Ariba BAdIs that you have implemented in your environment. You can view these SAP Ariba BAdIs in the Migrate customer-implemented SAP Ariba BAdIs report. ● each implementation of the BAdI to your computer. ● Ensure that the namespaces of all the objects that are used in the method file or referred from the method file of an implementation are updated from /ARBA/ to ARBCIG_. ● Ensure that the names of the objects that are referred from the method file of an implementation are updated to the latest name. This applies only to the objects whose names are changed.


CONFIDENTIAL

27

● Create the new BAdI implementation using the updated method files.  Note You must ensure that the names of the methods are as per the new SAP Ariba BAdIs. We have introduced a few new methods in some of the new SAP Ariba BAdIs. If you want to use these methods, you must include them while implementing the corresponding new BAdIs. The following methods available with the old SAP Ariba BAdIs have been removed. They are not available with the new BAdIs. If you want to introduce the logic of these methods, you must add their logic to the new BAdIs. Methods removed

Old BAdIs where these methods were available

PUBLISH_VENDOR_EXTENSION

/ARBA/MASTER_DATA

●

UPDATE_CONDITIONS

●

UPDATE_EACH

●

UPDATE_EACHITEM

●

CONTRACT_PREPROCESSING

●

CONTRACT_POSTPROCESSING

●

CONTRACT_MODIFY_ITEM

●

CONTRACT_MODIFY_

●

CONTRACT_MODIFY_CONDITION

/ARBA/QUOTEMESSAGE

FI_INVOICE_CREATE

/ARBA/INVOICE_CREATE

PUBLISH_PO_CREATE1

/ARBA/PO_IMPORT



Note

This is replaced by the new PUBLISH_PO_CREATE method

The following table lists the names of the SAP Ariba BAdIs available in Ariba Network adapter for SAP NetWeaver and their corresponding BAdIs available in SAP Ariba Cloud Integration Gateway: BAdI in Ariba Network adapter for SAP NetWeaver

BAdI in SAP Ariba Cloud Integration Gateway

/ARBA/ADV_PYMNT

ARBCIG_ADV_PYMNT

/ARBA/ADVANCE_SHIPMENT_NOTICE

ARBCIG_ADVANCE_SHIPMENT_NOTICE

/ARBA/INTERFACE_CHANGE

ARBCIG_AUTO_INTERFACE

/ARBA/BADI_COMPNT_CONSUMPTION

ARBCIG_BADI_COMPNT_CONSUMPTION

/ARBA/BADI_COMPONENT_ACK

ARBCIG_BADI_COMPONENT_ACK

/ARBA/BUYER_CATALOG_EXPORT

ARBCIG_BUY_CATALOG_EXPORT

28

CONFIDENTIAL


BAdI in Ariba Network adapter for SAP NetWeaver


/ARBA/PO_CHANGEORDER

ARBCIG_BUY_ORDCHANGE_BADI

/ARBA/PO_IMPORT

ARBCIG_BUY_PURCHORD_BADI

/ARBA/CONTRA_DETAILS

ARBCIG_CONTRACTDET

/ARBA/DERIVATION

ARBCIG_DERIVATION

/ARBA/BADI_CREDIT_MEMO_CANCEL

ARBCIG_ES_CREDIT_MEMO_CANCEL

/ARBA/BADI_DOC_STAT_UPD

ARBCIG_ES_DOCUMENT_STAT_UPD

/ARBA/ERP_RESPONSE_TO_P2P

ARBCIG_ES_ERP_RESPONSE_TO_P2P

/ARBA/SES_CREATE

ARBCIG_ES_SES_CREATE

/ARBA/GR_CREATE

ARBCIG_GR_CREATE

/ARBA/INVOICE_CREATE

ARBCIG_INVCREATE

/ARBA/BTE_ISU_UPDATE

ARBCIG_INVOICESTATUSUPDATE

/ARBA/LIABILITY_INVOICE

ARBCIG_LIABILITY_INVOICE

/ARBA/MASTER_DATA

ARBCIG_MASTERDATA

/ARBA/PP_UPDATE

ARBCIG_PP_UPDATE

/ARBA/PR_CHANGE

ARBCIG_PR_CHANGE

/ARBA/BADI_PRODUCT_ACTIVITY

ARBCIG_PRODUCT_ACTIVITY

/ARBA/PURINFREC

ARBCIG_PURCHASE_INFOREC

/ARBA/PURREQ

ARBCIG_PURREQ

/ARBA/QUALITY_NOTIFICATION

ARBCIG_QUALITY_NOTIFICATION

/ARBA/QUOTEMESSAGE

ARBCIG_QUOTEMSG

/ARBA/RECEIPT_UPDATE

ARBCIG_RET_UPDATE

/ARBA/REMITTANCE_ADVICE

ARBCIG_REMITTANCE_ADVICE

/ARBA/SHIP_NOTICE_REQUEST_OUT

ARBCIG_SHIP_NOTICE_REQUEST_OUT

/ARBA/BADI_SMI_REPLENISHMT

ARBCIG_SMI_REPLENISHMENT

/ARBA/SRCNG_CONTRT_CREATE_RESP

ARBCIG_SOURCING_CONTRACT

/ARBA/REMIT_EXPORT

ARBCIG_REMIT_EXPORT


CONFIDENTIAL

29

The following are the new BAdIs available in SAP Ariba Cloud Integration Gateway: ● ARBCIG_ES_ATTACHMENT_UTIL ● ARBCIG_ES_COMMENT_UTIL ● ARBCIG_ES_SESR_UPDATE ● ARBCIG_PARAM_UPDATE ● ARBCIG_SEG_INSERT

5.3.1 How to migrate SAP Ariba BAdIs to SAP Ariba Cloud Integration Gateway Prerequisites ● The Migrate customer-implemented SAP Ariba BAdIs report is the third migration report that you must run. Before you run this report, you must run the following migration reports in the following order: 1. Migrate SAP Ariba data to new database tables For more information, see How to migrate data to the new database table [page 24] 2. Migrate transaction setups to SAP Ariba Cloud Integration Gateway For more information, see How to migrate the configurations of transactions from SAP ERP to SAP Ariba Cloud Integration Gateway [page 26] ● Create a folder in the local drive of your computer and designate it for ing the implementations of SAP Ariba BAdIs available in your environment.

Context The Migrate customer-implemented SAP Ariba BAdIs report enables you to migrate the implementation of SAP Ariba BAdIs available in your environment. After you the implementation of customer-implemented SAP Ariba BAdI to the designated folder in your computer, you can see the following folder structure: ● Folder that is named after the name of the BAdI Implementation ○ One or more folders that are named after the name of the BAdI implementation classes. ○ One or more folders that are named after the methods within each class. Each of these folders contains a method file.

Procedure 1. In SAP Easy Access screen, run the arbcig_migration transaction code. 2. In the SAP Easy Access SAP Ariba Migration: Add on screen, under SAP menu, double-click Migrate customer-implemented SAP Ariba BAdIs.

30

CONFIDENTIAL


The Migrate customer-implemented SAP Ariba BAdIs screen appears. In this screen, you can view SAP Ariba BAdIs that are implemented in your environment listed in a table by their active implementation names. 3. In the Select a Folder field, browse and select the designated folder in the local drive of your computer where you want to the implementations of your customer-implemented SAP Ariba BAdIs. 4. In the table that lists the customer-implemented SAP Ariba BAdI implementations available in your environment, select one or more rows that represent the BAdI implementations that you want to migrate to SAP Ariba Cloud Integration Gateway and click Existing Implimentations. 5. In the Display Logs screen, under Date/Time/, click the entry that represents the BAdI implementation activity you have performed. You can view the following status of the record: 1. Path to the designated folder in your local drive where you have ed the BAdI implementations. 2. Names of the SAP Ariba BAdI, their implementation names, class, and the objects for which the parsing has been in progress. The objects may contain the /ARBA/ namespace. Navigate to each of the method files that is ed. In each of these files, manually replace the occurrences of /ARBA/ to ARBCIG_. For some objects, their names have been modified along with the namespaces. You must ensure that you update the appropriate names of the objects in the method files. 3. Parsing completion status 6. After you manually update all the method files, in the Migrate customer-implemented SAP Ariba BAdIs screen, select the updated BAdI implementation and click Create Implementation. If you have missed replacing any occurrence of /ARBA/ with ARBCIG_ in the method file, you can view the screen with the location of those method files. You must manually replace the occurrence of /ARBA/ with ARBCIG_ in those method files. If you have successfully updated the appropriate names of the objects for all the customer-implemented BAdIs, you can proceed to create the new BAdI implementation using the updated method files. 7. Under Create Implementation, view the enhancement spot automatically populated by the system for the new BAdI. Click Create Impl. to start implementing the BAdI using the method file that you have updated with the appropriate object names. 8. In the Create Enhancement Implementation dialog box, enter the implementation name and other details to start creating the BAdI implementation. You must use the updated method files to create the new BAdI implementations. For more information, see How to Implement a BAdI In the Create BAdI Implementations for Existing BAdI Definitions screen, you can do the following: ○ In the BAdI Implementation field, enter the name for the BAdI implementation ○ In the Implementation Class field, enter the BAdI implementation class ○ In the BAdI Definition field, select the definition of the BAdI Do not enter any code in the method file. Instead, you must the updated method files for the BAdI implementation from the local drive of your computer. To the method file, navigate to More Utilities / drive of your computer.

Utilities

and browse and select the method file from the local

To view the details of the BAdI implementation that you have created, you can select the row that represents the BAdI implementation in the Migrate customer-implemented SAP Ariba BAdIs screen and click Implementation Overview.


CONFIDENTIAL

31

5.4

About SAP Ariba BAdIs you want to migrate manually to SAP Ariba Cloud Integration Gateway

If you have implemented the following BAdIs in your current environment, you must manually transfer their implementations to the appropriate method files in the new BAdI objects after you migrate from SAP Ariba cloud integration adapter to SAP Ariba Cloud Integration Gateway: ● /ARBA/CUSTOM_ATTACHMENT ● /ARBA/GOS_ATTACHMENT  Note The implementations for the /ARBA/CUSTOM_ATTACHMENT and the /ARBA/GOS_ATTACHMENT BAdIs must be transferred to the new ARBCIG_BADI_ATTACHMENT_UTIL BAdI. We recommend you to analyze the requirement and transfer the implementation based on your analysis. ● /ARBA/PO_FILE_CHANNL ● /ARBA/CREATE_GR ● /ARBA/INVOICE_LOAD ● /ARBA/PO_MODIFY ● /ARBA/CONTRACT_RESPONSE  Note The following BAdIs are deprecated and are not ed on SAP Ariba Cloud Integration Gateway: ● EXPENSE INTEGRATION ● P2P REMITTANCE

5.5

What's Next?

After you successfully migrate to SAP Ariba Cloud Integration Gateway, proceed to integrate SAP ERP or SAP S/4HANA with Ariba Network, SAP Ariba Procurement solutions, and SAP Ariba Strategic Sourcing solutions using the SAP Ariba Cloud Integration Gateway. After the successful migration to SAP Ariba Cloud Integration Gateway, you must perform the post migration tasks, modify the parameters, enhancements, and the customer exits of the transactions that you have migrated, and perform the configuration tasks for integrating SAP ERP or SAP S/4HANA with Ariba Network, SAP Ariba Procurement solutions, and SAP Ariba Strategic Sourcing solutions using the SAP Ariba Cloud Integration Gateway. For more information, see Post-migration tasks [page 33]

32

CONFIDENTIAL


6

Post-migration tasks

After you migrate to SAP Ariba Cloud Integration Gateway, you can perform the set of tasks that are listed in the following tables to integrate SAP ERP or SAP S/4HANA with Ariba Network, SAP Ariba Procurement solutions, and SAP Ariba Strategic Sourcing solutions using the SAP Ariba Cloud Integration Gateway. This chapter also discusses the modifications to the transactions that you have migrated and the additional configurations that you can perform after migrating to SAP Ariba Cloud Integration Gateway. The following is the list of post-migration tasks that you can perform: Activity

Environment

Description

Configure logical ports and service

SAP ERP or

For more information, see Configuring

names for transactions performed us ing web services proxies

SAP S/4HANA

logical ports and service names for transactions performed using web serv ices proxies [page 37]

Send system details and SAP connec tivity data to SAP Ariba Cloud Integra tion Gateway


For more information, see the How to send SAP information to SAP Ariba Cloud Integration Gateway section in the SAP Ariba Cloud Integration Gate way configuration guide.

Confirm SAP connectivity information


For more information, see the Configur ing a cloud integration project section in the SAP Ariba Cloud Integration Gate way configuration guide.

Configure for attachments and comments Configure event linkages

SAP ERP or SAP S/4HANA SAP ERP or SAP S/4HANA

Modify partner profile settings


Create the table to map values of pric ing condition parameters to in SAP Ariba Cloud Integration Gateway


For more information, see: ing attachments and comments [page 35] For more information, see Configuring event linkages [page 37] For more information, see How to mod ify partner profile settings [page 36] For more information, see Creating a ta ble to map values of pricing condition parameters in SAP Ariba Cloud Integra tion Gateway [page 40]

Migrate advanced ship notice, dispatch delivery notification, and component ship notice transactions


For more information, see Migrating ad vanced ship notice, dispatch delivery notification, and component ship notice transactions [page 39]

SAP Ariba Cloud Integration Gateway migration guide Post-migration tasks

CONFIDENTIAL

33

Activity

Environment

Description

Configure global settings

SAP ERP or

For more information, see the Configur

SAP S/4HANA

ing global settings section in the SAP Ariba Cloud Integration Gateway instal lation guide.

After you modify the parameters, enhancements, and the customer exits of the transactions that you have migrated, you must perform the following additional configuration tasks to integrate your SAP ERP or SAP S/4HANA with the SAP Ariba solutions using SAP Ariba Cloud Integration Gateway: Import master data

SAP ERP

For more information, see the Working with master data chapter in the SAP Ariba Cloud Integration Gateway config uration guide.

Maintain parameters, enhancements, and the customer exits of the transac tions of SAP Ariba solutions


For more information, see: ●

Modifications to transactions sup ported by Ariba Network [page 41]

●

Modifications to transactions sup ported by SAP Ariba Strategic Sourcing solutions [page 65]

●

Modifications to transactions sup ported by SAP Ariba Procurement solutions [page 69]

Also, see the Configuring ed transactions chapter in the SAP Ariba Cloud Integration Gateway configuration guide. Specify cross-reference values


For more information, see the Setting up cross references on SAP Ariba Cloud Integration Gateway chapter in the SAP Ariba Cloud Integration Gateway config uration guide.

Add custom XSLT


To map any customized parameters on SAP ERP or SAP S/4HANA to SAP Ariba Cloud Integration Gateway, use custom XSLT. SAP Ariba Cus tomer to map your customiza tions using XSLT.

Review configuration


For more information, see the Review configuration section in the SAP Ariba Cloud Integration Gateway installation guide.

34

CONFIDENTIAL


Activity

Environment

Description

Test project


For more information, see the Test project section in the SAP Ariba Cloud Integration Gateway installation guide.

Prepare for deployment


For more information, see the About project deployment section in the SAP Ariba Cloud Integration Gateway config uration guide.

6.1

ing attachments and comments

After you migrate to SAP Ariba Cloud Integration Gateway, you will be able to use two new features attachments and comments. These features help you send additional information at the header and the lineitem level of transactions. For more information, see the SAP Ariba Cloud Integration Gateway configuration guide.

6.2

Modifying partner profile settings

After you successfully migrate to SAP Ariba Cloud Integration Gateway, perform the following tasks: ● Replace the partner profiles for the existing basic type with the partner profiles for the new basic types if you use IDocs for the transactions listed in the Partner profile settings table in the Partner profile settings [page 36] topic. ● Use the receiver port that you configured as part of migrating to the SAP Ariba Cloud Integration Gateway. This task applies only if you have connected to SAP Ariba Cloud Integration Gateway without using SAP Process Integration. For more information, see the How to create port definition section in the SAP Ariba Cloud Integration Gateway configuration guide. ● Remove the extension that is available in the existing configuration for the outbound transactions. The extensions are not relevant after you migrate to SAP ERP and SAP S/4HANA add-on for SAP Ariba Cloud Integration Gateway.  Note To create a new partner profile for a new basic type, perform the task in the Setting up the interface section of the SAP Ariba Cloud Integration Gateway configuration guide.


CONFIDENTIAL

35

Related Information How to modify partner profile settings [page 36]

6.2.1 How to modify partner profile settings To modify partner profile settings, perform the following steps:

Procedure 1. In SAP Easy Access screen, run the we20 transaction. 2. In the Partner Profiles screen, on the left-side , expand Partner Type LI or Partner Type LS as required. 3. Under Partner Type LI or Partner Type LS, click the partner number where you want to configure the partner settings. In the right-side , view the details of the partner number that you have clicked. 4. In the right-side , under Outbound parmtrs, double-click the message type for which you want to configure the partner profile settings. The Partner Profiles: outbound parameters screen appears. 5. Under the Outbound options tab, do the following: ○ In the Receiver port field, use the receiver port that you have configured as part of migrating to SAP Ariba Cloud Integration Gateway. ○ In the Basic type field, replace the existing basic type with the new basic type. ○ In the Extension field, remove the existing extension. 6. Click Save.

6.2.1.1

Partner profile settings

The following table displays the existing and the new basic type partner profile settings for transactions: Transaction

Existing basic type

New basic type

Schedule agreement release

DELFOR02

ARBCIG_DELINS

Invoice copy request: FI invoice

FIDC02

ARBCIG_FIDCC2

Invoice copy request: MM invoice

GSVERF03

ARBCIG_GSVERF

Order enquiry

ORDERS05

ARBCIG_ORDENQ

36

CONFIDENTIAL


Transaction

Existing basic type

New basic type

Purchase order

ORDERS05

ARBCIG_ORDERS

Payment remittance

PEXR2001

ARBCIG_REMADV

Quote request

ORDERS05

ARBCIG_REQOTE

Related Information How to modify partner profile settings [page 36]

6.3

Configuring event linkages

After you migrate master data and catalog to SAP Ariba Cloud Integration Gateway, do the following: ● Activate the linkage of the event types For more information, see the How to configure Ariba event linkages topic in the SAP Ariba Cloud Integration Gateway configuration guide. ● Configure SAP Ariba HR event linkage For more information, see the How to configure Ariba HR event linkage topic in the SAP Ariba Cloud Integration Gateway configuration guide.

6.4

Configuring logical ports and service names for transactions performed using web services proxies

Do this configuration only if you have connected to SAP Ariba Cloud Integration Gateway without using SAP Process Integration. After you migrate to SAP Ariba Cloud Integration Gateway, create logical ports for the outbound transactions and service names for the inbound transactions that are performed using web services proxies in SAP ERP. In SAP ERP, the following outbound and inbound transactions for Ariba Network are performed using proxies: Outbound transactions

Inbound transactions

Document status update

Advance Ship Notice

Invoice status update

Component Acknowledgment


CONFIDENTIAL

37

Outbound transactions


Payment proposal

Component Consumption Request

Product activity message

Credit Memo Cancel

Receipt request

Document Status Update

Service sheet response

Liability Transfer

Ship notice request

Product Replenishment Message Remittance Advice Service Sheet

In SAP ERP, the following outbound and inbound transactions for SAP Ariba Procurement solutions are performed using proxies: Outbound transactions


Master data

Purchase order export

ERP response to procurement

Purchase order change export

Catalog request

Purchase order cancel export Purchase order close status Requisition export request Derive ing export Receipt export request Service sheet export request Advance payment export request Cancel advance payment request Payment export request Requisition revert export

In SAP ERP, the following outbound and inbound transactions for SAP Ariba Strategic Sourcing solutions are performed using proxies: Outbound transactions


Master data

Ariba sourcing contracts

38

CONFIDENTIAL


Outbound transactions


Ariba sourcing status updates

Ariba sourcing purchase order

Ariba contract response

Ariba sourcing service items

Purchase info rec confirmation

Purchase info rec

SAP ERP generates the name of the logical port for a proxy-based outbound transaction from the name of the consumer proxy corresponding to that transaction. For example, the consumer proxy for the document status update transaction is ARBCIG_CO_DOCUMENT_STATUS_UPDAT. When you create a logical port for the document status update transaction, SAP ERP generates the name of the logical port as CO_DOCUMENT_STATUS_UPDAT. Authenticate logical ports when you configure them. You can use either a name and a or an SSL certificate for this authentication. To use SSL certificates for authenticating logical ports, ensure that you have the SSL certificates added to your SAP ERP system in advance.  Note In SAP ERP, you can create only one logical port for a consumer proxy or a service definition. If you create an additional logical port, SAP ERP overwrites the existing logical port with the latest one that you have created. For more information on configuring logical ports and service names, see the Setting up the interface section in the SAP Ariba Cloud Integration Gateway configuration guide.

6.5

Migrating advanced ship notice, dispatch delivery notification, and component ship notice transactions

Advanced ship notice transaction has been changed to a web service. Also, the web services for the dispatch delivery notification and the component ship notice have been combined into a new transaction named ship notice request. For component ship notice, the standard ESOA service GoodsMovementERPNotification_Out has been used. For returns, the standard ESOA service DespatchedDeliveryNotification_Out_V1 has been used. For the ship notice request transaction, DespatchedDeliveryNotification_Async_Out has been used. You must configure the interface for these transactions. If you have customized any of these transactions before you migrate to SAP Ariba Cloud Integration Gateway, you must implement those customizations again after migrating to SAP Ariba Cloud Integration Gateway. For more information, see the following sections in the SAP Ariba Cloud Integration Gateway configuration guide: ● Setting up the interface ● Configuring ed Ariba Network transactions ● Advance ship notice


CONFIDENTIAL

39

● Ship notice request

Related Information Ship notice request [page 63]

6.6

Creating a table to map values of pricing condition parameters in SAP Ariba Cloud Integration Gateway

You must manually map the values of pricing condition parameters available in SAP ERP to the new values configured in SAP Ariba Cloud Integration Gateway. to SAP Ariba Cloud Integration Gateway and create this mapping. The following table lists the sample values of the pricing condition parameters in SAP ERP: Pricing condition parameter

Value in SAP ERP

GrossPrice

PBXX

DiscountPercentage

RA01

DiscountAbs

RB00

SurchargePercentage

ZA01

SurchargeAbs

ZB00

TotalPrice

PRSX

DiscountPercentageHeader

01RH

DiscountAbsHeader

0RHA

AdditionalChargePercentageHeader

0ZHP

AdditionalChargeAbsHeader

0ZHA

DiscountPercentageItem

01RP

DiscountAbsItem

01RA

AdditionalChargePercentageItem

01ZP

AdditionalChargeAbsItem

01ZA

40

CONFIDENTIAL


7

Modifications to transactions ed by Ariba Network

As part of migrating to SAP Ariba Cloud Integration Gateway, parameters are added or modified for some of the transactions. Also, SAP Ariba provides new INCLUDE statements that you can use to replace the classes, function modules, or the code that we recommend to place in SAP standard customer exits, BADIs, or enhancements for integrating with SAP Ariba solutions. This chapter includes only the ed Ariba Network transactions that have been modified for integrating with SAP Ariba Cloud Integration Gateway. The sections in this chapter list the changes in the following areas for these transactions: ● Parameters (new and modified) ● Enhancements (new and modified) ● Customer exits  Note This release of SAP Ariba Cloud Integration Gateway does not the payment remittance batch request transaction. For more information on maintaining parameters and implementing customer exits for the transactions, see the Configuring ed Ariba Network transactions section in the SAP Ariba Cloud Integration Gateway configuration guide.  Note If you have any IDoc customizations for Ariba Network transactions, you must re-implement them in the new IDoc types in your SAP ERP or SAP S/4HANA systems. Also, ensure that you map the customized fields to the corresponding cXML structure in SAP Ariba Cloud Integration Gateway extension framework. Purchase order [page 42] Scheduling agreement release [page 46] Order confirmation [page 47] Invoice [page 49] ERP-initiated invoice [page 53] Invoice status update [page 57] Payment proposal [page 58] Payment remittance request [page 59] Remittance advice [page 61] Service sheet [page 61] Service sheet response [page 61] Liability transfer [page 62]

SAP Ariba Cloud Integration Gateway migration guide Modifications to transactions ed by Ariba Network

CONFIDENTIAL

41

Component consumption request [page 62] Component acknowledgment [page 62] Ship notice request [page 63] Product activity message [page 63] Product replenishment message [page 64]

7.1

Purchase order

The following are the parameters, enhancements, and customer exits that are modified for the purchase order transaction:

Parameters Maintain the following renamed parameters: Previous name (in SAP Ariba cloud integration ver sion 9.0 SP2)

Current name

Whether new or renamed

Details

/ARBA/

CSC_COPY_SUP

Renamed

Required for multitier pur

CSC_COPY_SUP

PLIER_PARVW

chase orders for SAP Ariba

PLIER_PARVW /ARBA/PARTNER_PARVW

Supply Chain Collaboration. DELIVER_TO_PARVW

Renamed

Mention the partner function to fetch the partner details.

/ARBA/ARIBA_SRVMAPKEY

ARIBA_SRVMAPKEY

Renamed

Required for service pur chase orders that have serv ice line number and use the service map key activated on the SAP ERP system.

Implicit Enhancements Implicit enhancement to confirgure new purchase orders has been removed. Configuration of new purchase orders has been implemented as part of the INCLUDE ZXM06U33 customer exit. For more information about removing the existing implicit enhancement to configure new purchase orders, see How to remove the implicit enhancement for configuring new purchase orders [page 43].

42

CONFIDENTIAL


Customer exit Replace the code that is used to configure an existing customer exit with the corresponding INCLUDE statements as described in the following table: New INCLUDE statement Customer exit name and

Code (used in the existing

(use to replace the code in

Functional module

integration)

the existing integration)

INCLUDE ZXM06U02 /

To view the code used in the

INCLUDE

EXIT_SAPLEINM_002

customer exit: INCLUDE

ARBCIG_ORDER_REQUES

ZXM06U02, see Code used

T_002 IF FOUND

in INCLUDE ZXM06U02 for the existing integration [page 45] INCLUDE ZXM06U33 /


INCLUDE

EXIT_SAPLEINM_011


ARBCIG_ORDER_REQUES


T_011 IF FOUND

in INCLUDE ZXM06U33 for the existing integration [page 45]

7.1.1 How to remove the implicit enhancement for configuring new purchase orders Context Previously, the configuration of new purchase orders were performed using an implicit enhancement. In the current release, this transaction has been implemented using a customer exit. Before you configure this new customer exit, remove the existing implicit enhancement for configuring service purchase orders.

Procedure 1. In SAP ERP, run the transaction code SE37. The Function Builder: Initial Screen appears. 2. In the Functional Module field, enter IDOC_OUTPUT_ORDERS and click Display. The Function Builder: Display Initial IDOC_OUTPUT_ORDERS screen appears. 3. Under Source code, search for Perform fill_srv_orders. 4. Double-click Perform.


CONFIDENTIAL

43

5. From the popup, select SAPLEINM. 6. In the application toolbar, click Enhance. 7. Click Edit Enhancement Operations Show Implicit Enhancement Options enhancement code that appears after the fill_srv_orders form.

to display the

You can view the following enhancement code: DATA: 1_flag(5) TYPE c, cl_purchaseorder TYPE REF TO /arba/cl_purchaseorder, cl_po_hierarchy TYPE REF TO /arba/cl_po_hierarchy, ls_idoc_status TYPE bdidocstat, lx_appl_idoc TYPE REF TO /arba/cx_appl_idoc. CONSTANTS: c_true TYPE char4 VALUE 'true', c_false(5) TYPE c VALUE 'false'. CREATE OBJECT cl_purchaseorder. CREATE OBJECT cl_po_hierarchy. TRY. CREATE OBJECT cl_po_hierarchy. CALL METHOD cl_po_hierarchy->get_systemversion_ishierarchy EXPORTING ebeln = ekpo-ebeln et_edi_esll = edi_esll[] IMPORTING flag = l_flag CHANGING int_edidd = int_edidd[]. CATCH /arba/cx_appl_idoc INTO lx_appl_idoc. MESSAGE e151(/arba/message) RAISING error_message_received. RETURN. ENDTRY. IF l_flag EQ c_true. CALL METHOD cl_purchaseorder->fill_service_line_number EXPORTING packno = ekpo-packno IMPORTING et_edi_esll = edi_esll[]. ENDIF. 8. Right-click this enhancement block and click Undo. 9. Below the last line in the fill_srv_orders form, right-click the enhancement block that displays the following code and click Undo: 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


44

CONFIDENTIAL


7.1.2 Code used in INCLUDE ZXM06U02 for the existing integration The following is the code used in the INCLUDE ZXM06U02 customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_ORDER_REQUEST_002 IF FOUND INCLUDE statement. **Code for 9W Partner type CALL FUNCTION '/ARBA/PO_PARVW' EXPORTING xekko = xekko dobject = dobject TABLES int_edidd = int_edidd xekpo = xekpo. *** Code to insert the copy supplier segment in the IDoc CALL FUNCTION '/ARBA/PO_COPY_SUPPILER_CSC' EXPORTING xekko = xekko dobject = dobject TABLES int_edidd = int_edidd xekpo = xekpo.


7.1.3 Code used in INCLUDE ZXM06U33 for the existing integration The following is the code used in the INCLUDE ZXM06U33 customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_ORDER_REQUEST_011 IF FOUND INCLUDE statement. DATA: lo_purchaseorder TYPE REF TO /arba/cl_purchaseorder. CREATE OBJECT lo_purchaseorder. CALL METHOD lo_purchaseorder->fill_additional_details EXPORTING dekko = dekko dpekko = dpekko control_record_out = control_record_out dobject = dobject CHANGING dekpo = dekpo[] dpekpo = dpekpo[] deket = deket[] desll = desll[] dint_edidd = dint_edidd[].


CONFIDENTIAL

45


7.2

Scheduling agreement release

The following are the customer exits that are modified for the scheduling agreement release transaction:

Customer exit Replace the code that is used to configure an existing customer exit with the corresponding INCLUDE statement as described in the following table: New INCLUDE statement (use to re Customer exit name and Functional

Code (used in the existing integra

place the code in the existing integra

module

tion)

tion)

INCLUDE ZXM06U59 / EXIT_SA

To view the code used in the INCLUDE

Replace the codes available with IN

PLEINM_019 (for forecast schedule)

ZXM06U59 and the INCLUDE

CLUDE ZXM06U59(Forcast) and IN

and

ZXM06U60 customer exits, see Code

CLUDE ZXM06U60(JIT) using

used in INCLUDE ZXM06U59 and IN

INCLUDE

CLUDE ZXM06U60 for the existing in

ARBCIG_SA_RELEASE_59_60 IF

tegration [page 46]

FOUND

INCLUDE ZXM06U60 / EXIT_SA PLEINM_020 (for JIT schedule)

7.2.1 Code used in INCLUDE ZXM06U59 and INCLUDE ZXM06U60 for the existing integration The following is the code used in the INCLUDE ZXM06U59 and the INCLUDE ZXM06U60 customer exits for the existing integration. Replace this code using the new INCLUDE ARBCIG_SA_RELEASE_59_60 IF FOUND INCLUDE statement. 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

46

CONFIDENTIAL


dekek_x = dekek_x dekeh = dekeh desll = desll dint_edidd = dint_edidd.

Related Information Scheduling agreement release [page 46]

7.3

Order confirmation

The following are the modified customer exits for the order confirmation transaction:




module

tion)

tion)

INCLUDE ZXM06U19 / EXIT_SA


INCLUDE

PLEINM_007

ZXM06U19 customer exit, see Code

ARBCIG_INCL_ORDER_CONFIRM_

used in INCLUDE ZXM06U19 for the ex 01 IF FOUND isting integration [page 47] INCLUDE ZXM06U20 / EXIT_SA


INCLUDE

PLEINM_008


ARBCIG_INCL_ORDER_CONFIRM_

used in INCLUDE ZXM06U20 for the

02 IF FOUND

existing integration [page 48]

7.3.1 Code used in INCLUDE ZXM06U19 for the existing integration The following is the code used in the INCLUDE ZXM06U19 customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_INCL_ORDER_CONFIRM_01 IF FOUND INCLUDE statement. data ls_status type bdidocstat.


CONFIDENTIAL

47

ls_status = i_status. call method /arba/cl_po_confirmation=>update_idtnr exporting i_control = i_control ct_status = ls_status changing i_data = i_data[] is_ekpo = c_ekpo.

Related Information Order confirmation [page 47]

7.3.2 Code used in INCLUDE ZXM06U20 for the existing integration The following is the code used in the INCLUDE ZXM06U20 customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_INCL_ORDER_CONFIRM_02 IF FOUND INCLUDE statement. CALL METHOD /arba/cl_po_confirmation=>update_po_text EXPORTING i_control = i_control is_ekko = order it_edidd = i_data[] CHANGING ct_status = i_status[].

Related Information Order confirmation [page 47]

48

CONFIDENTIAL


7.4

Invoice

The following are the customer exits that are modified for the invoice transaction:




module

tion)

tion)

INCLUDE ZXM08U22 /


INCLUDE

EXIT_SAPLMRMH_011


ARBCIG_INCL_INCOMING_INVOI

used in INCLUDE ZXM08U22 for the ex CE01 IF FOUND isting integration [page 49] INCLUDE ZXM08U25 /


INCLUDE

EXIT_SAPLMRMH_014



used in INCLUDE ZXM08U25 for the ex CE03 IF FOUND isting integration [page 50] INCLUDE ZXM08U26 /


INCLUDE

EXIT_SAPLMRMH_015



used in INCLUDE ZXM08U26 for the ex CE02 isting integration [page 52]

7.4.1 Code used in INCLUDE ZXM08U22 for the existing integration The following is the code used in the INCLUDE ZXM08U22 customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_INCL_INCOMING_INVOICE01 IF FOUND INCLUDE statement. 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


CONFIDENTIAL

49

t_idoc_data = t_idoc_data[] ).

Related Information Invoice [page 49]

7.4.2 Code used in INCLUDE ZXM08U25 for the existing integration The following is the code used in the INCLUDE ZXM08U25 customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_INCL_INCOMING_INVOICE03 IF FOUND INCLUDE statement. 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/_DATA TYPE /ARBA/_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 directly we need to * get this additional information regarding the ing needs to * fetched in an extension segment. Reading data from extension * segement IF i_idoc_data-segnam = '/ARBA/_DATA'. ls_/ARBA/_DATA = i_idoc_data-sdata. IF NOT ls_/ARBA/_DATA IS INITIAL. MOVE-CORRESPONDING ls_/ARBA/_DATA TO ls_cobl_mrm. * Conversion exit for WBS Element CALL FUNCTION 'CONVERSION_EXIT_ABPSP_INPUT'

50

CONFIDENTIAL


EXPORTING input = ls_/ARBA/_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 WHERE bukrs = ls_/ARBA/_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/_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


CONFIDENTIAL

51

*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 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. *ing IDOC Number IF i_idoc_data-segnam = 'E1EDK01'. e_rbkpv-sgtxt = i_idoc_data-docnum. e_change = 'X'. ENDIF.


7.4.3 Code used in INCLUDE ZXM08U26 for the existing integration The following is the code used in the INCLUDE ZXM08U26 customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_INCL_INCOMING_INVOICE02 INCLUDE statement. *&-----------------------------------------------------------------* *& Include ZXM08U26 * *&-----------------------------------------------------------------* * move the data which needs to be posted directly to G/L 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.

52

CONFIDENTIAL


* Apply OSS Note 385756 e_rbkpv-xmwst = 'X'. e_change = 'X'.


7.5

ERP-initiated invoice

The following are the newly added parameters and the modified customer exits for the ERP-initiated invoice transaction:

Parameters Maintain the new INVOICE_OUTPUT_TYP parameter as described in the following table: Previous name

Current name

Whether new

Details

INVOICE_OUTPUT_TYP

New

Stores the output type con figured for MR application in NACE. If you maintain this parame ter with the output type, then the ERP-initiated invoice function module generates GSVERF IDocs. If you do not maintain this parameter, then the ERP-ini tiated invoice function mod ule uses the default output type as ‘ERS’ and generates GSVERF Idoc.

/ARBA/

INVOICE_DOC_OPTION

INVOICE_DOC_OPTION

Renamed

To send the XBLNR – refer ence document number as the Invoice ID to Ariba Net work.


CONFIDENTIAL

53

Previous name

Current name

/ARBA/INVOICE_DOC_TYPE INVOICE_DOC_TYPE

Whether new

Details

Renamed

Stores doc types for the ERPinitiated invoice and invoice status update. If you maintain this parame ter with the document types, then the ERP-initiated invoice function module retrieves in voices for the specified docu ment types. If you do not maintain this parameter, then the ERP-ini tiated invoice function mod ule retrieves invoices for the document types maintained in the table IN VOICE_DOC_TYPE. To specify another general document type for invoices, for example, RE. Create the same variable and field name as RE in another row and increment the Num ber value to 2 with the selec tion value as RE. To store non-PO invoices cre ated in SAP ERP or SAP S/ 4HANA and reversed or can celed using FB08 (KA) and FI invoices (non-PO invoices)

54

CONFIDENTIAL


Customer exit Replace the code that is used to configure an existing customer exit with the corresponding INCLUDE statement as described in the following table: New INCLUDE statement Customer exit name and



Functional module

integration)


INCLUDE /ARBA/


INCLUDE

INCL_INVOICE_GET_DE

INCLUDE /ARBA/

ARBCIG_INCL_INVOICE

TAILS /

INCL_INVOICE_GET_DE

_GET_DETAIL IF

EXIT_SAPLMRMN_001

TAILS customer exit, see

FOUND

Code used in INCLUDE / ARBA/ INCL_INVOICE_GET_DE TAILS for the existing inte gration [page 55] INCLUDE ZX050U01 /


INCLUDE

EXIT_SAPLF050_001

INCLUDE ZX050U01 cus

ARBCIG_INCL_ERPCC_F

tomer exit, see Code used in

I_INV_ITEM IF FOUND

INCLUDE ZX050U01 for the existing integration [page 56] INCLUDE ZX050U07 /


INCLUDE

EXIT_SAPLF050_007

INCLUDE ZX050U07 cus

ARBCIG_INCL_ERPCC_F

tomer exit, see Code used in

I_INV_HDR IF FOUND

INCLUDE ZX050U07 for the existing integration [page 56]

7.5.1 Code used in INCLUDE /ARBA/ INCL_INVOICE_GET_DETAILS for the existing integration The following is the code used in the INCLUDE /ARBA/INCL_INVOICE_GET_DETAILS customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_INCL_INVOICE_GET_DETAIL IF FOUND INCLUDE statement. /arba/cl_invoice_get_details=>invoice_get_details( EXPORTING if_ident = if_ident is_data_ers = is_data_ers is_data_rap = is_data_rap is_data_kons = is_data_kons if_segnam = if_segnam


CONFIDENTIAL

55

CHANGING ct_idoc_data = ct_idoc_data[] ).

Related Information ERP-initiated invoice [page 53]

7.5.2 Code used in INCLUDE ZX050U01 for the existing integration The following is the code used in the INCLUDE ZX050U01 customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_INCL_ERPCC_FI_INV_ITEM IF FOUND INCLUDE statement. 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.


7.5.3 Code used in INCLUDE ZX050U07 for the existing integration The following is the code used in the INCLUDE ZX050U07 customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_INCL_ERPCC_FI_INV_HDR IF FOUND INCLUDE statement. /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 ).

56

CONFIDENTIAL



7.6

Invoice status update

The following are the parameters that are newly added to the invoice status update transaction:  Note The name of the input proxy structure has been changed for this transaction. You must adjust the BAdI implementation accordingly.

Parameters Maintain the new parameters as described in the following table: Previous name

Current name

Whether new

Details

ISU_BTE_ENABLED

New

Enable or disable the SAP Ariba provided enhance ments for invoice status up date.

/ARBA/AVOID_DUPLI

AVOID_DUPLICATE_ISU_PP

Renamed

CATE_ISU_PP

To ensure that duplicate en tries for invoice status up date are not sent to Ariba Network.

INVOICE02_LOGICAL_SYS

New

TEM

To identify the partner num ber of the sender of invoices that are created in Ariba Net work, and sent as IDoc but fails to post on SAP ERP.

/ARBA/

INVOICE_DOC_OPTION

Renamed

INVOICE_DOC_OPTION

To send the XBLNR – refer ence document number as the invoice ID to Ariba Net work.

/ARBA/INVOICE_DOC_TYPE INVOICE_DOC_TYPE


Renamed

Stores doc types for invoices.

CONFIDENTIAL

57

Previous name

Current name

Whether new

Details

/ARBA/

IN

Renamed

To store doc type required for

IN

VOICE_DOC_TYPE_FULL_AU

full automatic payment for

VOICE_DOC_TYPE_FULL_AU TO

invoice status update.

TO /ARBA/

IN

IN

VOICE_DOC_TYPE_FULL_M

Renamed

To store doc type required for full manual payment for in

VOICE_DOC_TYPE_FULL_M

ANUAL

voice status update

ANUAL /ARBA/

INVOICE_DOC_TYPE_PAR

INVOICE_DOC_TYPE_PAR

TIAL

Renamed

To store doc type required for partial payment for invoice

TIAL

status update

/ARBA/

INVOIC02_REJECT_STATUS

Renamed

To display status number of

INVOIC02_REJECT_STATUS

the rejected invoice. If you do not specify a value, the de fault value would be 51. CHECK_XBLNR_EMPTY

New

To filter the SAP generated invoices with blank reference document number to prevent any error when sent to Ariba Network.

Related Information Prerequisites for migrating the invoice status update transaction [page 17]

7.7

Payment proposal

The name of the input proxy structure has been changed for this transaction. You must adjust the BAdI implementation accordingly when migrating from Ariba Network Adapter for SAP NetWeaver for Ariba Cloud Integration Releases 8.0, 9.0, 9.0 SP1, or 9.0 SP2.

58

CONFIDENTIAL


7.8

Payment remittance request

The following parameter is renamed and the customer exit is added for the payment remittance request transaction:

Parameters Maintain the renamed ORBIAN_PAYMENT_METHOD parameter: Previous name

Current name

Whether new

Details

OrbianPaymentMethod

ORBIAN_PAY

Renamed

To provide the payment con



Note

MENT_METHOD

figuration method in SAP ERP and SAP S/4HANA for Orbian payment method.

This parameter was available with SAP Proc ess Integration.

Customer exit Configure the new customer exit using the corresponding INCLUDE statement as described in the following table: Customer exit name and Functional module

INCLUDE

INCLUDE ZXF08U01 / EXIT_SAPLIEDP_001

Include ARBCIG_INCL_PAYMENT_REMITTANCE IF FOUND

For more information, see How to implement the customer exit for payment remittance to fill data into custom segments [page 59].

7.8.1 How to implement the customer exit for payment remittance to fill data into custom segments Prerequisites You are required to the following segments that need enhancements using the transaction code OBAZ


CONFIDENTIAL

59

Message Type

Basic Type

Extension

Segment Type

REMADV

ARBCIG_REMADV

–

E1IDKU1

REMADV

ARBCIG_REMADV

–

E1EDKA1

REMADV

ARBCIG_REMADV

–

E1IDB02

REMADV

ARBCIG_REMADV

–

E1IDPU1

Context To implement a customer exit to fill data into custom segments, perform the following steps:  Note For more information about this exit, see SAP Note: 1248868 IDoc generation.

: exits for PEXR2003/PEXR2002

Procedure 1. Run the transaction code SPRO. The Customizing: Execute Project screen appears. 2. Click SAP Reference IMG. The Display IMG screen appears. 3. Navigate to

Integration with Other mySAP.com Components

Ariba Network Integration

Application Specific Settings

SAP Ariba Cloud Integration Gateway Payment Remittance Request .

4. Click IMG-Activity for Implement Customer Exit for Payment Remittance to Fill Data into Segment. The Project Management of SAP Enhancements screen appears. 5. Create a new project. For example, ZREMADV 6. Click Create. 7. Click Enhancement Assignments. The Create Object Directory Entry screen appears. 8. Enter values for the following: ○ Object: R3IR CMOD ZREMADV ○ Package: Customer-specific value 9. Click Save. 10. In the Enhancement text box, enter FEDI0003 and then click Enter. 11. Click Components.

60

CONFIDENTIAL


12. Double-click EXIT_SAPLIEDP_001. 13. In the Function Builder: Display EXIT_SAPLIEDP_001 page, double-click INCLUDE ZXF08U01. 14. Add the following code: Include ARBCIG_INCL_PAYMENT_REMITTANCE IF FOUND 15. Click Activate. 16. Go back and activate the exit also.

7.9

Remittance advice

This transaction was introduced in Ariba Network Adapter for SAP NetWeaver 8.0. In the Ariba Network Adapter for SAP NetWeaver for Ariba Cloud Integration Releases 8.0, 9.0, 9.0SP1, and 9.0 SP2, the business logic for this transaction has been implemented using the /ARBA/CL_REMITTANCE_ADVICE or the /ARBA/CL_REMITTANCE_ADVCE_IMPL class. SAP Ariba Cloud Integration Gateway add-on uses the new CL_ARBCIG_REMITTNCE_ADVCE_IMPL class. Also, the method CHANGE is not available with SAP Ariba Cloud Integration Gateway add-on. If you have implemented any BAdI or implicit enhancement for this transaction, you must reimplement the business logic accordingly after you migrate to SAP Ariba Cloud Integration Gateway.

7.10

Service sheet

In this release, the interface has been modified from RFC /ARBA/ENTRYSHEET_CREATE to ESOA service CL_ARBCIG_ENTRYSHEET_IMPL. The BAdI name has been changed from /ARBA/SES_CREATE to ARBCIG_SES_CREATE. So, you must reimplement the BAdI. However, the business logic remains the same.

7.11

Service sheet response

Along with the structure of the proxy, the name of the proxy has also been changed from /ARBA/SESR_UPDATE to ARBCIG_SESR_UPDATE. Because of these changes, you must adjust the BAdI implementation accordingly. To define message output control for service sheet response, the /ARBA/ENTRYSHEET_UPDATE program was used in the Ariba cloud integration adapter. For this task, SAP Ariba Cloud Integration Gateway uses the ARBCIG_ENTRYSHEET_UPDATE program.  Note The method CHANGE_SES_RESPONSE is not available with SAP Ariba Cloud Integration Gateway. If you have implemented the CHANGE_SES_RESPONSE method while integrating this transaction with your SAP


CONFIDENTIAL

61

ERP or SAP S/4HANA using SAP Ariba network adapter, you must reimplement the logic of this method in a BAdI available with SAP Ariba Cloud Integration Gateway. You can also specify your customizations, if any, using the SESR_AN parameter.

7.12

Liability transfer

This transaction was introduced in Ariba Network Adapter for SAP NetWeaver for Ariba Cloud Integration Release 8.0. In the Ariba Network Adapter for SAP NetWeaver for Ariba Cloud Integration Releases 8.0, 9.0, 9.0SP1, and 9.0 SP2, the business logic for this transaction has been implemented using the /ARBA/ CL_LIABILITY_TRANSFER class. SAP Ariba Cloud Integration Gateway add-on uses the new CL_ARBCIG_LIABLTY_TRANSFR_IMPL class. Also, the method CHANGE is not available with SAP Ariba Cloud Integration Gateway add-on. If you have implemented any BAdI or implicit enhancement for this transaction, you must reimplement the business logic accordingly after you migrate to SAP Ariba Cloud Integration Gateway.

7.13

Component consumption request

This transaction was introduced in Ariba Network Adapter for SAP NetWeaver 9.0. In the Ariba Network Adapter for SAP NetWeaver for Ariba Cloud Integration Releases 9.0, 9.0SP1, and 9.0 SP2, the business logic for this transaction has been implemented using the /ARBA/CL_COMPNT_CONSUMPTN_IMPL class. SAP Ariba Cloud Integration Gateway add-on uses the new CL_ARBCIG_COMPNT_CONSUMPN_IMPL class. The proxy structure has been changed for this transaction. If you have implemented any BAdI or implicit enhancement for this transaction, you must reimplement the business logic accordingly after you migrate to SAP Ariba Cloud Integration Gateway.

7.14

Component acknowledgment

This transaction was introduced in Ariba Network Adapter for SAP NetWeaver for Ariba Cloud Integration Release 9.0. In the Ariba Network Adapter for SAP NetWeaver for Ariba Cloud Integration Releases 9.0, 9.0SP1, and 9.0 SP2, the business logic for this transaction has been implemented using the /ARBA/CL_COMPONENT_ACK_IMPL class. SAP Ariba Cloud Integration Gateway add-on uses the new CL_ARBCIG_COMPONENT_ACK_IMPL class. The proxy structure has been changed for this transaction. If you have implemented any BAdI or implicit enhancement for this transaction, you must reimplement the business logic accordingly after you migrate to SAP Ariba Cloud Integration Gateway.

62

CONFIDENTIAL


7.15

Ship notice request

This transaction was introduced in Ariba Network Adapter for SAP NetWeaver 9.0. The proxy structure has been changed for this transaction. You must adjust the BAdI implementation accordingly. If you are migrating from SAP Ariba Network Adapter for SAP NetWeaver 9.0 to SAP Ariba Cloud Integration Gateway, maintain the parameters as described in the following table: For more information, see Migrating advanced ship notice, dispatch delivery notification, and component ship notice transactions [page 39]

Parameters Maintain the following new parameters: Previous name

Current name

Whether new

Details

/ARBA/

CSC_COMP_SHIP_MVMT_T

Renamed

Required for the component

CSC_COMP_SHIP_MVMT_T

YP

shipment (single step and

YP

two steps) to maintain the movement type. TRIGGER_CSN_ON_DELIV

New

ERY

Set this parameter to trigger component ship notice dur ing delivery process.

DONOT_TRIG

New

GER_CSN_DURING_PGI

Set this parameter to not trigger component ship no tice through PGI.

7.16

Product activity message

This transaction was introduced in Ariba Network Adapter for SAP NetWeaver for Ariba Integration Release 9.0. In Ariba Network Adapter for SAP NetWeaver for Ariba Integration Releases 9.0 and 9.0 SP1, the MB_DOCUMENT_BADI BAdI has been implemented using the /ARBA/CL_IM_PROA_PUBLISH class. SAP Ariba Cloud Integration Gateway add-on uses the CL_ARBCIG_PROA_CSNPGI_PUB_IMPL implementation class. Also, the proxy structure has been changed for this transaction. If you have implemented ARIBA delivered / ARBA/PRODUCT_ACTIVITY BAdI, re-implement the business logic in the ARBCIG_BADI_PRODUCT_ACTIVITY BAdI accordingly. For more information, see SAP Ariba Cloud Integration Gateway configuration guide.


CONFIDENTIAL

63

Related Information Prerequisites for migrating the product activity message transaction [page 17]

7.17

Product replenishment message

This transaction was introduced in Ariba Network Adapter for SAP NetWeaver for Ariba Cloud Integration Release 9.0 SP1. In the Ariba Network Adapter for SAP NetWeaver for Ariba Cloud Integration Releases 9.0 SP1 and 9.0 SP2, the business logic for this transaction has been implemented using the /ARBA/CL_SMI_REPLENISHMT_IMPL class. SAP Ariba Cloud Integration Gateway add-on uses the new CL_ARBCIG_SMI_REPLNISHMNT_IMPL class. The proxy structure has been changed for this transaction. If you have implemented any BAdI or implicit enhancement for this transaction, you must re-implement the business logic accordingly after you migrate to SAP Ariba Cloud Integration Gateway.  Note For the customers migrating from Ariba Network Adapter for SAP NetWeaver 8.0 or 9.0 to SAP Ariba Cloud Integration Gateway: If you want to use the product replenishment message transaction, configure this transaction separately. For more information, see SAP Ariba Cloud Integration Gateway configuration guide.

64

CONFIDENTIAL


8

Modifications to transactions ed by SAP Ariba Strategic Sourcing solutions

This chapter includes only the transactions ed by SAP Ariba Strategic Sourcing solutions that have been modified for integrating with SAP Ariba Cloud Integration Gateway. The sections in this chapter list the changes in the following areas for these transactions: ● Parameters (new and modified) ● Customer exits with the new INCLUDE statements  Note The configurations of the quote message and the contract request transactions are migrated from the SAP ERP or SAP S/4HANA systems to SAP Ariba Cloud Integration Gateway. For more information, see the following topics: ● About migrating the configurations of transactions from SAP ERP to SAP Ariba Cloud Integration Gateway [page 25] ● Creating a table to map values of pricing condition parameters in SAP Ariba Cloud Integration Gateway [page 40] For more information on maintaining parameters and implementing customer exits for the transactions ed by SAP Ariba Strategic Sourcing solutions, see the Configuring transactions ed by SAP Ariba Sourcing and SAP Ariba Contracts section in the SAP Ariba Cloud Integration Gateway configuration guide.

SAP Ariba Cloud Integration Gateway migration guide Modifications to transactions ed by SAP Ariba Strategic Sourcing solutions

CONFIDENTIAL

65

8.1

Request for quotation

The following are the parameters and customer exit that are modified for the request for quotation transaction:

Parameters Maintain the following renamed parameters: Previous name

Current name


Details

/ARBA/RFQ_EXTER

RFQ_EXTERNAL_NOTE

Renamed

To send the long text descrip

NAL_NOTE

tion specified at the headerlevel for external s in the Request for Quotation

/ARBA/RFQ_EXTER

RFQ_EXTERNAL_NOTE

Renamed

NAL_NOTE

To send the long text descrip tion specified at the line-item level for external s in the Request for Quotation

/ARBA/RFQ_INTER

RFQ_INTERNAL_NOTE

Renamed

NAL_NOTE

To send the long text descrip tion specified at the headerlevel for internal s in the Request for Quotation

/ARBA/RFQ_INTER

RFQ_INTERNAL_NOTE

Renamed

NAL_NOTE

To send the long text descrip tion specified at the line-item level for internal s in the Request for Quotation.

RFQ_DISABLED

New

To disable the RFQ integra tion. This parameter setting prevents SAP Ariba Sourcing from receiving and process ing RFQs from an SAP ERP system.

66

CONFIDENTIAL


Customer exit Replace the code that is used to configure an existing customer exit with the corresponding INCLUDE statements as described in the following table: New INCLUDE statement Customer exit name and



Functional module

integration)


INCLUDE ZXM06U02 /


INCLUDE

EXIT_SAPLEINM_002


ARBCIG_QUOTE_REQUES


T_002 IF FOUND

in INCLUDE ZXM06U02 for the existing integration [page 67] INCLUDE ZXM06U33 /


INCLUDE

EXIT_SAPLEINM_011


ARBCIG_QUOTE_REQUES


T_011 IF FOUND

in INCLUDE ZXM06U33 for the existing integration [page 68]

8.1.1 Code used in INCLUDE ZXM06U02 for the existing integration The following is the code used in the INCLUDE ZXM06U02 customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_QUOTE_REQUEST_002 IF FOUND INCLUDE statement.  Sample Code call function exporting ekko lfa1 object tables int_edidd int_ekpo call function exporting xekko xlfa1 xlfb1 dobject tables int_edidd xekpo xeket dekek_x dekeh dsadr

'/ARBA/RFQ_GET_DETAILS' = xekko = xlfa1 = dobject = int_edidd = xekpo. '/ARBA/ORDENQ_DETAILS' = = = =

xekko xlfa1 xlfb1 dobject

= = = = = =

int_edidd xekpo xeket dekek_x dekeh dsadr


CONFIDENTIAL

67

dvbak dvbap dvbkd

= dvbak = dvbap = dvbkd.

Related Information Request for quotation [page 66]

8.1.2 Code used in INCLUDE ZXM06U33 for the existing integration The following is the code used in the INCLUDE ZXM06U33 customer exit for the existing integration. Replace this code using the new INCLUDE ARBCIG_QUOTE_REQUEST_011 IF FOUND INCLUDE statement.  Sample Code DATA: lo_purchaseorder TYPE REF TO /arba/cl_purchaseorder. CREATE OBJECT lo_purchaseorder. CALL METHOD lo_purchaseorder->fill_additional_details EXPORTING dekko = dekko dpekko = dpekko control_record_out = control_record_out dobject = dobject CHANGING dekpo = dekpo[] dpekpo = dpekpo[] deket = deket[] desll = desll[] dint_edidd = dint_edidd[]

Related Information Request for quotation [page 66]

68

CONFIDENTIAL


9

Modifications to transactions ed by SAP Ariba Procurement solutions

This chapter includes only the transactions ed by SAP Ariba Procurement solutions that have been modified for integrating with SAP Ariba Cloud Integration Gateway. The sections in this chapter list the changes in the programs and parameters for these transactions: For more information on maintaining parameters for the transactions ed by SAP Ariba Procurement solutions, see the Configuring transactions ed by Ariba buying solutions section in the SAP Ariba Cloud Integration Gateway configuration guide.

9.1

Purchase order

The program for importing the header status of purchase order has been modified as follows: Program name in Ariba cloud adapter

Program name in SAP Ariba Cloud Integration Gateway

/ARBA/PO_HEADER_STATUS

ARBCIG_PO_HEADER_STATUS

For more information, see the How to create and define message output control for purchase order header status section in the SAP Ariba Cloud Integration Gateway configuration guide.

SAP Ariba Cloud Integration Gateway migration guide Modifications to transactions ed by SAP Ariba Procurement solutions

CONFIDENTIAL

69

9.2

Goods receipt

The following are the parameters that are modified for the goods receipt transaction:

Parameters Maintain the following renamed parameters: Previous name (in version 9.0 SP1)

Current name


Details

/ARBA/

GOODS_RECEIPTS_CREATE

Renamed

Configure time-out settings

GOODS_RECEIPTS_CREATE

(in seconds) for the goods re ceipt export task to prevent it from being locked in the SAP ERP system.

9.3

Service entry sheet

In this release, the interface has been modified from RFC /ARBA/ENTRYSHEET_CREATE to ESOA service CL_ARBCIG_ENTRYSHEET_IMPL. The BAdI name has been changed from /ARBA/SES_CREATE to ARBCIG_SES_CREATE. Though the logic of the BAdI remains the same, you must adjust the BAdI implementation accordingly. To define message output control for service sheet response, the /ARBA/ENTRYSHEET_UPDATE program was used in the Ariba cloud integration adapter. For this task, SAP Ariba Cloud Integration Gateway uses the ARBCIG_ENTRYSHEET_UPDATE program. For service sheet response, the name of the proxy has been changed along with its structure. The name of the proxy has been changed from /ARBA/SESR_UPDATE to ARBCIG_SESR_UPDATE. Because of these changes, you must adjust the BAdI implementation accordingly.  Note The method CHANGE_SES_RESPONSE is not available with SAP Ariba Cloud Integration Gateway. If you have implemented the CHANGE_SES_RESPONSE method while integrating this transaction with your SAP ERP or SAP S/4HANA using SAP Ariba network adapter, you must reimplement the logic of this method in a BAdI available with SAP Ariba Cloud Integration Gateway. You can also specify your customizations, if any, using the SESR_P2P parameter.

70

CONFIDENTIAL


The following are the parameters that are modified for the service sheet transaction:

Parameters Maintain the following renamed parameters for service sheet: Previous name (in version 9.0 SP1)

Current name


Details

/ARBA/ENTRY

ENTRYSHEET_CREATE

Renamed

If the purchase order at SAP

SHEET_CREATE

ERP is in the edit mode, the system does not allow you to create a service entry sheet. Configure the duration (in seconds) for which the sys tem would attempt to create a service entry when the pur chase order at ERP is in edit mode.

9.4

Invoice

The following are the parameters that are modified for the invoice transaction:


Current name


Details

/ARBA/INVOICE_PUSH

INVOICE_PUSH

Re-named

Configure time-out settings (in seconds) for the invoice export task to prevent invoi ces from being locked in the SAP ERP system.


CONFIDENTIAL

71

Related Information About migrating the configurations of transactions from SAP ERP to SAP Ariba Cloud Integration Gateway [page 25]

9.5

Advance payment

The following are the parameters that are modified for the advance payment transaction:


Current name


Details

ADV_PAY_ENABLED

New

Enable or disable the SAP Ariba provided enhance ments for advance payment. If this parameter is not ena bled, the implementation of the

ARBCIG_ADV_PAYMENT_ IMPL BAdI will not be exe cuted.

72

CONFIDENTIAL


9.6

Payment remittance

The following are the program, function module, table, and BAdI that are modified for the payment remittance transaction:

Program The program for exporting payment remittance records from SAP ERP to SAP Ariba Procurement solutions has been modified as follows: Program name in Ariba Network Adapter for SAP NetWea ver

Program name in SAP Ariba Cloud Integration Gateway

/ARBA/CR_REMITTANCE_EXPORT

ARBCIG_REMITTANCE_EXPORT

Database table The database table for the date and time stamp entry for exporting payment remittance records has been modified as follows: Database table in Ariba Network Adapter for SAP Net Weaver

Database table in SAP Ariba Cloud Integration Gateway

/ARBA/REM_DATETM

ARBCIG_REMDATETM

If you are using file-channel based cloud integration, you must copy the date and time stamp entry from the / ARBA/REM_DATETM table, navigate to


SAP Ariba Cloud

Integration Gateway SAP Ariba Procurement Integration General Settings , and enter it in the Ariba On-demand - Remittance Date Time Storage table. You must ensure that the entry follows the YYYYMMDDhhmmss format. If you are using web service based cloud integration, you must get the date and time stamp entry maintained by the Application.Settlement.RemittanceStartDate parameter in SAP Ariba Procurement solutions, navigate to



SAP Ariba Procurement Integration General Settings , and enter it in the Ariba On-demand Remittance Date Time Storage table. You must ensure that the entry follows the YYYYMMDDhhmmss format.


CONFIDENTIAL

73

BAdI The BAdI for modifying the payment remittance data before exporting it to SAP Ariba Procurement solutions has been modified as follows: BAdI in Ariba Network Adapter for SAP NetWeaver


/ARBA/REMIT_EXPORT

ARBCIG_REMIT_EXPORT

You can migrate this BAdI using the Migrate customer-implemented SAP Ariba BAdIs report.

74

CONFIDENTIAL


10 Troubleshooting

For more information, see the Monitoring messages and troubleshooting chapter in the SAP Ariba Cloud Integration Gateway configuration guide.

SAP Ariba Cloud Integration Gateway migration guide Troubleshooting

CONFIDENTIAL

75

11

Revision history

The following table provides a brief history of the updates to this guide. SAP Ariba updates the technical documentation for its cloud solutions if ● software changes delivered in service packs or hot fixes require a documentation update to correctly reflect the new or changed functionality; ● the existing content is incorrect or indicated that important content is missing. SAP Ariba reserves the right to update its technical documentation without prior notification. Most documentation updates will be made available in the same week as the software service packs are released, but critical documentation updates may be released at any time.

Version

Month and year of update

February 2018 SAP Ariba Cloud Integra tion Gateway release April 2018

Updated chapter and section Multiple

Short description of change Updated throughout for the SAP Ariba Cloud Integration Gateway release

ed SAP

Updated to SAP Ariba Supplier Lifecycle and Performance

Ariba Solutions

with SAP Ariba Cloud Integration Gateway

Prerequisites for migrating transac tions to SAP Ariba Cloud Integration Gateway SAP Ariba

May 2018

Multiple

Cloud Integra

Updated throughout for the SAP Ariba Cloud Integration Gateway May 2018 release

tion Gateway SAP Ariba

September 2018

Cloud Integra

Payment remit

Added this new topic for the SAP Ariba Cloud Integration Gateway

tance

September 2018 release

tion Gateway

76

CONFIDENTIAL

SAP Ariba Cloud Integration Gateway migration guide Revision history

Important Disclaimers and Legal Information

Hyperlinks Some links are classified by an icon and/or a mouseover text. These links provide additional information. About the icons: ●

●

Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this: ●

The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

●

SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental Features Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up. The purpose of experimental features is to get early on, allowing customers and partners to influence the future product accordingly. By providing your (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

SAP Ariba Cloud Integration Gateway migration guide Important Disclaimers and Legal Information

CONFIDENTIAL

77

www.ariba.com

Copyright © 2018 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 ed trademarks of Ariba, Inc. in the United States and other countries. Please see http://www.ariba.com/ legal/trademarks for additional trademark information and notices. Ariba Sourcing solutions (On Demand and software) are protected by one or more of the following patents, including without limitation: U.S. Patent Nos. 6,199,050; 6,216,114; 6,223,167; 6,230,146; 6,230,147; 6,285,989; 6,408,283; 6,499,018; 6,564,192; 6,871,191; 6,952,682; 7,010,511; 7,072,061; 7,130,815; 7,146,331; 7,152,043;7,225,152; 7,277,878; 7,249,085; 7,283,979; 7,283,980; 7,296,001; 7,346,574; 7,383,206; 7,395,238; 7,401,035; 7,407,035; 7,444,299; 7,483,852; 7,499,876; 7,536,362; 7,558,746; 7,558,752; 7,571,137; 7,599,878; 7,634,439; 7,657,461; 7,693,747; 8,364,577; and 8,392,317. Patents pending. Other Ariba product solutions are protected by one or more of the following patents: U.S. Patent Nos. 6,199,050, 6,216,114, 6,223,167, 6,230,146, 6,230,147, 6,285,989, 6,408,283, 6,499,018, 6,564,192, 6,584,451, 6,606,603, 6,714,939, 6,871,191, 6,952,682, 7,010,511, 7,047,318, 7,072,061, 7,084,998; 7,117,165; 7,225,145; 7,324,936; 7,536,362; 8,364,577; and 8,392,317. Patents pending. Certain Ariba products may include third party software or other intellectual property licensed from a third party. For information regarding software or other intellectual property licensed from a third party, go to http://www.ariba.com/copyrights.cfm.

THE BEST RUN

Sap Ariba Cloud Integration Gateway Migration Guide 1g205o

Overview 5o1f4z

More details 6z3438

Related Documents c2h70

Sap Ariba Cloud Integration Gateway Migration Guide 1g205o

Ariba Migration 2r103z

Sap Ariba Course Content 1h5m3e

Entrenamiento Sap Ariba 595f5m

Ariba Sap Discovery 303p10

Migration Manual - Integration Framework 5se1v

More Documents from "GayatriPatil01" 6c4e5n

Sap Ariba Cloud Integration Gateway Migration Guide 1g205o