My Oracle Support Banner

FCIS - Unitholder History Data Store Not Having Consistent Timestamp (Doc ID 2700499.1)

Last updated on AUGUST 18, 2020

Applies to:

Oracle FLEXCUBE Investor Servicing - Version 12.4.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.4.0.0.0 version, Production Support-SET

Symptoms of the Problem:
Unitholder History data is not consistent for the field date time stamp value across all data stores. The existing Unitholder which is having UH Intermediary maintained and ensure time zone maintenance in the system is correct with AGY timezone which is different than DB timezone settings (example DB timezone is GMT +8:00 and application AGY is BST time zone).

System is logging all the history table with consistent Local Time and date for the change log entry except the tables UHINTERMEDIARYHISTORYTBL, KYCUNITHOLDERHISTORYTBL and UHTAXINFOHISTORYTBL.

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.