Search Results ar_credit_histories




Overview
Explore in AI Chat

Overview

The AR_CREDIT_HISTORIES table is a core data object within the Oracle E-Business Suite Receivables (AR) module, specifically for versions 12.1.1 and 12.2.2. As documented, its primary function is to maintain a historical audit trail of all modifications made to a customer's credit profile. This table is essential for credit management and compliance, providing a chronological record of changes to credit limits, ratings, and related attributes. Its role is to support auditability, enable trend analysis for credit risk assessment, and facilitate the resolution of disputes regarding credit term adjustments over time.

Key Information Stored

The table's structure is designed to capture the details of each credit profile transaction. While the full column list is not provided in the excerpt, the documented primary and foreign keys reveal critical data points. The primary key, CREDIT_HISTORY_ID, uniquely identifies each history record. The foreign keys, CUSTOMER_ID and SITE_USE_ID, link the history to the specific customer (HZ_CUST_ACCOUNTS) and, optionally, their bill-to site (HZ_CUST_SITE_USES_ALL). Typical columns in such a history table would include fields for the old and new values of changed attributes (e.g., CREDIT_LIMIT, CREDIT_RATING, RISK_CODE), the DATE of the change, the USER_ID or CREATED_BY who initiated it, and a REASON_CODE or COMMENT field explaining the adjustment.

Common Use Cases and Queries

This table is central to credit management reporting and operational inquiries. A common use case is generating a customer credit audit report for internal reviews or external auditors. Another is analyzing the frequency and magnitude of credit limit increases for a customer cohort to inform risk policy. Sample SQL patterns often involve joining to customer tables to get descriptive information.

  • Credit Change Audit for a Customer: SELECT ach.*, hca.account_number FROM ar_credit_histories ach, hz_cust_accounts hca WHERE ach.customer_id = hca.cust_account_id AND hca.account_number = 'CUST123' ORDER BY ach.creation_date DESC;
  • Recent High-Value Limit Increases: SELECT customer_id, old_credit_limit, new_credit_limit, change_date FROM ar_credit_histories WHERE change_date > SYSDATE - 30 AND (new_credit_limit - old_credit_limit) > 10000;

Related Objects

As per the documented foreign key relationships, AR_CREDIT_HISTORIES is integrally linked to the Trading Community Architecture (TCA) customer model. The table has defined foreign key dependencies on the following objects:

  • HZ_CUST_ACCOUNTS: Joined via the CUSTOMER_ID column. This relationship ties each credit history record to the master customer definition.
  • HZ_CUST_SITE_USES_ALL: Joined via the SITE_USE_ID column. This optional relationship links the credit history to a specific customer site (typically a bill-to site), allowing for credit profile tracking at both the customer and site levels.

The primary key constraint AR_CREDIT_HISTORIES_PK on CREDIT_HISTORY_ID ensures the integrity of each historical entry. This table is a likely source for standard Oracle Receivables credit history reports and may be referenced by various AR APIs and credit management forms.