The Instruction Date From NON STP QUEUE Is Not Properly Calculated (Doc ID 2993220.1)

Last updated on DECEMBER 17, 2023

Applies to:

Symptoms

On : 14.7.0.2.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
The instruction date from NON STP QUEUE is not properly calculated

When we upload a message mt103 for example with back value date 20.09.2023 (filed 32A), it goes to NON STP QUEUE, after modification the instruction date is calculating +2 business days from date 20.09.2023. The expected calculation should be +2 from booking date, (29.09.23) it cannot be a back date for credit value date.

EXPECTED BEHAVIOR
-----------------------
Proper calculation (+2 days) should have Instruction date and Credit value date matching and the calculation should be +2 from booking date or let's say system date not from activation date or let's say value date(field 32A) - only for messages that are at NON STP queue and need to be modified.
The correct way as it should be, currently only happens when the payment is processed straight through, automatically. We are asking for the same thing to happen when it goes from NON STP.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, the instruction date from NON STP QUEUE isn't properly calculated.

Changes

 Fix :- The condition to override received date is changed from Channel Type to Init Channel, Received date will get overridden only if initChannel is UI.
Components Affected
-------------------
xborderintxndatevalidator.java;

Search String
-------------
35883858;

Cause

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