Search Results compile_status_dsp

Overview

XLA_PRODUCT_RULES_FVL is an APPS-owned view within the Subledger Accounting (XLA) product of Oracle E-Business Suite, valid in both the 12.1.1 and 12.2.2 releases. It presents a denormalized, user-facing representation of subledger product rules — the configuration records that govern how transactions in a given subledger application are accounted for under a specific accounting method. The "FVL" suffix indicates a flex-field-style validation view, meaning the view joins translation, lookup, and descriptive flexfield sources so that code values are surfaced alongside their human-readable descriptions. Because product rules carry a compilation lifecycle (they must be compiled before they take effect), the view exposes the COMPILE_STATUS_CODE column prominently, along with its decoded meaning. This makes it the principal query target for implementers and support teams who need to audit which product rules exist, whether they are enabled, and whether each has been successfully compiled.

Underlying Base Objects

The view is defined over five documented base objects. The primary data source is XLA_PRODUCT_RULES_B, the base table holding the rule definitions keyed by application, accounting method context, rule type, and rule code. XLA_PRODUCT_RULES_TL supplies the translated NAME and DESCRIPTION columns, joined on the same composite key with the language filtered by USERENV('LANG'). XLA_APPLICATIONS_XVL contributes the APPLICATION_NAME, resolving APPLICATION_ID to a readable subledger application label. XLA_LOOKUPS appears twice: aliased L1 to decode PRODUCT_RULE_TYPE_CODE against the XLA_OWNER_TYPE lookup type, and aliased L2 to decode COMPILE_STATUS_CODE against XLA_COMPILE_STATUS_TYPE. Finally, FND_ID_FLEX_STRUCTURES_V is joined twice (aliases F1 and F2) on an outer-join basis to resolve TRANSACTION_COA_ID and ACCOUNTING_COA_ID into chart-of-accounts structure names, restricted to the GL# flexfield code and application 101. The joins to the flexfield structures are outer joins, so rules without an assigned COA still appear.

Key Columns

• APPLICATION_ID / APPLICATION_NAME — Identifies the subledger application (for example Payables or Receivables) that owns the rule.
• AMB_CONTEXT_CODE — The accounting method context that scopes the rule.
• PRODUCT_RULE_TYPE_CODE / PRODUCT_RULE_TYPE_DSP — The rule classification code and its decoded meaning.
• PRODUCT_RULE_CODE — The unique identifier of the rule.
• NAME / DESCRIPTION — Translated, user-facing labels from the _TL table.
• TRANSACTION_COA_ID / TRANSACTION_COA_NAME — The chart of accounts used for transaction data.
• ACCOUNTING_COA_ID / ACCOUNTING_COA_NAME — The chart of accounts used for accounting entries.
• PRODUCT_RULE_VERSION — Version indicator for the rule definition.
• COMPILE_STATUS_CODE / COMPILE_STATUS_DSP — The compilation state of the rule and its decoded description; this is the column most frequently queried.
• PRODUCT_RULE_HASH_ID — Hash reference used by the compilation process to detect changes.
• ENABLED_FLAG — Indicates whether the rule is active.
• REQUEST_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit and concurrent-request tracking columns.

Common Use Cases and Queries

The most frequent use case is determining compile status across all product rules, typically after a patch or setup change reveals that accounting is not being generated. A basic audit query follows:

• SELECT application_name, product_rule_code, name, compile_status_dsp, enabled_flag FROM xla_product_rules_fvl ORDER BY application_name, product_rule_code;
• SELECT * FROM xla_product_rules_fvl WHERE compile_status_code <> 'C'; — identify rules that are not fully compiled (the status lookup value for "compiled" varies by release).
• SELECT name, compile_status_dsp FROM xla_product_rules_fvl WHERE application_id = 200 AND enabled_flag = 'Y'; — list active, uncompiled rules for a specific subledger.
• SELECT product_rule_code, transaction_coa_name, accounting_coa_name FROM xla_product_rules_fvl WHERE transaction_coa_name IS NULL OR accounting_coa_name IS NULL; — detect rules missing a chart-of-accounts assignment, using the outer-joined COA columns.

Because the view resolves codes to descriptions and COA identifiers to structure names, it is well suited to diagnostic reports, Fast Formula lookups, and integration extracts where readable values are required without additional decoding logic.