| To synchronize CUMs based on external component data |  |
| If an external component communicates schedule requirements to ERP LN and you want the cumulatives to be synchronized and reset based on the cumulative data received from the external component, select the Synchronize Cums check box in the Schedule Terms and Conditions (tctrm1131m000) session. Note If the Synchronize Cums check box is cleared, cumulatives are updated based on an order based or receipt based cumulative model, as defined in the CUM Model used field of the Sales Contract Line Logistic Data (tdsls3102m000) session. For more information, refer to To synchronize CUMs based on cumulative model. To compare and synchronize cumulative data If you have agreed to synchronize CUMs, the external component provides the Cumulative Shipped Quantity and Last Shipment when sending a new sales release line in the Sales Release Lines (tdsls3508m000) session. When the sales release is processed into a sales schedule (revision), your shipped cumulatives are compared and synchronized with the shipped cumulatives received from the external component. Based on the following fields, the cumulative data is compared: Cumulative Shipped Quantity Last Shipment Schedule Note If more than one shipped cumulative record is found with the same shipment number, the shipped CUM record with the latest Transaction Date is used for comparison. If no shipped cumulative record can be found for the sales release line’s Last Shipment, ERP LN warns that the cumulatives will not be synchronized, but that you can continue processing the sales release. To synchronize shipped cumulatives After a shipped cumulative record is found, the following can be applicable: The sales release line's Cumulative Shipped Quantity is equal to your Cumulative Shipped Quantity. Therefore, the shipped cumulative record is set to Matched in the Shipped CUM (tdsls3532m000) session. All preceding records with the Created status are updated to Matched (no feedback). The sales release line's Cumulative Shipped Quantity is higher or lower than your Cumulative Shipped Quantity. Therefore, your shipped CUM is adjusted with a correction value to equal the external component's shipped CUM. This shipped cumulative record receives the Synchronize status. All preceding records with the Created status are updated to Matched. Example
Sales Release Lines (tdsls3508m000) | Shipped CUM (tdsls3532m000)
--- | ---
Shipped CUM | Schedule | Shipment | Shipped CUM | Schedule | Shipment | Transaction date | Status | Shipped quantity | New shipped CUM
- | DJ0001 | - | 10 | DJ0001 | XXX-1 | 1 April | Matched | 10 | 10
20 | DJ0001 | YYY-2 | 15 | DJ0001 | YYY-2 | 1 May | Matched | 5 | 15
- | DJ0001 | - | - | DJ0001 | YYY-2 | Current date | Synchronize | 5 | 20
- | DJ0001 | - | 25 | DJ0001 | ZZZ-3 | 1 June | Created | 10 | 30
- | DJ0001 | - | 50 | DJ0001 | VVV-4 | 1 July | Created | 25 | 55
For the cumulative record with the Synchronize status, the following is applicable: Correction value = Sales Release Lines (tdsls3508m000) session's shipped CUM – Shipped CUM (tdsls3532m000) session's shipped CUM. Shipped quantity = correction value. New shipped CUM = old shipped CUM + correction value. To reset cumulatives After a shipped cumulative record is found, the Customer CUMs Reset Date from the Sales Release Lines (tdsls3508m000) session can differ from the Cumulative Reset Date in the Shipped CUM (tdsls3532m000) session. The following can be applicable: The sales release line's Customer CUMs Reset Date is earlier than your Cumulative Reset Date. ERP LN warns that the cumulatives will not be reset, but that you can continue processing the sales release. The sales release line's Customer CUMs Reset Date is later than your Cumulative Reset Date. In this case, sales schedule cumulatives are reset in the following sessions: Shipped CUM (tdsls3532m000) Invoiced CUM (tdsls3533m000) FAB/RAW Authorizations (tdsls3134m000) These cumulative records receive the Reset status. Note Based on the Transaction Date in the Shipped CUM (tdsls3532m000) session, ERP LN determines the applicable invoiced cumulative record and authorization record. To calculate the reset quantity Before cumulatives 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)
Example
Sales Release Lines (tdsls3508m000)
Schedule | YYYYY1
Last Shipment | XXXXX1
Shipped CUM | 80
Customer Reset Date | 10/10/10
The current cumulatives are as follows:
Shipped CUM (tdsls3532m000) | Invoiced CUM (tdsls3533m000) | FAB/RAW Authorizations (tdsls3134m000)
--- | --- | ---
Schedule | YYYYY1 | Schedule | YYYYY1 | Schedule | YYYYY1
Last Shipment | XXXXX1 | - | - | FAB Authorization | 100
Shipped CUM | 100 | Invoiced CUM | 100 | RAW Authorization | 100
Customer Reset Date | 9/10/10 | Customer Reset Date | 9/10/10 | Customer Reset Date | 9/10/10
Transaction Date | 15/11/10 | Transaction Date | 15/11/10 | Release Date | 15/11/10
After processing the sales release, the new cumulatives are as follows:
Shipped CUM (tdsls3532m000) | Invoiced CUM (tdsls3533m000) | FAB/RAW Authorizations (tdsls3134m000)
--- | --- | ---
Schedule | YYYYY1 | Schedule | YYYYY1 | Schedule | YYYYY1
Last Shipment | - | - | - | - | -
Shipped Quantity | -20 | Invoiced Quantity | -20 | FAB Authorization | 80
Shipped CUM | 80 | Invoiced CUM | 80 | RAW Authorization | 80
Customer Reset Date | 10/10/10 | Customer Reset Date | 10/10/10 | Customer Reset Date | 10/10/10
Transaction Date | 0 | Transaction Date | 0 | Transaction Date | 0
Status | Reset | Status | Reset | - | -
Note You cannot manually reset cumulatives in the Reset Cumulatives (tdsls3230m000) session. Related topics Sales schedule cumulatives Sales schedule authorizations Overview of sales schedule handling |