Search Results hz_credit_usage_rule_sets_tl




Overview
Explore in AI Chat

Overview

The HZ_CREDIT_USAGE_RULE_SETS_TL table is a translation table within the Oracle Receivables (AR) schema that stores the multilingual, language-specific definitions of credit usage rule sets. It is the child translation table of the base table HZ_CREDIT_USAGE_RULE_SETS_B, and together these two tables implement the standard Oracle EBS "TL/Base" multilingual pattern. In Oracle E-Business Suite 12.1.1 and 12.2.2, credit usage rule sets determine how a customer's credit exposure is calculated — for example, which transaction types, order types, or adjustments count toward open credit balances.

From a Data Vault modeling perspective, the ETRM metadata heuristically classifies this object as satellite-leaning. This is appropriate: the table carries descriptive attributes (the translated NAME) keyed by the natural identifier and language, dependent on the parent base table. A satellite classification suggests the row depends on a hub (here, the rule set identity) and is descriptive rather than a standalone entity.

Key Information Stored

The table contains nine documented columns. The most significant are:

  • CREDIT_USAGE_RULE_SET_ID — Surrogate identifier for the credit usage rule set, part of the composite primary key and the foreign key to the base table.
  • LANGUAGE — The language code in which the translated value is stored, the second component of the primary key.
  • SOURCE_LANG — The source language of the original record, indicating the language from which the translation originated.
  • NAME — The user-facing, translated name of the credit usage rule set.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the row was inserted.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking the most recent modification and originating login.

The surrogate primary key is HZ_CREDIT_USAGE_RULE_SETS_TL_P on (CREDIT_USAGE_RULE_SET_ID, LANGUAGE). A unique index, HZ_CREDIT_USAGE_RS_TL_U1, on the same column pair, reinforces the business-key candidate that no rule set may have more than one translated name per language. Notably, the table contains no translated description column — only NAME is translated.

Common Use Cases and Queries

Reporting on rule set names typically joins this translation table to its base table and filters by the active language. A common pattern retrieves the translated name for a specific rule set:

  • Bilingual reporting: SELECT b.credit_usage_rule_set_id, t.name, t.language 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 = 'US';
  • Translation gap analysis: Identify rule sets lacking a row for a required language to detect incomplete translations.
  • Audit reporting: Use LAST_UPDATE_DATE and LAST_UPDATED_BY to trace when names were changed and by which user.
  • Multi-language dashboards: Join to FND_LANGUAGES to map LANGUAGE codes to descriptive language names.

Related Objects

  • HZ_CREDIT_USAGE_RULE_SETS_B — The base table; join on CREDIT_USAGE_RULE_SET_ID. This is the documented foreign-key relationship.
  • HZ_CREDIT_USAGE_RULES — The individual rules belonging to rule sets defined in the base and translation tables.
  • HZ_CUSTOMER_PROFILES — References credit usage rule sets to determine customer credit exposure.
  • HZ_CUST_PROFILE_AMTS — Credit profile amounts that consume the rule set logic.
  • FND_LANGUAGES — Maps LANGUAGE codes to installable language names.
  • FND_TERRITORIES / FND_LANGUAGE_TL — Provide the language context used throughout the multilingual join strategy.

Because the table is populated and maintained primarily through the Receivables setup user interface and concurrent translation programs rather than directly, direct DML should be avoided in favor of the supported Credit Management configuration screens.