There are three options:
- Option 1: Create new metric types, but with the same name
- Option 2: Don’t create any new metric type, but overwrite metric data
- Option 3: Create new metric types, but with different name
- It is possible in scorecard design to use same name called Call Frequency Attainment
- However, two identifiers are used; the identifier of old one is WORKLOAD_MT, while the identifier of new one is V_WorkLoadAttain
- In Metric designer, you will only see one name Call Frequency Attainment when doing metric mapping
- To figure out which one is the real one mapped; you can go to xml to determine.
- <valueSourceMapping attribute="PREVIOUS_YEAR_MT">
<valueSource type="expression">total([Metric Types].[AG_MS_VEE_WorkloadAttainment].[WorkLoadActual])/total([Metric Types].[AG_MS_VEE_WorkloadAttainment].[WorkLoadGoal])</valueSource>
- <mapping attribute="aggregate_function">
- <mapping attribute="rollup_aggregate_function">
- In strategy design, you will see two metric type with the same name, it displayed with the sequence from metric type, the old one is listed first
- In report, we can share the same strategy where each strategy element contains both old and new one. We can define filter to control what metric type to display based on scorecard.
#/* control what metric type to show */#
( (?Scorecard? starts with '2%')
and ([Metrics].[Metrics].[Metric Type External ID] not in ('WORKLOAD_MT','WORKLOAD_YEAR_MT','CUSTOMER_CALL_ENTRY_MT','PRE_CALL_PLANNING_MT','SALES_REP_ACTIVITY_MT','DAILY_CALL_AVERAGE_FOR_AB_CUSTOMER_MT','DAILY_CALL_AVERAGE_FOR_AB_Physician_MT')))
( (not ?Scorecard? starts with '2%')
and ([Metrics].[Metrics].[Metric Type External ID] not in
- Re# 6, another more flexible solution is to use data security to filter metric types to be applied.
Option 2: This is probably the better solution, as you don’t need to make any special handling in metric studio, metric strategy design and report adjustment. The only big issue is to decide how to handle the top level (All business unit). The only thing you need to touch is metric designer
- You can have multiple inputs to feed to metric type in metric designer by slice and dice manner
- Feed data at specific level, such as different business unit
- Feed data to different kinds of value, such as actual and objective
- The running sequence becomes extremely important, when extracting the same metric with multiple steps. The basic idea is overwritten, subsequent step always overwrite data from last step, which is exactly opposite approach in TM1 rule.
Option 3: This option is to make option 1 much more clearly in term of maintenance; the only change is to metric name in report, which is very easy to proceed.