Storage of Subperiod Values for Writeback KPIs
In your sales organization, if you enable Subperiod Writeback, a writeback KPI is stored based on the value of the subperiod field that you select for the KPI. For example, if you set the subperiod to Week Splits By Month, the system creates structures to support the calculation of weekly splits.
Required Editions
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled |
To store subperiod values, make sure that you:
- Set Writeback to Subperiod in the relevant Sales Organization.
- In the KPI Definition, set Subperiod to Week Splits By Month under Storage Options Settings.
Week splits writeback is only at the product level and only for KPIs. Subperiod KPIs aggregate for volume and cost, but not for rates or prices.
Writeback KPIs for subperiods are stored in these tables:
- Account Measure Result JSON
- Claim Tactic Measure Result JSON
- Promotion Measure Result JSON
| Object | Configuration |
|---|---|
| Promotion |
|
| KPI Definition |
|
| Sales Organization |
|
The promotion ranges from Tue, Dec 29, 2020, to Sat, Feb 06, 2021, and spans across seven periods (P1 to P7).
When the subperiod is set to Week Splits By Month, here’s how the week split values are determined.
- Based on parameters, such as time scope or the change in promotion or tactic time frame, the subperiod values for the KPI and product path are determined. The value of each subperiod is based on the weekday share profile.
- After retrieving the subperiod values, the week splits for each month are determined. For P1, the subperiod for the month of December forms weeksplit 0, and the subperiod for the month of January forms weeksplit 1. A similar split occurs for P7. The subperiod for January forms weeksplit 8 and the subperiod for February forms weeksplit 9.
- After determining the weeksplits, the system merges the subperiod values to calculate the weekly values.
- The writeback value for each month is the sum of the weeksplit values of that month. So, the writeback value for December = 500, February = 1,600, and January = the sum of the remaining weeksplit values = 200 + 1,000 + 2,000 + 1,000 + 1,200 + 1,500 + 200 = 7,100.
If the subperiod is set to Week Splits By Month, each period or week can have a maximum of two splits.
When you manually input KPIs monthly or quarterly, some values might be misallocated to adjacent months. To ensure accurate distribution of values within the monthly limits, turn on the EnableReadSubperiodWriteback setting. This lets the calculation engine use precalculated subperiod values. This feature is particularly useful for customers who edit KPIs at the monthly or quarterly level.
For the trade calendar to show accurate values for the first and last periods, your selected date range must align with the exact start and end of a calendar period (week or month). The Start Date must be the first day of a week or the first day of a month and the End Date must be the last day of a week or the last day of a month. If the selected date range doesn't align with these boundaries, inaccurate value is shown for that period.
For example, consider a standard calendar where the first week of the year starts on December 30, 2024:
- A view starting on December 30, 2024 (the exact start of the week) will show an accurate value for the first period.
- A view starting on December 31, 2024 will show an inaccurate value because it will show the full value for the entire first week.
- Enable Reading Subperiod-Level KPI Values for Monthly Distribution
Configure settings to ensure that manually entered KPI values are distributed accurately and dependent KPIs are calcuated correctly within the correct monthly or quarterly boundaries.
