My Oracle Support Banner

E1:41:GL Date Error Does Not Clear After Implementing Fix For Bug 23640165 (Doc ID 2369425.1)

Last updated on MARCH 05, 2018

Applies to:

JD Edwards EnterpriseOne Inventory Foundation - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

On : 9.1 version, Inventory
P4112, P4113, P4114, P4116

The fix for Bug 23640165 was entered for P4112 application since this application was not saving the transaction after correcting a Fiscal Year Not Set Up error generated from the GL date field in the header portion of the form.

After applying the fix for Bug 23640165, even though the GL date is corrected by the user, the error will only clear if a change is made to one of the grid lines. Client disagrees with the fix that was implemented for bug 23640165 and would like development to reconsider the fix for the following reasons:

- The error is in the GL Date field in the header. Why should the end user have to make a change to a grid line to clear an error in a header field?
- After fixing the GL date in the header, and the error not clearing, the end user has no idea why the transaction is not saving. There is not a new instruction/error telling the user to change something in the grid.
- This fix will cause end users to have to completely re-do their transactions because they will become frustrated as to why the error is not clearing.
- The problem was reported for the P4112 application, yet the fix was applied to P4113, P4114, and P4116 as well. Those applications did not have the problem. But now, they too, will leave the end user in a frustrated state, not knowing how to clear the Fiscal Year Not Set Up error message.


Steps
-------
1. Add new transaction into any of these applications: P4112, P4113, P4114, P4116
2. Enter a GL date in the header that is sometime out in the future (for a Fiscal Year that is NOT defined in the calendar), such as 01/01/2046.
3. Complete the remaining header fields as needed then add at least one grid line.
4. Hit the Save button. Result is that a Fiscal Year Not Set Up error is generated and the GL date field turns red.
5. Change the GL date field to be today’s date (or a date you know is in the calendar)
6. Hit the Save button. Result is that the Fiscal Year Not Set Up error is still displayed and the GL date field is still red.

This leaves the user wondering what to do to clear the error.


Prior to FIX for Bug 23640165, P4113/P4114/P4116 worked as follows:
------------------------------------------------------------------------------------
1. Enter transaction with GL date = 1/1/2046; receive error upon clicking on Save button.
2. Change date to today then click on Save button; error clears and the transaction saves.

Applications P4113/P4114/P4116 worked fine before fix for Bug 23640165. Only P4112 had the issue where the transaction was not being saved upon clicking the Save button (the error would clear, but the transaction would not save).


After FIX for Bug 23640165, P4113/P4114/P4116 works as follows:
--------------------------------------------------------------------------------
1. Enter transaction with gl date = 1/1/2046; receive error upon clicking on Save button.
2. Change date to today then click on Save button; error DOES NOT clear and the transaction CANNOT be saved.

End user does not know they need to change something in the grid to clear the error. And, they shouldn’t have to. The error should clear once the GL Date is fixed.

This now happens to all applications P4112, P4113, P4114, P4116.


Desired Outcome
---------------------
Bug 23640165 needs to be reversed from P4113, P4114, P4116 since these applications did not have the problem reported under Bug 23640165. A new solution needs to be implemented for the P4112 application. The way P4113, P4114, P4116 applications dealt with the error before fix for bug 23640165, incorporate that same fix in P4112 as well.

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.