Search Results reference_6




Overview

AX_SLE_LINES_V is a database view within the Oracle E-Business Suite Global Accounting Engine (AX) module. It exposes the entry line detail associated with Subledger Accounting (SLA) event processing, presenting journal entry lines in a denormalized form suitable for reporting and reconciliation. The view is defined primarily over the AX_SLE_LINES table (aliased L) and joins to additional header and supplier-related objects to enrich each line with application context, third-party, and site-level attributes.

In the context of Oracle EBS 12.1.1 and 12.2.2, this view serves as a read-only reference for the Global Accounting Engine's accounting line data. Because it consolidates posting status, accounted and entered amounts, account code combinations, and a large set of reference flexfields, it is well suited to audit, reconciliation, and downstream integration reporting where detailed journal line context is required. As documented in the ETRM metadata, the view is described simply as "Entry lines," and it is not implemented as a physical object in the source database — it is a view definition only.

Underlying Base Objects

The view text demonstrates that AX_SLE_LINES_V is defined over the following objects and aliases:

  • AX_SLE_LINES (L) — the principal source, contributing all line-level columns including journal sequence, accounting amounts, references, posting flags, and currency information.
  • AX_SLE_HEADERS (H) — joined to supply header context, notably the APPLICATION_ID that identifies the originating application.
  • Supplier/Vendor tables (V and VS) — used to resolve THIRD_PARTY_NAME from VENDOR_NAME and SUB_NAME from VENDOR_SITE_CODE.

Per the ETRM metadata, no referenced base objects are individually documented for this view, and the view is listed as "Not implemented in this database." The relationships above are inferred directly from the SELECT statement rather than from separately documented foreign keys.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling subledger entries to GL, auditing unposted lines, and exporting line-level detail with supplier context.

  • Review lines awaiting GL transfer:
    SELECT SLE_HEADER_ID, SLE_LINE_NUM, ACCOUNTED_DR, ACCOUNTED_CR FROM AX_SLE_LINES_V WHERE GL_POSTED_FLAG = 'N';
  • Reconcile by account and operating unit:
    SELECT CODE_COMBINATION_ID, SUM(ACCOUNTED_DR), SUM(ACCOUNTED_CR) FROM AX_SLE_LINES_V WHERE ORG_ID = :org GROUP BY CODE_COMBINATION_ID;
  • Extract supplier-context detail:
    SELECT THIRD_PARTY_NAME, SUB_NAME, CURRENCY_CODE, ENTERED_DR FROM AX_SLE_LINES_V WHERE THIRD_PARTY_ID IS NOT NULL;

Consumers should treat the view as read-only and apply ORG_ID filtering to respect multi-org security.