Search Results receipt_class_name




Overview
Explore in AI Chat

Overview

OKL_BPD_RCPT_MTHDS_UV is a read-only view owned by the APPS schema within the OKL (Leasing and Finance Management) product family. It presents a filtered, denormalized list of receipt methods that are eligible for use against bank accounts within Oracle Receivables and Oracle Leasing workflows. In essence, it resolves the intersection between receipt methods, receipt classes, and internal bank account uses, and exposes that combined data as a single flattened row set.

The view is not a substitute for the underlying AR and CE setup tables; rather it is a convenience access point intended for LOV (List of Values) queries, concurrent report data sources, and integration lookups where a caller needs to know which receipt methods map to which bank accounts under the current organization context. Because it embeds a call to MO_GLOBAL.CHECK_ACCESS, it is multi-org aware and returns only rows belonging to organizations the current session is permitted to see.

Underlying Base Objects

The view is defined over seven underlying objects, six of which are synonyms to base tables and two of which are database programs:

Key Columns

The view exposes a mixture of identifiers, descriptive attributes, and derived values:

Common Use Cases and Queries

The most frequent use of this view is to populate receipt method and bank account selections for receipts entered against leases. A typical query filters by receipt method name and organization:

  • SELECT receipt_method_name, bank_account_num, bank_name, remit_flag FROM okl_bpd_rcpt_mths_uv WHERE org_id = :p_org_id ORDER BY receipt_method_name;
  • SELECT receipt_method_id, receipt_method_name FROM okl_bpd_rcpt_mths_uv WHERE remit_flag = 'Y' AND rownum < 100;
  • SELECT DISTINCT bank_account_id, bank_account_num, currency_code FROM okl_bpd_rcpt_mths_uv WHERE receipt_method_id = :p_method_id;

Because the view already applies SYSDATE-based filtering on receipt method and bank account use effective dates, callers do not need to add their own date predicates. The embedded exclusion of receipt classes with NOTES_RECEIVABLE or BILL_OF_EXCHANGE_FLAG set to Y means those classes will never appear, which is important when reconciling against AR_RECEIPT_CLASSES directly.