Results for “creation_method_code”

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

Overview

AR_CASH_RECEIPTS_V is a valid APPS-owned view in the Oracle E-Business Suite Receivables (AR) module. Its documented purpose is explicit: it serves as the base table view for the Receipts window, and the embedded view comment states that it "is used in the Receipts Gateway as the basetable for the Receipts Form." In practical terms, this view is the presentation layer through which the Receipts form and related reporting extract receipt header information, joining the transaction-level receipt record to its current history row, receipt method, receipt class, bank, and customer attributes.

Because the view exposes descriptive decoded values in addition to raw IDs — for example lookup meanings for receipt status and conversion-type descriptions — it is widely used in custom reports, concurrent programs, and integration extracts where a denormalized, ready-to-read receipt record is required without replicating the Receipts form's complex join logic.

Underlying Base Objects

The view is defined over a substantial set of base objects. The principal driving tables are the AR_CASH_RECEIPTS synonym (aliased CR) and AR_CASH_RECEIPT_HISTORY_ALL (aliased CRH_CURRENT), which supplies the ACCTD_AMOUNT and current receipt amount. Descriptive context comes from AR_RECEIPT_METHODS, AR_RECEIPT_CLASSES, AR_BATCHES_ALL, and AR_RECEIVABLES_TRX_ALL, while disbursement and distribution relationships draw on AR_PAYMENT_SCHEDULES_ALL, AR_MISC_CASH_DIST, and AR_DISTRIBUTION_SETS_ALL.

Bank and customer information is sourced through CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_OU, CE_BANK_BRANCHES_V, IBY_EXT_BANK_ACCOUNTS_V, and CE_BANK_AND_ACCOUNT_UTIL. Trading-party attributes come from HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, and HZ_RELATIONSHIPS. Currency and tax context is provided by GL_DAILY_CONVERSION_TYPES, ZX_ACCOUNTS, and ZX_RATES_B. The ARPT_SQL_FUNC_UTIL package supplies lookup-decoding functions used directly in the SELECT list, and AR_LOOKUPS supplies the lookup view. Note that most AR and general-ledger objects are referenced through synonyms owned by APPS.

Key Columns

• CASH_RECEIPT_ID / ROW_ID — primary key and row identifier for the receipt record.
• CASH_RECEIPT_HISTORY_ID — current history row, the source of functional and net amounts.
• AMOUNT, NET_AMOUNT, FUNCTIONAL_AMOUNT — entered, net, and accounted receipt amounts.
• RECEIPT_NUMBER, RECEIPT_DATE — receipt identifier and accounting-relevant date.
• TYPE, RECEIPT_STATUS, RECEIPT_STATUS_DSP — receipt type, status code and decoded status meaning via ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING('CHECK_STATUS', CR.STATUS).
• BILL_OF_EXCHANGE_FLAG — sourced from RC.BILL_OF_EXCHANGE_FLAG on AR_RECEIPT_CLASSES, indicating whether the receipt class represents a bill of exchange.
• CREATION_METHOD_CODE, CREATION_METHOD_DSP — automatic, manual or remittance creation method and its decoded description.
• EXCHANGE_RATE, EXCHANGE_RATE_DATE, EXCHANGE_RATE_TYPE, EXCHANGE_RATE_TYPE_DSP — currency conversion attributes drawn with GL_DAILY_CONVERSION_TYPES.
• CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER, TAXPAYER_ID — payer identity derived from HZ_PARTIES and HZ_CUST_ACCOUNTS.
• MISC_PAYMENT_SOURCE, COMMENTS, DOCUMENT_NUMBER, USSGL_TRANSACTION_CODE — subsidiary reference and reporting attributes.

Common Use Cases and Queries

Typical usage includes receipt register reports, bank reconciliation feeds, treasury extracts, and reconciliation of receipt amounts to customer balances. Because BILL_OF_EXCHANGE_FLAG was the searched term, the following query returns all receipts for a given customer whose receipt class is flagged as a bill of exchange:

• SELECT cash_receipt_id, receipt_number, receipt_date, amount, currency_code, bill_of_exchange_flag FROM ar_cash_receipts_v WHERE customer_id = :p_customer_id AND bill_of_exchange_flag = 'Y' AND receipt_date BETWEEN :p_from AND :p_to;
• SELECT bill_of_exchange_flag, creation_method_dsp, COUNT(*), SUM(functional_amount) FROM ar_cash_receipts_v GROUP BY bill_of_exchange_flag, creation_method_dsp;

All queries should be filtered on receipt_status and receipt_date to limit the join cost over AR_CASH_RECEIPT_HISTORY_ALL and the HZ and CE objects.