Results for “okl_terms_and_cond_uv”

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

Overview

OKL_TERMS_AND_COND_UV is a user interface view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL product family — Oracle Lease and Finance Management — and is documented as the "User Interface View for Contracts terms and conditions summary page." Its purpose is to present the header-level navigational structure of the Terms and Conditions page (function OKL_TERMS_CONDS), driving the display of links, group titles, and rule navigation for the contract terms and conditions maintenance flow. Rather than storing transactional contract data, the view exposes a static, UNION-generated result set that models the page layout as a set of link rows, each identified by a sequence number and a token.

The view is a presentation-layer construct. It does not join to contract tables; instead it builds one row per navigation link and pulls its display text from FND_LOOKUPS, keyed on lookup type OKL_TC_LINKS. This design isolates the page layout from the underlying OKL rule/attribute data model, allowing the layout to be extended through lookup maintenance rather than code changes.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the referenced base objects are:

• FND_LOOKUPS (VIEW) — the primary data source. Every row in OKL_TERMS_AND_COND_UV is produced by a SELECT from FND_LOOKUPS, filtered on LOOKUP_TYPE = 'OKL_TC_LINKS' and a specific LOOKUP_CODE. The lookup MEANING supplies GROUP_TITLE and the lookup DESCRIPTION supplies DESCRIPTION.
• FND_GLOBAL (PACKAGE) — referenced by the view definition (typically through FND_GLOBAL and related session/context calls used in Oracle EBS UI views); it supplies runtime application/user context rather than row data.

No OKL contract tables are referenced directly. The UNION of SELECT statements against FND_LOOKUPS produces the fixed set of link rows (SEQ_NO 1 through 5 and beyond in the full view text), each corresponding to a lookup code such as OKLLABILLINGSETUPLABILL, OKLLARULEGROUPSLALCGR, OKLLARULEGROUPSLARNOP, OKLLARULESLASDEP, and OKLLARULESLARVIN.

Key Columns

• SEQ_NO — Hard-coded sequence number assigned per UNION branch; controls the display or processing order of the terms and conditions links.
• GROUP_TITLE — Taken from FND_LOOKUPS.MEANING; the group heading shown on the summary page.
• DESCRIPTION — Taken from FND_LOOKUPS.DESCRIPTION; the descriptive text for the link.
• RULE_GROUP — Pipe-delimited list of rule group codes associated with the link (for example 'LABILL' or 'LALCGR|LALIGR'), used to scope which rule groups the page section manages.
• RULE_SEQUENCE — The column most relevant to the search term "rule_sequence." It is a pipe-delimited string of rule-to-sequence mappings, e.g. 'LABILL-LAPMTH|LABILL-LABACC|LABILL-LAINVD|LABILL-LAINPR' or 'LASDEP-LASDEP|LAFCTG-LAFCTG|LAEVEL-LAEVEL|LAEVEL-LAEVPT|LAPREF-LAIVAR'. Each pair encodes a rule group code and its rule code, defining the ordered set of rules rendered under that group. Several rows return NULL for this column.
• TITLE_STYLE — 'SINGLE' or 'GROUP'; determines whether the section title is rendered as a single heading or as a grouping header.
• PAGETITLE — Constant 'OKL_TERMS_CONDS', the target page for all rows.
• REGION — Constant 'OKL_TC_ATTRIBUTES', the region into which the link renders.
• CURRENCY and DISABLED — Flags ('YES'/'NO') indicating whether a currency context applies and whether the link is disabled.
• TOKEN — Unique navigation token per link (for example 'OKLLABILLINGSETUPLABILL'), used by the OA Framework page to identify the link target.

Common Use Cases and Queries

Typical uses include diagnosing why a Terms and Conditions link is missing or rendered with unexpected labels (trace the offending row back to its OKL_TC_LINKS lookup entry), auditing the rule_sequence mappings that drive which rules appear under a given group, and extending the page by inserting new lookup codes. A representative query lists the navigation structure in display order:

SELECT seq_no, group_title, rule_group, rule_sequence, title_style, token
FROM  apps.okl_terms_and_cond_uv
ORDER BY seq_no;

To isolate the rule_sequence mappings for a single group, filter on the delimiter pattern; for example, to find all rows that sequence the LASDEP rule group:

SELECT seq_no, group_title, rule_group, rule_sequence
FROM  apps.okl_terms_and_cond_uv
WHERE  rule_sequence LIKE 'LASDEP-%';

To cross-check the view against its source lookup, join on the lookup code:

SELECT v.seq_no, v.group_title, v.token, f.lookup_code
FROM  apps.okl_terms_and_cond_uv v,
      apps.fnd_lookups f
WHERE  f.lookup_type = 'OKL_TC_LINKS'
  AND  f.lookup_code = v.token
ORDER BY v.seq_no;

Because the view is not contract-specific, it should not be used to report on individual lease terms. It is best treated as configuration and layout metadata: any change to labels, ordering, or rule sequencing belongs in the OKL_TC_LINKS lookup values, which the view will reflect on the next page render.