Search Results xla_acct_line_types_vl




Overview
Explore in AI Chat

Overview

XLA_ACCT_LINE_TYPES_VL is a seeded, VALID view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the XLA (Subledger Accounting) product and exposes the definition of accounting line types used by the Subledger Accounting engine to transform subledger transactions into journal entries. Each row describes a configurable accounting line type associated with a specific application, accounting method (AMB context), entity, event class, and accounting line. The "_VL" suffix denotes a "view with translation" pattern: the view joins the base table to its translation table and filters the language by USERENV('LANG'), returning the descriptive Name and Description in the session's current language. Because it centralizes the metadata that drives journal line creation, the view is a primary reference for diagnostics, reporting, and integration development around subledger accounting configuration.

Underlying Base Objects

The view is defined over two documented base objects, referenced in the ETRM metadata as synonyms: XLA_ACCT_LINE_TYPES_B (the base/definition table) and XLA_ACCT_LINE_TYPES_TL (the translation table). The join is performed on the full composite key — APPLICATION_ID, AMB_CONTEXT_CODE, ENTITY_CODE, EVENT_CLASS_CODE, ACCOUNTING_LINE_TYPE_CODE, and ACCOUNTING_LINE_CODE — with the additional predicate T.LANGUAGE = USERENV('LANG') restricting translated text to the current session language. All functional/configuration columns are sourced from the B table (aliased B), while NAME and DESCRIPTION come from the TL table (aliased T). The view is read-only; DML against line type definitions must target the underlying tables or use the Subledger Accounting configuration pages in the Accounting Methods Builder.

Key Columns

  • ROW_ID — the ROWID of the base table row, useful for addressing the underlying record.
  • AMB_CONTEXT_CODE — identifies the Accounting Methods Builder context (application-level configuration context).
  • APPLICATION_ID — the subledger application that owns the line type (e.g., Payables, Receivables, Assets).
  • ENTITY_CODE / EVENT_CLASS_CODE — the transaction entity and event class for which the line type applies.
  • ACCOUNTING_LINE_TYPE_CODE / ACCOUNTING_LINE_CODE — the line type and line identifiers within the accounting method.
  • TRANSACTION_COA_ID — chart of accounts associated with the transaction definition.
  • ACCOUNTING_ENTRY_TYPE_CODE / ACCOUNTING_CLASS_CODE — classify the resulting journal entry (e.g., accrual, cash, charge).
  • NATURAL_SIDE_CODE — the natural debit/credit side of the generated line.
  • GL_TRANSFER_MODE_CODE / SWITCH_SIDE_FLAG / MERGE_DUPLICATE_CODE — control how lines are transferred to and summarized in General Ledger.
  • ENABLED_FLAG — indicates whether the line type is active.
  • NAME / DESCRIPTION — translated, user-facing text from the TL table.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is commonly queried to audit accounting method configuration, confirm which line types are enabled for an application, and support reconciliation or interface development. A typical retrieval of enabled line types for a given application is:

SELECT application_id, event_class_code, accounting_line_type_code, accounting_line_code, natural_side_code, name FROM apps.xla_acct_line_types_vl WHERE enabled_flag = 'Y' AND application_id = :p_app_id ORDER BY event_class_code, accounting_line_type_code;

Because the translation predicate is bound to USERENV('LANG'), NAME and DESCRIPTION are automatically returned in the session language, so no explicit language filter is needed. In Release 12.2.2 the view remains unchanged against its 12.1.1 definition, and the same query patterns apply. Note that this view describes configuration only; it does not contain posted subledger journal lines, which reside in the XLA_AE_LINES and XLA_DISTRIBUTION_LINKS structures.