Example: KPI Value Distribution When Edits For Months and Quarters is Enabled
When manual inputs are entered at a month, week, or quarter level, the values for edited KPIs are distributed down to the sub-period level. The system uses the merge rule to combine values on the sub-period level to week, month, or quarter levels. The time aggregation rule won't be used when edits for months and quarters is enabled
Required Editions
Manual inputs are then distributed down to subperiod levels for read KPIs and editable KPIs.
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled |
When a week spans two different months, it is divided into subperiods, with each subperiod corresponding to a month. For example, if a week runs from Sunday to Saturday and the month changes on Wednesday, then Sunday through Wednesday constitutes one subperiod, while Thursday to Saturday forms another.
However, when a value is entered for a month, it influences only those weeks and subperiods that fall entirely within that month. This method ensures that monthly inputs do not alter the values of neighboring months.
The editable KPI has this configuration.
| KPI Definition Field | Value |
|---|---|
| Distribution Type (Planning Hierarchy) | Equal |
| Distribution Type (Time) | Equal |
| Aggregation Rule | Avg |
| Aggregation Time Rule | Avg |
| Merge Rule | Equal |
| Total Calculation Rule | Sum |
| Time Granularity | Period |
| 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 |
| Shipment | |||||||||||||||||||
- The promotion has two tactics, Tactic1 and Tactic2. The total manual input for Tactic1 and Tactic2 is 100. Here’s how the values are distributed.
- Aggregation time rule and time granularity setting is ignored when the edits for months and quarters is enabled.
- Distribution across the time hierarchy is equal (merge rule), 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.
- A 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.
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 |
