Search Results okl_payment_structures

Overview

APPS.OKL_SO_PLAN_SUMMARY_UV is a reporting view within the Oracle Lease and Finance Management (OLFM) module of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. It consolidates payment plan header information originating from Oracle Contracts (OKC) rule structures and renders it in a business-friendly format by resolving internal lookup codes into descriptive meanings. The view exposes supplier-side payment plan data — the arrangement by which lease payments are structured, priced, and assigned a status — and is primarily intended for inquiry screens, concurrent reporting, and integration extracts rather than transactional processing.

The view is of particular interest to users searching on okl_payment_plan_status, because it surfaces the OKL_PAYMENT_PLAN_STATUS lookup meaning directly through its STATUS column. This allows implementers and report developers to retrieve plan status descriptions (for example, whether a plan is active, terminated, or pending) without writing their own joins to FND_LOOKUPS.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKC_RULE_GROUPS_B (synonym) — supplies the rule group header; the view filters on RGD_CODE = 'SOPYSC' and exposes CLE_ID as PAYMENT_PLAN_ID.
• OKC_RULES_B (synonym) — referenced three times, once each for the rule categories SOPMSC (plan master/setup), SOPAMT (payment amount), and SOPSST (plan status). These joins supply the descriptive codes stored in the RULE_INFORMATION1 through RULE_INFORMATION9 columns.
• OKL_LS_RT_FCTR_SETS_B (synonym) — outer-joined to provide the rate factor set name (LRTV.NAME) for pricing method 'RC'.
• FND_LOOKUPS (view) — joined four times to decode lookup codes against lookup types OKL_PRICING_METHOD, OKL_BOOK_CLASS, OKL_PAYMENT_PLAN_STATUS, and OKL_PAYMENT_STRUCTURES.
• FND_GLOBAL (package) — referenced for session context (for example, org or user identifiers) used by dependent reporting logic.

Because the view sits above the OKC rule framework, it inherits the flexibility of the rule model: payment plan attributes are stored generically in RULE_INFORMATION1–9 columns rather than as discrete table columns, which is why the view performs multiple self-joins to pivot these attributes into named columns.

Key Columns

• PAYMENT_PLAN_ID — the CLE_ID of the SOPYSC rule group; uniquely identifies the payment plan.
• CHR_ID — the contract/header identifier (DNZ_CHR_ID) to which the plan belongs.
• NAME — the plan name, formed as the pricing method meaning concatenated with either the rate factor set name (for method 'RC') or the value in RULE_INFORMATION7.
• BOOK_CLASS — decoded from RULE_INFORMATION9 against OKL_BOOK_CLASS; indicates the accounting book classification of the plan.
• PAYMENT — sourced from SOPAMT.RULE_INFORMATION5; represents the payment amount or frequency attribute of the plan.
• STATUS — the decoded OKL_PAYMENT_PLAN_STATUS meaning, derived from SOPSST.RULE_INFORMATION1. This is the column that answers the "okl_payment_plan_status" search.
• PAYMENT_STRUCTURE — decoded from SOPMSC.RULE_INFORMATION3 against OKL_PAYMENT_STRUCTURES; describes the payment structure type (for example, level or stepped).

Common Use Cases and Queries

Typical scenarios include listing all payment plans for a contract, auditing plan status distribution, and building extracts for downstream finance or treasury systems.

SELECT payment_plan_id, chr_id, name, book_class,
       payment, status, payment_structure
  FROM apps.okl_so_plan_summary_uv
 WHERE chr_id = :p_chr_id;

SELECT status, COUNT(*)
  FROM apps.okl_so_plan_summary_uv
 GROUP BY status;

The second query is frequently used to report on the OKL_PAYMENT_PLAN_STATUS lookup values actually in use. Because the view decodes all lookup codes, it removes the need for consumers to replicate joins to FND_LOOKUPS, making it suitable for both ad hoc inquiry and published reporting layers.