Problem with IDOC structure update

[Werner_Magerl]

Hello,

I have a problem with an update in the IDOC structure and the depending mappings.

I have an z-extension of an SAP IDOC and SAP did an update in the MAX-occurence field (9 --> 99)of a segment.

I have double checked my extensio in ABAP and then I imported the new strctures into PI (7.11).

In the IDOC XSD I can see the changes in maxoccurence=999 now.

I also can see this maxoccurence in the corresponding message mappings.

But when I process a message mapping and try to create and IDOC with this occurence of this segment >9

then the mapping does not create more then 9 segments.....

Only when I edit the message mapping and save it, then it works correct.

But I have defined about 20 messages depending on this extension and a lot of message mappings

I want to avoid to update all these mappings (about 50) now and to transport them.

Maybe I am wrong, but I remember on PI 7.0 I just had to import the new IDOC structures...and all depending mappings work fine.

Is there anybody having the same problem?

May somebody check on 7.0 or 7.10 if there is the same problem?

best regards

Werner

[Former Member · Accepted solution]

Hi,

Did you deleted the existing metadata in IDX2...where it will have the metadata of the old idoc..

delete the existing metadata and rerun your scenario and check the same...

HTH

Rajesh

[Former Member · Accepted solution]

Hello,

yes, I have deleted the IDX2, but it is not a problem in runtime.

I have the problem also in the repository when I TEST the message mapping.

And this is confusing, because in DISPLAY mode, the mapping show the correct occurence,

but in TEST it works wrong.

Werner

[Werner_Magerl · Accepted solution]

Hello,

did anyboday see the same probem in PI repository????

best regards

Werner

[former_member207622 · Accepted solution]

IF you see the properties tab in message mapping there in you will find a GUID or object id , check the messages in MONI that the same GUID is present , otherwise at run time the PI is using an old version of your mapping.

Do a cache refresh , Delete your mapping and then create with a slightly different name

Hope this helps

regards

Ninad

[Werner_Magerl · Accepted solution]

Hello Ninad,

it is a problem in the repository (also in RUNTIME). But it seems that the problem starts in the repository itself.

In the TEST of the message maping I see the wrong result.

Only updating the message mapping with the new IDOC structure again does help.

But before updating I can see the correct IDOC structure in DISPLAY mode, but the mapping does not work.

best regards

Werner

[former_member207622 · Accepted solution]

This is a strange problem , what I would suggest is , try creating a mapping with differnt name and execute the scenario

before that delete this mapping completely and do a cache refresh.

Are you experiencing this in other mappings as well or this mapping ?

Because in my case , it worked when I changed the mapping name .

regards

Ninad

[Werner_Magerl · Accepted solution]

as I use this IDOC structure in many mappings I have the same problem in all of the mappings I have tested.

I do not need to change the mapping name or so, because when changing the mapping and activating it again,

the runtime works fine.

Does full cache refresh also help for repository????

Werner

[former_member207622 · Accepted solution]

Please check the link for CPA cache refresh

http://www.dataxstream.com/2009/11/changed-rfc-structure-not-propagating-to-xipi-runtime/

on the PI start page , go to administration -- cache overview -- for repository and there do a refresh

regards

Ninad

[Werner_Magerl · Accepted solution]

Hi again,

no, nothing helps.....

I have started all cache refreshs but the same problem.

OSS message????

Werner

[former_member207622 · Accepted solution]

one thing remaining J2EE RESTART , after that you can log a call