Results for “ap_ae_lines_v”

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

Overview

AP_AE_LINES_V is a Payables (AP) module view in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents the accounted lines associated with subledger accounting events generated by Payables. The view is a descriptive, decoded projection of the base accounting entries table, joining it to Payables lookup codes so that stored code values are replaced by their human-readable display text. It is used in reporting and integration scenarios where accounting-line detail must be inspected or extracted with meaningful labels rather than raw lookup codes.

The view is particularly relevant to users searching on the ae_line_type_code attribute, since the view exposes that value as a decoded AE_LINE_TYPE_CODE column derived from the lookup type AE LINE TYPE. The object is documented as a view with no independent DBA implementation and no independently documented base objects, meaning its behavior is defined entirely by its view text.

Underlying Base Objects

The view is defined over AP_AE_LINES, the Payables subledger accounting lines table, aliased AAL. All primary business columns — identifiers, currency attributes, entered and accounted amounts, and audit columns — originate from this table. Each row in the view corresponds to one row in AP_AE_LINES, so key values such as AE_LINE_ID and AE_HEADER_ID are preserved unchanged.

The view also joins AP_LOOKUP_CODES three times to decode stored codes into display text:

• ALC1 — lookup type AE LINE TYPE, matched on the line type code. This is an inner join, so the line type must exist in the lookup set for the row to appear.
• ALC2 — lookup type ACCOUNTING ERROR TYPE, an outer join keyed to the accounting error code.
• ALC3 — lookup type POSTING EXCEPTIONS, an outer join keyed to the GL transfer error code.

Because the error-code joins are outer, lines without accounting or transfer errors are still returned, with null decode values.

Key Columns

The principal identifiers are AE_LINE_ID, AE_HEADER_ID, and AE_LINE_NUMBER, which uniquely locate a line within its accounting event header. AE_LINE_TYPE_CODE is the decoded line type — for example, distinguishing debit, credit, tax, or other accounting line categories — and is the attribute most commonly used to filter or group results.

The financial columns are ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, and ACCOUNTED_CR, along with CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_DATE, and CURRENCY_CONVERSION_RATE. CODE_COMBINATION_ID links the accounting line to its GL account combination.

Exception and audit columns include ACCOUNTING_ERROR_CODE, GL_TRANSFER_ERROR_CODE, ORG_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and the concurrent program columns PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include reconciling Payables accounting entries, analyzing line type distributions, and monitoring lines that failed accounting or GL transfer. A common query filters by line type:

• SELECT ae_header_id, ae_line_id, ae_line_type_code, accounted_dr, accounted_cr FROM ap_ae_lines_v WHERE ae_line_type_code = :line_type;
• SELECT ae_line_type_code, COUNT(*) FROM ap_ae_lines_v GROUP BY ae_line_type_code;
• SELECT ae_line_id, accounting_error_code, gl_transfer_error_code FROM ap_ae_lines_v WHERE accounting_error_code IS NOT NULL OR gl_transfer_error_code IS NOT NULL;

Because the view decodes line type, accounting error, and posting exception codes, it is well suited to reporting tools where end users must read descriptive values. Queries should still join to AP_AE_HEADERS to obtain invoice and event context, since the view exposes only line-level detail.