OBPM|Incorrect Debit Value Date Derivation For Backdated Incoming MT/MX Cross Ccy Payment (Doc ID 3078555.1)

Last updated on APRIL 13, 2025

Applies to:

Symptoms

On : 14.7.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
Incorrect debit value date derivation for backdated incoming  MT/MX cross ccy payment

EXPECTED BEHAVIOR
-----------------------
Debit is on nostro account, debit value date shall always be based on the date available in the incoming message

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
a) Current system date is 12th July
b) Initiate an incoming MT/MX cross currency payment where debit is on a nostro account with value date as 10th July
c) Transaction are successfully booked in NSTP queue, for cross currency payment, with below details:
i) Booking date:12-July
ii) Original instruction date:12-July
iii)Activation date: 12-Jul
iv) Debit value date:10-Jul
v) Credit value date: 12-Jul
d) User tries to modify these transaction from NSTP queue with action NSTP_MODIFY
e) Upon click of enrich, debit value date changes to current system date of 12-Jul which is not correct
f) On save and auth of the modification as well, debit value date remains 12th July
g) Our expectation is that as debit is on nostro  account, debit value date shall always be based on the date available in the incoming message

 

Cause

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