My Oracle Support Banner

Funds Transfer Contract , Incoming MT202 on Processing is having credit value date as n+2 working days. (Doc ID 2754424.1)

Last updated on FEBRUARY 24, 2021

Applies to:

Oracle FLEXCUBE Universal Banking - Version 12.0.3 and later
Information in this document applies to any platform.

Symptoms


ACTUAL BEHAVIOR
---------------

We are facing a issue that while creating of FT contract through SWIFT message of MT 202 by running the upload job (Function ID CSSJOBBR) the contract created and value date always 2 or 3 days future date of current date or booking date. Booking date and Value date has a 3 days difference, suppose booking date is as of today then value date is future after 3 days. Like in the share contract spool from UAT Booking date is 06-Jan-2021 and value date is 09-Jan-2021.



EXPECTED BEHAVIOR
-----------------------
Value Date and Booking Date of FT Contract Should be Same.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Book a FT Contract using FTDTRONL or Incoming SWIFT Message using MT202
2. The Value date of the Contract is the Book Date+2/3 Working days


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users can see difference in Dates between the Credit and Debit legs of the transaction.

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


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