ALEAUD error during Technical routing of reponse

Former Member · ‎08-30-2005

Hi,

I have tried to use the documentation "How to... Handle Acknowledgment for IDoc" for one of my scenario.

XI picks up a file on a ftp server, maps it to an IDoc (ORDERS03 by the way) and sends it to a R3 server. Then the R3 server creates hourly acknowledgments (ALEAUD), sends them back to XI. The acknowledgments should be forwarded by XI to someone by a mail communication channel.

The problem is when XI receives the acknowledgments, it updates the status of corresponding IDocs locally stored on XI but it does not send the email as excepted: the pipeline stops during the "Technical routing of response" (see Trace below) .

<!-- Technical Routing of Response

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="T">COMMIT is expected by application !</Trace>

- <!-- ************************************

-->

- <!-- ************************************

-->

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = RMS</Trace>

<Trace level="1" type="T">client = 111</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XIAPPLUSER</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = 9166935A72D4A04D893558342D79C6A5</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL_BACK</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline = CENTRAL_BACK</Trace>

<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL_BACK</Trace>

<Trace level="1" type="T">Queue name : XBTB0___0000</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTB0___0000</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="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL_BACK</Trace>

<Trace level="1" type="T">system-ID = RMS</Trace>

<Trace level="1" type="T">client = 111</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XIAPPLUSER</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL_BACK</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL_BACK</Trace>

- <Trace level="1" type="B" name="PLSRV_UPDATE_ACK_STATUS">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

</Trace>

- <Trace level="1" type="B" name="PLSRV_INSERT_BRANCH_ACKS">

- <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="CL_XMS_INSERT_BRANCH_ACKS-ENTER_PLSRV">

<Trace level="1" type="T">Switching RefToMsgId due to branch:</Trace>

<Trace level="1" type="T">old RefToMsgId was: D8C03190189C11DA9D560013216B8075</Trace>

<Trace level="1" type="T">new RefToMsgId is: D8C03190189C11DA9D560013216B8075</Trace>

</Trace>

- <Trace level="1" type="B" name="PLSRV_TECHNICAL_ROUTING_BACK">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <!-- ************************************

-->

</Trace>

<Trace level="1" type="T">Runtime exception return from pipeline processing !</Trace>

<Trace level="1" type="T">Persist Message in Stopped State</Trace>

- <!-- ************************************

-->

</SAP:Trace>

I have tried to configured a scenario for processing incoming ALEAUD.ALEAUD01 in namespace urn:sap-com:document:sap:idoc:messages but it doesn't seem to be used.

Last point, "ALEAUD.ALEAUD01 with namespace urn:sap-com:document:sap:idoc:messages" is not the name of incoming interface:

<SAP:Sender>

<SAP:Service>UPG</SAP:Service>

<SAP:Interface namespace="http://sap.com/xi/XI/Message/30">Acknowledgment</SAP:Interface>

</SAP:Sender>

<SAP:Receiver>

<SAP:Party agency="" scheme="" />

<SAP:Service>WebServer</SAP:Service>

<SAP:Interface namespace="http://sap.com/xi/XI/Message/30">Acknowledgment</SAP:Interface>

</SAP:Receiver>

<SAP:Interface namespace="http://sap.com/xi/XI/Message/30">Acknowledgment</SAP:Interface>

Maybe that could be the reason...

Regards,

Yann Le Blevec

Former Member · ‎07-22-2011

Hi experts,

I have the same problem as Adixen.

Does anyone know how to solve this?

Thanks in advance,

LUIS

Former Member · ‎02-13-2006

Hi Yann,

how did you solve this issue?

Thanks

ALEAUD error during Technical routing of reponse

Accepted Solutions (0)

Answers (2)

Answers (2)

Re: HTTP Receiver adapter with Dynamic value in UR...

How to create a rolling forecast in SAC? I have an...

In SAP Hana Cloud, do packages exist as database o...

Re: Mass Update a Zfield in Std Table with Split &...

Re: Change BW Query Initial Variable Input at runt...