TM1 Forum

Hi All,

I've a cube (A) that displays the claims details by several granularity for an account. I need a report that fetches summarized details from cube A and hence I've built a cube (B) with minimal granularity i.e. this cube has just the account, Claim incurred date and measure dimension (which is different from cube A). Since the structure of both the cubes are different, I'm not able to use DB function in cube B's rule. To overcome this issue, I created a different cube (C) whose structure is same as cube A but with different measure dimension. In this cube C, the rule to fetch required data from Cube A does not work using DB function despite the rule saving as ok. Even if I hard code a number to be displayed at leaf level, the cube C still does not display that number.

Could somebody please guide me on displaying the summarized details in Cube B. Thanks for your time and help.

Please upload the rule/feeders you tried and details of the dimensions in each cube.

Structure of Cube A (Detailed Cube)
-Claim Incurred Date
-Unique Key that identifies each of the claims
-Type of Risk
-Type of Service undertaken
-Account
-Detailed Measure Dimension - Member Name, Number, Claim $ amt, Claim Paid amt, Subscriber number etc

Structure of Cube B (Summarized Cube)
-Claimed Processed Date
-Account
-Summarized Measure Dimension - Total Dollars paid to Account, Total Claim Lines

Structure of Cube C (Cube built with similar structure as A in order to use DB function)
-Claim Incurred Date
-Unique Key that identifies each of the claims
-Type of Risk
-Type of Service undertaken
-Account
-Summarized Measure Dimension - Total Dollars paid to Account, Total Claim Lines

Rule written in Cube C

['Total dollars paid to Account' ] = N: 1234; (Hardcoded a number for test purpose. Although the rule saves, the number is not written to the measure element)

['Total dollars paid to Account' ] = N: DB('Cube A', !IncurredDt, !UniqueKey, !Risk_Type, !Type of Service, '3620999', 'Claim $ Amt'); (Although the rule saves, the number is not written to the measure element

Could you please assist me loading summarized values from Cube A into Cube B.

Looking at your cube design it seems quite likely that you are treating TM1 as a relational engine rather than a cube-based analytics (OLAP) engine:

Structure of Cube A (Detailed Cube)
-Claim Incurred Date
-Unique Key that identifies each of the claims
-Type of Risk
-Type of Service undertaken
-Account
-Detailed Measure Dimension - Member Name, Number, Claim $ amt, Claim Paid amt, Subscriber number etc

Structure of Cube B (Summarized Cube)
-Claimed Processed Date
-Account
-Summarized Measure Dimension - Total Dollars paid to Account, Total Claim Lines

It is entirely feasible to summarise your content, but you will need to take some steps to get there:
- Dimensions you are 'summarising over' need to have a total element. These would be Unique Key, Type of Risk, and Type of Service
- Dimensions which are 'related' need to have structures put in place to do that eg Total Claim Lines in Cube B needs to match to a consolidated element 'Total Claim Lines' in Cube A.
- I'm far from clear how you relate the two date dimensions (and, btw, holding days in a TM1 dimension - if you are - could well be more 'granular' than is really sensible). How do you intend to link Claim Incurred Date to Claim Process Date?
When you've solved these issues, you need to consider whether to use Rules or TI. Personally, I tend to go for Rules on traceability grounds, combining them with TIs to freeze the output from complex calculations across to somewhere that users can analyse quickly. However, if you do, you need to write feeders that work - and from the thread so far, you will probably find that pretty challenging. Since your focus is summarisation, a TI approach is probably preferable. In either case you need to extend the content of Cube A to deliver the numbers which are needed in Cube B. From what I can see it may be better to go back to the business to find out what they are trying to deliver and then redesign:
- Drop the Unique Key
- Include Claim Incurred Month and Claim Processed Month as two separate dimensions in your new Cube A
Then (I think) Cube A, at summary level, should be pretty close to Cube B. You may not even need Cube B as TM1 cumulates on the fly very efficiently.
Good luck