on 06-22-2012 3:55 PM
The requirement is to split one inbound messages to 2 idocs. Any help will be greatly appreciated. I created 1 message mapping and 1 message interface on the repository. I created 1 receiver determination, 1 interface determination and 1 receiver agreement.
Any help will be greatly appreciated.
Thanks
Natarajan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Greg,
Thank you very much for the response. Yes the idocs are of separate type (DELINS and ORDERS05). The requirement is that confirmed order received in the inbound EDI message should be mapped to ORDERS05 and forecast data in the EDI message should be mapped to DELINS. For this we have created 1 message mapping, 1 message interface on the repository, 1 receiver determination, 1 interface determination and 2 receiver agreements. Please let us know is there anything else that needs to be done?. Also we are using SPS13 of PI 7.1
Regards
Natarajan
Your objects checklist is still missing Sender Agreement and Sender&Receiver Communication Channels. Do you have them in place? By the way, the best way to verify if your configuration is complete is to go to the "Configuration Overview" tab page of your Receiver Determination and see if it shows any errors for your desired receiver. Or even better: run the scenario did you experience any problems with that?
Regards,
Greg
Hi Greg and Amit,
Thank you very much for your help. For some reason the second idoc (DELINS) is not getting produced. I am looking into this right now. When I disable the second idoc, first idoc message got created in PI successfully for ORDERS05. Then when I disabled the first idoc and processed the message, I am getting error Runtime exception when processing target-field mapping /ns0:Messages/ns0:Message2/DELFOR02/IDOC/. Is there an easy way to find out where the mapping is failing?
Regards
Natarajan
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
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.