Data Source

Data Source

M4V
1. bb_profit DB
  1. M4V_Cust
    1. OCIS ID (PTY_ID)
    2. GRP_PTY_ID
      1. OCIS ID (PTY_ID)
      2. OCIS ID (PTY_ID)
  2. M4V_Prod
    1. Shows all sorts of products which the client has . i.e lending limit
  3. cepm
Migration DB
1. COL/ LOLI/ DIAL UP
  1. COG
    1. Reg ID
    2. Reg ID
    3. Reg ID
      1. COM CMD ID
      2. CRISP GRO ID
      3. OCIS MRG ID
  2. Each channel shows clients' usage, such as last logon time , status, model
    1. Vol & Val of payments
      1. BACS
      2. CHAPS
      3. Faster Pay
      4. Inter Pay
  3. Single Client VIew
    1. SCV1_ACC
      1. REG_ID
        Annotations:
        Instead of having three different columns for each channel ,Migration developers decided to put customer identifiers as REG_ID in Migrated DB.This column represents different column name in underlined channel tables or databases
        COL -agreementnumber
        LOLI - cus_ID
        Dial up - Customer_ID
      2. Account
      3. MRG_PTY_ID
        OCIS_PTY_ID
      4. CMD_ID
      5. GRO_ID
    2. SCV1_REG
      1. REG_ID
        Annotations:
        Instead of having three different columns for each channel ,Migration developers decided to put customer identifiers as REG_ID in Migrated DB.This column represents different column name in underlined channel tables or databases
      2. COG
        Annotations:
        COG - it is something similar to super group in OneMI but not exacty same.When they want to move clients to new digital platform (CBO) they want to move clients which come under one group at same time or in same batch.They grouped clients which have relation between then under one COG.basically they migrate clients who come under one COG in one batch.But this may not be the case always,as they found an issue with FI (Eg. AVIVA) .The COG AVIVA come under have more cliets which may not be directly linked to AVIVA ,so they may not want migrate all indirect linked clients to new digital platform at same time. From Digita reporting point of view: Roray may want slice and dice data from super group and COG point of view
CBO MI
1. Star Schema -OLAP
2. SQL Server
  1. Event audit
  2. webseries (payments)
  3. Client series
    1. Users
      1. Device
    2. Legal Entity
  4. Daily Reg & System report
OneMI
1. Financial performance
  1. RWA
  2. RAI
  3. Balances
    1. Drawn lending
    2. Off B/S lending
    3. CB PE Assets
    4. CB PE Liabilities
  4. Income from different prod
    1. NII
    2. OOI
2. Client View MM GC FI
  1. Supergroup / Ultimate Relationship Group Crisp ID
    1. Legal Entity ID
    2. Lgl Ent ID
    3. Lgl Ent ID
  2. Complex group (A brand)
    1. URG
    2. URG
CB DB
1. CB CUST_All
  1. Cust ID
  2. COM CMD ID
  3. CRISP ID

Next up

Description

Resource summary

Similar

	Created by lynnyu008 over 9 years ago