Virtual Receiver - Why do you 'really' need it?

[Shabarish_Nair]

Lately I came across this

article

on virtual receivers which prompted me to write this blog.<PartnerIdentification><domain><FreeFormText>DUNS</FreeFormText></domain><GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier><locationID><Value>CompanyX</Value></locationID></PartnerIdentification></messageReceiverIdentification><messageSenderIdentification><PartnerIdentification><domain><FreeFormText>DUNS</FreeFormText></domain><GlobalBusinessIdentifier>987654321</GlobalBusinessIdentifier><locationID><Value>CompanyY</Value></locationID></PartnerIdentification></messageSenderIdentification><messageTrackingID><InstanceIdentifier>09c54710419111dd979dddaaabbbccc66666</InstanceIdentifier></messageTrackingID></DeliveryHeader></p><p> </p><p>If you are familiar with the concept of Party, you will know that specific identifiers like DUNS (in the above case) are captured in it. Now take a day to day scenario of the exchange of PIP (RNIF document) to SAP R3 (IDoc) or vice versa.</p><p>The BS for SAP will be found in your SLD. But does it have the DUNS number captured in it? Indeed NO!! So we create a party that will have the DUNS number. Now how do you associate your BS (for R3) to this party?</p><p>In simple terms^@, this is how you can relate it,</p><p>+Business System for R3 = Party + Business Service for R3*+

Now that it's said, lets get into action.

Say a PIP is inbound (Sender adapter) to XI. The sender agreement when created will use the Party, Service and interface defined for the external Customer/Vendor.

Use the VR and then use the combination for your R3 (party + Bus. service) and provide the Sender CC.

So what does this do? Go back to the header of the PIP mentioned earlier in the blog. Doesnt this combination now help to validate the header of the incoming message?

The DUNS number and the details are part of the party and by providing VR and you now expose the BS of R3 as a B2B entity.

Lets continue and now create the Receiver Determination. Don't you think we will have to use the VR option here too?

!https://weblogs.sdn.sap.com/weblogs/images/37298/RD_VA2.JPG|height=387|alt=image|width=677|src=https...!</body>