Search Results hz_credit_usage_rules

Overview

The HZ_CREDIT_USAGE_RULES 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 serves as the transactional repository for the individual usage rules that are assigned to a customer's credit limit. The table's primary role is to define and enforce the specific conditions and criteria under which a credit limit can be applied, such as restricting usage to particular transaction types, currencies, or operating units. By storing these granular rules separately from the limit definition itself, the system enables flexible and complex credit management policies, allowing a single credit limit to be governed by multiple, distinct usage conditions.

Key Information Stored

The table stores the linkage between a credit usage rule and its parent rule set, along with the specific rule attributes. The most critical columns include CREDIT_USAGE_RULE_ID, which is the unique primary key identifier for each rule record. The CREDIT_USAGE_RULE_SET_ID is a mandatory foreign key column that ties each individual rule back to its parent definition in the HZ_CREDIT_USAGE_RULE_SETS_B table. While the provided metadata does not list all attribute columns, typical rule data stored would encompass fields to define the rule's applicability, such as transaction type, currency code, operating unit identifier, and rule precedence or activation status.

Common Use Cases and Queries

A primary use case is analyzing the complete set of restrictions placed on a specific credit limit for auditing or troubleshooting purposes. For instance, a credit analyst may need to understand why a particular transaction is being blocked from consuming a customer's available credit. A common reporting query involves joining this table to the credit limit and rule set tables to list all active rules. A sample SQL pattern to retrieve rule details for a specific rule set would be: SELECT * FROM HZ_CREDIT_USAGE_RULES WHERE CREDIT_USAGE_RULE_SET_ID = <rule_set_id> ORDER BY CREDIT_USAGE_RULE_ID;. This data is also critical during the order-to-cash cycle, where the Oracle Trading Community Architecture (TCA) and Receivables modules evaluate transaction eligibility against these stored rules before approving credit.

Related Objects

The table maintains a direct and essential foreign key relationship with the HZ_CREDIT_USAGE_RULE_SETS_B table, which is the header table for grouping usage rules. The join is performed on the column HZ_CREDIT_USAGE_RULES.CREDIT_USAGE_RULE_SET_ID. This structure indicates that a single rule set defined in HZ_CREDIT_USAGE_RULE_SETS_B can contain multiple individual rules stored in HZ_CREDIT_USAGE_RULES. This table is, in turn, referenced by the credit limit assignment objects within the TCA schema, ultimately linking the rules to a specific customer site's credit limit. The primary key constraint HZ_CREDIT_USAGE_RULES_PK on CREDIT_USAGE_RULE_ID ensures the integrity of each rule record.