Audit Framework for Fully-Insured Billing

Oracle Revenue Management and Billing calculates the membership premium when you add a membership to a policy plan. It also enables you to recalculate the membership premium in the following scenarios:

• A member person is added or removed from the membership.

• The fields, characteristics, or statuses which are monitored for the auditing purposes are updated at the membership, member person, or pricing rule level.

• A pricing rule is added or updated for the policy plan.

• The derivation and pricing parameters are defined or updated for a bill group.

The membership premium calculation and recalculation (i.e. repricing) is implemented using the Entity Audit feature. The entity audit framework is already configured for the following business objects:

• C1-Membership

• C1_​PERSON_​BO

• C1-PricingRuleTierBased

• C1-PricingRuleAgeBased

• C1-BillLevel

To configure the entity audit framework for the above listed business objects, the following changes are made to these business objects:

• The Eligible for Audit Event option type is set to Y in

• An algorithm created using the C1-REAUDEVNT algorithm type is already attached to the Audit system event of the C1-PricingRuleTierBased, C1-PricingRuleAgeBased, and C1-BillLevel business objects.

• An algorithm created using the C1-FIAUDEV algorithm type is already attached to the Audit system event of the C1-Membership and C1_​PERSON_​BO business objects.

But, the entity audit framework will work when you define an active audit event type for the above listed business objects. For more information on how to create an audit event type, see Defining an Audit Event Type. While creating an audit event type for the C1-PricingRuleTierBased and C1-PricingRuleAgeBased business objects, you need to attach an algorithm created using the C1-AUDEVMPR algorithm type to the Audit Event Processing system event of the respective audit event type. And, while creating an audit event type for the C1-BillLevel business object, you need to attach an algorithm created using the C1-AUDBILLVL algorithm type to the Audit Event Processing system event of the audit event type.

In addition, you need to list the following in the pricing rule types where the category is set to Age Based and Tier Based:

• Audit event types of the C1-Membership and C1_​PERSON_​BO business objects using which the audit event should be created whenever a membership and member person is added, updated, or removed from the policy plan, respectively.

• Elements of the C1-Membership and C1_​PERSON_​BO business objects for which auditing is required.

The way in which the audit events are created and processed for a pricing rule, membership, and member person is different. While creating an audit event, the system checks whether an audit event for the entity with the same effective date already exists in the Pending status. If so, the system does not create a new audit event for the entity. Instead, the system adds a log in the existing audit event.

Related Topics

Parent topic: Fully-Insured Billing