Configuring External Commands for Operating System

There are some pre-requisites and limitations for Master Data Integration. Please refer to the CIG Overview Guide & CIG Configuration Guide for more details.

This unit cover the configurations of common settings required to import master data in any of the SAP Ariba solution – Procurement or Sourcing.

Master data consists of general information that reside on SAP ERP that SAP Ariba uses to build and process data in transactions.

Buyers using SAP Ariba Cloud Integration Gateway can seamlessly integrate master data from the SAP system to the SAP Ariba solutions using the following options:

• Full Load
• Incremental Load

A feature (PL-17883) is available to use both Integration Tool Kit (ITK) & CIG to import master data in following applications.

• SAP Ariba Procurement Solutions
• SAP Ariba Strategic Sourcing Solutions

This feature is useful during below listed situations:

• New or existing customers using ITK with multiple ERP systems but like to use CIG for master data import from SAP ERP.
• Existing customers using ITK with SAP ERP & wish to switch to CIG for master data import.

To enable this feature please create an SR or contact SAP Ariba DSC (Designated Support Contact).

Notes for ITK & CIG co-existence feature (PL-17883):

• If you are already using ITK to import Master Data & additionally want to use CIG to import master data from SAP ERP, you must retain the ITK Shared Secret or the ITK certificate that is configured in the Integration Manager → Integration Tool Kit Security section of Ariba Procurement site.
• If you want to use CIG to import master data from SAP ERP & discontinue the use of the ITK, you need to remove the ITK Shared Secret or the ITK certificate that is configured in the Integration Manager → Integration Tool Kit Security section of Ariba Procurement site. In this scenario, you do not need to download the CIG Tenant certificate & configure it in the Integration Manager>>>Integration Tool Kit Security section of Ariba Procurement site.

Users need to configure the commands on SAP System & associate them with their Operating System commands. This is a one-time activity & a mandatory configuration.

To configure External Commands:

1. Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Master Data Integration → General Settingsusing the transaction code SPRO.
2. Expand General Settings section & click on IMG-Activity for Configure External Commands for Operating System – The External Operating System Commands screen appears.
3. Click Create – the External Commands screen appears.
4. Enter the values as mentioned in the table:

   Command name	Operating System	Operating System Command	Operating System Command	Additional Parameters Allowed
   ZSSPDIRCREATE	Windows NT	cmd	/C mkdir ?	Enabled by default
   ZSSPDIRREMOVE	Windows NT	cmd	/C rmdir /q/s ?	Enabled by default
   ZSSPMOVE	Windows NT	cmd	/C move ? ?	Enabled by default
   ZSSPDIRCREATE	Linux	mkdir	-p ?	Enabled by default
   ZSSPDIRREMOVE	Linux	rm	-r ?	Enabled by default
   ZSSPMOVE	Linux	mv		Enabled by default

Users need to configure the incremental extract to run the incremental load for Master Data.

This is a one-time activity & a mandatory configuration.

To configure Incremental Extract Event:

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 Configure Ariba Incremental Extract Event – The Ariba Incremental Extract Event Configuration screen appears.
3. Choose the Master Data that you want to configure & click Execute.
4. The Display logs screen appears with the details of the configured master data extract events.
   Note

   You can also see the details using the TCode SLG1 with the object ARBCIG_MASTERDATA and subobject INCREMENT_EVENT.

Users need to configure the field restrictions for the incremental load for Master Data.

User need to set up the field restrictions manually in the SWEC table.

To configure Incremental Field Restrictions:

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 Master Data Incremental Field Restrictions – The Ariba Master Data Incremental Field Restrictions screen appears.
   Note

   This is for sending only the specific field changes to SAP Ariba Apps which are relevant to Ariba Integration.

   Always make a note of the object type, event & the action type (create, change, or delete) for the selected object.

3. Select a Master Data object that you want to extract & click Execute – The Ariba Master Data Incremental Field Restrictions screen appears with the details of the configured restrictions.
4. Press Ctrl + C to copy the content of the page. Note that the content is already selected.
5. Run the TCode SWEC – The Change View "Events for Change Document": Overview screen appears.
6. Locate the object with the same object type, event & action type (Create or Change or Delete).
7. Select event line in change mode & double-click Field Restrictions folder in the left pane – The Change View "Field Restrictions": Overview screen appears.
8. Click Condition Editor.
9. If the direct text entry mode is not configured for your user interface, perform the following steps:
   • Click Utilities → Settings
   • On the Condition Editor: Personal Settings page, select Direct text entry (traditional mode)
   • Save the configuration
   
   
10. Click New rows to include the content for field restriction. Ensure that the number of rows you add is equal to the number of rows of content that you copied in Step#4.
11. Click column for Expression 1 & paste the copied content for field restrictions.
12. Click Back & enter the Transport Request number.

Click Save.

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

To configure 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 the page located at the beginning of this lesson.
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.

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

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 the page located at the beginning of this lesson.
4. Click Next Entry to enter the information for the next record.

   Once all records are entered, click Save.

Users need to add the realms for each Ariba solution that can be used to process master data events. This is needed to define Realm Name & Ariba Solution relationship in order to determine the appropriate target URL.

To configure Connection Parameters:

1. Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Master Data Integration → Connection Parameters for Master Data using the transaction code SPRO.
2. Click on IMG-Activity for Connection Parameters for Master Data – The Change View "Direct Connectivity Parameters": Overview screen appears.
3. Click New Entries & enter the following values:
   • Solution: Select a solution name from the list.
   • Realm: Add a realm name.
   • P: Select the checkbox if this is a parent realm.
   • Wait Time: Add time in seconds to wait to connect to the gateway. Do not enter values for Logical Port Name.
   
4. Click Save.

This is to map the SAP vendors which are already existing in SAP Ariba Procurement solutions. Users need to map the SAP Ariba Procurement solution’s unique System ID to the SAP vendor. This configuration is required only if you import master data for suppliers.

To maintain System ID:

1. Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Master Data Integration → Maintain System ID for Master Data using the transaction code SPRO.
2. Click on IMG-Activity for Maintain System ID for Master Data – The Change View "System ID For Customers": Overview screen appears.
3. Click New Entries & enter the following values:
   • System ID: Enter the system ID of Ariba Procurement solutions for the Supplier. SID499 (for example).
   • Vendor: Enter SAP Vendor code.
   
4. Click Save.

Users need to maintain Date & Time Stamp for an incremental extract of Master Data.

To maintain System ID:

1. Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Master Data Integration → Maintain Date Time Stamp for Master Data using the transaction code SPRO.
2. Click on IMG-Activity for Maintain Date Time Stamp for Master Data – The Change View "Date and Time stamp for Master Data": Overview screen appears.
3. Click New Entries & enter the following values:
   • Extract: Select from the list.
   • Realm: Enter realm name.
   • Date Time Stamp: Add date & time in YYYYMMDDHHMMSS format.
   
4. Click Save.

Users need to maintain use roles mapped to each solution.

To maintain User Profiles:

1. Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Master Data Integration → Maintain User Profiles for User Master Data using the transaction code SPRO.
2. Click on IMG-Activity for Maintain User Profiles for User Master Data – The Change View "Table to hold the user roles mapped to groups": Overview screen appears.
3. Click New Entries & enter the following values:
   • Solution: Select the solution name from the list.
   • Role: Select the user role to be mapped with the solution.
   • Realm: Enter realm name.
   
4. Click Save.

Users need to maintain mappings between custom field in SAP System & SAP Ariba solution’s custom field for Master Data & Catalog extracts.

To maintain Field Mappings:

1. Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Master Data Integration → Enhancements using the transaction code SPRO.
   Note

   (This is an optional activity. Do not change the default values.)

   • In SAP ERP, the fields are always in upper case but in SAP Ariba solutions, it is in mixed case.
   • Custom table ARBCIG_FIELDMAP is maintained to map the SAP System & SAP Ariba Procurement solutions system’s field values.
2. Expand Enhancements & click on IMG-Activity for Maintain Field Map for Master Data and Catalog Upload Request – The Change View "Table to maintain mapping of SAP to Buyer fields": Overview screen appears.
3. Click New Entries & enter the following values:
   • Solution: Select the solution name from the list for which you are mapping the field.
   • Structure: Add a structure name. ARBCIG_BP_LANG_STR (For example).
   • Field SAP: Add the SAP ERP field name that you want to map. BUDGETPDTX (For example).
   • Field Ariba: Add the Ariba solution field name to which you want to map. Name (For example).
   
4. Click Save.

Users can schedule a job to export Master Data from SAP System to SAP Ariba solutions.

Ensure that you have configured the ARBCIG_MASTER_DATA_EXPORT program before scheduling the export job.

To schedule a job:

1. Run TCode SM36 – The Define Background Job screen appears.
2. Schedule the program:
   • ARBCIG_MASTER_DATA_EXPORT
   • ARBCIG_BUYER_CATALOG_EXPORT

Users can implement BAdIs to enhance the Master Data Upload Request as required. Available in the ARBCIG_MASTER_DATA_EXPORT program.

To maintain BAdI:

1. Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Master Data Integration → Enhancements → Business Add-Ins(BAdIs) using the transaction code SPRO.
2. Expand Business Add-Ins(BAdIs) & click on IMG-Activity for one of the followings as per your requirements:
   • BAdIs for Master Data Export – BAdI Name: ARBCIG_MASTERDATA.
   • BAdIs for Catalog Upload Request – BAdI Name: ARBCIG_BUY_CATALOG_EXPORT.
   • BAdIs for Purchase Info Record – BAdI Name: ARBCIG_PURINFREC.
3. Implement the BAdI. The methods that you can implement are listed in SAP Ariba Cloud Integration Gateway Configuration Guide.

In the event users want to resend the Master Data or Catalog Upload Request (except Bill of Materials) to SAP Ariba Solutions, it can be done using this utility.

To resend Master Data or Catalog Upload Request:

1. Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Master Data Integration using the transaction code SPRO.
2. Click on IMG-Activity for Resend Master Data or Catalog Upload Request – The Resend Batch Extracts to Cloud Integration Gateway screen appears.
3. Enter the following values:
   • File Name: Select the archived file.
   • Variant: Provide the variant if you want to resend the Sourcing Master Data.
   • Partition: Provide the partition if you want to resend the Sourcing Master Data.
   
4. If you want to delete the archived files, enter the following values:
   • Archive Directory: Select the directory where the files are archived.
   • Till Date: Select a date. Archived files before this date would be removed.
5. Click Execute.

Users need to maintain the required parameters for more than one SAP Ariba solution.

To maintain parameters for more than one SAP Ariba solution:

1. Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Master Data Integration → General Settings → Maintain Parameters using the transaction code SPRO.
2. Expand Maintain Parameters & click on IMG-Activity for Cross Application – The Parameters – Cross Application Master Data screen appears.
3. Click Modify & maintain the parameter mentioned in the table on the next page.
4. Click Save.

Users need to configure selection criteria to filter Master Data records to import for more than one SAP Ariba solution.

User can filter the Master Data records using following conditions:

• Equality & Inclusion: where Option is EQ & Sign is I.
• Ranges & Exclusion: where Option is BT & Sign is E.
• Patterns & Comparisons: where Option is CP & Sign is I or E.

To maintain filters for more than one SAP Ariba solution:

1. 
   Navigate to Integration with Other SAP Components → Ariba Cloud Integration Gateway → Master Data Integration → General Settings → Maintain Filters using the transaction code SPRO.
2. 
   Expand Maintain Filters & click on IMG-Activity for Cross Application – The Prefilters – Cross Application Master Data screen appears.
3. 
   Click Modify & maintain the filters based on your requirements. Refer to the values mentioned in the table of this lesson.
4. Click Save.