ALE Logical System Error

Hi Experts
In a simple File to Idoc scenario i used a BPM and did the mapping outside the BPM. The BPM just receives the message of type IDOC and sends it to the R/3 system. In Message monitoring the transformation of message from file server to BPM has been sucessfull but the tranformation of message from BPM to R/3 reported the following error.
"Unable to convert the sender service FileIdoc_BPM to an ALE logical system"
Suggest me the solution for this problem
Regards
Saravanan

Hi,
Go to the Sender Business System / Service , Dobule Click on it, In the menu at the top Business <b>Service --> Adapter Specific Identifiers</b> --> Add Some value to the logical system name , save and activate the Business System / Service and then trigger the interface.
Cheers,
Jag

Similar Messages

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

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.

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

ALE logical systems for business service or process

Hi,
I am trying to send an IDOC into my R/3 system. It is the same IDOC type that I have sucessfully sent out to parties. All the config is in place for communicating with the system, because I have sent others IDOCs in the past. However, they always were sent from another R/3 business system. They processed sucessfully.
I am now trying to sending IDOC's from a BPM,as well as, from a business service. They are under the "With Party" section of the directory. These obviously do not have logical systems, so when I try to send the IDOC I get
"Unable to convert the sender service Purchase_Orders to an ALE logical system", where purchase_Orders being the name of the business serice.
How can I handle this problem?
Should I hard code values somewhere?
Which ones?
I have read the other posts for the error above, but my situation seems to be different.
Help!
Chris

Hi,
To solve your problem, here my solution:
1/ In your Business Process of your ID (configurator), go to menu "Service > Adapter-specific identifier" and in the part "IDoc Adapter", write your Logical System.
2/ Create this Logical System on your target system (R/3).
WARNING: XI allows you to used a Logical System for only one service (Business Process). Thus, if you are several interfaces, you must used different Logical Systems.
Mickael.

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.

Logical System Error

Hi AlL
I am working on the JDBC TO IDOC Scenario and when testing I get error:
Unable to convert the sender service ABC_Service to an ALE logical system
I check on the SLD under the Business System and what I find is that there is no LOGICAL SYSTEM NAME.
How to make the PI System to keep up the LS, on the TCode BD54 I created it
Role:
Pipeline URL:
Group:
Technical System: PI1 on saptrain1 Change...
Client: 001 of PI1
Logical System Name: #######
Thanks
Yonela

Hi Guys
On my JDBC TO IDOC Scenario when testing on the MONI I get the below 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>XIServer</SAP:Category>
<SAP:Code area="XICACHE">BUSINESS_SYSTEM</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>NO INTEGRATION SERVER</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
but on the SLD my Business System looks like this:
Role: Integration Server
Pipeline URL:   http://saptrain1:8000/sap/xi/engine?type=entry
Group:    No group assigned
Technical System: PI1 on saptrain1 Change...
Client: 001 of PI1
Logical System Name: LSJDBC
I have done
with this user : PIDIRUSER i have done the full cache
http://saptrain1:8000/CPACache/refresh?mode=full
CPA cache refresh (mode=full) successfully executed in 30937 milliseconds.
but when running
http://saptrain1:8000/sap/xi/engine?type=entry on the browser i get :
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
- <SOAP:Body>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Empty HTTP request received</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
- <detail>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope
What I am I missing out
Thanks,
Yonela

ALE logical system - File -- XI -- R/3 scenario

Hi
I have the following scenario which I'm trying to run.
File --> XI --> R/3 scenario.
I have created a sender agreement XID|ASN_out|NBD where XID is my XI 3.0 system and NBD is my R/3 system. I have also created an interface determination and receiver determination.
The following error is in transaction SXMB_MONI in my XID system:
"Unable to convert the sender service to an ALE logical system"
Both XID and NBD are business systems defined in SLD and they have both a logical system assigned.
Why do I get this error and how can I fix it?
Best regards
Göran
Message was edited by: Göran Westin
Message was edited by: Göran Westin

Ok. I fixed the problem.
In the Integration Builder - Configuration > Select business system of choice > Menu > Service > Adapter specific identifiers > IDOC Adapter > Logical system - got a value after reading/refreshing it from the SLD.

Unable to convert the sender service to an ALE logical system

Hello,
file adapter > XI 3.0 > Idoc adapter > r/3 system
In sxmb_moni I receive "Unable to convert the sender service to an ALE logical system".
In we05 in r/3 system no Idocs are arrving. I have no problem with idoc > XI > idoc scenario to this same r/3 system (using same sld business system)
I read other topics on this error but it seems they all talk about an IDOC outbound interface.
What should I check?
Thanks
Boaz

I do have the same problem as Boaz Paz
When I try :
file adapter > XI 3.0 > Idoc adapter > r/3 system
> This is a B2B scenario where "AVTItalia" is the external party trying to send via its "AwayOrders" business service (a file pickup) an idoc to business system "UPG" (non party service)
I get an error while XI tries to call its IDoc 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>AwayOrders</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service AwayOrders to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
With the following trace logs :
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = AVTItalie</Trace>
<Trace level="1" type="T">Sender party normalized = AVTItalie</Trace>
I ve tried to (cf. /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc ):
1. add a logical system name "ACYAVTFBC1" in "Adapter specifier Id" of "AwayOrders"
In the runtime cache > services an entry appears for " ... Logical System | AVTItalia | ACYAVTFBC1...".
2. declare "AVTItalia" as a business partner in SLD with the logical system name
Plz help!

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]

Unable to convert the sender service BS_PARTNER to an ALE logical system..!

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" ?>
- 
- <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.

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

ALE Logical System Error

Similar Messages

Maybe you are looking for