Charge Account Re-Generated When Edit Requisition After Changing It Manually
(Doc ID 2501940.1)
Last updated on SEPTEMBER 28, 2023
Applies to:
Oracle iProcurement - Version 12.2.6 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.6 version,
ACTUAL BEHAVIOR
---------------
After patches are applied, the charge account is regenerating when the charge account is changed first, then the GL Date
EXPECTED BEHAVIOR
-----------------------
Expect the charge account to not get regenerated when GL Date is changed.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Go to create a new requisition
2. Go to the Edit page where the charge account is defaulted
3. Change the charge account first, then the GL Date
The message Charge Account Re-Generated is shown, and the charge account goes back to the previous value.
4. If the GL Date is changed first, then change charge account, the charge account does not get regenerated.
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 |