Monitoring the Status of Inbound IDocs Using ALE Audit
Use
Using ALE audit you can monitor the processing status of dispatched IDocs in the receiving system (inbound) from the sending SAP system. The receiving SAP system periodically sends confirmation messages to the sending system. These confirmations are logged in IDoc status records and in separate audit tables in the sending system.
Connections are also created between IDocs in the sending system and IDocs in the receiving system.
A report program on the sending system analyzes the audit database.
Prerequisite
Confirmations can only be dispatched, if you have defined a message flow for message type ALEAUD in the distribution model.
Choose the following activity in ALE Customizing:
Transaction SALE ® Set-Up System Monitoring ® Set-Up IDoc Confirmation in Receiver System (ALE Audit) ®Configure Distribution Model for ALE Audit (BD64).
To improve performance, confirmations are dispatched periodically for packets of IDocs rather than for individual IDocs. Confirmations have a special ALEAUD01 IDoc with message type ALEAUD.
The filter object message type (MESTYP) provides a more detailed specification. You can use this filter object type to set the message types for generating audit confirmations. As a rule, you do not have to send confirmations for all message types. For example, it is quite likely that confirmations will not be necessary for master data. If the MESTYP filter object type is not used all IDocs are confirmed by ALEAUD in the receiver system.
Activities
In the receiver system you have to make the settings for periodic confirmations. You can also send confirmations directly.
When confirmations are sent (program RBDSTATE), IDocs of message type ALEAUD are generated containing information about the processing state of inbound IDocs. An audit IDoc contains confirmations for up to 500 IDocs. If there are more IDocs to be confirmed, several audit IDocs are generated. A list of the generated IDocs is displayed. If an IDoc cannot be generated or an error occurs, a message is displayed.
IDocs whose statuses have recently changed are selected. Because almost every IDoc activity (e.g. creation, successful posting/ unsuccessful posting in an application) alters the status of the IDoc, it is precisely these IDocs which have in some way or other been processed.
Setting Periodic Confirmations
So that audit data can be confirmed periodically back to the sending system, you have to use the program RBDSTATE to specify a variant and schedule a background job in the receiving system.
Choose the following activity in ALE Customizing:
Set-Up System Monitoring ® Set-Up IDoc Confirmation in Recipient System (ALE Audit) ® Confirm Audit Data ® Specify Variant.
Schedule this variant as a background job:
Choose SAP menu ® Tools ® IDoc Interface/ALE ® Administration ® Services ® Periodic Jobs ® Inbound ® Set-Up IDoc Confirmation in Recipient System.
You can schedule confirmations at hourly or daily intervals.
To display an aggregated overview of all periodic confirmations you can Analyze the Audit Database in the sending system.
Sending Confirmations Directly
To send confirmations directly to the sending system, in the status monitor choose Goto ® ALE Audit ® Send confirmations.
The selection parameters allow you to regulate in which systems and for which message types, confirmations should be generated.
You have to enter a start and end date for the change period.
-
-
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.
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.
-
-
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.
An acknowledgment informs the sender about the status of message processing.
It is applicable to both the scenarios.
like File to IDOC and IDOC to File.Its not depends on your scenarios.Its depends on your applications.
acknowledgments have to be requested explicitly by the sender. However, this does not apply to IDocs.You have to setup ALEAUDIT for IDOC acknoldgements
Suppose (IDOC to File ....in your perspective)
IDocs only return acknowledgments if the receiver is configured for using ALE audit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.