Results for “payment_method_code”

50+ results




Overview
Explore in AI Chat

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

Overview

OKL_BPD_PAYMENT_METHODS_V is a lightweight, APPS-owned database view within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Leasing and Finance Management (OKL) product family. It exposes the set of currently valid payment method codes available for use in leasing and finance transactions, presenting them through a single, denormalized column named PAYMENT_METHOD_CODE. The view is read-only by design and surfaces only those payment methods that are both enabled and not past their end-date-of-activity, making it a convenient, always-current source for reporting, integration, and validation logic without requiring callers to understand the underlying lookup architecture.

Because it distills the FND_LOOKUPS lookup type OKL_PAYMENT_METHODS into a minimal result set, the view is frequently used as a reference (or "list of values" style) source for downstream processes, custom reports, and interface programs that must present or validate the payment methods a lease or financed contract may adopt. Its role is not to store transactional data but to publish configuration metadata in a consumable form.

Underlying Base Objects

The view is defined over the FND_LOOKUPS view, which in turn is based on the FND application's lookup tables that store configurable code lists. The documented view text restates the essential logic:

The WHERE clause constrains results to the OKL_PAYMENT_METHODS lookup type, filters to enabled lookups, and excludes any lookup whose end-date-of-activity has passed (treating a null end date as open-ended). Referenced metadata also notes the FND_GLOBAL package as a related base object, typically associated with session context functions such as the current SYSDATE environment. In practice, the operational dependency of the view is the set of payment method lookup values maintained through the application's lookup maintenance forms.

Key Columns

The view projects a single column:

  • PAYMENT_METHOD_CODE — The lookup code from the OKL_PAYMENT_METHODS lookup type, representing a valid payment method identifier (for example, a code signifying check, wire, or other configured settlement method). This value is the technical code used in transaction records; the corresponding descriptive meaning is stored on the same lookup row in FND_LOOKUPS but is not exposed by this view.

Because only the code is returned, callers that require the human-readable description must join back to FND_LOOKUPS (or the related TL/interface views) on LOOKUP_TYPE = 'OKL_PAYMENT_METHODS' and LOOKUP_CODE = PAYMENT_METHOD_CODE.

Common Use Cases and Queries

The view is most often consumed to populate selection lists, validate user or interface input, and drive conditional business logic in custom extensions. A typical query is simply:

  • SELECT PAYMENT_METHOD_CODE FROM APPS.OKL_BPD_PAYMENT_METHODS_V;

To confirm a specific method is currently valid before processing a contract, a developer might issue:

  • SELECT PAYMENT_METHOD_CODE FROM APPS.OKL_BPD_PAYMENT_METHODS_V WHERE PAYMENT_METHOD_CODE = :p_method;

When the descriptive name is required, the view is joined to the lookup definition, for example joining FND_LOOKUPS on LOOKUP_TYPE = 'OKL_PAYMENT_METHODS' to retrieve MEANING or DESCRIPTION alongside the code. Because the view already applies enablement and end-date filtering, embedding it in these joins guarantees that superseded or disabled methods are automatically excluded, reducing the need to replicate that logic in every caller.

In summary, OKL_BPD_PAYMENT_METHODS_V provides a simple, filtered, and authoritative listing of active OKL payment method codes, and it is best treated as a configuration reference view rather than a transactional data source.