Exchange Protocol Should Update XLA_EVENTS.EVENT_DATE When Updating AR Invoice GL_DATE And ACCOUNTING_DATE
(Doc ID 2138447.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Public Sector Financials (International) - Version 12.2 and later
Information in this document applies to any platform.
When a Receivables invoice is validated and Exchange Protocol (EXP) is installed, an EXP hold is placed.
As part of the EXP approval process, the invoice GL_DATE and ACCOUNTING_DATE are changed to the date the EXP Transmission Unit is approved. This is the expected functionality.
However XLA_EVENTS.EVENT_DATE is not updated accordingly.
In Release 12 because XLA_EVENTS.EVENT_DATE does not get updated, it is out of sync with the invoice GL_DATE and ACCOUNTING_DATE.
The same issue occurred in Payables (AP) and for this <Bug 21681771> - APPROVE TRANSMISSION UNIT AS FINAL APPROVER LEADS TO SLA DATA CORRUPTION has been created and a patch has been released.
The same fix is also required for Receivables (AR).
Expected that if OPSFi EXP is resetting the invoice GL_DATE and ACCOUNTING_DATE that it will also reset the XLA_EVENTS.EVENT_DATE.
The issue can be reproduced at will with the following steps:
1. Use EXP to validate and approve an AR invoice where the invoice date is earlier than the sysdate
2. The invoice GL_DATE and ACCOUNTING_DATE are changed to the date the EXP Transmission Unit is approved
3. Observe XLA_EVENTS.EVENT_DATE is not updated accordingly
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