My Oracle Support Banner

Initial Record Not Populated For Parent Customer In Customer Dimension (Doc ID 2480644.1)

Last updated on MARCH 04, 2019

Applies to:

Oracle Financial Services Revenue Management and Billing Analytics - Version 2.7.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 2.7.0.0.0 version, ORMBA - Extractors and Schemas

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

We have an issue wherein, the initial record is not populated for parent customer records in BD_CUST dimension .

Considering PHI Data , we will not be able to share the actual data.

Below is an illustration for the issue.

For a customer ,'ABC' if some information(lets consider phone number changed from 888 to 999) is updated on 8-Nov then,
 below is the entry currently present in BD_CUST.

select cust_name , per_id, phone , jrn_eff_start_dttm , jrn_eff_end_dttm from bd_cust;

CUST_NAME PER_ID PHONE JRN_EFF_START_DTTM JRN_EFF_END_DTTM
ABC 123 999 08-NOV-18 01-01-4000

while the initial record is not populated in BD_CUST
-------------------------------------------------------------------------
Below is the expected output from BD_CUST:

select cust_name , per_id, phone , jrn_eff_start_dttm , jrn_eff_end_dttm from bd_cust;

CUST_NAME PER_ID PHONE JRN_EFF_START_DTTM JRN_EFF_END_DTTM
ABC 123 888 01-JAN-2000 08-NOV-18
ABC 123 999 08-NOV-18 01-01-4000


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.