My Oracle Support Banner

Date format issue when the date column is hard coded in F2T screen (Doc ID 2599540.1)

Last updated on OCTOBER 17, 2019

Applies to:

Oracle Financial Services - Regulatory Reporting for Reserve Bank of India - Lombard Risk Integration Pack - Version 8.0.7 and later
Information in this document applies to any platform.

Symptoms

On platform 8.0.7 version

ACTUAL BEHAVIOR
---------------
In 805 platform version when we hard code a DATE column in F2T screen the target table gets populated with the same date format which is hard coded but after upgrading to 807 the target date format has been changed which is not as expected

In 805 environment-

Hard coded value - to_date('01-JAN-1901', 'DD-MON-YYYY')
Value in target table after F2T execution- 01-JAN-1901

In 807 environment-

Hard coded value - to_date('01-JAN-1901', 'DD-MON-YYYY')
Value in target table after F2T execution- 01-JAN-0001

EXPECTED BEHAVIOR
-----------------------
F2T execution should pass the same date into target table when it is hard coded in UI

STEPS
-----------------------
The issue can be reproduced with the following steps:


1. Go to F2T mapping screen and hard code any of the DATE column as follows - to_date('01-JAN-1901', 'DD-MON-YYYY')
2. Execute the F2T
3. Check the target column for which it is hard coded
4. Target column has the date value 01-JAN-0001 

BUSINESS IMPACT
-----------------------
There is a custom query built on the target table used in the F2T and because of the DATE format mismatch the custom query is failing

Changes

 Upgrading the ofsaa platform version from 805 to 807

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
References


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