I am using the SAP Integration Suite, managed gateway for spend management and SAP Business Network (Buy-side) in order to integrate my SAP ERP with SAP Ariba Applications (e.g. SAP Business Network, SAP Ariba Procurement and invoice, SAP Ariba Sourcing and Supplier Management, etc). I realized the SAP Integration Suite, managed gateway for spend management and SAP Business Network (CIG) out-of-the-box standard 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 Managed Gateway for Spend&Network custom mappings at your end using the Managed Gateway for Spend&Network mapping tool. However, for known limitations which cannot be accomplished by the mapping tool, a formal XSLT mapping change request can be requested by submitting an SAP Case along with the following details:

• Reason of why the desired mapping could not be achieved by the mapping tool.
• The original preprocess payload that is being sent to Managed Gateway for Spend&Network from source system.
• The current outbound payload that is sent out from Managed Gateway for Spend&Network to target system.
• The desired final outbound payload after XSLT mapping applied (i.e. how it should look after going through CIG).
• The mapping sheet template information with the xpath information and mapping rules/logic.
• CIG Add-on SP version info of all affected system(s).

After you have gathered all of the above required details, please create an SAP Case and include all of these 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.
• Managed Gateway for Spend&Network does not support complex transformations, calculations, and rules. We always recommend that you send the final information to Managed Gateway for Spend&Network which should be mapped to the final payload to be delivered to the target system (e.g. SAP ERP, SAP Business Network, etc.). One-to-one mapping is the best approach.

Practical example for SAP Integration Suite, managed gateway for spend management and SAP Business Network mapping change request

Business Problem: We are using SAP Integration Suite, managed gateway for spend management and SAP Business Network 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 SAP Business Network limitations, we 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 SAP Business Network from Ariba Sourcing and then reaches Managed Gateway for Spend&Network, the preprocess payload (the original payload that is being sent to CIG) contains a custom value field in form of an extrinsic: <Extrinsic name="cus_SAPDocumentCategory">ZMK1</Extrinsic>.
3. The requirement is to have the cus_SAPDocumentCategory information (in this case ZMK1) mapped to the <ProcessingTypeCode>ZMK1<ProcessingTypeCode/> of outbound PurchasingContractERPRequest_V1 request which is posted in SAP ERP via Managed Gateway for Spend&Network.
4. The desired custom mapping rule is provided via the mapping template information sheet.

SAP Integration Suite Managed Gateway > Managed Gateway for Business Network
SAP Integration Suite Managed Gateway > Managed Gateway for Procurement
SAP Integration Suite Managed Gateway > Managed Gateway for Procurement Custom Map (XSLT)
SAP Integration Suite Managed Gateway > Managed Gateway for Sourcing Integration
SAP Integration Suite Managed Gateway > Managed Gateway Foundation & Tools > Managed Gateway for Managed Gateway Portal