Skip to Content
avatar image
Former Member

AE_DETAILS_GET_ERROR

Hello everybody,

I have a scenario proxy->XI->RFC and I'm getting the next error:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- 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="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.xid.lfmxh02</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine</SAP:Stack>

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

</SAP:Error>

I have another interfaces IDOC->XI->IDOC working perfectly, any suggestions??, thanks in advance.

Regards,

Julio Cesar

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Nov 08, 2007 at 06:30 PM

    Hi Julio,

    Your Idoc- XI - Idoc scenario will work because you are using Idoc adapters, which are not deployed on adapter engine( Java engine). The error message says that the Integration engine is not able to connect to the Adapter engine and since you are RFC adapter is deployed on the adapter engine your scenario is failing.

    Try checking transaction SM58, you might be able to see the exact error msg.

    Cheer's

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 08, 2007 at 06:31 PM

    Hi Julio,

    As far as scenario IDOC->XI->IDOC is consider, Idoc adapter resides on abap stack..hence u r not facing any issue.

    Run following FM and and check the output...SAI_AE_DETAILS_GET with Adapter Engine "af.xid.lfmxh02"..if you debug probably u will get more details.

    Let us know how it goes..

    Hope this will help.

    Nilesh

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 08, 2007 at 06:50 PM

    Hi Guys, thanks for your fast answers, I don’t have any records in transaction SM58, now I’ve already debugged FM SAI_AE_DETAILS_GET, and I’m facing next problem, this FM has two parameters AE_NAME and BYPASSING_CACHE, now Function Module with BYPASSING_CACHE parameter = null don’t find any value the first call but after the first call it finds every value every time, when BYPASSING_CACHE is = ‘X’ sometimes it finds host value, sometimes it finds host and user values, sometimes it finds host, user and password values, sometimes finds anything and sometimes it dumps, I found in some thread that this FM is executed by default with BYPASSING_CAHCE = ‘X’, now the problems in this FM are because the FM LCRBEAN_GET_PROFILE_PARAMETER that is a CALL FUNCTION DESTINATION called by FM EXCHANGE_PROFILE_GET_PARAMETER, the TCP/IP RFC that is used by this call function is working perfectly, I don’t know exactly why but the execution of EXCHANGE_PROFILE_GET_PARAMETER is really intermittent, even in SLDCHECK sometimes works fine and sometimes doesn’t work, now this disruptions is what is causing the problems, system users and passwords have been checked, JAVA and ABAP instances are in the same box, but do you think it needs to go over the net to execute this function module?? Because hardware provider has already done a analysis to the server and network card and they didn’t find anything wrong with it, What other suggests do you have? Maybe some tuning parameters?, thanks for your help is really really appreciated cause this is turning into a serious problem, We’ve already posted an OSS Note to SAP but with priority medium cause is not a Productive system is a Development System, so we are waiting the call in the next two days but we can’t actually wait that long.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 13, 2007 at 07:16 PM

    Hi guys, problem solved the problem was a RFC Sender Adapter that was using the standard RFC connection LCRSAPRFC so this was causing the interruptions in connection for the adapter engine.

    Add comment
    10|10000 characters needed characters exceeded