Oracle® Communications Data Model Reference Release 11.3.1 Part Number E28440-03 |
|
|
PDF · Mobi · ePub |
This chapter includes the following sections:
In Oracle Communications Data Model, reference and lookup tables store master, reference, and dimensional data; and the base, derived, and aggregate tables store transaction and fact data at different granularities. The base tables store the transaction data at the lowest level of granularity, while the derived and aggregate tables store consolidated and summary transaction data.
Two types of Extract, Transform, and Load (ETL) operations populate the tables with data. The source-ETL operations populate the reference, lookup, and base tables with data from the source On-Line Transaction Processing (OTLP) applications. Additional Intra-ETL operations populate the derived and aggregate tables with the data in the base, reference, and lookup tables. While the source ETL operations are not a part of Oracle Communications Data Model, the Intra-ETL operations are.
There are two categories of Intra-ETL operations (scripts):
Derived Population: A database package containing scripts that populate the derived tables based on the content of the base, reference, and lookup tables.
Aggregate Population: A database package containing scripts to refresh the Oracle Communications Data Model aggregate tables, mostly Materialized Views, based on the content of the derived tables and some reference tables.
Derived tables are implemented using Oracle tables, while the Aggregate tables are implemented using Materialized Views.
Note:
Changes to intra-ETL cannot be supported. But it is expected that if the business needs require a change in the business logic of the intra-ETLs, some customer adaptations could be necessary even if they are not be supported.The INTRA_ETL_FLW is actually a process flow designed using the Oracle Warehouse Builder Workflow component which includes the dependency of each individual sub process flow and executes each process flow in the proper order. The result of each table loading is tracked in DWC_ control tables.
For more information, see "Intra-ETL Process Flows" and Oracle Communications Data Model Implementation and Operations Guide.
Oracle Communications Data Model Value_Lookup values contains the Lookup tables and its values which are used in Intra-ETL mapping. Hardcoded values contains the list of tables and values which are used in Join conditions & Filter conditions in Intra-ETL mapping.
Table 7-1 Shows the lookup tables and values which are used in Intra-ETL mapping.
Table 7-1 Value Lookup Values for Intra-ETL Mapping
SI No. | Hard Coded Value Table Name | Hard Coded Value Column | Value used | ETL Program Name | ETL Usage Type |
---|---|---|---|---|---|
1 |
|
|
|
|
Hardcoded |
2 |
|
|
|
|
Hardcoded |
3 |
|
|
|
|
Hardcoded |
4 |
|
|
|
|
Hardcoded |
5 |
|
|
|
|
Hardcoded |
6 |
|
|
|
|
Hardcoded |
7 |
|
|
|
|
Hardcoded |
8 |
|
|
|
|
Hardcoded |
9 |
|
|
|
|
Hardcoded |
10 |
|
|
|
|
Hardcoded |
|
|
|
Hardcoded |
||
11 |
|
|
|
|
Hardcoded |
14 |
|
|
|
|
Hardcoded |
15 |
|
|
|
|
Hardcoded |
16 |
|
|
|
|
Hardcoded |
17 |
|
|
|
|
Hardcoded |
18 |
|
|
|
|
Hardcoded |
19 |
|
|
|
|
Hardcoded |
20 |
|
|
|
|
Hardcoded |
|
|
|
Hardcoded |
||
21 |
|
|
|
|
Hardcoded |
22 |
|
|
|
|
Hardcoded |
23 |
|
|
|
|
Hardcoded |
24 |
|
|
|
|
Hardcoded |
25 |
|
|
|
|
Hardcoded |
26 |
|
|
|
|
Hardcoded |
27 |
|
|
|
|
Hardcoded |
28 |
|
|
|
|
Hardcoded |
29 |
|
|
|
|
Hardcoded |
30 |
|
|
|
|
Hardcoded |
31 |
|
|
|
|
Hardcoded |
32 |
|
|
|
|
Hardcoded |
33 |
|
|
|
|
Hardcoded |
34 |
|
|
|
|
Hardcoded |
35 |
|
|
|
|
Hardcoded |
36 |
|
|
|
|
Hardcoded |
37 |
|
|
|
Hardcoded |
|
38 |
|
|
|
|
Hardcoded |
39 |
|
|
|
|
Hardcoded |
40 |
|
|
|
|
Hardcoded |
41 |
|
|
|
|
Hardcoded |
44 |
|
|
|
|
Hardcoded |
1 |
|
|
|
|
Value_Lookup |
2 |
|
|
|
|
Value_Lookup |
3 |
|
|
|
|
Value_Lookup |
4 |
|
|
|
|
Value_Lookup |
6 |
|
|
|
|
Value_Lookup |
7 |
|
|
|
|
Value_Lookup |
8 |
|
|
|
|
Value_Lookup |
9 |
|
|
|
|
Value_Lookup |
10 |
|
|
|
|
Value_Lookup |
16 |
|
|
|
|
Value_Lookup |
17 |
|
|
|
|
Value_Lookup |
18 |
|
|
|
|
Value_Lookup |
Shows the packages to populate the derived tables. The naming convention by default is the physical name of the target table plus,"_PKG
"
Populate target table DWD_ACCT_DEBT_DAY
. For more information, see ACCOUNT DEBT DAY DRVD.
Populate target table DWD_ACCT_PYMT_DAY
. For more information, see ACCOUNT PAYMENT DAY DRVD.
Populate target table DWD_ACCT_PYMT_MTHD_STAT_HIST
. For more information, see ACCOUNT PAYMENT METHOD STATUS HIST DRVD.
Populate target table DWD_ACCT_RFND_DAY
. For more information, see ACCOUNT REFUND DAY DRVD.
Populate target table DWD_ACCT_STAT
. For more information, see ACCOUNT STATUS DRVD.
Populate target table DWD_ARPU_BASE
. For more information, see ARPU BASE DRVD.
Populate target table DWD_CALL_CNTR_CALL_DAY
. For more information, see CALL CENTER CALL DAY DRVD.
Populate target table DWD_CALL_CNTR_CASE_DAY
. For more information, see CALL CENTER CASE DAY DRVD.
Populate target table DWD_CANBLZTN_DTL_DAY
. For more information, see CANNIBALIZATION DETAIL DAY DRVD.
Populate target table DWD_CMISN_DAY
. For more information, see COMMISSION DAY DRVD.
Populate target table DWD_CNCT_DSCNCT_DAY
. For more information, see CONNECT DISCONNECT DAY DRVD.
Contains connect and disconnect information of particular subscriber.
Populate target table DWD_CNRT_CHNG
. For more information, see CONTRACT CHANGED DRVD.
Populate target table DWD_COST_CUST
. For more information, see COST CUSTOMER DRVD.
Populate target table DWD_COST_ORG
. For more information, see COST ORGANIZATIONAL DRVD.
Populate target table DWD_CRDT_CTGRY
. For more information, see CREDIT CATEGORY DRVD.
Populate target table DWD_CUST_ACQSTN_SUMM_DAY
. For more information, see CUSTOMER ACQUISITION SUMMARY DAY DRVD.
Populate target table DWD_EXTRNL_DEBT_COLLCTN_DAY
. For more information, see EXTERNAL DEBT COLLECTION DAY DRVD.
Populate target table DWD_GIVE_AWAY_ITEM_DAY
. For more information see GIVE AWAY ITEM DAY DRVD.
Populate target table DWD_INTRNL_DEBT_COLLCTN_DAY
. For more information, see INTERNAL DEBT COLLECTION DAY DRVD.
Populate target table DWD_INVC_ADJ
. For more information, see INVOICE ADJUSTMENT DRVD.
Populate target table DWD_LYLTY_PROG_DAY
. For more information, see LOYALTY PROGRAM DAY DRVD.
Populate target table DWD_MKT_OPRTR_PRTNG
. For more information, see MARKET OPERATOR PORTING DERIVED.
The summary information about succeeded Number Porting between operators.
Populate target table DWD_PRPD_ACCT_STTSTC
. For more information, see PREPAID ACCOUNT STATISTIC DRVD.
Populate target table DWD_PRPD_ALWNCE_DAY
. For more information, see PREPAID ALLOWANCE DAY DRVD.
Populate target table DWD_PYMT_AGNG_DAY
. For more information, see PAYMENT AGING DAY DRVD.
Populate target table DWD_RDMPTN_DAY
. For more information, see REDEMPTION DAY DRVD.
Populate target table DWD_SHOP_EFFNCY_DAY
. For more information, see SHOP EFFICIENCY DAY DRVD.
Populate target table DWD_SL_RPRSTV_STTSTC_MO
. For more information, see SALES REPRESENTATIVE STATISTICS DRVD.
Populate the table DWD_SPLMNTR_SRVC_USG
. For more information, see SUPPLEMENTARY SERVICE USAGE DRVD.
Populate target table DWD_VAS_SBRP_QCK_SUMM
. For more information, see VAS SUBSCRIPTION QUICK SUMMARY DRVD.
Shows the PL/SQL mapping to populate derived tables.
Populate target table DWD_DATA_USG_DAY
. For more information, see DATA USAGE DAY DRVD.
Populate target table DWD_VAS_USG_DAY
. For more information, see VAS USAGE DAY DRVD.
Populate target table DWD_VOI_CALL_DAY
. For more information, see VOICE CALL DAY DRVD.
The INTRA_ETL_FLW is the complete Intra-ETL process designed using Oracle Warehouse Builder, and is composed of individual sub-process flows to populate derived aggregate tables, and relational materialized views where the data originates from base, reference, and lookup tables. This process flow respects the dependency of each individual program.
Figure 7-1 shows the main process flow INTRA_ETL_FLW.
The process flow INTRA_ETL_FLW is initialized from START_PROCESS, and this checks if any previous process flows are running. If any process is running then START_PROCESS jumps to END_ERROR or START_PROCESS generate the process number from the sequence. This process number is sent as input to the Derived Flow.
In the DRVD_FLW when the START process is initiated this generates the process number and is sent as input to the Derived mapping. Once the number is generated it updates the status at backend (Control Tables). If derived mapping is successful then the derived mapping checks the status in control tables.
The DRVD_FLW sub-process flow contains all the Oracle Warehouse Builder mappings for populating derived tables, based on the content of the base, reference, and lookup tables. This sub-process flow has a dependency on the AGGR_FLW. If the DRVD_FLW is successful then it navigates to AGGR_FLW otherwise the process ends.
Figure 7-2 shows the DRVD_FLW sub-process flow for populating the derived tables.
Figure 7-2 Intra-ETL Derived Flow Sub-process (DRVD_FLW)
After the DRVD_FLW starts successfully, it moves to the fork. The sub-process FORK performs the derived mappings (these run in parallel). Once the activity is started then Start_Activity
inserts one record in the control table, DWC_INTRA_ETL_ACTIVITY, and the state is set to 'Running'. The End_Activity updates the status in control tables (the state mapping is COMPLETED-SUCCESS or COMPLETED-ERROR) in the control tables. The AND activity specifies whether all the parallel mappings have been completed or not and then switches to the next activity, for example END_SUCCESS. This DRVD_FLW depends on the AGGR_FLW sub-process flow.
The AGGR_FLW sub-process flow contains PL/SQL code using Partitions Change Tracking Strategy for refreshing all the aggregate tables which are Materialized Views in Oracle Communications Data Model.
Figure 7-3 shows the AGGR_FLW sub-process flow for refreshing all the aggregate tables.
Figure 7-3 Intra-ETL Aggregate Flow Sub-process (AGGR_FLW)
After the AGGR_FLW is initiated and started successfully it is moved to the Fork. The FORK process makes the aggregates to run in parallel. The AND activity specifies that all the parallel aggregates have been completed or not and then switches over to the next activity, (for example, END_SUCCESS).
The OLAP_MAP sub-process flow triggers the OLAP package which can load data from Oracle Communications Data Model aggregate tables to Oracle Communications Data Model Analytical Workspace and calculate the forecast data. It reads OLAP ETL parameters from DWC_OLAP_ETL_PARAMETER table.
Figure 7-4 shows the OLAP_MAP sub-process flow that triggers the OLAP packages.
Figure 7-4 Intra-ETL OLAP Flow Sub-process (OLAP_MAP)
The MINING_FLW sub process flow triggers the data mining model.
The window of data is decided by following variables:
churn_interval_months
ltv_age_interval_years
dwc_etl_parameter.to_date_etl
The dwc_etl_parameter.to_date_etl limits the end date for data and first two parameters limit the start date of data for the churn models and life time value models respectively.
Figure 7-5 shows the MINING_FLW sub-process flow.
Figure 7-5 Intra-ETL Mining Flow Sub-process (MINING_FLW)