E1: 34: FWO in Past Due Does Not Consume Lot Due to Expire (Doc ID 1558126.1)

Last updated on AUGUST 07, 2015

Applies to:

JD Edwards EnterpriseOne Requirements Planning - Version XE and later
Information in this document applies to any platform.
P3413 Time Series
R3482 MRP
System 34: Resource requirements Planning

Symptoms

This document is part of an Information Center - to see other documents related to MRP, please use the links provided below: Information Center: Overview of JD Edwards EnterpriseOne Requirements Planning > Information Center: Troubleshooting JD Edwards EnterpriseOne Requirements Planning > Document 1558126.1

MRP output is incorrect when the following conditions exist:
  1. Item Branch has Commitment Method set to "3" (Expiration Date)
  2. The -FWO (Firm Work Order) value is in Past Due Period 2
  3. A Lot Expiration Date occurs in the 1st Planning Period.  After MRP is run with this scenario, the LEXP is not decreased by FWO but it
  is consuming the lot that will expire in near future.
 
  STEPS TO REPRODUCE
  ==================
  1.    Add parent (STKT=M) and component (STKT=P), e.g., RAW1.  Set the Item Branch Commitment Method to3 Expiration Date, for both parent and component.
  2.    Add bill of material (BOM): 1 Parent requesting 1RAW on BOM.
  3.    In the Lot Master (P4108), add 2 lots for component RAW1 & adjust in stock as follows:
         LOT 1:  RAW1 with Expiration Date April 29th (3 days ahead from the Generation Date) = 110 each.
         LOT 2:  RAW2 with Expiration Date May 16th = 50 each.
  4.    Add a work order (WO) for the parent for 50 each with a request date in past due 2 period.
  5.    Run Order Processing (R31410) and check the parts list for a hard commitment for LOT1: ROW1, i.e., the first one that expires.
  6.    Run MRP (R3482), data selecting both the parent and the component.
  7.    Check Detail Messages (P3411) and observe that LEXP = 110 each is not decreased by the FWO quantity of 50 each.
  7.    Note it is actually decreased so LEXP=60 each on the first MRP run.  At  the second MRP run on next day, the -LEXP=110 each.  The system does not take into account the Lot Expiration date (April 29) which is not the earliest date (as per commitment method=3) and allocates the lot RAW2 (50) for this work order demand, and an additional extra demand of a planned order (+PLO) of 50 is generated.
 
  The expectation is that the LEXP takes into account the quantity committed on the work order and be decreased accordingly, and that MRP considers the commitment method and takes into account the earliest Lot Expiration date.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms