Results for “xla_product_rules_vl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XLA_PRODUCT_RULES_VL is a seeded, VALID view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the XLA (Subledger Accounting) product and exposes multilingual (MLS) product rule definitions maintained by the Subledger Accounting engine. The view presents a translated, language-aware projection of the underlying product rule data by joining the base table XLA_PRODUCT_RULES_B with the translation table XLA_PRODUCT_RULES_TL and filtering translation rows to the session language via USERENV('LANG'). Because the view joins both the base and translation layers, consumers gain access to the descriptive fields NAME and DESCRIPTION alongside the operational attributes of each product rule without having to write the join or language filter themselves. In reporting and integration contexts, this view is the standard read interface for presenting product rule codes and their user-facing names consistently across the Subledger Accounting application. It is not a transactional or journal-entry view; it is a definitional view over application accounting configuration.

Underlying Base Objects

The documented metadata identifies exactly two referenced base objects, both accessed through synonyms in APPS:

• XLA_PRODUCT_RULES_B — the base (non-translated) table holding the primary product rule attributes, including identification keys, flags, audit columns, and program-related metadata. It supplies all columns aliased as B.* in the view definition.
• XLA_PRODUCT_RULES_TL — the translation table holding the language-specific NAME and DESCRIPTION fields. It is aliased as T.

The join condition between the two tables is a composite key spanning APPLICATION_ID, AMB_CONTEXT_CODE, PRODUCT_RULE_TYPE_CODE, and PRODUCT_RULE_CODE. Consistency of the AMB_CONTEXT_CODE (accounting methods builder context) indicates that product rules are scoped to an accounting context, and that translations are maintained per that same scope. The view additionally projects B.ROWID as ROW_ID.

Key Columns

• ROW_ID — the ROWID of the underlying base row, useful as a surrogate identifier.
• PRODUCT_RULE_CODE / PRODUCT_RULE_TYPE_CODE — the identifying code and classification of the product rule.
• APPLICATION_ID — the owning application, forming part of the composite join key.
• AMB_CONTEXT_CODE — the accounting methods builder context in which the rule is defined.
• TRANSACTION_COA_ID / ACCOUNTING_COA_ID — chart of accounts references associated with transaction and accounting side processing.
• PRODUCT_RULE_VERSION / PRODUCT_RULE_HASH_ID — version and hash identifiers used to detect and track definitional changes.
• COMPILE_STATUS_CODE, LOCKING_STATUS_FLAG, UPDATED_FLAG, VERSION_NUM — lifecycle and concurrency state indicators maintained by the Subledger Accounting configuration infrastructure.
• ENABLED_FLAG — whether the rule is active.
• NAME / DESCRIPTION — translated descriptive attributes drawn from XLA_PRODUCT_RULES_TL.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage covers configuration review, migration verification, and integration extracts. A common pattern is to enumerate enabled product rules for a given application and accounting context. The LANGUAGE predicate is embedded in the view, so callers need not repeat it.

SELECT product_rule_code,
       product_rule_type_code,
       name,
       description,
       enabled_flag,
       compile_status_code
  FROM xla_product_rules_vl
 WHERE application_id = 101
   AND amb_context_code = 'DEFAULT'
   AND enabled_flag = 'Y';

Because translations are resolved automatically, the view is well suited for user-facing reports and LOVs where descriptive names are required. It is equally useful for change detection during upgrades or patch analysis, using the version and hash columns:

SELECT product_rule_code,
       product_rule_version,
       product_rule_hash_id,
       last_update_date,
       last_updated_by
  FROM xla_product_rules_vl
 ORDER BY application_id, product_rule_code;

Extracts for data migration or reconciliation typically project the identifying columns along with TRANSACTION_COA_ID and ACCOUNTING_COA_ID. As with any MLS view, results depend on the session language, so integrations should set the language environment explicitly before querying.