Pipeline with Accumulating snapshot
2 posters
Page 1 of 1
Pipeline with Accumulating snapshot
I have accumulating snapshot design for insurance new business workflow process. The current grain in the fact table is policy level with all associated dates and measures from policy submission to being issued. So, in summary I have one activce entry per policy in the fact table. This is working very well in current BI environment.
Need help on the following new requirement:
Policy dimension can have many underwriting requirements associated to it. Similarly policy dimension is associated to many policy riders. In this case, should I be creating two additional factless fact tables with UW requirement and policy rider as dimensions along with policy and insured dimension (i.e., Policy Rider Fact and Policy UW Reqmt Fact) to handle one to many relationship with policy?
Or is there an alternate option.
I would appreciate the input.
Thanks!
Need help on the following new requirement:
Policy dimension can have many underwriting requirements associated to it. Similarly policy dimension is associated to many policy riders. In this case, should I be creating two additional factless fact tables with UW requirement and policy rider as dimensions along with policy and insured dimension (i.e., Policy Rider Fact and Policy UW Reqmt Fact) to handle one to many relationship with policy?
Or is there an alternate option.
I would appreciate the input.
Thanks!
sr_da- Posts : 14
Join date : 2009-10-19
Re: Pipeline with Accumulating snapshot
Your solution is fine.
In addition, you may also want to consider treating riders and/or underwriting requirements as a multi-valued dimension off the main fact table. An MV group structure allows you to easily do additional analysis such as, 'for policies with rider x, what are the top 5 other riders customers usually choose?' or, 'which policies have riders x and either rider y or z?'.
In addition, you may also want to consider treating riders and/or underwriting requirements as a multi-valued dimension off the main fact table. An MV group structure allows you to easily do additional analysis such as, 'for policies with rider x, what are the top 5 other riders customers usually choose?' or, 'which policies have riders x and either rider y or z?'.
Re: Pipeline with Accumulating snapshot
Thank you, appreciate the input. Could you please elaborate more on multi-valued dimension use in this scenario.
sr_da- Posts : 14
Join date : 2009-10-19
Similar topics
» Can you combine an accumulating and periodic snapshot into a single accumulating periodic snapshot table?!
» Accumulating Snapshot and Transaction Snapshot
» Fact table type
» Accumulating snapshot
» accumulating snapshot -random # of status
» Accumulating Snapshot and Transaction Snapshot
» Fact table type
» Accumulating snapshot
» accumulating snapshot -random # of status
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum