Demand netting, demand prioritizing, and assigning quantities

The following example explains:

The basic demand netting logic and the results for the Direct Material Supply Distribution (whinh6130m000) session.
The assignment, according to priority rules, of the received quantity or the on-hand inventory to demand.

Example 1: Netting and the results for the DMS session

In the Item Data by Warehouse (whwmd2510m000) session, the following settings apply to item X and warehouses WH1, WH2, and WH3:

Parameter	WH1	WH2	WH3
DMS Supplied	Yes	Yes	No
DMS upon Receipt	Interactive/ Manual	Irrelevant	No
DMS on Inventory	Receipt and Outbound	Irrelevant	No

Assumptions

DMS demand type, DMS planning horizon, and warehouse supply structures are not taken into account.
No cross-dock orders or outbound advice in process.
DMS on Inventory is preferred above the received quantity ( Force cross-docking range is not set).
Minimum order quantity of 10 pieces.
At most, one planned order per day is created (Order interval is one day).

Warehouses and transactions

The previous figure shows three warehouses in a cluster, and transactions for item X. Warehouses WH1 and WH2 are DMS supplied, whereas warehouse WH3 is not.

Enterprise Planning totals all transactions of the three warehouses and sees, for example, an inventory of three pieces (total of the warehouses). All transactions are sorted on date, and the planned stock is calculated, see the following figure. Note that transfers T1 and T2 are both skipped, because these move goods within a cluster, so the net result is 0. The Generate Order Planning (cprrp1210m000) session must create planned supply orders whenever the planned stock drops below zero or below the safety stock.

Enterprise Planning creates five planned purchase orders. The first planned order at 10/4/2005 is planned one day before the requirement date of sales order S1. The second planned order for 10 pieces is enough to supply sales orders S2 and S3, and so on. All planned orders are created for the default warehouse of the plan item, in this case warehouse WH1.

Generation of planned supply orders

DMS is triggered when the first planned purchase order is released to Purchase Control and received in Warehousing as purchase order P1.

Item	X
Warehouse	WH1
Received Quantityin Inventory Unit	10 pcs.
Inventory on Hand	2 pcs.

After receiving the goods, distribution in the DMS session is as follows:

Priority	Date	Demand	WH	Shortage	Assigned Received Quantity	Assigned Inventory	Cross-dock Order
104	12-4-2005	Sales S2	1	5	3	2
106	14-4-2005	Sales S4	2	9	7
203	10-4-2005	Sales S1	1	10
205	13-4-2005	Sales S3	2	5
212	15-4-2005	Transfer T2	1	5
500	20-4-2005	Forecast F1	2	20

Orders (Sales S5 and JSC M1) of warehouse WH3 are ignored, because this warehouse has the DMS Supplied check box cleared. However, TPOP on WH3 did plan a warehouse transfer from WH1 to WH3, and this transfer T2 is considered as demand on WH1. This is even the case if warehouse WH3 would be part of another cluster.

Note

DMS can also respond to demand outside the warehouse cluster.

Transfer T1 is to a DMS-supplied warehouse (in the same cluster), and therefore ignored. A transfer from WH1 to WH2 is a demand order to sending warehouse WH1, but is in fact a movement/shift of demand from WH2 to WH1, for example, a sales order in WH2. Because DMS takes the original demand (sales order) from WH1 into account, the warehouse transfer demand on WH2 must be ignored. Otherwise, DMS supplies twice for the same sales order.

Note

DMS ignores warehouse transfers between two DMS-supplied warehouses in the same cluster.

Demand orders are now sorted on priority, the lowest value indicating the highest priority.

Demand orders are netted against stock.

Note

DMS ignores planned receipts when netting.

The netted quantity is shown as shortage. Sales order S2 requires five pieces. Only two pieces are on hand in warehouse WH1, which implies a shortage of three pieces.

Similarly, sales order S4 consumes stock of warehouse WH2, and has a shortage of nine pieces. Note that the sales order S1 demand date precedes the demand date of S2, but due to lower priority, S1 does not consume the stock.

Receipt of 10 pieces is first allocated to sales order S2, for thee pieces, and then the remaining seven are allocated to sales order S4.

Note

On-hand stock in the supply warehouse is only taken into account if DMS on Inventory is selected in the Item - Warehousing (whwmd4600m000) session.
On-hand stock in the destination warehouses is always taken into account, irrespective of any DMS on Inventory setting.

Generated transfer orders, cross-dock orders, and outbound advice

If the DMS proposal is accepted, the three and seven pieces must be shipped to the proper location.

If you approve and process the DMS run, LN performs the following process steps:

For sales order S2:

Creates cross-dock order CD2 on WH1 to move the three pieces to a staging location in WH1. This cross-dock order is related to sales order S2.
Creates cross-dock order line of three pieces for the cross-dock order. This cross-dock order line is related to the received purchase order (line) P1.
Generates and releases outbound advice OA1 of two pieces for sales order S2.

For sales order S4:

Creates transfer order T3 from WH1 to WH2 for seven pieces.
Creates cross-dock order CD3 on WH1 to move the seven pieces to a staging location in WH1. This cross-dock order is related to the outbound order line of transfer order T3.
Creates cross-dock order line of seven pieces for cross-dock order CD3. This cross-dock order line is related to the received purchase order (line) P1.
Creates second cross-dock order CD4 to move the seven pieces in WH2 from receiving to staging location. Cross-dock order CD4 is related to sales order S4.
Creates cross-dock order line for cross-dock order CD4. This cross-dock order line is related to the inbound order line of transfer order T3.

Note

The second cross-dock order is only created if the order falls within the time fence as defined in the Item Data by Warehouse (whwmd2510m000) session. Otherwise, the goods are inbounded (IA3).

If all procedure activities are set to Automatic, the cross-dock orders, outbound advice, and transfer orders are processed. Five pieces (3 + 2) end up on the staging location of WH1, seven pieces are cross-docked, transferred, and again cross-docked, to end up on the staging location of WH2.