Results for “trn_code”

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

Overview

OKL_VP_TERMINATION_REASON_UV is an APPS-owned database view in the Oracle Lease and Finance Management (OKL) product family, delivered in Oracle E-Business Suite 12.1.1 and 12.2.2. The suffix "UV" denotes a user-facing validation view, which in the ETRM (Applications Technology) naming convention signals that the object is intended for use as a List of Values (LOV) source or as a lookup validation reference within Oracle Forms and OAF-based pages. The view presents a curated, bilingual-filtered list of lease termination reasons, exposing only the subset of lookup codes that Oracle Lease and Finance Management considers valid for termination processing.

The view is essentially a thin, purpose-built projection over the FND_LOOKUP_VALUES and FND_LOOKUP_TYPES tables, restricted to the lookup type OKC_TERMINATION_REASON. It serves as the authoritative runtime source for populating termination reason LOVs in lease termination workflows, contracts, and reporting queries. Because it applies ENABLED_FLAG, date-range, language, and security-group filtering, it returns only currently effective lookup values for the session user's language and security context.

Underlying Base Objects

The view is defined over the following documented base objects:

• FND_LOOKUP_TYPES (synonym in APPS) — supplies the lookup type metadata and security group alignment.
• FND_LOOKUP_VALUES (synonym in APPS) — supplies the individual lookup codes, meanings, effective dates, and enabled flag.
• FND_GLOBAL (package) — invoked via FND_GLOBAL.LOOKUP_SECURITY_GROUP to enforce lookup-level security, and indirectly via USERENV('LANG') for language filtering.

Joins are performed on LOOKUP_TYPE, SECURITY_GROUP_ID, and VIEW_APPLICATION_ID across the two FND tables, ensuring the type and value rows belong to the same lookup configuration. Additional predicates restrict the result set to ENABLED_FLAG = 'Y', NVL(START_DATE_ACTIVE, SYSDATE) <= SYSDATE, and NVL(END_DATE_ACTIVE, SYSDATE) >= SYSDATE, guaranteeing that only active, currently effective values are returned.

Key Columns

• TRN_CODE — Aliased from FLV.LOOKUP_CODE. The stored termination reason code. The view hard-codes the allowed set to 'DEF', 'MUA', 'OOB', 'EOT', 'CTY', 'OBS', 'REF', corresponding to standard lease termination scenarios such as default, mutual agreement, out-of-business, end-of-term, early termination, obsolescence, and refinance.
• TERMINATION_REASON — Aliased from FLV.MEANING. The translatable user-facing description of the termination reason, resolved to the session language through the ENABLED/date filters.

Only these two columns are exposed. All other lookup attributes (description, tag, attribute columns, effective dates) are suppressed to present a minimal LOV surface.

Common Use Cases and Queries

The view is typically consumed by Oracle Forms LOVs, OAF region lookups, and custom reports that need the standard lease termination reason set without re-implementing the underlying lookup join logic. Users searching for "trn_code" are usually inspecting a value returned from this view — for example, to map a stored TRN_CODE back to its meaning, or to validate which codes the application permits.

A representative query:

SELECT trn_code, termination_reason
FROM   apps.okl_vp_termination_reason_uv
ORDER  BY termination_reason;

To resolve a stored code:

SELECT termination_reason
FROM   apps.okl_vp_termination_reason_uv
WHERE  trn_code = :trn_code;

To enumerate the supported termination basis:

SELECT trn_code
FROM   apps.okl_vp_termination_reason_uv;

Because only the seven hard-coded codes are exposed, any value in a lease termination record outside that set will not resolve through this view and must be joined against FND_LOOKUP_VALUES directly. This constraint makes the view suitable for validation and LOV rendering but unsuitable for historical lookups if the effective date window has expired.