FAQ KB0398973
Email
Managed Gateway for Spend&Network - What is the required information I need to provide for XSLT mapping customization?
Symptom

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 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?


Resolution

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 Managed Gateway for Spend&Network mapping tool, a formal mapping change request can be requested by submitting a Case along with the following details:

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

Please note:


See Also
Additional Information

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, 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 SAP Business Network from Ariba Sourcing and then reaches Managed Gateway for Spend&Network, 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 Managed Gateway for Spend&Network (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).


Attached File
Managed Gateway for SpendNetwork - What is the required information I need to provide for XSLT mapping customization.xlsx11.72 KB

Applies To

SAP Integration Suite Managed Gateway > Managed Gateway for Business Network
SAP Integration Suite Managed Gateway > Managed Gateway for Business Network SCC > Managed Gateway for Buyer Business Network SCC
SAP Integration Suite Managed Gateway > Managed Gateway for Sourcing Integration
SAP Integration Suite Managed Gateway > Managed Gateway for Sourcing Integration > Managed Gateway for Sourcing - Contract Workspace
SAP Integration Suite Managed Gateway > Managed Gateway Foundation & Tools > Managed Gateway for Managed Gateway Portal
Supplier Lifecycle & Performance

Terms of Use  |  Copyright  |  Security Disclosure  |  Privacy