How You Can Edit Measures at an Aggregate Time Level

This topic explains how you can edit measures at an aggregate time level in tables in demand, demand and supply, replenishment, sales and operations, and supply plans.

You can edit a measure with an edit range that's set to only the future at an aggregate time level in only those table cells that don't contain time periods for the past. For example, if the current date is Wednesday, August 11, 2021, and you're viewing the data at a weekly level, you can't edit the forecast for the week starting August 09 or any aggregate level such as the year 2021. Instead, you can edit the forecasts for the days of August 11 and later as well as the weeks starting August 16 and later.

You can edit a measure with an edit range that's set to only the history at an aggregate time level in only those table cells that don't contain time periods for the future. For example, if the current date is Wednesday, August 11, 2021, and you're viewing the data at a weekly level, you can't edit the history for the year 2021. Instead, you can edit the history for the days before August 11 and the weeks starting August 02 and earlier.

The same behavior applies when you summarize data across time in tables. For example, the Adjusted Shipments Forecast measure has an edit range that's set to only the future. If you summarize the measure by time in a table, the summarized value is editable only if all the included values are editable. If the current month is August 2021, you can't edit the summary for 2021, but you can edit the summary for 2022.

The same behavior also applies to plans with aggregate planning time levels. For example, if the planning time level is week, and the current month is August 2021, you can't edit measures at aggregate time levels such as quarter and year if the underlying weeks aren't editable. Instead, you can view the data at the weekly level to update the values for editable weeks.

The edit ranges of measures are enforced at the Hybrid time level in demand plans. For example, for the week starting Monday, December 31, 2029, there are two Hybrid time level members, one starting on Monday, December 31, 2029, and the other starting on Tuesday, January 01, 2030. If the forecasting time level is set to week, and the plan is run on Wednesday, January 02, the forecast would begin on Monday, December 31. But, the first Hybrid time level member is before the plan run date and considered as history. Therefore, any measure with an edit range that's set to the future, such as Adjusted Shipments Forecast, isn't editable for the first Hybrid time level member.

Thus, data integrity is ensured because you can't make changes to the values of measures outside of their configured edit ranges.