Results for “note_status”

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

Overview

OKL_NOTES_BALI_UV is a reportable view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL – Leasing and Finance Management product family. It provides a denormalized, presentation-ready projection of lease-related notes held in the shared JTF (Notes/Collateral) infrastructure. Notes in Oracle EBS are stored in a generic framework so that a single note can be attached to many source objects; OKL_NOTES_BALI_UV resolves that framework into a form suitable for inquiry screens, concurrent report output, and downstream integration extracts.

The view joins the base notes table to its translation table, its context table, and the FND_LOOKUPS reference data for both the note type and note status, and it enriches each row with the resource-resolved name of the creating user. Because the status and type codes are replaced with their translated meanings (NOTE_STATUS_MEANING, NOTE_TYPE_MEANING), the view is particularly well suited to reporting where a user expects readable labels rather than lookup codes. This is the object most commonly queried when a developer searches for the JTF_NOTE_STATUS lookup, since it is the OKL view that materializes that lookup value alongside note content.

Underlying Base Objects

The documented base objects are JTF_NOTES_B (synonym to the notes base table), JTF_NOTES_TL (the notes translation table), JTF_NOTE_CONTEXTS (the note-to-object context table), JTF_RS_RESOURCE_EXTNS (resource extension data used to resolve the creator), FND_LOOKUPS (the generic lookup view), and FND_GLOBAL (the package supplying session context). The view text confirms the following join conditions:

• B.JTF_NOTE_ID = TL.JTF_NOTE_ID, restricted by TL.LANGUAGE = USERENV('LANG'), so only the current session language is returned.
• B.JTF_NOTE_ID = C.JTF_NOTE_ID, linking each note to its context row in JTF_NOTE_CONTEXTS.
• B.NOTE_TYPE = FND_TYPE.LOOKUP_CODE with outer join to lookup type 'JTF_NOTE_TYPE'.
• B.NOTE_STATUS = FND_STATUS.LOOKUP_CODE with outer join to lookup type 'JTF_NOTE_STATUS'.
• RES.USER_ID(+) = B.CREATED_BY, an outer join to JTF_RS_RESOURCE_EXTNS so that the creator name is returned even when no resource row exists.

The outer joins on the FND_LOOKUPS instances are significant: records are not dropped when a lookup value is missing or disabled, so the view remains complete for audit purposes while exposing a null meaning in those cases.

Key Columns

• ROW_ID – The ROWID of the JTF_NOTES_B row, useful for direct row addressing but not stable across reorganizations.
• JTF_NOTE_ID – The primary note identifier shared across all participating base tables.
• NOTES – The translated note body text from JTF_NOTES_TL.
• NOTE_STATUS / NOTE_STATUS_MEANING – The raw JTF_NOTE_STATUS lookup code and its translated meaning.
• NOTE_TYPE / NOTE_TYPE_MEANING – The JTF_NOTE_TYPE lookup code and meaning.
• OBJECT_ID / OBJECT_CODE – The note context type identifier and code from JTF_NOTE_CONTEXTS, indicating the entity the note is attached to.
• SOURCE_OBJECT_ID / SOURCE_OBJECT_CODE – The source object reference carried on the note row itself.
• ENTERED_BY, ENTERED_DATE, CREATED_BY, CREATED_BY_NAME – Authorship and creation metadata, with the creator resolved to a resource name.
• CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes lease note listings for a particular source object, auditing notes by status, and feeding note extracts into external systems. Because the view filters on the session language, reports should be run under the intended language responsibility.

• List open notes for a lease: SELECT jtf_note_id, note_type_meaning, notes FROM okl_notes_bali_uv WHERE source_object_id = :p_lease_id AND note_status_meaning = 'Open';
• Audit note status distribution: SELECT note_status, note_status_meaning, COUNT(*) FROM okl_notes_bali_uv GROUP BY note_status, note_status_meaning;
• Retrieve notes created by a specific user: SELECT jtf_note_id, created_by_name, entered_date, notes FROM okl_notes_bali_uv WHERE created_by_name = :p_user;

Queries should always constrain on JTF_NOTE_ID, SOURCE_OBJECT_ID, or a date range where possible, since the view performs multiple joins including outer joins to FND_LOOKUPS and JTF_RS_RESOURCE_EXTNS, and unrestricted scans can be costly on large note populations.