Ansicht
Dokumentation

RBDSTATE - Send Audit Confirmations

PERFORM Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Description

This report sends confirmations for the ALE Audit. Selection parameters allow you to determine the systems to which the confirmations are to be sent and the application message types for which they are to be sent.

The report creates IDocs with the ALEAUD message type. They contain information about the processing status of inbound IDocs on your own system. Thus the report selects changes to the current processing status of IDocs. These are really changes to the status of an IDOC. In this sense, the creation of an IDoc represents a change in its status, as does a successful posting in the application after the first attempt resulted in an error.

The entries for the ALEAUD message type and the associated filter object MESTYP in the distribution model determine the systems to which audit messages are sent.

If there are no suitable entries in the distribution model for your selection parameters, no message is sent.

You can use the last selection parameter to determine the period of time for the IDoc selection. This parameter refers to the data of the last change in status and not to the creation date of the IDoc. If the report is started online, then this parameter is mandatory; in batch operation it is optional.

Notes on Periodic Batch Operation.

There are two possible operating modes when this report runs periodically in the background:

• Dispatch of confirmations at either daily or longer intervals

• Dispatch of confirmations at shorter intervals

Dispatch of confirmations at either daily or longer intervals

This operating mode is preferable if the confirmations are not time- critical. You can use this to send confirmations for IDOCs from the previous day or for changes that occurred even longer ago.

When maintaining the variant for batch operation, you should choose a selection variable, a date variable in fact, for the selection parameter for the change date. This allows you to be remain flexible in setting the days, e.g. 'yesterday', for which IDOC status changes should be reported.

When scheduling the batch job note that if, for example, you want to send the changes from the previous day, then you should not schedule the job to run straight away at midnight, but several minutes later. Otherwise there may be IDOCs from the previous day that had not been posted by 00:00, and these will not get confirmed.

Dispatch of confirmations at shorter intervals

This operating mode is intended for time-critical jobs, for example, if confirmation is required every hour.

Do not specify a selection parameter for the change date. The report can itself find out the time when it last ran, or, if it is running for the first time, the time when it was scheduled. This time (date and time) minus 5 minutes forms the lower selection boundary for all IDOC changes. The starting time of the batch job minus 4 minutes gives the upper selection boundary for the IDOC changes.

In summary, all IDocs whose status has changed in the specified time period and that satisfy all the other selection criteria are selected.

Requirements

The settings for the ALE Audit must already have been made. You can find more information on this in the IMG section ALE IMG under System Monitoring.

Output

A list is generated of all the IDocs with the ALEAUD message type that were created. If no IDocC was created or if an error occurred, then a message is issued.

Example

ROGBILLS - Synchronize billing plans   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 3825 Date: 20240601 Time: 115325     sap01-206 ( 81 ms )