Resetting purchase schedule cumulatives

Over time, a purchase schedule's cumulatives (CUMS) can be incremented to very high values. To decrease these values, you can reset the CUMs in the Reset Cumulatives (tdpur3230m000) and Reset Cumulatives by Contract Total Line (tdpur3230m100) sessions. Although this reset is usually performed at the end of the year, the CUMs cannot be reset exactly when the year is changing. This means that updates can be stored in the cumulative sessions after the reset date. By calculating a reset quantity, these values are also included in the reset process.

Resetting is carried out based on the following cumulative (CUM) models, which you can define in the CUM Model field of the Purchase Schedule Parameters (tdpur0100m500):

  • Order based CUM model
  • Receipt based CUM model

Conditions for successfully resetting the cumulatives:

  • Suppliers and customers must use the same CUM reset date when resetting the cumulatives in the Reset Cumulatives (tdpur3230m000), Reset Cumulatives by Contract Total Line (tdpur3230m100), and Reset Cumulatives (tdsls3230m000) sessions.
  • Resetting can only take place when the releases sent by the customer, are received and approved by the supplier. If not, suppliers cannot approve releases that are processed after the reset date, because the reset dates are different. Purchase release lines with the Created, or Scheduled status are automatically reset.
  • Suppliers must not update incoming releases or manually create new releases, because resetting can then result in wrong quantities.

To calculate the reset quantity

To reset the existing CUM values, the reset quantity is determined and subtracted from the existing CUMs. In the Shipped Cumulatives (tdpur3131m000), Received Cumulatives (tdpur3132m000), Required Cumulatives (tdpur3130m000), and the Invoiced Cumulatives (tdpur3133m000) sessions, a reset record is added and the CUMs are reduced by the reset quantity. Furthermore, the FAB/RAW Authorizations (tdpur3534m000) session is reset and the release lines that are generated, but not yet sent, are reset.

Based on the CUM model, the reset quantity is calculated as follows:

  • Order Based CUM model

    Reset Quantity = last required quantity that is communicated on a release date that is prior to the new reset date. This quantity is retrieved from the Required CUM field of the FAB/RAW Authorizations (tdpur3534m000) session.

  • Receipt Based CUM model

    Reset Quantity = last received quantity that is communicated on a release date that is prior to the new reset date. This quantity is retrieved from the Received CUM field of the FAB/RAW Authorizations (tdpur3534m000) session.

Example 1 - Order Based CUM model

  • Reset date = start week 3
  • The schedule lines are generated before the reset takes place
  • Schedule line 2 is released in week 3
  • Schedule line 3 is released in week 5
Week Line 1 Required CUM before reset Line 2 Required CUM before reset Line 3 Required CUM before reset Required CUM after reset
1 20 20 - 20 - 20 20
2 20 40 - 40 - 40 40
3 20 60 5 45 - 45 5
4 20 80 5 50 - 50 10
5 20 100 5 55 20 70 30
6 20 120 55 110 5 75 35
7 - - 5 115 5 80 40
8 - - 5 120 5 85 45
9 - - - - 5 90 50
10 - - - - 5 95 55

TOTALS CUM line 1 CUM line 2 CUM line 3 CUMs after reset
Start CUM 0 40 50 10

The reset date starts in week 3. Because of the Order Based CUM model, resetting is carried out based on the required cumulatives. At the end of week 2, the reset quantity is 40. As a result, all CUMs are updated by -40 from the CUM reset date (week 3) on.

Example 2 - Receipt Based CUM model

Take the same data from the previous example, but also take into consideration the following data:

Week Received quantity Received CUM before reset Received CUM after reset
1 10 10 10
2 25 35 35
3 20 55 20
4 - 55 20
5 5 60 25

The reset date starts in week 3. Because of the Receipt Based CUM model, resetting is done based on the received cumulatives. At the end of week 2, the reset quantity is 35. As a result, all CUMs are updated by -35 from the CUM reset date (week 3) on.

The totals from example 1 would then arrive at:

TOTALS CUM line 1 CUM line 2 CUM line 3 CUMs after reset
Start CUM 0 40 50 15
Related topics