My Oracle Support Banner

How Does the Customer Credit Limit Histories Stored? (Doc ID 2671350.1)

Last updated on JUNE 01, 2020

Applies to:

Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Customers Module

ACTUAL BEHAVIOR
---------------
How does the Customer credit limit histories get stored in Oracle?

There is an issue with the dates stored in the AR_CREDIT_HISTORIES table for the customer credit limit changes. A difference is seen in the CREATION_DATE in the AR_CREDIT_HISTORIES table when compared to the date originally the credit limits were updated in the system.  Because of this discrepancy in the date, an audit report is not reflecting the correct dates for credit limit changes.




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

1. In this example,  if a credit limit is updated on 01-Jan-20 for a customer. then what date will be populated in AR_CREDIT_HISTORIES for the column CREDIT_INFO_UPDATE_DATE?
2. Later the credit limit is updated on 15-Jan-20 for the same customer, what will the date populated in CREDIT_INFO_UPDATE_DATE?


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot see the correct dates in their report.

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


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