Unable to convert receiver to IDoc partner (IDoc 2 external R3)

[Former Member]

Hi Folks,

I tried to send a idoc from R/3 2 XI 2 external R3 and recieved the folowing error:

Unable to convert receiver XI party

http://sap.com/xi/XI/XIParty/<partner>; to an IDoc

partner.

until now I testet:

1) configuration wizard: partner communication with a internal system (business system of sld) and a communication partner (<partner> with a business service)

2) integration scenario with internal system and b2b partner

I played around with the identifiers for partners and communication channels but nothing happens. Has anyone an idea..... ?

thx in advance

Martin

[STALANKI]

check thz out wether it will be helpful

/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party

[Former Member]

thx for your answers, but the "issue" is still the same.

I've created the following objects in integration directory:

1) sender: service without party (INT-R3)

2) reciever: party (EXT-Party) ; identifiers

3) Both, business service and ext. business system (3rd Party in SLD) tested.

4) communication channel

5) reciever det. :

sender: party: empty, service: INT-R3

reciever party: * , service *

6) reciever agreement:

sender: party: empty, service: INT-R3

reciever: party: EXT-Party , service: EXT-Service

7) result:

a) With empty reciever-party and the correct business service I get following error:

Receiver service ****** cannot be converted into an ALE logical system

b) No Mapping

Unable to convert receiver XI party http://sap.com/xi/XI/XIParty/****** to an IDoc partner.

c) Everything works fine if I use Header-Mapping to set reciever-party empty and reciever-service to ANY business system of SLD. Idoc reaches the correct System.

I'm sure it's only a little error in reasoning but...

[Former Member]

Martin,

<i>1) sender: service without party (INT-R3)</i>

As ur telling that it is B2B scenario, the above is wrong. Both sender and receiver are both parties only.

U take sender and receiver of the scenario as a whole. Then both of them are external to each other.

-Naveen.

[Former Member]

Hi,

Make sure you partner profile settings are correct.

Also, we need to specify party for external systems.

As long as it is not a logical system, we need to specify the party.

You would have to create a party in the sld and import the same into the configuration.

Regards,

Smitha.

[bhavesh_kantilal]

Hi,

have you created a receiver service / business system in the SLD ,pointing to the receiver r3 system and used it in your configuration for the R3 system?

Regards,

Bhavesh

[Former Member]

Martin,

Check if this helps.

https://websmp108.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=011000358700000002...

-Naveen.

[Former Member]

Hi Naveen,

thanks but this won't help at all. The SAP XI IDoc-guides apparently don't discuss communication with external partners. Even saphelp or service (note 792333) aren't very useful....

Martin

Message was edited by: Martin Sliwka

[Former Member]

Martin,

Do u have everything setup at both the ends (for both O/B and I/B).

-Naveen.

[Former Member]

Hi Naveen,

I'm not sure what you mean, but I think I've setup everything what you need for idoc2idoc communication (by hand, with wizard, with importing integrationscenario).

I just discovered that making the following changes to the header mapping of the reciever agreement will solve the problem, but I think it is not a clean way:

reciever-party: empty

reciever-service: <any business-system>

The message reaches the correct reciever but: Why works with a "wrong" entry and why it don't work with the "correct" service as reciever?!

[Former Member]

Martin,

<i>reciever-party: empty</i>

Receiver party should not be empty, if I am right.

In any scenario party field would be empty only if it is an A2A communication(with in the company). As urs is a comm with external R/3 system(B2B comm, as I understood it), party field should be filled with approriate entry.

-Naveen.