Search Results receipt_document_number

Overview

AR_CR_INF_V is a read-only 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 is classified as a VALID database object in the ETRM repository. The view presents a denormalized, human-readable picture of cash receipts activity by joining core receipt data with customer and party information and with the receipt method definition. Its central purpose is to expose receipt-level detail — receipt number, document sequence value, receipt date, customer name, customer account number, and receipt method name — without requiring the report or integration author to reimplement the underlying join logic.

The object is most frequently encountered in reporting and integration contexts: custom concurrent program reports, BI Publisher data templates, Oracle Discoverer or OBIEE subject areas, interface extracts, and ad hoc SQL used by functional and technical consultants. Because the view resolves the receipt method name from AR_RECEIPT_METHODS, it is particularly relevant to users searching on the term "receipt_method." The receipt method is the user-defined instrument or channel through which a payment is received, such as check, wire transfer, credit card, or cash, and it governs posting, remittance, and clearing behavior within Receivables. AR_CR_INF_V surfaces that name directly rather than requiring a lookup against the receipt method identifier.

The view is defined with outer joins to the customer and party tables, so it retains receipt rows even where the paying customer or party record is not populated. This is significant for receipts that are applied to unidentified or on-account remittances.

Underlying Base Objects

The view text identifies four base objects, all referenced through APPS synonyms:

• AR_CASH_RECEIPTS_ALL — the primary transactional table storing cash receipt headers across all organizations. It supplies the cash receipt identifier, receipt number, document sequence value, receipt date, pay-from customer, and receipt method identifier.
• AR_RECEIPT_METHODS — the receipt method definition table, providing the receipt method name used to populate the RECEIPT_METHOD column.
• HZ_CUST_ACCOUNTS — the Trading Community Architecture customer account table, supplying the account number exposed as CUSTOMER_NUMBER.
• HZ_PARTIES — the TCA party table, supplying the party name exposed as CUSTOMER_NAME.

The join conditions are: CR.PAY_FROM_CUSTOMER = CA.CUST_ACCOUNT_ID(+) and CA.PARTY_ID = PTY.PARTY_ID(+) establish the customer and party relationships as outer joins, while CR.RECEIPT_METHOD_ID = ARM.RECEIPT_METHOD_ID is an inner join to the receipt method definition.

Key Columns

• CASH_RECEIPT_ID — Primary key of the receipt header in AR_CASH_RECEIPTS_ALL; the join key to distributions, applications, and adjustments.
• CUSTOMER_NAME — Party name of the paying customer, sourced from HZ_PARTIES.
• CUSTOMER_NUMBER — Customer account number from HZ_CUST_ACCOUNTS.
• RECEIPT_NUMBER — The user-visible receipt number.
• RECEIPT_DOCUMENT_NUMBER — The document sequence value assigned to the receipt.
• RECEIPT_CREATION_DATE — The receipt date recorded on the receipt header.
• RECEIPT_METHOD — The name of the receipt method, resolved from AR_RECEIPT_METHODS.

Common Use Cases and Queries

Typical scenarios include receipt method analysis, cash positioning, and reconciliation extracts.

• Listing all receipts by method for a period.
• Reporting receipt totals per customer.
• Feeding downstream reconciliation systems with receipt-level detail.

Example:

SELECT receipt_number, receipt_creation_date, customer_name, customer_number, receipt_method FROM apps.ar_cr_inf_v WHERE receipt_creation_date >= :from_date AND receipt_method = :method ORDER BY receipt_creation_date;