Results for “jtf_note_id”

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

Overview

OKL_NOTES_DETAILS_UV is a read-only Oracle EBS view owned by the APPS schema and shipped as part of the OKL – Leasing and Finance Management product family. It presents a denormalized, reporting-friendly projection of notes captured against leasing and finance objects. Oracle Leasing stores free-text notes in the shared JTF (Notes/Resource) infrastructure tables JTF_NOTES_B and JTF_NOTES_TL; this view assembles those rows together with decoded lookup meanings, the creator's resource name, and a computed note-body length. Because the view is defined with outer joins to FND_LOOKUPS and JTF_RS_RESOURCE_EXTNS, it does not drop note records when a lookup code or resource mapping is missing, which makes it safer than ad-hoc joins for operational reports and integration extracts.

Underlying Base Objects

The view text joins the following documented objects:

• JTF_NOTES_B – base table holding the note header: note ID, type, status, source object, entry metadata, and the DESCRIPTIVE flexfield attribute columns (ATTRIBUTE1–15 and CONTEXT).
• JTF_NOTES_TL – the translation table, filtered by TL.LANGUAGE = USERENV('LANG') so the returned NOTES text is language-specific.
• FND_LOOKUPS – referenced twice: once joined on NOTE_TYPE with LOOKUP_TYPE = 'JTF_NOTE_TYPE', and once on NOTE_STATUS with LOOKUP_TYPE = 'JTF_NOTE_STATUS'.
• JTF_RS_RESOURCE_EXTNS – joined on CREATED_BY = USER_ID to resolve the creator's source name.
• DBMS_LOB – used through GETLENGTH to size the NOTES_DETAIL LOB, and FND_GLOBAL for session/context resolution.

All lookup and resource joins are outer joins, and the base/translation join is keyed on JTF_NOTE_ID.

Key Columns

• JTF_NOTE_ID, ROW_ID – primary note identifier and the ROWID of the base row.
• NOTES – the translated note text; NOTES_DETAIL_SIZE – character length of the detail LOB.
• NOTE_TYPE / NOTE_TYPE_MEANING – the raw lookup code and its translated meaning from 'JTF_NOTE_TYPE'. This is the column most frequently referenced when users search for "note_type_meaning".
• NOTE_STATUS / NOTE_STATUS_MEANING – the status code and its decoded meaning from 'JTF_NOTE_STATUS'.
• SOURCE_OBJECT_ID / SOURCE_OBJECT_CODE – the leasing entity (contract, asset, quote, etc.) the note is attached to.
• CREATED_BY_NAME, ENTERED_BY, ENTERED_DATE – creator resource name and entry audit data.
• ATTRIBUTE1–15, CONTEXT – the descriptive flexfield columns for additional, client-specific note attributes.

Common Use Cases and Queries

Typical uses include listing notes for a leasing contract, reporting on note distribution by type or status, and extracting note text into external document repositories. Because the view already resolves lookup meanings, consumers avoid re-joining FND_LOOKUPS.

Notes for a single source object, showing decoded types:

SELECT jtf_note_id, note_type_meaning, note_status_meaning,
       created_by_name, entered_date, notes
FROM   apps.okl_notes_details_uv
WHERE  source_object_code = :p_object_code
AND    source_object_id   = :p_object_id
ORDER BY entered_date DESC;

Counting active notes grouped by type meaning:

SELECT note_type_meaning, COUNT(*) note_count
FROM   apps.okl_notes_details_uv
WHERE  note_status_meaning = 'Active'
GROUP BY note_type_meaning
ORDER BY note_count DESC;

Because the underlying note tables are shared across OKL, Service, and other modules, all queries should constrain SOURCE_OBJECT_CODE to isolate Leasing records.