4 Collecting Revenue Assurance Data for Usage Write-Offs

This chapter describes how to configure Oracle Communications Billing and Revenue Management (BRM) to collect revenue assurance data for usage write-offs.

Configuring BRM to Collect Revenue Assurance Data for Usage Write-Offs

For usage event records written off by Suspense Manager, Revenue Assurance Manager collects the original batch ID and the number of event records that were written off in the batch. See "About Collecting Revenue Assurance Data on Write-Offs".

To collect revenue assurance data for written-off usage event records, do the following:

• Configure event notification to call the PCM_OP_PROCESS_AUDIT_CREATE_WRITEOFF_SUMMARY opcode when Suspense Manager generates the /event/notification/suspense/writeoff event.

  See "Configuring Event Notification for Revenue Assurance".

• (Optional) Rename the default control point for collecting revenue assurance data on written-off usage event records.

  See "Renaming the Control Point for Collecting Data from Usage Write-Offs".

Configuring Event Notification for Revenue Assurance

Revenue Assurance Manager uses event notification to collect data on written-off usage event records.

Before you can use Revenue Assurance Manager to collect such data, you must configure the event notification feature as follows:

1. If your system has multiple configuration files for event notification, merge them.

   See "Merging Event Notification Lists" in BRM Developer's Guide.

2. Ensure that the merged file includes the entire event notification list in the BRM_home/sys/data/config/pin_notify_ra file.

3. (Optional) If necessary to accommodate your business needs, add, modify, or delete entries in your final event notification list.

   See "Editing the Event Notification List" in BRM Developer's Guide.

4. (Optional) If necessary to accommodate your business needs, create custom opcodes for event notification to trigger.

   See "Triggering Custom Operations" in BRM Developer's Guide.

5. Load your final event notification list into the BRM database.

   See "Loading the Event Notification List" in BRM Developer's Guide.

   Note:

   In addition, your business needs might require you to use event notification to call opcodes when other objects are created in the BRM database.

See "Using Event Notification" in BRM Developer's Guide.

Renaming the Control Point for Collecting Data from Usage Write-Offs

The control point to collect revenue assurance data from written-off usage event records is configured in the CM configuration file (BRM_home/sys/cm/pin.conf).

To rename the control point for collecting data from usage write-offs:

1. Open the CM BRM_home/sys/cm/pin.conf file in a text editor.

2. Rename the control point in the writeoff_control_point_id entry.

   The default name for the control point is CP_SuspenseWriteOff.

3. Save and close the file.

4. Stop and restart the CM.