Results for “ap_inv_selection_criteria_v”

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

Overview

The view AP_INV_SELECTION_CRITERIA_V belongs to the Oracle Payables (AP) application module and is documented in the ETRM reference material as a Release 10SC-only object. In the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, its metadata is retained for historical and reference purposes, but the view is not implemented in current schemas. The ETRM implementation notes confirm this with the statement: "Not implemented in this database," meaning the object does not exist as a valid database construct in a standard 12.1.1 or 12.2.2 installation.

Conceptually, this view presents invoice selection criteria records used by the Payables payment processing engine. Payment batch and payment process requests store the criteria that determine which invoices, payment methods, dates, and amounts are eligible for a given check run. The view consolidates these criteria — including payment priorities, check date ranges, exchange rate attributes, and print/document controls — to expose them in a denormalized, query-friendly format for reporting and integration.

Underlying Base Objects

The ETRM metadata for this view records no documented base objects in 12.2.2, and the view text is derived from a single primary table aliased as AISC, which corresponds to AP_INV_SELECTION_CRITERIA_ALL. The view also performs an outer join to a bank account table aliased as ABA, which supplies the BANK_ACCOUNT_NAME value. The join AISC.BANK_ACCOUNT_ID = ABA.BANK_ACCOUNT_ID enriches the criterion rows with the corresponding bank account name.

Because the metadata states "Referenced base objects: none documented," the base table relationships should be treated as inferred from the view text rather than as officially confirmed dependencies in the 12.2.2 data dictionary. The AISC.ROWID is exposed as ROW_ID, and the inclusion of standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and ORG_ID confirms that the underlying entity is a multi-org (Operating Unit) enabled table.

Key Columns

• CHECKRUN_ID / CHECKRUN_NAME — Identifies the payment batch or check run whose selection criteria are represented.
• PAYMENT_METHOD_LOOKUP_CODE — The payment method (for example, check, wire, or electronic) applied to the selection.
• CHECK_DATE, PAY_THRU_DATE, EXCHANGE_DATE — Date parameters controlling which invoices are selected.
• MIN_CHECK_AMOUNT, MAX_PAYMENT_AMOUNT, MAX_OUTLAY — Amount thresholds that bound the payment run.
• HI_PAYMENT_PRIORITY / LOW_PAYMENT_PRIORITY — The payment priority range used to filter candidate invoices.
• PAY_ONLY_WHEN_DUE_FLAG — Determines whether invoices must be due before payment.
• DOCUMENT_ORDER_LOOKUP_CODE and END_PRINT_DOCUMENT — Control the order in which payment documents print and whether document printing terminates after the run; these are directly relevant to the user's search term.
• FIRST_AVAILABLE_DOCUMENT / FIRST_VOUCHER_NUMBER — The starting document or voucher number for the run.
• BANK_ACCOUNT_ID / BANK_ACCOUNT_NAME — The disbursement bank account associated with the criteria.
• ORG_ID — The Operating Unit to which the criteria record belongs.
• Attribute columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15) — Descriptive flexfield context and segment values.

Common Use Cases and Queries

This view would traditionally support reporting on payment batch configuration, particularly for auditing the END_PRINT_DOCUMENT and document-ordering behavior specified for a check run. A representative query, notwithstanding the view's absence in 12.x, follows the documented column list:

• SELECT checkrun_name, payment_method_lookup_code, check_date, end_print_document FROM ap_inv_selection_criteria_v WHERE org_id = :p_org_id;
• SELECT checkrun_id, min_check_amount, max_payment_amount, pay_only_when_due_flag FROM ap_inv_selection_criteria_v WHERE checkrun_id = :p_checkrun_id;

In practice, on a 12.1.1 or 12.2.2 instance, equivalent data is obtained from AP_INV_SELECTION_CRITERIA_ALL and related payment process request tables such as IBY_PAY_SERVICE_REQUEST_INT and IBY_PAYMENT_INSTRUCTIONS. The END_PRINT_DOCUMENT flag is most reliably found in the payment instruction and payment process request tables in modern releases, since Oracle Payables migrated payment processing to the Oracle Payments (IBY) framework. Consultants should therefore avoid referencing AP_INV_SELECTION_CRITERIA_V in custom 12.1.1 or 12.2.2 code and instead use the currently implemented IBY-based objects.