Migrating Legacy Account with backdated LTC run date next, system is not considering the legacy late charge dates. (Doc ID 2885643.1)

Last updated on JULY 26, 2022

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
Account Migration process, should validate NextRunDate calculated & Backdated Calculation.  Should Not reverse ACTIVE transaction posted

Account was migrated with a backdated LTC run date next, which has triggered a change in DUE DAY CUR.
Following should be done:
1. Current Logic of calculation of LTC is due_dt1 + grace days. However if the same is less than conversion date(active date), then it means that LTC for the same has been charged in legacy system and the LTC run date should be calculated as Due date next + grace days
2. any other run date next, should never be less than the migration date. If they are, they should be set as Migration Date.
3. For Migrated account, the backdated calculation should never go beyond the ACTIVE date. Also ACTIVE should not be reversed and reposted for any Migrated Account.

EXPECTED BEHAVIOR
-----------------------
For Migrated account, the backdated calculation should never go beyond the ACTIVE date. Also ACTIVE should not be reversed and reposted for any Migrated Account.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Migrate an account with LTC Run date which is behind the migrated date. LTC was charged in the legacy system, so LTC run date will be behind migrated date
2. Check whether the Due Day Cur and LTC run date next are derived correctly after migration

Changes

Cause

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