E1: 34: Branch Plant 'ALL' Required Even With Date Branch Defined in Processing Option (Doc ID 2007494.1)

Last updated on DECEMBER 16, 2015

Applies to:

JD Edwards EnterpriseOne Requirements Planning - Version 9.0 to 9.0 [Release 9.0]
Information in this document applies to any platform.

Symptoms

E1 9.0 / MRP R3483 and R3482

MRP Messages (P3411) can be incorrect when running multi-facility MRP, R3483 if the Date Branch is defined in the processing options (Multi-Facility tab, option #1) but the calendars
for Branch Plant 'ALL' or calendars for all of the branch plants in the Data Selection are not setup.
If the Date Branch is defined in the R3483 processing options and calendars through the planning horizon are setup for this branch, no other branch plant calendars should be required.

The issue occurs when an inventory lot number was treated as if it were a non-lot inventory (effective all the time and never expired)
It happens if:  
-   Shop floor calendar for the B/P that the lot inventory resides or ‘ALL’  doesn’t exist. (The month of the lot effective date)
-   Expiration date processing option is on.
-   There is an inventory that has a lot number.

(Regarding R3482 the shop floor calendar for the branch that MRP processes or branch ‘ALL’ must be setup).

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