on 10-27-2015 1:05 AM
Hello there,
I have a B2B scenario where I recieve an EANCOM EDIFACT message for Purchase Orders from our vendor which would have to mapped to the ORDERS05 IDOC.
I have used these links for reference: http://scn.sap.com/thread/3528910
I have reached a stage where the EDIFACT message is failing at the IDOC receiver (IDOC_AAE) because the Sender and receiver paramters of the IDOC control record are missing. I am using XSLT mapping to get the EDIFACT XML mapped to the IDOC, including the header.
I am also using TPM to maintain the partner details.
My question is how would I map the Sender party details to the IDOC control record in XSLT?
Regards,
Amith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Eng Swee..
There isn't any particular reason for using XSLT. It is just my preference.
I wanted to use the Sender Partner name to fetch the Customer Number of the partner in SAP. Ideally, I would use Party identifiers itself but since the sender here is EDI Separator, I am not really sure how I would receive the ALE#KU (partner type) identifier.
I was wondering if I could maintain this is TPM as an identity and fetch it from there? Would this be the best practice? If so, then what would be the agency code?
If I could, then it would make more sense to use message mapping and these UDFs that you have pointed to.
Regards,
Amith
Hi Eng Swee,
I have already used thoise modules to fetch the partner details that are relevant for EDI(GLNs etc).
It is the control record details for the IDOC that are troublesome. I really don't want to hardcode the system details. I guess I will get the Customer number from TPM and the logical system details sender(PI) and receiver(ECC) usinng value mapping in XSLT.
Rgds,
Amith
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.