Search Results hz_credit_usage_rule_sets_vl




Overview
Explore in AI Chat

Overview

The HZ_CREDIT_USAGE_RULE_SETS_VL view is a multilingual (VL) reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Receivables (AR) product family. It exposes credit usage rule set definitions that govern how Oracle Advanced Collections, Credit Management, and Receivables evaluate a customer's exposure against established credit limits. A credit usage rule set designates which transaction sources — such as open receivables, unapplied cash, on-account credits, or external exposure feeds — are aggregated to determine the amount of credit currently in use for a given customer or account.

Because the object is a VL view, it joins the translation table HZ_CREDIT_USAGE_RULE_SETS_TL to the base table HZ_CREDIT_USAGE_RULE_SETS_B and filters the translated name by the session language. This design is consistent with the Oracle EBS multilingual architecture: non-translatable attributes reside in the _B table, while language-dependent descriptive columns reside in the _TL table. Consequently, the view presents a single, fully attributed record per rule set (in the user's language) rather than one row per installed language.

As with other HZ (Trading Community Architecture) views, HZ_CREDIT_USAGE_RULE_SETS_VL serves as the supported read interface for concurrent programs, OBIEE/BI Publisher reports, custom forms, and integration extracts that must reference credit usage rule sets without directly joining the underlying tables.

Underlying Base Objects

The view definition references two objects via public synonyms:

  • HZ_CREDIT_USAGE_RULE_SETS_B — the base table holding the non-translatable columns of each rule set, aliased as B in the view text.
  • HZ_CREDIT_USAGE_RULE_SETS_TL — the translation table holding the language-specific NAME, aliased as T.

The join predicate is B.CREDIT_USAGE_RULE_SET_ID = T.CREDIT_USAGE_RULE_SET_ID AND T.LANGUAGE = USERENV('LANG'). The USERENV('LANG') call returns the language code of the current session, ensuring that only the row corresponding to the user's active language is returned. If no _TL row exists for that language, the rule set will not appear in the view — a common cause of "missing rows" in custom queries.

Key Columns

  • ROW_ID — the ROWID of the underlying base table row; useful for row-level identification and updates.
  • CREDIT_USAGE_RULE_SET_ID — the primary key of the rule set; the primary join and lookup key.
  • NAME — the translated, user-facing name of the rule set (from _TL).
  • GLOBAL_EXPOSURE_FLAG — indicates whether the rule set applies globally to exposure calculations across all operating units, versus being scoped to specific organizations.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard "Who" audit columns.
  • PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program context columns used to trace the request that created or last modified the row.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns, allowing customer-defined attributes to be captured against each rule set.

Common Use Cases and Queries

Typical usage includes looking up a rule set ID by name, listing all active rule sets for a configuration report, and joining the view to assignment tables linking rule sets to credit profiles or customer accounts.

Sample query — retrieve all rule sets with their names and global flag:

  • SELECT credit_usage_rule_set_id, name, global_exposure_flag FROM hz_credit_usage_rule_sets_vl ORDER BY name;

Sample query — resolve a rule set ID from a known name (useful in TCA integration scripts):

  • SELECT credit_usage_rule_set_id FROM hz_credit_usage_rule_sets_vl WHERE name = :rule_set_name;

Because the view already applies the session-language filter, no additional LANGUAGE predicate is required. When constructing joins to profile assignment or exposure tables, join on CREDIT_USAGE_RULE_SET_ID to maintain cardinality. For bulk extracts, add the standard audit columns to enable incremental refresh logic. Report developers should remember that a missing translation row suppresses the rule set entirely, so a UNION with the base table may occasionally be necessary for completeness in diagnostic queries.