Search Results reference_8

Overview

The view AX_SLE_LINES_V belongs to the AX – Global Accounting Engine product within Oracle E-Business Suite, and is documented in ETRM for releases 12.1.1 and 12.2.2. Its description, "Entry lines", identifies it as a reporting layer over the subledger accounting entry lines generated by the Global Accounting Engine (also referred to as AX or the Global Accounting Engine subledger). The Global Accounting Engine creates accounting entries for transactions originating in feeder systems and stores them prior to transfer and posting to the General Ledger. AX_SLE_LINES_V exposes one row per accounting entry line, denormalised with header-level and third-party attributes so that reporting, reconciliation, and integration processes can retrieve fully described journal lines without joining multiple tables.

Underlying Base Objects

The ETRM implementation section for this object states that it is "Not implemented in this database", meaning the view is not created in every EBS environment and that its presence depends on whether the Global Accounting Engine is installed. ETRM also records no formally documented base objects for this view, so the relationship to underlying tables must be read from the view text itself. The view text shows that the primary source is aliased L, the subledger entry line table, with supporting joins to aliased H (supplying APPLICATION_ID), V (supplying VENDOR_NAME as THIRD_PARTY_NAME), and VS (supplying VENDOR_SITE_CODE as SUB_NAME). These joins resolve the numeric third-party and site identifiers into human-readable supplier and supplier site names, which is the principal value the view adds over the base line table.

Key Columns

• L.SLE_HEADER_ID, L.SLE_LINE_NUM, L.JOURNAL_SEQUENCE_ID — header and line identifiers that uniquely order entry lines.
• L.CODE_COMBINATION_ID — the accounting flexfield combination for the line; the natural join key to GL code combinations.
• L.ACCOUNTED_DR, L.ACCOUNTED_CR, L.ENTERED_DR, L.ENTERED_CR — accounted and entered debit/credit amounts, the core monetary values.
• L.CURRENCY_CODE, L.CURRENCY_CONVERSION_TYPE, L.CURRENCY_CONVERSION_DATE, L.CURRENCY_CONVERSION_RATE — currency and conversion attributes for foreign-currency lines.
• L.GL_POSTED_FLAG, L.GL_POSTED_DATE — indicators of whether and when the line was posted to the General Ledger, essential for reconciliation.
• L.THIRD_PARTY_ID, V.VENDOR_NAME, L.SUB_ID, VS.VENDOR_SITE_CODE — supplier and supplier site identification, resolved to descriptive names.
• L.REFERENCE_1 through L.REFERENCE_60 and L.REFERENCE_NUM1 through L.REFERENCE_NUM9 — the extensive flexible reference attributes used by the Global Accounting Engine to carry descriptive and transactional context into accounting.
• L.ORG_ID — the operating unit, supporting multi-org security and reporting.
• L.COMMENT_LINE, L.BALANCE_FLAG — descriptive text and balance indicator for the line.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and ROW_ID.

Common Use Cases and Queries

The view is typically queried for subledger-to-GL reconciliation, unposted entry analysis, supplier-based accounting reporting, and data extraction into external warehouses. Because third-party and site names are pre-joined, users avoid re-deriving supplier detail. A representative query retrieving unposted supplier lines is:

SELECT sle_header_id, sle_line_num, third_party_name, sub_name, currency_code, accounted_dr, accounted_credit_placeholder, gl_posted_flag, gl_posted_date, org_id FROM ax_sle_lines_v WHERE gl_posted_flag = 'N' AND org_id = :p_org_id ORDER BY sle_header_id, sle_line_num;

Aggregation by supplier and period is equally common:

SELECT third_party_name, SUM(accounted_dr) total_dr, SUM(accounted_cr) total_cr FROM ax_sle_lines_v WHERE gl_posted_date BETWEEN :p_from AND :p_to GROUP BY third_party_name;

Note that ACCOUNTED_DR and ACCOUNTED_CR are the documented debit and credit columns; substitute them directly for any placeholder shown above. Always confirm the view exists in the target environment, since ETRM records it as not implemented in all databases.