Day5 3 Migration
Day5 3 Migration
Integration Redefined
CONFIDENTIAL
SAP Ariba Cloud Integration Gateway
ü Pre-Migration Activities
ü Migration Activities
ü Post-Migration Activities
ü Additional Activities
ü 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.
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.
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.
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.
ü 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.
Following activities must be carried out before migrating Master Data & Catalog for Ariba
Procurement solutions & Ariba Sourcing solutions.
ü /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.
ü 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.
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.
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.
ü 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.
To ensure that duplicate entries for ISU are not sent to Ariba
/ARBA/AVOID_DUPLICATE_ISU_PP AVOID_DUPLICATE_ISU_PP Renamed
Network.
ü 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.
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.
ü 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
ü 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.
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.
ü 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.
ü 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.
ü 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.
ü 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.
ü Service Entry Sheet Number – Filter by a specific range of Service Entry Sheet Number or
Filter by a specific External Entry Sheet Number.
ü Goods Receipt Creation Date – Filter by the Creation Date of the Goods Receipt.
Ø Fiscal Year filter by one or more fiscal years that applies to the payment export requests
Ø Created Date filter by the date of creation of the payment export requests
Ø Invoicing Party filter by the party for which the payment export request 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
ü 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.
Solution Transaction SAP Parameter Name SAP Field Name CIG Field Name
Prerequisites –
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.
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
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
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 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
ü Migrate Transactions
© 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.
© 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.
© 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 –
© 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.
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.
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
If you get the error message: No Entry exists in T777IBO table, maintain the following entry in the
T777IBO table:
© 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 –
© 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.
ü 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 –
ü 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
ü 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 –
ü 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…) –
ü Specify Cross Reference in CIG for the transactions you want to use.
ü Test Project
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ CONFIDENTIAL 161
End of the session.
Thank you.