Example of Updating Commits Mid-Cycle

During a planning cycle, if there is a change in the commit quantity mid-cycle, the schedule details are versioned and the commit quantities are updated.

You need not provide commits across all the time buckets at the same time. For example, you can commit buckets 1-3 on Monday and commit buckets 4-8 on Tuesday.

Whenever you cancel a forecast, suppliers will need to resend the bucket they have already sent with the quantity set to 0.

If the supplier commits at a higher aggregation level, the previous commits within the time frame are automatically canceled. New schedule details are created and up-versioned and the commit quantity is set to 0.

For example, if the commit values are updated during the planning cycle 2-Jan to 3-Jan:

• Commit Version 1 on 2-Jan:

  • 6-Feb to 13-Feb: 500

• Commit Version 2 on 3-Jan:

  • 6-Feb to 6-Feb: 200

  • 8-Feb to 8-Feb: 300

  • 6-Feb to 13-Feb: 0 (Version previous commit and set quantity to 0)