Results for “due_date_low”

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

Overview

AR_BR_BATCHES_V is a Receivables (AR) reporting view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It presents a denormalized, user-facing representation of automatic receipt and remittance batches defined in RA_BATCHES, enriched with decoded lookup meanings, batch source names, selection criteria ranges, transaction type names, customer and site information, receipt method names, and bank details. The view functions as the principal query surface for batch-level receipt processing information in Oracle Receivables, supporting concurrent programs, Oracle Reports, OAF-based pages, and ad hoc SQL used by finance and IT staff. Because it exposes both foreign-key identifiers and their descriptive equivalents, it is frequently chosen over direct queries against RA_BATCHES when human-readable output is required. The view is documented as VALID in the ETRM metadata, and no PL/SQL API or form-level logic is associated with it; it is purely a read-only construct.

Underlying Base Objects

The view is defined over a mix of base tables and synonyms resolved in the APPS schema. The documented referenced objects are: AR_LOOKUPS (a view over FND_LOOKUPS used for status, class, and category decoding), AR_RECEIPT_METHODS, AR_SELECTION_CRITERIA, HZ_CUST_ACCOUNTS_ALL, HZ_CUST_SITE_USES, HZ_PARTIES, HZ_RELATIONSHIPS, RA_BATCHES, RA_BATCH_SOURCES_ALL, and RA_CUST_TRX_TYPES_ALL. RA_BATCHES is the master batch table, and the view joins it to RA_BATCH_SOURCES_ALL for the batch source name (BS.NAME). AR_SELECTION_CRITERIA supplies the include/exclude ranges and filter attributes, including TRX_DATE_LOW and TRX_DATE_HIGH, DUE_DATE_LOW and DUE_DATE_HIGH, TRX_NUMBER_LOW and TRX_NUMBER_HIGH, CUSTOMER_CLASS_CODE, CUSTOMER_CATEGORY_CODE, CUSTOMER_ID, SITE_USE_ID, and BANK_BRANCH_ID. HZ_CUST_ACCOUNTS_ALL, HZ_PARTIES, HZ_CUST_SITE_USES, HZ_RELATIONSHIPS, and HZ_PARTIES (aliased as BRANCHPARTY and BANKPARTY) provide customer account numbers, party names, site locations, and bank branch names. AR_LOOKUPS is joined three times to decode batch process status, customer class, and customer category. Most joins to the selection criteria and lookup tables are outer joins, allowing batches without criteria or unmapped codes to remain visible.

Key Columns

• BATCH_ID, NAME, BATCH_DATE, GL_DATE — Identifiers and dates for the batch header.
• SET_OF_BOOKS_ID, ORG_ID, CURRENCY_CODE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE, EXCHANGE_RATE — Ledger, operating unit, and currency conversion context.
• TYPE, BATCH_SOURCE_ID, BS.NAME — Batch classification and the decoded batch source name.
• LOOKUP_CODE, MEANING (AL_STATUS) — Decoded batch process status.
• ISSUE_DATE, MATURITY_DATE, SPECIAL_INSTRUCTIONS, COMMENTS — Remittance and document attributes.
• SELECTION_CRITERIA_ID, DUE_DATE_LOW, DUE_DATE_HIGH, TRX_DATE_LOW, TRX_DATE_HIGH, TRX_NUMBER_LOW, TRX_NUMBER_HIGH — Include ranges used to select transactions into the batch; TRX_DATE_LOW is the user-searched column representing the lower bound of the transaction date filter.
• CUST_TRX_TYPE_ID, CT.NAME — Transaction type identifier and name.
• RECEIPT_METHOD_ID, RM.NAME — Receipt method identifier and name.
• CUSTOMER_CLASS_CODE, CUSTOMER_CATEGORY_CODE and their MEANING columns — Decoded customer classification fields.
• CUSTOMER_ID, ACCOUNT_NUMBER, PARTY_NAME, SITE_USE_ID, LOCATION — Customer and site identifiers with descriptive attributes.
• BANK_BRANCH_ID, BANK_NAME — Bank branch party name for the remittance.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Audit and concurrent program columns.

Common Use Cases and Queries

Typical usage includes reporting on batch composition, verifying selection criteria applied to automatic receipt creation, and analyzing batch source and status distributions. The following example retrieves batches whose transaction date lower bound falls within a given range, demonstrating the user-searched column:

SELECT batch_id, name, batch_date, type, trx_date_low, trx_date_high
FROM   apps.ar_br_batches_v
WHERE  trx_date_low BETWEEN :p_from_date AND :p_to_date
ORDER  BY batch_date DESC;

A second common pattern joins the view to RA_CUSTOMER_TRX_ALL or AR_CASH_RECEIPTS_ALL to confirm which transactions were selected by a batch's criteria. Administrators also query the view to audit batch source names, receipt method names, and bank names for reconciliation. Because the view performs numerous outer joins across the TCA and Receivables schemas, queries should filter on indexed columns such as BATCH_ID, ORG_ID, or BATCH_DATE where possible to maintain performance.