Search Results guarantee_amount




Overview
Explore in AI Chat

Overview

OKL_SO_PLAN_DETAILS_UV is a read-only view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKL – Leasing and Finance Management product family. Its documented purpose is to display Payment Plan details on screen, and it is a display-layer object originally defined in the ETRM 12.1.1 environment and carried forward into 12.2.2. The view consolidates data that is otherwise scattered across the OKC (Contracts) Core tables and OKL Leasing tables, resolving coded lookup values into user-facing meanings and joining translated contract line names to the rule groups that define a lease payment plan. Because the underlying contracts data model stores most of its business attributes as flexfield-style RULE_INFORMATIONn columns rather than discrete typed columns, this view exists primarily to transpose that generic structure into a conventional, readable columnar result set for Oracle Forms-based screens, concurrent programs, and ad hoc reporting. It does not itself perform any validation or update logic; all rows are derived.

Underlying Base Objects

The view is documented as referencing the following base objects through APPS synonyms and the FND foundation layer:

  • OKC_RULE_GROUPS_B and OKC_RULES_B — the contract rule group and rule tables. Each payment plan is a rule group of type SOPYSC, with three rule categories attached: SOPMSC (payment schedule / pricing), SOPSST (plan status), and SORVGT (residual value guarantee).
  • OKC_K_LINES_TL — the translated contract line table, supplying the plan name and joined on CLE_ID = CLET.ID with LANGUAGE = USERENV('LANG').
  • OKL_LS_RT_FCTR_SETS_B — the lease rate factor set (rate card) table, joined through TO_NUMBER(SOPMSC.RULE_INFORMATION2) = LRTV.ID using an outer join because the rate card is optional.
  • FND_LOOKUPS — joined twice to resolve OKL_PAYMENT_PLAN_STATUS and OKL_PRICING_METHOD codes into their meanings.
  • FND_GLOBAL — the package supplying session context such as the language in USERENV('LANG').

Efforts to trace the view definition should expect the single filter RGP.RGD_CODE = 'SOPYSC', which restricts the result set to sales-order-style payment plans only.

Key Columns

Common Use Cases and Queries

Typical usage includes diagnosing pricing method and status on a specific plan, listing all plans for a contract, and feeding downstream rate or residual value analysis.

  • Locate plans by pricing method: SELECT payment_plan_id, plan_name, pricing_method_code FROM okl_so_plan_details_uv WHERE pricing_method_code = 'FIXED';
  • Report all plans for one contract: SELECT plan_name, plan_status, rate, frequency_code FROM okl_so_plan_details_uv WHERE chr_id = :contract_id;
  • Join to OKC_K_HEADERS on chr_id to include contract number and customer, or to OKL_LS_RT_FCTR_SETS_B via rate_card_id for rate factor detail.

Because the view is read-only and performs several outer joins, filters on chr_id, payment_plan_id, or pricing_method_code should be applied whenever possible to keep query cost low.