Search Results object_code_name




Overview
Explore in AI Chat

Overview

OKL_NOTES_CONTEXTS_UV is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Lease and Finance Management product family. The view exposes note contexts associated with lease and finance contracts, joining the generic Oracle Notes infrastructure (the JTF_NOTE_CONTEXTS and JTF_OBJECTS tables) with OKL-specific presentation logic. It is designated a "UV" (user view) object, meaning it is intended for end-user and reporting consumption rather than for direct transactional use.

The view plays a supporting role in the Notes feature of Oracle Lease Management, where notes are attached to business entities such as parties, contracts, and other objects. Its principal contribution is the enrichment of the raw note context record with derived, human-readable attributes — most notably the display name of the associated object, the originating table, and the LOV (List of Values) metadata that drives the Notes user interface. Because it answers the question of "which object does this note context belong to, and how should it be labelled," it is commonly referenced when diagnosing issues around the note_context_id identifier.

Underlying Base Objects

The view is defined over five documented base objects, combined in a single SELECT statement:

  • JTF_NOTE_CONTEXTS (SYNONYM) — the driving table, aliased C, supplying the note and note-context identifiers together with audit columns and the context type.
  • JTF_OBJECTS_B (SYNONYM) — aliased OBJ, providing the object-code definition, the dynamic SELECT clause fragments (SELECT_ID, SELECT_NAME, SELECT_DETAILS, FROM_TABLE, WHERE_CLAUSE, ORDER_BY_CLAUSE) used to resolve object descriptions.
  • JTF_OBJECTS_TL (SYNONYM) — aliased OBJTL, the translated table supplying LOV window, name, and details titles, restricted to the session language via USERENV('LANG').
  • AR_LOOKUPS (VIEW) — referenced in a scalar subquery to resolve PARTY_TYPE meanings for contexts whose type is 'PARTY'.
  • HZ_PARTIES (SYNONYM) — also referenced within the party-type DECODE, supplying the party type code for lookup translation.
  • OKL_CS_LC_CONTRACT_PVT (PACKAGE) — an OKL private package whose NOTE_CONTEXT_INFO function is invoked to derive the object display name from the dynamic SQL fragments.

The joins are driven by NOTE_CONTEXT_TYPE matching OBJECT_CODE across the JTF_NOTE_CONTEXTS, JTF_OBJECTS_B, and JTF_OBJECTS_TL objects, ensuring each context row is enriched with its object definition and localized titles.

Key Columns

  • NOTE_CONTEXT_ID — the primary identifier of the note context record; the column central to the user's search.
  • JTF_NOTE_ID — foreign key to the parent note in the JTF notes repository.
  • OBJECT_ID / OBJECT_CODE — the context-type identifier and its object code, exposing the underlying entity the note is attached to.
  • OBJECT_CODE_NAME / OBJECT_ID_NAME — derived display names; OBJECT_CODE_NAME applies a PARTY_TYPE lookup for party contexts and otherwise falls back to the translated object name, while OBJECT_ID_NAME is computed by OKL_CS_LC_CONTRACT_PVT.NOTE_CONTEXT_INFO.
  • SELECT_ID, SELECT_NAME, SELECT_DETAILS, FROM_TABLE, WHERE_CLAUSE, ORDER_BY_CLAUSE — dynamic SQL metadata describing how the related object can be queried.
  • LOV_WINDOW_TITLE, LOV_NAME_TITLE, LOV_DETAILS_TITLE — localized titles used by the Notes LOV interface.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

This view is typically queried to resolve a note_context_id to its associated object and display name, to audit note attachments across lease contracts, or to troubleshoot LOV behaviour in the Notes UI.

  • Resolving a specific context:
SELECT note_context_id, jtf_note_id, object_code, object_code_name,
       object_id_name, creation_date
FROM   okl_notes_contexts_uv
WHERE  note_context_id = :p_note_context_id;
  • Listing all contexts for a given object type:
SELECT c.note_context_id, c.jtf_note_id, c.object_id_name
FROM   okl_notes_contexts_uv c
WHERE  c.object_code = 'OKL_CONTRACT'
ORDER  BY c.creation_date DESC;
  • Auditing recent note attachments by user:
SELECT created_by, object_code, COUNT(*)
FROM   okl_notes_contexts_uv
GROUP  BY created_by, object_code;

Because OBJECT_ID_NAME and OBJECT_CODE_NAME depend on the OKL_CS_LC_CONTRACT_PVT package and AR_LOOKUPS join respectively, performance on large datasets can be affected; predicate filtering on object_code or note_context_id is therefore recommended in reporting extracts.