My Oracle Support Banner

Account with Next run date should not be less than GL Date. If it is less than GL date, batch job will not pick such accounts as it is in the past. DDT_RUN_DT_NEXT Data issue (Doc ID 2754840.1)

Last updated on MARCH 02, 2021

Applies to:

Oracle Financial Services Lending and Leasing - Version 14.8.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
Accounts with acc_due_dt_next - pre_bill_days with value less that the GL date present in the account. If ddt batch job tries to pick such accounts, it willl fail.

System should have an  edit validation to compare acc_due_dt_next-pre_bill_days > gl_post_dt. If acc_due_dt_next-pre_bill_days < gl_post_dt, the account should not be boarded .

EXPECTED BEHAVIOR
-----------------------
New validation EDIT required for accounts for migration where acc_due_dt_next-pre_bill_days is less than gl post dt should reject such accounts

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

1. Prepare accounts for migration with DDT_RUN_DT_NEXT less than GL DATE and ACC_DUE_DT_NEXT is > GL date.

2. Upload the accounts, by running the SET-API

3. Run the batch job, batch job will no pick those accounts or will throw error 


BUSINESS IMPACT
-----------------------
The issue has the following business impact:

Due to this issue, customer cannot process the accounts and delay in customer billing 

Changes

 

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


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