Search Results xla_compile_status_type




Overview
Explore in AI Chat

Overview

The view APPS.XLA_PROD_ACCT_HEADERS_FVL is a foreign-key/validation (FVL) view defined in the Oracle E-Business Suite (EBS) Subledger Accounting (XLA) module. It presents a denormalized, user-friendly projection of the XLA_PROD_ACCT_HEADERS table, joining it to translation and lookup objects so that descriptive names and display meanings are readily available for reporting and integration. In this view the internal codes that drive accounting rule definition — entity, event class, event type, product rule — are surfaced alongside the translatable class and type names and the display meaning of the validation status code.

The view is particularly relevant to users searching for xla_compile_status_type. The join to XLA_LOOKUPS uses lookup_type = 'XLA_COMPILE_STATUS_TYPE', so the VALIDATION_STATUS_DSP column resolves the VALIDATION_STATUS_CODE stored on the header into its human-readable meaning. This is the same lookup category that drives the compile/validation status indicators used elsewhere in Subledger Accounting, making the view a convenient source for determining whether a given product accounting definition set is valid, invalid, or has not yet been compiled.

Underlying Base Objects

According to the documented metadata, the view is defined over four referenced base objects, all in the APPS schema:

  • XLA_PROD_ACCT_HEADERS (SYNONYM) — the primary table supplying the header rows and the majority of columns, aliased PAH.
  • XLA_EVENT_CLASSES_TL (SYNONYM) — the translation table supplying event_class_name, aliased ECL.
  • XLA_EVENT_TYPES_TL (SYNONYM) — the translation table supplying event_type_name, aliased ETL.
  • XLA_LOOKUPS (VIEW) — the lookup view supplying validation_status_dsp, aliased XLK.

Joins to XLA_EVENT_CLASSES_TL and XLA_EVENT_TYPES_TL are performed on the composite key of application_id, entity_code, event_class_code, and (for event types) event_type_code, with a language restriction of USERENV('LANG'). The lookup join is an outer join ((+)) on validation_status_code with lookup_type = 'XLA_COMPILE_STATUS_TYPE', so headers are retained even when no matching meaning exists.

Key Columns

  • row_id — the ROWID of the underlying header row, useful for direct-row addressing.
  • application_id — the application owning the accounting definition.
  • amb_context_code — the Application Accounting Definition (product) context.
  • product_rule_code / product_rule_type_code — the product rule and its type that the header belongs to.
  • entity_code / event_class_code / event_type_code — the entity and event identifiers that scope the accounting definition.
  • event_class_name / event_type_name — translated descriptive names for the class and type.
  • accounting_required_flag — indicates whether accounting entries are required for the associated event.
  • locking_status_flag — indicates the locking state of the definition set.
  • validation_status_code / validation_status_dsp — the raw compile/validation status code and its decoded meaning from XLA_COMPILE_STATUS_TYPE.
  • creation_date, created_by, last_update_date, last_updated_by, last_update_login — standard audit columns.

Common Use Cases and Queries

The view is typically queried to report the compile/validation state of product accounting definitions with readable names rather than raw codes.

  • Listing header definitions with decoded validation status:

SELECT application_id, entity_code, event_class_name, event_type_name, validation_status_code, validation_status_dsp FROM apps.xla_prod_acct_headers_fvl ORDER BY application_id, entity_code;

  • Isolating definitions that are not yet valid or compiled:

SELECT entity_code, event_class_name, event_type_name, validation_status_dsp FROM apps.xla_prod_acct_headers_fvl WHERE validation_status_code <> 'VALID';

  • Joining to related product rule detail by application_id, entity_code, and event_class_code for detailed diagnostics.

Because it exposes both codes and translated meanings, the view is well suited to diagnostic queries, custom reports, and integration extracts requiring human-readable subledger accounting definition status.