Unable to convert sender service for IDoc to SOAP Scenario

Hi,
I tried to find the solution my way and by using the search function but without any success. I have the folowing scenario:
SYS(my sap system) => IDoc => PI (Process Integration) => SOAP => XML
When i send the IDoc to the PI System and open SXI_Moni the folowing error is shown:
"Unable to convert the sender service receiver_service to an ALE logical system"
I read about Adapter Specific Identifies so i go to ID->Service without partner->Business System->MyBusinessSystem(SYS) then in Menü on Services and checked Adapter Specific Identifies. They are like maintained in SLD.
Next is a Cache refresh i tried a full one but no impact
Then i tried a header mapping in receiver agreement. I mapped there the receiver party to the definied receiver party and the receiver_service to the service.
I have no idea
Thanks for help, be sure that helpful answers will be awarded
regards
Matthias
P.S. What causes this error ? For my opinion ALE has already done all neccesary things (The Idoc is in PI System and the data is available in mesaage payload) so why didn't the pi map it and send it via Soap?

Hi Matthias
>>I dont know if its helpful but in SLD are only the system of our landscape so i have no entry for the external Party.
Party information is generally not required to be maintained in SLD
>>Adapter Specific Identifies
What is the value you have given for sender Business system->adapter specific identifier. Is it the same as the partner profile name in sender SAPECC. if not try making them same.
Regards
Suraj

Similar Messages

BPM - IDoc to SOAP problem (Unable to convert sender service)

Hi,
I have a BPM scenario where I'm sending an Idoc from r/3 to XI to SOAP. As part of my scenario I'm sending an acknowledgment (ALEAUD) back to R/3.
I'm getting Unable to convert sender service IP_BPEL_INBOUND_ORDER to an ALE logical system on the Ack back.
So I usually know what to do when I get this, I do the SLD settings on the r/3 service and I'm OK. But in this case, it's asking for those ALE settings on the Integration Process?
I tried adding a logical system on it but now I'm getting the error that this is already used by the r/3 service. So I'm not to sure what to do next???
Rgds,
Yves

Ok do one thing, in you mapping take one field at target side (may be u can create one or use which is not been used yet) just map the standard function called Sender to this field in target.
Now in Intergration Directory when you do the header mapping by using F4 do not map the business systems this time, just press the button "Etended Path" (m not sure abt the exact name of this button) not use the X-Path here and select that target field which you mapped with Sender function in mapping.
How To Handle Acknowledgments for IDoc
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
I hope this will solve your problem.
Regards,
Sarvesh

SOAP to IDOC: Unable to convert sender service BS to an ALE logical system

Hello everyone,
I have this scenario where i receive web services calls and have to integrate the received xml messages (idocs) into SAP R3 system.
I allready reveive the message in my XI engine, but i'm getting this error (being BS the name of my Business Service included in my external party):
"Unable to convert sender service BS to an ALE logical system"
I allready tried everything that is specified in this blog:
The specified item was not found.
Probably it doesn' fit my requirements. I'm not sure...
Can anyone help ?
Thank you in advance for any help
Nuno

- do u have the same logical name defined in the BS and in the Adapter specific attributes.
also check if u have defined the logical system (SALE ) with the same name.

IDOC Receiver - Unable to convert sender service to ALE

Hi!!!
I am trying to configure the following scenario: FILE - XI - IDoc to R/3.
A business service called IDOC_Demo recovers from the server the file, and after mapping it, it tries to send it to IBP, the R/3 system using a IDOC Receiver comunication channel.
IBP is configured in SLD.
I have in XI System the RFC conexion, and I have define the port via TCODE IDX1.
But it does not work, I am geting the following error:
"Unable to convert sender service IDOC_Demo to an ALE logical system"
I have checked the adapter specific identifiers, but I can not see anything wrong...
I do not know what can I check! Could someone help me?! What can I do?
Thank a lot!!
Araitz.

Thank you very much, but I still get the error message! Of course, I read your blogs Michal before posting the question, and they have been very useful, but still...
In SLD I only have the R/3 system, the name is IBP and the business landscape and the logical system name (I do not know if this could cause a problem).
The connexion is IBP, and it works, and in idx1 I have configured a port, and its name is SAPIBP, using the IBP connexion.
Design I have imported the CREMAS.CREMAS03 IDOC, and I have done a mapping interface, I have disabled the EDI_DC40, and set begin and segment to 1.
Configuration I have created a business service, IDOC_Demo, that has a communication channel, sender, file type.
And I have the IBP service. In adapter specific I can see: logical system IBP, and R/3 System IBP, client 100. If I push the Compare with SLD button, nothing happens what should happen?
IDOC_Demo receives the file, and via an Outbound, async interface, calls IBP, that receives the IDoc using a receiver IDoc type adapter
Now the receiver agreement has information in the header mapping, sender service, IDOC_Demo, receiver service, IBP.
And I do not know why, but it does not work any idea?
Than you!
Araitz.

Unable to convert sender service(BPM) to an ALE logical system

Hi All,
I am working on simple File to File Scenario where XI picks the File and process thru BPM and sends the file to R/3 Application server and wait for SYSTAT STATUS IDoc for the acknowledgement from R/3 System.
My scenario is working fine by receiving the STATUS IDoc and closing the BPM instance.
But later I am getting System error message as below:
Unable to convert sender service (BPM) to an ALE logical system
Any clues in this case?
Thanks in Advance.
Regards
Sudha.

Hi Rajesh,
1. I am receiving the file into BPM and after validation Iu2019m splitting the file into multiple files.
2. Each split file sent to R/3 Application Server(by activating the correlation with the filename)
3. BPM will wait for SYSTAT STATUS IDoc (by using correlation with the filename) from R/3 System
    for acknowledgement purpose. After receiving the respective STATUS IDoc (with the filename) then
    BPM will close the instance.
4. If the STATUS IDoc not received with in specified duration an alert will raise and close the BPM
    instance.
   So we are not sending the STATUS IDoc data to Sender system.
Regards
Sudha.

Once again: Unable to convert sender service to an ALE logical system

Hi,
I know there's a lot of threads regarding that error but I didn't find one that fits to our current scenario:
IDoc -> XI -> File
We have checked if the logical system name in SALE (of sending system) fits to the one in the business system and it does now.
It didn't fit at first but we've changed it in the SLD and reimported the business system.
We still get the same message:
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:Stack>Unable to convert sender service to an ALE logical system</SAP:Stack>
There is no logical system entered in the receiver business system. Do we need that? But of which logical system?
Thanks for any advice
Karsten

Hi,
Acknowledgments
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender.( Ex : Idoc----File). Here by default Idoc has the inbuilt feature of requesting the Ack.
Acknowledgments are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments.
Sender adapters of the Adapter Engine do not request any acknowledgments
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
Regards
Seshagiri

Unable to convert sender service BPM_Name to an ALE logical System

Hello ,
While sending from BPM to R/3 ( IDOC) i am getting the following error :
"Unable to convert sender service <BPM_Name> to an ALE logical system"
Please kindly advice,
Reddy

Hi Bujji,
I just remembered that you have to maintain your adapter specific parameters for your business process. The side effect however is that you have to define the business process name as logical system in your receiving SAP system and that you have to maintain partner profile settings.
The answer to your question is there in this Blog:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
If the above solution doesnot work.....
You can also try this, don't enter the "adapter specific settings" on the Integration Process. Instead enter a "Header Mapping" Sender Service in the Receiver Agreement. this should be the real sending system.
When you enter "adapter specific settings" in a BPM, the receiving SAP systems ALE layer thinks the sending system is your BPM - using the method discussed here we are overriding that so that ALE see's that its communicating with the real sending system.
I hope it helps....
Regards,
Abhy
Message was edited by: Abhy Thomas

Unable to convert sender service IP_testScenario to an ALE logical system

i have a IDOC -> BPM--->File scenario,
the BPM is named as IP_testScenario
when IDOC is sent from R3 to BPM, in the MONI i can also see a Acknowledgement message saying
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>IP_MMWIS016_01</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service IP_testScenario to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
why this happens...........pls help

Hi..
For Sender you have to create the TS of Type Web AS ABAP right..
While assigning your Bs in ID...Double click on your BS , Goto Service--> Adapter Specific Identifiers..
Hope it helps...
Kumar.S

Getting error message ' Unable to convert sender service to an ALE logical

Hi,
I am using idoc to file.
and my xi system is working fine. at sudden when i process one idoc . I got this message.
Unable to convert sender service to an ALE logical system
Here in monitoring, i am able to see the success falg but in acknowledgement column, i see system error..
I did no change in configuration.
Your inputs will be appreciable.

Hi,
Also, is it possible that the XI system was recently upgraded?
As you indicated that no config changes were done, therefore, such error should not just pop up with no reason.
In an earlier release of XI (sorry I cannot recall the SP level), IDOC ack was not provided. However, in a later release, it is the default.
Regards,
Bill

ERROR"Unable to convert sender service to an ALE logical system,(Urgent)

Hi All when i am not giving the sender service address in the Receiver Aggrement i am getting this perticular error .
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
==========================================
And if i am giving this one then i am not getting any such error rather i am getting another error "Unable to convert sender service to an ALE logical system" for this also i have checked the LS system name in the Adapter specific Identifier and the logical name are exactly same. But still i am getting this error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
=============================================
Still i am getting this error can anyone please let me know what to do now..??
Please treat this as urgent

Hi,
This error is caused when Sender System name does not match the logical system name of partner. As you mentioned you have done all the steps to ensure that, here's a checklist that could be helpful:
1. Check adapter specific parameters for sender system.
2. Maintain header mapping in receiver agreement and ensure that sender service name provided is same as business partner name required in R3 and business partner type is LS.
3. This may sound very basic, but ensure that checkbox for 'Apply control record from payload' is not checked and if it is then the values passed through payload are appropriate.
Hope this would be helpful.
Thanks,
Bhavish

Unable to convert sender party to IDoc partner

Hi guys!
I have read a lot of threads to this topic, however, I can't make my scenario working...
I use Party as sender of document and need to send it to target (our) R/3.
I have set up:
Sender party: Cocoon, Sender Business SERVICE: IslandSys
To target IDoc XML I map:
SNDPRT - KU
SNDPRN - D600
SNDPOR - IslandLS
In Party Identifiers:
Agency: IslandSys
Scheme: ALE#KU
Name: D600
Pertner profile - WE20 (target R/3)
type: KU, No. D600
In Business Service's Adapter Specific Identifiers: Logical System: IslandLS
But the scenario doesn't work..
What's wrong with the config?
Thanx a lot for help!
Olain

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

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
<SAP:P1>http://sap.com/xi/XI</SAP:P1>
<SAP:P2>XIParty</SAP:P2>
<SAP:P3>Cocoon</SAP:P3>
<SAP:P4/><SAP:AdditionalText/>
<SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI / XIParty / Cocoon to an IDoc partner
</SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>

Unable to convert sender service to an ALE logical

hi all,
I have referred N num of blogs and answers in form w.r.t to this error but still not able to resolve the error
analysis wat we have done is:
1. all the ALE settings w.r.t to R3 are correct.
2. LS names are maintained for both sender as well as for receiver in SLD.
3. Adapter specific parameters are been maintained.
This is Idoc to SOAP scenario.
please help us with ur suggestions!!!
Regards
Anu

Hi all,
Thank you all, Finally we could resolve the above error but got stuck with the below error..
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
My message mapping is working fine and even web service is up and running.. any more suggestions

Do we need a sender channel for IDOC to file scenario.

Hi,
Do we need a sender channel in IDOC to FILE scenario.
Because IDOC is being sent by SAP R/3 System and when creating objects in ID using wizard, it doesn't ask for sender channel.
What is the reason for this?
Regards,
Younus

Younus,
to add more...
From <b>WAS(Web Application Server) 6.20</b> and above BASIS is not the runtime for SAP.WAS is the runtime for SAP.
And it has got ABAP and JAVA engine in it.
It handles connections made over various protocols such as SMTP for mail, HTTP(S), and SOAP/XML.
<b>
The SAP Web AS 6.10 did not have a Java engine.</b>
and IDOC and HTTP are present on the ABAP engine and the rest reside on JAVA engine.
and that is the reason why IDOC and HTTP doesnt require Sender Adapter and Sender Aggrement aswell.
Hope i cleared ur point...
Cheers,
Raghavesh
Message was edited by:
Raghavesh Reddy

Unable to Convert Sender Service to an ALE Logical system

Hi,
I am doing a simple SOAP -> PI 7.11 -> IDOC scenario. All objects are created and activated. In testing I get an error
Unable to convert the sender service TemporaryDisconnection_Sender to an ALE logical system
Sender is a Business Service.
I search SDN and found this blog /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
I did the Compare with SLD for the Business System. But still the error comes.
In mapping I Disable EDI_DC40 segment.
Also find one suggestion which tells to change the Header Mapping in Receiver Agreement, what exactly should I put in Sender Communication Component of the Header mapping?
Thank you,
Pankaj.

Hi,
In this thread I could find a solution by Michal: Unable to convert the sender service to an ALE logical system
3. click on sender service (header mapping section) and select your business system that represents XI business system
Will try if it works for me also.
If there are any suggestions, then please do post.
Thank you,
Pankaj.

Unable to convert sender XI party to an IDOC Partner

Hi,
We are doing a IDOC-File scenario for which we got this error Unable to convert sender XI party http://sap.com/xi/XI / XIParty / UK to an IDoc partner .The receiver is a party. We have already set the adapter specific atttributes for the receiver service.

R u using partner type customer.
can u check the configuration refer the below blog.
Wanna Party ?
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
chirag

Unable to convert sender service for IDoc to SOAP Scenario

Similar Messages

Maybe you are looking for