Account opening and closing. 1 or 2 business processes
4 posters
Page 1 of 1
Account opening and closing. 1 or 2 business processes
Hi,
Opening an account is a separate process to closing and account. Would this be 2 separate processes with 2 fact tables?
Also opening an account generates no metrics. Is that a factless fact?
Thanks
M
Opening an account is a separate process to closing and account. Would this be 2 separate processes with 2 fact tables?
Also opening an account generates no metrics. Is that a factless fact?
Thanks
M
Marmite- Posts : 3
Join date : 2015-08-10
Re: Account opening and closing. 1 or 2 business processes
It could just be dimensional attributes of the account. Is there a use case?
Re: Account opening and closing. 1 or 2 business processes
The accounts are like bank accounts, they are opened and are of a specific type. We need to analyse new accounts, when accounts are funded, fees applied, change type etc.
Would I have a one fact which is account and have the open date, account type, close date as dimensions?
Thank you for your help
Would I have a one fact which is account and have the open date, account type, close date as dimensions?
Thank you for your help
Marmite- Posts : 3
Join date : 2015-08-10
Marmite- Posts : 3
Join date : 2015-08-10
Re: Account opening and closing. 1 or 2 business processes
I think the answer is the typical "it depends".
If you analytic requirements require analysis of the account activity (How many accounts opened, how many closed, how many stale etc) - then perhaps a fact table is warranted to track these events/states.
If Your analytics only require the account state to provide context (How much growth on accounts opened in the past 6 months), then opening date, closing date etc can just be attributes of the account dimension.
If you analytic requirements require analysis of the account activity (How many accounts opened, how many closed, how many stale etc) - then perhaps a fact table is warranted to track these events/states.
If Your analytics only require the account state to provide context (How much growth on accounts opened in the past 6 months), then opening date, closing date etc can just be attributes of the account dimension.
LAndrews- Posts : 132
Join date : 2010-05-13
Location : British Columbia, Canada
Re: Account opening and closing. 1 or 2 business processes
I personally would regard an account opening as a fact. It's a business process that you can map on your bus matrix.
If you're talking about retail banking, then you'd presumably have dimensions associated along the lines of:
Time - Account Opened Date
Location - Which branch did the opening take place at?
Account Type - Which type of account was opened?
Customer - Who opened it?
Sales Person/Employee - Who gets the credit for doing it?
Other possible degenerate dimensions:
Person age at opening (if you wanted to do age profiling of new accounts)
The fact would be: Accounts Opened, nearly always populated as 1
Then you'd have similar for closing, but could include Closure Reason to try whether it is instigated by the bank or customer and why it was closed, again with a fact nearly always populated as 1.
Hopefully that's a decent starter for ten for you.
You can always build aggregate tables on these to exclude customer level transactions - accounts opened by branch and type per day would provide a decent set of metrics, allowing you to see what day is most popular for account openings, etc.
If you're talking about retail banking, then you'd presumably have dimensions associated along the lines of:
Time - Account Opened Date
Location - Which branch did the opening take place at?
Account Type - Which type of account was opened?
Customer - Who opened it?
Sales Person/Employee - Who gets the credit for doing it?
Other possible degenerate dimensions:
Person age at opening (if you wanted to do age profiling of new accounts)
The fact would be: Accounts Opened, nearly always populated as 1
Then you'd have similar for closing, but could include Closure Reason to try whether it is instigated by the bank or customer and why it was closed, again with a fact nearly always populated as 1.
Hopefully that's a decent starter for ten for you.
You can always build aggregate tables on these to exclude customer level transactions - accounts opened by branch and type per day would provide a decent set of metrics, allowing you to see what day is most popular for account openings, etc.
mark_p- Posts : 1
Join date : 2015-09-15
Similar topics
» Identifying business processes
» Including two business processes in one report
» (Text)book on core business processes
» Modelling two independent business processes related to a single event
» Joining indirectly related business processes in a dimensional model
» Including two business processes in one report
» (Text)book on core business processes
» Modelling two independent business processes related to a single event
» Joining indirectly related business processes in a dimensional model
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum