cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to See Custom Field value in the Idoc at ECC

Former Member
0 Kudos

Hi all,

We  are using ZINVOIC02  custom idoc  where  we create a custom zsegment with addition of two field. 

We replicate the required changes in DEV and TEST both. 

Its file to Idoc  interface.    But when do the testing in DEV it works fine and  new field values apppeared at ECC side  in WE02.

We transport all the ABAP development and PI development  Object to TEST environment. 

But when tested in  TEST it does not show the  new field value in IDoc.

we increase the payload persistance at PI side  to show how the Idoc structure is creating and it shows well and populating new field in  the IDoc structure.

This is interface was working earlier  with other custom fields but this time it did not .

We retransport all the configuration  from  DEV to TEST and compare the same. 

1. We checked the version History , logs, caching in PI and its fine.

2.  Can we check somthing at  ECC side to ensure what its receiving from  PI side,

3.   Can we have related transaction for Idoc to validate , do we need to activate again  any thing in TEST still we are transporting those changes

Any input or  link on that would be thanks ful

let me know if any other input required to resolve this issue. 

regards

Ram Singhal

Accepted Solutions (1)

Accepted Solutions (1)

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi Ram,

Are you able to see new segment in WE 02-Test environment? if yes then problem with meta data , follow Anupam suggestion,import meta data once again.

Regards,

Raj

Former Member
0 Kudos

Thanks Raja,

I am able to see the  segment at We02  but  not all  new  fields.

But when we  run we19   then new field appear over there.

probelm is that its find in dev but  not in test.

we reimport the transport in ECCand PI again. 

Let me know if we need to check any thing which we need to use in ECC transport  or which we need to use in  PI Transport.

We  use the trace  and check the logs  and all does not say any thing. 

do we have any place in ECC where we can see how the idoc is receiving at ECC end  except We02/we05..

And one more question  Does WE02 Means its PI provided metadata. 

regards

Ram Singhal

Former Member
0 Kudos

Hi Ram,


any luck ? Could you resolve it ? In SAP PI 7.3 single stack, though the Meta data cannot be imported through IDX2 , the meta data has to be refreshed.

Though we can see the value going out through the payload, the value dosnt reach the ECC system. The only solution to this in SAP PI7.3 is to restart the system , so that the meta data gets refreshed. This issue has been addressed in SAP PI 7.31 .

Try this out , and let us know, if this works.


Thank you !

Regards,

Hemantika

Former Member
0 Kudos

Hi Hemantika,

thanks  for your input .  It works after PI restart. 

Regards

Ram Singhal

Answers (1)

Answers (1)

anupam_ghosh2
Active Contributor
0 Kudos

Hi Ram,

             In the ECC side check if the transport of changes (related to idoc structure) to TEST env is complete or not. Secondly whether structural changes have been released or not in ECC. Thirdly during transport please check if you have transferred the external definition related to the idoc(if any) or not. 4thly you need to check if in message mapping the new fields are showing properly or not. Finally use idx2 transaction in PI to delete the idoc metadata  and rerun the scenario.

Regards

Anupam

Former Member
0 Kudos

Thanks  Anupam,

We check all the transport both in PI and ECC ,

Both side structure is available.

We are on PI 7.3 java only stack , So no IDX2 requried.   Message mapping works fine.

We increase the persistance level too  to see the inbound payload and it shows new field in the idoc after all the execution completed in  PI.

regards

Ram