Example of Updating Order Forecasts Mid-Cycle
During a planning cycle, if there is a change in the plan data mid-cycle, it will be considered to be an update and any previous commits for that time bucket will be cleared.
For example, you create a collaboration plan with a weekly frequency and the start date set for Monday. If you publish a plan on Monday, January 16, any changes to the published data during the week of January 16 will be considered as an update and will clear any previous commits for that time bucket. The following week, on Monday, January 23, when the plan is published again, it will be treated as a new planning cycle.
The following table shows changes in the plan data when there are changes in the published data mid-cycle:
|
Date Data Received |
Ship-From |
Ship-To |
Item |
Values for Schedule Date 6-Feb |
Values for Schedule Date 13-Feb |
Values for Schedule Date 20-Feb |
Values for Schedule Date 27-Feb |
|---|---|---|---|---|---|---|---|
|
2-Jan-2017 |
Supplier A |
Site A |
Y |
150 units |
150 units |
150 units |
No Record Sent |
|
4-Jan-2017 |
Supplier A |
Site A |
Y |
150 units |
No Record Sent |
300 units |
300 units |
An order forecast is published on 2-Jan-2017 with a weekly aggregation and Monday as the start date. The schedule is for the weeks of 6-Feb, 13-Feb, 20-Feb, and 27-Feb. On 4-Jan-2017 the decomposition process evaluates each schedule detail and compares it to the previous item forecast received on 2-Jan-2017.
-
No update: For the aggregation week of 6-Feb, the decomposition process determines that there is no change to the pre-existing schedule detail. There are no changes in the forecast quantity, so there is no change in the commit quantity.
-
Cancel: For the aggregation week of 13-Feb, because no record was sent, the decomposition process will assume the 2/13 bucket has been canceled. The record will be versioned and the forecast quantity will be set to 0. Any commits made will remain.
-
Update: For the aggregation week of 20-Feb, because the forecast quantity changed, the decomposition process will create a new up versioned schedule detail record. The record will be versioned and the forecast quantity will be set to 300. A new commit will be expected.
-
Add: For the aggregation week of 27-Feb, because the time bucket 27-Feb did not exist previously the decomposition process will create a new schedule detail record. The forecast quantity will be set to 300. A commit will be expected.
When an order forecast is republished, the service level agreement is recalculated. For example, if the service level agreement is 2 days. If the original publish date for the order forecast is 2-Jan the due date is 4-Jan. If the order forecast is republished on 3-Jan the due date is set to 5-Jan.