Results for “paymt_rule_id”

8 results




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

Overview

OKL_SO_PAYMENT_SCEN_UV is a PL/SQL view owned by the APPS schema within the Oracle Leasing and Finance Management (OKL) module, part of Oracle E-Business Suite. The suffix "UV" denotes a user-facing validation or reporting view. The view consolidates payment scenario rule definitions associated with a lease or contract, deriving its data primarily from the OKC rule framework used to model contract terms and conditions.

It exposes payment amounts, payment methods, and payment plan statuses, presenting each as descriptive lookup meanings rather than raw coded values. Because the view decodes identifiers into human-readable text, it is well suited for reporting, data extraction, and integration scenarios that require a flattened, readable representation of payment scenarios. The object is documented as VALID in the ETRM repository and is intended for reference and query purposes rather than direct DML.

Underlying Base Objects

The view is defined over the following documented base objects:

  • OKC_RULES_B (SYNONYM) — the base table storing individual contract rules. It appears three times as aliases SOPAMT, SOPSST, and SOPMSC, each filtered by a distinct RULE_INFORMATION_CATEGORY ('SOPAMT', 'SOPSST', 'SOPMSC').
  • OKC_RULE_GROUPS_B (SYNONYM) — the rule group header table, aliased RGP. Rows are restricted to RGD_CODE = 'SOPYSC', identifying the payment scenario group.
  • FND_LOOKUPS (VIEW) — joined twice, as METHOD and STATUS, to translate coded values into lookup meanings.
  • FND_GLOBAL (PACKAGE) — referenced as a standard dependency, typically for session/context values.
  • OKC_RULES_V (VIEW) — a documented related view over the same rule data.

The joins establish that a single payment scenario (RGP_ID) links three rules of differing categories — the amount rule, the status rule, and the method/scheme rule — plus a method lookup derived from SOPMSC.RULE_INFORMATION1.

Key Columns

  • RGP_ID — identifier of the payment scenario rule group.
  • LINE_ID (CLE_ID) — the contract line to which the scenario applies.
  • AMT_RULE_ID / PAYMT_RULE_ID — both return SOPAMT.ID, the payment amount rule identifier.
  • STATUS_RULE_ID — the payment plan status rule identifier (SOPSST.ID).
  • DNZ_CHR_ID — the contract header identifier carried from the rule group.
  • AMOUNT — the payment amount, sourced from SOPAMT.RULE_INFORMATION5.
  • STATUS — decoded payment plan status from OKL_PAYMENT_PLAN_STATUS lookup.
  • METHOD — decoded pricing/payment method from OKL_PRICING_METHOD lookup.
  • TERM, ARREARS, START_DATE — currently return NULL and are reserved placeholders.

Common Use Cases and Queries

Typical uses include reporting all payment scenarios for a contract, validating that a payment method and status are assigned, and feeding downstream integration extracts. A representative query by contract line follows:

SELECT rgp_id, line_id, amount, status, method FROM apps.okl_so_payment_scen_uv WHERE dnz_chr_id = :contract_id;

To list all scenarios with their decoded attributes:

SELECT line_id, amount, status, method FROM apps.okl_so_payment_scen_uv ORDER BY line_id;

Because TERM, ARREARS, and START_DATE are NULL placeholders, consumers should not rely on those columns for functional logic.