Scenarios for CUM settings in the CUM adjustment rules

Refer to these scenarios for each setting option in the CUM field set.

Referenced

For referenced schedules, a combination of reference key fields is used to determine the shipped quantities and to reduce the required quantities, as in the example of Pick-up Sheet messages. By default, the in-transit quantity is set to zero.


	Current Shipped CUM	Current Received CUM	Total Shipped CUM	Total Received CUM	In-Transit Quantity
Starting CUMS	20	0	20	0	0
Shipped Shipment of 5 pieces	25	20	25	20	5
Incoming Schedule BOD Sets In-Transit Quantity to Zero and Increases Received CUMs	25	25	25	25	0

From CUM

This method uses the shipped CUM of the last packing slip and the received CUM of the incoming Schedule BOD to calculate the in-transit quantity (Shipped CUM – Received CUM = In-Transit Quantity). You can select the Check Shipments check box as an additional option for the calculation base From CUM.


	Current Shipped CUM	Current Received CUM	Total Shipped CUM	Total Received CUM	In-Transit Quantity	Calculation of Shipped CUM – Received CUM = In-Transit Quantity
Starting CUMs	28	28	28	28	0
Shipped Shipment of 5 pieces	33	28	33	28	5	33 – 28 = 5
Incoming Schedule BOD With Received CUM = 5	33	33	33	33	0	33 – 33 = 0

Note: First time Schedule BODs should not have Received CUMs. If they must be initialized with CUMs, then the PlanCUMTestHandler flag must be active only for the first schedule import.

No Received CUM

If the trading partner does not send a received CUM, you can select this option. It keeps the in-transit quantity at zero. For example, in the sequencing process of a trading partner the planning schedule does not contain a received CUM. The planning schedule is based on the delivery forecast message EDIFACT DELFOR. Only the shipped CUM is updated based on the received inventory consumption. See the field description for Update Shipped Quantity by Inventory Consumption in the topic Reviewing the settings of a CUM adjustment rule under step 6.


	Current Shipped CUM	Total Shipped CUM	In-Transit Quantity
Starting CUMS	20	20	0
Shipped Shipment of 5 pieces	25	25	5
Incoming Schedule BOD Without Received CUM Sets In-Transit Quantity to Zero	25	25	0

Note: The imported schedules should not have a Received CUM, but if they do, the system ignores the value and sets the Received CUM to 0.

From Confirmed Shipments

This method uses the existing confirmed shipments to calculate the in-transit quantity. The shipped quantity of all packing slips that are newer than the last confirmed packing slip gives the resulting in-transit quantity. The system calculates the Received CUM as Shipped CUM – In-Transit Quantity.

Note: This option only works if the received confirmed packing slip information is available.


	Current Shipped CUM	Current Received CUM	Total Shipped CUM	Total Received CUM	In-Transit Quantity	Calculation of Shipped CUM - In-Transit Quantity = Received CUM
Starting CUMs	28	28	28	28	0
Shipped Shipment of 5 pieces	33	28	33	28	5	33 – 5 = 28
Confirmed Shipment of 5 pieces	33	33	33	33	0	33 – 0 = 33

By Horizon

If the trading partner does not send a received CUM and a confirmed packing slip, or if the packing slip information is not reliable, you can select this method to calculate the in-transit quantity. The in-transit quantity is calculated using the sum of the shipped quantities from the previous combined plan’s demands that lie between the horizon dates. The horizon start and end dates can be set using the first and last requirements’ demand date, in the BOD, or set in the user interface. This then takes the in-transit quantity and distributes it through the horizon range. Any demands outside the horizon range that are not fully shipped have their shipped quantity set to zero if they are non-referenced demands. If the plan is using referenced demands, the difference of Received CUMs is calculated by taking the newReceivedCum – oldReceivedCum and this quantity is then distributed to demands outside the horizon dates. Fully shipped demands outside of the horizon dates are not added to the new plan.

For example, a Schedule BOD has been loaded and the horizon start date is 2/25 and the horizon end date is 3/24.


Requirement Date	Required Quantity	Effective Quantity	Inside Horizon Dates
2/25/24	200	200	Yes
3/3/24	200	200	Yes
3/10/24	100	100	Yes
3/17/24	50	50	Yes
3/24/24	300	300	Yes
Total	850	850	N/A

The plan has been built with the horizon range being between 2/25 and 3/24. In the user interface, two demands have been manually added outside of the horizon range on 2/7/24 and 5/7/24.


Requirement Date	Required Quantity	Effective Quantity	Inside Horizon Dates
2/7/24	200	200	No
2/25/24	200	200	Yes
3/3/24	200	200	Yes
3/10/24	100	100	Yes
3/17/24	50	50	Yes
3/24/24	300	300	Yes
5/7/24	200	200	No
Total	1250	1250	N/A

Shipped shipment of 1200 pieces. The combined plan has demands 2/7 fully shipped and demand 5/7 partially shipped. These two demands are outside of the horizon dates.


Requirement Date	Required Quantity	Shipped Quantity	Effective Quantity	Inside Horizon Dates
2/7/24	200	200	0	No
2/25/24	200	200	0	Yes
3/3/24	200	200	0	Yes
3/10/24	100	100	0	Yes
3/17/24	50	50	0	Yes
3/24/24	300	300	0	Yes
5/7/24	200	150	50	No
Total	1250	1200	50	N/A

Import a load shipment schedule with demands from 2/25 to 3/24. This is the horizon start and end dates. The delivered quantities of the demands within that date range are added up:

200 + 200 + 100 + 50 + 300 = 850 (New in-transit quantity)
1200 – 850 = 350 (newCumReceived – oldCumReceived = diffCumReceived)

The new in-transit quantity is dispersed down the demands within the horizon. While the diffCumReceived is dispersed to the demands outside the horizon dates. If the diffCumReceived is larger than the demands required quantity, then it is a fully shipped demand out of the horizon date range and is not added to the new plan. That demand quantity is then subtracted from the diffCumReceived and the next demand outside the date horizon is checked. The first demand outside the horizon date range without its demand quantity being larger than the diffCumReceived have its shipped quantity set to the diffCumReceived and net quantity recalculated using required quantity – shipped quantity = net quantity

In the combined plan, for requirements outside of horizon, demand for 2/7 was removed from the plan as it was fully shipped. Demand for 5/7 was partially shipped, so the shipped quantity is set to 0 and this demand is retained in the new plan. The shipped quantity within the horizon range 2/25 – 3/24 from the previous combined plan are added up to total the in-transit quantity (850).


Requirement Date	Required Quantity	Shipped Quantity	Effective Quantity	Inside Horizon Dates
2/25/24	200	200	0	Yes
3/3/24	200	200	0	Yes
3/10/24	100	100	0	Yes
3/17/24	50	50	0	Yes
3/24/24	300	300	0	Yes
5/7/24	200	0	200	No
Total	1050	850	200	N/A

In the single plan, the net quantity is recalculated using required quantity – shipped quantity = net quantity.


Requirement Date	Required Quantity	Net Quantity	Inside Horizon Dates
2/25/24	200	200	Yes
3/3/24	200	200	Yes
3/10/24	100	100	Yes
3/17/24	50	50	Yes
3/24/24	300	300	Yes
5/7/24	200	200	No
Total	1050	1050	N/A