on 01-13-2016 3:32 PM
Hi experts,
we are facing a problem with PI-AAE IDOC-Adapter after migrating from PI double stack to AEX.
We have to send ALEAUD IDOCs from ECC to a third-party system via PI AEX.
In this case the value of the control record field SNDLAD is empty (the field is not shown in message monitor).
In ECC the element SNDSAD of table EDIDC is filled with the specific value accordingly.
If we are sending other IDOCs like ORDERS through the same sender communication channel everything works fine.
Please help on this.
Please let me know if any more details is required.
Regards
Andreas
I opend a OSS ticket and there was an error in IDoc-Adapter.
SAP will deliver a patch for this issue.
Nonetheless thank you for your input.
Regards,
Andreas
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.
Hello Andreas,
Are you using Apply control record from Payload option in the idoc channel?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Raghuraman, in the scenario described by Andreas, SAP ECC acts as a sender system, so it should be Java IDoc sender communication channel which is used for ALEAUD IDocs processing. As to my knowledge, "Apply Control Records from Payload" is only relevant for Java IDoc receiver channels, isn't it?
Regards,
Vadim
Hi Andreas,
Please check a mapping for the affected scenario - is field SNDSAD from a source message (IDoc) used in mapping rules for required target element(s)? IDoc object generated by Java IDoc adapter contains standard IDoc control record structure (which also includes this field) and which is then propagated to a generated XI message and is accessible from the mapping, being a part of IDoc source message structure (a child element of EDI_DC40 structure of a message type).
Regards,
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Vadim,
I activated the message staging for step MS (Before mapping step)
See Message Staging and Logging Options in Advanced Adapter Engine of PI/PO 7.3x/7.4.
And in this early stage the attribute is still not visible.
So from my point of view it shouldn’t be a mapping problem!
Regards,
Andreas
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.