Examples: KPI Value Distribution Based on Time Granularity
These examples show how time granularity affects a calculation.
Required Editions
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled |
For period type time granularity, the calculation and distribution of weekly values remain the same regardless of the number of days in a week (periods or custom periods). The calculation is the same for all periods because the values are distributed by weeks and not days.
The editable KPI in this example has this configuration.
| KPI Definition Field | Value |
|---|---|
| Distribution Order | Planning Hierarchy-> Time |
| Distribution Type (Planning Hierarchy) | Copy |
| Distribution Type (Time) | Equal |
| Aggregation Rule | Avg |
| Total Calculation Rule | Avg |
| Merge Rule | Sum |
| Time Granularity | Period |
The total manual input for Tactic 1 and Tactic 2 is 100. Here’s how the values are distributed.
- The distribution across the planning hierarchy is Copy, and the time hierarchy is Equal. The manual inputs are copied to the product total levels. The product total levels are further equally divided by the total number of weeks. Weekly values at the product level are 25 (100/4).
- The total value at the product level is calculated by applying the KPI’s total calculation rule to the weekly values.
- The total values at the higher levels of the hierarchy (tactic) are calculated by applying the KPI’s aggregation rule to the total values at the lower levels.
Here’s how the values are distributed.
| Total | Week 47 | Week 48 | Week 49 | Week 50 | |
|---|---|---|---|---|---|
| KPI | 100 | 25 | 25 | 25 | 25 |
| Tactic1 | 100 | 25 | 25 | 25 | 25 |
| Product1 | 100 | 25 | 25 | 25 | 25 |
| Product2 | 100 | 25 | 25 | 25 | 25 |
| Product3 | 100 | 25 | 25 | 25 | 25 |
| Tactic2 | 100 | 25 | 25 | 25 | 25 |
| Product1 | 100 | 25 | 25 | 25 | 25 |
| Product2 | 100 | 25 | 25 | 25 | 25 |
The ABC calculated KPI has this configuration.
| Total | Week 47 | Week 48 | Week 49 | Week 50 | |
|---|---|---|---|---|---|
| KPI ABC | 400 | 39 | 67 | 126 | 168 |
| Tactic1 | 323 | 28 | 45 | 100 | 150 |
| Product1 | 98 | 8 | 20 | 30 | 40 |
| Product2 | 109 | 4 | 15 | 30 | 60 |
| Product3 | 116 | 16 | 10 | 40 | 50 |
| Tactic2 | 77 | 11 | 22 | 26 | 18 |
| Product1 | 38 | 8 | 10 | 10 | 10 |
| Product2 | 39 | 3 | 12 | 16 | 8 |
The editable KPI has this configuration.
| KPI Definition Field | Value |
|---|---|
| Distribution Order | Planning Hierarchy -> Time |
| Distribution Type (Planning Hierarchy) | Equal |
| Distribution Type (Time) | Metric (KPI ABC) |
| Aggregation Rule | Sum |
| Total Calculation Rule | Sum |
| Merge Rule | Sum |
| Round | 2 |
| Time Granularity | Period |
The total manual input for Tactic1 and Tactic2 is 100. Here’s how the values are distributed.
- The distribution across the planning hierarchy is equal, so the tactic total values are
first equally distributed for product total levels.
- Total values at the product level for Tactic1 are 33.33 (100/3).
- Total values at the product level for Tactic2 are 50 (100/2).
- The values are distributed across weeks using KPI ABC as the metric. The factor is calculated by dividing the corresponding weekly value in KPI ABC with the total value at the product level in KPI ABC. The respective weekly values are calculated by multiplying the total value at the product level with the factor. For example, for week 47, the value at the Product1 level for Tactic2 is calculated as (8/ 38) × 50 = 10.53. Similarly, for week 47, the value at the Product1 level for Tactic1 is calculated as (8 / 98) × 33.33 = 2.72. All the weekly values are calculated in a similar manner.
- The total values at the higher levels of the hierarchy (tactic) are calculated by applying the KPI’s aggregation rule to the total values at the lower levels.
Here’s how the values are distributed.
| Total | Week 47 | Week 48 | Week 49 | Week 50 | |
|---|---|---|---|---|---|
| KPI | 200 | 22.91 | 42.81 | 64.54 | 69.74 |
| Tactic1 | 100 | 8.54 | 14.26 | 30.87 | 46.32 |
| Product1 | 33.33 | 2.72 | 6.80 | 10.20 | 13.61 |
| Product2 | 33.33 | 1.22 | 4.59 | 9.17 | 18.35 |
| Product3 | 33.33 | 4.60 | 2.87 | 11.49 | 14.37 |
| Tactic2 | 100 | 14.37 | 28.54 | 33.67 | 23.41 |
| Product1 | 50 | 10.53 | 13.16 | 13.16 | 13.16 |
| Product2 | 50 | 3.85 | 15.38 | 20.51 | 10.26 |
The editable KPI has this configuration.
| KPI Definition Field | Value |
|---|---|
| Distribution Order | Planning Hierarchy -> Time |
| Distribution Type (Planning Hierarchy) | Equal |
| Distribution Type (Time) | Equal |
| Aggregation Rule | Sum |
| Total Calculation Rule | Sum |
| Time Granularity | Sub Period |
| Object Scope | Promotion |
| Time Scope | Shipment |
Here’s the time frame of the promotion.
| Week29 | Week30 | Week31 | Week32 | ||||||||||||||||
| 1 | 2 | 3 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 1 |
| Complete | |||||||||||||||||||
| Shipment | |||||||||||||||||||
| Instore | |||||||||||||||||||
The promotion has two tactics, Tactic1 and Tactic2, with the same shipment time frame as the promotion. The total manual input for Tactic1 and Tactic2 is 100. Here’s how the values are distributed.
- Distribution across the planning hierarchy is equal, so the tactic total values are equally
distributed for product total levels.
- Total values at the product level for Tactic1 are 33.33 (100/3).
- Total values at the product level for Tactic2 are 50 (100/2).
- Distribution across the time hierarchy is equal, so the product total values are equally
distributed across the participating weeks, considering the time frame of the KPI and the
number of participating days in a week. The factor is calculated by dividing the product’s
total value with the total number of days in the KPI time frame. This factor is then multiplied
with the number of participating days in that week.
- For week 30, the value at the Product1 level for Tactic1 is calculated as (33.33 /12) × 2 = 5.56.
- For week 31, the value at the Product1 level for Tactic1 is calculated as (33.33 /12) × 9 = 25.00.
- For week 32, the value at the Product1 level for Tactic1 is calculated as (33.33 /12) × 1 = 2.78.
All the weekly values for Tactic1 and Tactic2 are calculated similarly, but week 29 isn’t considered because it’s not in the KPI time frame.
- The total values at the higher levels of the hierarchy (tactic) are calculated by applying the KPI’s aggregation rule to the total values at the lower levels.
Here’s how the values are distributed.
| Total | Week 29 | Week 30 | Week 31 | Week 32 | |
|---|---|---|---|---|---|
| KPI | 200 | — | 33.33 | 150.00 | 16.67 |
| Tactic1 | 100 | — | 16.67 | 75.00 | 8.33 |
| Product1 | 33.33 | — | 5.56 | 25.00 | 2.78 |
| Product2 | 33.33 | — | 5.56 | 25.00 | 2.78 |
| Product3 | 33.33 | — | 5.56 | 25.00 | 2.78 |
| Tactic2 | 100 | — | 16.67 | 75.00 | 8.33 |
| Product1 | 50 | — | 8.33 | 37.50 | 4.17 |
| Product2 | 50 | — | 8.33 | 37.50 | 4.17 |

