on 06-06-2011 12:01 PM
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
Hi Suma.
I'm facing a similar issue. Did you solved this ?
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.