Hypertext: Object Class - Class to which a document belongs.
Document Name
OALE_AUDITVAR_SE38
In this section you create variants for the RBDSTATE report. Create the variants on the receiver system of the original message.
Example
An ALE audit confirmation is required for the 'ORDERS' message, which is sent from System A to System B. This means that a variant of the RBDSTATE report with logical sender system 'A' and message type 'ORDERS' must be created in System B.
Activities
You can define various values for your variants:
Logical sender system,
Message type
Message variant
Message function
Creation date of IDocs
Create appropriate variants for the RBDSTATE report.
To do this, execute the function, enter "RBDSTATE", select Variants and choose Change.
Enter a name for the variant and choose Create.
Maintain the attributes for the variant.
The logical sending system is the system to which the audit confirmation is to be sent.
Message type, message variant and message function specify the messages for which there are confirmations.
If the fields are not defined in the variant, then the system uses the possible settings from the distribution model.
The creation date specifies the selection time range. If nothing is specified here, then all messages since the time the report was last executed will be covered.
Save the variant.
Create as many variants as needed to take account of all message flows for which ALE audit should be performed.
Hierarchy 
SAP_BASIS (Software Component) SAP Basis Component
BC-MID-ALE (Application Component) ALE Integration Technology
SALC (Package) Application Link Enabling: Customizing
IMG Activity 
Document 
History 
