Search Results ar_selection_criteria_u1

Overview

AR.AR_SELECTION_CRITERIA is a Bills Receivable-specific table within the Oracle E-Business Suite Receivables (AR) schema. It stores the reusable selection criteria that drive different stages of the Bills Receivable lifecycle. The most prominent consumer is the Bills Receivable Batch Creation concurrent program, which reads the criteria to determine precisely which transactions qualify for inclusion in a newly generated bill receivable batch. Rather than hard-coding filter logic, the application persists each criterion set as a row, allowing multiple batch definitions, remittance selection rules, and downstream bill processing routines to share a single configuration repository.

The object is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, residing in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Heuristic Data Vault classification mined from the foreign-key structure suggests treating this table as a link — it connects an external selection-criteria parent (PV_ENTY_SELECT_CRITERIA) to multiple dimension entities such as customers, transaction types, receipt methods, and bank branches, capturing the qualifying ranges that bind them together.

Key Information Stored

The table contains 19 documented columns. The surrogate primary key is SELECTION_CRITERIA_ID (NUMBER(15)), which is also the sole business-key candidate, enforced uniquely by index AR_SELECTION_CRITERIA_U1 on tablespace APPS_TS_TX_IDX. Beyond the key, the most significant columns fall into range, classification, and foreign-key groups:

• Range filters: DUE_DATE_LOW / DUE_DATE_HIGH and TRX_DATE_LOW / TRX_DATE_HIGH bound the transaction and due-date windows; TRX_NUMBER_LOW / TRX_NUMBER_HIGH bound the document-number range.
• Transaction attributes: CUST_TRX_TYPE_ID (transaction type), RECEIPT_METHOD_ID (payment method), and BANK_BRANCH_ID (bank name) target specific processing classifications.
• Customer attributes: CUSTOMER_CLASS_CODE and CUSTOMER_CATEGORY_CODE classify the customer population; CUSTOMER_ID and SITE_USE_ID narrow selection to a specific account or site.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN follow the standard WHO column convention, with CREATED_BY and LAST_UPDATED_BY referencing FND_USER.USER_ID.

Common Use Cases and Queries

The dominant use case is inspecting or auditing the criteria that a Bills Receivable batch will apply before execution. A typical query joins the criteria to its parent to preview eligible transactions:

SELECT sc.selection_criteria_id, sc.cust_trx_type_id, sc.trx_date_low, sc.trx_date_high, sc.due_date_low, sc.due_date_high, sc.customer_id, sc.site_use_id FROM ar.ar_selection_criteria sc WHERE sc.selection_criteria_id = :p_id;

Reporting scenarios include verifying which receipt methods or bank branches are targeted, reconciling batch output against configured criteria, and validating range overlaps that might cause duplicate transaction selection. When a batch produces unexpected results, the criteria row is the first object to review, since every filter that the concurrent program applies is materialized here. Developers extending the Bills Receivable flow frequently query by CUSTOMER_ID or CUST_TRX_TYPE_ID to trace which selection definitions reference a given account or transaction type.

Related Objects

The foreign keys documented for this table identify the principal related objects and the exact join columns:

• PV_ENTY_SELECT_CRITERIA — parent entity linked via AR_SELECTION_CRITERIA.SELECTION_CRITERIA_ID → PV_ENTY_SELECT_CRITERIA.
• HZ_CUST_ACCOUNTS — referenced through AR_SELECTION_CRITERIA.CUSTOMER_ID.
• HZ_CUST_SITE_USES_ALL — referenced through AR_SELECTION_CRITERIA.SITE_USE_ID.
• RA_CUST_TRX_TYPES_ALL — referenced through AR_SELECTION_CRITERIA.CUST_TRX_TYPE_ID.
• AR_RECEIPT_METHODS — referenced through AR_SELECTION_CRITERIA.RECEIPT_METHOD_ID.
• FND_USER — implied by the WHO columns CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — implied by LAST_UPDATE_LOGIN.

Together these relationships establish AR_SELECTION_CRITERIA as the connective link between Bills Receivable processing logic and the customer, transaction, and payment reference data it evaluates.