My Oracle Support Banner

E1: 31: P48013 INCORRECT WARNING 'REQUESTED DATE IS NOT A WORK DAY' (Doc ID 2499077.1)

Last updated on APRIL 23, 2020

Applies to:

JD Edwards EnterpriseOne Shop Floor Control - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When using Manufacturing Effective Days for a process item and creating a work order for that process, the system triggers the warning message ID 1921
"Requested Date Is Not a Work Day" even though all Requested, Planned Effective and Start Dates are set as working days in the Shop Floor Calendar.
It seems that the system determines the Planned Effective Date by adding the regular calendar days for Manufacturing Effective Days value to the Requested
Date and if that day is a non-working day in the Shop Floor Calendar, it moves the date to the next working day.

Note: Issue can be duplicated using a using discrete parent item as well.

This is misleading for the users, as the warning refers to the Requested Date and not to the other dates (e.g. Planned Effective or Start Dates) and the
users need to re-check the Shop Floor Calendar and confirm that all days are correctly set as working days. Also, as the system triggers the warning
regarding the Requested Date, even if correcting this entry, the warning does not disappear because the real date that the system complains about is a
"calculated" date (=Requested Date + Manufacturing Effective Days), which does not have an editable field on the screen where the user can correct its
value.

Steps To Duplicate:
1. P4101 / P41026 - Create a process item (Stk Ty = R, Ln Ty = S) with
Manufacturing Effective Days = 15 and Leadtime Level = 10 (days); Co Product
(Stk Ty = M, Ln Ty = S) and Ingredient item (Stk Ty = P, Ln Ty = S)
2. P3003 / P3002 / P3002P - Create Routing for the process item; define the
BOM for the process item; define the output of the process item
3. P00071 - Check the SF Calendar; weekend days are non-working days.
In addition, April 2 and 17, May 1, 8 and 21 are set as non-working days.
4. P48013 - Create a WO with the Requested Date as 04-27-2018; the system
asigns the following dates:
Planned Effective Date = 05-14-2018
Satrt Date = 04-12-2018
It seems that the Planned Effective Date = Requested Date + 15 calendar days
for Manufacturing Effective Days = May 12. But since May 12 and 13 are
weekend days (non-working days), the system moves the Planned Effective Date
to the next available working day = May 14.
5. If changing the Manufacturing Effective Days to e.g. 7 days, the system
does not trigger any warning message and assigns the Planned Effective Date
by taking into account only 7 calendar days added to the Requested Date.
System's behavior is not consistent as the Work order Entry (P48013), Work
Orders Completions (P31114 / P31115) and MRP (R3483 / R3482) should trigger
the exact same results for similar situations.

Changes

 

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!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.