This chapter describes the aggregation scenarios provided to collect revenue assurance data from Oracle Communications Billing and Revenue Management (BRM) pipeline batch rating.
Before you read this chapter, you should be familiar with these concepts:
Pipeline batch rating and aggregation scenarios. See "About Pipeline Rating" in BRM Configuring Pipeline Rating and Discounting and the discussion of aggregation scenarios in the Pricing Center Help for more information.
How Revenue Assurance Manager uses control points and aggregation scenarios. See "About Control Points" and "About Aggregation Scenarios" for more information.
Aggregation scenarios specify the data that is collected by Revenue Assurance Manager from pipeline batch rating. You must specify an aggregation scenario at every control point you set up in the pipeline.
Revenue Assurance Manager includes scenarios that are suitable for use in a production system. These scenarios group revenue assurance data in different ways. See "Data Fields Collected by All Scenarios" for a list of the fields from which the scenarios collect data. See "Fields Used to Group Scenario Data" for a list of the fields by which the scenarios can group data.
For example, the EDR statistics for scenario RA_03 are grouped by service type, such as TEL, SMS, or GPRS. Data, such as event count, retail charged amount, and so on, is aggregated for each service type.
Most of the scenarios group by combinations of grouping fields. For example, scenario RA_04 groups fields by both service type (TEL, SMS, and so on) and EDR status (duplicate, rejected, written-off or successful). Data is aggregated separately for each combination; duplicate EDRs for the SMS service, for example.
If the preconfigured scenarios do not meet your business needs, you can also create your own. For details, see "Creating New Aggregation Scenarios for Revenue Assurance" and instructions for defining aggregation scenarios in Pricing Center Help.
Note:
Custom scenarios require custom UEL templates and cannot be used with Revenue Assurance Center.Before you can use the preconfigured scenarios, you must load them into the pipeline database. See "Loading Scenarios into the Pipeline Manager Database" for instructions.
All of the preconfigured aggregation scenarios collect statistics from the EDR fields listed in Table 7-1:
Table 7-1 All Scenarios Data Fields
| Field | Description |
|---|---|
|
Event count |
Number of EDRs. |
|
Retail charged amount |
Retail charged amount collected. |
|
Event wholesale value |
Total wholesale amount charged for the EDR, if appropriate. |
|
Discount amount |
Discount amount applied. |
|
Duration |
Total usage time, in seconds, if appropriate (for example, for a voice call). |
|
Volume sent |
Data transferred in bytes, if appropriate (for example, for a GPRS event). |
|
Volume received |
Data received in bytes, if appropriate (for example, for a GPRS event). |
|
Earliest call made |
The earliest call start timestamp. |
|
Latest call made |
The latest call start timestamp. |
The EDR data fields in Table 7-2 are available to use for grouping data.
Table 7-2 Grouping Data Fields
| Grouping Field | Description |
|---|---|
|
Batch ID |
Batch ID of the batch being processed. |
|
Original batch ID |
Mediation batch ID of the rerating or recycling EDR batches. |
|
Suspended from batch ID |
The batch ID from which the EDR was suspended. |
|
Service type |
Type of service, such as TEL, SMS, or GPRS. |
|
Revenue stream |
Retail, Wholesale, or Roaming. |
|
Output stream |
The output stream of the EDR. This is based on the service type; for example, if the service type is SMS, the output stream is SMS. |
|
EDR status |
Success, Suspense, Duplicate, Discard, Rejected, or Skipped. |
|
Suspense code |
Suspense reason code assigned to the EDR. |
Table 7-3 provides information about the Revenue Assurance Manager preconfigured aggregation scenarios.
Table 7-3 RA Manager Preconfigured Aggregation Scenarios
| Scenario/ File Name | Collects Data for an EDR Batch Based On | Grouping Fields (Listed in the Grouping Order) | Storable Class | Installation Point | iScripts Required |
|---|---|---|---|---|---|
|
RA_01, Batchstatat_simple |
An EDR batch. |
Batch ID, Original batch ID, Suspended from batch ID |
/process_audit/batchstat/simple |
Anywhere in a pipeline |
None |
|
RA_02, BatchStat_status |
EDR Status. |
Batch ID, Original batch ID, Suspended from batch ID, EDR status |
/process_audit/batchstat/status |
Anywhere in a pipeline |
ISC_SetEDRStatus |
|
RA_03, BatchStat_SvcType |
Service type. |
Batch ID, Original batch ID, Suspended from batch ID, Service type |
/process_audit/batchstat/svctype |
After FCT_ServiceCodeMap |
None |
|
RA_04, BatchStat_SvcTypeStatus |
Service type and EDR status. Using this scenario, you can find the number of records that are duplicate, rejected, or successful for each service type. |
Batch ID, Original batch ID, Suspended from batch ID, Service type, EDR status |
/process_audit/batchstat/svctype_status |
After FCT_ServicecodeMap |
ISC_SetEDRStatus |
|
RA_05, BatchStat_RevenueStream |
Revenue stream. The revenue streams are: Retail, Wholesale, and Roaming. |
Batch ID, Original batch ID, Suspended from batch ID, Revenue stream |
/process_audit/batchstat/revstream |
After Post Rating |
ISC_SetRevenueStream |
|
RA_06, BatchStat_Revenue Stream_Status |
Revenue stream and EDR status. |
Batch ID, Original batch ID, Suspended from batch ID, Revenue stream, EDR status |
/process_audit/batchstat/revstream_status |
After Post Rating |
ISC_SetRevenueStream, ISC_SetEDRStatus |
|
RA_07, BatchStat_RevenueStream_SvcType |
Revenue stream and service type. |
Batch ID, Original batch ID, Suspended from batch ID, Revenue stream, Service type |
/process_audit/batchstat/revstream_svctype |
After Post Rating |
ISC_SetRevenueStream |
|
RA_08, BatchStat_RevenueStream_ServiceType_Status |
Revenue stream, service type, and EDR status. |
Batch ID, Original batch ID, Suspended from batch ID, Revenue stream, Service type, EDR status |
/process_audit/batchstat/revstream_svctype_status |
After Post Rating |
ISC_SetRevenueStream, ISC_SetEDRStatus |
|
RA_09, BatchStat_SvcType_RevenueStream |
Service type and the revenue stream. |
Batch ID, Original batch ID, Suspended from batch ID, Revenue stream, Service type |
/process_audit/batchstat/revstream_status_svctype |
After Post Rating |
ISC_SetRevenueStream |
|
RA_10, BatchStat_ServiceType_RevenueStream_Status |
Service type, revenue stream, and EDR status. |
Batch ID, Original batch ID, Suspended from batch ID, Revenue stream, Service type, EDR status |
/process_audit/batchstat/svctype_revstream_status |
After Post Rating |
ISC_SetRevenueStream, ISC_SetEDRStatus |
|
RA_11, BatchStat_Outputstream |
Output stream. |
Batch ID, Original batch ID, Suspended from batch ID, Output stream |
/process_audit/batchstat/outputstream |
Just before output |
ISC_SetOutputStream |
|
RA_12, BatchStat_ServiceType_RevenueStream_Outputstream |
Service type, revenue stream, and output stream. |
Batch ID, Original batch ID, Suspended from batch ID, Output stream, Service type, Revenue stream |
/process_audit/batchstat/svctype_revstream_outputstream |
Just before output |
ISC_SetRevenueStream and ISC_SetOutputStream |
|
RA_13, BatchStat_Suspense |
Suspense reason code. |
Batch ID, Original batch ID, Suspended from batch ID, Suspense code |
/process_audit/batchstat/suspense |
After FCT_Suspense |
None |
|
RA_14, BatchStat_ServiceType_RevenueStream_Status_Outputstream |
Service type, revenue stream, EDR status, and output stream. |
Batch ID, Original batch ID, Suspended from batch ID, Service type, Revenue stream, EDR status, Output stream |
/process_audit/batchstat/svctype_revstream_status_outputstream |
Just before output |
ISC_SetRevenueStream, ISC_SetOutputStream, and ISC_SetEDRStatus |