Search Results okl_pricing_method




Overview
Explore in AI Chat

Overview

APPS.OKL_SO_PAYMENT_SCEN_UV is a reporting and integration view within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. It exposes the payment scenario configuration associated with lease and loan contracts, consolidating amount, status, and payment rules that belong to a single rule group. The view derives its name from its business purpose: presenting the payment scenario (SOPYSC, or "Sales Order Payment Scenario") defined at the contract level. Rather than requiring downstream applications to join the generic rules engine tables directly, this view flattens the contract rule model into a single denormalized rowset, which makes it suitable for concurrent program extraction, business intelligence reporting, and interface development. Because it is an underscored "UV" (user view) object, it is intended for query-only access and should not be used as a DML target. The view is documented as stable across EBS 12.1.1 and 12.2.2, with the referenced base objects resolving through synonyms and view layers in both releases.

Underlying Base Objects

The view is defined over four referenced objects. OKC_RULE_GROUPS_B is the base table that anchors each rule group; the view aliases it as RGP and filters on RGD_CODE = 'SOPYSC' to isolate payment-scenario rule groups. OKC_RULES_V is a rules view that supplies the individual rule entries; it appears three times in the join, aliased RLEA, RLEB, and RLEC, each constrained by a distinct RULE_INFORMATION_CATEGORY: SOPAMT for amount, SOPSST for status, and SOPMSC for miscellaneous payment attributes. FND_LOOKUPS is the standard Oracle Application Object Library lookup view, joined here on LOOKUP_TYPE = 'OKL_PRICING_METHOD' to translate the stored lookup code into a human-readable meaning. FND_GLOBAL is listed as a referenced package, consistent with the runtime context established by the flexfield and rules engine. The view therefore acts as a semantic bridge between the contract rules engine and the presentation layer.

Key Columns

  • RGP_ID — Primary identifier of the rule group row in OKC_RULE_GROUPS_B.
  • LINE_ID — Foreign key to the contract line (CLE_ID) to which the payment scenario applies.
  • DNZ_CHR_ID — The contract header identifier that owns the rule group.
  • AMT_RULE_ID / STATUS_RULE_ID / PAYMT_RULE_ID — Surrogate keys to the individual amount, status, and payment rules.
  • AMOUNT — Rule information 1 from the amount rule, representing the monetary amount for the scenario.
  • STATUS — Rule information 1 from the status rule, indicating the lifecycle or processing state.
  • TERM, ARREARS, START_DATE — Payment-term related attributes read from rule information positions 5, 4, and 11 of the miscellaneous rule.
  • METHOD — The decoded lookup meaning for the pricing method (lookup type OKL_PRICING_METHOD), which resolves the user's search term to this column.

Common Use Cases and Queries

Typical usage includes reporting payment scenarios for a contract, validating pricing method assignment, and feeding integrations that must reproduce contract payment terms. The following query illustrates retrieval by contract line, using the METHOD column that resolves the OKL_PRICING_METHOD lookup.

  • SQL: SELECT rgp_id, line_id, amount, status, term, arrears, start_date, method FROM apps.okl_so_payment_scen_uv WHERE line_id = :p_line_id;
  • Filter by pricing method: SELECT line_id, term, method FROM apps.okl_so_payment_scen_uv WHERE method = 'Advance';
  • Aggregate exposure by method: SELECT method, COUNT(*), SUM(amount) FROM apps.okl_so_payment_scen_uv GROUP BY method;

Because the view relies on OKC_RULES_V for its rule data, query performance is improved when predicates on DNZ_CHR_ID or LINE_ID are supplied, allowing the rules engine joins to be pruned. The view should be treated as read-only in all query and integration scenarios.