Search Results hz_credit_usages




Overview
Explore in AI Chat

Overview

The HZ_CREDIT_USAGES 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. It functions as a critical junction or association table within the Trading Community Architecture (TCA) framework. Its primary role is to establish and manage the relationship between a defined credit limit and a specific credit usage rule set. This association is fundamental to the system's credit management functionality, enabling the application of sophisticated business rules that govern how a customer's available credit is calculated and consumed across different transaction types and business contexts.

Key Information Stored

The table's structure is designed to link various credit profile amount entities to a rule set. While the full column list is not detailed in the provided metadata, the foreign key relationships explicitly identify its key columns. The primary key is CREDIT_USAGE_ID, which uniquely identifies each association record. The table contains several foreign key columns that point to the source of the credit limit and the governing rule set: CREDIT_PROFILE_AMT_ID (links to HZ_CREDIT_PROFILE_AMTS), CUST_ACCT_PROFILE_AMT_ID (links to HZ_CUST_PROFILE_AMTS), PROFILE_CLASS_AMOUNT_ID (links to HZ_CUST_PROF_CLASS_AMTS), and CREDIT_USAGE_RULE_SET_ID (links to HZ_CREDIT_USAGE_RULE_SETS_B). Each record effectively answers which rule set (CREDIT_USAGE_RULE_SET_ID) applies to a given credit limit defined at the account, profile, or profile class level.

Common Use Cases and Queries

This table is central to queries and processes that determine the active credit checking rules for a customer. A common use case is during order entry or invoice creation, where the system must identify the correct usage rules to validate an order against a customer's credit limit. For reporting, administrators may query this table to audit which rule sets are assigned to various customer tiers. A typical SQL pattern involves joining HZ_CREDIT_USAGES to the relevant profile amount table and the rule set table to get a complete picture.

SELECT cua.CREDIT_USAGE_ID,
       cpa.AMOUNT AS CREDIT_LIMIT,
       curs.NAME AS RULE_SET_NAME
FROM HZ_CREDIT_USAGES cua
JOIN HZ_CREDIT_PROFILE_AMTS cpa ON cua.CREDIT_PROFILE_AMT_ID = cpa.CREDIT_PROFILE_AMT_ID
JOIN HZ_CREDIT_USAGE_RULE_SETS_B curs ON cua.CREDIT_USAGE_RULE_SET_ID = curs.CREDIT_USAGE_RULE_SET_ID
WHERE cpa.CUST_ACCOUNT_ID = :cust_account_id;

Related Objects

The HZ_CREDIT_USAGES table sits at the intersection of several key TCA credit management tables, as documented by its foreign keys:

  • HZ_CREDIT_PROFILE_AMTS: Joined via HZ_CREDIT_USAGES.CREDIT_PROFILE_AMT_ID. This table holds credit limits defined for a specific customer account.
  • HZ_CUST_PROFILE_AMTS: Joined via HZ_CREDIT_USAGES.CUST_ACCT_PROFILE_AMT_ID. This table stores amounts, including credit limits, from a customer's assigned credit profile.
  • HZ_CUST_PROF_CLASS_AMTS: Joined via HZ_CREDIT_USAGES.PROFILE_CLASS_AMOUNT_ID. This table contains default amounts, including credit limits, defined for a customer profile class.
  • HZ_CREDIT_USAGE_RULE_SETS_B: Joined via HZ_CREDIT_USAGES.CREDIT_USAGE_RULE_SET_ID. This is the master table defining the sets of rules that control how credit is used (e.g., including or excluding specific transaction types).