ALEAUD

[Former Member]

Hi,

I have scenario BPM-> R/3 ->ALEAUD -> BPM.

I am posting Idoc to R/3 and sending ALEAUD from R/3 to BPM back for acknowledgemnt.I would like to use bpm to wait for the response from R3 (aleaud) and to create and process the acknowledegement for the sender , but I´m not really sure if this works because, the correlation for the sending msg and the aleaud could only be the idoc-no.

Does anyone have any information regarding this and if this is possible using this approach?

Regards,

Bhavana

[Former Member · Accepted solution]

Hi ;

For making the process wait you will have to use an application level ack in the send step of the BPM for IDoc.

Mudit

[Former Member]

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

[bhavesh_kantilal]

The Aleduit will contain the Idoc number against the Docnum field.

This is possible, but how will you send the Idoc Ack back to XI?

1. Either send the Aleaudit using te RBDSATE report.

2,. Or write a Exit in the Idoc processing code.

Regards

Bhavesh

[Former Member]

Hi,

Thats fine. however, problem is not in sending ALEAUD to Xi but in receiving the ALEAUD in XI.

When we define corelation , we compare Idoc Number in Creams (IDOC) and ALEAUD.But while sending There is no value in DOCNUM field of IDOC because IDOC number gets generated when IDOC is posted in R/3.

So, Corelation always returns false when it tries to compare a balnk value with a non-blank value in DOC Field of ALEAUD.

Regards,

Bhavana

[Former Member]

Bhavana -- can this below trick work for you ?

While sending CREMAS to r/3, try using any unused field in any segment with some unique timestamp (like timestamp from IDoc control record) and make sure you send the same timestamp back in ALEAUD in some unused segment field. These fields you can defnitely use for correlation.....

hope this helps....