Results for “xla_line_definitions_f_v”

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

Overview

XLA_LINE_DEFINITIONS_F_V is an APPS-owned, VALID view in the Oracle E-Business Suite Subledger Accounting (XLA) product module. It presents a language-resolved, denormalized read-only image of the line definition setup owned by XLA. A line definition determines how Subledger Accounting builds the individual journal entry lines applied to an accounting event, and this view joins the definition's base and translated records with the descriptive names of the owning application, event class, event type, flexfield structures, and lookup meanings.

The view is the primary reporting and integration surface for line definition metadata. Because it exposes both the coded values (for example VALIDATION_STATUS_CODE, LINE_DEFINITION_OWNER_CODE, BUDGETARY_CONTROL_FLAG) and their translated meanings (VALIDATION_STATUS, LINE_DEFINITION_OWNER), it is suitable for setup reports, migration and comparison scripts across environments, and downstream integrations that need to identify which line definitions participate in budgetary control. Users and implementers frequently query this view when investigating the budgetary_control_flag, since that attribute is surfaced here in the context of the full line definition setup rather than on the underlying base table alone.

Underlying Base Objects

The view is defined over seven documented base objects, combining base and translation tables with lookup and flexfield views:

• XLA_LINE_DEFINITIONS_B (synonym) — the base table holding the header-level line definition attributes; the view's driving table, aliased XLAB.
• XLA_LINE_DEFINITIONS_TL (synonym) — the translated table supplying the language-specific NAME and DESCRIPTION, aliased XLAT.
• XLA_EVENT_CLASSES_TL (synonym) — provides the translated EVENT_CLASS_NAME.
• XLA_EVENT_TYPES_TL (synonym) — provides the translated EVENT_TYPE_NAME.
• FND_APPLICATION_TL (synonym) — supplies the application name for the owning application.
• FND_ID_FLEX_STRUCTURES_V (view) — joined twice to resolve the transaction and accounting chart of accounts flexfield structure names.
• XLA_LOOKUPS (view) — joined twice to translate XLA_OWNER_TYPE and XLA_COMPILE_STATUS_TYPE lookup codes into meanings.

Translation joins consistently filter on USERENV('LANG'), so the view returns exactly one row per line definition for the session language.

Key Columns

• ROW_ID — the ROWID of the underlying base-table row, useful for direct row identification.
• AMB_CONTEXT_CODE, APPLICATION_ID, APPLICATION_NAME — the owning application context.
• ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE with EVENT_CLASS_NAME and EVENT_TYPE_NAME — the subledger event context the definition applies to.
• LINE_DEFINITION_CODE, LINE_DEFINITION_NAME, DESCRIPTION — the definition's identifier and translated text.
• LINE_DEFINITION_OWNER_CODE / LINE_DEFINITION_OWNER — the owner classification (via XLA_OWNER_TYPE).
• VALIDATION_STATUS_CODE / VALIDATION_STATUS — compile/validation state (via XLA_COMPILE_STATUS_TYPE).
• ENABLED_FLAG — whether the definition is active.
• TRANSACTION_COA_ID / TRANSACTION_COA_NAME and ACCOUNTING_COA_ID / ACCOUNTING_COA_NAME — the chart of accounts structures used for transaction and accounting flexfields.
• BUDGETARY_CONTROL_FLAG — indicates whether budgetary control is applied for this line definition; a key search target.
• OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include auditing enabled line definitions per event type, identifying definitions configured for budgetary control, and comparing setup between instances. The pattern below lists all definitions with budgetary control enabled, resolved to names.

• Find budgetary-control line definitions:
  SELECT line_definition_code, line_definition_name, application_name, event_class_name, event_type_name, validation_status
FROM apps.xla_line_definitions_f_v
WHERE budgetary_control_flag = 'Y'
AND enabled_flag = 'Y';
• Audit definitions by owner and validation status, joining to XLA_EVENT_CLASSES_TL names already supplied by the view.
• Compare line definition setups across development, test, and production by extracting LINE_DEFINITION_CODE, TRANSACTION_COA_NAME, ACCOUNTING_COA_NAME, and BUDGETARY_CONTROL_FLAG.

Method values pass through the view's underlying lookup joins, so budgetary_control_flag should be filtered using the stored coded value ('Y' for enabled, 'N' otherwise) to ensure reliable results.