Search Results okc_contact_role




Overview
Explore in AI Chat

Overview

APPS.OKL_CONTACT_ROLE_UV is a read-only Oracle E-Business Suite view that exposes contact role definitions for the Oracle Lease and Finance Management (OKL) and Oracle Contracts (OKC) modules. The "_UV" suffix identifies it as a user-facing validation view, typically consumed by Oracle Forms LOVs, concurrent programs, and custom reporting layers. In EBS 12.1.1 and 12.2.2 the view surfaces role codes maintained in the OKC_CONTACT_SOURCES table and decodes them into user-readable meanings via the OKL_ACCOUNTING_UTIL package.

The view's distinguishing behaviour is temporal filtering. Its WHERE clause restricts output to records where SYSDATE falls between START_DATE and END_DATE (or where END_DATE is null), which means only currently effective contact roles are returned. Because of this, the view behaves as an active-date snapshot rather than a full history listing.

Underlying Base Objects

The view is defined over two referenced objects documented in the ETRM repository:

Because the view joins a synonym to a PL/SQL function call, it is not a pure table projection; each row triggers a lookup invocation, which can affect cost when the view is queried at high cardinality.

Key Columns

  • MEANING — the translated, user-readable description of the contact role, produced by OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING against lookup type OKC_CONTACT_ROLE.
  • LOOKUP_CODE — the underlying CRO_CODE value; the code stored in OKC_CONTACT_SOURCES that identifies the role.
  • LOOKUP_TYPE — a literal value, always 'OKC_CONTACT_ROLE', indicating the lookup category used for translation.
  • JTOT_OBJECT_CODE — the JTF object code that classifies which entity type the contact role applies to.
  • RLE_CODE — the role code that ties the contact source record to the underlying role definition.
  • BUY_OR_SELL — indicates whether the contact role is associated with a buying or selling party context.
  • CONSTRAINED_YN — a Y/N flag showing whether the role is restricted or constrained for use.

Common Use Cases and Queries

The view is commonly used to populate LOVs, validate role codes entered by users, and drive reporting that requires current, date-effective contact role definitions. A typical listing query is:

  • SELECT MEANING, LOOKUP_CODE, JTOT_OBJECT_CODE, BUY_OR_SELL FROM APPS.OKL_CONTACT_ROLE_UV ORDER BY MEANING;
  • SELECT LOOKUP_CODE, MEANING FROM APPS.OKL_CONTACT_ROLE_UV WHERE CONSTRAINED_YN = 'N'; — to restrict output to unconstrained roles only.
  • SELECT a.*, r.MEANING FROM OKC_CONTACT_SOURCES a, APPS.OKL_CONTACT_ROLE_UV r WHERE a.CRO_CODE = r.LOOKUP_CODE; — to decorate raw contact source rows with descriptions. Note that the join can eliminate historical rows, since the view returns only active records.

Custom reports that need expired roles must query OKC_CONTACT_SOURCES directly rather than this view. Because the view lives in the APPS schema, consumers require appropriate grants and should reference it as APPS.OKL_CONTACT_ROLE_UV to avoid synonym resolution differences between the 12.1.1 and 12.2.2 environments.