Results for “ap_ae_lines_all”

50+ results




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

Overview

AP_AE_LINES_ALL is the accounting entry lines table in the Oracle Payables (AP) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual debit and credit lines that make up the subledger accounting entries generated for Payables transactions, including invoices, payments, adjustments, and related events. Each row represents one accounting line within an accounting event, carrying the distribution account, entered and accounted amounts, currency conversion information, and the linkage back to the source transaction processed by Payables Accounting.

The table is owned by the AP schema and is validated in the ETRM 12.2.2 data model. Its physical schema documents 56 columns. The primary key is AP_AE_LINES_PK, defined on the AE_LINE_ID column. Two unique indexes serve as business-key candidates: AP_AE_LINES_U1 on AE_LINE_ID and AP_AE_LINES_U2 on the composite of AE_HEADER_ID and AE_LINE_NUMBER. This composite uniqueness enforces that line numbers are sequential and non-duplicated within an accounting header.

Based on the mined foreign-key structure, the ETRM metadata offers a heuristic Data Vault classification of this object as a link. In modeling terms, this reflects the table's role in associating an accounting header with accounts, currencies, document sequences, conversion types, and supplier parties via its foreign keys, rather than functioning as an independent hub of business keys or a descriptive satellite.

Key Information Stored

The most significant columns of AP_AE_LINES_ALL include the following. The surrogate primary key is AE_LINE_ID, which uniquely identifies each accounting line. The business-key candidate pair AE_HEADER_ID and AE_LINE_NUMBER ties each line to its parent accounting entry header and establishes line ordering within that header.

Common Use Cases and Queries

AP_AE_LINES_ALL is central to subledger accounting reconciliation, audit, and reporting. Typical queries join lines to their headers to reconstruct complete accounting entries, or join to GL interfaces to confirm transfer status.

  • Reconstructing the full accounting entry: SELECT h.ae_header_id, l.ae_line_number, l.ae_line_type_code, l.code_combination_id, l.entered_dr, l.entered_cr, l.accounted_dr, l.accounted_cr FROM ap.ap_ae_headers_all h, ap.ap_ae_lines_all l WHERE h.ae_header_id = l.ae_header_id;
  • Identifying lines not yet transferred to GL by checking GL_TRANSFER_ERROR_CODE or the absence of a GL_SL_LINK_ID.
  • Auditing supplier activity using THIRD_PARTY_ID and THIRD_PARTY_SUB_ID to trace accounting lines to vendor and vendor site.
  • Currency analysis using CURRENCY_CODE, CURRENCY_CONVERSION_RATE, and the entered versus accounted amount columns.

Related Objects

The following related objects are the most significant based on the documented foreign-key relationships.

  • AP_AE_HEADERS_ALL — parent header table; join on AE_HEADER_ID.
  • FND_CURRENCIES — currency definition; join on CURRENCY_CODE.
  • GL_DAILY_CONVERSION_TYPES — conversion type definition; join on CURRENCY_CONVERSION_TYPE.
  • FND_DOCUMENT_SEQUENCES — document sequence definition; join on SUBLEDGER_DOC_SEQUENCE_ID.
  • PO_VENDORS — supplier master; join on THIRD_PARTY_ID.
  • PO_VENDOR_SITES_ALL — supplier site; join on THIRD_PARTY_SUB_ID.