Search Results okl_cs_notes_uv




Overview
Explore in AI Chat

Overview

OKL_CS_NOTES_UV is a consolidated view owned by the APPS schema in Oracle Lease and Finance Management (OKL). It presents lease and finance contract notes in a denormalized, human-readable form by joining the underlying JTF notes tables to resource, lookup, and activity tables. The view is status VALID in Oracle EBS 12.1.1 and 12.2.2 and is treated as a user-facing presentation layer rather than a base table; the "_UV" suffix conventionally denotes a user view intended for inquiry and reporting.

Its role is to expose note text together with the descriptive meanings that are otherwise scattered across multiple lookup and object tables. Rather than returning bare codes such as NOTE_STATUS or SOURCE_OBJECT_CODE, the view resolves them into NOTE_STATUS_MEANING, NOTE_TYPE_MEANING, and SOURCE_OBJECT_MEANING. It also resolves the internal ENTERED_BY user id into the resource name ENTERED_BY_NAME. This makes the view well suited for reporting, integration extracts, and any inquiry that must display notes against lease contracts without requiring the caller to re-implement the joins.

Underlying Base Objects

The documented metadata lists the following referenced objects: FND_GLOBAL (package), FND_LOOKUPS (view), and synonyms JTF_IH_ACTIVITIES, JTF_NOTES_B, JTF_NOTES_TL, JTF_OBJECTS_TL, and JTF_RS_RESOURCE_EXTNS. The view joins these as follows. JTF_NOTES_B and JTF_NOTES_TL supply the note header and translated note text, joined on JTF_NOTE_ID with T.LANGUAGE restricted to USERENV('LANG'). JTF_OBJECTS_TL is matched on SOURCE_OBJECT_CODE and its language, providing SOURCE_OBJECT_MEANING. FND_LOOKUPS is used twice: once with LOOKUP_TYPE 'JTF_NOTE_STATUS' to translate NOTE_STATUS, and once with LOOKUP_TYPE 'JTF_NOTE_TYPE' to translate NOTE_TYPE. JTF_RS_RESOURCE_EXTNS supplies ENTERED_BY_NAME via RES.USER_ID(+) = B.CREATED_BY. The rows are restricted by an outer join to JTF_IH_ACTIVITIES on SOURCE_OBJECT_ID = ACTIVITY_ID, which yields CONTRACT_ID from ACT.DOC_ID. The result set is ordered by B.CREATION_DATE DESC.

Key Columns

  • ROW_ID — Rowid of the JTF_NOTES_B row, useful for locating the underlying note record.
  • JTF_NOTE_ID / PARENT_NOTE_ID — Note identifier and optional parent note for threaded notes.
  • SOURCE_OBJECT_ID / SOURCE_OBJECT_CODE — The object the note is attached to and its code; SOURCE_OBJECT_MEANING provides the display name from JTF_OBJECTS_TL.
  • NOTES / NOTES_DETAIL — Short note text and expanded detail text from JTF_NOTES_TL.
  • ENTERED_BY / ENTERED_BY_NAME — The creating user id and the resolved resource name; ENTERED_BY is sourced from B.CREATED_BY and is the column most frequently searched by users.
  • ENTERED_DATE — Date the note was entered (sourced from JTF_NOTES_B.ENTERED_DATE).
  • NOTE_TYPE / NOTE_TYPE_MEANING — Note classification code and its JTF_NOTE_TYPE lookup meaning.
  • NOTE_STATUS / NOTE_STATUS_MEANING — Note status code and its JTF_NOTE_STATUS lookup meaning.
  • CONTEXT / CONTRACT_ID — Context token and the associated contract identifier derived from the activity's DOC_ID.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — Standard audit columns from the base note row.

Common Use Cases and Queries

Typical uses include displaying contract notes in custom concurrent programs, feeding note extracts to downstream systems, and building inquiry screens that filter by author. Because the user searched for "entered_by", the most relevant pattern is filtering notes by the entering user.

List all notes entered by a specific user:

  • SELECT JTF_NOTE_ID, CONTRACT_ID, ENTERED_BY, ENTERED_BY_NAME, ENTERED_DATE, NOTE_TYPE_MEANING, NOTE_STATUS_MEANING, NOTES FROM APPS.OKL_CS_NOTES_UV WHERE ENTERED_BY = :user_id ORDER BY ENTERED_DATE DESC;

List notes for a given contract with reader-friendly meanings:

  • SELECT CONTRACT_ID, ENTERED_BY_NAME, ENTERED_DATE, NOTES FROM APPS.OKL_CS_NOTES_UV WHERE CONTRACT_ID = :contract_id ORDER BY ENTERED_DATE DESC;

Because joins to JTF_RS_RESOURCE_EXTNS, FND_LOOKUPS, and JTF_IH_ACTIVITIES are present, rows where a resource name cannot be resolved may show a null ENTERED_BY_NAME; the outer joins on RES.USER_ID(+), the note type lookup, and the activity join preserve the note rows. FND_GLOBAL is referenced to supply session context such as the language through USERENV('LANG'). Callers should treat the view as read-only and rely on the resolved meaning columns for presentation rather than joining to FND_LOOKUPS again.