E1: 34: Forecast Revisions - P3460 Does Not Clear Error ID 1838 – 'No Records Selected' Even if Search Criteria Are Correct
(Doc ID 2911563.1)
Last updated on NOVEMBER 30, 2022
Applies to:
JD Edwards EnterpriseOne Requirements Planning - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
When inquiring data in P3460, if the search criterion is not valid, the system triggers the following error correctly:
No Records Selected
Go to error..
CAUSE: The search information entered did not select any records.
RESOLUTION: Check the search information for validity or change the values to
expand the search range.
ER Details:
Form P3460_W3460B
Event Last Grid Record Has Been Read
Line No 4
Error ID 1838
However, if the user does not close the P3460 screen and then uses a valid search criterion, the system still does not clear error ID 1838 as it should, and it does not display the correct records.
The issue can be reproduced at will with the following steps:
- P3460 - Find the forecast records of an item
- P3460 - In the QBE, filter by an existing Request Date. Since the search criterion is valid, the system displays the corresponding record.
- P3460 - In the QBE, filter by an invalid Request Date. The search criterion is not valid, therefore the system triggers Error ID 1838 – ‘No Records Selected’. This is correct.
Error ID 1838 - No Records Selected
Go to error..
CAUSE: The search information entered did not select any records.
RESOLUTION: Check the search information for validity or change the values to
expand the search range.
ER Details:
Form P3460_W3460B
Event Last Grid Record Has Been Read
Line No 4
Error ID 1838 - P3460 - Remove the invalid Request Date and do a Find. The system still displays error ID 1838 – 'No Records Selected'. This is incorrect.
- P3460 - In the QBE, re-add the valid / existing Request Date and press Find. System still displays Error ID 1838 incorrectly.
- P3460 - Change the Item Number and press Find. Error ID 1838 – 'No Records Selected' is still displayed incorrectly. To retrieve other forecast records for different items / branch plants, the
user needs to close the application and re-inquire.
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 |