E1: 43E: RSS Cache Error (P43E10)
(Doc ID 1628785.1)
Last updated on FEBRUARY 05, 2019
Applies to:JD Edwards EnterpriseOne Requisition Self Service - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.
Enter Requisition application (P43E10) produces cache errors when selects Justification (text attachment) before fixing the Branch Plant error. The system also allows the order to be save and submitted despite the cache errors prompted. This causes data integrity issue with the Requisition and it can no longer be edited, or deleted.
Fetch from Cache B43E0010A37041414 Failed
Update to Cache B43E0010A37041414 Failed
The issue can be reproduced at will with the following steps:
1. User is setup without a Default Branch in P400951
2. Address Book Master for the user is set up with Business Unit ‘PM1’. This is a business unit, but not a branch plant. Since no Default Branch is set up in P400951, Requisition Self Service (P43E10) will default ‘PM1’ into the branch field.
3. At P43E10 (Requisition Self Service) – notice the branch has defaulted as PM1
NOTE: If the user corrects the Branch Plant error first, the requisition is created correctly.
4. However, the issue occurs if the user clicks the Justification hyperlink first and enters a text attachment.
5. After adding the text attachment, the user then corrects the branch plant
6. And then enters the details for the requisition, cache errors on 'Fetch from Cache B43E0010A37041414 Failed' and 'Update to Cache B43E0010A37041414 Failed' have been prompted
7. User can proceed to submit the requisition despite the error and has resulted with the following issues.
1) The Requisition Header (F43E01) doesn’t have a total amount and the number of lines is 0
2) The Requisition Inquiry shows the connection between the requisition header and detail correctly, but when you go into edit mode it loses the link to the detail lines and disabled deletion of the requisition as deletion of the detail lines are disabled.
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