ATTRIBUTE_INV_SND_SERV

[Former Member]

When I receive a message of a party I get the following message

Unable to convert sender XI party http://sap.com/xi/XI/SiXe/ to an IDoc partner

The WE20 customizing in R/3 is KU / SP / 0000001070

I tried already a lot of settings with header mapping and schema's but I don't get it working.

Any suggestions?

Ron

[aashish_sinha]

Hi,

This error come because of " In the Integration Server (IS) of the Exchange Infrastructure, the system issues an error message stating that the sender service cannot be converted to an ALE logical system when the acknowledgement is sent back to the sender."

In the IS, the system does not add a sender to the system acknowledgment if the acknowledgment is sent from the Integration Server and the recipient is not yet or could not be determined.

If an IDoc inbound adapter was used to receive the request message in the IS, the system issues the error message mentioned above.

If this error occurs even though the correction is already implemented in your system, check the connection to the System Landscape Directory (SLD).

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/corr_instr/correction_instructions.htm?...

check out the corrective package download using above link.

Regards

Aashish Sinha

PS : reward points if helpful

[Former Member]

Hi Ron,

I think you are getting this error message in call adapter of SXMB_MONI .

check this..

1. Check the business system's "Logical system" name is correct with that of SLD.

2. In your receiver communication channel ...go to Identifiers tab and check the agency and schema of both the sender and receiver....this should be same as the agency and schema defined mentioned both the party's.

cheers

Sunil.

[Former Member]

Hello Sunil John,

You are obsolutely correct and it worked.

Thanks and sorry it was not my post and so I could not assign any points.

Shall I create a new post with the same query and assign you the points after your reply or is there any way to assign you the points.

RGds,

Vasanth.

[Former Member]

thanks vasanth

[anupam_ghosh2]

Hi Sunil,

This has solved my problem too. Thanks a lot. I was struggling with this problem for long time.

All the best.

Anupam

[former_member185856]

Hi Sunil,

I am facing the same issue and referred many blogs and changed settings as per the blogs.

1. Adapter Specific settings says same Logical system maintained in SLD and ALE service

2. Header mapping done for receiver agreement by selecting the Sender Service and also selecting receiver service

Regarding the Idetifiers tab:

I didn't find any values in the IDENTIFIERS Tab in Receiver Communication channel.

Could you please let me know what values I need to fill.

Details of the Error:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>

<SAP:P1>CAPTOR3_PRU</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unable to convert sender service X12345X to an ALE logical system</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Please help me.

Thanks in Advance,

Sunil.

[Former Member]

Hi,

For the business sytem you have to mention the adapter specific identifiers in the Integration Directory.

Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers

Maintain Logical System name and System ID and Client number.

Trouble shooting file to IDOC and IDOC to file

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario

Refer below links for indepth troubleshooting

Refer below steps

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

IDOC to File steps to be followed please verify your scenario with it

R3 system.

1. Create SM 59 RFC destination to XI,.

2. We21 - Create port to XI.

3. We 20 -- Maintain Partner Profile for the outbound Idoc.

XI SLD

1. Create technical system for R3 system

2. Create Business System for the Client of the R3 system.

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

These are the required steps for IDoc to File scenario...

In R3 (i.e., your IDES system)...

RFC dest to XI (sm59) - any name

Logical system (bd54) - any name

Port to XI (we21) - any name

Partner profile for the logical system (we20) - use Logical system name created in bd54

In XI...

RFC dest to R3 (sm59) -

Port to R3 (idx1) -

create metadata for the idoc (idx2)

In sld...

create business system for R3 with Logical system name as r3 sys.

In we19

and give in control record as

Sender : Port ; Partner

Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>

see the below links

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

Also

/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133

IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario

Thanks

Swarup

[stefan_grube]

Check this document:

https://websmp202.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700003604082004E

Regards

Stefan

[Former Member]

Hello Stefan,

I too face the same error.But unfortunately the link you have provided is not valid

could you please be so kind and check it once.

RGds,

Vasanth.