Results for “future_dated_payment_flag”

10 results




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

Overview

AP_INV_SELECTION_CRITERIA_ALL is the Oracle Payables table that stores payment batch invoice selection criteria. Each row represents the header definition of a payment batch — the user-supplied filters and options that the Payment Batch (payment run) process uses to select invoices for payment and to drive check or electronic payment generation. It is owned by the AP schema and is populated whenever a user creates a payment batch from the Payment Workbench or the Payment Batch window, or when a batch is created programmatically through the Payables payment APIs.

The table sits at the center of the payment batch lifecycle. The primary key AP_INVOICE_SELECTION_CRITER_PK corresponds to the CHECKRUN_ID column, which is the surrogate identifier of the payment batch. Foreign-key metadata also identifies CHECKRUN_NAME with ORG_ID as the unique business-key candidate (AP_INV_SELECTION_CRITERIA_U1), meaning the batch name is unique per operating unit. From a Data Vault modeling perspective, the mined FK structure suggests this object behaves as a hub: CHECKRUN_ID/CHECKRUN_NAME is the business key referenced by numerous downstream satellites and link-style detail tables (checks, selected invoices, groups, confirmations).

Key Information Stored

The table contains 93 documented columns. The most functionally significant are:

Common Use Cases and Queries

Typical usages include auditing active payment batches, reporting on selection criteria, and diagnosing why an invoice was or was not selected. A common query retrieves batch headers per operating unit:

  • SELECT checkrun_id, checkrun_name, check_date, status, bank_account_name FROM ap.ap_inv_selection_criteria_all WHERE org_id = :p_org_id AND status = 'CREATED';
  • Join to AP_SELECTED_INVOICES_ALL on CHECKRUN_NAME to view the invoices chosen for a batch, and to AP_UNSELECTED_INVOICES_ALL on CHECKRUN_ID for rejects.
  • Join to AP_CHECKS_ALL on CHECKRUN_ID or CHECKRUN_NAME to obtain payment documents produced.
  • Compare against FV_AAN_MATCHES_TEMP on CHECKRUN_NAME — the search term that led here — since that temporary table is keyed by CHECKRUN_NAME and is populated by Funds/Public Sector matching processes that reference the payment batch header.
  • Template reporting: SELECT template_id, checkrun_name FROM ap.ap_inv_selection_criteria_all WHERE template_flag = 'Y';

Related Objects

The table is both a child of configuration objects and a parent of payment-processing detail tables. Key relationships include: