Results for “jtf_note_status”

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

Overview

The view APPS.AST_NOTES_BALI_VL is a TeleSales (AST) module database object that exposes notes captured against sales-related source objects, resolved to their display values and status meanings. It is a "VL" (value-list) style view built on the JTF Notes schema, which is a shared foundation used across multiple Oracle EBS applications, including TeleSales, Marketing, Service, and Order Management. In EBS 12.1.1 and 12.2.2, the view serves as the primary read interface for reporting, Forms LOVs, OAF pages, and integration extracts that require note text alongside human-readable lookup meanings.

The object is owned by APPS and is reported as VALID in the ETRM metadata. Its principal role is to denormalize the multi-table Notes data model — base note rows, translated note text, note contexts, lookup meanings, entered-by resource names, and source object names — into a single queryable row. This makes it convenient for concurrent programs and BI Publisher reports that must present note content without joining the underlying tables manually.

Underlying Base Objects

The view is defined over both base data tables and supporting packages as documented in the ETRM metadata:

• JTF_NOTES_B — the base notes table holding key identifiers, creation/update audit columns, entered-by/entered-date, source object id and code, note type, and note status.
• JTF_NOTES_TL — the translated notes table supplying the NOTE text and the LOB NOTES_DETAIL, filtered by USERENV('LANG').
• JTF_NOTE_CONTEXTS — provides the note context type id and context type for each note.
• JTF_OBJECTS_TL — the translated source object table providing the display name (OBJTL.NAME) for the SOURCE_OBJECT_CODE.
• JTF_RS_RESOURCE_EXTNS and JTF_COMMON_PVT — resolve the creating resource's display name (RES.SOURCE_NAME).
• FND_LOOKUPS — used twice, once for lookup type 'JTF_NOTE_TYPE' and once for 'JTF_NOTE_STATUS', to translate note type and status codes into meanings.
• DBMS_LOB and FND_GLOBAL — package references used for LOB length retrieval and session/language context.

All joins are outer joins against FND_LOOKUPS and the resource extension table, ensuring notes remain visible even when a lookup meaning or resource name is absent.

Key Columns

• JTF_NOTE_ID — the unique identifier of the note; primary correlation key.
• NOTES — the note text from the translated table.
• NOTES_DETAIL_SIZE — the byte/character length of the detailed LOB note content.
• ENTERED_BY / ENTERED_DATE — who and when the note was entered; distinct from creation audit columns.
• SOURCE_OBJECT_ID / SOURCE_OBJECT_CODE — the entity the note is attached to, plus SOURCE_OBJECT_CODE_NAME for its translated name.
• NOTE_STATUS / NOTE_STATUS_MEANING — the status code and its FND lookup meaning, driven by lookup type JTF_NOTE_STATUS.
• NOTE_TYPE / NOTE_TYPE_MEANING — the note classification and its lookup meaning, driven by JTF_NOTE_TYPE.
• CREATED_BY_NAME — the resource display name of the creator.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

The view supports note reporting by status, notes associated with a specific source object, and extraction for integration. Because the user search term was "jtf_note_status", the status-related columns are the most relevant focus. A typical query lists note statuses and their meanings for a given source object:

• SELECT jtf_note_id, note_type_meaning, note_status, note_status_meaning, entered_date FROM ast_notes_bali_vl WHERE source_object_code = :code ORDER BY creation_date DESC;
• SELECT note_status, note_status_meaning, COUNT(*) FROM ast_notes_bali_vl GROUP BY note_status, note_status_meaning;
• SELECT jtf_note_id, notes, source_object_code_name FROM ast_notes_bali_vl WHERE note_status = :status AND entered_date >= :from_date;

These patterns are used in custom reports, Oracle Answers/Dashboards, and BI Publisher data templates. Security and language filtering are inherited from the underlying joins via USERENV('LANG') and standard EBS VPD policies, so queries return only the records permitted to the connected responsibility.