ALEAUD back to ccBPM

[Former Member]

Hello,

I have a scenario like this

WebService -> XI -> ccBPM (Sync-Async Bridge) -> async IDOC to R/3 -> ALEAUD -> XI -> close Bridge -> WebService Response

R/3 sends ALEAUD back to the ccBPM.

I'm sending an IDOC from a ccBPM to R/3 and in R/3 I'm sending the status of the posting via ALEAUD back to XI.

XI takes the the ALEAUD IDOC which is sent via the SM59 to XI and treats it like an acknowlegement for the send step even so my BPM send step has no acknowledgment requested.

My question is: Can I make XI not treat the ALEAUD for the BPM, e.g. configure an outbound async ALEAUD interface to XI? Or if XI treats the acknowledgement how can I get the ALEAUD IDOC data used in my ccBPM, e.g I want to map the stautus back to my web service call.

Cheers

Stefan

[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

[cdumont69]

Hello,

If you don't need the ALEAUD IDOCs to be got back, you can add the PORT,CLIENT and MESSAGETYPE to the table IDXNOALE.Use transaction SE16 -> specify the table name "IDXNOALE" and then choose create new entries.Specify the values for PORT, CLIENT and MESTYPE fields, save the entry.This procedure helps switch off ALEAUD IDOCs from being sent back to the sender SAP system.

Is it that you want ?

Regards,

Chris

[Former Member]

Hi Chris,

this is not my problem. I want the ALEAUD back, e.g. I produce it in R/3 to be sent to XI. The send step on the ccBPM has set "no acknowledgement" but XI still sees the ALEAUD and thinks it is for the send step instead of routing it to a real receive step I have in my ccBPM.

I have now changed the message type of ALEAUD to ZALEAUD and now XI leaves it alone. This solves my problem but more custom ABAP work is necessary to achieve this.

Thanks

Stefan