Introducing CIG Migration

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

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

Pre-Migration Activities – Migrating Master Data & Catalog

The following sub-activities must be carried out before migrating Master Data & Catalog for SAP Ariba Procurement solutions & SAP Ariba Sourcing solutions:

3.3.1 Removing Data from specific database tables.

3.3.2 Deactivate event type linkages.

3.3.3 Remove the HR-CA event linkages.

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.

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.

Steps to deactivate event type linkages:

1. In the SAP Easy Access screen, run the TCode – SWETYPV.
2. In the Change View "Event Type Linkages": Overview screen, select events, double-click Type linkage active against it.
3. In the Change View "Event Type Linkages": Details screen, in the Linkage Setting (Event Receiver) section, uncheckLinkage Activated box.
4. Click Save.

Follow these steps to remove the HR-CA event linkages:

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 necessary events, click Delete.
3. Click Save.

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, per table:

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.

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:

• 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:

• 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; SAP Ariba Procurement & SAP 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 this activity.

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:
   1. 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.
   2. Under Shared data, select Master Data, or Catalog, or both as required.
4. Click Execute.

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:
  • Ariba Network
  • SAP Ariba Procurement Solutions
  • SAP Ariba Strategic Sourcing Solutions
• 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.
• The filters are available for following transaction documents –
  • Requisition (Req.)
  • Purchase Order (PO)
  • Service Entry Sheet (SES)
  • Contracts
  • Goods Receipt (GR)
  • Payment Export Request

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

  
• 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.
• 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 request.
  • 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.
  • 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.
  
  Note

  For all Invoice / Payment Export Request filters, except the Document Header Text filter, you can select multiple values using the Multiple selection option.

• 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 tables in this activity.

This table lists the details of the parameter fields that you can migrate from SAP system to CIG:

This table lists the details of parameters that you can migrate from SAP system to CIG:

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.

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.
3. Perform these actions:
   1. Under Authenticate on SAP Ariba Cloud Integration Gateway using SOA Manager credentials, enter your SOA Manager details required to authenticate yourself to SAP Ariba Cloud Integration Gateway. This includes your P User Name, Password, Proxy Host Name, and Port Number to connect to the proxy host.
   2. Specify whether you are connecting to the test installation or the production installation of SAP Ariba Cloud Integration Gateway.
   3. Under Select one or more transactions to migrate the corresponding setups, select the solution and select the transactions that you want to migrate to SAP Ariba Cloud Integration Gateway.
   
4. Click Execute.

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.

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.

The following table lists the names of the SAP Ariba BAdIs available in Ariba Network Adapter for SAP NetWeaver & their corresponding BAdIs available in CIG:

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

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 –
   1. Migrate SAP Ariba data to new database tables.
   2. 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.

Folder Structure

• *Folder that is named after the name of the BAdI Implementation.
• **One or more folders that are named after the name of the BAdI implementation classes.
• ***One or more folders that are named after the methods within each class. Each of these folders contains a method file.

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.

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 –
   1. Path to the designated folder in your local drive where you have downloaded the BAdI implementations.
   2. 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.

   3. Parsing completion status.

   Example: Code downloaded excludes /ARBA/ object.

   

   Example: Code downloaded includes /ARBA/ object.

   
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.
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 –
    1. In the BAdI Implementation field, enter the name for the BAdI implementation.
    2. In the Implementation Class field, enter the BAdI implementation class.
    3. In the BAdI Definition field, select the definition of the BAdI.
    4. Click OK.
    5. 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.
    6. 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.
    

Example: New code will appear & then you have to activate.

Example: BAdI migration screen will look like this.

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

After you migrate to CIG, you need to perform the set of tasks that are required to integrate SAP system with Ariba Network, SAP Ariba Procurement, and SAP Ariba Sourcing using CIG.

• After you complete the migration of the transactions from Ariba Network adapter for SAP NetWeaver to CIG, you must perform the steps 4-5 described in the SAP Note 2402191.
• 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.

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 page.
• 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 & SAP S/4HANA add-on for CIG.

Table: Existing & the new basic type partner profile settings for IDoc transactions.

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.
4. Under the Outbound Options tab, perform the following actions –
   1. In the Receiver port field, use the receiver port that you have configured as part of migrating to CIG.
   2. In the Basic type field, replace the existing basic type with the new basic type.
   3. In the Extension field, remove the existing extension.
   
5. Click Save.

Configure Event Linkages

In this section you need to configure the following linkages –

5.2.1 Ariba Event Linkages

5.2.2 Ariba User HR Event Linkages

You need to link the incremental extract events with the corresponding function module. This is required to capture any changes occurred in Master Data record & store it in a CHANGE LOG table for incremental extract event of that particular master data object.

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 in this activity.
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.

   Once all records are entered, click Save.

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 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 in this activity.
4. Click Next Entry to enter the information for the next record.

   Once all records are entered, click Save.

In the event in which you receive an error message:

No Entry exists in T777IBO table, maintain the following entry in the T777IBO table:

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.

In SAP system, you can create only one logical port for a consumer proxy or a service definition. If you create an additional logical port, SAP ERP overwrites the existing logical port with the latest one that you have created.

• SAP system generates the name of the Logical Port for a proxy-based outbound transaction from the name of the consumer proxy corresponding to that transaction.
• For example, the consumer proxy for the Document Status Update transaction is ARBCIG_CO_DOCUMENT_STATUS_UPDAT.
• When you create a Logical Port for the Document Status Update transaction, SAP system generates the name of the logical port as CO_DOCUMENT_STATUS_UPDAT.

In SAP system, the following outbound & inbound transactions for Ariba Network are performed using proxies:

In SAP system, the following outbound & inbound transactions for SAP Ariba Procurement solutions are performed using proxies:​

In SAP system, the following outbound & inbound transactions for SAP Ariba Sourcing solutions are performed using proxies:

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.

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 .