Pegging Dates Are Not Following WIP Discrete Job Dates for Lower Level Components - Discussion of Profile MRP:Create Time Fence = Yes

Last updated on JUNE 28, 2017

Applies to:

Goal

On : 11.5.10.2 version, Materials Requirements Plan in All instances:

Users have the following setup/scenario

BOM
===
JMFinGood - MPS planned Fix LT = 3 - no routing
- JMMakeOSP - MPS planned contains routing with OSP item = JMOSP - 1 per

OSP Resource = JM-OSP - PO Move - OSP item = JMOSP - Dept = ASSEMBLY

Setup routing in item = JMMakeOSP

Op Seq 10 -Dept = ASSEMBLY - 2 resources
-Res Seq = 10 - Res = JM-OSP rate = 1 - item basis - Schedule = No - PO Move
-Res Seq = 15 - Res = DL-LBR1 rate = 160 - Lot basis - schedule = Yes - WIP Move

Ran LT rollups and the above gives Fix LT = 20 (also makes proc LT = 20) - no other LT's

Created MDS = JMMDS and for End Item = JMFinGood put in the following manual demands

Qty = 1 due 07-NOV
Qty = 1 due 14-NOV
Qty = 1 due 21-NOV

Created MPS plan = JMMPS - attached MDS = JMMDS - enabled Pegging but left reservation level and hard pegging level = Null

Ran MPS Plan and checked planned orders and pegging is working as the component requirement is due at the start of the end assembly as expected. Next step is to release some wip jobs - rerun to check pegging with no changes so far

Released (no changes made) the Planned order qty = 1 for JMMakeOSP due 04-NOV-2014 and Planned Order qty = 1 for JMFinGood Qty = 1 due 07-NOV-2014

Rerunning the MPS plan to validate pegging and pickup of new wip jobs. Pegging looks the same as it did before with no changes as expected

Now go into WIP Discrete Discrete Jobs form and change the completion date of WIP job qty = 1 for item = JMFinGood from 07-NOV-2014 to 04-NOV-2014 and tell it to backward schedule from completion date so now the start date is 30-OCT-2014.

Ran the MPS plan again to see what pegging shows after the manual changes in wip. The WIP job for JMMakeOSP still shows pegging 04-NOV-2014 when I really need it 29-OCT-2014 per the change I made to the WIP job completion date. Is this by design? Does MRP:Create Time Fence = Yes come into play in this scenario?
 

Solution