A new budget line has been added to Demand Planning. This capability closes a gap between our newer Advanced Planning application and our legacy S&OP application. The Budget functionality includes the capability to manually upload and/or creating a budget by an in-app copy function that copies the total demand plan value to the budget line.

To learn more, please read the knowledge base article Demand Plan Budgets.

Previously, the Demand Plan waterfall would populate each monthly or weekly view of the plan in the waterfall based on the last approval. This means that if the planning process was not executed on a weekly or monthly basis as expected, gap would form in the waterfall. With this update, each planning period is now populated with the last approved plan to ensure there are no gaps in the waterfall.

In the example below, the planning periods of Sept 2019 through Jan 2020 are all the same since there was no new plan approved during this time span. In Feb 2020 a new plan was approved thus the plan values changed.

Previously, when users uploaded demand plans at hierarchical levels above the SKU and SKU's have life cycle settings that overlap the uploaded demand plan, there was no messaging communicating the issue to end users. We have enhanced our Error Messaging to communicate when such an issue occurs to allow users to knowingly address the issue.

Previously, when rolling periodic grouping was applied, there was no guarantee that the order would be spread perfectly in the dedicated time span. This was because the suggested order due date was based on when it was needed during the time frame and not at the beginning of the time frame. The logic has been updated to ensure that all orders are at the beginning of the rolling time bucket regardless if it is needed later.

The image below is based on a rolling 10 day grouping. The three columns are as follows:

• Original Suggested Order: Shows the results of the requirement plan with no grouping applied
• Prior Grouped Logic: Shows the previous grouping logic where the order is grouped and scheduled at the first order instance within the grouping time frame. As can be seen, orders are not placed at equivalent time spans.
• New Grouped Logic: Shows how the new logic schedules the order at the beginning of every bucketed period. This ensure orders are placed on a predictable frequency.