Search Results hz_credit_usage_rules




Overview
Explore in AI Chat

Overview

HZ_CREDIT_USAGE_RULES is a Receivables (AR) module table within the Oracle E-Business Suite schema, owned by the AR user. It stores the individual usage rules that are assigned to a credit limit configuration. In the Oracle Advanced Collections and Credit Management (ETRM) data model, credit checking behavior is driven by rule sets, which in turn are composed of one or more granular usage rules. This table holds those granular rule definitions and links each rule to its parent rule set through the CREDIT_USAGE_RULE_SET_ID foreign key.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as satellite-leaning. This reflects its role as a descriptive, attribute-carrying structure that hangs off a parent entity (the credit usage rule set), rather than serving as a central hub or a pure association link. In practice, HZ_CREDIT_USAGE_RULES functions as the detail-level component of the credit usage rule set hierarchy, capturing the conditions and inclusion or exclusion logic that determines how credit limits are consumed during transaction processing.

Key Information Stored

The table contains 31 documented columns in the 12.2.2 physical schema. The most significant include:

No business-key candidate beyond the surrogate primary key is documented; the unique index U1 is defined on CREDIT_USAGE_RULE_ID itself.

Common Use Cases and Queries

This table is most commonly queried when diagnosing credit limit behavior, auditing rule configurations, or building custom credit management reports. A typical query joining rules to their parent rule sets resembles:

  • SELECT r.CREDIT_USAGE_RULE_ID, r.USAGE_TYPE, r.EXCLUDE_FLAG, r.INCLUDE_ALL_FLAG FROM HZ_CREDIT_USAGE_RULES r WHERE r.CREDIT_USAGE_RULE_SET_ID = :rule_set_id;
  • A reporting query lists all rules for a given usage type across rule sets: SELECT * FROM HZ_CREDIT_USAGE_RULES WHERE USAGE_TYPE = :usage_type;
  • An audit query flags recently modified rules using LAST_UPDATE_DATE to support change tracking and compliance review.

These patterns support troubleshooting why a specific transaction is or is not subject to credit checking, verifying that rule sets are configured with the intended include and exclude behavior, and generating configuration documentation for implementation teams.

Related Objects

The most significant related objects, based on the documented foreign key and primary key relationships, include:

  • HZ_CREDIT_USAGE_RULE_SETS_B — the parent table. Joined on HZ_CREDIT_USAGE_RULES.CREDIT_USAGE_RULE_SET_ID = HZ_CREDIT_USAGE_RULE_SETS_B.CREDIT_USAGE_RULE_SET_ID. This is the only documented foreign key relationship for this table.
  • HZ_CREDIT_USAGE_RULE_SETS_TL — the translation table for rule set names and descriptions, joined for multilingual reporting.
  • HZ_CUSTOMER_PROFILES and associated credit profile tables — reference rule sets indirectly through credit limit configurations.
  • HZ_CREDIT_USAGE_RULES_PK — the primary key constraint object used to enforce uniqueness on CREDIT_USAGE_RULE_ID.
  • AR APIs and concurrent programs that read rule configurations during credit checking, referencing records through the rule set hierarchy.

Because HZ_CREDIT_USAGE_RULES is a satellite-leaning detail table, its dependents are primarily upstream rule set and credit profile objects that consume its configuration during transaction credit evaluation.