My Oracle Support Banner

REVERSAL FROM PXSIVIEW IS POPULATING THE REVR TRANSACTION DATE AS ORIGINAL TRANSACTION DATE OF DRLQ AND CRLQ EVENTS (Doc ID 2988668.1)

Last updated on JANUARY 09, 2024

Applies to:

Oracle Banking Payments - Version 14.7.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 14.7.0.3.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
Issue in REVR Transaction date derivation.

EXPECTED BEHAVIOR
-----------------------
In REVR transaction date should be correctly derived.

STEPS
-----------------------
When reversing an incoming cross border payment using the Reverse button from PXSIVIEW screen, OBPM is passing REVR accounting entries with wrong transaction date.
System is assigning transaction date based on original DRLQ/CRLQ transaction date instead of populating transaction date for REVR entries with today’s date (Reversal Date).
This logic should only apply to Value Date and not to Transaction Date.



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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.