Audit Event Processing

On executing the Audit Event Processing (C1-AUDEV) batch, the system checks whether there are any audit events in the Pending status. If there is an audit event in the Pending status, the system checks whether an algorithm is attached to the Audit Event Processing system event of the respective audit event type. If an algorithm is not attached to the Audit Event Processing system event of the respective audit event type, the status of the audit event is set to Complete.

However, if an algorithm is attached to the Audit Event Processing system event of the respective audit event type, the system executes the algorithm and accordingly changes the status of the audit event to Complete. For example, while processing the audit events of the C1-PricingRuleTierBased and C1-PricingRuleAgeBased business objects, the system checks whether an algorithm is attached to the Audit Event Processing system event of the respective audit event type. If the C1-AUDEVMPR algorithm is attached to the audit event type, the system identifies the policy plan where the pricing rule is defined. Once the policy plan is identified, it extracts a list of membership defined on the policy plan and the pricing rule type using which the pricing rule is created. Then, the system creates an entry for each membership, pricing rule type, and effective date combination in the CI_​REPRC_​ENTITY_​DTL table. The status of these entries is set to P. Finally, the status of the audit event is set to Complete.

If any error occurs, the status of the audit event is set to Error. The system enables you to either reprocess or cancel the audit events which are in the Error status. On canceling an audit event, the status of the audit event is changed to Canceled.

For more information about the Audit Event Processing (C1-AUDEV) batch and its parameters, see Oracle Revenue Management and Billing Batch Guide.