Search Results source_object_meaning

Overview

AST_NOTES_VL is a TeleSales (AST) module view in Oracle E-Business Suite that presents a consolidated, translated (VL, or "view language") representation of notes attached to TeleSales source objects. It is a denormalized presentation view that joins the base notes tables with translation tables, lookup tables, and resource extension tables so that reporting and integration consumers can retrieve human-readable note content, note status meaning, note type meaning, and the name of the resource who entered the note without needing to reconstruct those joins manually.

The "_VL" suffix indicates the view exposes translated columns based on the session language, resolved through USERENV('LANG'). The view is documented as not implemented in the standard database, meaning it is a metadata artifact that may be deployed in specific environments or referenced for integration design rather than a universally present object. Its role is primarily analytical: it serves as a read-only reporting surface over TeleSales notes data.

Underlying Base Objects

The view is defined over five documented base objects via outer joins and lookup-based outer joins:

• JTF_NOTES_B — the base notes table, containing the note ID, parent note ID, source object references, dates, audit columns, note type, note status, and the 15 descriptive flexfield attribute columns and context.
• JTF_NOTES_TL — the translation table supplying NOTES and NOTES_DETAIL text filtered by the session language.
• JTF_OBJECTS_TL — the translation table for source objects, providing OBJECT_CODE and its translated NAME.
• FND_LOOKUPS — referenced twice: once aliased LKUP for JTF_NOTE_STATUS and once aliased LKCMTTYPE for JTF_NOTE_TYPE, supplying lookup MEANING values.
• JTF_RS_RESOURCE_EXTNS — resource extension data, outer-joined on CREATED_BY to resolve the entering resource.

No referenced base objects are separately documented in the ETRM registry, so relationships must be derived from the view text itself.

Key Columns

• JTF_NOTE_ID / PARENT_NOTE_ID — primary identifier of the note and its optional parent, supporting threaded notes.
• SOURCE_OBJECT_ID / SOURCE_OBJECT_CODE — the TeleSales object the note belongs to; SOURCE_OBJECT_MEANING and NAME expose the translated object name.
• NOTES / NOTES_DETAIL — the short and long note text in the session language.
• NOTE_STATUS / NOTE_STATUS_MEANING — status code and its lookup meaning (JTF_NOTE_STATUS).
• NOTE_TYPE / NOTE_TYPE_MEANING — type code and its lookup meaning (JTF_NOTE_TYPE).
• ENTERED_BY / ENTERED_BY_NAME — the resource who entered the note, resolved through JTF_RS_RESOURCE_EXTNS.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — descriptive flexfield segments for extensibility.

Common Use Cases and Queries

Typical uses include TeleSales activity reporting, note audit listings, and integration extracts that need decoded status and type values. The view is well suited to dashboards summarizing note volumes by object, status, and entered-by resource.

Sample query listing notes for a source object:

• SELECT JTF_NOTE_ID, NOTES, NOTE_STATUS_MEANING, NOTE_TYPE_MEANING, ENTERED_BY_NAME, CREATION_DATE FROM AST_NOTES_VL WHERE SOURCE_OBJECT_CODE = :object_code ORDER BY CREATION_DATE DESC;

Sample query aggregating note activity:

• SELECT SOURCE_OBJECT_MEANING, NOTE_STATUS_MEANING, COUNT(*) FROM AST_NOTES_VL GROUP BY SOURCE_OBJECT_MEANING, NOTE_STATUS_MEANING;

Because the view joins translation and lookup tables, results reflect the run-time session language and current lookup configurations, which should be considered when comparing historical extracts.