Skip to Content
author's profile photo Former Member
Former Member

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?

Add comment
10|10000 characters needed characters exceeded

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jul 01, 2004 at 08:02 AM

    Hi Jason

    I faced a similar problem when configuring exactly the same scenario when i used XI 2.0.

    But it worked when i gave an ALE name for the sender system (file adapter) also.

    Maybe you can try this.

    Regards

    Venu

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      I saw this problem at customer site recently. They posted to the destination business system but specified the wrong RFC destination in the IDOC adapter.

      Check your RFC destination is correct and posting to the right system. The customer found the missing IDOCs in another system.

  • author's profile photo Former Member
    Former Member
    Posted on Jul 07, 2004 at 12:38 PM

    Thanks Jason.

    I checked the RFC Destination again - I set it up to go to the R/3 system (receiver where the IDOC needs to be created).

    I set it up as a type 3 (R/3) connection. And in the technical settings, I specified the host name as the target host and also specified the IP address. In the Logon/Security tab, I specified my ID/Password. When I test the connection it is connecting OK.

    Do I need to do any more setup?

    Thanks again

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Srini,

      You need to check the following things in IDOC configuration:

      1) Using tr code IDX1 in XI check the Port is defined correctly for the backend R/3 System. The name of the Port usually have SAP<SID> where SID is the system number for the backend R/3 System. Make sure you used the right RFC destination in the Port definition.

      2)Make sure you defined RFC Destination as R/3 connection. Click on test connection as well as Remote logon to check the connection is OK.

      3) Use tr code IDX5 in XI, to track the inbound and outbound messages that were sent and received by IDoc Adapter.

      Hope this helps.

      Rgds,

      Sam Raju

  • author's profile photo Former Member
    Former Member
    Posted on Jul 08, 2004 at 01:27 PM

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

    - <!-- Response

    -->

    - 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

    smandala@yahoo.com

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Srini:

      It looks like your message is going through.

      On the Backend logon to your SAP System(IR1) and go to transaction WE05 or WE02 and check to see if there are any IDocs created in the System for those dates.

      Regards,

      Sam Raju

  • author's profile photo Former Member
    Former Member
    Posted on Jul 08, 2004 at 03:17 PM

    Jason: Thanks for the quick reply.

    Checked on IR1/300 with WE02/WE05 but no IDOCs. Also checked SM58 (tRFC log) and found nothing stuck there.

    Do we need to activate/trigger any queues on the R/3 side to pick up these IDOCs?

    Regards,

    Srini

    smandala@yahoo.com

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Srini:

      As a next step check the configuration of your Communication Channel for the IDOC Adapter in the Integration Directory.

      Make sure you have the same RFC Destination, PORT and SAP Relase specified in the Parameters Tab of the Communication Channel.

      Regards,

      Sam Raju