Unable to convert the sender service to an ALE logical system

[Former Member]

I am sending DEBMAS03 type IDOC from SAP 4.6C to AS400 using XI. We are using FTP as communication channel.

Data is passed successfully to the target. But in 'Runtime Workbench' there is a system error. It looks like we have to setup a receiver service for the acknowledgement. I cannot find where it is setup to get an acknowledgement from AS400.

Please let me know if anyone has seen this error and how can we fix this error.

Thanks for your help.

RR

<?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 the sender service to an ALE logical system</SAP:Stack>

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

</SAP:Error>

[p_vanos · Accepted solution]

Hi Ramesh,

I solved the issue about acknowledgement some days ago, please look at my posted message with use of table IDXNOALE. This table contains port/client/message type and should be filled with the correct values when you DO NOT want the ALEAUD idoc's.

When you are on stacklevel 9 or lower please use the ABAP I enclosed in the message mentioned above! If you are on level 10 and higher there is a program for it delivered by SAP.

Which problems do you stil encounter now?

Cheers,

Paul

[Former Member · Accepted solution]

Paul,

Thanks for the solution. It worked. Once we added the port and the message to IDXNOALE, system was able to ignore the acknowledgements.

We are at service pack 9 and were able to create records in IDXNOALE by using SE16.

Thanks for your help.

Ramesh

[Former Member]

I also got the same problem with an outbound J2SE file adapter.

The only why I was able to solve this was to remove my system from the technical and business landscapes and re-create it with a <b>different</b> name. For some reason this setup becomes corrupt and even if you delete the entries from the SLD, some traces still remain. The problem will persist if you use the same name.

When creating the new entries, make sure to logical system name in the business landscape.

[Former Member]

Paul and Johan,

Thanks for your prompt reply. We tried both the options as suggested by you. We still have the same problem.

We checked IdX1 and IDX2 transactions at the Integration server as well? Port setting was wrong. We corrected the error and re-created the technical system and business system.

For now, we do not need to get an acknowledgement from the receiving system. Is there a place where we can specify not to expect an acknowledgement.

Again, thanks for your help.

Ramesh

[p_vanos]

Also, did you execute transaction IDX1 and IDX2 on the integration server?

[p_vanos]

Hi Ramesh,

Make sure you have assigned a logical system to the business system of your SAP system. Normally the logical system is assigned to your SAP-client, where you can look it up. If you have forgotten to assign the logical system of a client during creation of the technical system you have to remove the technical system and create it again!

After this goto the directory:

Goto service without Party and select your business system which is your sap system. Make sure you have cleared the SLD datacache (environment-->clear SLD data cache).

When you change the service to change mode, goto:

Service-->Adapter specific identifiers.

You will enter a screen with below 3 buttons. The middle one is takeover from SLD. When pressing this button the logical system shoul appear in the screen, together with SAP-system id and client.

Have fun,

Paul