Skip to end of metadata
Go to start of metadata

ALE Audit

ALE AUDIT is the technique of using IDocs communication. The purpose of ALE Audit is to check the cross-system IDoc flow and posting in the partner system.

Features:

1. ALE Audit provides an automatic and seamless tracing facility for individual documents in distributed applications.
2. Documents that have been sent from one application to another can also be traced from start to finish.    
3. Another feature of ALE Audit is that the processing status of a document can be queried from a central point.          

ALE Audit is a statistics database for IDocs that is maintained on the sending system.

ALE Audit enables the sender system to monitor the processing status of dispatched IDocs in the receiver system. The receiver system periodically sends confirmations back to the sender system, which are logged in IDoc status records and in individual audit tables.

Status records generated from the confirmations contain the following values:
 •       39 - IDocs in receiver system (ALE Service) and still being processed.
 •       40 - Application document processing not completed successfully in receiver system.
 •       41 - Application document processed in the receiver system. Processing completed independently of the processing status in the receiver system. The message in the status record is the same as the corresponding message in the IDoc status record in the receiver system.

Dispatch of Audit confirmations

For performance reasons confirmations are dispatched periodically for a packet of IDocs rather than for each one. Confirmations have a special IDoc ALEAUD01 with message type ALEAUD.
Confirmations can only be dispatched if a message flow for the message type ALEAUD has been maintained in the distribution model (BD64).

ALE Audit IDocs

The Audit IDoc ALEAUD01 contains three segments: E1ADHDR, ESTATE and E1PRTOB.

One IDoc contains a maximum of 500 IDocs confirmations. The segments comprise the following:
•       Segment E1ADHDR
 E1ADHDR contains message type, variants and function for the ensuing confirmations. Each confirmation comprises exactly one segment E1STATE and one segment E1PRTOB.
•       Segment E1STATE
 E1STATE contains the IDoc number of the sender system (Field DOCNUM), the current status in the receiver system and the message fields from the current status record.
•       Segment E1PRTOB
 E1PRTOB contains the receiver's IDoc number and, if existing, the application object generated in inbound processing.

Scenario:

Here we are taking the scenario for message type DEBMAS (Customer Master).

Here we need to transfer the customer master data from the outbound system to inbound system and audit confirmations for the DEBMAS.

ALE Audit requirement for DEBMAS

Procedure

These below steps are for the ALE Audit confirmations for the message type DEBMAS.

Sender logical system is ECICLNT800 and

Receiver logical system is ECICLNT080.

Note: for the ALEAUD configuration, we must have the regular ALE configurations...i.e.

1.     Define logical systems - BD54,
2.     Assigning logical systems to clients - SCC4
3.     Create RFC destination - SM59
4.     Port definition - WE21
5.     Create Partner profiles - WE20

All the above configuration has to be done both sides, i.e. the sender system and the receiver system.
After the above steps, we need to follow the below steps.

6.     Creation of Distribution Model - Transaction BD64
a.     Create Distribution model (in the outbound system) for message type DEBMAS
                      I.        Generate Partner profiles: Environment ->Generate Partner Profiles
                    II.        Distribute the Distribution model: EDIT->Model view Distribute

b.    Create Distribution model (in the inbound system) for message type ALEAUD

                      I.        Generate Partner profiles: Environment ->Generate Partner Profiles
                    II.        Distribute the Distribution model: EDIT->Model view Distribute

For Audit confirmations, we need to maintain the message type ALEAUD in the distribution model view of inbound system. So for that we need to create the model view in the inbound system.
Example: Here the Screen shot from T.Code: BD64, Distribution model ALEAUD1 created in the inbound system. For audit confirmation we need to add a message type 'ALEAUD'.

ALEAUD working Process:
Once all the above configurations are complete, we need to send an IDoc of DEBMAS type.

We can use Standalone application from SAP for this...

Go to T.Code: BD12 transaction and enter a valid customer number and enter the message type (DEBMAS) and logical system (ECICLNT080).
 

Dispatch of Audit confirmations:

The RBDSTATE report we need to execute at the receiver system (ECICLNT 080) that means in the inbound system.
The RBDSTATE report dispatches the audit confirmations. This Report can also use from the BALE transaction by selecting Periodic processing -> Schedule audit

This report generates IDocs from the message type ALEAUD containing information about the processing state of inbound IDocs in your own system.
Go to SE38 and enter the report name and pass the parameters                      
The selection screen parameters of this report allows you to regulate the in which system and which application message type that confirmation should be generated in the current report run.

1. Confirmations to system: The system which we need to send the information (here outbound system ECICLNT800)
2. Message type - message type audit confirmations should be made - DEBMAS
3. Date IDoc changed - IDoc creation date

Above three parameters are mandatory.

Message code - optional and Message function - optional

And execute. We see the generated ALEAUD IDoc:

Using this IDoc number, we can analyze the details about the application data and as well as the outbound system details that is control record data, status record  and data record for which message type IDoc is generated. Using the application data field (in table EDID4) we can know that for which message type IDoc is generated.


 

                                                                      or

Using this document number go to WE02, give this document number (here 000000000020054) and execute and we can find the IDoc number for the DEBMAS (here is the DEBMAS) for the inbound system (080).

 


Go to BD87 and give the IDoc number and execute the transaction

 

Using this document number go to outbound system and go to WE02 and enter DEBMAS as message type  and execute and we can find the IDoc number for the DEBMAS (here is the DEBMAS) for the outbound system (client 800).  

And go to BD87 and give the IDoc number (0000000000870818 or 0000000000870819) and execute  

and click on trace IDocs, there we can find the ALE message status.

So like this ALEAUD sends the confirmation to the outbound system (Sender system).

This is the process for the Audit confirmation for DEBMAS (Customer Master).

Conclusions: With the above example explains on how the ALE Audit requirements can be used in projects. This can be a reference document for all such requirements of Audit acknowledgements in ALE environment.