Acknowledgement not possible

[Former Member]

HI,

i´m using a R/3 (IDOC) -> XI -> Party (JMS Adapter) scenario.

We have configured a receiver IDoc CC beginning with "Ack" and made the settings for the SenderPort and Interface in IDXNOALE.

1.) If the message fails in XI due to an error the ALEAUD message will be send to the sender R/3 system but the reliable Message is not shown (look at 4. in the "how to handle Ack for IDoc guide"

2.) If the message is without any errors and transfered to the Party by JMS, the acknowledgement Icon shows the following error and the reliable massage is missing, too.

"No Acknowledgement possible"

any ideas ?

I think it´s something with the configuration an the "sender payload or something else".

3.) is it possible to map the ALEAUD (from XI - to sender) interface ?

Thanks.

Gordon

[udo_martens]

Hi Gordon,

>1.) If the message fails in XI due to an error the ALEAUD message will be send to the sender R/3 system but the reliable Message is not shown

This is misunderstandable: Which message failed at PI? If the IDoc message failed and did not reach the target, how can the target send an acknowledgment? Please explain your scenario and the errors more detailed.

>2.) If the message is without any errors and transfered to the Party by JMS, the acknowledgement Icon shows the following error and the reliable massage is missing, too.

"No Acknowledgement possible"

That is clear: You stopped the requesting of the acknowledgment with report IDX_NOALE (why?). If you nevertheless want to send a ALEAUD back to R/3 system, you need to send it as "request" message, not as acknowledgment. This can be configured with report IDX_ALEREQUEST.

Regards,

Udo

[Former Member]

Hi Udo,

i try to explain more detailed.

Sender = R/3

Interface = IDoc

Receiver = JMS Party

I need 2 kind of acknowledgements.

1) PI/XI Ack

2) Party Ack

1. If the message got an mapping error in XI/PI we need to send "any kind of ack" back to the R/3 to inform the Team that something happens during the mapping.

If everything is ok and the message was sent to the JMS- I got an error like "ACK is not possible for party". Anyway .. i don´t need a ack if mapping in XI/PI is successful.

How can I get rid of this error ack information ?

2.) If the message reached the Party (after adapter transport) we need a second ack that the party has reached.

What kind of ACK Type do i have to use. IDXNOALE or REQUEST_ALE ?

In general i was wondering why the second message (reliable message) is missing in both cases.

3.) is it possible to map the ALEAUD message ?

Can i use a IF mapping ?

The mapping error message "ERROR in Messagemapping transform at .... in interface ..." is to long for the STATUS Text in the ALEAUD IDoc. The sender IDoc is updated without STAPA1-4 information.

Thx,

Gordon

[udo_martens]

Hi Gordon,

>1. If the message got an mapping error in XI/PI we need to send "any kind of ack" back to the R/3 to inform the Team that something happens during the mapping.

This is not standard, you request the acknowledgment from the receiver, not from the middleware

>If everything is ok and the message was sent to the JMS- I got an error like "ACK is not possible for party". Anyway .. i don´t need a ack if mapping in XI/PI is successful. How can I get rid of this error ack information ?

Stop sending the acknowledgment at JMS side. If only the error at PI monitoring disturbs you then send the ackn as request by configuring the PI report IDX_ALEREQUEST.

>2.) If the message reached the Party (after adapter transport) we need a second ack that the party has reached.

What kind of ACK Type do i have to use. IDXNOALE or REQUEST_ALE ?

What??? This are PI reports...

>3.) is it possible to map the ALEAUD message ? Can i use a IF mapping ?

If your requirement is to receive from target AND PI acknowledgments i recomment following design:

Container: IDoc, JMS msg, ALEAUD

Delete the interfaces from the PI reports IDX_NOALE and IDX_ALEREQUEST

Create a BP receiving the IDoc

Block begins

Map to receiver and define an exception for the step

Map in the exception branch to ALEAUD error case: Put a fitting constant to error text

Create a send step requesting an acknowledgment and define an exception for the step

Map in the the exception ALEAUD error case

Map behind the send step to ALEAUD success case

Block ends

Send ALEAUD

Regards,

Udo