credit card model

View previous topic View next topic Go down

credit card model

Post  dim67 on Tue Apr 16, 2013 9:39 pm

I have a challenge with the Card Program Design (DEBIT&CREDIT), I wanted to show the following:
1. Do I keep keep the Card Program as one dimension (both Credit & Debit)
This is because the data comes in at a SYS/PRIN/AGENT & PAR/BIN level & partitioning the dimension would make the ETL lookup for the dimension keys a lot more difficult
Also, the business views programs at the description level, which both Credit & Debit have
2. We maintain the 000000000000 in the Participant BIN dimension
This is because data is coming in with these BIN numbers
3. Do I expand the Participant BIN dimension to include program attributes
4. Do I create create a FACT table for SYS/PRIN level data
What do I call this SYS/PRIN FACT table?

dim67

Posts : 15
Join date : 2012-05-05

View user profile

Back to top Go down

the model

Post  dim67 on Thu Apr 18, 2013 2:42 pm

Key Institution Key System Prin Agent Participant Id Bin Card Type Program Description Detailed Program Description LOB Program Level Start Date Stop Date
1 1 5389 1000 1000 -1 -1 V Credit Rewards Credit SysPrinAgent 1/1/2000 12/31/2999
2 1 5389 1000 2000 -1 -1 V Credit Credit Credit SysPrinAgent 1/2/2000 12/31/2999
3 2 6574 2000 1000 -1 -1 M TDS Total Debit Traditional Credit SysPrinAgent 1/3/2000 12/31/2999
4 2 6574 2000 2000 -1 -1 M TDS Total Debit Rewards Credit SysPrinAgent 1/4/2000 12/31/2999
5 2 6574 2000 3000 -1 -1 M TDS Total Debit Traditional Credit SysPrinAgent 1/5/2000 12/31/2999
6 1 -1 -1 -1 123456 123456 V TDS Total Debit Traditional Debit ParticipantBin 1/6/2000 12/31/2999
7 1 -1 -1 -1 123456 1234567 V TDS Total Debit Rewards Debit ParticipantBin 1/7/2000 12/31/2999

dim67

Posts : 15
Join date : 2012-05-05

View user profile

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum