My Oracle Support Banner

E1: 34: Master Planning Schedule - Multiple Plant - R3483 Using Forecast Consumption Logic Plans with Past Due Forecast (Doc ID 3013188.1)

Last updated on MARCH 28, 2024

Applies to:

JD Edwards EnterpriseOne Requirements Planning - Version 9.2 and later
Information in this document applies to any platform.


When forecast consumption logic is enabled and MRP runs over both forecast consumption planning fence rule items and also with non-forecast consumption planning fence, such as G planning fence rule, forecast is selected from F3460 with no criteria for the date to not be in-the-past.


  1. P41026  - Enter a forecast consumption planning item, say item A in branch M10, followed by an item with another (G rule) planning fence rule, such as same item A or another item B, but in a branch, such as M20, that is processed (per ascending order) after the H planning fence rule item and branch.
  2. P3460 - Enter future dated and past dated forecast for each item in the planning run.  G and H rules used in this test, as they each plan to forecast records.  
  3. R3483 -Run MRP in MCU ascending order, followed by MCU in descending order.  The first item planned is H forecast consumption item.  Item in M30 descending or item in M10 Ascending.  
  4. Review Time Series and messages.  When item in M30 is first item planned, the entire past due forecast quantity is populated in the -FCST past due 1 (PD1) period bucket.  When the item in M30 is planned last, not first, then the -FCST in PD1 is blank, as expected.


To view full details, 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 a vibrant support community of peers and Oracle experts.