cancel
Showing results for 
Search instead for 
Did you mean: 

ALEAUD not coming to SAP from XI & u0093Acknowledgment not possible" in idx5

Former Member
0 Kudos

Hi All,

I am trying to configure ALEAUD in SAP->XI->JDBC scenario for Idoc acknowledgment.

I did following config in SAP

WE21 create port for XI

WE20 create Partner type XIDLOGSYS1 ‘LS’ , Inbound parameter ALEAUD.

In XI I delete all entries from IDXNOALE table.

But still I am not receiving any ALEAUD in D02 when, any IDOC posted from SAP to XI.

In SXMB_MONI I am able to see Ack status “Acknowledgment not possible”

Please guide how to get ALE AUD in SAP from XI.

Regards

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Before I ask my questions, please note I do have a copy of the "How To Handle Acknowledgements for IDoc" How To Guide. I just need some clarification from the group.

Here are my questions:

1. XI will not send a positve acknowledgement/status to let the sender system know it made it to XI ok, correct?

2. The only status that XI itself will initiate will be if there is a techncial issue with XI, correct? (Granted the Receiver system could send a positive or negative status back to Sender System) I just want to make sure that XI will not send a status back to Sender System that equates to "Triggering EDI subsystem OK" (or something like that)

3. How does the status of an idoc get set to 12 from 03? Does that mean that I always have the program RBDMOIND configured when I am interfacing to XI in order to force the status from 03 to 12?

4. As a norm, are those who are using XI seeing a 12 status on the Sender System IDoc Status?

5. If a techical issue error occurs in XI, what specific error status will be sent back to the Sender System?(if at all) I am looking for an example status number of what to expect.

6. If we are doing SAP R/3 to a partners XI system directly and that partner does not have RBDSTATE configured on their SAP R/3 environment and there is nothing else on their XI system for ALEAUD processing, I am out of luck in determining if the IDoc actually made it to their XI system, correct?

7. The Configure Scenario 2 in the document How To Handle Acknowledgements for IDoc" How To Guide should allow us to determine "did the Idoc get to that Server" correct?

Thanks for any feedback on this,

Ian

Former Member
0 Kudos

Hi Rohan,

Acknowledgment is available in SP16. What you should do is:

XI

1) create receiver determination

R3

2)create partner profile in WE20

here is blog how to do that:

/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc

Regards,

Wojciech

Former Member
0 Kudos

Hi Wojciech,

Its ok I already used this feature in SP12 in other project,

& I configured both configurations XI/ R/3 configs but still not getting

any ALEAUD message in we05-R/3 back for XI in SP16.

Also why help.sap under new feature of Adapter SP18, why following lines are written

“On the Integration Server, you can use the IDoc Adapter: Acknowledgments

function to define the acknowledgments you want to request for a sender port and client.”

IN XI SP16 i m still getting “Acknowledgment not possible & Error in back routing

Error in communication channel"

in idx5.

Any suggestions how to correct it and get

ALEAUD in R/3

Regards

Former Member
0 Kudos

Hello Rohan,

Do you have any news about this issue?

Former Member
0 Kudos

Hi Rohan,

I meet this error too, did you solve the problem? Plz give me some help

Thanks

Former Member
0 Kudos

HI

Check this document on handling IDOC acknowledgements. This might give you some pointers.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50...

Satish

Former Member
0 Kudos

More Detail Error in SXMB_MONI->Technical Routing of Response->Error

- <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="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>

<SAP:P1>,BECHTEL_IMSD_DEV</SAP:P1>

<SAP:P2>,D02,,</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error in back routing Error in communication channel</SAP:Stack>

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

</SAP:Error>

Former Member
0 Kudos

Find the solution.

This Feature is Available under SP 18 and we are on SP16

http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm