OUA Default JRN_EFF_START_DTTM Of 01-JAN-2000 Is Too Recent
Last updated on FEBRUARY 03, 2017
Applies to:Oracle Utilities Advanced Spatial and Operational Analytics - Version 18.104.22.168.1 and later
Information in this document applies to any platform.
1. On OUA 22.214.171.124.1. there have been encountered instances where the initial JRN_EFF_START_DTTM of 01-JAN-2000 is too recent.
For meter reads it is needed to use ci_mr.read_dttm when joining to the dimensions, rather than ci_mr.jrn_update_dttm. The reason for this is that it may take a number of days for meter reads to reach CCB, in which time the property could have changed - e.g. gone from being occupied to vacant. I.e. it is a need to capture the dimensional at the time of the read, not when the read entered CCB. We will also have to retrospectively load missing/failed reads.
Is there any way that it be changed the default JRN_EFF_START_DTTM to be an older date - e.g. 01-JAN-1971 or even 01-JAN-1901?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms