Search Results decoded_source_meaning
Overview
APPS.JTF_NOTES_VL is a versioned-language (VL) reporting view within the Oracle E-Business Suite CRM Foundation module. It presents note records stored by the Notes infrastructure — the framework used throughout EBS to associate free-form textual notes with arbitrary business entities such as parties, party relationships, resources, and various transactional records. The view consolidates the base notes entity table with its translation table and several lookup and object-registration sources, exposing human-readable meanings alongside the raw coded identifiers.
Because it returns decoded values rather than raw codes, JTF_NOTES_VL is well suited to ad-hoc reporting, Oracle Reports/XML Publisher data sources, OAF/Forms LOV queries, and integration extracts where consumers require descriptive text rather than internal lookup codes. The view is defined with USERENV('LANG') as the language filter on each translated table, so the values it returns are automatically rendered in the session language of the querying user, consistent with the standard EBS multi-language (MLS) virtualization pattern.
Underlying Base Objects
The view is defined over the following documented base objects:
JTF_NOTES_B— the base (language-independent) notes table, supplying identity, ownership, status, and the descriptive flexfield attribute columns. Aliased asJNB.JTF_NOTES_TL— the translation table holding the note text (NOTESandNOTES_DETAIL) per language. Aliased asJNT.JTF_OBJECTS_BandJTF_OBJECTS_TL— the JTF object registration tables, providing the source object code and its translated name (SOURCE_OBJECT_MEANING). Aliased asJOBandJOL.JTF_OBJECTS_TL(second instance, aliasedJOTL) — joined onOBJECT_CODE = 'PARTY'to supply the generic "Party" meaning for the three party-related source object codes.FND_LOOKUPS(two instances,FLSandFLP) — supplyingNOTE_TYPE_MEANINGandNOTE_STATUS_MEANINGdecoded values.JTF_NOTES_PKG,JTF_COMMON_PVT, andFND_GLOBAL— PL/SQL packages invoked within the view's column list to resolve the note context value (source_number) and the entered-by user name (ENTERED_BY_NAME).
The view therefore joins the note entity to its translations, its source-object registration, and two lookup sets, applying language predicates throughout to produce a single, decoded row per note.
Key Columns
JTF_NOTE_ID,PARENT_NOTE_ID— primary identifier and optional parent for threaded notes.SOURCE_OBJECT_ID,SOURCE_OBJECT_CODE— the entity the note is attached to and its object code.SOURCE_OBJECT_MEANING,DECODED_SOURCE_CODE,DECODED_SOURCE_MEANING— decoded descriptions of the source object. TheDECODED_SOURCE_CODEcollapses the party variants (PARTY_ORGANIZATION,PARTY_RELATIONSHIP,PARTY_PERSON) to a singlePARTYvalue, andDECODED_SOURCE_MEANINGreturns the generic "Party" meaning for those cases.source_number— a context value derived byJTF_NOTES_PKG.get_note_context_value, typically returning the source object's reference number.NOTES,NOTES_DETAIL— the note text and its detailed body in the session language.NOTE_STATUS,NOTE_STATUS_MEANING,NOTE_TYPE,NOTE_TYPE_MEANING— the status and type codes with their lookup meanings.ENTERED_BY,ENTERED_BY_NAME,ENTERED_DATE— the authoring user (ID and resolved name) and timestamp.CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE,LAST_UPDATE_LOGIN— standard WHO audit columns.ATTRIBUTE1–ATTRIBUTE15,CONTEXT— the descriptive flexfield segments and their context.
Common Use Cases and Queries
Typical uses include listing all notes for a given party, auditing note authorship, and joining decoded object meanings into custom reports. A representative query retrieving notes for a specific source object is:
SELECT jtf_note_id,
decoded_source_code,
decoded_source_meaning,
source_number,
note_type_meaning,
note_status_meaning,
entered_by_name,
entered_date,
notes
FROM apps.jtf_notes_vl
WHERE source_object_id = :p_object_id
AND decoded_source_code = 'PARTY'
ORDER BY entered_date DESC;
To summarize note activity by type and source object:
SELECT decoded_source_meaning,
note_type_meaning,
COUNT(*) AS note_count
FROM apps.jtf_notes_vl
WHERE entered_date >= :p_from_date
GROUP BY decoded_source_meaning, note_type_meaning
ORDER BY note_count DESC;
Because the view calls JTF_COMMON_PVT.GetUserInfo and JTF_NOTES_PKG per row, performance on large result sets should be assessed carefully; filtering on indexed columns such as JTF_NOTE_ID, SOURCE_OBJECT_CODE, or SOURCE_OBJECT_ID is advisable to limit the rows processed by these PL/SQL calls.
-
VIEW: APPS.JTF_NOTES_VL
12.1.1
-
VIEW: APPS.JTF_NOTES_VL
12.2.2
-
View: JTF_NOTES_VL
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:JTF.JTF_NOTES_VL, object_name:JTF_NOTES_VL, status:VALID, product: JTF - CRM Foundation , description: MLS view over JTF_NOTES_B and JTF_NOTES_TL. Main view to query up all Notes related to any object. , implementation_dba_data: APPS.JTF_NOTES_VL ,
-
View: JTF_NOTES_VL
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:JTF.JTF_NOTES_VL, object_name:JTF_NOTES_VL, status:VALID, product: JTF - CRM Foundation , description: MLS view over JTF_NOTES_B and JTF_NOTES_TL. Main view to query up all Notes related to any object. , implementation_dba_data: APPS.JTF_NOTES_VL ,
-
VIEW: APPS.JTF_NOTES_VL
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:JTF.JTF_NOTES_VL, object_name:JTF_NOTES_VL, status:VALID,
-
VIEW: APPS.JTF_NOTES_VL
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:JTF.JTF_NOTES_VL, object_name:JTF_NOTES_VL, status:VALID,
-
APPS.OKS_COVERAGES_PVT dependencies on JTF_NOTES_VL
12.1.1
-
APPS.OKS_COVERAGES_PVT dependencies on JTF_NOTES_VL
12.2.2
-
APPS.OKS_COVERAGES_PVT SQL Statements
12.1.1
-
APPS.OKS_COVERAGES_PVT SQL Statements
12.2.2
-
PACKAGE BODY: APPS.OKS_COVERAGES_PVT
12.1.1
-
PACKAGE BODY: APPS.OKS_COVERAGES_PVT
12.2.2
-
eTRM - JTF Tables and Views
12.2.2
description: Interface table to store data that needs to be displayed in Excel ,
-
eTRM - JTF Tables and Views
12.1.1
description: Interface table to store data that needs to be displayed in Excel ,