Regarding Error: Unable to Convert Sender System to ALE Logical System
Hi friends,
in File to IDoc scenario, i created a sender business system called bs_filetoidoc_send based on Standalone technical system and a receiver business system based on ABAP r/3 system. in my SAP IDES system which is dual stack (abap+java), XI client is 001 (LS: devclnt001) and r/3 client is 800 (LS: t90clnt090) i.e i'm posting idoc to t90clnt090.
I tried to send a text file. but while processing xml message in XI, i got an error saying "Unable to Convert Sender System to ALE Logical System".
then i searched the blogs and forum and found the solution. it was saying LS name was not assigned to BS bs_filetoidoc_send. so i went to SLD and tried to assign LS devclnt001 to my sender BS bs_filetoidoc_send, but got an error saying that "A business system with LS devclnt001 already exists". when i checked which is that BS, it is supposed to be the INTEGRATION SERVER itself with BS name INTEGRATION_SERVER_DEV.
then i configured my sender BS as INTEGRATION_SERVER_DEV itself which picked up the text file successfully and also receiver abap server received the IDOC with correct data and format with status 51. so scenario worked fine when i used my sender BS as INTEGRATION SERVER itself.
please clear my following doubts which arose after this scenario.
1) why the scenario didn't work when I used only standalone sender business system?
2) why should we assign a LS name of XI server to sender business system only in this scenario?
scenario worked according to my requirement, but using integration server itself as a sender BS confused though.
Many Thanks.
1) I can create any no of LS names using SALE
Yes you can create.
> 2) But I can assign a client to any one of those LS names (or 1 client will have only one LS name associated with it)
One Client will have one LS associated to it...and that can be any one of the LS..created.. use SCC4 to find the associated Ls for all the clients of a system
3) So anyways INTEGRATION_SERVER_DEV has to associated with the client 001 only, so finally I have to use INTEGRATION_SERVER_DEV only as my sender BS. Probleum is that I can't remove the LS name DEVCLNT001 from INTEGRATION_SERVER_DEV and assign it to bs_filetoidoc_send BS right. If I do so, I think I would get an error saying that INTEGRATION_SERVER_DEV is not associated with the LS name of client 001.
As the logical system defined in Partner profile is expected to arrive in Control record of IDoc..it should be passed in that...
Did u checked this blog../people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system so as per you need the explaination in the blog need to associate the logical system name .
HTH
Rajesh
Similar Messages
-
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" ?>
- <!-- Call Adapter
-->
- <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" ?>
- <!-- Call Adapter
-->
- <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 urgentHi,
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 send system to ALE logical system
Hi Expters,
I am doing FILE 2 IDoc Scenario as follows...
Created 1 BS for sender as Third Party...
Created 1 BS for receiver as WebAs ABAP...
I did everything perfect in IR and ID. But I am getting error in end to end testing. I am placing file in my local drive and the file has been picked up correctly.
And also I can see my Logical System name in ID(Adapter Specific Identifiers) towards my receiver BS. But There is no logical system is displaying for the sender BS in ID.
Still I am getting Error: Unable to Convert Sender System to ALE Logical System...
I have followed blogs and wikis but not successfull...
Do needful in this regard...
Regards,
Basha.Hi,
Refer this link
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Problem Unable to convert the sender service to an ALE logical system
http://wiki.sdn.sap.com/wiki/display/XI/UnabletoconvertSendersystemtoALElogicalsystem
Regards,
Nithiyanandam -
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. -
Problem converting Integration Process to ALE logical system(acknowledgmen)
Hello,
I have a scenario where a sender SAP system sends an IDoc via an Interface Mapping to an Integration Process.
This worked perfectly fine on our development environment, but after transporting the scenario to our quality systems I got the following acknowledgement error:
Unable to convert the sender service <i>name of integration process</i> to an ALE logical system.
What could be the reason for this? We have a logical system on the sender SAP system set up for the XI system itself but not for the Integration Process.
We also use SYSTAT IDocs and there we set the the logical sender system name to the logical system for SAP XI and not for the integration process.
Is this also necessary for acknowledgements? Where could this be done. Strange thing is that it works perfectly fine on our development environment.I raised the same question a few months back.Answer to this question is in the same thread.
Idoc Acknowledgements - Logical System Name
You will have to select option "Restore Original Parties for Idoc Acknowledgments " in the Acknowledgment Idoc adapter.
Regards
Bhavesh -
Unable to Convet IntegrationProcess in to ALE Logical System
Hi,
I am working on a BPM where i am using the two synchronous steps the process is working fine but iam not getting the Outbound messages and when i cheak in the Acknowledgement xml message its saying that unable to convert integration process in to ALE Logical system is this any thing to do with the IDOC Configuaration
AmareshHi,
If Integration Process/Business Service is used as a sender whilepostng IDocs to SAP System, it will identified by its Logical system name... which can be set in the adapter specific identifiers.
So go to your Integration Process
Menu path : Integration Process>service>Adapter specifc identifiers. Specify the Logical system name.
Check this blog
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Regards,
Prakash -
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,
ReddyHi 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 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 -
Sender service to an ALE logical system
Hi,
I have a question. I am getting an error "Unable to convert sender service to an ALE logical system". Please help!
Thank you.
regards,
Karun.MHi Karun,
Take a look at this excellent weblog
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
thanks,
Prashanth -
Error "Unable to convert the sender service to an ALE logical system"
Hi,
I send I message from XI to R3 and I get the error "Unable to convert the sender service to an ALE logical system" in transaction "sxmb_moni". I've configured the idoc-adapter, as following:
-I have created a business system "r3sys_bs" with a logical system "r3system". This business system is the idoc-adapter. This logical system is also created in transaction "bd54". In the ID I have assigned the business system the logical system (adapterspecific identification).
So, this error still appears.
Can anybody help me please?
Regards
StefanHi,
our scenario is JMS --> XI --> IDoc
so, I have created a business system "jms_bs" without a logical system in sld, that I use for the jms-connection to another software. so, the business system is a "third party".
Then I have created a business system with assigned logical system for the IDoc-Receiver as I in my first posting mentioned.
Which of both business systems need a logical system?
Thanks
Regards
Stefan -
Unable to convert the sender service XID_900 an ALE logical system Error~
Dear Expert:
I received a IDOC Ack but there is an error ocour~
Unable to convert the sender service XID_900 an ALE logical system
XID_900 is our business system that config in SLD.
it's very weird ....sender server should be like point to our BPM isn't?
Regards
Jack Leehi,
>>>it's very weird ....sender server should be like point to our BPM isn't?
this means that your XID_900 business system in Integration directory
does not have adapdater specific identifiers filled in
it has nothing to do with a BPM
also check out my blog:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Regards,
Michal Krawczyk -
Hi All,
File to IDoc scenario.
1. Business system is correct because its working for other scenarios.
2. I checked Adapter Specific attributes in Business service and given Partner number which in maintained in WE20 for the partner in R/3.
3. Refreshed cache.
But still... its showing the below error.
<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>BS_PARTNER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service BS_PARTNER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea what might be wrong?
Regards
Deepthi.Hi Experts,
Could you please help me to fix this.
SCENARIO: SAP - IDOC -
> XI -
> SOAP Adapter (Webservice)
Workaround:
1. Verified Adapter Specific configurations and its fine with same Logical system in SLD and ALE service.
2. Header mapping in Receiver com channel : Sender service and Receiver Service is assigned
3. Identifier Tab in comm channel details: Its empty - no values.
SXMB_MONI :
Error Details:
<?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>
Thanks in Advance,
Sunil. -
Unable to convert the sender service PPG to an ALE logical system
Hello all,
maybe anybody can help or give me further information.
I have set up a scenario to send IDOC from a business system ( ERP ) to a business service ( EXT ).
Receiver is a linux system so I use the FTP-FILE adapter as communication channel.
The send-process is so far ok.
Here my tests:
1) exclude the specific IDOC in IDXNOALE table ( means no technical acknowledgment for this IDOC )
result :
a) message in SXMB_MONI: status-flag: processed, acknowledgment-flag: not in use
b) message in RWB-Monitor: Sender ERP --> Receiver EXT ok
2) But I would like to have a system status..... here now the problem
add specific IDOC into IDXNOALE table ( for request acknowledgments )
result:
a) message in SXMB_MONI: status-flag: processed, acknowledgment-flag: acknowledgment not possible
--> error message: unable to convert the sender service EXT to an ALE logical system
b) message in RWB-Monitor: there are now two message,
first: Sender ERP --> Receiver EXT = ok
second: Sender EXT ---> Receiver ERP = system error
Receiver-Interface is : http/ww.ahlstrom.com/EXT/ MI_IN
3) furhter tests:
a) change FTP apdapter channel ( put some wrong settings )
message in SXMB_MONI: status-flag: processed, acknowledgment-flag: contains system errors
message in RWB-Monitor 3 messages ( one ok, and two error messages )
b) changed only the receiver communication channel to HTTP ( other extisting scenario )
then the acknowledgment works fine wihout errors.
I'm wondering, but here Receiver-Interface is: http://sap.com/xi/xI/Message/30/Acknowledgment
Summary: The process works, but strange:
message in SXMB_MONI: unable to convert the sender service EXT to an ALE logical system
message in RWB: system error
No problems with HTTP adapter
Regards,
Reinhard DoekerHi,
Addition to the above said by Udo...
for routing the ack back to the sender system you need to create communication channel of type idoc with name as Ack.....
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true
Check the above link section 3.2
HTH
Rajesh -
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. -
Unable to convert the sender service ABC_Service to an ALE logical system
Hi,
I have a JMS (Party) --> PI --> IDOC scenario.
Party: ABC_Party
Service: ABC_Service
I am getting the error Unable to convert the sender service ABC_Service to an ALE logical system when I test the scenario using RWB -> Component Monitoring -> Integration Engine -> Test Message.
I have already done the below settings:
1) Defined Header Mapping in Receiver Agreement for IDOC (Sender Party, Sender Service and even Receiver Service are specified)
2) Business Component (ABC_Service) -> Adapter Specific Identifiers -> mentioned details for SAP (IDOC) system.
The scenario works perfectly fine for a party-less communication JMS -> PI -> IDOC
Have already seen:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
Thank you,
Pankaj.You need to create party if its a B2B scenario
Under Identifiers
under agency select any standard agency , scheme name will automatical;ly get populated and name you can give manually as sender name
Please refer this for more details
http://help.sap.com/saphelp_nwpi71/helpdata/en/b9/64663c7a6c2545ae292fb26d8c33c4/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/104bb1fbab254c8644877c7f856bbf/content.htm
Re: Party Configuration
In case of cross company process it is required
Regards
Ninad
Edited by: Ninad Sane on Nov 18, 2010 11:17 AM
Maybe you are looking for
-
IPod freezing in the middle of a sync!
This happens to me almost every time I connect my 5G Black Video iPod to the computer. 1. I connect the iPod and iTunes opens and then the iPod shows up. And it starts to update. 2. After a while it stops on a file. Still saying that its updating. An
-
Automatic startup of database in Unix
I would like my database to startup automatically whenever the server starts up. Where do I put the startup scripts in Unix?
-
Table Name Storing date/time Data Loaded.
Hi All, In BI I have few Info Providers to which data will be loaded frequently. Is there any table in BI which stores the information like the date and time the data was loaded to the corresponding Info Provider. Is there any table as such?? If yes
-
PayPal Chained Payments integration
Hi all, I'm trying to use PayPal to integrate Chained Payments, but can't get it to work. Has anyone experience with this feature of PayPal and Apex? The Express Payments are working well, but that is not what we need... Regards, Jan
-
Help! I recently upgraded to Yosemite OS on my iMac desktop. I then needed to upgrade iPhoto which I did yesterday. Now, when I open my iPhoto icon there are only about 100 photos left of probably about 1,000. I should mention that all the photos