Search Results note_receivable_issue_date

Overview

ARBV_CASH_RECEIPTS is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and presents descriptive and transactional information about cash receipts remitted by customers as payment for goods or services. The view exposes a business-friendly projection of receipt data, applying Oracle EBS descriptive flexfield "_LA:" pseudo-column conventions so that lookup-based attributes such as receipt status, reversal reason, and reversal category are surfaced as translated meanings rather than raw codes. The view definition terminates with the WITH READ ONLY clause, confirming that it is intended strictly for query and reporting purposes and cannot be used for DML.

Because the underlying view filters on TYPE = 'CASH', ARBV_CASH_RECEIPTS returns only standard cash receipts, excluding miscellaneous, guaranteed, and other receipt types maintained in the base table. This makes it a convenient, self-filtering source for reporting on customer cash payments, remittances, and bank deposit activity.

Underlying Base Objects

The documented base object referenced by the view is AR_CASH_RECEIPTS, accessed through a synonym. AR_CASH_RECEIPTS is the core Receivables table that stores every receipt created in the system, including its accounting, customer, bank, and remittance attributes. ARBV_CASH_RECEIPTS is defined directly over this table with an explicit column list and a single filter predicate (TYPE = 'CASH'). No joins to lookup, customer, or bank tables are embedded in the view text; instead, descriptive flexfield ("_LA:") references resolve lookup meanings at runtime. Users should therefore expect one row per cash receipt for the organization context, and should be prepared to join to AR_LOOKUPS, AR_CUSTOMERS, and bank account tables when additional descriptive attributes are required.

Key Columns

• CASH_RECEIPT_ID — Primary key and unique identifier of the receipt; the basis for joins to related AR tables.
• RECEIPT_NUMBER — The user-visible, possibly document-sequenced receipt number.
• RECEIPT_AMOUNT — Entered amount of the receipt in its transaction currency.
• RECEIPT_DATE — Date the receipt was recorded.
• DOCUMENT_SEQUENCE_NUMBER — Assigned document sequence value where legal numbering applies.
• CURRENCY_EXCHANGE_RATE, CURRENCY_EXCHANGE_RATE_TYPE, CURRENCY_EXCHANGE_RATE_DATE — Currency conversion information for foreign-currency receipts.
• CURRENCY_CODE — Receipt currency.
• DEPOSIT_DATE — Date the receipt was deposited.
• "_LA:RECEIPT_STATUS" — Lookup meaning derived from CR.STATUS against the AR_LOOKUPS lookup type CHECK_STATUS. This is the attribute most commonly associated with the search term receipt_status_code, since the view surfaces the human-readable status meaning.
• "_LA:REVERSAL_REASON" — Meaning of the reversal reason code from lookup type CKAJST_REASON.
• REVERSAL_DATE, REVERSAL_COMMENTS, "_LA:REVERSAL_CATEGORY" — Reversal details, with the reversal category resolved from lookup type REVERSAL_CATEGORY_TYPE.
• CUSTOMER_RECEIPT_REFERENCE — Customer-supplied reference, such as a check number.
• "_LA:FACTORING_FLAG" — Yes/No meaning indicating whether the receipt was selected for factoring; accompanied by FACTOR_DISCOUNT_AMOUNT.
• "_LA:OVERRIDE_REMIT_ACCOUNT" — Yes/No meaning for the remittance account override flag.
• ANTICIPATED_CLEARING_DATE — Expected clearing date for the receipt.
• NOTE_RECEIVABLE_ISSUER_NAME, NOTE_RECEIVABLE_ISSUE_DATE — Issuer and issue data for note receivable receipts.
• PAY_FROM_CUSTOMER, CUSTOMER_SITE_USE_ID, CUSTOMER_BANK_ACCOUNT_ID — Customer and customer bank account references.
• REMITTANCE_BANK_ACCOUNT_ID — Remittance (internal) bank account used for the receipt.
• ORG_ID, SET_OF_BOOKS_ID — Organization and ledger context, essential for multi-org and multi-ledger filtering.
• USSGL_TRANSACTION_CODE, COMMENTS — Additional transaction and free-text attributes.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY for audit purposes.

Common Use Cases and Queries

The view is typically used for receipt status reporting, cash application analysis, deposit and remittance reconciliation, and export to downstream reporting or integration layers. Because the status is exposed as a translated lookup meaning, users can filter on business-readable values without joining AR_LOOKUPS.

Example — list receipts and their status for an organization:

• SELECT receipt_number, receipt_date, receipt_amount, currency_code, "_LA:RECEIPT_STATUS" receipt_status, customer_receipt_reference FROM arbv_cash_receipts WHERE org_id = :org_id ORDER BY receipt_date DESC;

Example — find reversed receipts with reason and category:

• SELECT receipt_number, receipt_date, "_LA:RECEIPT_STATUS" status, "_LA:REVERSAL_REASON" reversal_reason, "_LA:REVERSAL_CATEGORY" reversal_category, reversal_date FROM arbv_cash_receipts WHERE "_LA:REVERSAL_REASON" IS NOT NULL;

Example — trace unapplied cash awaiting clearing:

• SELECT cr.receipt_number, cr.receipt_amount, cr.anticipated_clearing_date, cr.remittance_bank_account_id FROM arbv_cash_receipts cr WHERE cr.anticipated_clearing_date >= SYSDATE AND NOT EXISTS (SELECT 1 FROM ar_receivable_applications_all ara WHERE ara.cash_receipt_id = cr.cash_receipt_id AND ara.status = 'APP');

Because the view is read only and filters to cash receipts only, it is a safe and efficient starting point for custom reports, Oracle BI Publisher data models, and integration extracts that require receipt status and remittance detail.