I am using the SAP Ariba Cloud Integration gateway (Buy-side) in order to integrate my SAP ERP with SAP Ariba Applications (e.g. Ariba Network, SAP Ariba Procurement and invoice, SAP Ariba Sourcing and Supplier Management, etc). I realized the Cloud Integration Gateway (CIG) out-of-the-box mappings do not meet my business requirements.

What is the required Information I should provide for XSLT mapping customization?

How can I extend or change the out-of-the-box mapping logic for CIG?

You can create CIG custom mappings at your end using the CIG Mapping tool, however for known limitations which cannot be accomplished by the CIG mapping tool, a formal mapping change request can be requested by submitting a Case along with the following details:

• The original payload that is being sent to CIG.
• The desired final payload output (how it should look after going through CIG).
• The mapping sheet template information with the xpath information and mapping rules/logic.

After you have gathered all of the required details, please create an Ariba Case and include all of this information.

Please note:

• The mapping sheet template is attached to this solution. Please complete it as per your mapping change needs and attach it to the Case along with the payloads.
• CIG does not support complex transformations, calculations, and rules. We always recommend that you send the final information to CIG which should be mapped to the final payload to be delivered to the external system (e.g. SAP ERP, Ariba Network, etc.). One-to-one mapping is the best approach.

Practical example for SAP Ariba CIG mapping change request

Business Problem: We are using Cloud Integration Gateway to integrate our SAP ERP to SAP Ariba Sourcing solution in order to create contracts in SAP ERP. In SAP ERP, we use multiple document types for contracts other than the standard ones (.eg. ZWK1, ZMK1, YWK1, etc). There is a business requirement to allow users to choose the custom document types from the SAP Ariba Sourcing side where the SAP ERP contracts should be created using the selected custom document type.  Due to some Ariba Network limitations, you can map only one document type based on the value or quantity (WK if value or MK if quantity). There is no standard way to have extra contract types.

Solution:

1. A custom field called cus_SAPDocumentCategory was created on the Ariba Sourcing side to allow users to select the contract types.
2. Whenever the contract request is sent to Ariba Network from Ariba Sourcing and then reaches CIG, the payload (The original payload that is being sent to CIG) contains a custom value field in a form of an extrinsic: <Extrinsic name="cus_SAPDocumentCategory">ZMK1</Extrinsic>.
3. The requirement is to have the cus_SAPDocumentCategory information (on this case ZMK1) mapped to the <ProcessingTypeCode>ZMK1<ProcessingTypeCode/> of PurchasingContractERPRequest_V1 request which is posted in SAP ERP via CIG (The desired final payload output, or how it should look like after going through CIG).
4. The desired custom mapping rule provided via the mapping template information sheet (The mapping sheet template information with the xpath information and mapping rules).

SAP Ariba Buying and Invoicing
SAP Ariba Contracts
SAP Ariba Strategic Sourcing Suite
SAP Ariba Supplier Lifecycle & Performance
SAP Business Network