Search Results ar_selection_criteria




Overview
Explore in AI Chat

Overview

AR_SELECTION_CRITERIA is a Receivables (AR) module table in the AR schema that stores the selection criteria associated with an entity. It functions as a configurable filter repository, allowing Oracle EBS Receivables processes — most notably AutoInvoice grouping, receipt application selection, and post-batch adjustments — to identify specific sets of customer transactions or receipts based on a defined range or list of attributes. Rather than hard-coding selection logic, EBS stores the predicates as rows so that concurrent programs and reporting tools can retrieve and apply them dynamically at runtime.

From a heuristic Data Vault modeling perspective, the mined foreign-key structure suggests a link classification. The table’s foreign keys point outward to multiple descriptive dimensions — HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, RA_CUST_TRX_TYPES_ALL, AR_RECEIPT_METHODS, and PV_ENTY_SELECT_CRITERIA — meaning each row ties a selection criteria header to specific customer, site, transaction type, and receipt method reference points. This is characteristic of a link table that resolves many-to-many relationships between a criteria entity and its associated business entities, rather than a pure hub (business key) or satellite (descriptive attributes) structure.

Key Information Stored

The table contains 19 documented columns. The surrogate primary key is SELECTION_CRITERIA_ID, which is also the sole business-key candidate enforced by the unique index AR_SELECTION_CRITERIA_U1. This column is the join point to the parent PV_ENTY_SELECT_CRITERIA table and uniquely identifies each criteria row.

Business filter attributes fall into several groups:

Common Use Cases and Queries

Typical scenarios include identifying all selection criteria defined against a given customer, or determining which transaction types and receipt methods are referenced by an active criteria set. A common reporting pattern joins the table to its parent criteria header and to the customer account:

  • Retrieving criteria for a specific customer: SELECT selection_criteria_id, trx_number_low, trx_number_high, due_date_low, due_date_high FROM ar_selection_criteria WHERE customer_id = :p_customer_id;
  • Resolving the transaction type description: join CUST_TRX_TYPE_ID to RA_CUST_TRX_TYPES_ALL.NAME to produce human-readable output.
  • Auditing recently created or modified criteria using CREATION_DATE or LAST_UPDATE_DATE range predicates, useful for change-tracking and SOX compliance reporting.
  • Diagnosing AutoInvoice or receipt application behavior by extracting the exact date and number ranges that a given criteria set applies.

Related Objects

The most significant related objects are those referenced by the documented foreign keys, plus the parent criteria entity:

  • PV_ENTY_SELECT_CRITERIA — parent table; joined on SELECTION_CRITERIA_ID.
  • HZ_CUST_ACCOUNTS — customer account master; joined on CUSTOMER_ID.
  • HZ_CUST_SITE_USES_ALL — customer site uses; joined on SITE_USE_ID.
  • RA_CUST_TRX_TYPES_ALL — transaction type definitions; joined on CUST_TRX_TYPE_ID.
  • AR_RECEIPT_METHODS — receipt method definitions; joined on RECEIPT_METHOD_ID.
  • RA_CUSTOMER_TRX_ALL — primary transaction table filtered by the criteria ranges in downstream processes.
  • AR_RECEIVABLES_TRX_ALL and AR_CASH_RECEIPTS_ALL — receipt-side objects commonly evaluated against receipt method and bank branch criteria.
  • FND_CONCURRENT_PROGRAMS / FND_REQUEST — submission framework used by concurrent processes that consume selection criteria at runtime.