Charge Account is Modified when Requester Value Changed on Autocreated Purchase Order
(Doc ID 399341.1)
Last updated on SEPTEMBER 20, 2021
Applies to:Oracle Purchasing - Version 184.108.40.206 to 220.127.116.11 [Release 11.5]
Information in this document applies to any platform.
FORM:POXPOEPO.FMB - Enter Purchase Orders GUI
Changing requester on autocreated purchase order causes the charge account for an expense destination purchase order to be changed to the default account of the new requester.
Expect charge account entered on requisition to remain on PO.
The issue can be reproduced at will with the following steps:
1. Create requisition and enter any charge account.
2. Autocreate requisition to purchase order.
3. In PO, navigate to distributions and change value for Requester.
Although charge account field is grayed out, the default charge account of new requester will be inserted and save in the distribution, causing budgetary records to be created against the incorrect charge account.
Due to this issue, users cannot change requester on a purchase order without regenerating the charge account, causing PO to create accounting against the wrong charge account, and causing a mismatch between requisition and purchase order distribution. The result is that the requisition charge account A is reversed and the new encumbrance is created against (incorrect) charge account B.
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