Results for “receipt_number”

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

Overview

The CE_FC_ARR_DISC_V view is a Cash Management (CE) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, presentation-ready projection of Accounts Receivable receipts sourced from the CE_AR_FC_RECEIPTS_V view. The view joins receipt data to lookup meanings, receipt method names, and operating unit names to produce a human-readable listing of receipts together with their receipt method and organizational context. Because the underlying CE_AR_FC_RECEIPTS_V captures forecast, reconciled, or counterparty receipt information used in cash forecasting and reconciliation flows, this view functions primarily as a query surface for reporting, Oracle Discoverer workbooks, and custom integrations that need resolved descriptions rather than raw identifiers.

The object is documented as VALID with the owner APP. Its view text performs outer joins on the status lookup and operating unit so that receipts without a resolvable status code or organization are still returned.

Underlying Base Objects

The view text selects from four primary sources: CE_AR_FC_RECEIPTS_V (the driving receipt view), FND_LOOKUP_VALUES (lookup meanings for the RECEIPT_CREATION_STATUS lookup type), AR_RECEIPT_METHODS (receipt method name resolution), and HR_OPERATING_UNITS (operating unit name). The documented referenced base objects additionally list ARP_CASHBOOK, FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS packages alongside CE_SECURITY_PROFILES_V and the FND_LOOKUP_VALUES synonym. These security and utility packages support the data-access predicates in the view, notably the EXISTS clause against CE_SECURITY_PROFILES_V that restricts rows to operating units for which the current user holds security access.

Because the view references public synonyms such as AR_RECEIPT_METHODS and FND_LOOKUP_VALUES, it is intended to be queried from the APPS schema rather than from a base-product schema.

Key Columns

• REFERENCE_ID – Character representation of the source reference identifier, produced via TO_CHAR(SRC.REFERENCE_ID).
• RECEIPT_NUMBER – The receipt number from the source view.
• TRX_AMOUNT – The receipt amount, mapped from SRC.AMOUNT.
• BANK_ACCOUNT_AMOUNT – The base-currency amount, derived as NVL(SRC.BASE_AMOUNT, SRC.AMOUNT).
• STATUS – The lookup meaning for the receipt creation status, or NULL if no matching lookup row exists (outer join).
• RECEIPT_METHOD – The receipt method name from AR_RECEIPT_METHODS, matched on RECEIPT_METHOD_ID. This column is the target of the "receipt_method" search term and provides the descriptive method name rather than the numeric identifier.
• ORGANIZATION – The operating unit name from HR_OPERATING_UNITS, resolved via an outer join on ORG_ID.

Common Use Cases and Queries

The most common application is producing a readable receipt register filtered by receipt method, status, or organization. A typical query retrieves all receipts for a specific method:

SELECT receipt_number, trx_amount, bank_account_amount,
       status, receipt_method, organization
  FROM apps.ce_fc_arr_disc_v
 WHERE receipt_method = 'Wire';

Analysts also aggregate totals by method and organization to support cash forecasting and reconciliation reporting:

SELECT receipt_method, organization, SUM(trx_amount) total_amount
  FROM apps.ce_fc_arr_disc_v
 GROUP BY receipt_method, organization;

Because the view enforces operating unit security through CE_SECURITY_PROFILES_V, results are automatically limited to organizations accessible to the connecting user. Organizations running multiple operating units should therefore not expect a global receipt listing unless the user holds unrestricted security profile access.