Results for “slh_id”

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

Overview

OKL_LA_PAYMENTS_SUMMARY_UV is a user interface view owned by the APPS schema within the OKL - Lease and Finance Management product family. It is documented in ETRM as the "User interface view for Payment Summary Page," meaning it is a presentation-layer object consumed by the Oracle Lease and Finance Management application to render the Payment Summary page rather than a standalone reporting entity. The view is defined as the UNION ALL of several branches, each assembling a normalized row set describing lease payment structures across different contract configurations.

The view is part of a broader family of leasing views (OKC_K_LINES_V, OKC_LINE_STYLES_V, OKL_STRMTYP_SOURCE_V) and exposes a consistent column projection across its UNION branches. Because it is a UI view, it is typically accessed through the OKL application pages rather than directly by end users. The user's search term, "okc_line_styles_v," appears in the view text: OKC_LINE_STYLES_V is cited in the second UNION branch as JOINed through LS.LTY_CODE = 'FREE_FORM1'. Both OKC_LINE_STYLES_V and OKC_LINE_STYLES_B are documented as referenced base objects of this view.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced objects: OKC_K_HEADERS_B (synonym), OKC_K_ITEMS (synonym), OKC_K_LINES_B (synonym), OKC_K_LINES_V (view), OKC_LINE_STYLES_B (synonym), OKC_LINE_STYLES_V (view), OKC_RULES_B (synonym), OKC_RULE_GROUPS_B (synonym), OKC_STATUSES_B (synonym), OKL_STRMTYP_SOURCE_V (view), and OKX_SYSTEM_ITEMS_V (view). In the view text, the first and second UNION branches join OKC_K_HEADERS_B (alias K), OKC_RULE_GROUPS_B (RG), OKC_RULES_B (RUL), OKL_STRMTYP_SOURCE_V (STRM), and OKC_STATUSES_B (STS). The second branch additionally joins OKC_K_LINES_V (KL) and OKC_LINE_STYLES_V (LS). Filtering restricts rows to RG.RGD_CODE = 'LALEVL' and RUL.RULE_INFORMATION_CATEGORY = 'LASLH', and status codes are filtered to exclude CANCELLED streams or lines.

The view therefore sits above the OKC contract/rule/line transactional tables and derives lease payment hierarchy data from lease-level rule groups and rule lines, tying them back to the contract header and stream type.

Key Columns

• CHR_ID and CONTRACT_NUMBER — the contract header identifier and its human-readable contract number from OKC_K_HEADERS_B.
• SERVICE_FEE_NAME and SERVICE_FEE_ID — the service fee label and identifier associated with the row's contract line.
• ASSET_NAME and ASSET_DESC — descriptive attributes for the leased asset (from OKC_K_LINES_V in the second branch).
• STREAM_NAME, STREAM_ID, STREAM_CODE — the payment stream type derived from OKL_STRMTYP_SOURCE_V via RUL.OBJECT1_ID1 = STRM.ID1.
• RULE_GROUP_ID and SLH_ID — the rule group identifier and the specific rule line identifier (OKC_RULES_B.ID) that drive the payment summary.
• TOP_LINE_LSE_ID, TOP_LINE_LTY_CODE, TOP_LINE_LSE_NAME — the top line lease identifier, its line type code, and description.
• SEQUENCE_NUM — a discriminator distinguishing the UNION branches (for example, 6 for the header-level branch and 1 for the line-level branch), used for consistent ordering on the UI page.

Common Use Cases and Queries

The primary use case is supporting the Payment Summary page, where the application displays payment streams and their associated rules for a lease contract. Developers and technical consultants also query it for diagnostics, especially when investigating how line styles (OKC_LINE_STYLES_V) map to payment structures.

To list payment summary rows for a contract:

SELECT contract_number, stream_name, stream_code,
       rule_group_id, slh_id, sequence_num
  FROM apps.okl_la_payments_summary_uv
 WHERE contract_number = 'YOUR_CONTRACT'
 ORDER BY sequence_num;

To inspect only line-level (fine form) rows, filter on the sequence column:

SELECT contract_number, asset_name, stream_code, top_line_lty_code
  FROM apps.okl_la_payments_summary_uv
 WHERE sequence_num = 1;

To join back to line styles and confirm which style each line uses, reference OKC_LINE_STYLES_V on TOP_LINE_LTY_CODE, mirroring the internal JOIN on LS.LTY_CODE = 'FREE_FORM1'. Because the object is a view, no DML may be issued against it; INSERT, UPDATE, or DELETE operations must target the underlying base tables.