Error: Receiver Service Cannot be converted into an ALE logical system

While doing scenario FILE to SAP R/3 by using BPM we get following error message:
<IDOC_Adapter> Attribute_INV_REC_SERV
SAP system is not able to receive the output.

Hi,
Goto Integration directory.
Click on your integration Process ( imported BPM).
Then check the Service in the menu bar of the Integration process.
You will have adapter specific paramters.
Give the logical system name of PI for the integration process.
This name will be used as the logical system when sending IDOC.
Hope this helps.
Regards,
Viany.

Similar Messages

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

Hi,
I am hoping for some help with an Idoc issue in XI version 3.0. The scenario is like this:
Flat file->File adapter->XI->Idoc adapter->R/3
I have configured a scenario in one system like this that works fine. But in the current system I am getting the error message "Receiver service ??? cannot be converted into an ALE logical system" from the Idoc adapter.
As it is XI 3.0, I have set the Agency and Scheme in the destination communication channel to <Service>, ALE#LS and in the destination party, I have created a alternative identifier <Service>, ALE#LS, SYSCLNT200.
I have configured an ALE logical system name in the SLD.
I have cleared the SLD cache in the integration builder.
The ALE logical system name was not in the SLD when the message first appeared, but I thought clearing the cache would fix that. I have not tried deleting the service and re creating it. That is my next step....if all else fails.
Not sure what else I haven't tried.
Can anyone offer any advice?

Thanks Sam Raju for the reply.
On your questions:
1. I checked IDX1 - port for the receiving R/3 is defined as SAPIR1_300 (port: SAPIR1 and Client: 300) and it is mapped to RFC destination of IR1300.
2. Checked RFC destination IR1300 - it is setup as R/3 connection and checked test connection and remote login and both are working fine
3. Checked IDX5 - did find one message (status is successful) corresponding to the file I am sending into R/3 and this entry is an Outbound entry.
Question: Should there be two entries here in IDX5 - one for inbound and the other for outbound?
May be I am doing something wrong here in setting up the interface mapping and endpoints. Anyway when I check the IDOCOutbound in the Soap Header, I see the following:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/exchange/MessageFormat/">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCNUM>0000000000008002</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>FLIGHT_SAVEREPLICA01</SAP:IDOCTYP>
<SAP:MESTYP>FLIGHT_SAVEREPLICA</SAP:MESTYP>
<SAP:SNDPOR>SAPBXI</SAP:SNDPOR>
<SAP:SNDPRN>PRISM</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:RCVPOR>SAPIR1</SAP:RCVPOR>
<SAP:RCVPRN>IR1CLNT300</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
</SAP:IDocOutbound>
Do you see anything wrong or missing here. SNDPOR is XI port, SNDPRN is the source partner (file) and RCV... information is all the receiving R/3.
I am suspecting that something is missing either here or in the endpoint setup.
Also, in the TechnicalRouting I have this:
- <SAP:address version="20">
<SAP:systemKey>IR1CLNT300</SAP:systemKey>
<SAP:endpointType>IDOC</SAP:endpointType>
<SAP:url>IDOC://SAPIR1?RFCDEST=IR1300&DOCREL=&VERSION=3&SAPREL=46C</SAP:url>
</SAP:address>
Any issues you see here in url?
Also, when I look on the XI server, I do not see these files deposited anywhere- so they are going somewhere (as the status in IDX5 is successful)!
Do I need to activate any queues or triggers anywhere.
Can you please offer advice and help us out.
Thanks again.
Srini
[email protected]

File2idoc receiver service cannot be converted into ale/logical system

hi
i m working with file to idoc the file adapter is working fine bit\ut wen i checked in
sx_monitor i found the red flag and it shows the error
receiver service cannot be converted in to ale/logicalsystem

Go to the Business System / Service you have maintained for your File.
Double Click ,Business System --> Adapetr Specific Identifiers.
Here, maintain the Logical System name of the Sender System. This logical system name should be the value for which the partner profile
has been created in your SAP system in we20.
The same should also be maintained for your Receievr Business System.
Regards
Bhavesh

IDOC to abap proxy- Receiver Service Cannot be converted into ALE logical

Dear all,
I have idoc to abap proxy -
R3 to SRM scenario.
I am getting the error Receiver service cannot be converted to ale logical system.
I have check the receiver bs SRM_BS , adapter specific attributes ... im getting the logical system ( this is not the problem)
i am using receiver XI adapter
with XI 3.0 as protocol
and http destination with /sap/xi/engine?type = receiver
i can see the data in the moni of receiver SRM system but it shows a red flag
pls help

Hi kiran,
i have checked all the RFC destinations ... seems OK
problem is in SRM moni .. sender service and sender interface are not visible.
trace ::::
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:03Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DD2FF717DAE395F186DF001560A1C7CB</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:04Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
- 
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o3314" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_SY_NO_HANDLER id="o3314">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o3313" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1564</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_NO_CHECK />
- <CX_SY_NO_HANDLER>
<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
</CX_SY_NO_HANDLER>
</cls:CX_SY_NO_HANDLER>
- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o3313">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1738</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
fault message says the sender is not having logical sys...but my sender sys is showing logical system in adapter specific attributes
pls help
points will be awarded

Filt to IDoc: cannot convert sender to ALE logical system

Hi there,
i have used forum search for my issue, but could not figure out the issue by myself so far.
I tried to read a file into PI 7.0, map to and IDoc and send IDoc to SAP system. I have the following configuration:
Sender: SYSTEM_A
---Logical System <none>
Receiver: SYSTEM_B
---Logical System: EIECLNT300
the IDoc i'm sending looks like this (most of them dummy values):
<?xml version="1.0" encoding="UTF-8"?>
<ORDERS05>
<IDOC BEGIN="value2">
---<EDI_DC40 SEGMENT="value2">
<TABNAM>value2</TABNAM>
<DIRECT>value2</DIRECT>
<IDOCTYP>value2</IDOCTYP>
<MESTYP>value2</MESTYP>
<SNDPOR>EIECLNT300</SNDPOR>
<SNDPRT>value2</SNDPRT>
<SNDPRN>PITCLNT001</SNDPRN>
<RCVPOR>value2</RCVPOR>
<RCVPRN>EIECLNT300</RCVPRN>
---</EDI_DC40>
---<E1EDK01 SEGMENT="value2">
---</E1EDK01>
</IDOC>
</ORDERS05>
PITCLNT001 is the logical System name of PI. Do i need to configure "PITCLNT001" as logical system at SYSTEM_A (besides, thats not possile)?
regards,
MS
Edited by: Manuel Schlestein on Jan 28, 2009 10:39 AM
Edited by: Manuel Schlestein on Jan 28, 2009 10:40 AM

Hi
Create a logical system for SYSTEM_A in SLD (you can give some string) and create that same logical
system in IDOC side (SALE).
Thanks
Prasad Nemalikanti

HT5654 Trying to install the latest update for itunes...error received "service apple mobile device failed to start. verify thay you have sufficient priveleges to start system services"...? I have unistalled and tried to reinstall???

Trying to install the latest update for itunes...error received "service apple mobile device failed to start. verify thay you have sufficient priveleges to start system services"...? I have uninstalled and tried to reinstall???

Hello Kimberly0914,
It sounds like you have tried to launch iTunes after a recent update due to this error message, and you cannot install iTunes after uninstalling. I recommend the troubleshooting from the following article to help you named:
Issues installing iTunes or QuickTime for Windows
http://support.apple.com/kb/ht1926
Then download and install iTunes with this link:
http://www.apple.com/itunes/download/
Thank you for using Apple Support Communities.
Cheers,
Sterling

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

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
Stefan

Hi,
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 Lee

hi,
>>>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

ERROR" unable to convert the service as an ALE logical system"

Hello All,
In SOAP to IDOC scenario I tested the webservice with the client tool. Its hitting the integration engine but its throwing up an error" unable to convert the service as an ALE logical system". How can I maintain a logical system for a service as its outside our landscape. Can any one let me know how to proceed with this.
Looking forward to expert comments.
Thanks and regards,
Neelima

Hi,
Check this blog by Michal.
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Regards,
Sudheer.

Cannot start VM - IDE Emulator Failed to Power on with Error 'The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.'

HI all.
New install of 2008R2 on HP DL-380 G6. I have created (several) VM's none of which will start. If I remove the IDE Hard Disk and add a DVD of the OS ISO, it will boot and start the install (although with no HDD).
It seems like the IDE controller is working ok - it is what the DVD drive is using, but it cannot mount a VHD. The error indicates a driver is not working (although the DVD on IDE works fine) so something to do with VHD? I can attach the VHD
in disk management, so it does not seem corrupt - again I have tried with both dynamic and fixed VHDs.
Full error is:
'Test1' failed to start. (Virtual machine ID 4320D2D6-DF7E-40D2-BD0F-9562CBB9F052)
'Test1' Microsoft Emulated IDE Controller (Instance ID {83F8638B-8DCA-4152-9EDA-2CA8B33039B4}): Failed to Power on with Error 'The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.' (0x80070422).
(Virtual machine ID 4320D2D6-DF7E-40D2-BD0F-9562CBB9F052)
'Test1': Failed to open attachment 'C:\Users\Public\Documents\Hyper-V\Virtual hard disks\New Virtual Hard Disk.vhd'. Error: 'The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.' (0x80070422).
(Virtual machine ID 4320D2D6-DF7E-40D2-BD0F-9562CBB9F052)
Any Ideas?

Hi ,
Did you try to disable the services , if they are exsit :
HP Smart Array SAS/SATAEvent notification
HP Insight storage agents
Then restart your server .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

On DNG Converter 8.3.0.141 Fuji X-T1 files (RAF) cannot be convertes into DNG. What can I do?

On DNG Converter 8.3.0.141 Fuji X-T1 files (RAF) cannot be convertes into DNG. What can I do?

Use DNG Converter 8.4: http://www.adobe.com/downloads/updates

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.

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 Doeker

Hi,
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.

Error: Receiver Service Cannot be converted into an ALE logical system

Similar Messages

Maybe you are looking for