Results for “ax_ap_ae_lines_all_v”

8 results




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

Overview

AX_AP_AE_LINES_ALL_V is a compatibility view in the Oracle E-Business Suite Global Accounting Engine (AX) module. Its documented purpose, per the ETRM metadata, is to serve as a replacement for the Payables table AP_AE_LINES_ALL when the AX accounting engine is used instead of the standard Subledger Accounting (SLA) engine. In 12.1.1 and 12.2.2 environments, the AX Global Accounting Engine was retained for certain country localizations and legacy configurations, where transactions must be transformed into the AX accounting model. This view abstracts that transformation, allowing external reports, integrations, and downstream processes that were written against AP_AE_LINES_ALL to continue functioning without modification of their SQL, mapping the underlying AX subledger lines (AXSL) into the AP_AE_LINES_ALL column shape.

Because the view presents accounting event lines in the familiar Payables accounting-entry structure, it is consumed by reporting tools, custom extensions, and reconciliation processes that expect the AP_AE_LINES_ALL interface rather than the internal AX schema.

Underlying Base Objects

The ETRM metadata lists no documented referenced base objects for this view. However, the view text reveals that it is defined over AX subledger line data and associated AX event data. The primary aliases are AXSL (the AX subledger lines source) and AXE (the AX event source), joined to supply journal and header information. Key source attributes include JOURNAL_SEQUENCE_ID, SLE_HEADER_ID, SLE_LINE_NUM, CODE_COMBINATION_ID, CURRENCY_CODE, and the entered/accounted debit and credit amounts. Event-level attributes such as DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE, and EVENT_TYPE are drawn from AXE.

Note the metadata states the view is "Not implemented in this database," meaning in the queried environment the object was not instantiated — behavior that occurs when the AX accounting engine is not active, so the view may exist only conditionally. Where the view is deployed, its definition is inert until the AX engine populates the underlying AX subledger tables.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling AX-generated accounting entries against Payables invoices, extracting distribution lines for GL transfer validation, and feeding custom accounting reports that were originally built on AP_AE_LINES_ALL.

SELECT ae_header_id, ae_line_number, code_combination_id,
       entered_dr, entered_cr, accounted_dr, accounted_cr,
       currency_code, vendor_id, org_id
FROM   ax_ap_ae_lines_all_v
WHERE  org_id = :p_org_id
  AND  creation_date >= :p_start_date;

Because the object is engine-dependent and may be unimplemented, production queries should first confirm the AX engine is active. Where it is not, standard AP_AE_LINES_ALL or the SLA tables (XLA_AE_LINES) should be queried instead. When available, this view remains the most direct path for preserving legacy AP accounting-line reporting under the Global Accounting Engine.