JRN Dates Not Calculated As Expected
(Doc ID 2523044.1)
Last updated on DECEMBER 04, 2019
Applies to:
Oracle Financial Services Revenue Management and Billing Analytics - Version 2.7.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On RMB v2.7.0.0.0 version, ORMBA - JRN dates not calculated as expected.
Below is a description of the problem:
We had enabled Audit on CI_ACCT_PER and CI_SA table to figure out the exact time when the account person relationships were established and contracts were created respectively.
Consider Account = 1111 , Person = 2222 , SA =3333
Querying the audit table to find the time in which Account person relationship where established:
select * from ci_audit where audit_tbl_name='CI_ACCT_PER' and pk_value1='1111'
AUDT_TABLE_NAME AUDT_FLD_NAME CRE_DTTM PK_VALUE1
CI_ACCT_PER PER_ID 1/18/2019 23:08:11 1111
Querying the audit table to find the time in which contract was created:
select * from ci_audit where audit_tbl_name='CI_SA' and pk_value1='3333'
AUDT_TABLE_NAME AUDT_FLD_NAME CRE_DTTM PK_VALUE1
CI_SA SA_ID 1/18/201923:08:11 3333
On checking the replication tables ,
select per_id,acct_id,jrn_eff_start_dttm, jrn_eff_end_Dttm from
RMB1REP.CI_ACCT_PER where per_id=2222
PER_ID ACCT_ID JRN_EFF_START_DTTM JRN_EFF_END_DTTM
2222 1111 1/18/2019 23:08:11 01/01/4000
select acct_id, SA_ID ,jrn_upd_dttm from RMB1REP.CI_ACCT_PER where
per_id=1111
ACCT_ID SA_ID JRN_UPD_DTTM
1111 3333 1/18/2019 23:08:10
Since the JRN_UPD_DTTM from SA is less than ACCT_PER JRN Dates or not between JRN start and end dates of CI_ACCT_PER,
these particular contracts gets missed and are not picked up in BF_SA_VW.
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 |