Search Results ap_document_lines_v

Overview

AP_DOCUMENT_LINES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Payables (AP). It exposes invoice line detail in the context of the payment that settled it, joining payment records to the corresponding invoice lines. The view is defined as a UNION of two branches: one anchored on issued payments (AP_CHECKS_ALL) and one anchored on payment batch selection criteria (AP_INV_SELECTION_CRITERIA_ALL and AP_SELECTED_INVOICES_ALL). This design allows the view to present payment-to-invoice-line relationships for both quick payments and batch payments within a single result set.

The view plays a supporting role in Payables reporting and integration scenarios where a consumer needs to reconcile what was paid against the individual invoice line detail. Because it is read-only and constructed entirely from base tables, it is typically used for inquiry, custom reports, and data extraction rather than for transactional processing.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects, all resolved through synonyms in the APPS schema:

• AP_CHECKS_ALL — payment header; supplies CHECK_ID and payment identification.
• AP_INVOICES_ALL — invoice header; links invoice to payment and line.
• AP_INVOICE_LINES_ALL — the invoice line detail (amount, tax, quantity, attributes).
• AP_INVOICE_PAYMENTS_ALL — the invoice-to-payment association; supplies INVOICE_PAYMENT_ID.
• AP_PAYMENT_SCHEDULES_ALL — payment schedules; supplies PAYMENT_NUM used in the join.
• AP_INV_SELECTION_CRITERIA_ALL — payment batch selection criteria (second UNION branch).
• AP_SELECTED_INVOICES_ALL — invoices selected into a payment batch.
• PO_HEADERS_ALL — purchase order header; joined outer to provide SEGMENT1.

Joins are keyed on CHECK_ID to INVOICE_ID chains, PAYMENT_NUM, ORG_ID, and the outer join on PO_HEADER_ID. The second branch substitutes the check-run identifier for the check identifier and leaves the invoice payment ID null.

Key Columns

The view exposes a fixed structure across both UNION branches. Notable columns include a literal type marker (200), the payment identifier (CHECK_ID or CHECKRUN_ID/NAME), INVOICE_ID, PAYMENT_NUM, INVOICE_PAYMENT_ID, PO SEGMENT1, and the full invoice line detail.

• LINE_NUMBER, LINE_TYPE_LOOKUP_CODE, AMOUNT, DESCRIPTION — standard line attributes.
• UNIT_PRICE, QUANTITY_INVOICED, UNIT_MEAS_LOOKUP_CODE — quantity and pricing detail.
• TAX, TAX_RATE — tax amounts and rates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield columns.

Common Use Cases and Queries

Typical use is to report payment activity at invoice line granularity, for example reconciling a check or batch to the lines of the invoices it settled.

SELECT check_id, invoice_id, payment_num, po_segment1,
       line_number, amount, tax
FROM   apps.ap_document_lines_v
WHERE  check_id = :p_check_id;

Analysts also aggregate tax or line amounts by payment to support tax reporting and payment reconciliation extracts. Because AP_PAYMENT_SCHEDULES_ALL participates through PAYMENT_NUM, the view is a convenient entry point when a user searches on payment schedules and needs the associated line detail.