Search Results hz_credit_usage_rule_sets_b




Overview
Explore in AI Chat

Overview

HZ_CREDIT_USAGE_RULE_SETS_B is a Receivables (AR) base table that stores the sets of credit usage rules within the Oracle E-Business Suite Trading Community Model. In Oracle EBS 12.1.1 and 12.2.2, this object defines the grouping construct under which individual credit usage rules are organized, allowing the credit management engine to determine how a customer's exposure is evaluated across different credit usage contexts such as orders, invoices, and commitments. The "_B" suffix denotes that the table holds base-language (non-translated) records, with translatable descriptive attributes managed in a companion "_TL" table.

The table resides in the AR schema and is documented as VALID in the ETRM data dictionary. Its primary key is defined by the constraint HZ_CREDIT_USAGE_RULE_SETS_B_PK, which is enforced over the single column CREDIT_USAGE_RULE_SET_ID. From a Data Vault modeling perspective, the mined foreign-key topology classifies this object as hub-leaning, suggesting it would typically be modeled as a hub because it establishes a durable, uniquely identified business entity (the credit usage rule set) whose identity is referenced by dependent links and satellites.

Key Information Stored

The table is documented with 27 columns. The most significant of these are summarized below.

  • CREDIT_USAGE_RULE_SET_ID — the surrogate primary key and the single column of unique index HZ_CREDIT_USAGE_RULE_SETS_B_U1, which serves as the business-key candidate. This identifier is reused as the foreign key throughout the related rule and translation tables.
  • GLOBAL_EXPOSURE_FLAG — indicates whether the rule set applies to global exposure calculations for the credit usage context.
  • CREATION_DATE, CREATED_BY — standard auditing columns recording when and by whom the rule set was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit trail columns capturing the most recent modification.
  • PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program and request context columns identifying the process that created or last updated the row, useful for batch lineage and troubleshooting.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (Descriptive Flexfield) column set enabling customer-specific extensibility without schema changes.

Common Use Cases and Queries

Credit analysts and implementers query this table to enumerate the rule sets governing how credit exposure is calculated for a customer or credit profile. A representative join retrieves the rules belonging to each set:

SELECT s.credit_usage_rule_set_id, r.credit_usage_rule_id
FROM hz_credit_usage_rule_sets_b s,
   hz_credit_usage_rules r
WHERE s.credit_usage_rule_set_id = r.credit_usage_rule_set_id;

To obtain the translatable name and description, join to the translation table on the same key:

SELECT b.credit_usage_rule_set_id, t.name, t.description
FROM hz_credit_usage_rule_sets_b b,
   hz_credit_usage_rule_sets_tl t
WHERE b.credit_usage_rule_set_id = t.credit_usage_rule_set_id
  AND t.language = USERENV('LANG');

Typical reporting scenarios include auditing which credit usage rule sets are linked to active credit usages, reviewing DFF attribute usage across rule sets, and tracing the REQUEST_ID to the concurrent program that last maintained a set. Because the table is hub-leaning, it is also a natural anchor for building conformed credit-usage dimensions in a warehouse.

Related Objects

The following objects reference or depend on HZ_CREDIT_USAGE_RULE_SETS_B through documented foreign-key relationships.

  • HZ_CREDIT_USAGES — references the rule set via CREDIT_USAGE_RULE_SET_ID, linking a credit usage entry to its governing rule set.
  • HZ_CREDIT_USAGE_RULES — references the rule set via CREDIT_USAGE_RULE_SET_ID, holding the individual rules belonging to each set.
  • HZ_CREDIT_USAGE_RULE_SETS_TL — references the rule set via CREDIT_USAGE_RULE_SET_ID, supplying language-specific name and description values.

Together these three dependent tables form the core of the credit usage rule configuration model, with HZ_CREDIT_USAGE_RULE_SETS_B acting as the central parent entity.