on 2020 Jul 20 3:07 PM
Dear Experts,
Please help me out with a doubt below on customizations in Purchase Order Export Request in Async mode from Ariba to SAP: -
1. Async mode activated
2. Cloud connector or SAP Netweaver PI is used to mediate the communications from CIG to SAP ECC or S4 HANA.
Now if we have custom fields to add to purchase order's header, to my understanding the below are the steps: -
1. Contact Ariba team to create xslt extrinsics for newer fields.
2. Create custom mapping in Ariba CIG, for source doc type "PurchaseOrder Export Request" to target for new fields.
3. Add new fields into ARBCIG_ARIBA_EXTENSION structure in SAP ECC or S4 HANA.
4. Implement badis or exits to fill custom fields of EKKO
Ariba CIG would call BuyerPurchaseOrderCreateRequest_Async_In interface in SAP ECC or S4 HANA via cloud connector or middleware.
My doubt is if we are using: -
1. Cloud connector scenario: - Cloud connector would redirect the payload to BuyerPurchaseOrderCreateRequest_Async_In interface to backend. Do we also need to perform any field additions into any structures here ?
2. SAP PI scenario: Do we need to go for any custom mappings in SAP PI as well in addition to the custom mapping carried out in Ariba CIG?
Please help me in this regard.
Thanks and Regards,
Harinadh
Request clarification before answering.
Hi Harinadh,
Answer for your queries:
Answer: CC is only for authorized connectivity for backend system. It is not related to any custom mapping.
Answer: If you are using CIG with SAP PI and you want to go for custom mapping then only in CIG you have to do mapping. From PI it will be passthrough. CIG will take care your custom mappings.
Regards
Neha Sarda
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.