Resetting sales schedule authorizations

It depends on the value of the Synchronize Cums check box in the Schedule Terms and Conditions (tctrm1131m000) how and when the sales schedule authorizations are reset.

Synchronize Cums is selected

If you want the cumulatives to be synchronized and reset based on the cumulative data received from an external component, your shipped cumulatives are compared and synchronized with the shipped cumulatives received from the external component when processing a sales release into a sales schedule (revision).

After a shipped cumulative record is found, the Customer CUMs Reset Date from the Sales Release Lines (tdsls3508m000) session can fall after the Cumulative Reset Date in the Shipped CUM (tdsls3532m000) session. In this case, the authorizations must be reset.

Reset process

Before authorizations can be reset, a reset quantity must be calculated.

This quantity is calculated as follows:


            Cumulative Shipped Quantity from Shipped CUM (tdsls3532m000) - Cumulative Shipped Quantity from Sales Release Lines (tdsls3508m000)
         

For an example on resetting FAB/RAW authorizations, Synchronizing CUMs based on external component data.

Synchronize Cums is cleared

Over time, the FAB authorizations and RAW authorizations can be incremented to very high values. To reduce these values, you can reset the FAB/RAW authorizations in the Reset Cumulatives (tdsls3230m000) session. Authorizations cannot be reset exactly when the year is changing. As a result, updates can be stored in the FAB/RAW Authorizations (tdsls3134m000) session after the reset date. By calculating a reset quantity, these values are also included in the reset process.

To reset the FAB/RAW authorizations successfully, the following conditions must be fulfilled:

  • Suppliers and customers must use the same CUM reset date when resetting the FAB/RAW authorizations in the Reset Cumulatives (tdsls3230m000) session and the Reset Cumulatives (tdpur3230m000) session.
  • 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.
  • Suppliers must not update incoming releases or manually create new releases, because resetting can then result in wrong quantities.
Note: 
  • You cannot reset FAB/RAW authorizations for the sales schedule if a reconciliation record exists with the Dispute status and the Transaction Date is before the CUM reset date. You can view sales schedule reconciliation records in the Sales Schedule Reconciliation (tdsls3131m000) session.
  • The FAB/RAW information, as stored in the Sales Schedules (tdsls3111m000) session for a specific sales schedule revision, is never updated during the reset process. It is kept as history information.

Reset process

  1. To determine a reset quantity

    If you reset FAB/RAW authorizations, LN first determines the reset quantity. LN retrieves the reset quantity from the last FAB/RAW authorizations record prior to the CUM Reset Date that you specified in the Reset Cumulatives (tdsls3230m000) session. Which quantity is the reset quantity depends on the CUM Model used, as specified in the Items - Sales Business Partner (tdisa0510m000) session and/or the Sales Contract Line Logistic Data (tdsls3102m000) session.

    If the CUM Model used is:

    • Order Based, the Prior Required CUM is the reset quantity.
    • Receipt Based, the Received CUM is the reset quantity.
  2. To create a new FAB/RAW authorization record

    LN creates a new FAB/RAW authorization record in the FAB/RAW Authorizations (tdsls3134m000) session:

    • With a Reset Date equal to the CUM Reset Date as specified in the Reset Cumulatives (tdsls3230m000) session.
    • For which the Prior Required CUM or the Received CUM is reset.

      If the CUM Model used is:

      • Order Based, LN decreases the Prior Required CUM with the reset quantity.
      • Receipt Based, LN decreases the Received CUM with the reset quantity.