cancel
Showing results for 
Search instead for 
Did you mean: 

ECC to PI-AAE IDOC-Adapter control record SNDLAD has no value

stuerzea
Explorer
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

stuerzea
Explorer
0 Kudos

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

Answers (3)

Answers (3)

stuerzea
Explorer
0 Kudos

Our basis team installed the xpi-inspector in PO Server, as suggested by Vadim.

In the xpi-trace i got a value for the SenderLogicalAddress field

However in the message monitor (stage MS - before mapping happens) the complete tag (SNDLAD) is missing

former_member186851
Active Contributor
0 Kudos

Hello Andreas,

Are you using Apply control record from Payload option in the idoc channel?

vadimklimov
Active Contributor
0 Kudos

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

vadimklimov
Active Contributor
0 Kudos

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

stuerzea
Explorer
0 Kudos

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

vadimklimov
Active Contributor
0 Kudos

Andreas,

Can you please check in IDoc Monitor in PIMON of a PI system, if this field is populated with a value? Alternatively, XPI Inspector trace of a Java sender communication channel and Messaging System will also be helpful.

Regards,

Vadim

stuerzea
Explorer
0 Kudos

Hello Vadim,

I can not find the field SNDLAD in IDoc Monitor

This is the information which is displayed in the control record tab of the IDoc Monitor.

Are I'm missing something?

Regards,

Andreas

former_member186851
Active Contributor
0 Kudos

Hello Andreas,

How your getting the Control record values?

If through XML ensure you mapped the SNDLAD Field

manoj_khavatkopp
Active Contributor
0 Kudos

Hi Andreas,

Check in ECC whether they are populating SNDLAD field or not ?

Br,

Manoj

former_member182412
Active Contributor
0 Kudos

Hi Andreas,

In the IDoc monitor Control Record tab display only important fields not all the control record fields. You can find them in actual payload.

Regards,

Praveen.