Results for “rle_code”

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

Overview

OKL_CONTACT_ROLE_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL - Lease and Finance Management product family. It exposes a filtered, presentation-ready projection of contact role assignments sourced from the OKC contact infrastructure. The view's central purpose is to translate the internal contact role code (CRO_CODE) into a human-readable meaning using the OKL_ACCOUNTING_UTIL package, while simultaneously restricting the result set to records that are currently effective based on their date range. This makes it a convenient reporting and integration surface for lease and finance inquiries that need to resolve contact roles without embedding lookup logic directly in application SQL.

In the architecture of Oracle EBS 12.1.1 and 12.2.2, the view behaves as a lightweight semantic layer over the OKC_CONTACT_SOURCES synonym. Because the view is marked VALID in the data dictionary, it is safe to reference from custom reports, Oracle Discoverer workbooks, BI Publisher data templates, and inbound/outbound interfaces that operate against APPS objects. The presence of a BUY_OR_SELL column is significant for users searching on that term, since it allows the same view to distinguish buyer-side and seller-side contact roles within leasing and finance transactions.

Underlying Base Objects

The view is defined over two documented referenced objects:

• OKC_CONTACT_SOURCES (synonym) — the principal source of contact role data. Its columns feed the view's MEANING derivation, LOOKUP_CODE, JTOT_OBJECT_CODE, RLE_CODE, BUY_OR_SELL, and CONSTRAINED_YN outputs.
• OKL_ACCOUNTING_UTIL (package) — supplies the GET_LOOKUP_MEANING function, which the view invokes at runtime to convert the CRO_CODE into its displayed MEANING.

The WHERE clause applies an effective-dating filter against the synonym: SYSDATE must be greater than or equal to START_DATE, and either END_DATE is null or END_DATE is greater than or equal to SYSDATE. Consequently, the view returns only contact roles active on the current date, excluding historical or future-dated assignments.

Key Columns

• MEANING — the translated, user-facing description of the contact role, produced by OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING against lookup type OKC_CONTACT_ROLE.
• LOOKUP_CODE — the underlying contact role code (aliased from CRO_CODE), matching the lookup code value.
• LOOKUP_TYPE — a constant literal of 'OKC_CONTACT_ROLE', identifying the lookup context.
• JTOT_OBJECT_CODE — the object code associated with the contact role, used to scope roles to particular business objects.
• RLE_CODE — the role code defining the party's function in the relationship.
• BUY_OR_SELL — indicates whether the contact role pertains to the buy side or the sell side, enabling directional filtering of contacts.
• CONSTRAINED_YN — a yes/no flag indicating whether the role is constrained, typically affecting allowable role assignments.

Common Use Cases and Queries

Typical scenarios include validating active contact roles for a lease or financial agreement, resolving role codes to descriptions in custom reports, and filtering contacts by BUY_OR_SELL to separate counterparties. Because the view is effective-dated, it is well suited to point-in-time operational reporting without additional date predicates.

A representative query filtering on BUY_OR_SELL:

• SELECT meaning, lookup_code, rle_code, buy_or_sell, constrained_yn FROM apps.okl_contact_role_uv WHERE buy_or_sell = 'BUY';

To list all roles with their business object scope:

• SELECT meaning, jtot_object_code, rle_code, buy_or_sell FROM apps.okl_contact_role_uv ORDER BY meaning;

Users should treat the view as read-only and rely on the effective-dating filter already embedded in its definition when constructing reports.