Search Results ce_receipt_methods_v




Overview
Explore in AI Chat

Overview

CE_RECEIPT_METHODS_V is a concurrent-programmable view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the Cash Management (CE) product family and exposes the set of receipt methods that are available for use in Cash Management. Functionally, the view acts as a filtered, joined projection over Oracle Receivables receipt method and receipt class definitions, presenting only those methods whose receipt class meets specific business criteria.

The view is commonly used in reporting, integration, and lookup scenarios where a caller requires a validated list of payment methods that are genuinely usable in CE. Rather than querying the underlying Receivables tables directly, consumers reference this view because it pre-applies the eligibility filters that determine whether a receipt method is exposed in the Cash Management user interface and processing logic. The view is documented with STATUS = VALID and is registered under the APPS schema, making it accessible to standard EBS responsibility-based access patterns.

Underlying Base Objects

Per the ETRM metadata, CE_RECEIPT_METHODS_V is defined over two base objects, both exposed through APPS synonyms:

  • AR_RECEIPT_METHODS (synonym) — the primary table holding receipt method definitions, including name, receipt class association, and effective dating.
  • AR_RECEIPT_CLASSES (synonym) — the receipt class table, which supplies the creation status, creation method, and remittance method attributes that drive the view's filter.

The join is performed on RM.RECEIPT_CLASS_ID = RC.RECEIPT_CLASS_ID. The view applies two predicate filters against the receipt class: RC.CREATION_STATUS IN ('CLEARED','REMITTED','CONFIRMED') and RC.CREATION_METHOD_CODE IN ('MANUAL','AUTOMATIC'). Consequently, receipt methods attached to receipt classes outside these value sets are excluded entirely from the view output. This behaviour is central to the view's purpose: it does not present every receipt method defined in Receivables, only those whose class qualifies for Cash Management availability.

Key Columns

The view exposes nine columns, listed below with their derivation:

  • ROW_ID — the ROWID of the AR_RECEIPT_METHODS row, useful for row-level addressing.
  • NAME — the receipt method name (RM.NAME).
  • RECEIPT_CLASS_ID — the receipt class identifier linking the method to its class.
  • RECEIPT_METHOD_ID — the unique identifier of the receipt method.
  • START_DATE — the effective start date of the receipt method.
  • END_DATE — the effective end date of the receipt method.
  • REMIT_METHOD_CODE — the remittance method code from the receipt class.
  • CREATION_STATUS — the creation status of the receipt class, restricted to CLEARED, REMITTED, or CONFIRMED. This is the column most relevant to searches for "creation_status", since it governs the view's filtering logic.
  • CLASS_NAME — the descriptive name of the receipt class (RC.NAME).

Common Use Cases and Queries

Typical usage involves populating LOVs, validating inbound integration payloads, or reporting on the receipt methods available for remittance workflows. A straightforward listing of available methods is:

SELECT receipt_method_id, name, class_name, creation_status, remit_method_code FROM ce_receipt_methods_v ORDER BY name;

Because the view pre-filters by CREATION_STATUS, a query such as the following still returns only the permitted statuses, but makes the filter explicit for auditing purposes:

SELECT name, class_name, creation_status FROM ce_receipt_methods_v WHERE creation_status IN ('CLEARED','REMITTED','CONFIRMED');

Effective-dating analysis can filter on the date columns to identify currently active methods. Note that the view does not itself restrict by SYSDATE; consumers must add that predicate if current-validity is required.