Results for “ar_funds_capture_orders_v”

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

Overview

AR_FUNDS_CAPTURE_ORDERS_V is an APPS-owned, VALID database view in the Oracle Receivables (AR) module. It exposes a consolidated, denormalized "funds capture order" record set that joins cash receipts against receipt classes, receipt methods, customer parties, locations, bank account usage, and payment schedules. The view is designed to feed funds-capture and bank-integration processing, where each row represents a single automatic, trxn-extension-tagged CASH receipt that is eligible to be transmitted through a payment/funds capture pipeline.

The view is a single-source, read-only projection. It contains no local modifications, and its WHERE clause enforces strict filtering so that only receipts meeting the funds-capture criteria are returned. The view is not seeded with a BR_DISPUTED_FLAG column; a user searching for "br_disputed_flag" will not find it here. The disputed flag concept relates to BR (Bill Receivables / dispute) logic rather than to this funds-capture view, and it must be sourced from the underlying AR tables (for example, receipt or transaction-level dispute attributes) rather than from AR_FUNDS_CAPTURE_ORDERS_V.

Underlying Base Objects

The view is defined over thirteen documented suppliers, joined with both inner and outer (ANSI (+)) joins:

• AR_AUTOREM_INTERIM — outer-joined on CASH_RECEIPT_ID and BATCH_ID (Bug 7133142); supplies CURRENT_WORKER.
• AR_CASH_RECEIPTS — the driving table (CR), filtered to TYPE = 'CASH'.
• AR_RECEIPT_METHODS and AR_RECEIPT_CLASSES — inner-joined via RECEIPT_METHOD_ID / RECEIPT_CLASS_ID, restricted to CREATION_METHOD_CODE = 'AUTOMATIC'.
• AR_PAYMENT_SCHEDULES — inner-joined on CASH_RECEIPT_ID to supply DUE_DATE.
• CE_BANK_ACCT_USES_OU_V — provides BANK_ACCOUNT_ID and BANK_ACCT_USE_ID.
• HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_PARTY_SITES, HZ_LOCATIONS — the TCA customer hierarchy, resolving party, account, site use, party site, and location.

Key Columns

• SELECTED_REMITTANCE_BATCH_ID — batch identifier; also concatenated as 'AR_'||batch_id for external order numbering.
• WORKER_ID — NVL(INTRM.CURRENT_WORKER,0); the interim worker assigned to the remittance batch.
• RECEIPT_DATE / DUE_DATE — receipt and payment-schedule due dates.
• CURRENCY_CODE, AMOUNT — receipt currency and amount.
• PAYMENT_TRXN_EXTENSION_ID — mandatory-mapped extension link; must be NOT NULL by the WHERE clause.
• BANK_ACCOUNT_ID, PAY_FROM_CUSTOMER, CUSTOMER_SITE_USE_ID, PARTY_ID, LOCATION_ID, ORG_ID, LEGAL_ENTITY_ID — identity and operational-unit context.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1–15, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — descriptive flexfield and audit columns.

Common Use Cases and Queries

Typical use cases include funds-capture batch extraction, remittance reconciliation, and bank-file generation. To confirm the absence of a disputed flag and inspect receipt-level data:

• SELECT SELECTED_REMITTANCE_BATCH_ID, AMOUNT, CURRENCY_CODE, RECEIPT_DATE, PAY_FROM_CUSTOMER FROM AR_FUNDS_CAPTURE_ORDERS_V WHERE ORG_ID = :org_id;
• SELECT WORKER_ID, COUNT(*) FROM AR_FUNDS_CAPTURE_ORDERS_V GROUP BY WORKER_ID;

To obtain dispute information, join back to the AR transaction or receipt tables rather than expecting a BR_DISPUTED_FLAG on this view.