Search Results okl_terms_conds

Overview

APPS.OKL_TERMS_AND_COND_UV is a union-based reporting view in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. It exposes configuration metadata used by the Terms and Conditions setup and rendering framework, which drives the display of lease and loan attribute pages within the OKL user interface. Rather than storing transactional data, the view materialises a curated set of lookup-driven definitions that pair a rule group with the associated rule sequence, page title, region, and navigation token.

Its principal role is to provide a single, ordered dictionary of the rule groups that govern how Terms and Conditions pages are assembled. Each row corresponds to a specific lookup code in the OKL_TC_LINKS lookup type, and the view decorates that lookup with technical attributes used by the OKL run-time engine and by diagnostic or integration reporting. Because it references FND_LOOKUPS, its content is highly configurable and non-static: changing a lookup meaning or description in the application propagates immediately into the view output.

The column RULE_SEQUENCE, which prompted the user's search, is central to the view's purpose. It encodes the ordered chain of rule identifiers that must be executed or rendered for a given group, using a pipe-delimited parent-child notation.

Underlying Base Objects

The documented base objects referenced by this view are FND_LOOKUPS (a view) and FND_GLOBAL (a package). The defining SQL comprises a series of SELECT ... UNION branches, each selecting from FND_LOOKUPS filtered by LOOKUP_TYPE = 'OKL_TC_LINKS' and a specific LOOKUP_CODE. Each branch contributes a row keyed by a literal SEQ_NO (1 through 5 and beyond in the excerpt).

FND_GLOBAL is referenced to supply session context such as the current user, responsibility, and application, which is the standard mechanism for securing or scoping EBS reporting views. The view does not join to OKL transaction tables directly; instead it decouples presentation metadata from the underlying lookup definitions.

Key Columns

• SEQ_NO — A literal ordering value assigned per union branch, controlling the sequence in which groups appear.
• GROUP_TITLE — The lookup meaning (FND.MEANING); the human-readable group heading.
• DESCRIPTION — The lookup description (FND.DESCRIPTION), providing explanatory text.
• RULE_GROUP — The logical group identifier, e.g. LABILL, LALCGR|LALIGR, LARNOP, LARVIN.
• RULE_SEQUENCE — The ordered, pipe-delimited chain of rule identifiers, e.g. LABILL-LAPMTH|LABILL-LABACC|LABILL-LAINVD. Null where a group has no defined sequence.
• TITLE_STYLE — Either SINGLE or GROUP, indicating presentation behaviour.
• PAGETITLE / REGION — Target page (OKL_TERMS_CONDS) and region (OKL_TC_ATTRIBUTES).
• CURRENCY / DISABLED — Flags (YES/NO) controlling currency sensitivity and whether the group is inactive.
• TOKEN — The navigation token, e.g. OKLLABILLINGSETUPLABILL.

Common Use Cases and Queries

Typical uses include auditing the Terms and Conditions rule configuration, verifying rule sequences for a given group, and diagnosing rendering or navigation issues. The following query returns all groups and their sequences in display order:

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

To inspect groups that actually define a rule sequence (excluding those with a null sequence):

SELECT rule_group, rule_sequence
FROM   apps.okl_terms_and_cond_uv
WHERE  rule_sequence IS NOT NULL;

To locate the group governing a specific billing rule such as LAPMTH:

SELECT group_title, rule_group, rule_sequence
FROM   apps.okl_terms_and_cond_uv
WHERE  rule_sequence LIKE '%LAPMTH%';

These queries are commonly executed under an APPS responsibility or in a read-only reporting schema, since the view depends on FND_GLOBAL for session context.