Search Results decoded_source_code

Overview

JTF_NOTES_VL is the primary Multi-Lingual Support (MLS) view over Notes in Oracle E-Business Suite, owned by the APPS schema and defined within the JTF – CRM Foundation product module. It unites the transactional note records held in JTF_NOTES_B with their translated, language-specific text held in JTF_NOTES_TL, presenting a single queryable interface for all notes attached to any object in the EBS data model. Because notes are stored generically against a source object identifier and code rather than dedicated foreign keys, JTF_NOTES_VL is the canonical access point for retrieving note content, context, and status irrespective of the owning entity.

The view is central to reporting and integration because it abstracts the underlying MLS join and enriches each row with derived values — user names, lookup meanings, and object descriptions — that would otherwise require multiple joins. Its status is VALID in the ETRM 12.2.2 dictionary, and it remains valid across 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The view is defined over the following documented objects:

• JTF_NOTES_B (synonym) — the base table holding note identity, parent hierarchy, source object linkage, status, entry metadata, and 15 descriptive attributes.
• JTF_NOTES_TL (synonym) — the translation table supplying NOTES and NOTES_DETAIL, joined on JTF_NOTE_ID and restricted by JNT.LANGUAGE = USERENV('LANG').
• JTF_OBJECTS_B and JTF_OBJECTS_TL (synonyms) — provide the object code and its translated meaning (SOURCE_OBJECT_MEANING).
• FND_LOOKUPS (view) — resolved twice (FLS, FLP) to translate note type and note status into display meanings.
• JTF_NOTES_PKG, JTF_COMMON_PVT, and FND_GLOBAL (packages) — supply derived values via GET_NOTE_CONTEXT_VALUE and GETUSERINFO.

Key Columns

• JTF_NOTE_ID — primary identifier of the note.
• PARENT_NOTE_ID — supports threaded or hierarchical notes.
• SOURCE_OBJECT_ID / SOURCE_OBJECT_CODE — the polymorphic link identifying the object to which the note is attached.
• SOURCE_NUMBER — derived context value returned by JTF_NOTES_PKG.GET_NOTE_CONTEXT_VALUE.
• NOTES / NOTES_DETAIL — the translated note text.
• NOTE_STATUS, NOTE_STATUS_MEANING, NOTE_TYPE, NOTE_TYPE_MEANING — status and classification, with decoded lookup meanings.
• ENTERED_BY / ENTERED_BY_NAME — user identifier and resolved display name.
• DECODED_SOURCE_CODE / DECODED_SOURCE_MEANING — normalized object codes, collapsing PARTY_ORGANIZATION, PARTY_RELATIONSHIP, and PARTY_PERSON into the single code PARTY.
• ATTRIBUTE1–15, CONTEXT — flexfield descriptor columns.

Common Use Cases and Queries

The view is used to list all notes for an entity, to filter notes by type or status, and to retrieve note text in the session language. The examples below reflect the polymorphic relationship model, including notes attached to party relationships.

• Retrieve all notes for a specific source object, e.g. a party relationship.
• Filter notes by status or type using the decoded meanings.
• Report note activity by creator with resolved user names.

SELECT jtf_note_id, source_object_code, decoded_source_code,
  notes, note_status_meaning, entered_by_name
FROM apps.jtf_notes_vl
WHERE source_object_code = 'PARTY_RELATIONSHIP'
  AND source_object_id = :p_relationship_id;

Because the view restricts translation rows to the session language via USERENV('LANG'), queries automatically return text in the operator's locale, making it suitable for both concurrent reporting and integrated API retrieval across the party and CRM relationship models.