Custom Mapping in SAP Ariba CIG

Customer requirement is often no limited to the standard delivered content. Often we get request for customizing the mapping in SAP Ariba CIG(Cloud Integration Gateway) for new custom fields created in Ariba. Starting from the SAP Ariba Cloud Integration Gateway June 2019 release (ARBCI1 100: SP 0005), buyers can use the mapping tool to create, edit, delete, and test their custom mappings. The motivation to write this blog is to explain how custom mapping is performed in CIG.

Assumption: You have the access to the CIG Tenant

In CIG Tenant Select My Configurations -> Mappings.

The Mappings tab displays the list of document types supported by SAP Ariba Cloud Integration Gateway like ArticleMaster(below screenshot), and other details such as Version, Standard Map, Custom Map, and so on.

Select a document type, and then click the + icon under Actions if you are editing for the first time

Personal Opinion: CIG is better compatible with Chrome Browser

Select the SID and press OK

The Document Mapper screen opens.

Hint: Click on the pencil edit icon if you would like to edit and already customized mapping as below

Mapping Extrinsic Fields

Ariba cXML consists of Extrinsic field in the structure at header and item level. This is to  accommodate any custom field requirement from Ariba. In this blog, I am considering the use case that the custom field is getting passed to the cXML payload from Ariba to CIG under extrinsic field like below

In the Document Mapper, Drag the Extrinsic field to the target field

Now right click on the connection made and click on Add source condition

In the source structure, select field @name and in the pop up just give the value of the field name created in Ariba (you must get it from Ariba Functional Consultant)

Important: Create Node to the parent item by right clicking the parent field

Ex. If Target field is /PurchasingContractERPRequest_V1/PurchasingContract/DeliveryTerms/Incoterms/ClassificationCode

then Create Node for /PurchasingContractERPRequest_V1/PurchasingContract/DeliveryTerms

In case the Source and Target Field has multiple occurrence example at Item level, add target position variable

Right click on the connection -> Target Variable -> Add position Variable

Select the Parent in the Target structure with occurrence > 1

Ex. Here Item is the Parent in the Target Structure with occurrence > 1

Then right click on the connection between source and target field -> Add source condition

Select the parent in the source with occurrence > 1

Ex. Here ContractItemln in source has occurrence >1

In the Pop-up select Position Variable and OK.

Save the Mapping and click on to activate the mapping.

How to test Mapping in CIG

You now have the possibility to test the Mapping in CIG. You can test the mapping by clicking on

Step 1: Browse from your local machine the input payload to be tested

Step 2: Select the System ID

Step 3: Execute the test

Step 4: Check the output payload after test

Check the Outcome of the Mapping Test Log once you execute the test

Check the output payload in Result Document

Conclusion: The above blog can be referred in scenarios when the standard mapping provided in SAP Ariba CIG can’t meet customer’s requirement like addition of new custom field in Ariba which needs to be mapped to the respective structure of ECC or S/4.

Note: Currently SAP Ariba CIG Document Mapper has limited functions available. Please refer to below SAP Help link for the list of functions supported.

Reference

How to Create Custom Mapping – Help.sap.com