Results for “ap_selected_invoices_all”

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

Overview

AP_SELECTED_INVOICES_ALL is a Payables (AP) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that serves as temporary storage for invoices selected for payment within a payment batch. During the Payment Workbench process, the selection criteria engine evaluates open invoices against defined parameters and writes the qualifying candidates into this table before payment documents are built. The records it holds are transient: rows are populated by the invoice selection program, consulted and updated during the payment build and formatting stages, and cleared once the batch is confirmed or the selection is re-run.

The table resides in the AP schema and contains 115 documented columns. Its primary key is AP_SELECTED_INVOICES_PK, composed of CHECKRUN_NAME, INVOICE_ID, and PAYMENT_NUM. Based on the foreign key structure mined from the metadata, the heuristic Data Vault classification for this object is a link — a transactional association table connecting invoice, vendor, bank, check, and accounting dimensions rather than a standalone entity hub or descriptive satellite.

Key Information Stored

The composite primary key uniquely identifies each selected invoice line within a payment run:

• CHECKRUN_NAME — Identifier of the payment batch; foreign key to AP_INV_SELECTION_CRITERIA_ALL.
• INVOICE_ID — The invoice being selected; foreign key to AP_INVOICES_ALL.
• PAYMENT_NUM — Payment sequence number within the batch, allowing a single invoice to appear across multiple payment groupings.

Operationally significant attributes include INVOICE_NUM, INVOICE_DATE, VOUCHER_NUM, INVOICE_AMOUNT, AMOUNT_PAID, and AMOUNT_REMAINING, which drive payee-facing and reconciliation reports. PAYMENT_AMOUNT, DISCOUNT_AMOUNT, and PROPOSED_PAYMENT_AMOUNT capture the amounts computed by the selection engine, while AMOUNT_MODIFIED_FLAG indicates manual override. PAYMENT_PRIORITY, SEQUENCE_NUM, TRANSFER_PRIORITY, and PAYMENT_GROUPING_NUMBER control ordering during payment build. Vendor context is stored in VENDOR_ID, VENDOR_SITE_ID, VENDOR_NUM, VENDOR_NAME, and VENDOR_SITE_CODE, while bank routing uses BANK_ACCOUNT_NUM, BANK_NUM, EXTERNAL_BANK_ACCOUNT_ID, and PAYMENT_CURRENCY_CODE. Control flags such as OK_TO_PAY_FLAG, DONT_PAY_REASON_CODE, EXCLUSIVE_PAYMENT_FLAG, and ALWAYS_TAKE_DISCOUNT_FLAG govern eligibility. Links to physical payment artifacts are held in PAY_SELECTED_CHECK_ID and PRINT_SELECTED_CHECK_ID, both referencing AP_SELECTED_INVOICE_CHECKS_ALL.

Common Use Cases and Queries

Because the table is transient, typical queries support payment batch diagnostics, audit of selection decisions, and reporting on amounts proposed versus paid.

• Reviewing all invoices selected for a specific batch:

SELECT invoice_num, vendor_name, payment_amount, discount_amount
FROM   ap_selected_invoices_all
WHERE  checkrun_name = :batch_name
ORDER  BY sequence_num;

• Identifying invoices flagged not to pay, with reasons:

SELECT invoice_num, dont_pay_reason_code, dont_pay_description
FROM   ap_selected_invoices_all
WHERE  ok_to_pay_flag = 'N';

• Reconciling selected amounts to check assignments by joining on PAY_SELECTED_CHECK_ID.
• Detecting manually modified payment amounts via AMOUNT_MODIFIED_FLAG.

Related Objects

• AP_INVOICES_ALL — joined on INVOICE_ID; source of invoice header data.
• AP_INV_SELECTION_CRITERIA_ALL — joined on CHECKRUN_NAME and CHECKRUN_ID; defines the batch selection parameters.
• AP_SELECTED_INVOICE_CHECKS_ALL — joined on PAY_SELECTED_CHECK_ID and PRINT_SELECTED_CHECK_ID; holds check/ payment document details.
• AP_INVOICE_PAYMENTS_ALL — joined on INVOICE_PAYMENT_ID; links to posted payment records.
• PO_VENDORS and PO_VENDOR_SITES_ALL — joined on VENDOR_ID and VENDOR_SITE_ID.
• GL_CODE_COMBINATIONS — joined on AP_CCID for liability account context.
• AP_BANK_ACCOUNTS_ALL — joined on EXTERNAL_BANK_ACCOUNT_ID.
• GL_SETS_OF_BOOKS_11I and FV_LEGAL_ENTITIES — provide ledger (SET_OF_BOOKS_ID) and legal entity context.