Search Results hz_credit_usage_rules_u1

Overview

The HZ_CREDIT_USAGE_RULES table, owned by the AR schema and registered under FND Design Data as AR.HZ_CREDIT_USAGE_RULES, stores the configuration that governs how transactions denominated in different currencies are grouped — either individually or into a single consolidated currency group — for the purposes of computing a total credit limit and the corresponding current credit exposure. In Oracle EBS 12.1.1 and 12.2.2, this table is central to cross-currency credit management within Oracle Receivables and the broader Trade Management / credit checking framework.

Each rule row is assigned to a credit limit, meaning that credit exposure calculation logic is parameterized per limit rather than being globally fixed. This allows an organization to define, for example, that exposures in EUR, GBP, and CHF are aggregated and evaluated against a single limit expressed in USD, while other currencies are handled independently. The table is classified as VALID and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.

From a heuristic Data Vault modeling perspective, the mined FK structure suggests this object is satellite-leaning: it holds descriptive, versioned attributes (flags, currency groupings) keyed to a parent entity rather than acting as an independent business hub or a pure association link. The single documented foreign key to HZ_CREDIT_USAGE_RULE_SETS_B reinforces this characterization, positioning HZ_CREDIT_USAGE_RULES as a dependent detail table beneath the rule-set parent.

Key Information Stored

The table carries 31 documented columns in the 12.2.2 physical schema. The most operationally significant are:

• CREDIT_USAGE_RULE_ID — NUMBER(15), the surrogate primary key and the column backing the unique index HZ_CREDIT_USAGE_RULES_U1. This is the documented business-key candidate for unique identification.
• CREDIT_USAGE_RULE_SET_ID — NUMBER(15), foreign key to HZ_CREDIT_USAGE_RULE_SETS_B, linking each rule to its parent rule set. Indexed by HZ_CREDIT_USAGE_RULES_N2.
• USAGE_TYPE — VARCHAR2(30), references AR_LOOKUPS; defines the category of credit usage the rule applies to. Indexed by HZ_CREDIT_USAGE_RULES_N1 together with USER_CODE.
• USER_CODE — VARCHAR2(150), holds currency codes that participate in the rule.
• EXCLUDE_FLAG — VARCHAR2, Y/N indicator of whether any currencies are excluded; defaults to N.
• INCLUDE_ALL_FLAG — VARCHAR2, Y/N indicator of whether all currencies are included; defaults to N.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus the concurrent-program columns PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF/descriptive flexfield columns reserved for customer-specific extensions.

The interplay of INCLUDE_ALL_FLAG and EXCLUDE_FLAG is what enables flexible cross-currency exposure logic: a rule may include all currencies by default and explicitly exclude selected ones, or include only the currencies named in USER_CODE.

Common Use Cases and Queries

Typical scenarios include auditing which currencies roll into a given credit limit, verifying that exposure aggregation is configured as expected after a setup change, and reporting rule coverage per customer or limit.

Retrieve all rules belonging to a rule set:

• SELECT credit_usage_rule_id, usage_type, user_code, exclude_flag, include_all_flag FROM hz_credit_usage_rules WHERE credit_usage_rule_set_id = :p_rule_set_id;

Find rules that include all currencies but exclude specific ones:

• SELECT * FROM hz_credit_usage_rules WHERE include_all_flag = 'Y' AND exclude_flag = 'Y';

Lookup-driven reporting on usage type (join to AR_LOOKUPS):

• SELECT r.credit_usage_rule_id, l.meaning FROM hz_credit_usage_rules r, ar_lookups l WHERE r.usage_type = l.lookup_code AND l.lookup_type = :usage_lookup_type;

Because USER_CODE holds currency codes, joining to FND_CURRENCIES validates that configured codes correspond to enabled currencies. Indexes N1 (USAGE_TYPE, USER_CODE) and N2 (CREDIT_USAGE_RULE_SET_ID) should drive predicate design for performance.

Related Objects

• HZ_CREDIT_USAGE_RULE_SETS_B — parent entity; join on CREDIT_USAGE_RULE_SET_ID.
• HZ_CREDIT_USAGE_RULE_SETS_TL — translated rule-set names for reporting.
• AR_LOOKUPS — lookup source for USAGE_TYPE.
• FND_CURRENCIES — validates currency codes held in USER_CODE.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY to user names.
• HZ_CUSTOMER_PROFILES / credit limit entities — the limits to which these rules are ultimately assigned.