0% found this document useful (0 votes)
795 views162 pages

Day5 3 Migration

The document discusses the SAP Ariba Cloud Integration Gateway (CIG), which allows customers using the SAP Ariba Cloud Integration Network Adapter to migrate their integration to CIG. It provides an overview of CIG and outlines the key pre-migration, migration, and post-migration activities required to migrate transactions, master data, and configurations from the existing integration solution to CIG. These include securing data transfer, maintaining certificates, migrating specific tables and configurations, and additional post-migration configurations.

Uploaded by

y421997
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
795 views162 pages

Day5 3 Migration

The document discusses the SAP Ariba Cloud Integration Gateway (CIG), which allows customers using the SAP Ariba Cloud Integration Network Adapter to migrate their integration to CIG. It provides an overview of CIG and outlines the key pre-migration, migration, and post-migration activities required to migrate transactions, master data, and configurations from the existing integration solution to CIG. These include securing data transfer, maintaining certificates, migrating specific tables and configurations, and additional post-migration configurations.

Uploaded by

y421997
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 162

SAP Ariba Cloud Integration Gateway

Integration Redefined
CONFIDENTIAL
SAP Ariba Cloud Integration Gateway

During this training –

The SAP Ariba Cloud Integration Gateway will be referred to as CIG.

SAP Ariba AddOn will be referred to as AddOn.

SAP Ariba Sourcing Solutions will be referred to as Ariba Sourcing.

SAP Ariba Contracts Solutions will be referred to as Ariba Contracts.

SAP Ariba Procurement Solutions will be referred to as Ariba Procurement.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 2


SAP Ariba Cloud Integration Gateway
Agenda
ü Overview

ü Migration Support Metrics

ü Pre-Migration Activities

ü Migration Activities

ü Post-Migration Activities

ü Modifications to the Supported Transactions

ü Additional Activities

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 3


SAP Ariba Cloud Integration Gateway
Overview
SAP Ariba Cloud Integration Gateway
Overview
If you are using SAP Ariba Cloud Integration Network Adapter to connect your SAP system with
Ariba Network & wish to migrate / move to the SAP Ariba Cloud Integration Gateway, you must first
install one of the following AddOn connected to SAP Ariba Cloud Integration Gateway:

ü SAP Ariba Cloud Integration Gateway AddOn for SAP ERP

ü SAP Ariba Cloud Integration Gateway AddOn for SAP S/4HANA

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 5


SAP Ariba Cloud Integration Gateway
Overview
You can migrate to SAP Ariba Cloud Integration Gateway in following ways –

ü 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, and catalog 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 intact.

ü This enables you to use SAP Ariba Cloud Integration Gateway as an integration mechanism in
addition to the existing integration solutions.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 6


SAP Ariba Cloud Integration Gateway
Overview
High-Level Migration Steps –

Srl Activity Environment Description


1 Enable SAP Ariba Cloud Integration Gateway. SAP Ariba Solutions Enable CIG settings on Ariba Solutions.

2 Download; install & configure Cloud Connector. Within customer firewall SAP Development Tools.

3 Download; install & configure SAP Ariba AddOn. SAP ERP or SAP S/4HANA SAP Service Marketplace.

4 Set up middleware (optional) SAP NW PI / § Enable integration in SAP system


SAP CPI (Private Tenant) § Configure middleware

5 Perform the prerequisite tasks before you migrate SAP ERP or SAP S/4HANA § Securing inbound data transfer from CIG to
the transactions of SAP Ariba solutions, Master the on-premise SAP system.
Data & Catalog from the existing integration § Maintain Certificates
solutions to CIG.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 7


SAP Ariba Cloud Integration Gateway
Overview
High-Level Migration Steps –

Srl Activity Environment Description

6 Run the report to migrate SAP Ariba data from the SAP ERP or SAP S/4HANA § Generic tables for Ariba Network
/ARBA/ database table to the new ARBCIG_ § Generic tables for Ariba Sourcing
database table. § Generic tables for Ariba Sourcing

7 Run the report to migrate the configurations of SAP ERP or SAP S/4HANA § Migrate parameters.
designated transactions from SAP ERP to CIG. § Migrate configurations.

8 Run the report to migrate the implementations of SAP ERP or SAP S/4HANA Migrate BAdIs.
SAP Ariba Business Add-in (BAdI) information
available in your environment.

9 Manually migrate the required SAP Ariba BAdIs SAP ERP or SAP S/4HANA Manually transfer implementations to the
(optional). appropriate method files in the new BAdI objects

10 Perform the post-migration tasks & the additional SAP ERP or SAP S/4HANA Additional configurations in SAP system & in
configurations. CIG.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 8


SAP Ariba Cloud Integration Gateway
Migration Support Metrics
SAP Ariba Cloud Integration Gateway
Migration Support Metrics
You can migrate to SAP Ariba Cloud Integration Gateway from the following SAP Ariba Cloud
Integration release versions:

ü Ariba Network Adapter for SAP NetWeaver 8.0

ü Ariba Network Adapter for SAP NetWeaver 9.0

ü Ariba Network Adapter for SAP NetWeaver 9.0 SP1

ü Ariba Network Adapter for SAP NetWeaver 9.0 SP2

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 10


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities
ü Securing inbound data transfer from CIG to the on-premise SAP system.

ü Maintain Certificates

ü Migrating Master Data & Catalog

ü Migrating the Invoice Status Update transaction

ü Migrating the Product Activity Message transaction

ü Migrating the Purchase Order transaction

ü Migrating the Advance Payment transaction

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 12


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities –
Securing inbound data transfer from CIG to the on-premise SAP system
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities –
Securing inbound data transfer from CIG to the on-premise SAP system.
ü You can use SAP Cloud Connector or a Reverse Proxy to secure inbound data transfer to the
on-premise SAP system.
ü SAP Cloud Connector or a Reverse Proxy ensures secure communication from SAP Ariba Cloud
Integration Gateway to the on-premise SAP system.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 14


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Maintain Certificates
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Maintain Certificates

ü You must maintain certificates in the SAP systems before you start migrating the configurations
of transactions to CIG.

ü Maintaining certificates is a prerequisite for running all the migration reports that enables you to
migrate the configurations of transactions to CIG.

ü To maintain certificates, you must run the TCode SPRO & navigate to Global Settings.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 16


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog

Following activities must be carried out before migrating Master Data & Catalog for Ariba
Procurement solutions & Ariba Sourcing solutions.

ü Removing Data from specific database tables.

ü Deactivate event type linkages.

ü Remove the HR-CA event linkages.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 18


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Removing Data from specific database tables
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Removing Data from specific database tables
Before you start migrating to CIG, you must remove data from the following database tables from
SAP system. You must also ensure that the table is empty.

ü /ARBA/CHANGE_DOC table – If you are planning to migrate database tables for Master Data
for the SAP Ariba Procurement solutions or the Ariba Sourcing solutions.

ü /ARBA/DOC_CHANGE table – If you are planning to migrate database tables for Catalogs for
the Ariba Procurement solutions or the Ariba Sourcing solutions.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 20


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Deactivate event type linkages
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Deactivate event type linkages
Note –

ü Certain Master Data events are connected to object types with the /ARBA/ namespace.

ü As part of using CIG for integration, the namespace of the objects is changed from /ARBA/ to
ARBCIG_.

ü You cannot use these events in CIG without updating the namespace of the object types to
ARBCIG_

ü Migrating these events to CIG would cause data clogging. To avoid data clogging, we need to
deactivate these event type linkages before you migrate Master Data & Catalog to CIG.

ü After you successfully migrate to CIG, you can configure new event linkages connected to object
types with the ARBCIG_ namespace.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 22


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Deactivate event type linkages
Follow these steps –

1. In the SAP Easy Access screen, run the TCode – SWETYPV.

2. In the Change View "Event Type Linkages": Overview screen, select each of the events
mentioned in the table in next 2 slides & double-click Type linkage active against it.

3. In the Change View "Event Type Linkages": Details screen, in the Linkage Setting (Event
Receiver) section, uncheck Linkage Activated box.

4. Click Save.

Please refer to the example shown in the screenshots in 3 slides after the 2 table slides.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 23


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Deactivate event type linkages
Object category Object type Event Receiver type Type Linkage Active
BO /ARBA/0012 COSTCENTERCHANGED CHANGE X
BO /ARBA/0012 COSTCENTERCREATED CREATE X
BO /ARBA/0012 COSTCENTERDELETED DELETE X
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
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 24
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Deactivate event type linkages
Object Category Object Type Event Receiver Type Type Linkage Active
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/USER CLONED USER_CHANGE X
BO BUS1001 CREATED CHANGE X
BO BUS1001006 VIEWCREATED CREATE X
BO BUS3003 STARTVEEKPLAMATNRDEL CHANGE X
BO BUS3003 STARTVENDORMATNRDEL CREATE X
BO BUS3060 STATUSCHANGED CHANGE X
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 25
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Deactivate event type linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 26


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Deactivate event type linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 27


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Deactivate event type linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 28


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Remove the HR-CA event linkages
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Remove the HR-CA event linkages

Follow these steps –

1. In the SAP Easy Access screen, run the TCode – SWEHR3.

2. In the Change View "HR-CA Event Linkage for Customer": Overview screen, select each of
the events mentioned in the table in next slide & click Delete.

3. Click Save.

Please refer to the example shown in the screenshots in 2 slides after the table slide.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 30


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Remove the HR-CA event linkages

OT Object Type Text IT Updat SeqNo Obj. Type Function Module

P Person 1 UPD 0 BUS1065 /ARBA/HRPM_CHANGE_DOCS

P Person 2 UPD 0 PERSDATINT /ARBA/HRPM_CHANGE_DOCS

P Person 105 DEL 0 EMPLCOMM /ARBA/HRPM_CHANGE_DOCS

P Person 105 INS 0 EMPLCOMM /ARBA/HRPM_CHANGE_DOCS

P Person 105 UPD 0 EMPLCOMM /ARBA/HRPM_CHANGE_DOCS

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 31


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Remove the HR-CA event linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 32


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating Master Data & Catalog –
Remove the HR-CA event linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 33


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities –
Migrating the Invoice Status Update transaction
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Invoice Status Update transaction

ü Before migrating the Invoice Status Update (ISU) transaction of Ariba Network to CIG, you must
process the existing data in the /ARBA/AN_ISUINV database table & ensure that the table is
empty.

ü Maintain the new parameters as described in the table in next slide.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 35


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Invoice Status Update transaction
Previous Name Current Name Whether new Details

Enable or disable the SAP Ariba provided enhancements for


ISU_BTE_ENABLED New
ISU.

To ensure that duplicate entries for ISU are not sent to Ariba
/ARBA/AVOID_DUPLICATE_ISU_PP AVOID_DUPLICATE_ISU_PP Renamed
Network.

To identify the partner number of the sender of invoices that are


INVOICE02_LOGICAL_SYSTEM New created in Ariba Network, and sent as IDoc but fails to post on
SAP system.

To send the XBLNR – reference document number as the


/ARBA/INVOICE_DOC_OPTION INVOICE_DOC_OPTION Renamed
invoice ID to Ariba Network.

/ARBA/INVOICE_DOC_TYPE INVOICE_DOC_TYPE Renamed Stores doc types for invoices.


/ARBA/INVOICE_DOC_TYPE_FULL_AUTO INVOICE_DOC_TYPE_FULL_AUTO Renamed To store doc type required for full automatic payment for ISU.
/ARBA/INVOICE_DOC_TYPE_FULL_MANUAL INVOICE_DOC_TYPE_FULL_MANUAL Renamed To store doc type required for full manual payment for ISU.
/ARBA/INVOICE_DOC_TYPE_PARTIAL INVOICE_DOC_TYPE_PARTIAL Renamed To store doc type required for partial payment for ISU.

To display status number of the rejected invoice. If you do not


/ARBA/INVOIC02_REJECT_STATUS INVOIC02_REJECT_STATUS Renamed
specify a value, the default value would be 51.

To filter the SAP generated invoices with blank reference


CHECK_XBLNR_EMPTY New document number to prevent any error when sent to Ariba
Network.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 36


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities –
Migrating the Product Activity Message transaction
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Product Activity Message transaction

ü Before you migrate the Product Activity Message transaction that Ariba Network supports to CIG,
the BAdI implementation of the MB_DOCUMENT_BADI should be removed.

ü In the Ariba Network Adapter for SAP NetWeaver for Ariba Integration Releases 9.0 & 9.0 SP1
MB_DOCUMENT_BADI has been implemented using the /ARBA/CL_IM_PROA_PUBLISH
class. CIG AddOn uses the CL_ARBCIG_PROA_CSNPGI_PUB_IMPL implementation class.

ü The proxy structure has also 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.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 38


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Product Activity Message transaction

To remove BAdI implementation, follow these steps –

1. Run the TCode SE24.


2. In the Object type field of the Class Builder: Initial Screen, enter the name of the implementation
class. For example, /ARBA/CL_IM_PROA_PUBLISH to remove the BAdI implementation that
uses the /ARBA/ CL_IM_PROA_PUBLISH class.
3. Click Use of class / interface.
4. In the Where-Used List Class/Interface dialog box, select the following & click Execute –
ü Business Add-ins
ü Enhancement Implementation
ü Enhancement Spots
5. 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 – ZMB_DOCUMENT_BADI.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 39


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Product Activity Message transaction

To remove BAdI implementation, follow these steps (continued…) –

6. To deactivate BAdI, you can run the SE19 transaction and enter the name of the enhancement
implementation.
7. Click Change & uncheck Implementation is Active check box.
8. Click Save.
9. Alternatively, you can run the SE18 transaction and in the BAdI Name field, enter the BAdI
definition name. For example, enter MB_DOCUMENT_BADI.
10. On the menu bar, click Enhancement Implementation>>>Overview.
11. 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.
12. Click Display>>>Change.
13. Click Deactivate.

Refer to the example shown in the screenshots in next 8 slides.


© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 40
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Product Activity Message transaction

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 41


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Product Activity Message transaction

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 42


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Product Activity Message transaction

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 43


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Product Activity Message transaction

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 44


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Product Activity Message transaction

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 45


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Product Activity Message transaction

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 46


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Product Activity Message transaction

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 47


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Product Activity Message transaction

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 48


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities –
Migrating the Purchase Order transaction
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Purchase Order transaction

ü Before you migrate the Purchase Order transaction that the Ariba Procurement solutions
supports to CIG, you must run the Purchase Order Header Status Pull report.

ü 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

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 50


SAP Ariba Cloud Integration Gateway
Pre-Migration Activities –
Migrating the Advance Payment transaction
SAP Ariba Cloud Integration Gateway
Pre-Migration Activities – Migrating the Advance Payment transaction

ü Remove the existing implementations of the Advance Payment transaction that is integrated with
the SAP system.

ü After you migrate to CIG, you can configure this transaction again.

ü Also remove the BAdI implementation of the BADI_ACC_DOCUMENT.

ü New parameter is introduced for the Advance Payment transaction:


Parameter Name Details
Enable or disable the SAP Ariba provided enhancements for
Advance Payment.
ADV_PAY_ENABLED
If this parameter is not enabled, the implementation of the
ARBCIG_ADV_PAYMENT_IMPL BAdI will not be executed.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 52


SAP Ariba Cloud Integration Gateway
Migration Activities
SAP Ariba Cloud Integration Gateway
Migration Activities
ü Overview

ü Migrate data to the new database table

ü Migrate transaction configurations

ü Migrate Ariba BAdIs

ü Manually migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 54


SAP Ariba Cloud Integration Gateway
Migration Activities – Overview
SAP Ariba Cloud Integration Gateway
Migration Activities – Overview
You must first run the standard SAP upgrade program.
There are 3 migration reports provided which has to be executed in the given order –

Order Report Name Purpose

To migrate data from the /ARBA/ database table to the new ARBCIG_ database
Step 1 Migrate SAP Ariba data to new database tables
table.

Step 2 Migrate transaction setups to CIG To migrate the configurations of designated transactions from SAP system to CIG.

Step 3 Migrate customer-implemented SAP Ariba BAdIs To migrate Business Add-in (BAdI) information from SAP system to CIG.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 56


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
ü The Migrate SAP Ariba data to new database tables report is the first migration report that
you run after completing the standard SAP upgrade.
ü As part of integrating SAP system with Ariba Network; Ariba Procurement & Ariba Sourcing
using CIG, the namespace of the existing database tables has been changed from /ARBA/ to
ARBCIG_.
ü This report enables you to migrate data from the database tables with the /ARBA/ namespace to
the new tables with the ARBCIG_ namespace.
ü You must migrate data from the database tables with /ARBA/ namespace to the new tables with
ARBCIG_ namespace.
ü The details of the existing database tables with /ARBA/ namespace & their corresponding new
tables with ARBCIG_ namespace is described in the table in next 2 slides.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 58


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Existing Table Name New Table Name
/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/TVARV ARBCIG_TVARV
/ARBA/GR ARBCIG_GOODSRCPT
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 59
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Existing Table Name New Table Name
/ARBA/PARAM_TAB ARBCIG_TVARV
/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/PROXYPARAM ARBCIG_PRXYPARAM
/ARBA/TAXCAT_MAP ARBCIG_TAXCATMAP
/ARBA/RFQ_TEXTS ARBCIG_RFQTEXTS
/ARBA/REQPARAM ARBCIG_REQPARAM
/ARBA/PR_HISTORY ARBCIG_PRHISTORY
ESSR ARBCIG_SES
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 60
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Follow these steps –
1. In the SAP Easy Access screen, run the TCode – arbcig_migration – The SAP Easy Access
SAP Ariba Migration: Add on screen appears.
2. Under SAP Menu, double-click Migrate SAP Ariba data to new database tables – The
Migrate SAP Ariba data to new database tables screen appears.
3. Perform following all or required actions & click Execute –
a) Under Select one or more transactions to migrate the corresponding data, select the checkboxes for
Ariba Network, SAP Ariba Procurement solutions & SAP Ariba Strategic Sourcing solutions and select
the transactions for which you want to migrate associated database tables.
b) Under Shared data, select Master Data, or Catalog, or both as required.

Please refer to the example shown in the screenshots in next 3 slides.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 61


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 62


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 63


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 64


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Additional Information –

ü When you select the checkbox for Ariba Network, SAP Ariba Procurement solutions & 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 categories are –
Ø General Tables for Ariba Network
Ø General Tables for SAP Ariba Procurement
Ø General Tables for SAP Ariba Strategic Sourcing

ü The first checkbox in each category is for migrating the general tables for that category & is
checked by default for each category.

ü This indicates that the data from the general tables is migrated after you press the Execute
button.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 65


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Additional Information (continued…) –

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

ü Under Shared data, you can select Master data or Catalog, or both as required & migrate the
database tables associated with them to the ARBCIG_ tables.

Please refer to the example shown in the screenshot in next slide.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 66


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 67


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Additional Information (continued…) –

ü In the SAP Ariba Procurement solutions category, you can use filters to select a specific set of
transactions & migrate the data for them to CIG.

ü These filters help you improve efficiency of migration by avoid migrating data pertaining to all
transaction to CIG.

ü The filters are available for following transaction documents –


Ø Requisition (Req.)
Ø Purchase Order (PO)
Ø Service Entry Sheet (SES)
Ø Contracts
Ø Goods Receipt (GR)
Ø Payment Export Request

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 68


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Additional Information (continued…) –

ü SAP Purchase Requisition Number – Filter by a specific range of requisitions.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 69


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Additional Information (continued…) –

ü SAP Purchase Order Number – Filter by a specific range of requisitions. Along with migrating
Purchase Order Header Status to CIG, you must migrate the Goods Receipt & the Payment
Export Request transactions as well.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 70


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Additional Information (continued…) –

ü Service Entry Sheet Number – Filter by a specific range of Service Entry Sheet Number or
Filter by a specific External Entry Sheet Number.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 71


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Additional Information (continued…) –

ü Goods Receipt Creation Date – Filter by the Creation Date of the Goods Receipt.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 72


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Additional Information (continued…) –

ü Payment Export Request –

Ø Document Number filter by a specific range of document numbers

Ø Fiscal Year filter by one or more fiscal years that applies to the payment export requests

Ø Document Type filter by one or more document types

Ø Created Date filter by the date of creation of the payment export requests

Ø Company Code filter by the company code

Ø Invoicing Party filter by the party for which the payment export request has been created

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 73


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Additional Information (continued…) –

ü Payment Export Request (continued…) –

Ø 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

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 74


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate data to the new database table
Additional Information (continued…) –

ü Payment Export Request (continued…) –

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 75


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate transaction configurations
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate transaction configurations
ü Once you migrate data from the /ARBA/ database table to the ARBCIG_ database table in your
SAP system, you can migrate the configurations of certain transactions from your SAP system
to CIG.

ü You can migrate parameters & database tables associated with the designated transactions
from Ariba Network; SAP Ariba Procurement solutions & SAP Ariba Sourcing solutions.

ü Before you run this report, you must maintain certificates in your SAP system.

ü The details of the parameters that you can migrate from SAP system to CIG are listed in the
table in the next 2 slides.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 77


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate transaction configurations
Solution Transaction SAP Parameter Name SAP Field Name CIG Field Name

QUOTE COSTCENTER Cost Center

QUOTE GL_ACCOUNT G/L Account

QUOTE ASSET Asset

QUOTE SUB_NUMBER Asset Subnumber

QUOTE ORDER Order


Quote Automation
Quote Message
(supported by Ariba Network)
QUOTE WBS_ELEMENT WBS Element

QUOTE ACCTASSCAT Account Assignment Category

QUOTE DOC_TYPE Quote Document Type

QUOTE ONETIME_VENDOR Quote Automation Vendor ID

QUOTE PLANT Quote Automation Plant


© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 78
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate transaction configurations

Solution Transaction SAP Parameter Name SAP Field Name CIG Field Name

Requisition /ARBA/PURREQ_DOC_TYP SAP Document Type

BAPI_PO_CREATE_DOC_TYPE SAP Document Type

BAPI_PO_CREATE_ERP_DOC_TYPE SAP CC Document Type

SAP Ariba Procurement solutions Purchase Order

/ARBA/HEADER_TEXT_ID Header Text ID

/ARBA/ITEM_TEXT_ID Item Text ID

Invoice /ARBA/INVOICE_DOC_TYPE SAP Document Type

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 79


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate transaction configurations
The following table lists the details of the database tables that you can migrate from SAP system to
CIG.

Solution Transaction Database Table Name CIG Lookup Table Name

Requisition /ARBA/TAX_CHECK TaxOnCompanyCode

SAP Ariba Procurement solutions Purchase order /ARBA/COND_MAP ProcurementConditionType

Invoice /ARBA/WHT_TYPE WithholdingTaxMap

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 80


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate transaction configurations
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.

Prerequisites –

1. Maintain Certificates before you run this report.


2. Run the Migrate SAP Ariba data to new database tables report before you run this report.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 81


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate transaction configurations
Process to migrate the configurations of transactions from SAP system to CIG –

1. In SAP Easy Access screen, run the TCode ARBCIG_MIGRATION – The SAP Easy Access
SAP Ariba Migration: Add on screen appears.
2. Under SAP menu, double-click Migrate transaction setups to SAP Ariba Cloud Integration
Gateway – The Migrate transaction setups to SAP Ariba Cloud Integration Gateway
screen appears.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 82


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate transaction configurations
Process to migrate the configurations of transactions from SAP system to CIG (continued…) –
3. Perform the actions listed in the next slide.
a) 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 user name, password, proxy host name, and port number to connect
to the proxy host.
b) Specify whether you are connecting to the test installation or the production installation of SAP Ariba
Cloud Integration Gateway.
c) 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.
4. Click Execute.

Please refer to the example shown in the screenshots in 3 slides after next slide.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 83
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate transaction configurations

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 84


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate transaction configurations

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 85


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate transaction configurations

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 86


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
ü After you migrate the setups of transactions from SAP system to CIG, you can proceed to
migrate the customer-implemented SAP Ariba BAdIs to CIG.
ü SAP Ariba BAdIs that customers have implemented in their environment contain the
configurations specific to their environment.
ü A customer-implemented SAP Ariba BAdI contains one or more BAdI implementations.
ü Each of these BAdI implementations contains one or more methods.
ü Migrating these SAP Ariba BAdIs to CIG includes the certain manual steps.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 88


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
Steps to manually migrate the SAP Ariba BAdIs to CIG –
1. 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.
2. Download each implementation of the BAdI to your computer.
3. 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_.
4. 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.
5. Create the new BAdI implementation using the updated method files.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 89


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
The following methods available with the old SAP Ariba BAdIs have been removed. These 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_EACHACCOUNT

UPDATE_EACHITEM

CONTRACT_PREPROCESSING

/ARBA/QUOTEMESSAGE
CONTRACT_POSTPROCESSING

CONTRACT_MODIFY_ITEM

CONTRACT_MODIFY_ACCOUNT

CONTRACT_MODIFY_CONDITION

FI_INVOICE_CREATE /ARBA/INVOICE_CREATE
PUBLISH_PO_CREATE1
/ARBA/PO_IMPORT
(This is replaced by the new PUBLISH_PO_CREATE method)
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 90
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
The list of the names of the SAP Ariba BAdIs available in Ariba Network Adapter for SAP
NetWeaver & their corresponding BAdIs available in CIG.
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
/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
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 91
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
The list of the names of the SAP Ariba BAdIs available in Ariba Network Adapter for SAP
NetWeaver & their corresponding BAdIs available in CIG (continued…).
BAdI in Ariba Network adapter for SAP NetWeaver BAdI in SAP Ariba Cloud Integration Gateway
/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_RECPT_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
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 92
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
The following are the new BAdIs available in CIG –

ü ARBCIG_ES_ATTACHMENT_UTIL

ü ARBCIG_ES_COMMENT_UTIL

ü ARBCIG_ES_SESR_UPDATE

ü ARBCIG_PARAM_UPDATE

ü ARBCIG_SEG_INSERT

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 93


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
The Migrate customer-implemented SAP Ariba BAdIs report is the third migration report that you
must run.
Prerequisites –
1. Before you run this report, you must run the following migration reports in the given order –
a) Migrate SAP Ariba data to new database tables.
b) Migrate transaction setups to SAP Ariba Cloud Integration Gateway.

2. Create a folder in the local drive of your computer & designate it for downloading the
implementations of SAP Ariba BAdIs available in your environment.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 94


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
Process to migrate SAP Ariba BAdIs to CIG –
1. In SAP Easy Access screen, run the TCode arbcig_migration – The SAP Easy Access SAP
Ariba Migration: Add on screen appears.
2. Under SAP menu, double-click Migrate customer-implemented SAP Ariba BAdIs – The
Migrate customer-implemented SAP Ariba BAdIs screen appears.
3. You can view SAP Ariba BAdIs that are implemented in your environment listed in a table by
their active implementation names.
4. In the Select a Folder field, browse & select the designated folder in the local drive of your
computer where you want to download the implementations of your customer-implemented
SAP Ariba BAdIs.
5. 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 CIG & click Download Existing Implementations.
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 95
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
Process to migrate SAP Ariba BAdIs to CIG (continued…) –
6. In the Display Logs screen, under Date/Time/User, click the entry that represents the BAdI
implementation download activity you have performed. You can view the following status of the
record –
a) Path to the designated folder in your local drive where you have downloaded the BAdI
implementations.
b) Names of the SAP Ariba BAdI; their implementation names; class & 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 downloaded. 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.
c) Parsing completion status.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 96


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
Process to migrate SAP Ariba BAdIs to CIG (continued…) –
7. After you manually update all the method files, in the Migrate customer-implemented SAP Ariba
BAdIs screen, select the updated BAdI implementation & 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.
8. Under Create Implementation, the Enhancement Spot automatically gets 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.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 97


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
Process to migrate SAP Ariba BAdIs to CIG (continued…) –
9. In the Create Enhancement Implementation dialog box, enter the Enhancement
Implementation name & other details to start creating the BAdI implementation. You must use
the updated method files to create the new BAdI implementations.
10. In the Create BAdI Implementations for Existing BAdI Definitions screen, you can perform the
following steps –
a) In the BAdI Implementation field, enter the name for the BAdI implementation
b) In the Implementation Class field, enter the BAdI implementation class
c) In the BAdI Definition field, select the definition of the BAdI
d) Click OK.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 98


SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs
Process to migrate SAP Ariba BAdIs to CIG (continued…) –
10. In the Create BAdI Implementations for Existing BAdI Definitions screen, you can perform the
following steps (continued…) –
e) Do not enter any code in the method file. Instead, you must upload the updated method files for the
BAdI implementation from the local drive of your computer. To upload the method file, navigate to
Utilities >>> More Utilities >>> Upload/Download >>> Upload & browse & select the method file from
the local drive of your computer.
f) 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 &
click Implementation Overview.

Please refer to the example shown in the screenshots in next 13 slides.


© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 99
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 100
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 101
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 102
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 103
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 104
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 105
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 106
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 107
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 108
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 109
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 110
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 111
SAP Ariba Cloud Integration Gateway
Migration Activities – Migrate Ariba BAdIs

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 112
SAP Ariba Cloud Integration Gateway
Migration Activities – Manually migrate Ariba BAdIs
SAP Ariba Cloud Integration Gateway
Migration Activities – Manually migrate Ariba BAdIs
This is an optional activity.
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.
ü ARBA/CUSTOM_ATTACHMENT
ü /ARBA/GOS_ATTACHMENT
ü /ARBA/PO_FILE_CHANNL
ü /ARBA/CREATE_GR
ü /ARBA/INVOICE_LOAD
ü /ARBA/PO_MODIFY
ü /ARBA/CONTRACT_RESPONSE

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 114
SAP Ariba Cloud Integration Gateway
Migration Activities – Manually migrate Ariba BAdIs
Note –
ü The implementation for /ARBA/CUSTOM_ATTACHMENT & /ARBA/GOS_ATTACHMENT BadIs
must be transferred to the new ARBCIG_BADI_ATTACHMENT_UTIL BAdI.
ü Following BAdIs are deprecated and are not supported on CIG –
Ø EXPENSE INTEGRATION
Ø P2P REMITTANCE

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 115
SAP Ariba Cloud Integration Gateway
Post-Migration Activities
SAP Ariba Cloud Integration Gateway
Post-Migration Activities
ü Overview

ü Modifying Partner Profile Settings

ü Configure Event Linkages

ü Configure Logical Ports & Service Names

ü Migrate Transactions

ü Create Table Map Values

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 117
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Overview
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Overview
ü After you migrate to CIG, you need to perform the set of tasks that are required to integrate
SAP system with Ariba Network; Ariba Procurement & Ariba Sourcing using CIG.
ü You also need to perform certain modifications to the transactions that you have migrated & the
additional configurations after migrating to CIG.
ü After you migrate to CIG, you will be able to use two new features – Attachments & Comments.
ü These features help you send additional information at the header & the line-item level of
transactions.
ü You also need to send system details & SAP connectivity data to CIG & then confirm the SAP
connectivity information in CIG.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 119
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Modifying Partner Profile Settings
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Modifying Partner Profile Settings
After you successfully migrate to CIG, 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 table on next slide.
ü Use the Receiver Port that you configured as part of migrating to the CIG. This task applies
only if you have connected to CIG without using SAP Process Integration middleware.
ü 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 CIG.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 121
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Modifying Partner Profile Settings
The following table displays the existing & the new basic type partner profile settings for IDoc
transactions.

Transaction Existing Basic Type New Basic Type

Schedule Agreement Release DELFOR02 ARBCIG_DELINS

Invoice Copy Request: FI Invoice FIDCCP02 ARBCIG_FIDCC2

Invoice Copy Request: MM Invoice GSVERF03 ARBCIG_GSVERF

Order Enquiry ORDERS05 ARBCIG_ORDENQ

Purchase Order ORDERS05 ARBCIG_ORDERS

Payment Remittance PEXR2001 ARBCIG_REMADV

Quote Request ORDERS05 ARBCIG_REQOTE


© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 122
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Modifying Partner Profile Settings
Steps to modify Partner Profile settings –
1. In SAP Easy Access screen, run the TCode we20 & in the Partner Profiles screen, on the left-
side panel, expand Partner Type LI or Partner Type LS as required.
2. Under Partner Type LI or Partner Type LS, click the partner number where you want to
configure the partner settings & in the right-side panel, view the details of the partner number
that you have clicked.
3. In the right-side panel, 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.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 123
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Modifying Partner Profile Settings
Steps to modify Partner Profile settings (continued…) –
4. Under the Outbound Options tab, perform the following actions –
a) In the Receiver port field, use the receiver port that you have configured as part of migrating to CIG.
b) In the Basic type field, replace the existing basic type with the new basic type.
c) In the Extension field, remove the existing extension.
5. Click Save.

Pleaser refer to the example shown in the screenshots in next 2 slides.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 124
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Modifying Partner Profile Settings

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 125
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Modifying Partner Profile Settings

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 126
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages
In this section you need to configure the following linkages –

ü Ariba Event Linkages


ü Ariba User HR Event Linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 128
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages –
Ariba Event Linkages
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba Event Linkages
You need to link the incremental extract events with the corresponding function module.

To configure Ariba Event Linkages:

1. Navigate to Integration with Other SAP Components >>> Ariba Cloud Integration Gateway
>>> Master Data Integration >>> General Settings using the transaction code SPRO.
2. Expand General Settings section & click on IMG-Activity for Ariba Event Linkages – The
Change View Event Type Linkages: Overview screen appears.
3. Click New Entries & enter the values mentioned in the table on next slide.
4. For Event delivery , choose Using tRFC.
5. Check the Linkage Activated checkbox (for all the entries mentioned in the table).
6. Click Next Entry to enter the information for the next record.
7. Once all records are entered, click Save.
Also refer to the example shown in the screenshots in 4 slides after the table.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 130
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba Event Linkages
Object Category Object Type Event Receiver Type Receiver Call Receiver Function Module
BOR Object Type ARBCIG0012 COSTCENTERCHANGED CHANGE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG0012 COSTCENTERCREATED CREATE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG0012 COSTCENTERDELETED DELETE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG1001 CREATED CHANGE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG1006 CREATED CREATE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG1006 VIEWCREATED CREATE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG1022 ASSETCHANGED CHANGE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG1022 ASSETCREATED CREATE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG1022 ASSETDELETED DELETE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG3006 CHANGEGL CHANGE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG3006 CREATEGL CREATE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG3006 DELETEGL DELETE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG3060 ONCREATE CREATE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG3060 STATUSCHANGED CHANGE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG3060 UPDATED CHANGE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIGLFA1 VENDORCHANGED CHANGE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIGLFA1 VENDORCREATED CREATE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIGLFA1 VENDORDELETED DELETE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIGUSER CLONED USER_CHANGE Function Module ARBCIG_CHANGEDOC
BOR Object Type ARBCIG1001 CREATED CHANGECAT Function Module ARBCIG_DOC_CHANGES
BOR Object Type ARBCIG1006 VIEWCREATED CREATECAT Function Module ARBCIG_DOC_CHANGES
BOR Object Type ARBCIG3003 STARTVEEKPLAMATNRDEL CHANGECAT Function Module ARBCIG_DOC_CHANGES
BOR Object Type ARBCIG3003 STARTVENDORMATNRDEL CREATECAT Function Module ARBCIG_DOC_CHANGES
BOR Object Type ARBCIG3060 STATUSCHANGED CHANGECAT Function Module ARBCIG_DOC_CHANGES

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 131
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba Event Linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 132
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba Event Linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 133
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba Event Linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 134
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba Event Linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 135
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages –
Ariba User HR Event Linkages
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba User HR Event Linkages

Users need to configure this if they need to send User Master Data with Incremental Load option.

To configure HR Event Linkages:

1. Navigate to Integration with Other SAP Components >>> Ariba Cloud Integration Gateway
>>> Master Data Integration >>> General Settings using the transaction code SPRO.
2. Expand General Settings section & click on IMG-Activity for Ariba User HR Event Linkage –
The Change View HR-CA: Event Linkage for Customer: Overview screen appears.
3. Click New Entries & enter the values mentioned in the table on next slide.
4. Click Next Entry to enter the information for the next record.
5. Once all records are entered, click Save.

Also refer to the example shown in the screenshots in 4 slides after the table.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 137
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba User HR Event Linkages

Object Type Infotype Update Operation Sequence Number Object Type Function Module

P 1 UPD 0 ARBCIG1065 ARBCIG_HRPM_CHANGE_DOCS

P 2 UPD 0 ARBCIGTNT ARBCIG_HRPM_CHANGE_DOCS

P 105 DEL 0 ARBCIGEMPL ARBCIG_HRPM_CHANGE_DOCS

P 105 INS 0 ARBCIGEMPL ARBCIG_HRPM_CHANGE_DOCS

P 105 UPD 0 ARBCIGEMPL ARBCIG_HRPM_CHANGE_DOCS

If you get the error message: No Entry exists in T777IBO table, maintain the following entry in the
T777IBO table:

OT Object Type Text IT Object type Name

P Person 1 ARBCIG1065 Add a meaningful name

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 138
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba User HR Event Linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 139
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba User HR Event Linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 140
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba User HR Event Linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 141
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Event Linkages – Ariba User HR Event Linkages

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 142
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Logical Ports & Service Names
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Logical Ports & Service Names
ü Perform this configuration only if you have connected to CIG without using SAP Process
Integration.
ü After you migrate to CIG, create Logical Ports for the outbound transactions & Service Names
for the inbound transactions that are performed using web services proxies in SAP system.
ü Authenticate Logical Ports when you configure them. You can use either a User Name & a
Password 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 system in advance.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 144
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Logical Ports & Service Names
In SAP system, the following outbound & inbound transactions for Ariba Network are performed
using proxies –

Outbound Transactions Inbound Transactions


Document Status Update Advance Ship Notice
Invoice Status Update Component Acknowledgment
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
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 145
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Logical Ports & Service Names
In SAP system the following outbound & inbound transactions for Ariba Procurement solutions are
performed using proxies –
Outbound Transactions Inbound Transactions
Master Data Purchase Order Export
ERP Response to Procurement Purchase Order Change Export
Catalog Upload Request Purchase Order Cancel Export
Purchase Order Close Status
Requisition Export Request
Derive Accounting Export
Receipt Export Request
Service Sheet Export Request
Advance Payment Export Request
Cancel Advance Payment Request
Payment Export Request
Requisition Revert Export
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 146
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Configure Logical Ports & Service Names
In SAP system the following outbound & inbound transactions for Ariba Sourcing solutions are
performed using proxies –

Outbound Transactions Inbound Transactions

Master Data Ariba Sourcing Contracts

Ariba Sourcing Status Updates Ariba Sourcing Purchase Order

Ariba Contract Response Ariba Sourcing Service Items

Purchase Info Rec Confirmation Purchase Info Rec

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 147
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Migrate Transactions
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Migrate Transactions
In this step, you will need to migrate Advanced Ship Notice (ASN); Dispatch Delivery Notification
(DDN) & Component Ship Notice (CSN) transactions
ü Advanced Ship Notice transaction has been changed to a web service.
ü The web services for the Dispatch Delivery Notification & the Component Ship Notice have
been combined into a new transaction named Ship Notice Request.
ü If you have customized any of these transactions before you migrate to CIG, you must
implement those customizations again after migrating to CIG.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 149
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Create Table Map Values
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Create Table Map Values
Creating a table to map values of Pricing Condition parameters in CIG is a mandatory step.
You must manually map the values of Pricing Condition parameters available in SAP system to the
new values configured in CIG. Login to CIG & create this mapping under Cross Reference in your
CIG Project .

The list of the sample values of the Pricing Condition parameters in SAP system is shown in the
table in next slide.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 151
SAP Ariba Cloud Integration Gateway
Post-Migration Activities – Create Table Map Values
Pricing Condition Parameter Sample Value in SAP System
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
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 152
SAP Ariba Cloud Integration Gateway
Modifications to the Supported Transactions
SAP Ariba Cloud Integration Gateway
Modifications to the Supported Transactions
As part of migrating to CIG, parameters are added or modified for some of the transactions.

SAP Ariba has provided 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.

Replace the code that is used to configure an existing customer exit with the corresponding
INCLUDE statements.

There are changes made to the following areas –

ü Parameters (new and modified)

ü Enhancements (new and modified)

ü Customer exits
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 154
SAP Ariba Cloud Integration Gateway
Modifications to the Supported Transactions
For Ariba Network integration with SAP system using CIG, modifications are made to following
transactions –

Purchase Order Service Sheet


Scheduling Agreement Release Service Sheet Response
Order Confirmation Liability Transfer
Invoice Component Consumption Request
ERP-initiated Invoice Component Acknowledgment
Invoice Status Update Ship Notice Request
Payment Proposal Product Activity Message
Payment Remittance Request Product Replenishment Message
Remittance Advice
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 155
SAP Ariba Cloud Integration Gateway
Modifications to the Supported Transactions
For Ariba Sourcing integration with SAP system using CIG, modifications are made to following
transactions –

ü The parameters for Request for Quotation are renamed & INCLUDE statements are introduced
to replace the code that is used to configure an existing customer exit.

ü The configurations of the Quote Message & the Contract Request transactions are migrated
from the SAP system to CIG under Cross Reference section of CIG Project creation.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 156
SAP Ariba Cloud Integration Gateway
Modifications to the Supported Transactions
For Ariba Procurement integration with SAP system using CIG, modifications are made to
following transactions –

ü Purchase Order

ü Goods Receipt

ü Service Entry Sheet

ü Advance Payment

ü Invoice

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 157
SAP Ariba Cloud Integration Gateway
Additional Activities
SAP Ariba Cloud Integration Gateway
Additional Activities
Once you have performed all the Post-Migration tasks, you also need to ensure that following
activities are carried out in order to have all the configurations & settings are in place for you to start
transacting with CIG –

ü Send SAP system details & connectivity data to CIG.

ü Confirm SAP connectivity information in CIG.

ü Configure Global Settings in SAP system

ü Import Master Data to Ariba Sourcing & Ariba Procurement as needed.

ü Configure General Settings in SAP system for the transactions you want to use.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 159
SAP Ariba Cloud Integration Gateway
Additional Activities
Once you have performed all the Post-Migration tasks, you also need to ensure that following
activities are carried out in order to have all the configurations & settings are in place for you to start
transacting with CIG (continued…) –

ü Create Project in CIG

ü Configure Project Connection in CIG.

ü Specify Cross Reference in CIG for the transactions you want to use.

ü Address your customization needs in SAP system

ü Add custom XSLT in CIG.

ü Review your Project configurations in CIG


© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 160
SAP Ariba Cloud Integration Gateway
Additional Activities
Once you have performed all the Post-Migration tasks, you also need to ensure that following
activities are carried out in order to have all the configurations & settings are in place for you to start
transacting with CIG (continued…) –

ü Test Project

ü Prepare for deployment.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 161
End of the session.

Thank you.

You might also like