cancel
Showing results for 
Search instead for 
Did you mean: 

Message mapping - Duplicate subtree

Former Member
0 Kudos

Hi Experts,

I am working on 7.0 server.

In the existing message mapping I found that target nodes are duplicated.

For example

/ns0:FiletoFile_ib_mt/Record/Emp[1]

/ns0:FiletoFile_ib_mt/Record/Emp

And the order for the node in the target message structure is same as above.

And in the output, the order is reversed as below

/ns0:FiletoFile_ib_mt/Record/Emp

/ns0:FiletoFile_ib_mt/Record/Emp[1]

But when am duplicating one more node in the existsing mapping the order is

/ns0:FiletoFile_ib_mt/Record/Emp[2]

/ns0:FiletoFile_ib_mt/Record/Emp[1]

/ns0:FiletoFile_ib_mt/Record/Emp

And now the output is

/ns0:FiletoFile_ib_mt/Record/Emp[2]

/ns0:FiletoFile_ib_mt/Record/Emp[1]

/ns0:FiletoFile_ib_mt/Record/Emp

But I need the output as

/ns0:FiletoFile_ib_mt/Record/Emp

/ns0:FiletoFile_ib_mt/Record/Emp[1]

/ns0:FiletoFile_ib_mt/Record/Emp[2]

Please let me know if you have faced similar issue.

If am creating a new message mapping and duplicating the subtrees the order is given below

/ns0:FiletoFile_ib_mt/Record/Emp

/ns0:FiletoFile_ib_mt/Record/Emp[1]

Why in the existing mapping duplicate subtree is going in the top order and for new message mapping duplicate subtree is going in the bottom. Please advice

Thanks

Suma S

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Suma.

I'm facing a similar issue. Did you solved this ?

Regards.

Former Member
0 Kudos

Hello Luis! Check if your system has all SP and patch levels according to the note below.

[Note 1371541 - Duplicate subtree is Message Mapping not working properly|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1371541]

Former Member
0 Kudos

Hi Lucas

I checked this sap note but I used PI 7.0.


This happens from 7.10 onwards and this is primarily due to the reason that the occurence of the duplicated node was not remembered when the mapping program gets executed. So, the mapping program was expecting data from the payload for the duplicated node and hence the error