My Oracle Support Banner

E1: 34: Forecast Consumption Logic with No Date Branch Plans Past Due Forecast Quantity (R3483) (Doc ID 3069340.1)

Last updated on JANUARY 30, 2025

Applies to:

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

Symptoms

When running R3483 over two or more branches with mix of items and various planning fence rules, with a blank date branch per suggested setup for proper processing of H forecast consumption planning fence rule items, there is an intermittent issue with the planning of past due forecast quantities.  Single Item planning does not seem to duplicate the issue.  

Steps:  

  1. P41026 - Verify that for suspect planning items, the same H planning fence rule is used across all item branch records.  
  2. P41026 - Set the forecast consumption items as Planning code 1, 2, or 3 and use the same in the R3483 data selection.  
  3. P41026 - Assign the H and other planning fence rule items to a select master planning family or to a select few planning fence rules.  
  4. Run R3483, data selecting by specific branches, planning families, and Planning codes, to start.  
  5. Review P3413 for time series quantity type -FCST quantity with a positive quantity placed in the Past Due 1 (PD1) bucket.  This is F3413.QT Quantity Type '50' with F3413.STRT Start Date = blank.  
  6. R3483 - If no problem records present, expand data selection to additional branches and planning families.  Given a certain set of data, the issue can be duplicated at will.  Past Due forecast is planned and is written to the P3413 Time series.

Cause

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.