New mapped fields in existing SOAP to IDOC are not getting updated in ECC

[Former Member]

Hi,

In an existing SOAP to IDOC scenario, New field have been mapped and during run time mapping also working fine and in outbound payload i could see the new mapped segments and fields. But in ECC side they are getting only existing fields and new mapped fields are not getting updated. Is there any way other than SXMB_MONI to check the values passing from PI contains new mapped fields.

Below highlighted segments are newly mapped and it is available in Outbound Payload in PI.

In ECC the IDOC is reached with error and new mapped segments are not updated.

Please Help..

Thanks & Regards,

Vinoth

[former_member183908 · Accepted solution]

use IDX5 in PI and check for your IDOC payload, even after reloading metadata does not help then you need to debug the FM associated with inbound process code in SAP ECC

Thanks

[Former Member]

Thank you all... It worked.. There was some problem in ECC and FM has been debuged.

[former_member201275]

The layout of your idoc doesn't look correct.

In your 2nd screenshot, you have E1EDP02/03/19. Are you expecting entries in there, because if you display these segments in ECC then you will see they contain no fields anyway.

What you can do, in ECC, is go to transaction WE19 and enter your IDOC number and retest it i.e. check the fields you want are there and filled. If not then you can put values in here yourself to test.

[pvishnuvardan_reddy]

Hi Vinoth,

I echo with out colleagues. It looks like metadata issue.

Please reload the metadata into PI, if you are on ABAP stack then using IDX2, if you are on Java stack then Monitoring & Configuration-->Adapter Engine-->IDOC Adapter Monitor-->Meta Data.

After reloading of metadata, do a dummy change in the existing message mapping and then activate it.

Then do testing.

Regards

Vishnu

[sahithi_moparthi]

Hi Vinoth,

As suggested by Priyanka,Please reload the metadata in PI.

If you are on ABAP stack then reload the metadata using IDX2.

If you are on single stack re-load the metadata using Monitoring -> Adapter engine -> IDOC adaptermonitor -> Metadata Monitor.

[PriyankaAnagani]

Hi Vinoth,

Try to reload the metadata of IDoc into PI & restart the IDoc receiver communication channel and then retrigger the interface.

Regards,

Priyanka