oracle communications data model adapters and analytics ...[1]oracle® communications data model...

[1] Oracle® Communications Data ModelAdapters and Analytics User’s Guide

Release 12.1

E64316-02

October 2015

Oracle Communications Data Model Adapters and Analytics User's Guide, Release 12.1

E64316-02

Copyright © 2013, 2015, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

iii

Contents

Preface ................................................................................................................................................................. ix

Audience....................................................................................................................................................... ixDownloading Oracle Communications Documentation....................................................................... ixDocumentation Accessibility ..................................................................................................................... ixRelated Documents ..................................................................................................................................... xDocument Revision History ...................................................................................................................... x

Part I Billing and Revenue Management Application Adapter

1 About the BRM Adapter for Oracle Communications Data Model

About the BRM Adapter ........................................................................................................................ 1-1Components of the BRM Adapter ................................................................................................... 1-2

Database Schemas Used by the BRM Adapter ...................................................................... 1-2Oracle Data Integrator................................................................................................................ 1-2Oracle GoldenGate...................................................................................................................... 1-2

BRM Adapter Execution Flows.............................................................................................................. 1-3Execution Flow Using the BRM Adapter with Only Oracle Data Integrator............................ 1-3Execution Flow Using the BRM Adapter with Oracle Data Integrator and Oracle GoldenGate... 1-4

2 Using the BRM Adapter

About Populating a Warehouse Using the BRM Adapter................................................................ 2-1About the BRM Adapter Data Load Packages............................................................................... 2-2About the BRM Adapter Data Load Parameters........................................................................... 2-2About BRM Adapter Configuration................................................................................................ 2-2

Using Email Alert Notifications with the BRM Adapter ...................................................... 2-3Using Intermediate Commits for Huge Batch Updates ........................................................ 2-3Using Parallel Loading to Speed Up the Data Loads ............................................................ 2-3

Performing an Initial Load of the Foundation Layer of the Oracle Communications Data Model Warehouse ................................................................................................................................................. 2-4Refreshing the Foundation Layer of the Oracle Communications Data Model Warehouse..... 2-8

Refreshing the Foundation Layer on a Scheduled Basis .............................................................. 2-9Scheduling Data Loads with the Oracle Data Integrator Built-In Scheduler from a Command Line 2-9

iv

Scheduling Data Loads with the Oracle Data Integrator Built-In Scheduler from a Web Service 2-10

Refreshing the Foundation Layer with Real-Time Data Using Oracle GoldenGate ............. 2-11Manually Refreshing the Foundation Layer ............................................................................... 2-12

Administering BRM Adapter Data Load Processes ....................................................................... 2-13Configuring the BRM Adapter for Populating Oracle Communications Data Model Warehouse 2-13

Updating the Data Load Parameters..................................................................................... 2-13Setting the Intermediate Commit Interval ........................................................................... 2-14Configuring the BRM Adapter to Send Email Alert Notifications................................... 2-15Configuring Parallel Loading................................................................................................. 2-16

Managing and Monitoring BRM Adapter Data Load Processes.............................................. 2-17Using Oracle Data Integrator Web Console to Manage and Monitor Data Load Process ....... 2-17Displaying Your Brand Logo on the User Interface ........................................................... 2-18Monitoring a Huge Batch Update ......................................................................................... 2-19Using Oracle Database In-Memory Column Store to Improve Database Operations Performance 2-19Restarting a Data Load Process After a Package Execution Fails ..................................... 2-20BRM Adapter Exception Handling ....................................................................................... 2-21Exception Handler Configuration ......................................................................................... 2-21Drop Error Tables (E$_) .......................................................................................................... 2-26Moving Data into History Tables .......................................................................................... 2-26

3 BRM Adapter Reference

BRM Source and Oracle Communications Data Model Target Tables ......................................... 3-1Oracle Data Integrator BRM_OCDM Project ..................................................................................... 3-4

Objects in SRC_STG_NONGG Folder of the BRM_OCDM Project............................................ 3-4Objects in the STG_OCDM Folder of the BRM_OCDM Project.................................................. 3-7

Schema Definitions Added by the BRM Adapter .......................................................................... 3-10BRM_STG Schema Objects............................................................................................................. 3-11OCDM_SYS Objects for the BRM Adapter.................................................................................. 3-11

Part II Network Charging and Control Application Adapter

4 About NCC Adapter for Oracle Communications Data Model

What Are Oracle Communications Prepaid Charging and Network Charging and Control.... 4-1Overview of NCC Adapter ..................................................................................................................... 4-1

Components of the NCC Adapter ................................................................................................... 4-2Database Schemas Used by the NCC Adapter ....................................................................... 4-2Oracle Data Integrator................................................................................................................ 4-3Oracle GoldenGate...................................................................................................................... 4-3

NCC Adapter Execution Flows .............................................................................................................. 4-4Execution Flow Using the NCC Adapter with Oracle GoldenGate and Oracle Data Integrator... 4-4Execution Flow Using the NCC Adapter with Only Oracle Data Integrator............................ 4-5

v

5 Using the NCC Adapter

About Populating a Warehouse Using the NCC Adapter ................................................................ 5-1Initial Loading Using the NCC Adapter.............................................................................................. 5-1Refreshing the Data Using the NCC Adapter..................................................................................... 5-2

Refreshing the Foundation Layer on a Scheduled Basis .............................................................. 5-2Refreshing the Foundation Layer with Real-Time Data............................................................... 5-3

6 NCC Adapter Reference

NCC Adapter Source and Target Tables.............................................................................................. 6-1Oracle Data Integrator NCC_OCDM Project...................................................................................... 6-2

SRC_STG_NONAGG ........................................................................................................................ 6-2SRC_STG_LOAD_NON_OGG_PKG Package ....................................................................... 6-2SRC_STG_EDR_LOAD_INCREMENTAL_PKG Package .................................................... 6-2SRC_STG_EDR_LOAD_INITIAL_PKG Package................................................................... 6-2

STG_OCDM ........................................................................................................................................ 6-2STG_OCDM_INITIAL_LOAD_PKG Package........................................................................ 6-2STG_OCDM_EDR_PKG Package............................................................................................. 6-3STG_OCDM_OGG_CDC_LOAD_SCENARIO_PKG Package ............................................ 6-3

NCC_STG Schema Objects .................................................................................................................... 6-4NCC Source Schema Objects ................................................................................................................. 6-5Schema Definitions Added by the NCC Adapter.............................................................................. 6-5

NCC_STG Schema Objects ............................................................................................................... 6-5Definitions Added to the OCDM_SYS Schema ............................................................................. 6-6

Part III Social Network Analytics for Oracle Communications Data Model

7 Social Network Analytics

Overview of the Social Network Analytics Add-On Adapter......................................................... 7-1About Social Network Analytics Features ..................................................................................... 7-1Social Network Analytics Opt-Out Features.................................................................................. 7-2Social Network Analytics Concepts and Terms ............................................................................ 7-2

Social Network Analytics Process Flow............................................................................................... 7-3About Social Network Analytics Roles ............................................................................................... 7-3

Social Network Analytics Subscriber Roles Leaders and Role Strength.................................... 7-3

8 Social Network Analytics Reports

SNA Home Page ....................................................................................................................................... 8-1SNA Analysis Report............................................................................................................................... 8-2SNA Analysis Runs Report .................................................................................................................... 8-3

Scheduler Jobs Overview: Polling Analysis Job Report ............................................................... 8-4Scheduler Jobs Overview: Update Analysis Job Run Log Details Report ................................. 8-4

SNA Network Report .............................................................................................................................. 8-5SNA Communities Report...................................................................................................................... 8-6SNA Churn Report................................................................................................................................... 8-8SNA Influence Report ............................................................................................................................. 8-9

vi

SNA Subscribers Report ......................................................................................................................... 8-9

Part IV Billing Analytics for Oracle Communications Data Model

9 Billing Analytics Overview and Reports

Overview of Oracle Communications Data Model Billing Analytics ........................................... 9-1Overview of Billing Analytics Process Flow ...................................................................................... 9-1Billing Analytics Reports........................................................................................................................ 9-2

Billed Revenue Reports ..................................................................................................................... 9-2Billed Revenue Overview .......................................................................................................... 9-3Revenue Detail ............................................................................................................................ 9-6ARPU ............................................................................................................................................ 9-9Discounts................................................................................................................................... 9-12Payments and Collections....................................................................................................... 9-14Adjustments.............................................................................................................................. 9-19Maps........................................................................................................................................... 9-22

Billing Efficiency Reports............................................................................................................... 9-23Billing Calculations.................................................................................................................. 9-23Billing Collection and Receivables Management ................................................................ 9-27Billing Inquiries, Disputes, and Adjustments...................................................................... 9-28

Customer Metrics Reports ............................................................................................................. 9-30Acquisition................................................................................................................................ 9-30Churn ......................................................................................................................................... 9-34

Prepaid Metrics Reports................................................................................................................. 9-37Recharges Reports.................................................................................................................... 9-37Prepaid Customer Base Reports ............................................................................................ 9-38Account Recharge .................................................................................................................... 9-39Disturbed Recharge ................................................................................................................. 9-40

Usage Revenue Reports.................................................................................................................. 9-41Voice Usage............................................................................................................................... 9-41Voice Usage Revenue .............................................................................................................. 9-44Data Usage ................................................................................................................................ 9-47SMS Usage................................................................................................................................. 9-48MMS Usage............................................................................................................................... 9-49

10 Billing Analytics Reference

Billing Analytics Physical Objects..................................................................................................... 10-1Billing Analytics Relationships and Measures ............................................................................... 10-2

DWB_INVC_ITEM Analytics ........................................................................................................ 10-2DWD_ACCT_BAL_MO Analytics................................................................................................ 10-4DWD_ACCT_DEPT_MO Analytics ............................................................................................. 10-6DWD_ACCT_PYMT_DAY Analytics .......................................................................................... 10-8DWD_CNT_DAY Analytics ........................................................................................................ 10-10DWD_DATA_USG_DAY Analytics........................................................................................... 10-12DWD_INVC_DAY Analytics ...................................................................................................... 10-14DWD_PRPD_ACCT_STTSTC_DAY Analytics......................................................................... 10-15

vii

DWD_RVN_DAY Analytics ........................................................................................................ 10-17DWD_TMF_KPI Analytics........................................................................................................... 10-21DWD_VAS_USG_DAY Analytics .............................................................................................. 10-22DWD_VOI_CALL_DAY Analytics............................................................................................. 10-25DWV_PRPD_CUST_STAT View Analytics .............................................................................. 10-27

A TMF KPI Business Metrics

Percentage of Payment Transactions by Payment Method (B-CE-1B) .......................................... A-1Percentage of Electronic Bills Issued (B-CE-1C) ............................................................................... A-2Mean Time to Prepare and Dispatch Bills (B-CE-4B)....................................................................... A-2Percentage of Inaccurate Bills (B-CE-4C) ............................................................................................ A-3Determine Percentage of Bills Adjusted (B-CE-4D)......................................................................... A-3Percentage of Billing-Related Queries (B-CE-4E) ............................................................................. A-4Time to Prepare Bills for Display and Dispatch (B-OE-2A) ........................................................... A-4Collections Efficiency Against Credit Terms (B-OE-3E) ................................................................. A-5Percentage of E-payments Received (B-CE-1D) ................................................................................ A-5Percentage of Bills Adjusted Internally (B-CE-4F) ........................................................................... A-6Mean Time from Service Activation to Bill Dispatch (B_OE_2C) ................................................. A-6Percentage Collectible Debt Written Off (B_OE_3D) ...................................................................... A-7Volume of Customer Requests (CM_CE_3A) .................................................................................... A-7

ix

Preface

This book describes the adapters and analytics available for Oracle Communications Data Model. Since the needs of each Oracle Communications Data Model environment are unique, Oracle Communications Data Model is configurable so it can be modified to address each customer's needs. This book covers adapter specific information and the analytics options.

AudienceThe information in this book is intended for:

■ IT specialists, who maintain and adjust Oracle Communications Data Model. They are assumed to have a strong foundation in Oracle Database and PL/SQL and Oracle Business Intelligence Suite Enterprise Edition.

■ Database administrators, who administer the data warehouse and the database objects that store the data. They are assumed to understand Intra-ETL, which transfers data from one format to another, and, also PL/SQL, and the Oracle Database.

■ Business analysts, including information and data analysts, market analysts, and sales analysts.

Downloading Oracle Communications DocumentationProduct documentation is located on Oracle Help Center:

http://docs.oracle.com

Additional Oracle Communications documentation is available from the Oracle software delivery website:

https://edelivery.oracle.com

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle SupportOracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing

x

impaired.

Related DocumentsFor more information about Oracle Oracle Communications Data Model, see the following documents in the Oracle Oracle Communications Data Model documentation set:

■ Oracle Communications Data Model Adapters and Analytics Installation Guide

■ Oracle Communications Data Model Installation Guide

■ Oracle Communications Data Model Release Notes

■ Oracle Communications Data Model Implementation and Operations Guide

■ Oracle Communications Data Model Reference

Document Revision HistoryThe following table lists the revision history for this book:

Version Date Description

E64316-02 October 2015 Documentation updates.

■ Added the "Using Oracle Database In-Memory Column Store to Improve Database Operations Performance" section.

■ Updated the "Objects in the STG_OCDM Folder of the BRM_OCDM Project" section.

E64316-01 September 2015 Initial release.

Part IPart I Billing and Revenue Management Application

Adapter

Part I contains the following chapters:

■ Chapter 1, "About the BRM Adapter for Oracle Communications Data Model"

■ Chapter 2, "Using the BRM Adapter"

■ Chapter 3, "BRM Adapter Reference"

1

About the BRM Adapter for Oracle Communications Data Model 1-1

1About the BRM Adapter for OracleCommunications Data Model

This chapter describes the Oracle Communication Billing and Revenue Management Adapter for Oracle Communications Data Model (BRM Adapter).

For information about the Oracle Communications Data Model, see Oracle Communications Data Model Implementation and Operations Guide.

About the BRM Adapter The BRM Adapter is an option for Oracle Communications Data Model. You use the BRM Adapter to populate the foundation layer (that is, the base, reference, and lookup tables) of an Oracle Communications Data Model warehouse with the data from a BRM source system.

Figure 1–1 shows the BRM Adapter architecture.

The BRM adapter supports both Oracle Data Integrator and Oracle GoldenGate.

Oracle Data Integrator is used for batch loading (to the staging layer) and for transforming the data in the staging layer and loading it to the foundation layer of the Oracle Communications Data Model.

Oracle GoldenGate is used for real-time data feeds to the staging layer.

Figure 1–1 BRM Adapter Architecture

About the BRM Adapter

1-2 Oracle Communications Data Model Adapters and Analytics User's Guide

Components of the BRM AdapterThe BRM Adapter uses the following components:

■ Database schemas used by the BRM Adapter

■ Oracle Data Integrator

■ Oracle GoldenGate

■ Oracle Communications Data Model

■ Billing and Revenue Management source system

Database Schemas Used by the BRM Adapter The BRM Adapter uses the following database schemas:

■ Source schemas: The Oracle Communications Billing and Revenue Management (BRM) database schema, defined as BRM_SRC schema.

See "BRM Source and Oracle Communications Data Model Target Tables" for information on the specific source objects.

■ Staging layer schema. The BRM Adapter uses a staging layer when loading data from the BRM source system to the Oracle Communications Data Model warehouse. The staging layer schema stores changed data and historical data and is used as the source schema when loading the foundation layer objects of the Oracle Communications Data Model.The staging layer database schema is defined as BRM_STG schema.

■ Target schema. The target of the BRM Adapter is an Oracle Communications Data Model warehouse. The specific target objects are the foundation layer objects. These objects are defined in the Oracle Communications Data Model OCDM_SYS schema. For information about the OCDM_SYS schema, see Oracle Communications Data Model Reference.

The BRM Adapter defines additional procedures in the OCDM_SYS schema (see "OCDM_SYS Objects for the BRM Adapter").

Oracle Data IntegratorThe BRM Adapter uses extract, transform, and load (ETL) procedures created in Oracle Data Integrator for the initial load of the foundation layer of the Oracle Communications Data Model warehouse (that is, the base, reference, and lookup tables in the OCDM_SYS schema). You can also use the Oracle Data Integrator ETL procedures to perform a scheduled refresh of the data in the warehouse.

For more information on the use of Oracle Data Integrator ETL procedures with the BRM Adapter, see:

■ "Execution Flow Using the BRM Adapter with Only Oracle Data Integrator"

■ "Execution Flow Using the BRM Adapter with Oracle Data Integrator and Oracle GoldenGate"

Oracle GoldenGateAfter the initial load of the foundation layer of the Oracle Communications Data Model, you can use Oracle GoldenGate to perform real-time feeds of the BRM source data to the staging layer.

BRM Adapter Execution Flows


For more information on the use of Oracle GoldenGate with the BRM Adapter, see:

■ "Execution Flow Using the BRM Adapter with Oracle Data Integrator and Oracle GoldenGate".

■ "Refreshing the Foundation Layer with Real-Time Data Using Oracle GoldenGate".

BRM Adapter Execution FlowsThe BRM Adapter uses a different execution flow depending on whether you are using the adapter with Oracle GoldenGate:

■ Execution Flow Using the BRM Adapter with Only Oracle Data Integrator

■ Execution Flow Using the BRM Adapter with Oracle Data Integrator and Oracle GoldenGate

Execution Flow Using the BRM Adapter with Only Oracle Data IntegratorWhen you use the BRM Adapter with only Oracle Data Integrator, this method of using the BRM Adapter is the Oracle Data Integrator-pull version.

You always use the Oracle Data Integrator-pull version for the initial load of the data warehouse. The Oracle Data Integrator-pull version also provides the option to refresh the data in the warehouse at regular periods.

Figure 1–2 illustrates the BRM Adapter execution flow when using the adapter with only Oracle Data Integrator.

Figure 1–2 Execution Flow When Using the BRM Adapter with Only Oracle Data Integrator

When using Oracle Data Integrator-pull version, the execution flow is as follows (as shown in Figure 1–2):

1. (Steps 1 and 3) The BRM Adapter, using Oracle Data Integrator, loads the data from the BRM source database into the staging layer database tables.

2. (Steps 2 and 5) Using procedures, the BRM Adapter loads data into several staging layer database tables; for example, last day, delta, and history tables.

3. (Step 4) The BRM Adapter loads the delta tables with the changed data between staging table and last day table (staging table 'MINUS' last day table).



4. (Step 6) The BRM Adapter loads the data from the delta tables into the foundation layer of the Oracle Communications Data Model warehouse.

Execution Flow Using the BRM Adapter with Oracle Data Integrator and Oracle GoldenGate

When you use the BRM Adapter with Oracle Data Integrator and Oracle GoldenGate to refresh the foundation layer of the Oracle Communications Data Model warehouse, this method allows the data in the foundation layer to be synchronized with the BRM source data.

Figure 1–3 illustrates the BRM Adapter execution flow when using the BRM Adapter with Oracle Data Integrator and Oracle GoldenGate.

Figure 1–3 Execution Flow When Using the BRM Adapter with Oracle Data Integrator and Oracle GoldenGate

When using Oracle Data Integrator and Oracle GoldenGate with the BRM Adapter, the execution flow is as follows (as shown in Figure 1–3):

1. (Step 1) When new data is updated in the BRM source database, Oracle GoldenGate extracts the new data and uses it to populate the staging layer database tables.

2. (Steps 2 and 3) After the staging tables are updated by the Oracle GoldenGate extract process, the STG_OCDM_OGG_CDC_LOAD_SCENERIO_PKG procedure loads the delta tables in the staging layer with data from the staging tables and the delta history tables in the staging layer with data from the delta tables.

Note: You always use Oracle Data Integrator pull-version for the initial load of the foundation layer of the Oracle Communications Data Model warehouse.

Note: Only the data in the delta history tables remains forever and is always synchronized with source data. After the data in the delta staging tables is loaded into the foundation layer of the Oracle Communications Data Model warehouse, the delta tables are truncated.



3. (Step 4) BRM Adapter, using Oracle Data Integrator, loads the data from the delta tables into to the foundation layer of Oracle Communications Data Model warehouse.

2

Using the BRM Adapter 2-1

2Using the BRM Adapter

This chapter provides information about using the Oracle Communications Billing and Revenue Management Adapter for Oracle Communications Data Model (the BRM Adapter) to populate the foundation layer of an Oracle Communications Data Model warehouse with data from a BRM source system.

To use the BRM Adapter, you should have experience with:



■ Oracle SQL Developer

■ Extensible markup language (XML) programming

You should also have a basic knowledge of the following:

■ BRM Adapter architecture and execution flows. See "About the BRM Adapter for Oracle Communications Data Model".

■ Extract, transform, and load (ETL) concepts

■ Data warehouse concepts

For information about installing the BRM Adapter, see Oracle Communications Data Model Adapters and Analytics Installation Guide.

For detailed information about the objects and procedures associated with the BRM Adapter, see "BRM Adapter Reference".

About Populating a Warehouse Using the BRM AdapterYou use the BRM Adapter to populate or refresh the foundation layer (that is, the base, reference, and lookup tables defined in the OCDM_SYS schema) of the Oracle Communications Data Model warehouse.

The BRM Adapter includes data load packages that you run in Oracle Data Integrator to populate the target Oracle Communications Data Model warehouse with data from a source BRM system.

Typically, you perform an initial load of the Oracle Communications Data Model warehouse with the data from your BRM source system, and then you set up incremental loads to regularly refresh the data in the Oracle Communications Data Model warehouse to keep the warehouse synchronized with the BRM system.

After you use the BRM Adapter to populate the foundation layer, you populate or refresh the analytical layer (that is, the derived tables, aggregate tables, Oracle OLAP cubes, and data mining models defined in the OCDM_SYS schema) of the Oracle

About Populating a Warehouse Using the BRM Adapter


Communications Data Model warehouse. For more information, see Oracle Communications Data Model Implementation and Operations Guide.

About the BRM Adapter Data Load PackagesThe BRM Adapter includes data load packages that you run in Oracle Data Integrator to load data from the BRM source system into the foundation layer of the Oracle Communications Data Model warehouse.

The four main packages load different types of data:

■ The usage package loads usage-related data

■ The billing package loads billing-related data

■ The payment package loads payment-related data

■ The collection package loads collection-related data

The packages provide the flexibility to load the data as needed. For example, you can run the billing package to update billing-related data to the Oracle Communications Data Model warehouse during off-peak hours but run the usage package to update usage-related data to the warehouse more frequently.

Additionally, the packages load data from the BRM source system based on the data dependencies to maintain the data integrity in the warehouse.

For instance, when you run the usage package, any new subscriber information (from the last update) is loaded into the Oracle Communications Data Model warehouse before the subscriber usage data is loaded.

Similarly, when you run the billing package, any new subscriber information and subscriber usage data (from the last update) are loaded into the warehouse before the subscriber billing data is loaded. When you run the payment package, any new subscriber information, subscriber usage data, and billing data (from the last update) are loaded into the warehouse before the subscriber payment data is loaded. When you run the collection package, any new subscriber information, subscriber usage data, billing data, and payment data (from the last update) are loaded into the warehouse before the subscriber collection data is loaded.

About the BRM Adapter Data Load ParametersThe data load parameters specify which data to extract from the BRM source system and transform and load into the foundation layer in the Oracle Communications Data Model warehouse.

For example, you could extract all the usage events from the BRM source system that occurred between May 10 12:50 PM and May 11 1:00 PM.

You configure the data load parameters before you perform the initial load of the data warehouse. After the initial load, the BRM Adapter updates and maintains the date parameter values for refreshing the data in the warehouse.

About BRM Adapter ConfigurationThe following sections describe the BRM Adapter configurations to manage the data loads.

About Populating a Warehouse Using the BRM Adapter


Using Email Alert Notifications with the BRM AdapterYou can configure the BRM Adapter to send email alert notifications to the end-users and operations personnel to keep them informed of a data load process.

The BRM Adapter triggers the alert notifications when:

■ A data load process finishes.

■ In the event an error is encountered at the mapping-level during the data load process.

See "Configuring the BRM Adapter to Send Email Alert Notifications" for more information.

Using Intermediate Commits for Huge Batch UpdatesWhen you have a huge batch update (that might run for several hours) that would require a full rollback of the whole transaction if a database failure or a transaction failure, you can choose to use intermediate commits to prevent loss of the previous updates. When you use intermediate commits, the updates that are performed (until the intermediate commit happens) are made permanent in the database. When a failure occurs and you restart the batch update, the update proceeds from the last completed transaction.

For example, when the intermediate commit interval is six hours for a huge batch update, the BRM Adapter extracts the BRM source data and loads it to the foundation layer of the Oracle Communications Data Model using six hour time intervals as follows:

■ Data with a timestamp from midnight to 6AM is extracted and loaded.

■ Data with a timestamp from 6AM to 12PM is extracted and loaded.

■ Data with a timestamp from 12PM to 6PM is extracted and loaded.

■ Data with a timestamp from 6PM to midnight is extracted and loaded.

This method allows the BRM Adapter to continue the updates from the last data load that completed without loosing the previous updates.

The best Oracle database commit frequency is never to explicitly commit and let the entire update complete as a single transaction, but using intermediate commits is reserved only for huge batch updates where the time that is required for a full rollback of the transaction is not feasible due to the size of the batch window according to the daily scheduled jobs run by your operations team.

For information about configuring the intermediate commit interval, see "Setting the Intermediate Commit Interval".

Using Parallel Loading to Speed Up the Data LoadsUsing parallel loading can speed up load times for large volume of data. When you use parallel loading, instead of one process performing the data load, multiple processes do part of the load at the same time. For example, a single process loads a batch of 100 records at one record per minute. When you use parallel loading with four processes, each process handles one fourth of the data or 25 records. It takes 25 minutes to load the entire batch instead of 100 minutes.

You might want to use parallel loading to improve load time depending on the volume of your data. It is important that you consult with your database administrator to ensure that your database system can support multiple parallel processing. Using

Performing an Initial Load of the Foundation Layer of the Oracle Communications Data Model Warehouse


parallel loading on a system with insufficient resources may result in poor performance because of overutilized system resources.

See "Configuring Parallel Loading" for information about configuring parallel loading.


Oracle recommends that you perform an initial load of the foundation layer of the Oracle Communications Data Model warehouse on a pre-production environment to verify and correct any errors in the BRM source data to minimize errors in your production system, and then perform the initial load of the foundation layer on your production system.

You can perform the initial load of the foundation layer in two ways:

■ You can run one data load package to load the data from end to end, which loads the data from the BRM source system to staging layer and then to foundation layer.

■ You can run separate data load packages to load the data in stages, from the BRM source system to the staging layer and from the staging layer to foundation layer, if needed.

For instance, you may want to load data from different source systems to the staging layer, and then load the data from the staging layer to the foundation layer.

To perform an initial load of the foundation layer:

1. Copy the sample XML template below into an XML editor or a text editor.

The sample XML template contains a <DATA_RECORD> element for each data load package (usage, billing, payment, and collection). The data load parameters for each load package are defined as the child elements in the <DATA_RECORD> element.

<?xml version="1.0" ?><!DOCTYPE main [

<!ELEMENT main (DATA_RECORD*)><!ELEMENT DATA_RECORD(PROCESS_ID,PROCESS_NAME,FROM_DATE_ETL,TO_DATE_ETL,LOAD_DATE?,SUCC_

IND?,SPLIT_INTERVAL?,PROCESS_TYPE?)+><!ELEMENT PROCESS_ID (#PCDATA)><!ELEMENT PROCESS_NAME (#PCDATA)><!ELEMENT FROM_DATE_ETL (#PCDATA)><!ELEMENT TO_DATE_ETL (#PCDATA)><!ELEMENT LOAD_DATE (#PCDATA)><!ELEMENT SUCC_IND (#PCDATA)><!ELEMENT SPLIT_INTERVAL (#PCDATA)><!ELEMENT PROCESS_TYPE (#PCDATA)>

]><main>

<DATA_RECORD><PROCESS_ID>1</PROCESS_ID>

Tip: When you perform the initial load on your production system, you can copy the XML configuration file that you created on your pre-production environment to your production system, and then set the data load parameters.



<PROCESS_NAME>BRM-ADAPTER</PROCESS_NAME><FROM_DATE_ETL></FROM_DATE_ETL><TO_DATE_ETL></TO_DATE_ETL><LOAD_DATE></LOAD_DATE><SUCC_IND>N</SUCC_IND><SPLIT_INTERVAL></SPLIT_INTERVAL><PROCESS_TYPE>USAGE-EVENTS</PROCESS_TYPE>

</DATA_RECORD><DATA_RECORD>

<PROCESS_ID>2</PROCESS_ID><PROCESS_NAME>BRM-ADAPTER</PROCESS_NAME><FROM_DATE_ETL></FROM_DATE_ETL><TO_DATE_ETL></TO_DATE_ETL><LOAD_DATE></LOAD_DATE><SUCC_IND>N</SUCC_IND><SPLIT_INTERVAL></SPLIT_INTERVAL><PROCESS_TYPE>BILLING-INVOICE</PROCESS_TYPE>


<PROCESS_ID>3</PROCESS_ID><PROCESS_NAME>BRM-ADAPTER</PROCESS_NAME><FROM_DATE_ETL></FROM_DATE_ETL><TO_DATE_ETL></TO_DATE_ETL><LOAD_DATE></LOAD_DATE><SUCC_IND>N</SUCC_IND><SPLIT_INTERVAL></SPLIT_INTERVAL><PROCESS_TYPE>PAYMENT-DATA</PROCESS_TYPE>


<PROCESS_ID>4</PROCESS_ID><PROCESS_NAME>BRM-ADAPTER</PROCESS_NAME><FROM_DATE_ETL></FROM_DATE_ETL><TO_DATE_ETL></TO_DATE_ETL><LOAD_DATE></LOAD_DATE><SUCC_IND>N</SUCC_IND><SPLIT_INTERVAL></SPLIT_INTERVAL><PROCESS_TYPE>COLLECTION-DATA</PROCESS_TYPE>

</DATA_RECORD></main>

2. For each <DATA_RECORD> element, enter the values for the following child elements: <FROM_DATE_ETL>, <TO_DATE_ETL>, <LOAD_DATE>, and <SPLIT_INTERVAL>.

Table 2–1 describes the <DATA_RECORD> child elements.

Table 2–1 Data Load Parameters

XML Element Description

PROCESS_ID A unique ID that identifies the load process type. This value is set as follows:

■ 1: USAGE-EVENTS load process type.

■ 2: BILLING-INVOICE load process type.

■ 3: PAYMENT-DATA load process type.

■ 4: COLLECTION-DATA load process type.

Do not change these values.



3. Save the file as dwc_log_retention.xml.

4. Using SQL Developer, update the location of the XML file in the database:

a. Connect to the BRM_STG schema.

b. Run the following query, which stores the location of the dwc_log_retention.xml file in the XML_FILEPATH table.

UPDATE XML_FILEPATH SET XML_FILEPATH=file_path/dwc_log_retention.xml WHERE XML_TYPE=’LOG_RETENTION’;COMMIT;

PROCESS_NAME Specifies the name for the BRM Adapter process.

This value is set to BRM-ADAPTER. Do not change this value.

FROM_DATE_ETL Specifies the starting date (in the format YYYY/MM/DD HH:MM:SS) from which data in the BRM source system is extracted, transformed, and then loaded into the Oracle Communications Data Model warehouse.

For example, if FROM_DATE_ETL is 2015/05/10 12:50:00, then all data with a timestamp after May 10 12:50 PM is extracted, transformed, and then loaded into the warehouse.

TO_DATE_ETL Specifies the ending date (in the format YYYY/MM/DD HH:MM:SS) until which data in the BRM source system is extracted, transformed, and then loaded into the Oracle Communications Data Model warehouse.

For example, if TO_DATE_ETL is 2015/05/11 13:00:00, then all data with a timestamp before May 11 1:00 PM is extracted, transformed, and then loaded into the warehouse.

Note: If TO_DATE_ETL is null, the BRM Adapter sets the date to the source system date, which is useful in an incremental load.

LOAD_DATE Specifies the date (in the format YYYY/MM/DD HH:MM:SS) on which the load process is run.

Usually, this value is the system date.

SUCC_IND Indicates whether the load process was successful.

Y = Load process was successful.

N = Load process was not successful.

This value is set to N for the initial load. Do not change this value.

SPLIT_INTERVAL Specifies the intermediate commit interval for a huge batch update. This value is specified in minutes.

See "Using Intermediate Commits for Huge Batch Updates".

PROCESS_TYPE Specifies the load process type:

■ USAGE-EVENTS: Loads usage data.

■ BILLING-INVOICE: Loads usage and billing data.

■ PAYMENT-DATA: Loads usage, billing, and payment data.

■ COLLECTION-DATA: Loads usage, billing, payment, and collection data.

Do not change these values.

Table 2–1 (Cont.) Data Load Parameters

XML Element Description



where file_path is the directory in which the dwc_log_retention.xml file is located.

5. Using Oracle Data Integrator Studio, load the data load parameter values:

a. Navigate to the Designer navigator.

b. Expand the BRM-OCDM project folder, then the CONFIG folder, and then the Packages folder.

c. Select and run the XML_LOAD_CONFIG package, which loads the data load parameter values from the dwc_log_retention.xml file into the BRM_ETL_PARAMETER table in the BRM_STG schema.

6. (Optional) Configure email notification. See "Configuring the BRM Adapter to Send Email Alert Notifications".

7. Using Oracle Data Integrator Studio, run the packages to populate the foundation layer. You can choose to load the data to the foundation layer or to load the data to the staging layer and then to the foundation layer.

Do one of the following:

■ Load the BRM source data to the foundation layer (source to staging layer to foundation layer):


b. Expand the BRM-OCDM project folder, then the STG_OCDM folder, and then the Packages folder.

c. Select and run the COLLECTION_DATA_BULKLOAD package, which populates the foundation layer of Oracle Communications Data Model with the BRM source data.

If you encounter an error at the mapping level during the load process, you will need to correct the data errors and then run the COLLECTION_DATA_BULKLOAD package again. See "Restarting a Data Load Process After a Package Execution Fails".

After the initial load has finished, the BRM Adapter automatically updates the date values in the BRM_ETL_PARAMETER table for incremental load-ing as follows:

UPDATE BRM_ETL_PARAMETER SET FROM_DATE_ETL = TO_DATE_ETL, TO_DATE_ETL = NULL, WHERE PROCESS_NAME =’BRM-ADAPTER’ AND PROCESS_TYPE = process_type;

where process_type is USAGE-EVENTS, BILLING-INVOICE, PAY-MENT-DATA, or COLLECTION-DATA.

■ Load the BRM source data to the staging layer and then to the foundation layer:

a. Expand the BRM-OCDM project folder, then the SRC_STG_NONGG folder, and then the Procedures folder.

b. Select and run the ETL_DATE_PARAMETER_SPLITTING_BILLING_INVOICE Version 001 scenario for the ETL_DATE_PARAMETER_SPLITTING_BILLING_INVOICE procedure.

c. Select and run the ETL_DATE_PARAMETER_SPLITTING_COLLECTION_DATA Version 001 scenario for the ETL_DATE_PARAMETER_SPLITTING_COLLECTION_DATA procedure.

Refreshing the Foundation Layer of the Oracle Communications Data Model Warehouse


d. Select and run the ETL_DATE_PARAMETER_SPLITTING_PAYMENT_DATA Version 001 scenario for the ETL_DATE_PARAMETER_SPLITTING_PAYMENT_DATA procedure.

e. Select and run the ETL_DATE_PARAMETER_SPLITTING_USAGE_EVENTS Version 001 scenario for the ETL_DATE_PARAMETER_SPLITTING_USAGE_EVENTS procedure.

f. Expand the SRC_STG_NONGG folder and then the Packages folder.

g. Select and run the SRC_STG_LOAD package, which populates the staging layer of Oracle Communications Data Model with the BRM source data.

If you encounter an error at the mapping level during the load process, you will need to correct the data errors and then run the SRC_STG_LOAD package again. See "Restarting a Data Load Process After a Package Exe-cution Fails".

h. Expand the STG_OCDM folder and then the Packages folder.

i. Select and run the STG_OCDM_LOAD package, which populates the foundation layer of the Oracle Communications Data Model warehouse with the data from the staging layer.

If you encounter an error at the mapping level during the load process, you will need to correct the data errors and then run the STG_OCDM_LOAD package again. See "Restarting a Data Load Process After a Pack-age Execution Fails".

After the initial load is finished, the BRM Adapter updates the date val-ues in the BRM_ETL_PARAMETER table for incremental loading as fol-lows:

UPDATE BRM_ETL_PARAMETER SET FROM_DATE_ETL = TO_DATE_ETL, TO_DATE_ETL = NULL, WHERE PROCESS_NAME =’BRM-ADAPTER’ AND PROCESS_TYPE = process_type;

where process_type is USAGE-EVENTS, BILLING-INVOICE, PAY-MENT-DATA, or COLLECTION-DATA.

For more information about the packages, see "BRM Adapter Reference".


After you perform an initial load of the foundation layer in the Oracle Communications Data Model warehouse, you need to refresh or update the data in the warehouse with the new data from your BRM source system. In a common business scenario; for example, usage occurs daily and billing occurs monthly. In this case, you refresh the usage data daily and refresh the billing and invoicing data monthly.

See "Execution Flow Using the BRM Adapter with Only Oracle Data Integrator" for an explanation of the execution flow.

To refresh the data in the warehouse, use one of the following methods:

■ Refreshing the Foundation Layer on a Scheduled Basis

Note: You must examine E$_{OCDM Table} for any records rejected during staging. These tables are truncated after every load.



■ Refreshing the Foundation Layer with Real-Time Data Using Oracle GoldenGate

■ Manually Refreshing the Foundation Layer

Refreshing the Foundation Layer on a Scheduled BasisYou can schedule the data loads to automate the data refresh.

To schedule the data load, use one of the following methods:

■ From the UNIX or Windows command line. See "Scheduling Data Loads with the Oracle Data Integrator Built-In Scheduler from a Command Line".

■ From a Web Service. See "Scheduling Data Loads with the Oracle Data Integrator Built-In Scheduler from a Web Service".

■ From Oracle Data Integrator Studio. See Oracle Fusion Middleware Developer’s Guide for Oracle Data Integrator.

Scheduling Data Loads with the Oracle Data Integrator Built-In Scheduler from a Command LineTo schedule the data loads with the Oracle Data Integrator built-in Scheduler from a command line:

1. Verify the Oracle Data Integrator Standalone Agent is running.

See Oracle Fusion Middleware Installation Guide for Oracle Data Integrator for information about configuring and starting the Standalone Agent.

2. Run one of the following commands to schedule the data load (see Table 2–2 for a description of the parameters):

■ On UNIX, run the following:

./startscen.sh scenario_name scenario_version context_code [log_level] [-AGENT_URL=remote_agent_url] [-NAME=local_agent_name] [-SESSION_NAME=session_name] [-KEYWORDS=keywords] [variable=value]*

■ On Windows, run the following:

startscen.bat scenario_name scenario_version context_code [log_level] [-AGENT_URL=remote_agent_url] ["-NAME=local_agent_name"] ["-SESSION_NAME=session_name"] ["-KEYWORDS=keywords"] ["variable=value"]*

Table 2–2 Parameters for Scheduling a Scenario from a Command Line

Parameter Description

scenario_name Name of the scenario you want to schedule.

For example, END_TO_END_LOAD_PLAN_USAGE_EVENTS.

scenario_version Version of the scenario.

context_code Context into which the scenario is started.

log_level Level of logging information to retain.

remote_agent_url URL for the remote agent running the scenario.

local_agent_name Name of the local agent running the scenario.

session_name Name of the session to appear in the session log.

keywords Comma-separated list of keywords attached to the session.



For more information about scheduling scenarios from a command line, see the discussion about running integration processes in Oracle Fusion Middleware Developer’s Guide for Oracle Data Integrator.

After the scenario is scheduled, Oracle Data Integrator automatically runs the scenario at the scheduled times.

Scheduling Data Loads with the Oracle Data Integrator Built-In Scheduler from a Web ServiceTo schedule the data loads with the Oracle Data Integrator built-in Scheduler from a Web Service:

1. From the Oracle Data Integrator Studio Designer navigator, expand the BRM-OCDM project folder, then the STG_OCDM folder, and then the Packages folder.

2. Open the package you want to schedule.

For example, END_TO_END_LOAD_PLAN_USAGE_EVENTS.

3. From the Package Toolbox, in the Internet folder, double-click OdiInvokeWebService.

4. Click HTTP Analyzer.

The Credentials dialog box appears.

5. In the WSDL URL field, enter http://hostname:20910/oraclediagent/OdiInvoke?wsdl where hostname is the IP address of the Web service.

6. From the Operations list, select InvokeStartScen(,).

7. In the Credentials section, do the following:

a. In the OdiUser: string field, enter SUPERVISOR.

b. In the OdiPassword: string field, enter sunopsis.

c. In the workRepository: string field, enter WORKREP1.

8. In the Request section, do the following:

a. In the ScenarioName: string field, enter the name of the scenario for the package.

b. In the ScenarioVersion: string field, enter the version number of the scenario.

c. In the Context: string field, enter Global.

9. Click Send Request.

10. Click OK.

After the scenario is scheduled, Oracle Data Integrator automatically runs the scenario at the scheduled times.

variable Variable used in the session.

value Value assigned to the variable.

Table 2–2 (Cont.) Parameters for Scheduling a Scenario from a Command Line




For more information about scheduling scenarios from a Web Service, see the discussion about running integration processes in Oracle Fusion Middleware Developer’s Guide for Oracle Data Integrator.

Refreshing the Foundation Layer with Real-Time Data Using Oracle GoldenGateAfter performing an initial load of the Oracle Communications Data Model warehouse, you can refresh the data in the foundation layer of an Oracle Communications Data Model warehouse on a real-time basis using Oracle Data Integrator and Oracle GoldenGate.

See "Execution Flow Using the BRM Adapter with Oracle Data Integrator and Oracle GoldenGate" for an explanation of the execution flow.

To refresh the data in the foundation layer of an Oracle Communications Data Model warehouse with real-time data:

1. Configure the BRM Adapter for use by both Oracle GoldenGate and Oracle Data Integrator as described in Oracle Communications Data Model Adapters and Analytics Installation Guide.

2. Verify that the installation and configuration created the schema objects described in "Schema Definitions Added by the BRM Adapter".

3. From the GGSCI prompt, run info all command to verify that the Oracle GoldenGate processes needed by the BRM Adapter in the source and staging systems are in the RUNNING status.

Table 2–3 lists the Oracle GoldenGate processes on the source and staging systems.

The following example shows the command on the source system and successful results:

GGSCI> (mypc1) 5> info all

Program Status Group Lag Time Since Chkpt

MANAGER RUNNINGEXTRACT RUNNING EXTBRM 47:29:00 00:00:20EXTRACT RUNNING EXTPBRM 00:00:00 47:29:06

The following example shows the command on the staging system and successful results:

GGSCI> (ocdm01) 2> info all


MANAGER RUNNINGREPLICAT RUNNING REPBRM 00:00:00 00:03:09

Table 2–3 Oracle GoldenGate Processes

Source System Processes Staging System Processes

■ Manager process

■ Extract process (EXTBRM)

■ Extract Pump process (EXTPBRM)

■ Manager process

■ Replicate process (REPBRM)



4. Reconfigure the BRM_SRC physical data server to point to the Oracle GoldenGate target tables.

The Oracle GoldenGate target tables are maintained with the BRM_STG schema. You can reconfigure BRM_SRC data server to point to Oracle GoldenGate target tables (the BRM_STG schema). See Oracle Communications Data Model Adapters and Analytics Installation Guide for more information.

5. Using Oracle Data Integrator Studio, do the following:


b. Expand the BRM-OCDM project folder and then the STG_OCDM folder.

c. Select and run the package for the data that you want to update:

* To load usage data, select and run END_TO_END_LOAD_PLAN_USAGE_EVENTS package.

* To load usage and billing data, select and run END_TO_END_LOAD_PLAN_BILLING_INVOICE package.

* To load usage, billing, and payment data, select and run END_TO_END_LOAD_PLAN_PAYMENT_DATA package.

* To load usage, billing, payment, and collection data, select and run END_TO_END_COLLECTION_DATA package.

For more information about these packages, see "BRM Adapter Reference".

Manually Refreshing the Foundation LayerTo manually refresh the data in the foundation layer, do the following:

1. Update the data load parameter values, if required. See "Updating the Data Load Parameters".

2. Update the users for email notification, if required. See "Configuring the BRM Adapter to Send Email Alert Notifications".



b. Expand the BRM-OCDM project folder, and then the STG_OCDM folder.

c. Select and run the package for the data that you want to update:

* To load usage data, select and run END_TO_END_LOAD_PLAN_USAGE_EVENTS package.

* To load usage and billing data, select and run END_TO_END_LOAD_PLAN_BILLING_INVOICE package.

Tip: If you have two source systems, check the process status on both. For commands to manage Oracle GoldenGate processes, see Oracle Communications Data Model Adapters and Analytics Installation Guide.

Note: You can schedule each of these packages to run periodically using Oracle Data Integrator. See "Refreshing the Foundation Layer on a Scheduled Basis".

Administering BRM Adapter Data Load Processes


* To load usage, billing, and payment data, select and run END_TO_END_LOAD_PLAN_PAYMENT_DATA package.

* To load usage, billing, payment, and collection data, select and run END_TO_END_COLLECTION_DATA package.

For more information about these packages, see "BRM Adapter Reference".

Administering BRM Adapter Data Load ProcessesTo administer the BRM Adapter data load processes, you perform the following system administration tasks:

■ Configuring the BRM Adapter for Populating Oracle Communications Data Model Warehouse

■ Managing and Monitoring BRM Adapter Data Load Processes

Configuring the BRM Adapter for Populating Oracle Communications Data Model Warehouse

The following sections describe how to configure the BRM Adapter for populating the foundation layer of the Oracle Communications Data Model warehouse.

Updating the Data Load ParametersYou can update the data load parameter values manually, only if required. For example, to re-run a package that failed, you may need to update the dates to use the previous dates.

You can update the data load parameters in two ways:

■ Updating the Data Load Parameters in the XML Configuration File

■ Updating the Data Load Parameters in the BRM_ETL_PARAMETER Table

Updating the Data Load Parameters in the XML Configuration FileTo update only the split interval data load parameter for intermediate commits, see "Setting the Intermediate Commit Interval".

To update the data load date parameters in the XML configuration file:

1. Open the dwc_log_retention.xml file using an XML editor or text editor.

2. Edit the date values (see Table 2–1).

3. Save and close the file.



b. Expand the BRM-OCDM project folder, then the CONFIG folder, and then the Packages folder.

Note: Because the data load date values are maintained by the BRM Adapter for incremental loads, manually updating the dates might lead to loss of data.



c. Select and run the XML_LOAD_CONFIG package, which loads the data load parameter values from the dwc_log_retention.xml file into the BRM_ETL_PARAMETER table in the BRM_STG schema.

Updating the Data Load Parameters in the BRM_ETL_PARAMETER TableTo update only the split interval data load parameter for intermediate commits, see "Setting the Intermediate Commit Interval".

To update the data load date parameters in the BRM_ETL_PARAMETER table:

1. Using SQL Developer, connect to the BRM_STG schema.

2. Run the update query.

For example, the following query updates the FROM_DATE_ETL for the USAGE-EVENTS load process.

UPDATE BRM_ETL_PARAMETER SET FROM_DATE_ETL='01-Dec-2015' WHERE PROCESS_TYPE='USAGE-EVENTS’;COMMIT;

Setting the Intermediate Commit IntervalTo set the intermediate commit interval:


2. Run the following query.

UPDATE BRM_ETL_PARAMETER SET SPLIT_INTERVAL=split_interval WHERE PROCESS_TYPE=’process_type’;COMMIT;

where:

■ split_interval determines the time interval used to extract and load the BRM source data to the Oracle Communications Data Model warehouse. This value is specified in minutes.

For example, if this value is 360 (6 hours), the BRM Adapter extracts and loads the BRM source data in the following order:

– Data with a timestamp from midnight to 6 AM

– Data with a timestamp from 6 AM to 12 PM

– Data with a timestamp from 12 PM to 6 PM

– Data with a timestamp from 6 PM to midnight

To disable intermediate commits, set this value to 1440, which indicates no intermediate commits within a 24-hour interval.

■ process_type is one of the following:

– USAGE-EVENTS: Loads usage data.

– BILLING-INVOICE: Loads usage and billing data.

– PAYMENT-DATA: Loads usage, billing, and payment data.

– COLLECTION-DATA: Load usage, billing, payment, and collection data.

For more information about using intermediate commits, see "Using Intermediate Commits for Huge Batch Updates".



Configuring the BRM Adapter to Send Email Alert NotificationsTo configure the BRM Adapter to send email alert notifications:

1. Copy the sample XML template below into an XML editor or text editor.

<?xml version="1.0" ?><!DOCTYPE main [

<!ELEMENT main (DATA_RECORD*)><!ELEMENT DATA_RECORD (MAIL_SERVER?,PORT?,FROM1?,TO1?,CC?)+><!ELEMENT MAIL_SERVER (#PCDATA)><!ELEMENT PORT (#PCDATA)><!ELEMENT FROM1 (#PCDATA)><!ELEMENT TO1 (#PCDATA)><!ELEMENT CC (#PCDATA)>

]><main>

<DATA_RECORD><MAIL_SERVER>ip_address</MAIL_SERVER><PORT>port_number</PORT><FROM1>from_user</FROM1><TO1>to_user1,to_user2</TO1><CC>cc_user</CC>

</DATA_RECORD></main>

2. Edit the values of the child elements in the <DATA_RECORD> element.

Table 2–4 describes the child elements.

3. Save the file as mail_config.xml.


5. Run the following query, which adds the location of the mail_config.xml file to the XML_FILEPATH table.

insert into BRM_STG.XML_FILEPATH (XML_TYPE, XML_FILEPATH) values (’MAIL_CONFIG’, ’/file_path/mail_config.xml’);commit;

where file_path is the directory in which the mail_config.xml file is located.

When you run a package, the BRM Adapter locates the configuration file using the information in the XML_FILEPATH table and loads the email details from the file into a database table.

Updating the Email Alert Notification Configurations To update the email alert notification configurations:

1. Open the mail_config.xml file using an XML editor or text editor.

Table 2–4 Email Configuration Parameters


ip_address The IP address of the SMTP mail server.

port_number The port number for the mail server.

from_user The email address from which to send the notification.

to_user The email addresses of the users to send the notification to.

cc_user The email addresses of the users to copy on the notification.



2. Edit the configuration values (see Table 2–4).

3. Save and close the file.

Configuring Parallel LoadingTo configure parallel loading:

1. Using Oracle Data Integrator Studio, navigate to the Designer navigator.

2. Expand the BRM-OCDM project folder.

3. Do one of the following:

■ To configure parallel loading for the staging layer tables, expand the SRC_STG_NONGG folder.

■ To configure parallel loading for the Oracle Communications Data Model foundation layer tables, expand the STG_OCDM folder.

4. In the Mappings folder, open the mapping for which you want to enable parallel loading.

5. In the physical design, select the target table.

6. From the Window menu, select Properties.

The Property Inspector displays.

7. In the Property Inspector, do one of the following:

■ For source-to-staging-layer loading, select the Loading Knowledge Module tab.

■ For staging-layer-to-target-table loading, select the Integration Knowledge Module tab.

8. In the Options tab, enter a value for SELECT_HINT using the following syntax:

/*+PARALLEL(target_table,number_of_ports)*/

where:

■ target_table is the name of the target table.

■ number_of_ports is the number of parallel ports on the database server. Consult your database administrator about the number of parallel ports that is supported on the database server.

For example:

/*PARALLEL(ACCOUNT_NAMEINFO_T_D,4)*/



Managing and Monitoring BRM Adapter Data Load ProcessesThe following sections describe how you can manage and monitor the BRM Adapter data load processes.

Using Oracle Data Integrator Web Console to Manage and Monitor Data Load ProcessUse the Oracle Data Integrator Web Console to manage and to monitor the BRM data load processes.

From the Runtime tab (see Figure 2–1), you can select and run the BRM scenarios.



Figure 2–1 RunTime Tab in Oracle Data Integrator Web Console

From the Sessions tab (see Figure 2–2), you can view the results of any data load session.

Figure 2–2 Sessions Tab in Oracle Data Integrator Web Console

For more information about using the Oracle Data Integrator Web Console, see Oracle Fusion Middleware Developer’s Guide for Oracle Data Integrator.

Displaying Your Brand Logo on the User InterfaceTo display your brand logo on the Oracle Data Integrator Web Console user interface:

1. Go to the ODI_Home directory, where ODI_Home is the directory in which Oracle Data Integrator Studio is installed.

2. Change to the /odi/studio/bin directory.



The directory contains the file logo.jpg.

3. Rename the existing logo.jpg file to another name. For example, logo_odi.jpg.

4. Copy your brand logo file to the /odi/studio/bin directory.

5. Rename your brand logo file to logo.jpg.

Monitoring a Huge Batch UpdateTo monitor a huge batch update:

1. From SQL Developer, connect to the BRM_STG schema.

2. In the Connections navigator, expand BRM_STG.

3. Select the BRM_ETL_TIME_SPLIT_PARAMETER table, which displays the table definition.

4. Click the Data tab, which displays the data.

The SUB_PROCESS_ID column indicates the number of batches. A Y value in the SUCC_IND column indicates the batch update has been completed.

Using Oracle Database In-Memory Column Store to Improve Database Operations PerformanceThe Oracle Database in-memory column store enables database tables to be stored in memory in a columnar format rather than the traditional row format. Data populated in the tables is optimized for analytical processing. For more information about the in-memory column store, see Oracle Database 12c Release 1 (12.1.0.2) Database Administrator's Guide.

You can use the in-memory column store to enable tables with performance-critical data to be stored in memory and improve performance of the database operations performed on the tables.

For example, you could enable the DD_OBJECT_MAP and DWC_ETL_MATRIX_OCDMLKUP_MATCH tables to be stored in the in-memory column store to improve performance for those queries that select a small number of columns from the table.

To enable a table to be stored in the in-memory column store:

Note:

■ The in-memory column store is available starting with Oracle Database 12c Release 1 (12.1.0.2).

■ The in-memory column store is a separately licensed option of Oracle Database Enterprise Edition.



1. Ensure that the in-memory column store is enabled for the database.

For information about enabling the in-memory column store for a database, see Oracle Database 12c Release 1 (12.1.0.2) Database Administrator's Guide.

2. Ensure that the size of the in-memory area is large enough to accommodate all of the database objects you want to store in the in-memory column store.

Ensure the amount of memory currently allocated for the in-memory area by entering the following command in SQL*Plus:

SHOW PARAMETER INMEMORY_SIZE;

Consult with your database administrator about how much memory can be allocated to the in-memory area.

3. Using SQL*Plus, connect to the BRM_STG schema as user SYSDBA.

4. Run the following statement:

ALTER TABLE table_name INMEMORY;

where table_name is the table to be stored the in-memory column store.

For example:

ALTER TABLE DWC_ETL_MATRIX_OCDMLKUP_MATCH INMEMORY;

You can also specify a priority level that determines the priority of the table in the population queue.

The following example enables the DWC_ETL_MATRIX_OCDMLKUP_MATCH table for the in-memory column store and specifies PRIORITY CRITICAL for populating the table data in memory:

ALTER TABLE DWC_ETL_MATRIX_OCDMLKUP_MATCH INMEMORY PRIORITY CRITICAL;

This example populates the DWC_ETL_MATRIX_OCDMLKUP_MATCH table in the in-memory column store before database objects with priority levels NONE, LOW, MEDIUM or HIGH.

For more information about using the in-memory column store, see Oracle Database 12c Release 1 (12.1.0.2) Database Administrator's Guide.

Restarting a Data Load Process After a Package Execution FailsIf you encounter an error at the mapping level during a package execution, fix the data error and then restart the data load process.

To restart a data load process after a package execution fails, do the following:

1. From Oracle Data Integrator Studio Operator navigator, identify the package and the mapping where the error occurred.

For more information about using the Operator navigator to view package execution results, see Oracle Fusion Middleware Developer’s Guide for Oracle Data Integrator.

2. Analyze the error and resolve the problem with the data. See "BRM Adapter Exception Handling".

3. From SQL Developer, do one of the following:

■ If the package execution error occurred during the source-to-staging-layer data load process, run the following query:



UPDATE BRM_EXEC_STAT SET EXEC_STAT=’CLOSED’ WHERE PROC_TYP=’SRC_STG’;

■ If the package execution error occurred during the staging-to-foundation-layer data load process, run the following query:

UPDATE BRM_EXEC_STAT SET EXEC_STAT=’CLOSED’ WHERE PROC_TYP=’STG_OCDM’;

The BRM Adapter does not allow to run a package if a load process is in the RUNNING or COMPLETED state.

The load process status is set to RUNNING when the packages are run. The status is set to COMPLETED after the package executions have completed successfully.

4. From the Oracle Data Integrator Studio Designer navigator, run the package that failed previously.

For example, if the END_TO_END_LOAD_PLAN_USAGE package failed previously, you would run this package again. Oracle Data Integrator restarts the data load from where it failed previously.

BRM Adapter Exception HandlingException handling is provided within the SRC_STG_LOAD and STG_OCDM_LOAD packages. All interfaces and procedures are provided with an exception-handling procedure. If any exception occurs, the exception-handling procedure is executed. The exception-handling procedure checks the exception-handling configuration and proceeds accordingly.

Figure 2–3 shows the exception handler operator log.

Figure 2–3 BRM Adapter Exception Handler Operator Log

Exception Handler ConfigurationException handling is configured for each step within the package, not for each interface or procedure. In most cases, interfaces and procedures can have the same name as the step name. Open the respective packages and click the particular step to look for the step name, as shown in Figure 2–4.



Figure 2–4 Finding Step Names for Exception Handling

Alternatively, you can find the step name in the exception handler log:

ODI-1228: Task PROCESS_ERROR_HANDLING (Procedure) fails on the target ORACLE connection BRM_STGCaused By: java.sql.SQLException: ORA-20001:Error occurred while processing DWR_ACCT_MAP, fix the error in interface or make entry into brm_stg (brm_odi_exception_handle) table, if you wish to skip this error

To skip an exception means do not stop the execution and proceed with the next step. You can run the following insert query in the BRM_STG schema:

insert into brm_odi_exception_handle ( interface_name, execution_context, skip_exception ) values ( 'name', 'context', 'skip' )

where

■ name is the step name.

■ context is the execution context; default is GLOBAL.

■ skip is Y to skip the execution and continue with the next step, or N to not skip the exception and raise an error.

For example:

insert into brm_odi_exception_handle ( interface_name, execution_context, skip_exception ) values ( 'DWR_ACCT_MAP', 'GLOBAL', 'Y' )



Table 2–5 Package and Step Name Mapping

Package Folder Step Name

100 - LOOKUP STG_OCDM DWB_CRNCY_EXCHNG_RATE_MAP

100 - LOOKUP STG_OCDM DWL_ACCT_BAL_TYP_MAP

100 - LOOKUP STG_OCDM DWL_CALL_SRVC_TYP_MAP

100 - LOOKUP STG_OCDM DWL_COLLCTN_TYP_MAP

100 - LOOKUP STG_OCDM DWL_CRNCY_MAP

100 - LOOKUP STG_OCDM DWL_CUST_TYP_MAP

100 - LOOKUP STG_OCDM DWL_PK_OFPK_TIME_MAP

100 - LOOKUP STG_OCDM DWL_PROD_SPEC_TYP_MAP

200 - CUSTOMER_PKG STG_OCDM exec_geo_map

200 - CUSTOMER_PKG STG_OCDM DWR_PRTY_MAP

200 - CUSTOMER_PKG STG_OCDM DWR_CUST_MAP

200 - CUSTOMER_PKG STG_OCDM DWR_CUST_ADDR_MAP

200 - CUSTOMER_PKG STG_OCDM DWR_PRTY_CNCT_INFO_MAP

200 - CUSTOMER_PKG STG_OCDM DWR_PRTY_MAP (Payinfo_CC)

200 - CUSTOMER_PKG STG_OCDM DWR_PRTY_MAP (Payinfo_DD)

200 - CUSTOMER_PKG STG_OCDM DWR_PRTY_MAP (Payinfo_INV)

200 - CUSTOMER_PKG STG_OCDM UPDATE_DWR_PRTY.CUST_KEY

300 - ACCOUNT_PKG STG_OCDM DWR_ACCT_SGMNT

300 - ACCOUNT_PKG STG_OCDM DWR_ACCT_MAP

300 - ACCOUNT_PKG STG_OCDM DWR_ACCT_BAL_GRP_MAP

300 - ACCOUNT_PKG STG_OCDM DWR_ACCT_PREF_INVC_DLVRY_MAP

300 - ACCOUNT_PKG STG_OCDM DWR_ACCT_PYMT_MTHD_MAP

400 - SERVICE_PKG STG_OCDM DWR_SRVC_MAP

400 - SERVICE_PKG STG_OCDM DWR_SRVC_SPEC_MAP

400 - SERVICE_PKG STG_OCDM DWR_CUST_FCNG_SRVC_MAP

500 - PRODUCT_PKG STG_OCDM DWR_PROD_SPEC_MAP (PRODUCT_T)

500 - PRODUCT_PKG STG_OCDM DWR_PROD_OFR_MAP

500 - PRODUCT_PKG STG_OCDM DWR_PROD_SBRP_MAP

500 - PRODUCT_PKG STG_OCDM DWR_PROD_OFR_PROD_SPEC_ASGN_MAP

500 - PRODUCT_PKG STG_OCDM DWR_PROD_CTLG_MAP

500 - PRODUCT_PKG STG_OCDM DWR_PROD_CTLG_PROD_OFR_ASGN_MAP

500 - PRODUCT_PKG STG_OCDM DWR_SRVC_SPEC_PROD_SPEC_RLTN_MAP

500 - PRODUCT_PKG STG_OCDM UPDATE_PROD_OFR_PLN_TYP

500 - PRODUCT_PKG STG_OCDM DWR_AGRMNT_MAP

500 - PRODUCT_PKG STG_OCDM DWR_VAL_ADD_SRVC_MAP

500 - PRODUCT_PKG STG_OCDM DWR_AGRMNT_ITEM_MAP

500 - PRODUCT_PKG STG_OCDM DWR_PROD_OFR_PRICE_MAP

600 - ACCOUNT_BALANCE_PKG STG_OCDM DWB_ACCT_BAL_MAP

600 - ACCOUNT_BALANCE_PKG STG_OCDM DWB_ACCT_BAL_IMPC_MAP

700 - INVOICE_PKG STG_OCDM DWB_INVC_MAP

700 - INVOICE_PKG STG_OCDM DWB_INVC_ITEM_MAP

700 - INVOICE_PKG STG_OCDM DWB_INVC_ADJ_MAP



700 - INVOICE_PKG STG_OCDM DWB_INVC_DISC_MAP

700 - INVOICE_PKG STG_OCDM exec_update_invc

800 - COLLECTIONS STG_OCDM DWB_ACCT_DEBT_MAP

800 - PAYMENT_PKG STG_OCDM DWB_ACCT_PYMT_MAP

800 - PAYMENT_PKG STG_OCDM payment assign view

800 - PAYMENT_PKG STG_OCDM DWB_INVC_PYMT_ASGN_MAP

800 - PAYMENT_PKG STG_OCDM update dwb_invc.FULL_PAY_RCVD_IND

10000 - BROADBAND_USAGE_EVENT_PKG STG_OCDM DWB_BRDBND_USG_EVT_MAP

10000 - DATA_SERVICE_EVENT_PKG STG_OCDM DWB_DATA_SRVC_EVT_MAP (DIALUP)

10000 - DATA_SERVICE_EVENT_PKG STG_OCDM DWB_DATA_SRVC_EVT_MAP (GSM POSTPAID)

10000 - DATA_SERVICE_EVENT_PKG STG_OCDM DWB_DATA_SRVC_EVT_MAP (GSM PREPAID)

10000 - GPRS_USAGE_EVENT_PKG STG_OCDM DWB_GPRS_USG_EVT_MAP (PostPaid)

10000 - GPRS_USAGE_EVENT_PKG STG_OCDM DWB_GPRS_USG_EVT_MAP (PrePaid)

10000 - SMS_EVENT_PKG STG_OCDM DWB_SMS_EVT_MAP (PostPaid)

10000 - SMS_EVENT_PKG STG_OCDM DWB_SMS_EVT_MAP (PrePaid)

10000 - VOICE_CALL_EVENT_PKG STG_OCDM DWB_WRLS_CALL_EVT_MAP(PostPaid)

10000 - VOICE_CALL_EVENT_PKG STG_OCDM DWB_WRLS_CALL_EVT_MAP (PrePaid)

ACCOUNT_PKG SRC_STG_NONGG ACCOUNT_T_NONGG_IU

ACCOUNT_PKG SRC_STG_NONGG ACCOUNT_NAMEINFO_T_NONGG_IU

ACCOUNT_PKG SRC_STG_NONGG BILLINFO_T_NONGG_IU

BAL_GRP_PKG SRC_STG_NONGG BAL_GRP_T_NONGG_IU

BAL_GRP_PKG SRC_STG_NONGG BAL_GRP_BALS_T_NONOGG_IU

BAL_GRP_PKG SRC_STG_NONGG BAL_GRP_SUB_BALS_T_NONOGG_IU

COLLECTION_PKG SRC_STG_NONGG COLLECTIONS_SCENARIO_T_NONOGG_IU

COLLECTION_PKG SRC_STG_NONGG COLLECTIONS_ACTION_T_NONOGG_IU

CONFIG_PKG SRC_STG_NONGG CONFIG_BEID_BALANCES_T_NONGG_IU

CONFIG_PKG SRC_STG_NONGG CONFIG_BUSINESS_TYPE_T_NONGG_IU

CONFIG_PKG SRC_STG_NONGG CONFIG_CUR_CONV_RATES_T_NONGG_IU

CONFIG_PKG SRC_STG_NONGG CONFIG_PAYMENT_PAY_TYPES_T_NONGG_IU

CONFIG_PKG SRC_STG_NONGG CONFIG_T_NONGG_IU

CONFIG_PKG SRC_STG_NONGG CONFIG_COLLECTIONS_SCENARIO_T_NONOGG_IU

CONFIG_PKG SRC_STG_NONGG CONFIG_BILLING_SEGMENT_T_NOOGG_IU

DD_OBJECTS_PKG SRC_STG_NONGG DD_OBJECTS_T_NONGG_IU

EVENT_ACTIVITY_TLCS_PKG SRC_STG_NONGG EVENT_ACTIVITY_TLCS_T_NONGG_IU

EVENT_ACTIVITY_TLCS_PKG SRC_STG_NONGG EVENT_ACTV_TLCS_SVC_CODES_T_NONGG_IU

EVENT_BAL_IMPACT_PKG SRC_STG_NONGG EVENT_BAL_IMPACTS_T_NONGG_IU

EVENT_BILLING_PKG SRC_STG_NONGG EVENT_BILLING_MISC_T_NONGG_IU

EVENT_BILLING_PKG SRC_STG_NONGG EVENT_BILLING_PAYMENT_CASH_T_NONGG_IU

EVENT_BILLING_PKG SRC_STG_NONGG EVENT_BILLING_PAYMENT_CC_T_NONGG_IU

EVENT_BILLING_PKG SRC_STG_NONGG EVENT_BILLING_PAYMENT_CHECK_T_NONGG_IU

EVENT_BILLING_PKG SRC_STG_NONGG EVENT_BILLING_PAYMENT_DD_T_NONGG_IU

EVENT_BILLING_PKG SRC_STG_NONGG EVENT_BILLING_PAYMENT_FAILED_T_NONGG_IU

Table 2–5 (Cont.) Package and Step Name Mapping




EVENT_BILLING_PKG SRC_STG_NONGG EVENT_BILLING_PAYMENT_PAYORD_T_NONGG_IU

EVENT_BILLING_PKG SRC_STG_NONGG EVENT_BILLING_PAYMENT_POST_T_NONGG_IU

EVENT_BILLING_PKG SRC_STG_NONGG EVENT_BILLING_PAYMENT_T_NONGG_IU

EVENT_BILLING_PKG SRC_STG_NONGG EVENT_BILLING_PAYMENT_WTRAN_T_NONGG_IU

EVENT_BROADBAND_USAGE_PKG SRC_STG_NONGG EVENT_BROADBAND_USAGE_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG SRC_STG_NONGG EVENT_DLAY_ACTV_TLCS_SVC_CDS_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG SRC_STG_NONGG EVENT_DLAY_ACTV_TLCS_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG SRC_STG_NONGG EVENT_DLAY_SESS_TLCS_SVC_CDS_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG SRC_STG_NONGG EVENT_DLAY_SESS_TLCS_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG SRC_STG_NONGG EVENT_DLYD_SESSION_TLCO_GPRS_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG SRC_STG_NONGG EVENT_DLYD_SESSION_TLCO_GSM_T_NONGG_IU

EVENT_PKG SRC_STG_NONGG EVENT_T_NONGG_IU

EVENT_RUM_MAP_PKG SRC_STG_NONGG EVENT_RUM_MAP_T_NONGG_IU

EVENT_SESSION_PKG SRC_STG_NONGG EVENT_SESSION_DIALUP_T_NONGG_IU

EVENT_SESSION_PKG SRC_STG_NONGG EVENT_SESSION_TELCO_GPRS_T_NONGG_IU

EVENT_SESSION_PKG SRC_STG_NONGG EVENT_SESSION_TLCO_GSM_T_NONGG_IU

EVENT_SESSION_PKG SRC_STG_NONGG EVENT_SESSION_TLCS_T_NONGG_IU

EVENT_SESSION_PKG SRC_STG_NONGG EVENT_SESS_TLCS_SVC_CODES_T_NONGG_IU

EVENT_TAX_JURISDICTIONS_PKG SRC_STG_NONGG EVENT_TAX_JURISDICTIONS_T_NONGG_IU

IFW_CURR_TIMEZOZE_USAGETYPE_PKG SRC_STG_NONGG IFW_CURRENCY_NONGG_IU

IFW_CURR_TIMEZOZE_USAGETYPE_PKG SRC_STG_NONGG IFW_TIMEZONE_NONGG_IU

IFW_CURR_TIMEZOZE_USAGETYPE_PKG SRC_STG_NONGG IFW_USAGETYPE_NONGG_IU

INVOICE_ITEM_PKG SRC_STG_NONGG EVENT_ITEM_TRANSFER_T_NONGG_IU

INVOICE_ITEM_PKG SRC_STG_NONGG ITEM_T_NONGG_IU

INVOICE_ITEM_PKG SRC_STG_NONGG BILL_T_NONGG_IU

INVOICE_ITEM_PKG SRC_STG_NONGG INVOICE_T_NONGG_IU

INVOICE_ITEM_PKG SRC_STG_NONGG INVOICE_STATUSES_T_NONGG_IU

PAYINFO_PKG SRC_STG_NONGG PAYINFO_T_NONGG_IU

PAYINFO_PKG SRC_STG_NONGG PAYINFO_INV_T_NONGG_IU

PAYINFO_PKG SRC_STG_NONGG PAYINFO_DD_T_NONGG_IU

PAYINFO_PKG SRC_STG_NONGG PAYINFO_CC_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG SRC_STG_NONGG PRODUCT_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG SRC_STG_NONGG DEAL_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG SRC_STG_NONGG DEAL_PRODUCTS_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG SRC_STG_NONGG PLAN_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG SRC_STG_NONGG PLAN_SERVICES_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG SRC_STG_NONGG RATE_PLAN_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG SRC_STG_NONGG DISCOUNT_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG SRC_STG_NONGG PURCHASED_PRODUCT_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG SRC_STG_NONGG PURCHASED_DISCOUNT_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG SRC_STG_NONGG DEAL_DISCOUNTS_T_D_NONGG_IU

SERVICE_PKG SRC_STG_NONGG SERVICE_T_NONGG_IU





Drop Error Tables (E$_)You should drop the E$_{OCDM_SYS} tables from the OCDM_SYS schema. If the OCDM_SYS schema table changes, the load will fail. Review existing data in these tables before you drop them. You can review the data by running the following query:

SELECT * FROM USER_OBJECTS WHERE OBJECT_NAME LIKE 'E$_%' AND OBJECT_TYPE = 'TABLE';

Moving Data into History TablesThe BRM Adapter by default moves data into history tables. History table mapping is available in the BRM_MAPPING_TAB staging table. You can disable moving data into history tables by running the following query:

UPDATE BRM_MAPPING_TAB SET DELTA_HIST_TAB_NAME = NULL WHERE NORMAL_TAB_NAME = 'ACCOUNT_T';

This query disables the history only for the ACCOUNT_T source table. You can disable the moving of history data into all tables by removing the WHERE clause from the previous query.

If the BRM_MAPPING_TAB staging table lacks an entry for a history table, you can add one.

SERVICE_PKG SRC_STG_NONGG SERVICE_EMAIL_T_NONGG_IU

SERVICE_PKG SRC_STG_NONGG SERVICE_TELCO_FEATURES_T_NONGG_IU

SERVICE_PKG SRC_STG_NONGG SERVICE_TELCO_GPRS_T_NONGG_IU

SERVICE_PKG SRC_STG_NONGG SERVICE_TELCO_GSM_T_NONGG_IU

Note: The history table structure must be the same as the structure of the delta table.



3

BRM Adapter Reference 3-1

3BRM Adapter Reference

This chapter provides the following information about the Oracle Communications Billing and Revenue Management Adapter for Oracle Communications Data Model (the BRM Adapter):

■ Mapping of Oracle Communications Billing and Revenue Management (BRM) source tables to Oracle Communications Data Model target tables.

■ BRM Adapter Oracle Data Integrator project

■ Schema definitions added by the BRM Adapter

BRM Source and Oracle Communications Data Model Target TablesTable 3–1 shows the BRM source table and the Oracle Communications Data Model target table mapping.

Table 3–1 BRM Source to Oracle Communications Data Model Target Table Mapping

BRM Source Table Oracle Communications Data Model Target Table

CONFIG_T, CONFIG_BUSINESS_TYPE_T DWL_CUST_TYP

CONFIG_T,CONFIG_BEID_BALANCES_T DWL_ACCT_BAL_TYP

CONFIG_T, CONFIG_CUR_CONV_RATES_T DWB_CRNCY_EXCHNG_RATE

IFW_TIMEZONE DWL_PK_OFPK_TIME

IFW_CURRENCY DWL_CRNCY

DD_OBJECTS_T DWR_SRVC_SPEC

PRODUCT_T DWR_PROD, DWR_SRVC_SPEC_PROD_RLTN

DISCOUNT_T DWR_PROD, DWR_SRVC_SPEC_PROD_RLTN

RATE_PLAN_T DWR_PROD_RTNG_PLN

DEAL_T DWR_PROD

DEAL_PRODUCTS_T DWR_PROD_PKG_ASGN

PLAN_T DWR_PROD_MKT_PLN

PLAN_SERVICES_T DWR_PROD_MKT_PLN_ASGN

SERVICE_T DWR_SRVC, DWR_CUST_FCNG_SRVC, DWB_SRVC_STAT_HIST

SERVICE_T, SERVICE_TELCO_GSM_T DWR_CUST_FCNG_SRVC

SERVICE_T, SERVICE_TELCO_GPRS_T DWR_CUST_FCNG_SRVC

BRM Source and Oracle Communications Data Model Target Tables


SERVICE_T, SERVICE_EMAIL_T DWR_CUST_FCNG_SRVC

SERVICE_TELCO_FEATURES_T DWR_SRVC_CHTRSTC

ACCOUNT_T, ACCOUNT_NAMEINFO_T DWR_GEO_CNTRY, DWR_GEO_STATE, DWR_GEO_CITY, DWR_POSTCD, DWR_ADDR_LOC DWR_PRTY, DWR_PRTY_CNCT_INFO, DWR_CUST, DWR_ACCT, DWR_ACCT_PREF_INVC_DLVRY

BILLINFO_T DWR_PRTY, DWR_CUST, DWR_ACCT, DWL_PYMT_MTHD_TYP

BAL_GRP_T DWR_ACCT_BAL_GRP

PURCHASED_PRODUCT_T DWR_SBRP, DWR_SBRP_PRICE_CHRG

PURCHASED_DISCOUNT_T DWR_SBRP, DWR_SBRP_PRICE_CHRG

BILL_T DWB_INVC

INVOICE_T DWB_EVT_INVC_DLVRY

ITEM_T DWB_INVC_ITEM

PAYINFO_T, PAYINFO_INV_T DWR_GEO_CNTRY, DWR_GEO_STATE, DWR_GEO_CITY, DWR_POSTCD, DWR_ADDR_LOC, DWR_PRTY, DWR_ACCT_PREF_PYMT_MTHD

PAYINFO_T, PAYINFO_DD_T DWR_PRTY, DWR_ACCT_PREF_PYMT_MTHD

PAYINFO_T,PAYINFO_CC_T DWR_PRTY, DWR_ACCT_PREF_PYMT_MTHD

EVENT_T used in all "NETWORK Event" type of mapping

EVENT_BAL_IMPACTS_T used in all "NETWORK Event" type of mapping, DWB_NTWK_EVT_ACCT_BAL_IMPC (any events)

EVENT_SESSION_TLCS_T used in all Prepaid/session "NETWORK Event" type of mapping

EVENT_SESS_TLCS_SVC_CODES_T used in all Prepaid/session "NETWORK Event" type of mapping

EVENT_SESSION_TLCO_GSM_T DWB_WRLS_CALL_EVT (Prepaid)

EVENT_SESSION_TELCO_GPRS_T DWB_GPRS_USG_EVT (Prepaid)

EVENT_BROADBAND_USAGE_T DWB_BRDBND_USG_EVT

EVENT_SESSION_DIALUP_T DWB_DATA_SRVC_EVT

EVENT_DLAY_SESS_TLCS_T used in all Postpaid/session "NETWORK Event" type of mapping

EVENT_DLAY_SESS_TLCS_SVC_CDS_T used in all Postpaid/session "NETWORK Event" type of mapping

EVENT_DLYD_SESSION_TLCO_GPRS_T DWB_GPRS_USG_EVT (Postpaid)

EVENT_DLYD_SESSION_TLCO_GSM_T DWB_WRLS_CALL_EVT (Postpaid)

EVENT_ACTIVITY_TLCS_T used in all Prepaid Activity "NETWORK Event" type of mapping

EVENT_ACTV_TLCS_SVC_CODES_T used in all Prepaid Activity "NETWORK Event" type of mapping

EVENT_DLAY_ACTV_TLCS_SVC_CDS_T E_DLAY_ACT_TLCS_SVC_CDS_T_D

EVENT_DLAY_ACTV_TLCS_T EVENT_DLAY_ACTV_TLCS_T_D

Table 3–1 (Cont.) BRM Source to Oracle Communications Data Model Target Table Mapping


BRM Source and Oracle Communications Data Model Target Tables


EVENT_TAX_JURISDICTIONS_T EVENT_TAX_JURISDICTIONS_T_D

EVENT_RUM_MAP_T EVENT_RUM_MAP_T_D

EVENT_BILLING_PAYMENT_T DWB_ACCT_RCHRG

EVENT_BILLING_PAYMENT_DD_T DWB_ACCT_RCHRG

EVENT_BILLING_PAYMENT_CASH_T DWB_ACCT_RCHRG

EVENT_BILLING_PAYMENT_CC_T DWB_ACCT_RCHRG

EVENT_BILLING_PAYMENT_CHECK_T DWB_ACCT_RCHRG

EVENT_BILLING_PAYMENT_FAILED_T DWB_ACCT_RCHRG

EVENT_BILLING_PAYMENT_PAYORD_T DWB_ACCT_RCHRG

EVENT_BILLING_PAYMENT_POST_T DWB_ACCT_RCHRG

EVENT_BILLING_PAYMENT_WTRAN_T DWB_ACCT_RCHRG

NOTE_T DWB_EVT_PRTY_INTRACN

BAL_GRP_T_D, BAL_GRP_BALS_T_D, BAL_GRP_SUB_BALS_T_D

DWB_ACCT_BAL

EVENT_BAL_IMPACTS_T_D, EVENT_T_D, EVENT_BILLING_MISC_T_D

DWB_ACCT_BAL_IMPC

DWL_COLLCTN_TYP, COLLECTIONS_SCENARIO_T_D, DWR_ACCT

DWB_ACCT_DEBT

DWR_ADDR_LOC, DWR_CUST, DWB_INVC_ITEM

DWB_ACCT_PYMT

EVENT_ITEM_TRANSFER_T_D, EVENT_T_D, EVENT_BILLING_MISC_T_D,EVENT_BILLING_MISC_T_D,DWB_INVC_ITEM,

DWB_INVC_ADJ

EVENT_BAL_IMPACTS_T_D, EVENT_T_D DWB_INVC_DISC

BRM_PYMT_ASGN_V DWB_INVC_PYMT_ASGN

Postpaid:

EVENT_T_D, E_DLYD_SES_TLCO_GSM_T_D, EVENT_DLAY_SESS_TLCS_T_D, EVENT_BAL_IMPACT_COLL_VW, DWR_VAL_ADD_SRVC, DWR_PROD_SBRP, DWR_CUST,DWR_SRVC,DWB_INVC_ITEM

Prepaid:

EVENT_BAL_IMPACT_COLL_VW, EVENT_T_D,EVENT_SESSION_TLCS_T_D, EVENT_SESSION_TLCO_GSM_T_D, DWR_PROD_SBRP, DWR_CUST, DWR_VAL_ADD_SRVC

DWB_SMS_EVT

IFW_USAGETYPE_D DWL_CALL_SRVC_TYP

CFG_COLLECTIONS_SCENARIO_T_D DWL_COLLCTN_TYP

IFW_CURRENCY_D DWL_CRNCY_MAP

DD_OBJECTS_T_D DWL_PROD_SPEC_TYP

PAYINFO_T_D, PAYINFO_CC_T_D, PAYINFO_DD_T_D, PAYINFO_INV_T_D,DWR_ACCT

DWR_ACCT_PYMT_MTHD

CONFIG_BILLING_SEGMENT_T_D DWR_ACCT_SGMNT



Oracle Data Integrator BRM_OCDM Project


Oracle Data Integrator BRM_OCDM ProjectThe Oracle Data Integrator BRM_OCDM project is created when you install the BRM Adapter. The BRM_OCDM project contains the following folders:

■ SRC_STG_NONGG

■ STG_OCDM

Objects in SRC_STG_NONGG Folder of the BRM_OCDM ProjectThe SRC_STG_NONGG folder of the BRM_OCDM project contains packages to populate the staging layer of the Oracle Communications Data Model warehouse (the tables in the BRM_STG schema) with data from the BRM source system.

The four main packages load different types of BRM source data:

■ #1_USAGE_EVENTS_PKG

■ #2_BILLING_INVOICING_PKG

■ #3_PAYMENTS_PKG

BAL_GRP_T_D, BAL_GRP_SUB_BALS_T_D,

DWR_ACCT,DWR_PROD_SBRP

DWR_AGRMNT

DWR_PROD_SBRP, DWR_AGRMNT, PURCHASED_PRODUCT_T_D

DWR_AGRMNT_ITEM

DWR_ACCT, BAL_GRP_T_D, BAL_GRP_SUB_BALS_T_D, DWR_PROD_SBRP,DWR_PROD_SPEC

DWR_BRM_BAL_GRP

DWR_CUST, DWR_ADDR_LOC, ACCOUNT_T_D

DWR_CUST_ADDR

PLAN_T_D DWR_PROD_CTLG

PLAN_SERVICES_T_D, PLAN_T_D, DWR_PROD_CTLG, DWR_PROD_OFR,

DWR_PROD_CTLG_PROD_OFR_ASGN

DEAL_T_D, DWR_PROD_OFR

RATE_PLAN_T_D, DWR_PROD_SPEC DWR_PROD_OFR_PRICE

DEAL_T_D, DEAL_DISCOUNTS_T_D, DWR_SRVC_SPEC, DWR_PROD_OFR, DEAL_PRODUCTS_T_D, DWR_PROD_SPEC,

DWR_PROD_OFR_PROD_SPEC_ASGN

DWR_CUST_FCNG_SRVC, DWR_SRVC, DWR_ACCT,PURCHASED_PRODUCT_T_D,DWR_PROD_OFR, DWR_PROD_SPEC

DWR_PROD_SBRP

DWR_PROD_SBRP, PURCHASED_DISCOUNT_T_D, ACCOUNT_T_D_H, DWR_ACCT, DWR_PROD_SBRP, PURCHASED_PRODUCT_T_D,

DWR_PROD_SBRP_PRICE

DISCOUNT_T_D, PRODUCT_T_D DWR_PROD_SPEC

ACCOUNT_NAMEINFO_T_D, ACCOUNT_T_D, DWR_PRTY,

DWR_PRTY_CNTCT_INFO

SERVICE_TELCO_FEATURES_T_D DWR_SRVC_SPEC_CHAR

PRODUCT_T_D, DWR_PROD_SPEC DWR_VAL_ADD_SRVC





■ #4_COLLECTIONS_PKG

Additionally, the packages load the BRM source data based on the data dependencies to maintain the data integrity in the warehouse.

#1_USAGE_EVENTS_PKGThe #1_USAGE_EVENTS_PKG package loads the usage-related data from the BRM source system into the staging layer of the Oracle Communications Data Model warehouse. This package loads any new subscriber information (from the last update) and then loads the subscriber usage data.

This package runs the following interfaces to populate the BRM_STG schema tables with the data from the BRM source system:

■ ACCOUNT_NAMEINFO_T_NONGG_IU

■ ACCOUNT_T_NONGG_IU

■ BAL_GRP_BALS_T_NONGG_IU

■ BAL_GRP_SUB_BALS_T_NONGG_IU

■ BAL_GRP_T_NONGG_IU

■ BILLINFO_T_NONGG_IU

■ BILL_T_NONGG_IU

■ CFG_CREDIT_PROFILE_T_NONGG_IU

■ CONFIG_BEID_BALANCES_T_NONGG_IU

■ CONFIG_BILLING_SEGMENT_T_NONGG_IU

■ CONFIG_BUSINESS_TYPE_T_NONGG_IU

■ CONFIG_COLLECTIONS_SCENARIO_T_NONGG_IU

■ CONFIG_CUR_CONV_RATES_T_NONGG_IU

■ CONFIG_PAYMENT_PAY_TYPES_T_NONGG_IU

■ CONFIG_T_NONGG_IU

■ DD_OBJECTS_T_NONGG_IU

■ DEAL_DISCOUNTS_T_D_NONGG_IU

■ DEAL_PRODUCTS_T_NONGG_IU

■ DEAL_T_NONGG_IU

■ DISCOUNT_T_NONGG_IU

■ EVENT_ACTIVITY_TLCS_T_NONGG_IU

■ EVENT_ACTV_TLCS_SVC_CODES_T_NONGG_IU

■ EVENT_BAL_IMPACTS_T_NONGG_IU

■ EVENT_BROADBAND_USAGE_T_NONGG_IU

■ EVENT_DLAY_ACTV_TLCS_SVC_CDS_T_NONGG_IU

■ EVENT_DLAY_ACTV_TLCS_T_NONGG_IU

■ EVENT_DLAY_SESS_TLCS_SVC_CDS_T_NONGG_IU

■ EVENT_DLAY_SESS_TLCS_T_NONGG_IU



■ EVENT_DLYD_SESSION_TLCO_GPRS_T_NONGG_IU

■ EVENT_DLYD_SESSION_TLCO_GSM_T_NONGG_IU

■ EVENT_ITEM_TRANSFER_T_NONGG_IU

■ EVENT_RUM_MAP_T_NONGG_IU

■ EVENT_SESSION_DIALUP_T_NONGG_IU

■ EVENT_SESSION_TELCO_GPRS_T_NONGG_IU

■ EVENT_SESSION_TLCO_GSM_T_NONGG_IU

■ EVENT_SESSION_TLCS_T_NONGG_IU

■ EVENT_SESS_TLCS_SVC_CODES_T_NONGG_IU

■ EVENT_TAX_JURISDICTIONS_T_NONGG_IU

■ EVENT_T_NONGG_IU

■ HISTORY_BILLS_INVOICES_T_NONGG_IU

■ HISTORY_BILLS_ITEMS_T_NONGG_IU

■ HISTORY_BILLS_T_NONGG_IU

■ IFW_CURRENCY_NONGG_IU

■ IFW_TIMEZONE_NONGG_IU

■ IFW_USAGETYPE_NONGG_IU

■ INVOICE_STATUSES_T_NONGG_IU

■ INVOICE_T_NONGG_IU

■ ITEM_T_NONGG_IU

■ NOTE_T_NONGG_IU

■ PLAN_SERVICES_T_NONGG_IU

■ PLAN_T_NONGG_IU

■ PRODUCT_T_NONGG_IU

■ PURCHASED_DISCOUNT_T_NONGG_IU

■ PURCHASED_PRODUCT_T_NONGG_IU

■ RATE_PLAN_T_NONGG_IU

■ SERVICE_EMAIL_T_NONGG_IU

■ SERVICE_TELCO_FEATURES_T_NONGG_IU

■ SERVICE_TELCO_GPRS_T_NONGG_IU

■ SERVICE_TELCO_GSM_T_NONGG_IU

■ SERVICE_T_NONGG_IU

#2_BILLING_INVOICING_PKGThe #2_BILLING_INVOICING_PKG package loads the billing-related data from the BRM source system into the staging layer of the Oracle Communications Data Model warehouse. This package loads any new subscriber information and subscriber usage data (from the last update) and then loads the subscriber billing data.




■ EVENT_BILLING_MISC_T_NONGG_IU

■ EVENT_BILLING_PAYMENT_CASH_T_NONGG_IU

■ EVENT_BILLING_PAYMENT_CC_T_NONGG_IU

■ EVENT_BILLING_PAYMENT_CHECK_T_NONGG_IU

■ EVENT_BILLING_PAYMENT_DD_T_NONGG_IU

■ EVENT_BILLING_PAYMENT_FAILED_T_NONGG_IU

■ EVENT_BILLING_PAYMENT_PAYORD_T_NONGG_IU

■ EVENT_BILLING_PAYMENT_POST_T_NONGG_IU

■ EVENT_BILLING_PAYMENT_T_NONGG_IU

■ EVENT_BILLING_PAYMENT_WTRAN_T_NONGG_IU

#3_PAYMENTS_PKGThe #3_PAYMENTS_PKG package loads the payment-related data from the BRM source system into the staging layer of the Oracle Communications Data Model warehouse. This package loads any new subscriber information, subscriber usage data, and subscriber billing data (from the last update) and then loads the subscriber payment data.


■ PAYINFO_T_NONGG_IU

■ PAYINFO_INV_T_NONGG_IU

■ PAYINFO_DD_T_NONGG_IU

■ PAYINFO_CC_T_NONGG_IU

#4_COLLECTIONS_PKGThe #4_COLLECTIONS_PKG package loads the collection-related data from the BRM source system into the staging layer of the Oracle Communications Data Model warehouse. This package loads any new subscriber information, subscriber usage data, subscriber billing data, and subscriber payment data (from the last update) and then loads the subscriber collection data.


■ COLLECTIONS_SCENARIO_T_NONOGG_IU

■ COLLECTIONS_ACTION_T_NONOGG_IU

Objects in the STG_OCDM Folder of the BRM_OCDM ProjectThe STG_OCDM folder of the BRM_OCDM project contains packages to populate the foundation layer of the Oracle Communications Data Model warehouse. The main packages are the BULKLOAD packages for the initial loading of the Oracle Communications Data Model warehouse and the END-TO-END packages for refreshing the data in the warehouse.

■ USAGE_EVENTS_BULKLOAD



■ BILLING_INVOICE_BULKLOAD

■ PAYMENT_DATA_BULKLOAD

■ COLLECTION_DATA_BULKLOAD

■ END_TO_END_LOAD_PLAN_USAGE_EVENTS

■ END_TO_END_LOAD_PLAN_BILLING_INVOICE

■ END_TO_END_LOAD_PLAN_PAYMENT_DATA

■ END_TO_END_LOAD_PLAN_COLLECTION_DATA

These packages populate the staging layer (the tables in the BRM_STG schema) and, also the foundation layer (the tables in the OCDM_SYS schema) with the data from the BRM source system.

The BULKLOAD packages are optimized for loading huge amounts of data during the initial load of the warehouse.

The END-TO-END packages provide the flexibility to refresh the data in the warehouse, as needed. The packages also track the date of the last refresh and automatically loads data from the date of the last refresh.

For example, you can run END_TO_END_LOAD_PLAN_BILLING_INVOICE during off-peak hours to refresh the billing-related data in the warehouse but run the END_TO_END_LOAD_PLAN_USAGE_EVENTS package more frequently to refresh the usage-related data.

USAGE_EVENTS_BULKLOAD and END_TO_END_LOAD_PLAN_USAGE_EVENTS Packages

The USAGE_EVENTS_BULKLOAD and END_TO_END_LOAD_PLAN_USAGE_EVENTS packages load usage-related data from the BRM source system into the Oracle Communications Data Model warehouse.

The packages run the #1_USAGE_EVENTS_PKG package to populate the usage-related tables in the BRM_STG schema with the data from the BRM source system and then runs the STG_OCDM_LOAD package to populate the related tables in the OCDM_SYS schema with the data from the BRM_STG schema delta tables.

BILLING_INVOICE_BULKLOAD and END_TO_END_LOAD_PLAN_BILLING_INVOICE PackagesThe BILLING_INVOICE_BULKLOAD and END_TO_END_LOAD_PLAN_BILLING_INVOICE packages load billing-related data from the BRM source system into the Oracle Communications Data Model warehouse.

The packages run the #2_BILLING_INVOICING_PKG package to populate the billing-related tables in the BRM_STG schema with the data from the BRM source system and then runs the STG_OCDM_LOAD package to populate the related tables in the OCDM_SYS schema with the data from the BRM_STG schema delta tables.

PAYMENT_DATA_BULKLOAD and END_TO_END_LOAD_PLAN_PAYMENT_DATA PackagesThe PAYMENT_DATA_BULKLOAD and END_TO_END_LOAD_PLAN_PAYMENT_DATA packages load payment-related data from the BRM source system into the Oracle Communications Data Model warehouse.

The packages run the #3_PAYMENTS_PKG package to populate the payment-related tables in the BRM_STG schema with the data from the BRM source system and then



runs the STG_OCDM_LOAD package to populate the related tables in the OCDM_SYS schema with the data from the BRM_STG schema delta tables.

COLLECTION_DATA_BULKLOAD and END_TO_END_LOAD_PLAN_COLLECTION_DATA PackagesThe COLLECTION_DATA_BULKLOAD and END_TO_END_LOAD_PLAN_COLLECTION_DATA packages load collection-related data from the BRM source system into the Oracle Communications Data Model warehouse.

The packages run the #4_COLLECTIONS_PKG package to populate the collection-related tables in the BRM_STG schema with the data from the BRM source system and then runs the STG_OCDM_LOAD package to populate the related tables in the OCDM_SYS schema with the data from the BRM_STG schema delta tables.

STG_OCDM_LOAD PackageThe STG_OCDM_LOAD package loads the Oracle Communications Data Model foundation layer tables with the data from the staging layer delta tables.

This package runs the following interfaces to populate the OCDM_SYS schema tables with the data from the BRM_STG schema delta tables:

■ DWB_ACCT_BAL_IMPC_MAP

■ DWB_ACCT_BAL_MAP

■ DWB_ACCT_DEBT_MAP

■ DWB_ACCT_PYMT_MAP

■ DWB_BRDBND_USG_EVT_MAP

■ DWB_CRNCY_EXCHNG_RATE_MAP

■ DWB_DATA_SRVC_EVT_MAP (DIALUP)

■ DWB_DATA_SRVC_EVT_MAP (GSM POSTPAID)

■ DWB_DATA_SRVC_EVT_MAP (GSM PREPAID)

■ DWB_GPRS_USG_EVT_MAP (PostPaid)

■ DWB_GPRS_USG_EVT_MAP (PrePaid)

■ DWB_INVC_ADJ_MAP

■ DWB_INVC_DISC_MAP

■ DWB_INVC_ITEM_MAP

■ DWB_INVC_MAP

■ DWB_INVC_PYMT_ASGN_MAP

■ DWB_SMS_EVT_MAP (PostPaid)

■ DWB_SMS_EVT_MAP (PrePaid)

■ DWB_SRVC_STAT_HIST_MAP

■ DWB_WRLS_CALL_EVT_MAP (PrePaid)

■ DWB_WRLS_CALL_EVT_MAP(PostPaid)

■ DWL_ACCT_BAL_TYP_MAP

■ DWL_CALL_SRVC_TYP_MAP

■ DWL_COLLCTN_TYP_MAP

Schema Definitions Added by the BRM Adapter


■ DWL_CRNCY_MAP

■ DWL_CUST_TYP_MAP

■ DWL_PK_OFPK_TIME_MAP

■ DWL_PROD_SPEC_TYP_MAP

■ DWR_ACCT_BAL_GRP_MAP

■ DWR_ACCT_MAP

■ DWR_ACCT_PREF_INVC_DLVRY_MAP

■ DWR_ACCT_PYMT_MTHD_MAP

■ DWR_ACCT_SGMNT

■ DWR_AGRMNT_ITEM_MAP

■ DWR_AGRMNT_MAP

■ DWR_BRM_BAL_GRP_MAP

■ DWR_CUST_ADDR_MAP

■ DWR_CUST_FCNG_SRVC_MAP

■ DWR_CUST_MAP

■ DWR_PROD_CTLG_MAP

■ DWR_PROD_CTLG_PROD_OFR_ASGN_MAP

■ DWR_PROD_OFR_MAP

■ DWR_PROD_OFR_PRICE_MAP

■ DWR_PROD_OFR_PROD_SPEC_ASGN_MAP

■ DWR_PROD_SBRP_MAP

■ DWR_PROD_SBRP_PRICE_MAP

■ DWR_PROD_SPEC_MAP (PRODUCT_T)

■ DWR_PRTY_CNCT_INFO_MAP

■ DWR_PRTY_MAP

■ DWR_PRTY_MAP (Payinfo_CC)

■ DWR_PRTY_MAP (Payinfo_DD)

■ DWR_PRTY_MAP (Payinfo_INV)

■ DWR_SRVC_MAP

■ DWR_SRVC_SPEC_CHAR_MAP

■ DWR_SRVC_SPEC_MAP

■ DWR_SRVC_SPEC_PROD_SPEC_RLTN_MAP

■ DWR_VAL_ADD_SRVC_MAP

■ OCDM_SYS_LOGS_ERROR_INTERFACE

Schema Definitions Added by the BRM AdapterInstalling and configuring the BRM Adapter adds the following definitions:



■ A database schema named BRM_STG that defines a staging area for use by the BRM adapter. For information on the definitions in this database schema, see "BRM_STG Schema Objects".

■ Procedure definitions that populate the foundation layer of an Oracle Communications Data Model warehouse. These definitions are added to the OCDM_SYS schema delivered with Oracle Communications Data Model. For more information on these procedures, see "OCDM_SYS Objects for the BRM Adapter".

BRM_STG Schema ObjectsThe BRM_STG schema includes the tables, views, functions, and procedures shown in Table 3–2.

OCDM_SYS Objects for the BRM AdapterInstalling and configuring the BRM Adapter adds the following procedure definitions to the OCDM_SYS schema:

■ DEL_OCDM

■ DISB_CONS

■ DISB_CONS_BRM

Table 3–2 Objects in the BRM_STG Schema

Object Type Object Name Description

Table source_table_name Standard staging tables. source_table_name is the same as the BRM source table name.

Table source_table_name_D Delta tables. Each BRM source table has one table definition.

Table source_table_name_D_H Delta history tables. Each BRM source table has one table definition.

Table BRM_MAPPING_TAB Oracle GoldenGate input parameter table.

Table BRM_ETL_PARAMETER BRM ETL parameter loading table.

View ADDRESS_VW Stores the address of 'Billing_address','Payment_invc','Payment_dd', and 'Payment_cc'.

View EVENT_BAL_IMPACT_COLL_VW

Stores the product related cost, tax, and discount amount.

View EVENT_BILLING_PAYMENTS_T_MAP_VW

Stores information about bill payment related information.

View SERVICE_T_MAP_VW

Function BRM_GET_DD_OBJ_MAP

Function FN_LOOKUP_MATRIX Returns the currency type of different country/customer type/peak-off peak time /Account Balance Type depending upon parameter used to call the function.

Function UTC_TO_ORACLE

Procedure PRE_STAGING_LOAD For Oracle GoldenGate.

Procedure POST_STAGING_LOAD For Oracle GoldenGate.



■ ENAB_CONS

■ GEO_MAP

■ INSERT_REF

■ UPDATE_ACCT_ACCT

■ UPDATE_ACCT_BILLINFO

■ UPDATE_ACCT_PYMT_MTHD

■ UPDATE_ADDR_LOC

■ UPDATE_BASE_PROD_KEY

■ UPDATE_CUST

■ UPDATE_CUST_FCNG_SRVC

■ UPDATE_DWB_INVC

■ UPDATE_DWB_INVC_ITEM

■ UPDATE_PROD_OFR

■ UPDATE_PROD_OFR_PRICE

■ UPDATE_PROD_SBRP

■ UPDATE_PROD_SBRP_CHRGS

■ UPDATE_PROD_SPEC

■ UPDATE_PRTY

■ UPDATE_PRTY_FOR_CUST

■ UPDATE_SRVC_SPEC

Part IIPart II Network Charging and Control Application

Adapter

Part II contains the following chapters:

■ Chapter 4, "About NCC Adapter for Oracle Communications Data Model"

■ Chapter 5, "Using the NCC Adapter"

■ Chapter 6, "NCC Adapter Reference"

4

About NCC Adapter for Oracle Communications Data Model 4-1

4About NCC Adapter for OracleCommunications Data Model

This chapter describes the Oracle Communications Network Charging and Control Adapter for Oracle Communications Data Model (referred to as the NCC Adapter in this chapter).

This chapter includes the following sections:

■ What Are Oracle Communications Prepaid Charging and Network Charging and Control

■ Overview of NCC Adapter

■ NCC Adapter Execution Flows

For more information on Oracle Communications Network Charging and Control Adapter for Oracle Communications Data Model Oracle Communications Data Model Implementation and Operations Guide.

What Are Oracle Communications Prepaid Charging and Network Charging and Control

Oracle Communications Prepaid Charging provides critical prepaid capabilities within the overall Oracle Communications Network Charging and Control strategy. Complementary options to Oracle Communications Prepaid Charging include Oracle Communications Messaging Manager and Oracle Communications Number Services Manager.

As the telecommunications market rapidly migrates from a voice-centric to a data-centric, multimedia business environment, communication service providers (CSPs) need reliable real-time charging capabilities for an increasingly diverse set of services. Oracle Communications Prepaid Charging is designed to help operators (MNOs, MVNEs and MVNOs) generate revenue, grow market share, and sustain competitive advantages by providing an agile platform to launch and charge for a full range of innovative service offerings to subscribers. Built to accommodate all content types and network protocols, Oracle Communications Prepaid Charging helps operators to rapidly and cost effectively create new streams of value-added services revenue.

Overview of NCC AdapterThe Oracle Communications Network Charging and Control Adapter for Oracle Communications Data Model (referred to as the NCC Adapter in this chapter) is an option for Oracle Communications Data Model. You can use the NCC Adapter to

Overview of NCC Adapter


populate the foundation layer (that is, the base, reference, and lookup tables) of an Oracle Communications Data Model warehouse with data from an Oracle Communications Network Charging and Control system.

Figure 4–1 shows the Oracle Communications Data Model NCC Adapter Architecture.

Figure 4–1 Overview of NCC Adapter Architecture

The NCC Adapter works with Oracle Communications Data Model and includes the following components:

■ Source system Oracle Communications Network Charging and Control (NCC)

■ Oracle GoldenGate: To use a real-time feed to staging layer

■ Oracle Data Integrator: to load from the source system Oracle Communications Network Charging and Control (NCC) to staging layer (if you decide not to use real-time feed with Oracle GoldenGate, then you can refresh data with Oracle Data Integrator). For more information see "Execution Flow Using the NCC Adapter with Only Oracle Data Integrator" on page 4-5.

■ Oracle Communications Data Model Oracle

Components of the NCC AdapterThe NCC Adapter uses the following components:

■ Database Schemas Used by the NCC Adapter



■ The NCC_OCDM Project For information on NCC_OCDM project, see "Oracle Data Integrator NCC_OCDM Project" on page 6-2.

■ NCC Source Schema Objects. For more information, see "NCC Source Schema Objects" on page 6-5.

■ Schema definitions added by the NCC Adapter. For more information, see "Schema Definitions Added by the NCC Adapter" on page 6-5.

Database Schemas Used by the NCC AdapterThe NCC Adapter uses the following database schemas:

Overview of NCC Adapter


■ Source schemas: The source of the NCC Adapter is an Oracle Communications Network Charging and Control (NCC) system as defined by the NCC BE and CSS schemas.

See "NCC Source Schema Objects" on page 6-5 for details on the specific source objects.

■ Staging layer schema: The NCC Adapter uses a staging layer when loading data from the NCC system to the foundation layer objects of an Oracle Communications Data Model warehouse. This staging layer is used for changed data and historical data storage and as a source schema when loading the foundation layer objects of the Oracle Communications Data Model. The NCC Adapter defines the staging layer as a database schema named ncc_stg.

See "NCC_STG Schema Objects" on page 6-4 for more information on the ncc_stg schema.

■ Target schema: The target of the NCC Adapter is an Oracle Communications Data Model warehouse. The specific target objects are the foundation layer objects of Oracle Communications Data Model. These objects are defined in the ocdm_sys schema, which is delivered with Oracle Communications Data Model and documented in Oracle Communications Data Model Reference.

The NCC Adapter defines additional procedures in the ocdm_sys schema. These procedures are shown in "Definitions Added to the OCDM_SYS Schema" on page 6-6.

Oracle Data IntegratorThe NCC Adapter uses extract, transform, and load (ETL) created in Oracle Data Integrator as the ETL for performing an initial load of the foundation layer objects of Oracle Communications Data Model (that is, the base, reference, and lookup tables). You can also use Oracle Data Integrator ETL to perform a scheduled refresh of the staging layer.

For more information on the use of Oracle Data Integrator with the NCC Adapter, see the following:

■ "Initial Loading Using the NCC Adapter" on page 5-1

■ "Execution Flow Using the NCC Adapter with Only Oracle Data Integrator" on page 4-5

■ "Refreshing the Foundation Layer with Real-Time Data" on page 5-3

■ "Oracle Data Integrator NCC_OCDM Project" on page 6-2

Oracle GoldenGateAfter you have performed an initial load of the foundation layer objects of Oracle Communications Data Model using Oracle Data Integrator, you can use Oracle GoldenGate for to perform a real-time feed of the NCC source data to the staging layer.

For more information on the use of Oracle GoldenGate with the NCC Adapter, see the following:

■ "Refreshing the Foundation Layer with Real-Time Data" on page 5-3

■ "Execution Flow Using the NCC Adapter with Oracle GoldenGate and Oracle Data Integrator" on page 4-4

NCC Adapter Execution Flows


NCC Adapter Execution FlowsThe NCC Adapter uses a slightly different execution flow depending on whether you are using the adapter with Oracle GoldenGate:

■ Execution Flow Using the NCC Adapter with Oracle GoldenGate and Oracle Data Integrator

■ Execution Flow Using the NCC Adapter with Only Oracle Data Integrator

Execution Flow Using the NCC Adapter with Oracle GoldenGate and Oracle Data Integrator

When you use the NCC Adapter with Oracle GoldenGate to refresh the foundation layer of the Oracle Communications Data Model warehouse as described in "Refreshing the Foundation Layer with Real-Time Data" on page 5-3, the foundation layer data is always synchronized with the NCC source data.

Figure 4–2 illustrates the NCC Adapter execution flow when using the adapter with Oracle GoldenGate.

Figure 4–2 Execution Flow When Using the NCC Adapter with Oracle GoldenGate

When using Oracle GoldenGate with the NCC Adapter, the execution flow is as follows (as shown in Figure 4–2):

1. (Step 1) When all Oracle GoldenGate processes for the NCC Adapter are running, whenever new data comes into the source database, Oracle GoldenGate extracts that new incoming data and uses it to populate the normal staging tables.

2. (Steps 2 and 3) The pre_ocdm_load procedure loads the delta tables in the staging area with data from the normal staging tables and the delta history tables in the staging area with data from the delta tables.

Note: Only the data in the delta history tables remains forever and is always synchronized with source data. After the data in the delta staging tables is loaded into the foundation layer of the Oracle Communications Data Model warehouse, the delta tables are truncated.



3. (Step 4) Oracle Data Integrator loads data from the delta tables in the staging layer into the foundation layer of the Oracle Communications Data Model warehouse when the data in the staging table changes.

Execution Flow Using the NCC Adapter with Only Oracle Data IntegratorYou can use the NCC Adapter with Oracle Data Integrator alone. This method of using the NCC Adapter is sometimes called the Oracle Data Integrator-pull version of the NCC Adapter.

You always use the Oracle Data Integrator-pull version of the NCC Adapter for the initial load that you perform right after installation as described in "Initial Loading Using the NCC Adapter" on page 5-1. Later, you can also use it to perform a scheduled data refresh as described in "Refreshing the Foundation Layer on a Scheduled Basis" on page 5-2.

Figure 4–3 illustrates the NCC Adapter execution flow when using the adapter only with Oracle Data Integrator.

Figure 4–3 Execution Flow When Using the NCC Adapter Without Oracle GoldenGate

When using this approach, the execution process is as follows (as shown in Figure 4–3):

1. (Steps 1 and 3) The NCC Adapter, using Oracle Data Integrator, loads the data from the source database into the staging database.

2. (Steps 2 and 5) Using procedures, the NCC Adapter loads data into several staging database tables; for example, last day, delta, and history tables.

3. (Step 4) The NCC Adapter loads the delta tables into the staging area using the normal table 'MINUS' last day table.

4. (Step 6 in diagram) The NCC Adapter loads the data from the delta tables into the foundation layer of the Oracle Communications Data Model warehouse.

5

Using the NCC Adapter 5-1

5Using the NCC Adapter

This chapter provides information about populating an Oracle Communications Data Model warehouse using the NCC Adapter.

This chapter contains the following topics:

■ About Populating a Warehouse Using the NCC Adapter

■ Initial Loading Using the NCC Adapter

■ Refreshing the Data Using the NCC Adapter

For information on installing and configuring the NCC Adapter, see Oracle Communications Data Model Adapters and Analytics Installation Guide.

For detailed information about the objects and extract, transform, and load (ETL) associated with the NCC Adapter, see Chapter 6, "NCC Adapter Reference".

About Populating a Warehouse Using the NCC AdapterYou use the NCC Adapter to populate or refresh the foundation layer of the Oracle Communications Data Model warehouse (that is, the base, reference, and lookup tables defined in the ocdm_sys schema).

After you use the NCC Adapter to populate the foundation layer, use the Oracle Communications Data Model procedures to populate or refresh the access layer (that is, the derived tables, aggregate tables, Oracle OLAP cubes, and data mining models defined in the ocdm_sys schema) in the same manner as you would if you were not using an application adapter for Oracle Communications Data Model to populate the foundation layer. For more information, see Oracle Communications Data Model Implementation and Operations Guide.

Initial Loading Using the NCC AdapterTo perform an initial load of the foundation layer of an Oracle Communications Data Model warehouse using the NCC Adapter, use Oracle Data Integrator:

1. Verify that the installation and configuration created the schema objects described in "Schema Definitions Added by the NCC Adapter" on page 6-5.

2. From Oracle Data Integrator Studio Designer, go to the NCC_OCDM project, then do the following:

See Also: Oracle Communications Data Model Adapters and Analytics Installation Guide for instructions on installing and configuring the NCC Adapter for use by Oracle Data Integrator.

Refreshing the Data Using the NCC Adapter


a. Select SRC_STG_NONOGG, then Packages, and then, select and run the following packages:

– SRC_STG_LOAD_NON_OGG_PKG

– SRC_STG_EDR_LOAD_INITIAL_PKG

b. Select STG_OCDM, then Packages, and then select and run the following packages:

– STG_OCDM_INITIAL_LOAD_PKG

– STG_OCDM_EDR_PKG

Refreshing the Data Using the NCC AdapterAfter you perform an initial data load of an Oracle Communications Data Model warehouse, you must refresh the data. Use the NCC Adapter to refresh the data in the foundation layer of an Oracle Communications Data Model warehouse. There are two different ways that you can refresh the data:

■ Use Oracle Data Integrator to refresh all the data in the staging area and in the foundation layer of the Oracle Communications Data Model warehouse. The steps for performing this type of refresh are in "Refreshing the Foundation Layer on a Scheduled Basis" on page 5-2. See "Execution Flow Using the NCC Adapter with Only Oracle Data Integrator" on page 4-5 for more information on the execution flow for this type of refresh.

■ Use Oracle GoldenGate to populate the staging area with real-time data and, then, use Oracle Data Integrator to refresh the data in the Oracle Communications Data Model warehouse. The steps for performing this type of refresh are in "Refreshing the Foundation Layer with Real-Time Data" on page 5-3. See "Execution Flow Using the NCC Adapter with Only Oracle Data Integrator" on page 4-5 for more information on the execution flow for this type of refresh.

Refreshing the Foundation Layer on a Scheduled BasisIf you are not using the NCC Adapter with Oracle GoldenGate, you refresh the foundation layer on a scheduled basis using Oracle Data Integrator.

To refresh the data in the foundation layer using only Oracle Data Integrator, do the following:

1. Verify that the installation and configuration created the schema objects described in "Schema Definitions Added by the NCC Adapter" on page 6-5.

2. From Oracle Data Integrator Studio Designer, go to the NCC_OCDM project, then do the following:

a. Select SRC_STG_NONOGG, then Packages, and then, select and run the following packages:

See Also: "Oracle Data Integrator NCC_OCDM Project" on page 6-2 for more information on the packages and "Execution Flow Using the NCC Adapter with Only Oracle Data Integrator" on page 4-5 for a description of the execution flow for the initial load.

See Also: Oracle Communications Data Model Adapters and Analytics Installation Guide for instructions on installing and configuring the NCC Adapter for use by Oracle Data Integrator.


Using the NCC Adapter 5-3

– SRC_STG_LOAD_NON_OGG_PKG

– SRC_STG_EDR_LOAD_INCREMENTAL_PKG

b. Select STG_OCDM, then Packages, and then, select and run the following packages:

– STG_OCDM_INITIAL_LOAD_PKG

– STG_OCDM_EDR_PKG

Refreshing the Foundation Layer with Real-Time DataAfter performing an initial load of the Oracle Communications Data Model warehouse as described in "Initial Loading Using the NCC Adapter" on page 5-1, you can refresh the data in the foundation layer of an Oracle Communications Data Model warehouse on a real-time basis.

To ensure that the data in the foundation layer of an Oracle Communications Data Model warehouse is refreshed on a real-time basis, do the following:

1. Install the NCC Adapter and configure it for use by both Oracle GoldenGate and Oracle Data Integrator and as described in Oracle Communications Data Model Adapters and Analytics Installation Guide.

Verify that the installation and configuration created the schema objects described in "Schema Definitions Added by the NCC Adapter" on page 6-5.

2. From the GGSCI prompt, run the info all command to verify that the Oracle GoldenGate processes needed by the NCC Adapter are running.

Table 5–1 lists the Oracle GoldenGate processes on the source and staging systems.

The following code shows these commands and the successful results:

GGSCI> (mypc1) 5> info all


MANAGER RUNNINGEXTRACT RUNNING EXTNCC 00:00:00 00:00:02EXTRACT RUNNING EXTPNCC 00:00:00 00:00:06

GGSCI> (ocdm01) 2> info all


MANAGER RUNNINGREPLICAT RUNNING REPNCC 00:00:00 00:03:09

Table 5–1 Oracle GoldenGate Processes

Source System Processes Staging System Processes

Manager process

Extract process (EXTNCC)

Extract Pump process (EXTPNCC)

Manager process

Replicate process (REPNCC)



3. From Oracle Data Integrator Studio Designer, go to the NCC_OCDM project, and then do the following:

a. Select SRC_STG_NONOGG, then select Procedures, and then select and run the EXEC_ NORMAL_TABLES_PKG.

b. Select STG_OCDM, then select Packages, and then, select and run the STG_OCDM_OGG_CDC_LOAD_SCENARIO_PKG.

Tip: If you have two source systems then check the process status on both.

For commands to manage Oracle GoldenGate processes, see Oracle Communications Data Model Adapters and Analytics Installation Guide.

See Also: "Oracle Data Integrator NCC_OCDM Project" on page 6-2 for more information on the packages; and "Execution Flow Using the NCC Adapter with Oracle GoldenGate and Oracle Data Integrator" on page 4-4 for an explanation of the execution flow.

6

NCC Adapter Reference 6-1

6NCC Adapter Reference


■ NCC Adapter Source and Target Tables

■ Oracle Data Integrator NCC_OCDM Project

■ NCC_STG Schema Objects

■ NCC Source Schema Objects

■ Schema Definitions Added by the NCC Adapter

NCC Adapter Source and Target TablesTable 6–1 shows the Oracle Communications Data Model target tables and the associated source tables for the NCC Adapter.

Table 6–1 Target Oracle Communications Data Model Tables for NCC Adapter

NCC Source Table Oracle Communications Data Model Target Table

BE_BALANCE DWB_ACCT_BAL

BE_BUCKET DWL_ACCT_TYP

BE_WALLET DWL_UOM

CCS_AACT_ACCT_REFERENCE DWR_ACCT

CCS_ACCT DWR_AGRMNT

CCS_ACCT_REFERENCE DWR_CUST

CCS_ACCT_TYPE DWR_PROD_SBRP

CCS_BALANCE_TYPE DWR_PROD_SPEC

CCS_BALANCE_UNIT DWR_PRPD_VCHR

CCS_MB_RECHARGE DWR_PRPD_VCHR_BTCH

CCS_RECHARGE_TYPE DWR_PRPD_VCHR_RCHRG_OPTN

CCS_VOUCHER_BATCH DWB_ACCT_PYMT

CCS_VOUCHER_REFERENCE DWB_ACCT_PYMT_BAL_IMPC

CCS_VOUCHER_TYPE_VIEW DWB_DATA_SRVE_EVT

CCS_WALLET_TYPE DWB_WRLS_CALL_EVT

CCS_BE_CDR DWD_SMS_EVT

Oracle Data Integrator NCC_OCDM Project


Oracle Data Integrator NCC_OCDM ProjectWhen you install and configure the NCC Adapter, an Oracle Data Integrator project named NCC_OCDM project is defined. The NCC_OCDM project contains the following folders:

■ SRC_STG_NONAGG: Contains packages to populate the staging layer with data from the NCC source system.

■ STG_OCDM: Contains packages used to populate the foundation layer of an Oracle Communications Data Model warehouse with data from the NCC Adapter staging area.

SRC_STG_NONAGGThe packages in the STG_STG_MPMAGG folder of the NCC_OCDM project populate the tables in the staging layer, that is, the tables defined in the NCC_STG database, from data in the NCC source system (that is, the tables defined in the NCC BE and CSS databases).

SRC_STG_LOAD_NON_OGG_PKG PackageThis package loads data from the NCC source database into the NCC staging database. You use this package during an initial load and when you refresh the foundation layer using only Oracle Data Integrator.

SRC_STG_EDR_LOAD_INCREMENTAL_PKG PackageThis package loads the NCC source event detail record incremental data into the Staging Database EDR Table (that is, the CCS_BE_CDR table).

SRC_STG_EDR_LOAD_INITIAL_PKG PackageThis package loads NCC source event detail record (EDR) initial data into the staging database EDR table (that is, CCS_BE_CDR). You use this package during an initial load of the foundation layer.

STG_OCDMThe packages in the STG_OCDM folder populate the tables in the foundation layer of an Oracle Communications Data Model warehouse, the tables defined in the OCDM_SYS database, from data in the staging area (the tables defined in the NCC_STG database).

The following packages are defined in the STG_OCDM folder of the NCC_OCDM project:

■ STG_OCDM_INITIAL_LOAD_PKG Package

■ STG_OCDM_EDR_PKG Package

■ STG_OCDM_OGG_CDC_LOAD_SCENARIO_PKG Package

STG_OCDM_INITIAL_LOAD_PKG PackageThe STG_OCDM_INITIAL_LOAD_PKG loads data into the foundation layer tables of the Oracle Communications Data Model warehouse from data in the staging area delta tables (other than event detail record objects). You use this package during the initial load and when refreshing the data using only Oracle Data Integrator (You can use the NCC Adapter with Oracle Data Integrator alone; this method is sometimes called the Oracle Data Integrator-pull version of the NCC Adapter).

Oracle Data Integrator NCC_OCDM Project


This package runs the interfaces in the STG_OCDM folder named ncc_source_table_MAP (where ncc_source_table is the name of an NCC source table listed in "NCC Source Schema Objects" on page 6-5) in hierarchical sequence. These interfaces use the data in the staging delta tables (that is, the ncc_source_table_DELTA tables) to populate the related Oracle Communications Data Model foundation layer tables.

The following interfaces are in this package:

■ BE_BALANCE_MAP

■ BE_BUCKET_MAP

■ CCS_ACCT_ BE_WALLET _MAP

■ CCS_ACCT_CNRT_MAP

■ CCS_ACCT_REFERENCE_MAP

■ CCS_ACCT_SBRP_MAP

■ CCS_ACCT_TYPE_MAP

■ CCS_BALANCE_TYPE_MAP

■ CCS_BALANCE_UNIT_MAP

■ CCS_MB_RECHARGE_MAP

■ CCS_RECHARGE_TYPE_MAP

■ CCS_VOUCHER_BATCH_MAP

■ CCS_VOUCHER_REFERENCE_MAP

■ CCS_WALLET_TYPE_MAP

STG_OCDM_EDR_PKG PackageThis package loads tables in the foundation layer of an Oracle Communications Data Model warehouse from event detail record objects in the NCC staging layer. You use this package during the initial load and when refreshing the data using the Oracle Data Integrator-pull version of the NCC Adapter.

The package includes the following STG_OCDM event detail record interfaces in hierarchical sequence:

■ EDR_FREEFROM

■ EDR_RECHARGE_BALANCE_TYPE

■ EDR_RECHRG

■ EDR_CALL_EVT

■ EDR_PREPAID

■ EDR_SMS

STG_OCDM_OGG_CDC_LOAD_SCENARIO_PKG PackageThe STG_OCDM folder contains one package for each of the NCC source tables. These packages are named ncc_source_table_PKG where ncc_source_table is the name of an NCC source table listed in "NCC Source Schema Objects" on page 6-5.

When these packages are run, they execute the interfaces that populate the Oracle Communications Data Model foundation layer tables.

NCC_STG Schema Objects


You use these packages when using Oracle GoldenGate to refresh the data in the staging layer.

The package STG_OCDM_OGG_CDC_LOAD_SCENARIO_PKG calls the package STG_OCDM_OGG_CDC_LOAD_PKG; which finally calls the following interfaces:

■ BE_BALANCE_PKG

■ BE_BUCKET_PKG

■ CCS_ACCT_ BE_WALLET _PKG

■ CCS_ACCT_CNRT_PKG

■ CCS_ACCT_REFERENCE_PKG

■ CCS_ACCT_SBRP_PKG

■ CCS_ACCT_TYPE_PKG

■ CCS_BALANCE_TYPE_PKG

■ CCS_BALANCE_UNIT_PKG

■ CCS_MB_RECHARGE_PKG

■ CCS_RECHARGE_TYPE_PKG

■ CCS_VOUCHER_BATCH_PKG

■ CCS_VOUCHER_REFERENCE_PKG

■ CCS_WALLET_TYPE_PKG

NCC_STG Schema ObjectsThe NCC_STG schema defines the staging area used by the NCC Adapter. The NCC_STG schema contains the definitions shown in Table 6–2.

Table 6–2 Definitions in the NCC_STG Schema

Object Type Object Name Description or Usage

Type CDR_T Supports the population of event detail record (EDR) data.

Type CDRSET_T Supports for the population of EDR data.

Table CCS_BE_CDR Event detail record table.

Table source_table_name Normal staging tables. There is one table definition for each of the NCC source tables listed in "NCC Source Schema Objects" on page 6-5.

Table source_table_name_LD Previous day tables. There is one table definition for each of the NCC source tables shown in "NCC Source Schema Objects" on page 6-5.

Table source_table_name_DELTA Delta tables. There is one table definition for each of the NCC source tables shown in "NCC Source Schema Objects" on page 6-5.

Table source_table_name_DELTA_H Delta history tables. There is one table definition for each of the NCC source tables shown in "NCC Source Schema Objects" on page 6-5.

View CCS_RECHARGE_TYPE A view in the staging area that corresponds to a view of the same name in the ncc_ccs database.

View CDR_FREEFORM_RECHARGE Supports the population of EDR data.

View CDR_PREPAID Supports the population of EDR data.

View CDR_SMS Supports the population of EDR data.

View CDR_VOICE_CALL Supports the population of EDR data.

View VOUCHER_RECHARGE Supports the population of EDR data.

View VOUCHER_RECHARGE_BALANCE_TYPE Supports the population of EDR data.

Schema Definitions Added by the NCC Adapter


NCC Source Schema ObjectsThe NCC Adapter uses the data in the following NCC source system tables as source data:

BE_BALANCEBE_BUCKETBE_WALLETCCS_ACCTCCS_ACCT_ACCT_REFERENCESCCS_ACCT_REFERENCECCS_ACCT_TYPECCS_BALANCE_TYPECCS_BALANCE_UNITCCS_BE_CDRCCS_MB_RECHARGECCS_VOUCHER_BATCHCCS_VOUCHER_REFERENCECCS_WALLET_TYPE

Additionally, the NCC Adapter uses the CCS_RECHARGE_TYPE view as defined in the NCC css Database.

Schema Definitions Added by the NCC AdapterInstalling and configuring the NCC Adapter as described in Oracle Communications Data Model Adapters and Analytics Installation Guide adds the following definitions:

■ A database named NCC_STG that defines a staging area for use by the NCC Adapter. For information on the definitions in this database, see "NCC_STG Schema Objects" on page 6-5.

■ Procedure definitions that populate the foundation layer of an Oracle Communications Data Model warehouse. These definitions are added to the OCDM_SYS schema delivered with Oracle Communications Data Model. For more information on these procedures, see "Definitions Added to the OCDM_SYS Schema" on page 6-6.

NCC_STG Schema ObjectsThe NCC_STG schema defines the staging area used by the NCC Adapter. The schema contains the definitions shown in Table 6–3.

Package EDR Supports the population of EDR data.

Procedure POST_STAGING_LOAD Maintains the everyday source data changes and history of the data changes. Used by the Oracle GoldenGate option.

Procedure PRE_STAGING_LOAD Maintains the everyday source data changes and history of the data changes. Used by the Oracle GoldenGate option.

Procedure PRE_OCDM_LOAD Maintains the everyday source data changes and history of the data changes. Used by the Oracle Data Integrator-pull version of the NCC Adapter option.

Table 6–2 (Cont.) Definitions in the NCC_STG Schema


Schema Definitions Added by the NCC Adapter


Definitions Added to the OCDM_SYS SchemaInstalling and configuring the NCC Adapter as described in Oracle Communications Data Model Adapters and Analytics Installation Guide adds the following procedure definitions to the OCDM_SYS schema.

DISB_CONSENAB_CONSINSERT_REFLOOK_UP_LOAD_ONE_TIMEUPDATE_ACCTUPDATE_CHURN_DATEUPDATE_CNRTUPDATE_CUSTUPDATE_PRODUPDATE_PRPD_VCHR_INSTNCUPDATE_SBRP

The NCC Adapter uses these procedures as it populates the target objects.

Table 6–3 Definitions in the NCC_STG Schema


Type CDR_T Supports the population of Event Detail Record (EDR) data.

Type CDRSET_T Supports for the population of EDR data.

Table CCS_BE_CDR Event detail record table.

Table source_table_name Normal staging tables. There is one table definition for each of NCC source tables listed in "NCC Source Schema Objects" on page 6-5.

Table source_table_name_LD Previous day tables. There is one table definition for each of NCC source tables shown in "NCC Source Schema Objects" on page 6-5.

Table source_table_name_DELTA Delta tables. There is one table definition for each of NCC source tables shown in "NCC Source Schema Objects" on page 6-5.

Table source_table_name_DELTA_H Delta history tables. There is one table definition for each of NCC source tables shown in "NCC Source Schema Objects" on page 6-5.

View CCS_RECHARGE_TYPE This is a view in the staging area that corresponds to a view of the same name in the ncc_ccs database.

View CDR_FREEFORM_RECHARGE Supports the population of EDR data.

View CDR_PREPAID Supports the population of EDR data.

View CDR_SMS Supports the population of EDR data.

View CDR_VOICE_CALL Supports the population of EDR data.

View VOUCHER_RECHARGE Supports the population of EDR data.

View VOUCHER_RECHARGE_BALANCE_TYPE Supports the population of EDR data.

Package EDR Supports the population of EDR data.

Procedure POST_STAGING_LOAD Maintains the everyday source data changes and history of the data changes. Used by the Oracle GoldenGate option.

Procedure PRE_STAGING_LOAD Maintains the everyday source data changes and history of the data changes. Used by the Oracle GoldenGate option.

Procedure PRE_OCDM_LOAD Maintains the everyday source data changes and history of the data changes. Used by the Oracle Data Integrator-pull version of the NCC Adapter.

Part IIIPart III Social Network Analytics for Oracle

Communications Data Model

Part III contains the following chapters:

■ Chapter 7, "Social Network Analytics"

■ Chapter 8, "Social Network Analytics Reports"

7

Social Network Analytics 7-1

7 Social Network Analytics

Oracle Communications Data Model provides the Social Network Analytics (SNA) Add-On adapter that is optimized for social network analysis across large volumes of call record data (CDR) associated with an Oracle Communications Data Model data warehouse.


■ Overview of the Social Network Analytics Add-On Adapter

■ Social Network Analytics Process Flow

■ About Social Network Analytics Roles

Overview of the Social Network Analytics Add-On AdapterOracle Communications Data Model Social Network Analytics supports the following:

■ About Social Network Analytics Features

■ Social Network Analytics Opt-Out Features

■ Social Network Analytics Process Flow

■ About Social Network Analytics Roles

About Social Network Analytics FeaturesOracle Communications Data Model Social Network Analytics features include:

■ Identification of social network communities.

■ Network metrics characterizing the social graph.

■ Network distribution information.

■ Predictive scores for churn and influence at a node level, and potential revenue and value at risk.

■ User interface targeted at business users and flexible, ad-hoc reporting.

Use Oracle Communications Data Model Social Network Analytics and the associated reports and tools to assist you with:

■ Acquiring customers

– Member-get-member campaigns.

– Profile off-net prospects using community membership information.

■ Retaining customers

Overview of the Social Network Analytics Add-On Adapter


– Enhance churn prediction capabilities.

– Focus retention marketing on high social network revenue segments.

– Augment existing customer segmentation capabilities.

– Identify rotational churners through social signatures.

■ Growing your customer base

– Increase conversion rates for cross-sell and up-sell campaigns.

– More focused product offer development.

Social Network Analytics Opt-Out Features■ Opt-Out field added at subscriber level to help address privacy concerns

■ All members still included in aggregate analysis (that is, when determining communities, connections, and so on)

■ Individual scores not computed, and subscribers excluded from reports with individual subscriber details.

Social Network Analytics Concepts and Terms

Table 7–1 Social Network Analytics Concepts and Terms

SNA Concept or Term Description

Churn pressure Measure by number of immediate neighbors for a node that have churned recently (during the period used to construct the graph).

Connectedness The average number of connections of a node’s immediate neighbors.

Connections The number of direct connections a node has with other nodes (also known as, first-order centrality).

Degree influence Number of connections a node has (also known as, degree centrality).

Eigen influence Correlated with degree influence, but taking into account the pattern of connectivity around the node. For example, A may have more connections than B, but if B is located in a highly connected region of the graph while A is located in isolated region, A would have higher degree influence, but lower Eigen influence.

Network value Individual node value, also factoring in the value of a node’s immediate neighbors.

Network value at risk Individual node’s network value multiplied by that node’s churn probability.

Product viral influence The number of times an immediate neighbor acquires a product within a predetermined window of time after the original node had purchased that product. Returns an integer score for each product considered in the analysis.

Subscriber viral influence Computed as the number of times an immediate neighbor of a node acquires a product (any product) within a predetermined window of time after the original node had purchased the product.

Value Monetary measurement of a node’s value or importance. User definable; typically will use ARPU or a subscriber’s lifetime value.

Value at risk The value of a node multiplied by its probability of leaving the network (churning).

Viral influence Measure of a node’s ability to influence others in a network, and the degree the adoption of a product displayed viral behavior characteristics.

About Social Network Analytics Roles


Social Network Analytics Process FlowFigure 7–1 shows the Oracle Communications Data Model Social Network Analytics process flow and major components. The process flow includes the following steps:

1. Call detail records, subscriber demographics, purchase history, and so on are loaded into Oracle Communications Data Model foundation layer tables.

2. The Oracle Communications Data Model intra-ETL populates Social Network Analytics input tables.

3. Oracle Business Intelligence Enterprise Edition dashboard is used to enter Social Network Analytics input parameters.

4. The Social Network Analytics application back-end process schedules jobs to run through mining models; it populates results to Social Network Analytics output tables.

5. Oracle Business Intelligence Enterprise Edition dashboards are used to display the Social Network Analytics results.

Figure 7–1 Social Network Analytics Process Flow

About Social Network Analytics RolesIn social network analysis, a role describes the position of a node in relationship to its neighbors and the network as a whole. For example, common metrics used for determining node roles include a node's centrality, popularity, and authority.

Social Network Analytics Subscriber Roles Leaders and Role StrengthThe Social Network Analytics Add-on provides community-based node roles based on Scripps, Tan and Esfahanian (2007)1. Thus, Social Network Analytics defines the

1 Scripps, Tan and Esfahanian (2007). Exploration of Link Structure and Community-Based Node Roles in Network Analysis. ICDM 2007. Seventh IEEE International Conference on Data Mining.



community-based role of a node according to the number of communities they connect to and the number of connections they have to direct neighbors.

As shown in Figure 7–2, Social Network Analytics defines four node roles by dividing a community-degree chart into four quadrants. Each quadrant is assigned a different role from the available roles listed in Table 7–2. The vertical axis represents relative degree, a measure of how many immediate neighbors a node has. This measure is scaled between 0 and 1. The horizontal axis is a community score representing how connected a node is to other communities. This metric is also scaled between 0 and 1. The four quadrants are defined by splitting the graph vertically and horizontally at 0.5.

Social Network Analytics Role StrengthIn addition to assigning a role to a node, Social Network Analytics provides a measure of role strength. The higher this measure, the more the node displays the characteristics of the role. With respect to the graph in Figure 7–2, the closer a node is to one of the corners, the stronger the role strength for the role assigned to it. For example, a node that is placed close to the upper left-hand corner based on its value for relative degree and community score is assigned a role of Big Fish with role strength close to 1. A node classified as Big Fish but with both relative degree and community score close to 0.5 will have role strength close to 0.

Social Network Analytics LeadersA node is considered to be a leader in a community if it is the most connected node in the community and it is also substantially more connected than the second most connected node in the community.

Figure 7–2 Social Network Analytics Subscriber Node Roles



Table 7–2 SNA Role Descriptions

Role Description

Ambassador These are nodes with a high-degree score, a high number of connections, and a high community score (connections with nodes in other communities). In this way they act as ambassadors between many different communities. They also help propagate information rapidly over the network.

Big Fish These are nodes that are very important only within a community. They are very connected, with a high-degree score, to nodes in their own community but have very few connections with nodes in other communities (low community score). The term comes from the cliché "big fish in a small pond."

Bridge These are nodes with a low degree of connections, small by number of connections, but a high community score (a relatively high number of connections to other communities). As such, they behave as bridges between small numbers of communities.

Loner These are nodes with a low degree of connections and most of them are only in their own communities.

8

Social Network Analytics Reports 8-1

8Social Network Analytics Reports

This chapter provides Oracle Communications Social Network Analytics reports.


■ SNA Home Page

■ SNA Analysis Report

■ SNA Analysis Runs Report

■ SNA Network Report

■ SNA Communities Report

■ SNA Churn Report

■ SNA Influence Report

■ SNA Subscribers Report

SNA Home PageFigure 8–1 shows the SNA Home page with the available Oracle Communications Social Network Analytics reports.

SNA Analysis Report


Figure 8–1 SNA Dashboard

SNA Analysis ReportFigure 8–2 shows the Analysis main page with settings and job execution details.

SNA Analysis Runs Report


Figure 8–2 Analysis Report

SNA Analysis Runs ReportFigure 8–3 shows the SNA Analysis Runs page.

SNA Analysis Runs Report


Figure 8–3 SNA Analysis Runs Report

Scheduler Jobs Overview: Polling Analysis Job ReportFigure 8–4 shows the polling analysis job report.

Figure 8–4 Polling Analysis Job Report

Scheduler Jobs Overview: Update Analysis Job Run Log Details ReportFigure 8–5 shows the update analysis job run log details report.

SNA Network Report


Figure 8–5 Update Analysis Job Run Log Details Report

SNA Network ReportFigure 8–6 shows the SNA network report.

Figure 8–6 Network Report (Top Network Metrics and Bottom Network Distributions)

SNA Communities Report


SNA Communities ReportFigure 8–7, Figure 8–8, and Figure 8–9 show the SNA communities report.

SNA Communities Report


Figure 8–7 SNA Communities Report (Top Communities and Viewers)

Figure 8–8 SNA Communities Report (Distributions: Size, Connections, Value, and Value at Risk)

SNA Churn Report


Figure 8–9 SNA Communities Report (Distributions: Churners, Influence, On-net and Off-net Subscribers)

SNA Churn ReportFigure 8–10 shows the SNA churn page.

Figure 8–10 SNA Churn Report

SNA Subscribers Report


SNA Influence ReportFigure 8–11 shows the SNA influence report.

Figure 8–11 SNA Influence Report

SNA Subscribers ReportFigure 8–12 shows the SNA subscribers report.

SNA Subscribers Report


Figure 8–12 SNA Subscribers Report

Part IVPart IV Billing Analytics for Oracle Communications

Data Model

Part IV contains the following chapters:

■ Chapter 9, "Billing Analytics Overview and Reports"

■ Chapter 10, "Billing Analytics Reference"

9

Billing Analytics Overview and Reports 9-1

9Billing Analytics Overview and Reports

This chapter contains the following sections:

■ Overview of Oracle Communications Data Model Billing Analytics

■ Overview of Billing Analytics Process Flow

■ Billing Analytics Reports

Overview of Oracle Communications Data Model Billing AnalyticsBilling Analytics provides the following:

■ End-to-end analytic applications developed on Oracle Communications Data Model

■ Data fed through the BRM Adapter and the NCC Adapter

■ Comprehensive and visually appealing dashboards built with Oracle Business Intelligence Enterprise Edition

■ Enables users to understand existing business customers across all their products and services and predict and analyze customer behavior to increase revenue and retention

■ Reduces time, cost, risk, and complexity of a custom solution.

Billing Analytics covers the following categories:

Overview of Billing Analytics Process FlowFigure 9–1 shows the Oracle Communications Data Model Billing Analytics process flow and major components. The process flow includes the following steps:

Category Description

Billed Revenue Revenue-related metrics: such as total revenue, Average Revenue Per User (ARPU), adjustments, collections, and so on

Prepaid Metrics Prepaid-specific metrics: such as total recharges, average recharges, disturbed recharge cycles, and so on

Usage Metrics Usage-specific metrics: such as total minutes of usage, number of calls, top users (voice, data, SMS)

Billing Efficiency Billing operations metrics: such as payments by payment method, percent of e-bills issued, percent of bills adjusted, and so on

Customer Metrics Customer acquisition and churn metrics that can be viewed across various parameters

Billing Analytics Reports


1. Data from Oracle Communications Billing and Revenue Management source system or Oracle Communications Network Charging and Control source system is loaded into Oracle Communications Data Model leveraging the BRM Adapter or the NCC Adapter.

OR

1. Data is loaded from other billing applications using a custom ETL.

2. The Intra-ETL populates Oracle Communications Data Model analytic layer which has the same tables used by the billing analytics application.

3. Oracle Business Intelligence Enterprise Edition dashboards display Billing Analytics metrics.

Figure 9–1 Billing Analytics Process Flow

Billing Analytics ReportsBilling Analytics includes reports in five areas:

■ Billed Revenue Reports

■ Billing Efficiency Reports

■ Customer Metrics Reports

■ Prepaid Metrics Reports

■ Usage Revenue Reports

Billed Revenue ReportsThis area includes revenue related metrics such as the following:

■ Billed Revenue Overview

■ Revenue Detail

■ ARPU

■ Discounts



■ Payments and Collections

■ Adjustments

■ Maps

Billed Revenue OverviewThe report in Figure 9–2 shows the total billed revenue by month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–2 Billed Revenue Overview Total Billed Revenue

The report in Figure 9–3 shows the total, prepaid, and postpaid ARPU (Average Revenue Per User) per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–3 Billed Revenue Overview ARPU

Figure 9–4 compares revenue targets that the company might have established to the actual revenue results. The difference is calculated and a flag is set based on positive or negative results.



Figure 9–4 Billed Revenue Overview Revenue Target

The report in Figure 9–5 compares ARPU targets that the company might have established to the actual ARPU results. The difference is calculated and a flag is set based on positive or negative results.

Figure 9–5 Billed Revenue Overview ARPU Target

The chart in Figure 9–6 shows the top five plans based on total revenue. This chart can be further filtered using the dashboard prompts.

Figure 9–6 Billed Revenue Overview Top Plan

The chart in Figure 9–7 shows the bottom five plans based on total revenue. This chart can be further filtered using the dashboard prompts.



Figure 9–7 Billed Revenue Overview Bottom Plan

The chart in Figure 9–8 shows the top five states within the United States (US) based on total revenue. This chart can be further filtered using the dashboard prompts. The chart allows for a further drill down to top cities for the given state by clicking the various bars in the chart.

Figure 9–8 Billed Revenue Overview Top State

The chart in Figure 9–9 shows the bottom five states in the US based on total revenue. This chart can be further filtered using the dashboard prompts. The chart also allows for a further drill down to the bottom cities for the given state by clicking the various bars in the chart.



Figure 9–9 Billed Revenue Overview Bottom State

Revenue DetailThe report in Figure 9–10 shows the total billed revenue by month. Use the slide bar and prompts to further filter the data.

Figure 9–10 Billed Revenue Detail Total Billed Revenue

The report in Figure 9–11 shows the total billed revenue per year by customer type (that is, individual or business users). Use the dashboard prompts to further filter the data.

Figure 9–11 Billed Revenue Detail Revenue by Customer Type

The report in Figure 9–12 shows a table view of a year-over-year comparison of the total billed revenue. The difference is calculated and the percent change is displayed.



Figure 9–12 Billed Revenue Detail Revenue Comparison

The report in Figure 9–13 shows a table view of the total billed revenue by customer type (individual subscribers, business users, and sum of the two).

Figure 9–13 Billed Revenue Detail Revenue by Customer Type

The report in Figure 9–14 shows a graphical and table view of the total billed revenue per year by product type. Use the dashboard prompts to further filter the data.

Figure 9–14 Billed Revenue Detail Total Revenue by Product Type

The report in Figure 9–15 shows the percent of the total billed revenue by revenue type. Use the dashboard prompts to further filter the data.



Figure 9–15 Billed Revenue Detail Revenue by Revenue Type

The report in Figure 9–16 shows the percent of the total billed revenue by state. Use the dashboard prompts to further filter the data.

Figure 9–16 Billed Revenue Detail Revenue by State

The report in Figure 9–17 shows a table view of the various total revenue details. Total and gross revenue are shown by each state in the US, along with comparisons to the previous year and the year-over-year percent change.



Figure 9–17 Billed Revenue Detail Revenue Detail Report

ARPUThe report in Figure 9–18 shows the total, prepaid, and postpaid ARPU (Average Revenue Per User) per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–18 Billed Revenue ARPU Summary

The report in Figure 9–19 shows the ARPU by customer type (that is, individual or business users). Use the dashboard prompts to further filter the data.



Figure 9–19 Billed Revenue ARPU Total by Customer Type

The report in Figure 9–20 report compares the ARPU targets that the company might have established to actual the ARPU results. The difference is calculated and a flag is set based on positive or negative results.

Figure 9–20 Billed Revenue ARPU Target

The report in Figure 9–21 shows the ARPU by customer type (that is, individual or business users) in a table view. Use the dashboard prompts to further filter the data.

Figure 9–21 Billed Revenue ARPU by Customer Type

The report in Figure 9–22 shows a graphical and table view of the ARPU per year by product type. Use the dashboard prompts to further filter the data.



Figure 9–22 Billed Revenue ARPU Total by Product Type

The report in Figure 9–23 shows the percent of ARPU by each state. Use the dashboard prompts to further filter the data.

Figure 9–23 Billed Revenue ARPU by State

The report in Figure 9–24 shows a table view of the various ARPU details. The ARPU is shown by state and customer type. The report also displays comparisons to the previous year and the year-over-year percent change.



Figure 9–24 Billed Revenue ARPU Detail Report

DiscountsThe report in Figure 9–25 shows the total discounts granted (in dollars) per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–25 Billed Revenue Discounts Total

The report in Figure 9–26 shows graphical and table views of the total discounts granted per year by product type. Use the dashboard prompts to further filter the data.



Figure 9–26 Billed Revenue Discounts by Product Type

The report in Figure 9–27 shows graphical and table views of the total discounts granted per year, by customer type (that is individual versus business customers). Use the dashboard prompts to further filter the data.

Figure 9–27 Billed Revenue Discounts by Customer Type



The report in Figure 9–28 shows graphical and table views of the total discounts granted per year, by discount type. Use the dashboard prompts to further filter the data.

Figure 9–28 Billed Revenue Discounts by Discount Type

Figure 9–29 shows a table view of the discounts granted by customer type. The total discount amounts are shown by year, along with comparisons to the previous year and the year-over-year percent change.

Figure 9–29 Billed Revenue Discounts Details

Payments and CollectionsThe report in Figure 9–30 shows the total billed revenue by month. Use the slide bar and dashboard prompts to further filter the data.



Figure 9–30 Billed Revenue Payments and Collections Billed Revenue

The report in Figure 9–31 shows the total payments received per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–31 Billed Revenue Payments and Collections Payments Received

The report in Figure 9–32 shows the total revenue that is overdue and sent to a collections process. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–32 Billed Revenue Payments and Collections Revenue in Collections



The report in Figure 9–33 shows the total revenue that has been written off per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–33 Billed Revenue Payments and Collections Total Written-Off Amount

The report in Figure 9–34 shows both graphical and table views of the total revenue amount overdue and sent to a collections process, by customer type (that is, an individual versus the business customer). Use the dashboard prompts to further filter the data.

Figure 9–34 Billed Revenue Payments and Collection Amount by Customer Type

The report in Figure 9–35 shows both graphical and table views of the total revenue written off by customer type (that is, an individual versus business customer). Use the dashboard prompts to further filter the data.



Figure 9–35 Billed Revenue Payments and Collections Write Off Amount by Customer Type

The report in Figure 9–36 shows both graphical and table views of the total revenue amount assigned to a specific collection agency. Use the dashboard prompts to further filter the data.

Figure 9–36 Billed Revenue Payments and Collections by Collection Agency



The report in Figure 9–37 shows both graphical and table views of the total revenue amount that was assigned to a specific collection agency, but was written off because it could not be collected. Use the dashboard prompts to further filter the data.

Figure 9–37 Billed Revenue Payments and Collections Written-Off Amount by Collection Agency

The report in Figure 9–38 shows the amount of revenue in collections by each state in the US. Use the dashboard prompts to further filter the data.

Figure 9–38 Billed Revenue Payments and Collections by State

The report in Figure 9–39 report is a table view of payment and collection details. The report shows the total billed revenue, payments received, revenue in collections, and amounts written off. The amounts are show by customer type and year-over-year changes.



Figure 9–39 Billed Revenue Payments and Collections Details

AdjustmentsThe report in Figure 9–40 shows the total amount of adjustments made (in dollars) per month. The slide bar and dashboard prompts to further filter the data.

Figure 9–40 Billed Revenue Adjustments Total

The report in Figure 9–41 shows the total amount of adjustments made per year by customer type (that is, an individual versus the business customers). Use the dashboard prompts to further filter the data.



Figure 9–41 Billed Revenue Adjustments by Customer Type

The report in Figure 9–42 shows graphical and table views of the total adjustments made per year for each product type. Use the dashboard prompts to further filter the data.

Figure 9–42 Billed Revenue Adjustments by Product Type

The report in Figure 9–43 shows the total amount of adjustments made by the various adjustment reasons. Use the dashboard prompts to further filter the data.



Figure 9–43 Billed Revenue Adjustments by Adjustment Reason

The report in Figure 9–44 shows the total amount of adjustments made per year by the various types of adjustments. Use the dashboard prompts to further filter the data.

Figure 9–44 Billed Revenue Adjustments by Adjustment Type

The report in Figure 9–45 report is a table view of adjustment details. The report shows adjustment amounts by product type, along with year-over-year differences and percent change.



Figure 9–45 Billed Revenue Adjustments Detail Report

MapsThe report in Figure 9–46 shows the total billed revenue on a graphical map view. The greater the amount of revenue the larger the circle on the map. Hover the cursor over the circle to display the revenue amount for that area.



Figure 9–46 Billed Revenue Maps of Revenue by State and City

Billing Efficiency ReportsThe Billing Efficiency reports leverage standard TM Forum metrics that measure the operational efficiency of the service provider's billing process.

Billing CalculationsThe report in Figure 9–47 shows the number of payment transactions per payment method/Total number of payments. Payment methods include cash, credit card, debit card, check, direct debit, bank transfer, and so on.



Figure 9–47 Percent Payment Transactions by Payment Method

The report in Figure 9–48 shows the number of bills paid electronically/Total number of bills.

Bills paid electronically is the bills paid through home banking, automatic bank deduction, funds transfers, ATM transactions, and web or IVR based credit or debit card transactions. This calculation excludes payments by cash or check.

Figure 9–48 Percent of Electronic Payments (E-payments) Received

The report in Figure 9–49 shows the number of Bills with errors / Total number of bills.



The number of bills with errors includes all bills that were found to have an error, which includes errors found internally and errors reported by the customer.

Figure 9–49 Percent Bills Inaccurate

The report in Figure 9–50 shows the total elapsed time from bill cycle close to bills ready for display or dispatch. The total elapsed time includes time required for bill processing up until the bills are ready for display, but excluding the time required for posting and printing.

Figure 9–50 Time to Prepare Bills for Display and Dispatch

The report in Figure 9–51 shows the aggregate time from service activation to bill dispatch / Total number of current orders. This report includes the aggregate time for all orders in hours.



Figure 9–51 Mean Time from Service Activation to Bill Dispatch

The report in Figure 9–52 shows the aggregate time from cycle close date until bills ready for dispatch / Total number of bills. The aggregate time includes time for bill processing and printing to be completed. The calculation includes the time to process delayed calls between the close date and the actual bill run initiation.

Figure 9–52 Mean Time to Prepare and Dispatch Bills



Billing Collection and Receivables ManagementThe report in Figure 9–53 shows the aggregate value of unpaid invoices / aggregate value of all invoices, which is the total value of all customer invoices unpaid at 10 days after due date for the billing period. This excludes all paid invoices, and all internal or noncustomer invoices.

Figure 9–53 Percent Collections Efficiency Against Credit Terms

The report in Figure 9–54 shows collectible debt written off / total revenue collected.

Figure 9–54 Percent Collectible Debt Written Off

The report in Figure 9–55 shows the number of bills issued electronically / Total number of bills issued. This report for bills issued electronically excludes any bills that have an associated paper bill.



Figure 9–55 Percent Bills Issued (Electronically Issued Bills)

Billing Inquiries, Disputes, and AdjustmentsThe report in Figure 9–56 shows the number of bills adjusted in response to customer queries or complaints / Total number of bills issued. The number of bills adjusted includes all bills requiring adjustments initiated by the customer. This calculation is for all financial adjustments or credit notes. The number does not include customer-initiated changes for items such as an address change or plan adjustments.

Figure 9–56 Percent Bills Adjusted

The report in Figure 9–57 shows the number of bills adjusted due to errors found internally before bills are issued / Total number of bills issued. The number of bills adjusted in this case includes only all bills requiring adjustments initiated by internal triggers. This includes things like plan changes, address changes, financial



adjustments, credit notes, and so on, if initiated internally. This calculation excludes any customer-initiated adjustments.

Figure 9–57 Percent Bills Adjusted Internally

The report in Figure 9–58 shows the number of customer-initiated billing-related contacts / Total number of bills issued. This report includes all inbound contacts such as phone, email, and web that are relating to billing and payment inquiries. It excludes any customer-initiated changes such as address changes or plan adjustments.

Figure 9–58 Percent Billing Contacts

The report in Figure 9–59 shows the number of customer requests multiplied by 1000 / Total number of customers. The number of customer requests includes all inbound contacts such as phone, email, and web contacts. This includes all billing and payment



inquiries, all inquiries about call plans, and so on. This calculation excludes outbound and store-front contacts.

Figure 9–59 Volume of Customer Requests by Category

Customer Metrics ReportsThis section shows the reports for customer acquisition and churn metrics.

AcquisitionThe report in Figure 9–60 shows the total number of subscribers acquired per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–60 Total Acquisition Count

The report in Figure 9–61 shows the total number of subscribers acquired per year by customer type (that is, an individual or business customer). Use the dashboard prompts to further filter the data.



Figure 9–61 Total Acquisition Count by Customer Type

The report in Figure 9–62 shows the total number of subscribers acquired per year by product type. Use the dashboard prompts to further filter the data.

Figure 9–62 Total Acquisition Count by Product Type

The report in Figure 9–63 shows the percent of subscribers acquired by product type. Use the dashboard prompts to further filter the data.



Figure 9–63 Acquisition Count by Product Type (Pie Chart)

The report in Figure 9–64 shows a table view of the number of subscribers acquired per year by product offer. Use the dashboard prompts to further filter the data.

Figure 9–64 Acquisition Count by Product Offer

The report in Figure 9–65 shows the top five states in the US with the highest number of subscribers acquired. This chart can be further filtered using the dashboard prompts. The chart allows for further drill down to top cities for the given state by clicking the various bars in the chart.

Figure 9–65 Top Five Acquisitions by State



The report in Figure 9–66 shows the bottom five states with lowest number of subscribers acquired. This chart can be further filtered using the dashboard prompts. The chart allows for further drill down to the top cities for the given state by clicking the various bars in the chart.

Figure 9–66 Bottom Five Acquisitions by State

The report in Figure 9–67 shows a table view of the total acquired subscribers by state and by customer type, along with comparisons to the previous year and the year-over-year percent change.

Figure 9–67 Customer Acquisition Details



ChurnThe report in Figure 9–68 shows the total number of subscribers that have churned (that is, canceled their subscription). Use the slide bar and dashboard prompts to further filter the data.

Figure 9–68 Total Churn

The report in Figure 9–69 shows the total number of subscribers that have churned per year by customer type (that is, an individual or a business customer). Use the dashboard prompts to further filter the data.

Figure 9–69 Churn by Customer Type

The report in Figure 9–70 shows the total number of subscribers that churned per year by product type. Use the dashboard prompts to further filter the data.



Figure 9–70 Churn by Product Type

The report in Figure 9–71 shows the percent of subscribers churned by product type. Use the dashboard prompts to further filter the data.

Figure 9–71 Churn by Product Type (Pie Chart)

The chart in Figure 9–72 shows the top five states in the US with the highest number of subscribers that have churned. This chart can be further filtered using the dashboard prompts. The chart allows for further drill down to the top cities for the given state by clicking the various sections in the chart.



Figure 9–72 Top Five Churners by State

The report in Figure 9–73 shows the bottom five states in the US with the lowest number of subscribers that have churned. This chart can be further filtered using the dashboard prompts. The chart allows for further drill down to the top cities for the given state by clicking the various bars in the chart.

Figure 9–73 Bottom Five Churners by State

The report in Figure 9–74 shows a table view of the total number of subscribers that have churned by state and by customer type, along with comparisons to the previous year and the year-over-year percent change.



Figure 9–74 Churn Detail Report

Prepaid Metrics ReportsThe prepaid metrics reports show details for prepaid-specific metrics such as total, average recharges, and disturbed recharge cycles.

Recharges ReportsThe report in Figure 9–75 shows the total number of recharges per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–75 Prepaid Metrics Total Number of Recharges



The report in Figure 9–76 shows the total monetary value of recharges per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–76 Prepaid Metrics Total Amount of Recharges

The report in Figure 9–77 shows a table view of the total number of recharges and the monetary value of the recharges per year. Users can make use dashboard prompts to further filter the data.

Figure 9–77 Prepaid Metrics Total Recharges

Prepaid Customer Base ReportsThe report in Figure 9–78 shows the total number of active prepaid customers per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–78 Prepaid Customer Base Active Customers Report



The report in Figure 9–79 shows the total number of inactive prepaid customers per month (that is, have a positive prepaid balance, but have had no usage activity for a period). Use the slide bar and dashboard prompts to further filter the data.

Figure 9–79 Prepaid Customer Base Inactive Customers Report

The report in Figure 9–80 shows a table view of active and inactive prepaid customers with positive balances, and customers with a zero balance. The results are shown per year and per quarter. Users can make use dashboard prompts to further filter the data.

Figure 9–80 Prepaid Customer Base Total Customers Report

Account RechargeThe report in Figure 9–81 shows both a graph and table view of the count of subscribers recharging their prepaid accounts within a specific number of days. The graph view shows results by customer type, and the table view shows results by customer type and product type. Users can make use dashboard prompts to further filter the data.



Figure 9–81 Prepaid Metrics Account Recharge Report

Disturbed RechargeThe report in Figure 9–82 shows a table view of customers with disturbed recharge cycles, meaning the last time they recharged their account is greater than their typical recharge pattern. The table shows the number of days since their last recharge, the number of disturbed recharge days (that is, days over their typical pattern), and the percent disturbance. In addition to day counts, the table shows the monetary value of the customer's last recharge and amount for the last three months.



Figure 9–82 Prepaid Metrics Disturbed Recharge Report

Usage Revenue ReportsThe usage revenue reports provide usage specific metrics such as the total minutes of usage, number of calls, top and users (voice, data, SMS and MMS).

Voice UsageThe report in Figure 9–83 shows the total number of voice calls (inbound and outbound) per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–83 Usage Revenue Voice Usage Total Number of Calls

The report in Figure 9–84 shows the total number of minutes used for voice calls (inbound and outbound) per month. Use the slide bar and dashboard prompts to further filter the data.



Figure 9–84 Usage Revenue Voice Usage Total Minutes of Use

The report in Figure 9–85 shows the total number of voice roaming calls (inbound and outbound) per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–85 Usage Revenue Voice Usage Total Number of Calls (Roaming)

The report in Figure 9–86 shows the total number of minutes used for voice roaming calls (inbound and outbound) per month. Use the slide bar and dashboard prompts to further filter the data.



Figure 9–86 Usage Revenue Voice Usage Total Minutes of Use (Roaming)

The report in Figure 9–87 shows the total number roaming and nonroaming voice calls per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–87 Usage Revenue Voice Usage Number of Calls (Roaming versus Nonroaming)

The report in Figure 9–88 shows the total number of minutes used for roaming and nonroaming voice calls per month. Use the slide bar and dashboard prompts to further filter the data.



Figure 9–88 Usage Revenue Minutes of Use (Roaming versus Nonroaming)

The report in Figure 9–89 shows the total number of on-net versus off-net voice calls per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–89 Usage Revenue Voice Usage On Net versus Off Net

Voice Usage RevenueThe report in Figure 9–90 shows the total amount of usage revenue associated with voice calls per month. Use the slide bar and dashboard prompts to further filter the data.



Figure 9–90 Voice Usage Revenue Total Usage Revenue

The report in Figure 9–91 shows the total amount of usage revenue associated with voice roaming calls per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–91 Voice Usage Revenue Roaming Usage Revenue

The report in Figure 9–92 shows the total amount of usage revenue associated with international versus local calls per month. Use the slide bar and dashboard prompts to further filter the data.



Figure 9–92 Voice Usage Revenue by Distance

The report in Figure 9–93 shows the total number of minutes associated with international versus local calls per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–93 Voice Usage Revenue Total Minutes by Distance

The report in Figure 9–94 shows the average usage revenue per minute of use for voice calls per month. Use the slide bar and dashboard prompts to further filter the data.



Figure 9–94 Voice Usage Revenue Average Revenue per Minute of Use

The report in Figure 9–95 shows the total amount of usage revenue for on-net versus off-net calls per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–95 Voice Usage Revenue On Net versus Off Net

Data UsageThe report in Figure 9–96 shows the total amount of data usage per month. Use the slide bar and dashboard prompts to further filter the data.



Figure 9–96 Data Usage Total Data Usage

The report in Figure 9–97 shows the total amount of data usage revenue per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–97 Data Usage Total Data Revenue

SMS UsageThe report in Figure 9–98 shows the total amount of SMS revenue per month. Use the slide bar and dashboard prompts to further filter the data.



Figure 9–98 SMS Usage Total SMS Revenue

The report in Figure 9–99 shows the total number of SMS messages sent per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–99 SMS Usage Total SMS Usage

MMS UsageThe report in Figure 9–100 shows the total amount of MMS usage revenue per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–100 MMS Usage Total MMS Revenue



The report in Figure 9–101 shows the total number of MMS messages sent per month. Use the slide bar and dashboard prompts to further filter the data.

Figure 9–101 MMS Usage Total MMS Usage

10

Billing Analytics Reference 10-1

10Billing Analytics Reference

This chapter provides information on Billing Analytics tables, relationships, and measures.

Billing Analytics Physical ObjectsTable 10–1 shows the Oracle Communications Data Model physical objects associated with the Billing Analytics reports.

Table 10–1 Physical Objects for Billing Analytics

Oracle Communications Data Model Objects for Billing Analytics

DWA_CNT_MO

DWA_RVN_MO

DWB_INVC_ITEM

DWD_ACCT_DEBT_MO

DWD_CNT_DAY

DWD_DATA_USG_DAY

DWD_PRPD_ACCT_STTSTC_DAY

DWD_TMF_KPI

DWD_VAS_USG_DAY

DWD_VOI_CALL_DAY

DWL_CALL_TYP

DWL_CUST_TYP

DWL_INVC_ADJ_RSN

DWL_INVC_ADJ_TYP

DWL_INVC_DISC_TYP

DWL_PRTY_TYP

DWL_RMNG_TYP

DWR_ACCT

DWR_CNTNT

DWR_COLLCTN_AGNCY

DWR_CUST

DWR_DAY

Billing Analytics Relationships and Measures



DWB_INVC_ITEM Analytics

DWR_GEO_CITY

DWR_GEO_CNTRY

DWR_GEO_CNTY

DWR_GEO_STATE

DWR_ORG_BSNS_UNIT

DWR_PROD_OFR

DWR_PROD_SPEC

DWV_PRPD_CUST_STAT (Oracle Business Intelligence Enterprise Edition View)

Table 10–2 DWB_INVC_ITEM Analytics

Component Description

Base Table Not Applicable

Derived Table DWB_INVC_ITEM

Intra-ETL Not required because this is a base table

Table 10–1 (Cont.) Physical Objects for Billing Analytics

Oracle Communications Data Model Objects for Billing Analytics



Figure 10–1 DWB_INVC_ITEM Relationships

Table 10–3 DWB_INVC_ITEM Relationships

Relationship

"Billing Analytics".""."OCDM_BILLING"."DWR_PROD_SPEC"."PROD_SPEC_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWB_INVC_ITEM"."PROD_SPEC_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_CUST"."CUST_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWB_INVC_ITEM"."CUST_KEY"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."CLNDR_DT" = cast("Billing Analytics".""."OCDM_BILLING"."DWB_INVC_ITEM"."BLLG_DT" as date)

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."BSNS_DT" = cast("Billing Analytics".""."OCDM_BILLING"."DWB_INVC_ITEM"."BLLG_DT" as date)

"Billing Analytics".""."OCDM_BILLING"."DWL_INVC_ADJ_RSN"."INVC_ADJ_RSN_CD" = "Billing Analytics".""."OCDM_BILLING"."DWB_INVC_ITEM"."INVC_ADJ_RSN_CD"



DWD_ACCT_BAL_MO Analytics

"Billing Analytics".""."OCDM_BILLING"."DWL_INVC_ADJ_TYP"."INVC_ADJ_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWB_INVC_ITEM"."INVC_ADJ_TYP_CD"

"Billing Analytics".""."OCDM_BILLING"."DWR_ORG_BSNS_UNIT"."ORG_BSNS_UNIT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWB_INVC_ITEM"."ORG_BSNS_UNIT_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWL_INVC_DISC_TYP"."INVC_DISC_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWB_INVC_ITEM"."INVC_DISC_TYP_CD"

Table 10–4 DWB_INVC_ITEM Facts and Calculated Measures

Measure Description

Adjustment Value sum(DWB_INVC_ITEM.ADJD_AMT)

Discount Value sum(DWB_INVC_ITEM.DISC_AMT)

Adjustment LY ago("Billing Analytics"."Dwb Invc Item"."Adjustment Value", "Billing Analytics"."Calendar Daydim"."Year",1 )

Discount LY ago("Billing Analytics"."Dwb Invc Item"."Discount Value", "Billing Analytics"."Calendar Daydim"."Year",1 )

% Change of Adjustment (("Billing Analytics"."Dwb Invc Item"."Adjustment Value" - "Billing Analytics"."Dwb Invc Item"."Adjustment LY" ) / "Billing Analytics"."Dwb Invc Item"."Adjustment LY" ) * 100

% Change of Discount (("Billing Analytics"."Dwb Invc Item"."Discount Value" - "Billing Analytics"."Dwb Invc Item"."Discount LY" ) / "Billing Analytics"."Dwb Invc Item"."Discount LY" ) * 100

Table 10–5 DWD_ACCT_BAL_MO Analytics


Base Tables ■ DWB_ACCT_BAL

■ DWB_ACCT_BAL_IMPC

■ DWB_UNIT_ALWNCE

Derived Table DWD_ACCT_BAL_MO

Intra-ETL dwd_acct_bal_mo_pkg

Table 10–3 (Cont.) DWB_INVC_ITEM Relationships

Relationship



Figure 10–2 DWD_ACCT_BAL_MO Relationships

Table 10–6 DWD_ACCT_BAL_MO Relationships

Relationship

"Billing Analytics".""."OCDM_BILLING"."DWR_PROD_SPEC"."PROD_SPEC_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_BAL_MO"."PROD_SPEC_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ACCT"."ACCT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_BAL_MO"."ACCT_KEY"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_BAL_MO"."MO_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ACCT_STAT"."ACCT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_BAL_MO"."ACCT_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWL_ACCT_BAL_TYP"."ACCT_BAL_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_BAL_MO"."ACCT_BAL_TYP_CD"

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."BSNS_DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_BAL_MO"."MO_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_PROD_OFR"."PROD_OFR_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_BAL_MO"."PROD_OFR_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_CUST"."CUST_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_BAL_MO"."CUST_KEY"



DWD_ACCT_DEPT_MO Analytics

Table 10–7 DWD_ACCT_BAL_MO Facts and Calculated Measures

Measure Description

Bonus Value sum(DWD_ACCT_BAL_MO.PPA_BONUS_ORIG_BAL_AMT)

Carried Forward Value last(DWD_ACCT_BAL_MO.PPA_BONUS_MAX_CARRIED_FRWD_AMT)

Ppa Value sum(DWD_ACCT_BAL_MO.PPA_ORIG_BAL_AMT)

Adjustment Value sum(DWD_ACCT_BAL_MO.ADJD_AMT)

Adjustment LY Ago(sum(DWD_ACCT_BAL_MO.ADJD_AMT), [Level Year], 1)

% Change of Adjustment (("Billing Analytics"."Dwd Acct Bal Mo"."Adjustment Value" - "Billing Analytics"."Dwd Acct Bal Mo"."Adjustment LY" ) / "Billing Analytics"."Dwd Acct Bal Mo"."Adjustment LY" ) *100

Inactive Customer count(distinct case when DWR_ACCT_STAT.STAT_CD <> 'A' and DWD_ACCT_BAL_MO.MAX_BAL_EXP_DT < DATE '2013-06-28' then DWD_ACCT_BAL_MO.ACCT_KEY end )

Active Customer count(distinct case when DWR_ACCT_STAT.STAT_CD <> 'A' and DWD_ACCT_BAL_MO.MAX_BAL_EXP_DT >= DATE '2013-06-28' then DWD_ACCT_BAL_MO.ACCT_KEY else 0 end )

Zero Balance Customer count(distinct case when DWD_ACCT_BAL_MO.BAL_AMT = 0 and DWD_ACCT_BAL_MO.MAX_BAL_EXP_DT >= DATE '2013-06-28' then DWD_ACCT_BAL_MO.ACCT_KEY end )

Total Utilization sum(DWD_ACCT_BAL_MO.UTILZD_AMT)

Bonus Utilization sum(case when DWD_ACCT_BAL_MO.PPA_BONUS_ORIG_BAL_AMT >= DWD_ACCT_BAL_MO.UTILZD_AMT then ifnull(DWD_ACCT_BAL_MO.PPA_BONUS_ORIG_BAL_AMT , 0) else ifnull(DWD_ACCT_BAL_MO.UTILZD_AMT , 0) end )

Utilized Value CASE WHEN IFNULL("Billing Analytics"."Dwd Acct Bal Mo"."Total Utilization", 0) - IFNULL("Billing Analytics"."Dwd Acct Bal Mo"."Bonus Utilization", 0 ) > 0 THEN IFNULL("Billing Analytics"."Dwd Acct Bal Mo"."Total Utilization", 0) - IFNULL("Billing Analytics"."Dwd Acct Bal Mo"."Bonus Utilization", 0 ) ELSE 0 END

Total Allowance Value IFNULL("Billing Analytics"."Dwd Acct Bal Mo"."Bonus Value" ,0) + IFNULL("Billing Analytics"."Dwd Acct Bal Mo"."Carried Forward Value" ,0) + IFNULL("Billing Analytics"."Dwd Acct Bal Mo"."Ppa Value",0) + IFNULL("Billing Analytics"."Dwd Acct Bal Mo"."Utilized Value",0 )

Total Allowance Value LY AGO("Billing Analytics"."Dwd Acct Bal Mo"."Total Allowance Value", "Billing Analytics"."Calendar Daydim"."Quarter",1 )

Bonus Value LY AGO("Billing Analytics"."Dwd Acct Bal Mo"."Bonus Value", "Billing Analytics"."Calendar Daydim"."Year" ,1 )

Table 10–8 DWD_ACCT_DEPT_MO Analytics


Base Table ■ DWB_INVC INVC

■ DWB_INVC_ADJ INVC_ADJ

■ DWB_INVC_PYMT_ASGN

■ INVC_PYMT_ASGN

■ DWB_ACCT_PYMT PYMT

■ DWR_ACCT ACCT

■ DWR_ADDR_LOC ADDR

■ DWR_CUST CUST

Derived Table DWD_ACCT_DEPT_MO

Intra-ETL dwd_acct_debt_mo_pkg



Figure 10–3 DWD_ACCT_DEPT_MO Relationships

Table 10–9 DWD_ACCT_DEPT_MO Relationships

Relationship

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."BSNS_DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_DEBT_MO"."MO_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_CUST"."CUST_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_DEBT_MO"."CUST_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_GEO_CNTY"."GEO_CNTY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_DEBT_MO"."GEO_CNTY_KEY"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_DEBT_MO"."MO_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ORG_BSNS_UNIT"."ORG_BSNS_UNIT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_DEBT_MO"."ORG_BSNS_UNIT_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWL_CUST_TYP"."CUST_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_DEBT_MO"."CUST_TYP_CD"

"Billing Analytics".""."OCDM_BILLING"."DWR_COLLCTN_AGNCY"."COLLCTN_AGNCY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_DEBT_MO"."COLLCTN_AGNCY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ACCT"."ACCT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_DEBT_MO"."ACCT_KEY"



DWD_ACCT_PYMT_DAY Analytics

Table 10–10 DWD_ACCT_DEPT_MO Facts and Calculated Measures

Measure Description

Payment Collected Amount sum(DWD_ACCT_DEBT_MO.TOT_PYMT_COLCTD_AMT)

Waiving Amount sum(DWD_ACCT_DEBT_MO.TOT_WVNG_AMT)

Payment Collected Amount Ly Ago("Billing Analytics"."Dwd Acct Debt Mo"."Payment Collected Amount" , "Billing Analytics"."Calendar Daydim"."Year" , 1)

Waving Amount Ly Ago("Billing Analytics"."Dwd Acct Debt Mo"."Waiving Amount" , "Billing Analytics"."Calendar Daydim"."Year" , 1)

Write Off Amount sum(DWD_ACCT_DEBT_MO.TOT_WRT_OFF_AMT)

Write Off Amount Ly Ago("Billing Analytics"."Dwd Acct Debt Mo"."Write Off Amount" , "Billing Analytics"."Calendar Daydim"."Year" , 1)

Payment Collected Amount % Change

(("Billing Analytics"."Dwd Acct Debt Mo"."Payment Collected Amount" - "Billing Analytics"."Dwd Acct Debt Mo"."Payment Collected Amount Ly" ) / "Billing Analytics"."Dwd Acct Debt Mo"."Payment Collected Amount Ly" ) * 100

Billed Revenue sum(DWD_ACCT_DEBT_MO.CURR_INVC_AMT)

Billed Revenue Ly Ago("Billing Analytics"."Dwd Acct Debt Mo"."Billed Revenue" , "Billing Analytics"."Calendar Daydim"."Year" , 1)

Total Written Off Amount IFNULL("Billing Analytics"."Dwd Acct Debt Mo"."Waiving Amount" , 0) + IFNULL("Billing Analytics"."Dwd Acct Debt Mo"."Write Off Amount" ,0)

Total Penalty Amount sum(DWD_ACCT_DEBT_MO.TOT_PNLTY_AMT)

Revenue In Collections ifnull("Billing Analytics"."Dwd Acct Debt Mo"."Payment Collected Amount" ,0) + ifnull("Billing Analytics"."Dwd Acct Debt Mo"."Total Penalty Amount" , 0)

Tot Written Off Amount Ly Ago(sum(DWD_ACCT_DEBT_MO.TOT_WRT_OFF_AMT), [Level Year], 1)

Revenue In Collections Ly ago("Billing Analytics"."Dwd Acct Debt Mo"."Revenue In Collections", "Billing Analytics"."Calendar Daydim"."Year", 1 )

Table 10–11 DWD_ACCT_PYMT_DAY Analytics


Base Table ■ DWB_ACCT_PYMT

■ DWB_INVC_PYMT_ASGN

■ DWB_INVC

■ DWV_AGRMNT_ACCT_SBRP_PROD

Derived Table DWD_ACCT_PYMT_DAY

Intra-ETL dwd_acct_pymt_day_pkg



Figure 10–4 DWD_ACCT_PYMT_DAY Relationships

Table 10–12 DWD_ACCT_PYMT_DAY Relationships

Relationship

"Billing Analytics".""."OCDM_BILLING"."DWR_CUST"."CUST_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_PYMT_DAY"."CUST_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ACCT"."ACCT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_PYMT_DAY"."ACCT_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_PYMT_DAY"."DAY_KEY"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_PYMT_DAY"."DAY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWL_ACCT_TYP"."ACCT_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_ACCT_PYMT_DAY"."ACCT_TYP_CD"

Table 10–13 DWD_ACCT_PYMT_DAY Facts and Calculated Measures

Measure Description

Total Amount of Recharge sum(cast(DWD_ACCT_PYMT_DAY.TOT_PYMT_AMT as INTEGER ) )

Total Count of Recharge sum(DWD_ACCT_PYMT_DAY.PYMT_SUCC_CNT)

Avg 3 Months Count of Recharge (PeriodRolling( "Billing Analytics"."Dwd Acct Pymt Day"."Total Count Of Recharge" , -2,0))/3

Avg 3 Months Amount of Recharge

(PeriodRolling("Billing Analytics"."Dwd Acct Pymt Day"."Total Amount Of Recharge" , -2,0))/3

Avg Total Recharge Value "Billing Analytics"."Dwd Acct Pymt Day"."Total Amount Of Recharge" /"Billing Analytics"."Dwd Acct Pymt Day"."Total Count Of Recharge"



DWD_CNT_DAY Analytics

Count of Days sum(case when DWD_ACCT_PYMT_DAY.PYMT_RSN_CD = 'RCHRG' then DWD_ACCT_PYMT_DAY.TOT_PYMT_CNT else 0 end )

Average Days Between Recharges "Billing Analytics"."Dwd Acct Pymt Day"."Total Count Of Recharge" /"Billing Analytics"."Dwd Acct Pymt Day"."Count Of Days"

Total Count of Recharge LY Ago("Billing Analytics"."Dwd Acct Pymt Day"."Total Count Of Recharge" , "Billing Analytics"."Calendar Daydim"."Year" , 1)

Total Amount of Recharge LY Ago("Billing Analytics"."Dwd Acct Pymt Day"."Total Amount Of Recharge" , "Billing Analytics"."Calendar Daydim"."Year" , 1)

Total Count of Recharge % Change LY

(("Billing Analytics"."Dwd Acct Pymt Day"."Total Count Of Recharge" -"Billing Analytics"."Dwd Acct Pymt Day"."Total Count Of Recharge LY" )/"Billing Analytics"."Dwd Acct Pymt Day"."Total Count Of Recharge LY" )*100

Total Amount of Recharge % Change LY

(("Billing Analytics"."Dwd Acct Pymt Day"."Total Amount Of Recharge" -"Billing Analytics"."Dwd Acct Pymt Day"."Total Amount Of Recharge LY" )/"Billing Analytics"."Dwd Acct Pymt Day"."Total Amount Of Recharge LY" )*100

Last Recharge Date max(DWD_ACCT_PYMT_DAY.CUST_START_DT)

Current Amount of Days Since Last Recharge

TimeStampDiff(SQL_TSI_DAY, "Billing Analytics"."Dwd Acct Pymt Day"."Last Recharge Date" , CURRENT_DATE)

Number Of Days Disturbed Recharge Cycle

"Billing Analytics"."Dwd Acct Pymt Day"."Current Amount Of Days Since Last Recharge" - "Billing Analytics"."Dwd Acct Pymt Day"."Average Days Between Recharges"

% Disturbance ("Billing Analytics"."Dwd Acct Pymt Day"."Number Of Days Disturbed Recharge Cycle" / "Billing Analytics"."Dwd Acct Pymt Day"."Average Days Between Recharges" ) * 100

Table 10–14 DWD_CNT_DAY Analytics


Base Table ■ DWR_ADDR_LOC

■ DWR_CUST

■ DWR_PROD_SBRP

■ V_PROD_OFR_HIE

■ V_PROD_SPEC_HIE

■ DWR_ACCT

■ DWR_AGRMNT AGRMNT

Derived Tables DWD_CNT_DAY

DWA_CNT_MO

Intra-ETL dwd_cnt_day_pkg

Table 10–13 (Cont.) DWD_ACCT_PYMT_DAY Facts and Calculated Measures

Measure Description



Figure 10–5 DWD_CNT_DAY Relationships

Table 10–15 DWD_CNT_DAY Relationships

Relationship

"Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO"."PROD_OFR_LVL" = 'PROD_OFR_KEY' and TRIM(CAST("Billing Analytics".""."OCDM_BILLING"."DWR_PROD_OFR"."PROD_OFR_KEY" AS CHAR)) = "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO"."PROD_OFR_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."BSNS_DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO"."MO_KEY"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO"."MO_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_GEO_CNTY"."GEO_CNTY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO"."GEO_CNTY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO"."PROD_SPEC_LVL" = 'PROD_SPEC_KEY' and TRIM(CAST("Billing Analytics".""."OCDM_BILLING"."DWR_PROD_SPEC"."PROD_SPEC_KEY" AS CHAR)) = "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO"."PROD_SPEC_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ORG_BSNS_UNIT"."ORG_BSNS_UNIT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO"."ORG_BSNS_UNIT_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWL_CUST_TYP"."CUST_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO"."CUST_TYP_CD"



DWD_DATA_USG_DAY Analytics

Table 10–16 DWD_CNT_DAY Facts and Calculated Measures

Measure Description

Total Acquisition Count sum(DWA_CNT_MO.NEW_ACTV_PROD_SBRP_CNT)

Total Acquisition Count LY ago("Billing Analytics"."Dwd Count Day"."Total Acquisition Count", "Billing Analytics"."Calendar Daydim"."Year" ,1 )

Involuntary Churn Count sum(DWA_CNT_MO.INVLTRY_DACTD_PODSBP_TSPD_CNT)

Voluntary Churn Count sum(DWA_CNT_MO.VLTRY_DACTDPROD_SBRP_TSPD_CNT)

Churn Count ifnull("Billing Analytics"."Dwd Count Day"."Involuntary Churn Count" , 0) + ifnull("Billing Analytics"."Dwd Count Day"."Voluntary Churn Count", 0 )

Churn Count LY ago("Billing Analytics"."Dwd Count Day"."Churn Count", "Billing Analytics"."Calendar Daydim"."Year", 1 )

Churn Count % Change LY (("Billing Analytics"."Dwd Count Day"."Churn Count" - "Billing Analytics"."Dwd Count Day"."Churn Count LY" ) / "Billing Analytics"."Dwd Count Day"."Churn Count LY" ) * 100

Prod Spec Cd CASE "Billing Analytics"."Dwd Count Day"."Prod Spec Lvl" WHEN 'PROD_SPEC_TYP_CD' THEN '-5000' WHEN 'TPROD_SPEC' THEN '-5000' WHEN 'PROD_SPEC_KEY' THEN "Billing Analytics"."Dwr Prod Spec"."Prod Spec Cd" END

Prod Spec Typ Cd CASE "Billing Analytics"."Dwd Count Day"."Prod Spec Lvl" WHEN 'PROD_SPEC_TYP_CD' THEN "Billing Analytics"."Dwd Count Day"."Prod Spec Key" WHEN 'TPROD_SPEC' THEN 'N/A' WHEN 'PROD_SPEC_KEY' THEN "Billing Analytics"."Dwr Prod Spec"."Prod Spec Typ Cd" END

Prod Ofr Name CASE "Billing Analytics"."Dwd Count Day"."Prod Ofr Lvl" WHEN 'PROD_OFR_KEY' THEN "Billing Analytics"."Dwr Prod Ofr"."Prod Ofr Name" ELSE '-5000' END

Acquisition % Change (("Billing Analytics"."Dwd Count Day"."Total Acquisition Count" - "Billing Analytics"."Dwd Count Day"."Total Acquisition Count LY" ) / "Billing Analytics"."Dwd Count Day"."Total Acquisition Count LY" ) * 100

Pln Typ CASE "Billing Analytics"."Dwd Count Day"."Prod Ofr Lvl" WHEN 'PLN_TYP' THEN "Billing Analytics"."Dwd Count Day"."Prod Ofr Key" WHEN 'PROD_OFR_KEY' THEN IFNULL("Billing Analytics"."Dwr Prod Ofr"."Pln Typ", 'N/A') else 'N/A' END

Table 10–17 DWD_DATA_USG_DAY Analytics


Base Table ■ DWB_CNTNT_DLVRY_EVT

■ DWB_WRLS_CNTNT_DNLDG_EVT

Derived Table DWD_DATA_USG_DAY

Intra-ETL dwd_data_usg_day_pkg



Figure 10–6 DWD_DATA_USG_DAY Relationships

Table 10–18 DWD_DATA_USG_DAY Relationships

Relationship

"Billing Analytics".""."OCDM_BILLING"."DWR_PRTY"."PRTY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_DATA_USG_DAY"."RMNG_OPRTR_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWL_CUST_TYP"."CUST_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_DATA_USG_DAY"."CUST_TYP_CD"

"Billing Analytics".""."OCDM_BILLING"."DWR_GEO_CNTY"."GEO_CNTY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_DATA_USG_DAY"."GEO_CNTY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWL_RMNG_TYP"."RMNG_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_DATA_USG_DAY"."RMNG_TYP_CD"

"Billing Analytics".""."OCDM_BILLING"."DWR_PROD_OFR"."PROD_OFR_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_DATA_USG_DAY"."PROD_OFR_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ORG_BSNS_UNIT"."ORG_BSNS_UNIT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_DATA_USG_DAY"."ORG_BSNS_UNIT_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_CNTNT"."CNTNT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_DATA_USG_DAY"."CNTNT_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."BSNS_DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_DATA_USG_DAY"."DAY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWL_CALL_TYP"."CALL_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_DATA_USG_DAY"."USG_TYP"

"Billing Analytics".""."OCDM_BILLING"."DWR_PROD_SPEC"."PROD_SPEC_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_DATA_USG_DAY"."PROD_SPEC_KEY"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_DATA_USG_DAY"."DAY_KEY"



DWD_INVC_DAY Analytics

Figure 10–7 DWD_INVC_DAY Relationships

Table 10–19 DWD_DATA_USG_DAY Facts and Calculated Measures

Measure Description

Inbound Transferred Bytes sum(DWD_DATA_USG_DAY.TOT_BYTES_TRNSFRD_INBND)

Outbound Transferred Bytes sum(DWD_DATA_USG_DAY.TOT_BYTES_TRNSFRD_OUTBND)

Bytes Used ifnull("Billing Analytics"."Dwd Data Usg Day"."Inbound Transferred Bytes", 0 ) + ifnull("Billing Analytics"."Dwd Data Usg Day"."Outbound Transferred Bytes", 0 )

Data Revenue sum(DWD_DATA_USG_DAY.CHRGD_AMT)

Table 10–20 DWD_INVC_DAY Analytics


Base Table ■ DWB_INVC

■ DWB_INVC_ITEM

Derived Table DWD_INVC_DAY

Intra-ETL dwd_invc_day_pkg



DWD_PRPD_ACCT_STTSTC_DAY Analytics

Table 10–21 DWD_INVC_DAY Relationships

Relationships

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."BSNS_DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_INVC_DAY"."DAY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWL_CUST_TYP"."CUST_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_INVC_DAY"."CUST_TYP_CD"

"Billing Analytics".""."OCDM_BILLING"."DWR_ORG_BSNS_UNIT"."ORG_BSNS_UNIT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_INVC_DAY"."ORG_BSNS_UNIT_KEY"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_INVC_DAY"."DAY_KEY"

Table 10–22 DWD_INVC_DAY Facts and Calculated Measures

Measure Calculation

Discount Value sum(DWD_INVC_DAY.BLNG_DISC_AMT)

Discount LY ago("Billing Analytics"."Dwd Invc Day"."Discount Value", "Billing Analytics"."Calendar Daydim"."Year", 1 )

% Change of Discount (("Billing Analytics"."Dwd Invc Day"."Discount Value" - "Billing Analytics"."Dwd Invc Day"."Discount LY" ) / "Billing Analytics"."Dwd Invc Day"."Discount LY" ) * 100

Table 10–23 DWD_PRPD_ACCT_STTSTC_DAY Analytics


Base Table ■ DWB_ACCT_PYMT

■ DWR_ACCT

■ DWR_AGRMNT

Derived Table DWD_PRPD_ACCT_STTSTC_DAY

Intra-ETL dwd_prpd_acct_sttstc_day_pkg



Figure 10–8 DWD_PRPD_ACCT_STTSTC_DAY Relationships

Table 10–24 DWD_PRPD_ACCT_STTSTC_DAY Relationships

Relationships

"Billing Analytics".""."OCDM_BILLING"."DWR_CUST"."CUST_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_PRPD_ACCT_STTSTC_DAY"."CUST_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_PROD_SPEC"."PROD_SPEC_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_PRPD_ACCT_STTSTC_DAY"."PROD_SPEC_KEY"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_PRPD_ACCT_STTSTC_DAY"."DAY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."BSNS_DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_PRPD_ACCT_STTSTC_DAY"."DAY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ACCT"."ACCT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_PRPD_ACCT_STTSTC_DAY"."ACCT_KEY"



DWD_RVN_DAY Analytics

Table 10–25 DWD_PRPD_ACCT_STTSTC_DAY Facts and Calculated Measures

Measure Description

Total Amount of Recharge sum(DWD_PRPD_ACCT_STTSTC_DAY.TOT_RCHRG_AMT)

Total Count of Recharge sum(DWD_PRPD_ACCT_STTSTC_DAY.TOT_RCHRG_CNT)

Total Amount of Recharge LY ago("Billing Analytics"."Dwd Prpd Acct Sttstc Day"."Total Amount Of Recharge" , "Billing Analytics"."Calendar Daydim"."Year",1 )

Total Count of Recharge LY ago("Billing Analytics"."Dwd Prpd Acct Sttstc Day"."Total Count Of Recharge", "Billing Analytics"."Calendar Daydim"."Year",1 )

Total Amount of Recharge % Change LY

(("Billing Analytics"."Dwd Prpd Acct Sttstc Day"."Total Amount Of Recharge" - "Billing Analytics"."Dwd Prpd Acct Sttstc Day"."Total Amount Of Recharge LY" ) / "Billing Analytics"."Dwd Prpd Acct Sttstc Day"."Total Amount Of Recharge LY" ) * 100

Total Count of Recharge % Change LY

(("Billing Analytics"."Dwd Prpd Acct Sttstc Day"."Total Count Of Recharge" - "Billing Analytics"."Dwd Prpd Acct Sttstc Day"."Total Count Of Recharge LY" )/ "Billing Analytics"."Dwd Prpd Acct Sttstc Day"."Total Count Of Recharge LY" ) * 100

Table 10–26 DWD_RVN_DAY Analytics


Base Table ■ DWB_INVC

■ DWB_INVC_ITEM

■ DWB_ACCT_BAL

■ DWD_VAS_USG_DAY

■ DWD_DATA_USG_DAY

■ DWD_VOI_CALL_DAY

Derived Table DWD_RVN_DAY

DWA_RVN_MO

Intra-ETL dwd_rnv_day_pkg



Figure 10–9 DWD_RVN_DAY Relationship

Table 10–27 DWD_RVN_DAY Relationships

Relationships

"Billing Analytics".""."OCDM_BILLING"."DWL_CUST_TYP"."CUST_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."CUST_TYP_CD"

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."BSNS_DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."MO_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."PROD_OFR_LVL" = 'PROD_OFR_KEY' and TRIM(CAST("Billing Analytics".""."OCDM_BILLING"."DWR_PROD_OFR"."PROD_OFR_KEY" AS CHAR)) = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."PROD_OFR_KEY"



"Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO_ARPU"."MO_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."MO_KEY" AND "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO_ARPU"."CUST_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."CUST_TYP_CD" AND "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO_ARPU"."GEO_CNTY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."GEO_CNTY_KEY" AND "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO_ARPU"."ORG_BSNS_UNIT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."ORG_BSNS_UNIT_KEY" AND "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO_ARPU"."PLN_TYP" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."PLN_TYP" AND "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO_ARPU"."SL_CHNL_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."SL_CHNL_KEY" AND "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO_ARPU"."PROD_OFR_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."PROD_OFR_KEY" AND "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO_ARPU"."PROD_OFR_LVL" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."PROD_OFR_LVL" AND "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO_ARPU"."PROD_SPEC_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."PROD_SPEC_KEY" AND "Billing Analytics".""."OCDM_BILLING"."DWA_CNT_MO_ARPU"."PROD_SPEC_LVL" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."PROD_SPEC_LVL"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."MO_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."PROD_SPEC_LVL" = 'PROD_SPEC_KEY' and TRIM(CAST("Billing Analytics".""."OCDM_BILLING"."DWR_PROD_SPEC"."PROD_SPEC_KEY" AS CHAR)) = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."PROD_SPEC_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ORG_BSNS_UNIT"."ORG_BSNS_UNIT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."ORG_BSNS_UNIT_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_GEO_CNTY"."GEO_CNTY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWA_RVN_MO"."GEO_CNTY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWD_RVN_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWVSBRPCNT"."DAY_KEY"

and "Billing Analytics".""."OCDM_BILLING"."DWD_RVN_DAY"."GEO_CNTY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWVSBRPCNT"."GEO_CNTY_KEY"

and "Billing Analytics".""."OCDM_BILLING"."DWVSBRPCNT"."ORG_BSNS_UNIT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_RVN_DAY"."ORG_BSNS_UNIT_KEY"

and "Billing Analytics".""."OCDM_BILLING"."DWVSBRPCNT"."CUST_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_RVN_DAY"."CUST_TYP_CD"

and "Billing Analytics".""."OCDM_BILLING"."DWVSBRPCNT"."PLN_TYP" = "Billing Analytics".""."OCDM_BILLING"."DWD_RVN_DAY"."PLN_TYP"

"Billing Analytics".""."OCDM_BILLING"."DWR_PROD_SPEC"."PROD_SPEC_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_RVN_DAY"."PROD_SPEC_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ORG_BSNS_UNIT"."ORG_BSNS_UNIT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_RVN_DAY"."ORG_BSNS_UNIT_KEY"

Table 10–28 DWD_RVN_DAYFacts and Calculated Measures

Measure Description

Usage Revenue sum(DWA_RVN_MO.USG_RVN_INVCD)

Expired Revenue sum(DWA_RVN_MO.EXPIRED_RVN)

Prepaid Revenue sum(case when DWA_RVN_MO.PLN_TYP = 'PREPAID' then ifnull(DWA_RVN_MO.EXPIRED_RVN , 0) + ifnull(DWA_RVN_MO.USG_RVN_INVCD , 0) else 0 end )

Recurring Bill sum(DWA_RVN_MO.RCRNG_ARREAR_FEES_INVCD)

Recurring Forward Bill sum(DWA_RVN_MO.RCRNG_FRWD_FEES_INVCD_ERND)

Equipment Sale Revenue Bill sum(DWA_RVN_MO.EQPMNT_SL_RVN_INVCD)

Other Revenue sum(DWA_RVN_MO.OTHR_RVN_INVCD)

Postpaid Revenue sum(case when DWA_RVN_MO.PLN_TYP = 'POSTPAID' then ifnull(DWA_RVN_MO.RCRNG_ARREAR_FEES_INVCD , 0) + ifnull(DWA_RVN_MO.USG_RVN_INVCD , 0) + ifnull(DWA_RVN_MO.RCRNG_FRWD_FEES_INVCD_ERND , 0) + ifnull(DWA_RVN_MO.EQPMNT_SL_RVN_INVCD , 0) else 0 end )

Table 10–27 (Cont.) DWD_RVN_DAY Relationships

Relationships



Total Gross Revenue sum(ifnull(DWA_RVN_MO.EXPIRED_RVN , 0) + ifnull(DWA_RVN_MO.USG_RVN_INVCD , 0) + ifnull(DWA_RVN_MO.RCRNG_ARREAR_FEES_INVCD , 0) + ifnull(DWA_RVN_MO.RCRNG_FRWD_FEES_INVCD_ERND , 0) + ifnull(DWA_RVN_MO.EQPMNT_SL_RVN_INVCD , 0) + ifnull(DWA_RVN_MO.OTHR_RVN_INVCD , 0))

Billed Refund Amount sum(DWA_RVN_MO.BLLD_RFND_AMT)

Billed Written Off Amount sum(DWA_RVN_MO.BLLD_WRITE_OFF_AMT)

Total Net Revenue sum(ifnull(DWA_RVN_MO.EXPIRED_RVN , 0) + ifnull(DWA_RVN_MO.USG_RVN_INVCD , 0) + ifnull(DWA_RVN_MO.RCRNG_ARREAR_FEES_INVCD , 0) + ifnull(DWA_RVN_MO.RCRNG_FRWD_FEES_INVCD_ERND , 0) + ifnull(DWA_RVN_MO.EQPMNT_SL_RVN_INVCD , 0) + ifnull(DWA_RVN_MO.OTHR_RVN_INVCD , 0)) - ifnull(sum(DWA_RVN_MO.BLLD_RFND_AMT) , 0) - ifnull(sum(DWA_RVN_MO.BLLD_WRITE_OFF_AMT) , 0) - ifnull(sum(DWA_RVN_MO.BLLD_TAX_AMT) , 0)

Bill Tax Amount sum(DWA_RVN_MO.BLLD_TAX_AMT)

Total Gross Revenue LY AGO("Billing Analytics"."Dwd Rvn Day"."Total Gross Revenue" , "Billing Analytics"."Calendar Daydim"."Year", 1 )

Total Net Revenue LY AGO("Billing Analytics"."Dwd Rvn Day"."Total Net Revenue", "Billing Analytics"."Calendar Daydim"."Year" , 1 )

Revenue % Change (("Billing Analytics"."Dwd Rvn Day"."Total Net Revenue" - "Billing Analytics"."Dwd Rvn Day"."Total Net Revenue LY" ) / "Billing Analytics"."Dwd Rvn Day"."Total Net Revenue LY" ) * 100

Prod Ofr Name CASE WHEN "Billing Analytics"."Dwd Rvn Day"."Prod Ofr Lvl" = 'PROD_OFR_KEY' THEN "Billing Analytics"."Dwr Prod Ofr"."Prod Ofr Name" ELSE '-5000' END

Prod Spec Cd CASE "Billing Analytics"."Dwd Rvn Day"."Prod Spec Lvl" WHEN 'PROD_SPEC_TYP_CD' THEN '-5000' WHEN 'TPROD_SPEC' THEN '-5000' WHEN 'PROD_SPEC_KEY' THEN "Billing Analytics"."Dwr Prod Spec"."Prod Spec Cd" END

Prod Spec Typ Cd CASE "Billing Analytics"."Dwd Rvn Day"."Prod Spec Lvl" WHEN 'PROD_SPEC_TYP_CD' THEN "Billing Analytics"."Dwd Rvn Day"."Prod Spec Key" WHEN 'TPROD_SPEC' THEN 'N/A' WHEN 'PROD_SPEC_KEY' THEN "Billing Analytics"."Dwr Prod Spec"."Prod Spec Typ Cd" END

Pln Typ CASE "Billing Analytics"."Dwd Rvn Day"."Prod Ofr Lvl" WHEN 'PLN_TYP' THEN "Billing Analytics"."Dwd Rvn Day"."Prod Ofr Key" WHEN 'PROD_OFR_KEY' THEN IFNULL("Billing Analytics"."Dwr Prod Ofr"."Pln Typ", 'N/A') ELSE 'N/A' END

ARPU Prepaid avg(case when DWA_RVN_MO.PLN_TYP = 'PREPAID' then ifnull(DWA_RVN_MO.EXPIRED_RVN , 0) + ifnull(DWA_RVN_MO.USG_RVN_INVCD , 0) else 0 end / nullif( DWA_CNT_MO_ARPU.TOT_ACTV_MN_PROD_SBRP_CNT , 0))

ARPU Postpaid avg(case when DWA_RVN_MO.PLN_TYP = 'POSTPAID' then ifnull(DWA_RVN_MO.RCRNG_ARREAR_FEES_INVCD , 0) + ifnull(DWA_RVN_MO.USG_RVN_INVCD , 0) + ifnull(DWA_RVN_MO.RCRNG_FRWD_FEES_INVCD_ERND , 0) + ifnull(DWA_RVN_MO.EQPMNT_SL_RVN_INVCD , 0) else 0 end / nullif( DWA_CNT_MO_ARPU.TOT_ACTV_MN_PROD_SBRP_CNT , 0))

Total ARPU avg((ifnull(DWA_RVN_MO.EXPIRED_RVN , 0) + ifnull(DWA_RVN_MO.USG_RVN_INVCD , 0) + ifnull(DWA_RVN_MO.RCRNG_ARREAR_FEES_INVCD , 0) + ifnull(DWA_RVN_MO.RCRNG_FRWD_FEES_INVCD_ERND , 0) + ifnull(DWA_RVN_MO.EQPMNT_SL_RVN_INVCD , 0)) / nullif( DWA_CNT_MO_ARPU.TOT_ACTV_MN_PROD_SBRP_CNT , 0))

Total ARPU LY AGO("Billing Analytics"."Dwd Rvn Day"."Total ARPU", "Billing Analytics"."Calendar Daydim"."Year" ,1 )

ARPU % Change (("Billing Analytics"."Dwd Rvn Day"."Total ARPU" - "Billing Analytics"."Dwd Rvn Day"."Total ARPU LY" ) / "Billing Analytics"."Dwd Rvn Day"."Total ARPU LY" ) * 100

Table 10–28 (Cont.) DWD_RVN_DAYFacts and Calculated Measures

Measure Description



DWD_TMF_KPI Analytics

Figure 10–10 DWD_TMF_KPI Relationships

Table 10–29 DWD_TMF_KPI Analytics


Base Table ■ dwd_acct_pymt_day

■ dwr_cust_sgmnt

■ dwb_invc

■ dwb_invc_item

Derived Table DWD_TMF_KPI

Intra-ETL pkg_tmf_kpi_load

Table 10–30 DWD_TMF_KPI Relationships

Relationship

"Billing Analytics".""."OCDM_BILLING"."DWD_TMF_KPI"."BATCHID" = "Billing Analytics".""."OCDM_BILLING"."DWD_TMF_KPI_A"."BATCHID"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."CLNDR_DT" = CAST("Billing Analytics".""."OCDM_BILLING"."DWD_TMF_KPI_A"."LOAD_DT" AS DATE)

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."BSNS_DT" = CAST("Billing Analytics".""."OCDM_BILLING"."DWD_TMF_KPI_A"."LOAD_DT" AS DATE)



DWD_VAS_USG_DAY Analytics

Table 10–31 DWD_TMF_KPI Facts and Calculated Measures

Measure Description

Entry sum(DWD_TMF_KPI_A.ENTRY)

Table 10–32 DWD_VAS_USG_DAY Analytics


Base Table ■ DWB_ISP_USG_EVT

■ DWB_WRLS_CALL_EVT

■ DWB_UMS_EVT

■ DWB_SMS_EVT

■ DWB_MMS_EVT

■ DWB_UDR_EVT

Derived Table DWD_VAS_USG_DAY

Intra-ETL dwd_vas_usg_day_pkg



Figure 10–11 DWD_VAS_USG_DAY Relationships

Table 10–33 DWD_VAS_USG_DAY Relationships

Relationship

"Billing Analytics".""."OCDM_BILLING"."DWR_PROD_OFR"."PROD_OFR_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VAS_USG_DAY"."PROD_OFR_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ORG_BSNS_UNIT"."ORG_BSNS_UNIT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VAS_USG_DAY"."ORG_BSNS_UNIT_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_CUST"."CUST_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VAS_USG_DAY"."CUST_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_GEO_CNTY"."GEO_CNTY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VAS_USG_DAY"."GEO_CNTY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_PROD_SPEC"."PROD_SPEC_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VAS_USG_DAY"."PROD_SPEC_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."BSNS_DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VAS_USG_DAY"."DAY_KEY"



"Billing Analytics".""."OCDM_BILLING"."DWR_ACCT"."ACCT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VAS_USG_DAY"."ACCT_KEY"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VAS_USG_DAY"."DAY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWL_CUST_TYP"."CUST_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_VAS_USG_DAY"."CUST_TYP_CD"

Table 10–34 DWD_VAS_USG_DAY Facts and Calculated Measures

Measure Description

Vas Revenue sum(DWD_VAS_USG_DAY.CHRGD_AMT)

Minutes of Usage sum(DWD_VAS_USG_DAY.EVT_DRTN)

Sms Revenue sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'SMS' then DWD_VAS_USG_DAY.CHRGD_AMT else 0 end )

Number of Sms sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'SMS' then DWD_VAS_USG_DAY.EVT_CNT else 0 end )

Number of Nonroaming SMS sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'SMS' and DWD_VAS_USG_DAY.RMNG_OPRTR_KEY <> '-5000' then DWD_VAS_USG_DAY.EVT_CNT else 0 end )

Number of Roaming SMS sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'SMS' and DWD_VAS_USG_DAY.RMNG_OPRTR_KEY = '-5000' then DWD_VAS_USG_DAY.EVT_CNT else 0 end )

Total No. of SMS sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'SMS' then DWD_VAS_USG_DAY.EVT_CNT else 0 end )

Total No. of Subscribers count(distinct case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'SMS' then DWD_VAS_USG_DAY.ACCT_KEY end )

Total KB sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'SMS' then DWD_VAS_USG_DAY.DATA_VOL else 0 end )

Average KB per Subscriber "Billing Analytics"."Dwd Vas Usg Day"."Total KB" / "Billing Analytics"."Dwd Vas Usg Day"."Total No. Of Subscribers"

Revenue from Roaming SMS sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'SMS' and DWD_VAS_USG_DAY.RMNG_OPRTR_KEY <> '-5000' then DWD_VAS_USG_DAY.CHRGD_AMT else 0 end )

Revenue from Nonroaming SMS sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'SMS' and DWD_VAS_USG_DAY.RMNG_OPRTR_KEY = '-5000' then DWD_VAS_USG_DAY.CHRGD_AMT else 0 end )

Total Duration sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'SMS' then DWD_VAS_USG_DAY.EVT_DRTN else 0 end )

Total No. of SMS LY AGO("Billing Analytics"."Dwd Vas Usg Day"."Total No. Of SMS", "Billing Analytics"."Calendar Daydim"."Year", 1 )

Total Duration LY AGO("Billing Analytics"."Dwd Vas Usg Day"."Total Duration" , "Billing Analytics"."Calendar Daydim"."Year", 1 )

Average SMS per Subscriber "Billing Analytics"."Dwd Vas Usg Day"."Total No. Of SMS" / "Billing Analytics"."Dwd Vas Usg Day"."Total No. Of Subscribers"

Average Duration per Subscriber "Billing Analytics"."Dwd Vas Usg Day"."Total Duration" / "Billing Analytics"."Dwd Vas Usg Day"."Total No. Of Subscribers"

MMS Revenue sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'MMS' then DWD_VAS_USG_DAY.CHRGD_AMT else 0 end )

Number of MMS sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'MMS' then DWD_VAS_USG_DAY.EVT_CNT else 0 end )

Number of Nonroaming MMS sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'MMS' and DWD_VAS_USG_DAY.RMNG_OPRTR_KEY <> '-5000' then DWD_VAS_USG_DAY.EVT_CNT else 0 end )

Number of Roaming MMS sum(case when DWD_VAS_USG_DAY.VAS_TYP_CD = 'MMS' and DWD_VAS_USG_DAY.RMNG_OPRTR_KEY = '-5000' then DWD_VAS_USG_DAY.EVT_CNT else 0 end )

Table 10–33 (Cont.) DWD_VAS_USG_DAY Relationships

Relationship



DWD_VOI_CALL_DAY Analytics

Figure 10–12 DWD_VOI_CALL_DAY Relationships

Table 10–35 DWD_VOI_CALL_DAY Analytics


Base Tables DWB_WRLS_CALL_EVT

Derived Table DWD_VOI_CALL_DAY

Intra-ETL dwd_voi_call_day_pkg



Table 10–36 DWD_VOI_CALL_DAY Relationships

Relationship

"Billing Analytics".""."OCDM_BILLING"."DWR_PROD_SPEC"."PROD_SPEC_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VOI_CALL_DAY"."PROD_SPEC_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_GEO_CNTY"."GEO_CNTY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VOI_CALL_DAY"."GEO_CNTY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_DAY"."BSNS_DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VOI_CALL_DAY"."DAY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_PROD_OFR"."PROD_OFR_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VOI_CALL_DAY"."PROD_OFR_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWL_RMNG_TYP"."RMNG_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_VOI_CALL_DAY"."RMNG_TYP_CD"

"Billing Analytics".""."OCDM_BILLING"."DWL_CUST_TYP"."CUST_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_VOI_CALL_DAY"."CUST_TYP_CD"

"Billing Analytics".""."OCDM_BILLING"."DWL_CALL_TYP"."CALL_TYP_CD" = "Billing Analytics".""."OCDM_BILLING"."DWD_VOI_CALL_DAY"."CALL_TYP_CD"

"Billing Analytics".""."OCDM_BILLING"."CALENDAR_DAY"."DAY_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VOI_CALL_DAY"."DAY_KEY"

"Billing Analytics".""."OCDM_BILLING"."DWR_ORG_BSNS_UNIT"."ORG_BSNS_UNIT_KEY" = "Billing Analytics".""."OCDM_BILLING"."DWD_VOI_CALL_DAY"."ORG_BSNS_UNIT_KEY"

Table 10–37 DWD_VOI_CALL_DAY Facts and Calculated Measures

Measure Description

Total Call Duration sum(DWD_VOI_CALL_DAY.CHRGD_DRTN)

Average Call Duration avg(DWD_VOI_CALL_DAY.CHRGD_DRTN)

Total Revenue sum(DWD_VOI_CALL_DAY.CHRGD_AMT)

Average Revenue per Min sum(DWD_VOI_CALL_DAY.CHRGD_AMT) / nullif( sum(DWD_VOI_CALL_DAY.CHRGD_DRTN) , 0)

International Minutes sum(case when DWD_VOI_CALL_DAY.CALL_TYP_CD = 'INTL' then DWD_VOI_CALL_DAY.CHRGD_DRTN else 0 end )

Number of Roaming Calls sum(case when DWD_VOI_CALL_DAY.RMNG_TYP_CD = 'ROAM' then DWD_VOI_CALL_DAY.EVT_CNT else 0 end )

Number of Nonroaming Calls sum(case when DWD_VOI_CALL_DAY.RMNG_TYP_CD = 'NONROAM' then DWD_VOI_CALL_DAY.EVT_CNT else 0 end )

Total Roaming Voice Minutes sum(case when DWD_VOI_CALL_DAY.RMNG_TYP_CD = 'ROAM' then DWD_VOI_CALL_DAY.EVT_DRTN else 0 end )

Total Nonroaming Voice Minutes sum(case when DWD_VOI_CALL_DAY.RMNG_TYP_CD = 'NONROAM' then DWD_VOI_CALL_DAY.EVT_DRTN else 0 end )

Number of Roaming Call 60 sum(case when DWD_VOI_CALL_DAY.RMNG_TYP_CD = 'ROAM' then DWD_VOI_CALL_DAY.CEILED_DRTN_60 else 0 end )

Number of Nonroaming Call 60 sum(case when DWD_VOI_CALL_DAY.RMNG_TYP_CD = 'NONROAM' then DWD_VOI_CALL_DAY.CEILED_DRTN_60 else 0 end )

Revenue from Roaming Calls sum(case when DWD_VOI_CALL_DAY.RMNG_TYP_CD = 'ROAM' then DWD_VOI_CALL_DAY.CHRGD_AMT else 0 end )

Revenue from Nonroaming Calls sum(case when DWD_VOI_CALL_DAY.RMNG_TYP_CD = 'NONROAM' then DWD_VOI_CALL_DAY.CHRGD_AMT else 0 end )

Number of Outgoing Calls sum(case when DWD_VOI_CALL_DAY.EVT_DRCTN_CD = 'OUT' then DWD_VOI_CALL_DAY.EVT_CNT else 0 end )

Number of Incoming Calls sum(case when DWD_VOI_CALL_DAY.EVT_DRCTN_CD = 'IN' then DWD_VOI_CALL_DAY.EVT_CNT else 0 end )



DWV_PRPD_CUST_STAT View Analytics

Figure 10–13 DWV_PRPD_CUST_STAT Relationships

Table 10–38 DDV_PRPD_CUST_STAT _DAY Facts and Calculated Measures

Measure Description

Total Amount of Recharge sum(DWD_PRPD_ACCT_STTSTC_DAY.TOT_RCHRG_AMT)

Total Count of Recharge sum(DWV_PRPD_CUST_STAT.CUST_TOT_RCRRG_CNT)

Average Days Between Recharges avg(DWV_PRPD_CUST_STAT.AVG_DRTN_BTWN_RCHRG)

Last Recharge Date max(DWV_PRPD_CUST_STAT.LAST_RCHRG_DT)

Days Since Last Recharge TimeStampDiff(SQL_TSI_DAY, "Billing Analytics"."Prepaid Customers Current Status"."Last Recharge Date" , CURRENT_DATE)

Days Disturbed Recharge Cycle "Billing Analytics"."Prepaid Customers Current Status"."Days Since Last Recharge" - "Billing Analytics"."Prepaid Customers Current Status"."Average Days Between Recharges"

% Disturbance ("Billing Analytics"."Prepaid Customers Current Status"."Days Disturbed Recharge Cycle" / "Billing Analytics"."Prepaid Customers Current Status"."Average Days Between Recharges" ) * 100



Avg Total Recharge Value avg(DWV_PRPD_CUST_STAT.AVG_RCHRG_AMT)

Last 3 Months Recharge Count avg(DWV_PRPD_CUST_STAT.TOT_RCHRG_CNT_LAST3MO)

Last 3 Months Recharge Amount avg(DWV_PRPD_CUST_STAT.TOT_RCHRG_AMT_LAST3_MO)

Last Recharge Amount sum(DWV_PRPD_CUST_STAT.LAST_RCHRG_AMT)

Table 10–38 (Cont.) DDV_PRPD_CUST_STAT _DAY Facts and Calculated Measures

Measure Description

A

TMF KPI Business Metrics A-1

ATMF KPI Business Metrics

Oracle Communications Data Model is aligned with the TM Forum’s Business Metric Automation (BMA) initiative.

This appendix includes the following TM Forum Metrics in Oracle Communications Data Model:

■ Percentage of Payment Transactions by Payment Method (B-CE-1B)

■ Percentage of Electronic Bills Issued (B-CE-1C)

■ Mean Time to Prepare and Dispatch Bills (B-CE-4B)

■ Percentage of Inaccurate Bills (B-CE-4C)

■ Determine Percentage of Bills Adjusted (B-CE-4D)

■ Percentage of Billing-Related Queries (B-CE-4E)

■ Time to Prepare Bills for Display and Dispatch (B-OE-2A)

■ Collections Efficiency Against Credit Terms (B-OE-3E)

■ Percentage of E-payments Received (B-CE-1D)

■ Percentage of Bills Adjusted Internally (B-CE-4F)

■ Mean Time from Service Activation to Bill Dispatch (B_OE_2C)

■ Percentage Collectible Debt Written Off (B_OE_3D)

■ Volume of Customer Requests (CM_CE_3A)

Percentage of Payment Transactions by Payment Method (B-CE-1B)This KPI specifies metrics to determine the number of payment transactions per payment method.

The payment methods are: cash, credit card, debit card, check, direct debit, bank transfer, and so on.

This metric is calculated for every customer segment.

Percentage of Electronic Bills Issued (B-CE-1C)

A-2 Oracle Communications Data Model Adapters and Analytics User's Guide

Percentage of Electronic Bills Issued (B-CE-1C)

Percentage of Electronic Bills IssuedThis KPI specifies metrics to determine the percentage of electronic bills issued.

Metric = Number of bills issued electronically / Total number of bills issued

Bills issued electronically excludes any bills that have an associated paper bill.

The metric is calculated per service type (for example. fixed, mobile) and by customer segment.

Mean Time to Prepare and Dispatch Bills (B-CE-4B)

Mean Time to Prepare and Dispatch BillsThe aggregate time should include time for bill processing and printing to be completed. The metrics includes the time to process delayed calls between the close date and the actual bill run initiation. For the TMF this metric be is calculated per media type (paper, email, and so on.), and by customer segment.

Table A–1 Determine Preferred Access B-CE-1B Source Tables

Table Name Short Name Description

DWB_INVC I The invoice table documents each invoice issued to each account.

DWB_INVC_ITEM II Invoice item holds all components that appear on the invoice.

DWD_ACCT_PYMT_DAY Account Payment Day information.

DWL_CUST_TYP CT This lookup identifies or groups customers as corporate customers or individuals.

DWR_CUST C All the customers, including individual and organization customers. A customer is generally defined as a party using one or more services from the operator.

DWR_DAY D Calendar day in the day dimension.

DWR_ORG_CMPNY Company hierarchy level within an organization.

DWR_PROD_SPEC PS The product provided by the carrier.

Table A–2 Percentage of Electronic Bills Issued B-CE-1C Source Tables


DWB_INVC I The Invoices table documents each invoice issued to each account.

DWB_INVC_ITEM II Invoice Item holds all components that appear on the invoice.

DWL_CUST_TYP CT This lookup identifies or groups customers as Corporate customers or Individuals.





Determine Percentage of Bills Adjusted (B-CE-4D)


Aggregate time from cycle close date until bills ready for dispatch / Total number of bills

Percentage of Inaccurate Bills (B-CE-4C)

Percentage of Inaccurate BillsTo determine reliability and accuracy of invoices.

The number of bills with errors includes all bills that were found to have an error, which includes errors found internally and, also errors reported by the customer.

Determine Percentage of Bills Adjusted (B-CE-4D)

Percentage of Adjusted BillsThis metric provides information on the percentage of billing adjustments issued in response to customer queries or complaints.

The number of bills adjusted includes all bills requiring adjustments initiated by the customer. This is for all financial adjustments or credit notes. The number should not include customer-initiated changes for items such as address changes or plan adjustments.

Table A–3 Mean Time to Prepare and Dispatch Bills (B-CE-4B) Source Tables


DWB_INVC I The invoices table documents each invoice issued to each account.


DWD_PRCS_INVC_DAY IPD Provides all the information related to the invoices processed.






Table A–4 Percentage of Inaccurate Bills (B-CE-4C) Source Tables


DWB_INVC I The invoices table documents each invoice issued to each account.





Percentage of Billing-Related Queries (B-CE-4E)


Percentage of Billing-Related Queries (B-CE-4E)This KPI specifies metrics to determine percentage of billing contacts.

Number of customer-initiated billing related contacts / Total number of bills issued

This KPI includes all inbound contacts such as phone, email, and web that are related to billing and payment inquiries. The metric excludes customer-initiated changes such as address changes or plan adjustments.

Time to Prepare Bills for Display and Dispatch (B-OE-2A)This KPI specifies metrics total elapsed time from bill cycle close to bills ready for display or dispatch:

Total elapsed time includes the time required for bill processing up until the bills are ready for display, and excluding the time required for posting and or printing.

Table A–5 Determine Percentage of Bills Adjusted (B-CE-4D) Source Tables

Table NameShort Name Description

DWB_INVC The Invoices table documents each invoice issued to each account.

DWB_INVC_ADJ IA This is to record all adjustment made on the invoices.







Table A–6 Percentage of Billing Contacts B-CE-4E Source Tables


DWB_EVT_PRTY_INTRACN

The Party Interactions table records all interactions or communications with the customer.

DWB_INVC The Invoices table documents each invoice issued to each account. An invoice represents the request for payment for goods and services during a specified period.






Percentage of E-payments Received (B-CE-1D)


Collections Efficiency Against Credit Terms (B-OE-3E)This KPI specifies metrics for billing collection management: collections efficiency against credit terms.

Metric = Aggregate value of unpaid invoices / Aggregate value of all invoices

Total value of all customer invoices unpaid at ten days after due date for the billing period.

Percentage of E-payments Received (B-CE-1D)This KPI specifies metrics to determine the bills paid electronically.

This KPI includes bill paid electronically, that is bills paid using home banking, automatic bank deduction, funds transfers, ATM transactions, Web or IVR based credit or debit card transactions. This KPI excludes payments by cash or check:

Number of bills paid electronically / Total number of bills

Table A–7 Percentage of Billing Contacts B-OE-2A Source Tables




DWD_PRCS_INVC_DAY IPD






Table A–8 Collections Efficiency Against Credit Terms B-OE-3E Source Tables


DWB_ACCT_PYMT The payments table records details of each allocation of money from a receipt made by a party to a specific account.








Percentage of Bills Adjusted Internally (B-CE-4F)


Percentage of Bills Adjusted Internally (B-CE-4F)This KPI specifies metrics for billing calculations: Percentage of Bills adjusted Internally. The KPI specifies the number of bills adjusted and only includes all bills requiring adjustments initiated by internal triggers. This should include things like plan changes, address changes, financial adjustments, credit notes, and so on. If initiated internally the metric excludes any customer-initiated adjustments.

Mean Time from Service Activation to Bill Dispatch (B_OE_2C)This KPI specifies metrics to aggregate time from service activation to bill dispatch / Total number of current orders. This includes the aggregate time for all orders in hours.

Table A–9 Determine the Bills Paid Electronically B-CE-1D Source Tables


DWB_ACCT_PYMT AP The Payments table records details of each allocation of money from a receipt made by a party to a specific account.

DWB_INVC I The Invoices table documents each invoice issued to each account. An invoice represents the request for payment for goods and services during a specified period.



DWB_INVC_PYMT_ASGN IPA To indicate which payment reconciles which invoice.


DWL_PYMT_MTHD_TYP PMT Lookup for valid methods of payment.





Table A–10 Determine the Bills Paid Electronically B-CE-4F Source Tables










Volume of Customer Requests (CM_CE_3A)


Percentage Collectible Debt Written Off (B_OE_3D)This KPI specifies metrics for Billing Collection Management to determine the percentage of collectible debt that is written off.

Metric = Collectible debt written off / total revenue collected

Volume of Customer Requests (CM_CE_3A)This KPI specifies metrics for billing calculations: Volume of Customer Requests. This KPI reports the number of customer requests and includes all inbound contacts such as phone, email, and web contacts. This should include all billing and payment inquiries, all inquiries about call plans, and so on. It should exclude outbound and store front contacts.

Number of customer requests * 1000 / Total number of customers

Table A–11 Mean Time from Service Activation to Bill Dispatch B_OE_2C Source Tables


DWB_INVC I The Invoices table documents each invoice issued to each account. An invoice represents the request for payment for goods and services during a specified period.






DWR_PROD_SBRP The record of customer using a product (or product package). Customer subscription is the basis of billing and network usage authorization. One subscription may be based on contract.


Table A–12 Percentage Collectible Debt Written Off (B_OE_3D) Source Tables




DWD_ACCT_BAL_MO ABM






Volume of Customer Requests (CM_CE_3A)


Table A–13 Volume of Customer Requests (CM_CE_3A) Source Tables


DWB_CUST_ORDR

DWB_EVT_PRTY_INTRACN

The Party Interactions table records all interactions or communications with the customer. The interactions include:




