Search Results validation_status_code




Overview
Explore in AI Chat

Overview

XLA_PROD_ACCT_HEADERS_FVL is a validation-rule view owned by the APPS schema in Oracle E-Business Suite Subledger Accounting (XLA). It presents denormalized, language-resolved header information describing the product accounting rules that govern how subledger transactions are accounted. The view is built over XLA_PROD_ACCT_HEADERS and joins to event class, event type, and lookup translations to expose readable names in place of internal codes. Its primary role is to support reporting, diagnostics, and integration queries that must determine whether accounting is required for a given application, entity, event class, and event type, and to expose the compilation or validation status of the associated product rule. Because it is a view rather than a table, it is read-only by design and inherits the row-level security and language settings of the underlying objects.

Underlying Base Objects

According to ETRM metadata for 12.2.2, the view is defined over four referenced objects: XLA_PROD_ACCT_HEADERS, XLA_EVENT_CLASSES_TL, XLA_EVENT_TYPES_TL, and XLA_LOOKUPS. The first three appear as synonyms resolving to the base tables, while XLA_LOOKUPS is itself a view over the FND lookup infrastructure. The join keys enforce a multi-tenant style match on APPLICATION_ID, ENTITY_CODE, and EVENT_CLASS_CODE across the header, event class, and event type translation tables. Both translation joins filter on USERENV('LANG') so that the returned EVENT_CLASS_NAME and EVENT_TYPE_NAME reflect the caller's session language. The lookup join is outer-joined, matching VALIDATION_STATUS_CODE to LOOKUP_CODE where LOOKUP_TYPE equals 'XLA_COMPILE_STATUS_TYPE'. This outer join means a row is still returned even when no lookup meaning exists, and the associated display column is then null.

Key Columns

Common Use Cases and Queries

The most frequent use case is locating product accounting rules whose validation or compilation status is not successful, particularly after rule changes or upgrades. A typical query filters by code or decoded meaning:

  • SELECT application_id, entity_code, event_class_code, event_type_code, validation_status_code, validation_status_dsp FROM apps.xla_prod_acct_headers_fvl WHERE validation_status_code = '&status';
  • SELECT * FROM apps.xla_prod_acct_headers_fvl WHERE validation_status_dsp = 'Invalid';
  • SELECT application_id, event_class_name, event_type_name, accounting_required_flag FROM apps.xla_prod_acct_headers_fvl WHERE accounting_required_flag = 'Y';

Because the view already resolves the language-dependent names and the lookup meaning, it is preferable to querying XLA_PROD_ACCT_HEADERS directly whenever readable output is required. Note that all access should be performed through the APPS schema or a synonym, and that results are constrained by the session language and any applicable security profiles.