| # Shipped CUM (tdsls3532m000) Use this session to view the cumulated quantity that: You shipped for the sales schedule. Your business partner received for the sales schedule. A record can be inserted in this session when: A shipment is confirmed in Warehousing and no terms and conditions agreement is linked to the sales schedule. Shipment to the ship-to warehouse (VMI warehouse) is confirmed in Warehousing and the Method of Shipped CUM update is set to Shipment to VMI Warehouse in the Schedule Terms and Conditions (tctrm1131m000) session. An inventory consumption message is processed and the Method of Shipped CUM update is set to Consumption by Customer in the Schedule Terms and Conditions (tctrm1131m000) session. A sales release is processed into a sales schedule (revision) and the Synchronize Cums check box is selected in the Schedule Terms and Conditions (tctrm1131m000) session. Note Use the Consider Planned/Actual Delivery Date during Reconciliation check box in the Items - Sales Business Partner (tdisa0510m000) and/or the Sales Contract Line Logistic Data (tdsls3102m000) session to define how the shipped CUM is retrieved for sales schedule reconciliation. When the cumulatives are reset, LN adds a reset record in the current session. The reset record's fields have the following values: Cumulative Reset Date The CUM reset date as entered in the Reset Cumulatives (tdsls3230m000) session, or retrieved from the Sales Release Lines (tdsls3508m000) session. Transaction Date The reset record always has a transaction date of zero. Shipped Quantity -1 * reset quantity. Cumulative Shipped Quantity Cumulative shipped quantity of the last record that falls before the CUM reset date - reset quantity. Received CUM Cumulative received quantity of the last record that falls before the CUM reset date - reset quantity. Note The cumulative quantities of records with a transaction date that falls after the CUM reset date are decreased by the reset quantity. Example Reset date: 14-02 Reset quantity: 23
Transaction date | 01-02 | 05-02 | 06-02 | 0 | 01-03 | 04-03
Shipped quantity | 10 | 8 | 6 | -23 | 12 | 8
Shipped CUM | 10 | 18 | 24 | 1 | 13 | 21
Received CUM | 10 | 18 | 24 | 1 | 13 | 21
Related topics Sales schedule cumulatives Cumulative Reset Date The date and time at which a schedule's cumulatives/ authorizations are reset. Received CUM The total cumulated quantity that your business partner already received for the sales schedule. Cumulative Shipped Quantity The total cumulated quantity that you already shipped for the sales schedule. The setting of the Consider Planned/Actual Delivery Date during Reconciliation check box in the Items - Sales Business Partner (tdisa0510m000) and/or the Sales Contract Line Logistic Data (tdsls3102m000) session determines how the shipped CUM is calculated when reconciling sales schedules. Example
Shipment date | Shipment | Quantity | Shipped CUM | Delivery date | Status
--- | --- | --- | --- | --- | ---
27-9/13:00 | SHIP1 | 10 | 10 | 28-9/9:00 | Created
27-9/15:00 | SHIP2 | 10 | 20 | 28-9/11:00 | Created
27-9/17:00 | SHIP3 | 10 | 30 | 28-9/13:00 | Created
Shipment 2 arrives at 8:00 at the warehouse, before shipment 1. The following occurs if the Consider Planned/Actual Delivery Date during Reconciliation check box is cleared:
Shipment date | Shipment | Quantity | Shipped CUM | Delivery date | Status
--- | --- | --- | --- | --- | ---
27-9/15:00 | SHIP2 | 10 | 20 | 28-9/8:00 | Dispute
27-9/13:00 | SHIP1 | 10 | 10 | 28-9/9:00 | Created
27-9/17:00 | SHIP3 | 10 | 30 | 28-9/13:00 | Created
The following occurs if the Consider Planned/Actual Delivery Date during Reconciliation check box is selected:
Shipment date | Shipment | Quantity | Shipped CUM | Delivery date | Status
--- | --- | --- | --- | --- | ---
27-9/15:00 | SHIP2 | 10 | 10 | 28-9/8:00 | Matched
27-9/13:00 | SHIP1 | 10 | 10 | 28-9/9:00 | Matched (no feedback)
27-9/17:00 | SHIP3 | 10 | 30 | 28-9/13:00 | Created
Because the calculation of the shipped CUM is as follows, the out of sequence receipt does not cause a dispute:
    The total shipped quantity for the sales schedule (30) - the quantities that are
    shipped, but that are not received yet (-10, -10).
Note LN still generates disputes for shipments that are delayed till after the next shipment's delivery date. For example, if shipment 1 is delayed for more than one hour and shipment 2 is received as planned, a dispute is generated. On the View menu, you can sort your data by: Transaction Date As a result, LN shows the cumulative values based on the shipment date. Delivery Date As a result, LN shows the cumulative values based on the delivery date. If the Consider Planned/Actual Delivery Date during Reconciliation check box is selected, but you sorted your data by transaction date, LN shows the cumulative values based on the transaction date, but calculates the values based on the delivery date. This will give the following results:
Shipment date | Shipment | Quantity | Shipped CUM | Delivery date | Status
--- | --- | --- | --- | --- | ---
27-9/15:00 | SHIP2 | 10 | 20 | 28-9/8:00 | Matched
27-9/13:00 | SHIP1 | 10 | 10 | 28-9/9:00 | Matched (no feedback)
27-9/17:00 | SHIP3 | 10 | 30 | 28-9/13:00 | Created
Related topics Reconciling sales schedules Shipped Quantity The quantity of items that is shipped with the shipment. Last Receipt Quantity The last quantity that your business partner received for the sales schedule. Status The shipped CUM record's status. Allowed values Reconcile status Schedule A timetable of planned supply of materials. Sales schedules support long-term sales with frequent deliveries. All requirements for the same item, sold-to business partner, ship-to business partner, and delivery parameter are stored in the same sales schedule. Transaction Date The date on which the items are shipped. Delivery Date This field is filled with one of the following dates: The calculated receipt date when the shipment is confirmed. The actual receipt date when the shipment is received by the sold-to business partner. Shipment The shipment with which the items are shipped. Item In LN, the raw materials, subassemblies, finished products, and tools that can be purchased, stored, manufactured, sold, and so on. An item can also represent a set of items handled as one kit, or exist in multiple product variants. You can also define nonphysical items, which are not held in inventory but can be used to post costs or to invoice services to customers. The following are examples of nonphysical items: Cost items (for example, electricity) Service items Subcontracting services List items (menus/options) Unit The unit in which the item is expressed. |