Acknowledgement status

[Former Member]

Hello,

When we send a Asynchornous message , say from IDOC as sender and JMS as receiver via XI.

Do we really need to worry abt the Ack Status which is in sxmb_moni. Sometimes, it shows ack in error, sometimes in null, sometimes waiting for ack.

If it is a asynchronous, what is the purpose of it.

Moreover i see lot of messages in Message monitoring regaring acknowledgment.

[former_member556603]

Hi,

Go through this Document..

Click the link and Down load that Document i.e: How to handle Ack for IDOC's

How to handle Ack for IDOC's

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b...

Steps: if u want IDOC Ack You have to set up the ALEAUD.

Acknowledgment IDocs are always converted to XI acknowledgments.

This function enables you to send acknowledgment IDocs (ALEAUD) as XI request messages for a sender port and client.

Procedure

...

1. In the ABAP Editor (transaction SE38), under Program, enter IDX_ALEREQUEST and choose Execute.

2. Enter a sender port and a client and choose Execute.

3. Enter the partner number, partner type, and partner role for the receiver and choose Insert.

The entry is added to the table.

4. To delete an entry in the table, select the entry and choose Remove Entry.

Result

In the XI request message, the original sender of the acknowledgment IDoc is no longer known.

The XI request message created is a new message. Monitoring is not able to determine which was the original message.

File Acknowldgements

/people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments

Sending Acknowledgment IDocs as XI Request Messages

Use

Acknowledgment IDocs are always converted to XI acknowledgments.

This function enables you to send acknowledgment IDocs (ALEAUD) as XI request messages for a sender port and client.

.----

---

Processing Acknowledgment Messages

An acknowledgment message informs the sender of an asynchronous message about the result of the processing of the message within SAP Exchange Infrastructure. The reported result is referred to as an asynchronous acknowledgment.

Request Messages

Within the request message you must define whether an acknowledgment message is required, and if so, what kind of acknowledgment message. The acknowledgment message can refer to two events:

● The arrival of the request message at the final receiver

● The execution of the application in the receiver system

For this purpose, the request message contains an acknowledgment tag, which specifies the event for which an acknowledgment is expected. This tag must be specified by the sender (or a sender adapter that supports acknowledgment messages).

Message processing in SAP Exchange Infrastructure ensures that the acknowledgment message follows the same route from the receiver to the sender as the request message did from the sender to the receiver. For this purpose, the request message contains a hop list that logs the route of the request message. This information is provided by all Integration Engines and Integration Servers that are involved in the processing of the request message.

Acknowledgment Message

As soon as the request message processing encounters an event that requires an acknowledgment, a corresponding acknowledgment message is created and sent to the sender.

An acknowledgment message receives a new message ID, but also has a reference to the message ID of the request message as well as the value Response in the Directory tag of the message header. The request message hop list is copied to the acknowledgment message header, thus enabling backward routing of the acknowledgment message.

If a message is branched, a separate acknowledgment message is returned for each newly created request message. These acknowledgments enable the sender to recognize that its original message has been branched.

Acknowledgment messages are processed using backward pipelines. These pipelines are defined for each pipeline involved in the processing of a request message:

Pipelines and Corresponding Backward Pipelines:

Pipeline

Backward Pipeline

SENDER

SENDER_BACK

CENTRAL

CENTRAL_BACK

RECEIVER

RECEIVER_BACK

The backward pipelines have the following main tasks:

● Transport from the receiver system to the Integration Server

The receiver system sends an acknowledgment message back to the corresponding Integration Server (RECEIVER_BACK), as defined for the local Integration Engine.

If a receiver adapter is involved in message processing, it sends the acknowledgment message back to the Integration Server, provided that the respective adapter supports this procedure. Otherwise, a final acknowledgment message is returned with a comment that an acknowledgment is not possible.

● Transport from the Integration Server to the sender system

The Integration Server sends an acknowledgment message back to the sender (CENTRAL_BACK). It uses the name of the sender system for logical and technical backward routing.

If the sender is addressed using an ABAP proxy, you must define a corresponding receiver agreement for this sender.

If a sender adapter is involved in processing the message, the Integration Server sends an acknowledgment message to the sender adapter, which is then responsible for returning the acknowledgment to the sender.

To do this, some adapter types require a corresponding receiver agreement for the sender.

-

---

Hope This Information is useful to you,

Thanks,

Satya Kumar.

[former_member537867]

Hi Anandha Krishnan ,

Acknowledgments enable you to confirm that an asynchronous message has been received. You must explicitly request acknowledgments in the application program and can specify what kind of confirmation you want to receive. (or)

Acknowledgment is the confirmation of delivery of the message to receiver systems.

If the Interface is synchronous then you could have the response from Receveir system as an acknowledgment.

· Positive or negative acknowledgments

· System acknowledgments used by the runtime environment to confirm that an asynchronous message has reached the receiver.

· Application acknowledgments used to confirm that the asynchronous message has been successfully processed at the receiver.

SAP XI Acknowledgments are the confirmation of delivery of message to the receiver systems.

For Synchronous communication you could have the response from Receiver systems such as RFC, WebService (SOAP, HTTP), Proxy etc.

For Asynchronous communciation you might have to create the dummy response either as an alert notification or using BPM or may be with various Module processors.

You could mionitor the acknowledgment status in SXMB_MONI.

In case of Async message flow either you need to generate the acknolwledgment. It depends upon the communication adapers.

Either you could use Alert notification or BPM or various module processors.

For IDOC, you could have ALEAUD as an acknowledgment IDOC.

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...

have a look at the Alert Framework, which can be configured to send mails to specific persons if an interface processing fails.

http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm

There are two types of JDBC acknowledgements Transport level and application level.

IF the JDBC call is asynchronous you can set up for transport level acknowlegement in the send step in ur BPM.

if the JDBC call is synchronous then JDBC adaptor will generate a response message with a tag update count, which gives you the number of rows that were updated.

refer to the following link, which details about reciever jdbc

http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

just check out these links

http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm

The following link has entire configuration of Receiver XI Adapter (including acknowledgements)

http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm

Try and see the follwoing steps

1) In the Integration Server, call transaction SE38

2) Run program IDX_ALEREQUEST to process IDocs with message type ALEAUD as XI request

message.

3) Now Enter Sender Port, Sender Client,Partner Number, Partner Type, and Partner Rol

4) In Integration Directory, configure the routing of interface

5) Call transaction SXMB_MONI to display the XI message.

Also,

Further in IDX5 as well you will find entry for IDoc ALEAUD.ALEAUD01

Regards,

Vinod.

[Former Member]

Hi,

Acknowledgments

Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender.( Ex : Idoc----JMS). Here by default Idoc has the inbuilt feature of requesting the Ack.

Acknowledgments are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments.

Sender adapters of the Adapter Engine do not request any acknowledgments.

If u want to handl the the Idoc Ack

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df...

If you want to suppress the Ack & u dont want to see that Error ack in error means

please check the link

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

goto SE38 specify Report as XNOALE & Execute

Specify the value for PORT,CLIENT AND MESSAGETYPE.

Save the entry

hence

You can Switch of ALEAUD IDOCs

You wont receive the ack error on SXMB_MONI.

Regards

Seshagiri