Skip Headers
Oracle® Communications Data Model Adapters and Analytics Installation Guide
Release 11.3.2

E37744-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

B BRM Adapter Update

If you previously installed the BRM Adapter Oracle Communications Data Model 11.3.2 version, the Oracle Communications Data Model 11.3.2.1 update of the BRM Adapter requires a full reinstall. You need to follow the BRM Adapter Installation and Configuration instructions in Appendix A, "BRM Adapter Installation and Configuration". After the BRM Adapter is reinstalled you need to complete the post-installation and configuration steps in this appendix.

Pre Conditions

If the Oracle Communications Data Model patch is not installed, do the following:

  1. Run Oracle Communications Data Model 11.3.2 patch script. The scripts are available with bug 17863837.

BRM Adapter Configuration

The patch adds a CONFIG folder to the BRM Adapter work repository. You need to login Oracle Data integrator using ODI Connection and then check for the CONFIG folder under BRM-OCDM, as shown in Figure B-1.

Figure B-1 BRM Adapter Files CONFIG Folder

Description of Figure B-1 follows
Description of "Figure B-1 BRM Adapter Files CONFIG Folder"

The CONFIG folder contains Oracle Communications Data Model 11.3.2.1 procedures and the Oracle Communications Data Model 11.3.2 packages. You need to open procedure to complete configuration and then run package.

Note, do not run the procedure alone, this will fail and might lead to configuration issues. If the package fails, do not run it again. You need to check the failures and then run manually from failed step onwards.

Review Configuration Steps

The BRM Adapter configuration includes multiple steps, you need to review the steps as follows.

  1. Step 0 - SERVICE_T_MAP_VW - create view

    This step creates mapping table in BRM_STG schema. You do not need to review this.

    Note: refer DWL_SRVC_TYP table. If a new service is added then you need to make entry into DWR_SRVC_TYP table.

  2. Step 10 - BRM_DD_OBJECTS_MAP - create table

    This step creates table in BRM_STG schema for default mapping values. You do not need to review this step.

  3. Step 20 - brm_dd_objects_map - insert

    This step inserts mappings between BRM services. The BRM Adapter uses mappings. This step includes different insert statements as shown in Table B-1. You need to update these insert statements for your needs.

    Table B-1 BRM_DD_Object_Map Statements

    Mapping Description

    SERVICE_MAP

    This mapping helps to provide proper names to different BRM services. Using the BRM services name directly in the reports may not make any sense. In this mapping you assign proper, that is understandable names to each of the BRM services:

    insert into brm_dd_objects_map values (1868, '/service/email', 'EMAIL', 'SERVICE_MAP', sysdate, 'admin');
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/service/*).

    3. User understandable service name.

    4. Map type - do not change this column (key column used in adapter mapping).

    SERVICE_TYPE

    This mapping defines the type for BRM services. Values added services are tagged as 'VAS'

    insert into brm_dd_objects_map values (1868, '/service/email', 'REGULAR', 'SERVICE_TYPE', sysdate, 'admin');
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/service/*).

    3. Service type

    4. Map type - do not change this column (key column used in adapter mapping).

    PRICE_TYPE

    This mapping helps in mapping BRM price types to Oracle Communications Data Model price types. Oracle Communications Data Model has defined certain price type and these price types are used within IETL to generate derived and aggregated tables.

    Oracle Communications Data Model specification:

    1. 1% Recurring Fee

    2. 2% Onetime fee

    3. 3% Onetime usage

    4. 4% Duration based usage

    5. 5% Volume based usage

    6. 6% Free of charge

    7. 7% Usage discount

    8. 8% Other discounts

    9. -5000 unknown

    You can extend this list.

    INSERT INTO BRM_DD_OBJECTS_MAP VALUES (1696,'/item/cycle_arrear','1100', 'PRICE_TYPE',SYSDATE, 'admin');
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/item/*).

    3. Price type

    4. Map type - do not change this column (key column used in adapter mapping).

    Note: refer DWL_PRICE_TYP Oracle Communications Data Model table. If new price type is added then make sure to add entry into DWL_PRICE_TYP table in Oracle Communications Data Model.

    Make sure to map '/item/adjustment' as 'ADJUSTMENT'. This is used in mapping to find adjustments items.

    INVC_ITEM_TYPE

    You need to define the item type for each of invoice items. It is similar to PRICE TYPE. Oracle Communications Data Model specification:

    1. 1% Recurring Fees

    2. 2% One Time Fees

    3. 3% Usage (any type)

    4. 4% Recharges (any type)

    5. 5% to be defined

    6. 6% Discounts

    7. 7% Carry Over

    8. 8% Penalty

    9. 9% Specials (adj, write off, redirection,...)

    Insert into brm_dd_objects_map values (1696,'/item/cycle_arrear','1000','INVC_ITEM_TYPE',SYSDATE, 'ADMIN');
    
    • Obj_id0 column from dd_objects_t table.

    • Name column from dd_objects_t table (/item/*).

    • Invoice item type

    • Map type - do not change this column (key column used in adapter mapping).

    Note: refer DWL_INVC_ITEM_TYP Oracle Communications Data Model table. If new invoice item is added then make sure to add entry into DWL_INVC_ITEM_TYP table in Oracle Communications Data Model.

    DWL_INVC_DISC_TYP

    Here you can map BRM discount types to Oracle Communications Data Model mapping. BRM discount type can derived from event POID type.

    Oracle Communications Data Model specification:

    1. 1% Recurring Discount

    2. 2% Onetime Discount

    3. 3% Onetime usage discount

    4. 4% Usage Discount

    You can extend this list.

    INSERT INTO BRM_DD_OBJECTS_MAP VALUES (2214,'/event/delayed/session/telco/gsm','4000', 'DWL_INVC_DISC_TYP',SYSDATE, 'admin');
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/event/*).

    3. Discount Oracle Communications Data Model map

    4. Map type - do not change this column (key column used in adapter mapping).

    Note: referDWL_INVC_DISC_TYP Oracle Communications Data Model table. If new discount type is added then make sure to add entry into DWL_INVC_DISC_TYP table in Oracle Communications Data Model.

    EVENT_TYPE_MAP

    You can map different event POID type to some understandable names. This will help you for better reporting with meaningful names for event types.

    INSERT INTO BRM_DD_OBJECTS_MAP VALUES (2244,'/event/delayed/session/telco/gprs','USAGE','EVENT_TYPE_MAP', SYSDATE, NULL);
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/event/*).

    3. Event type map

    4. Map type - do not change this column (key column used in adapter mapping).

    Note: referDWL_EVT_TYP Oracle Communications Data Model table. If new event type is added then make sure to add entry intoDWL_EVT_TYP table in Oracle Communications Data Model.

    ROAMING_TYPE_MAP

    This mapping is used to find roaming and non-roaming events. You need to configure this to distinguish between roaming and non-roaming calls.

    Oracle Communications Data Model specification:

    1. NONROAM

    2. ROAM

    INSERT INTO BRM_DD_OBJECTS_MAP VALUES (2216,'/event/delayed/session/telco/gsm/roaming','ROAM','ROAMING_TYPE_MAP', SYSDATE, NULL);
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/event/*).

    3. Roaming type map

    4. Map type - do not change this column (key column used in adapter mapping).

    Note: referDWL_RMNG_TYP Oracle Communications Data Model table


  4. Step 40 - BRM_DD_OBJ_MAP_DEFAULT - create table

    This step creates default mapping table in BRM_STG schema. You do not need to review this step.

  5. Step 50 - BRM_DD_OBJ_MAP_DEFAULT - insert

    You can skip this step review, but it is recommended to review. Here you can define default values, in case mapping is not available for DD_OBJECT. If this step is not configured for any of mapping then it will return -5000 by default.

    INSERT INTO BRM_DD_OBJ_MAP_DEFAULT VALUES ('SERVICE_MAP', '-5000', SYSDATE, 'ADMIN')
    
    1. Map type (refer BRM_DD_OBJECTS_MAP table).

    2. Default value (make sure this value is available in respective lookup table).

  6. Step 60 - BRM_GET_DD_OBJ_MAP - create function

    This step creates BRM_GET_DD_OBJ_MAP function. You do not need to review this step.

  7. Step 70 - brm_odi_exception_handle - create table

    This step creates exception handling table. You do not need to review this step.

    Note: refer exception handling in Oracle Communications Data Model Adapters and Analytics User's Guide.

  8. Step 80 - DWC_ETL_MATRIX_OCDMLKUP_MATCH - INSERT

    This step provides extensions to the existing DWC_ETL_MATRIX_OCDMLKUP_MATCH mapping. This mapping is extended as shown in Table B-2:

    Table B-2 ETL OCDM Lookup Extensions

    Table Mapping Description

    DWL_INVC_ADJ_TYP

    You can map BRM adjustment type to Oracle Communications Data Model for better reporting. BRM adjustments are defined in STRINGS_T table in BRM. It is recommended to consult BRM developer for detail regarding VERSION range used for adjustment type. Actual adjustments event are available in EVENT_T and EVENT_BILLING_MISC_T BRM table.

    Oracle Communications Data Model specification:

    1. 2% Credit reasons

    2. 8% Debit reasons

    3. 3% Bill settlements

    4. 4% Write off

    You can extend this list.

    Note: refer DWL_INVC_ADJ_TYP Oracle Communications Data Model table. If you are adding new entry, then make sure to add same into DWL_INVC_ADJ_TYP Oracle Communications Data Model table.

    (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'STRINGS_T', 'VERSION', '21', 'DWL_INVC_ADJ_TYP', 'INVC_ADJ_TYP_CD', '221000');
    
    1. SRC_SYS_TAB_COL_VAL - BRM adjustment value. You need to configure this according to BRM system configuration.

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value. Can set any value by following Oracle Communications Data Model specifications mentioned above.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    Note: refer DWL_INVC_ADJ_TYP Oracle Communications Data Model table. If you add new adjustment type then make sure to make entry into DWL_INVC_ADJ_TYP table. If you do not want to make entry into DWL_INVC_ADJ_TYP table then recommended disabling respective constraints. If not done, it might lead to BRM adapter data load failure.

    DWL_INVC_ADJ_RSN

    You can map BRM adjustment reasons to Oracle Communications Data Model. BRM adjustments reasons are defined in STRINGS_T table in BRM. It is recommended to consult BRM developer for detail regarding VERSION and STRING_ID range used for adjustment reason.

    Actual adjustments event are available in EVENT_T and EVENT_BILLING_MISC_T BRM table.

    Oracle Communications Data Model specification:

    1. 2% Credit reasons

    2. 8% Debit reasons

    3. 3% Bill settlements

    4. 4% Write off

    You can extend this list.

    Note: refer DWL_INVC_ADJ_RSN Oracle Communications Data Model table. If you are adding new entry, then make sure to add same into DWL_INVC_ADJ_RSN Oracle Communications Data Model table.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'STRINGS_T', 'STRING_ID', '21-1', 'DWL_INVC_ADJ_RSN', 'INVC_ADJ_RSN_CD', '221100');
    
    • SRC_SYS_TAB_COL_VAL - BRM adjustment reason. If you need to configure this according to BRM system configuration. This column value is combination of both VERSION and STRING_ID from STRINGS_T table (VERSION || '_' || STRING_ID). This helps in assigning reason codes to respective adjustment types.

    • OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value. Can set any value by following Oracle Communications Data Model specifications mentioned above.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_CUST_TYP

    You can map BRM customer residency type to Oracle Communications Data Model customer type. Different business types are defined CONFIG_BUSINESS_TYPE_T BRM table. BRM adapter moves this table data into DWL_CUST_TYP Oracle Communications Data Model table.

    Oracle Communications Data Model specification:

    1. IND - individual customers

    2. ORG - Business customers

    You can extend this list.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL, OCDM_TGT_TAB_COL_VAL_DEF_IND, EFF_FROM_DT, EFF_TO_DT) VALUES ('BRM', 'CONFIG_BUSINESS_TYPE_T', 'REC_ID', '0', 'DWL_CUST_TYP', 'CUST_TYP_CD', 'IND', NULL, NULL, NULL);
    
    1. SRC_SYS_TAB_COL_VAL - REC_ID from CONFIG_BUSINESS_TYPE_T BRM table

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value. Can set any value by following Oracle Communications Data Model specifications mentioned above.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_BLLG_PRD

    You can map BRM "BILL WHEN" to Oracle Communications Data Model mapping. You do not need to change this mapping but still recommended to review.

    Oracle Communications Data Model specification:

    1. MONTHLY

    2. BI MONTHLY

    3. QUARTERLY

    4. ANNUALLY

    You can extend this list.

    Note: refer DWL_BLLG_PRD Oracle Communications Data Model table. If you are adding new entry, then make sure to add same into DWL_BLLG_PRD Oracle Communications Data Model table.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'PIN_FLD_BILL_WHEN', 'PIN_FLD_BILL_WHEN', '12', 'DWL_BLLG_PRD', 'BLLG_PRD_CD', 'ANNUALLY');
    
    1. SRC_SYS_TAB_COL_VAL - "BILL WHEN" value from BRM

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value. Can set any value by following Oracle Communications Data Model specifications mentioned above.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_PYMT_MTHD_TYP

    You can configure different payment methods available in BRM system to Oracle Communications Data Model. BRM payment methods are configured in CONFIG_PAYMENT_PAY_TYPES_T BRM table. BRM adapter moves data from CONFIG_PAYMENT_PAY_TYPES_T table to DWL_PYMT_MTHD_TYP Oracle Communications Data Model table.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'CONFIG_PAYMENT_PAY_TYPES_T', 'REC_ID', '10003', 'DWL_PYMT_MTHD_TYP', 'PYMT_MTHD_TYP_CD', '3');
    
    1. SRC_SYS_TAB_COL_VAL - REC_ID from CONFIG_PAYMENT_PAY_TYPES_T BRM table

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_CALL_TYP

    You can configure call type using this configuration option. Balance impact category can be used to configure different call types.

    Oracle Communications Data Model specification:

    1. NTNL - National calls

    2. LCL - Local calls

    3. INTL - International calls

    You can extend this list.

    Note: refer DWL_CALL_TYP Oracle Communications Data Model table. If you are adding new entry, then make sure to add same into DWL_CALL_TYP Oracle Communications Data Model table.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'CONFIG_IMPACT_CATEGORIES_T', 'REC_ID', 'NAT_FIX', 'DWL_CALL_TYP', 'CALL_TYP_CD', 'NTNL');
    
    1. SRC_SYS_TAB_COL_VAL - BRM balance impact category

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value for call type map.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_CALL_SUCC_FAIL_TYP

    You can configure call termination cause. Termination cause is available in EVENT_SESSION_TLCS_T table.

    Oracle Communications Data Model specification:

    1. SUCC - Successful call

    2. FAIL - Call failed

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'EVENT_SESSION_TLCS_T', 'TERMINATE_CAUSE', '0', 'DWL_CALL_SUCC_FAIL_TYP', 'CALL_SUCC_FAIL_TYP_CD', 'SUCC');
    
    1. SRC_SYS_TAB_COL_VAL - Call TERMINATE_CAUSE from EVENT_SESSION_TLCS_T BRM table

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value for call termination.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_INVC_STAT

    This mapping is used configure invoice status. You do not need to make any changes to this mapping but still recommended to review. STATUS column from INVOICE_T is BRM source for invoice statues.

    Oracle Communications Data Model specification:

    1. 1% Invoice is open but pending (not yet physically or digitally created to dispatch)

    2. 2% Invoice is created but not yet dispatched

    3. 3% Invoice is created and has been sent or published for customer to see (sub-types allowed)

    4. 5% Invoice has been fully paid.

    5. 9% Invoice was sent but came back.

    You can extend this list.

    Note: refer DWL_INVC_STAT Oracle Communications Data Model table. If you are adding a new entry, then make sure to add same into DWL_INVC_STAT Oracle Communications Data Model table.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'INVC_STAT', 'INVC_STAT_CD', '0', 'DWL_INVC_STAT', 'INVC_STAT_CD', '1000');
    
    1. SRC_SYS_TAB_COL_VAL - Invoice STATUS from INVOICE_T table

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value for invoice status.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.


  9. Step 90 - EVENT_BAL_IMPACT_COLL_VW - create view

    This step rebuilds the EVENT_BAL_IMPACT_CALL_VW view. You do not need to review this step.

  10. Step 100 - EVENT_BILLING_PAYMENT_T_MAP_VW - create view

    This step rebuilds the EVENT_BILLING_PAYMENT_T_MAP_VW view. You do not need to review this step.

  11. Step 120 - OCDM SYS - Disable Constraints

    This step disables few of OCDM constraint.You do not need to review this step.

  12. Step 130 - DWL_ADDR_TYP - insert

    You can configure different address type using CONTACT_TYPE column from ACCOUNT_NAMEINFO_T table. You need to configure it same as BRM value.

  13. Step 140 - DWL_BLLG_PRD - insert

    You do not need to makes changes to this step. Refer step 80 for more detail.

  14. Step 150 - DWL_BLLG_STAT_TYP - insert

    You do not need to make changes in this step but recommended to review. Source for this mapping is BILLING_STATUS column of BILLINFO_T BRM table and OCDM target is BLLG_STAT_CD column of DWR_ACCT table.

  15. Step 160 - DWL_INVC_ADJ_RSN - insert

    You need to review this mapping and also verify with step 80 (DWL_INVC_ADJ_RSN)

  16. Step 170 - DWL_INVC_ADJ_TYP - insert

    You need to review this mapping and verify with step 80 (DWL_INVC_ADJ_TYP)

  17. Step 180 - DWL_INVC_DISC_TYP - insert

    You need to review this mapping and verify with Step20 (DWL_INVC_DISC_TYP)

  18. Step 190 - DWL_INVC_DLVRY_TYP - insert

    You can configure different invoice delivery types. STATUS from INVOICE_STATUSES_T table is BRM source. BRM adapter uses this information to find delivery type and invoice dispatch date.

  19. Step 200 - BRM_ETL_PARAMETER - TO_DATE_ETL(null)

    This step alters BRM_ETL_PARAMETER table, makes TO_DATE_ETL as nullable. You do not need to review this step.

  20. Step 210 - BRM_ETL_LOAD_PLAN - create table

    Creates table for load scheduling.You do not need to review this step.

  21. Step 220 - GRANT ALL TO OCDM_SYS

  22. Step 230 - grant all to ocdm_sys

    Grants BRM_STG object access to OCDM_SYS schema. This is required in BRM adapter mapping. You do not need to review this step.

  23. Step 240 - DWL_SRVC_TYP - insert

    You do not need to review this mapping configuration.

  24. Step 250 - BRM_ETL_PARAMETER - insert

    Deletes existing BRM_ETL_PARAMETERS and makes dummy entry. You do not need to review this step.

  25. Step 260 - UPDATE DWL_ONOFF_NET

    Updates DWL_ONOFF_NET table with proper OCDM lookup values.

  26. Step 270 - dwl_rmng_typ - insert (NONROAM)

    Makes entry into DWL_RMNG_TYP table for NONROAM. You do not need to review this step.

  27. Step 280 - DWR_BLLG_CYCL - insert

    Makes entry into DWR_BLLG_CYCL table for billing cycle. You do not need to review this step.

  28. Step 290 - DWB_INVC - DUMMY INVOICE

    Makes dummy entry into DWB_INVC table.You do not need to review this step.

  29. Step 300 - DWL_CALL_DRCTN - CALL FORWARD

    BRM add new call direction type as call forwarding. This step adds the entry into DWL_CALL_DRCTN table. You do not need to review this step.