Party-based IDOC from external SAP sender

Question

Hello experts.
I have PI 7.0
I have a scenario where I receive an IDOC from an external SAP system - that has SID=PRD and client=400
I also have an SAP system in my landscape with SID=PRD and client=400.
when I tried to define a service and edit it's adapter specific identifiers - i received the following error:
Check Result for Object EXT_SRV
SAP system ID PRD and client 400 already exist in service | PRD400
I understood that the PI will not be able to identify the sender if an it will receive an IDOC with SNDPRN=PRD400
When trying to figure out a way to overcome this and be able to receive the IDOC I came across the term:
party-based communication. I understood that I should define a party an in it a service for the external SAP system.
can some one please show me a detailed step by step example of such scenario?
All I found was this: [Java IDoc Adapter Partner Conversion |http://help.sap.com/saphelp_nw73/helpdata/en/7b/ebc8b9e34b434d9f3e80ef6776d77a/content.htm] and it is only valid for PI 7.3
Thank you very much.

Answer 1

Hi ,
         In idoc communication few fields play a vital role SNDPRN,SNDPRT,RCVPRN,RCVPRT,SNDPOR and  RCVPOR in EDI_DC40 segment. These fields actually identify the sender and receiver systems and ports.
Now in your case as I understood that a new sender SAP system is sending the same  idoc to PI server along with an existing one. In this case you need to alter SNDPRN value to a new value, when you are sending the idoc. All other values will retain same values for same idoc (basic type and message type). In ID add a new party in object list with the new SNDPRN value.
In the  ID scenario create a copy of each entry in interface determination,receiver determination,sender agreement and receiver agreement.  In each of the copy add the new sender/receiver party information SNDPRN value.
This should take care of your problem. No need to do any changes in IR as IR will be common for both the senders, what differs will be the ID. PI server will run different instances of the scenario for different SNDPRN value.
Finally one small request, please kindly if possible close down your threads, in case you got proper and correct solutions to your questions. I noted you closed only one of last five threads you have opened. If you close threads after a solution has worked, then forum users become sure that the solution has worked for your case and therefore is correct.
Regards
Anupam