DRP Generates Two Planned Orders / Requested Inbound Shipments On The Same Day

Last updated on JUNE 28, 2017

Applies to:

Symptoms

12.1.3.9.1 or 12.2.4.1

ACTUAL BEHAVIOR
---------------
DRP generated 2 Planned inbound shipments on the same day.
When reviewing the records, the main difference was the NEED BY Date was different for the orders

EXPECTED BEHAVIOR
-----------------------
The Planned inbound shipments for the same day should be combined into single inbound shipment

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Run constrained DRP plan.
review the results.

EXAMPLES:

1. DIAGNOSTICS
   1. Item Definition Detail report for item in both Source Org and Destination Org
      Check for Order Modifiers, Safety Stock settings, ask about User Defined safety stock
   2. SQL output in XLS format
      
      select a.item_name, b.*
      from msc_system_items a, msc_supplies b
      where a.PLAN_ID in (-1,&plan_id)
      and ITEM_NAME like '&item_name'
      and organization_code in ('&org_code1','&org2')
      and a.inventory_item_id=b.inventory_item_id
      and b.organization_id=a.organization_id
      and a.sr_instance_id=b.sr_instance_id
      and a.plan_id=b.plan_id
      order by b.plan_id, b.organization_id, b.inventory_item_id,NEW_SCHEDULE_DATE;
      
      
      
   3. The Horizontal Plan (HZ) output for the item in both orgs
      - make sure /Tools /Preferences include all relevant rows - Target quantity, Maximum quantity and safety stock along with Shipments,etc.
      - set preference buckets to 30 days  / 30 weeks / 1 period
      
      Open HZ plan for the item including both orgs - then rt-click on the item name and copy horizontal plan
      Then use ctrl-V to paste into XLS file
      
      
   4. In XLS file also provide screen shots of the workbench showing all relevant Date columns and Order Number column
      and the expanded pegging for the order
      
      
   5. MBP DAT files per Note 245974.1 - #4

E.G. #1 - Item A - Plan run Date 21-SEP

No Order modifiers or safety stock driving item results for this example

We have order quantities of 20500  and 1700
The differences we can see are:
Order Date time has different timestamp
9/21/2015 12:12 - 1700
9/21/2015 23:53 - 20500

Dock Date  -  Due Date hav different timestamp
9/27/2015 12:16 - 9/29/2015 12:16
9/27/2015 23:57 - 9/29/2015 23:59

Need By Date is different
9/21/2015
9/30/2015

Forecast driving demand seen in pegging for each order lines
For Order qty 20500 - all the forecast in the plan + Target Quantity due on 21-SEP drive this order - all Late forecast and Target Quantity satisfied by this order
-- Noted the pegging to forecast was not for full 20500 and the left over quantity was seen as Target Quantity in HZ plan
-- DRP pegging does not have pegging lines for Target or Safety Stock quantities - so it is important to review the HZ plan for these values

For Order Qty 1700 - the forecast due on 30-SEP was satisfied on time by this order
Target Quantity from HZ Plan was level and did not change

E.G. #2 - Item B - Plan Run Date 23-SEP

No Order modifiers or safety stock driving item results for this example

Order Date time has different timestamp
9/23/2015 13:40 - 16,400
9/23/2015 23:53 - 900

Dock Date  -  Due Date hav different timestamp
9/29/2015 13:44 - 10/01/2015 13:46
9/29/2015 23:57 - 10/01/2015 23:59

Need By Date is different
9/23/2015
10/04/2015 -- the Need By date is AFTER the Due Date

For Order qty 16,400 - all the forecast in the plan + Target Quantity due on 23-SEP drive this order - all Late forecast and Target Quantity satisfied by this order
For Order Qty 900 - the forecast due on 04-OCT AND the change in Target Quantity drive this order
-- Noted for BOTH order lines, that the pegging to forecast was not for the total qty and could see the difference was the Target quantity in HZ plan
Target Quantity from HZ Plan was changing and increasing - and this caused the Due Date to be Earlier than the Need by Date

 

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot get expected result.

Cause