Search Results object_code_name

Overview

The APPS.AST_NOTES_CONTEXTS_V view is a TeleSales (AST) reporting and integration object that exposes the contexts associated with notes recorded in Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, notes are stored generically in the JTF (CRM Foundation) schema, and each note can be linked to one or more application objects — a party, an opportunity, a lead, a resource, or any other registered object type. AST_NOTES_CONTEXTS_V resolves this generic linkage into business-meaningful context information by joining the base context table to object metadata and applying decoding logic for party contexts.

The view is primarily read-only and is used by TeleSales and CRM components to render note context descriptions, LOV titles, and detail labels. Because it depends on USERENV('LANG') in its definition, the row set returned is language-dependent, meaning the translated object names and titles reflect the session language of the querying user.

Underlying Base Objects

According to the documented metadata for 12.2.2, the view references the following base objects:

• JTF_NOTE_CONTEXTS (synonym) — the driving table, holding one row per note-to-object context, keyed by NOTE_CONTEXT_ID.
• JTF_OBJECTS_B (synonym) — the base object registry, providing the object code, select ID, select name, select details, FROM/WHERE/ORDER BY fragments, and the base table used to resolve the context.
• JTF_OBJECTS_TL (synonym) — the translated object registry, supplying LOV window and column titles filtered by the session language.
• AR_LOOKUPS (view) — used inside a DECODE to translate the party type lookup code into a meaning when NOTE_CONTEXT_TYPE = 'PARTY'.
• HZ_PARTIES (synonym) — joined to AR_LOOKUPS to obtain the PARTY_TYPE for the specific party context.
• AST_NOTE_PACKAGE (package) — its NOTE_CONTEXT_INFO function resolves object-specific context details for non-party contexts.

The view joins JTF_NOTE_CONTEXTS to JTF_OBJECTS_B on NOTE_CONTEXT_TYPE = OBJECT_CODE, and to JTF_OBJECTS_TL on the same object code, constrained by the session language.

Key Columns

• NOTE_CONTEXT_ID — unique identifier of the note context; this is the column most commonly used in joins and lookups.
• JTF_NOTE_ID — foreign key to the parent note record in the JTF notes tables.
• NOTE_CONTEXT_TYPE_ID — the identifier of the specific object instance being referenced (for example, a PARTY_ID).
• OBJECT_ID — the resolved context type identifier exposed for reporting.
• OBJECT_CODE / OBJECT_CODE_NAME — the object code and its translated name.
• OBJECT_ID_NAME and OBJECT_ID_DETAILS — resolved name and descriptive detail for the referenced object instance, produced by the package function.
• SELECT_ID, SELECT_NAME, SELECT_DETAILS, FROM_TABLE, WHERE_CLAUSE, ORDER_BY_CLAUSE — metadata fragments describing how the context object can be queried, useful for dynamic SQL construction.
• LOV_WINDOW_TITLE, LOV_NAME_TITLE, LOV_DETAILS_TITLE — translated labels for LOV display in the TeleSales UI.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include retrieving all contexts for a given note, obtaining the human-readable object name for a context, or joining note information to the underlying business entity. A representative query is:

• SELECT note_context_id, jtf_note_id, object_code_name, object_id_name FROM apps.ast_notes_contexts_v WHERE jtf_note_id = :p_note_id;
• SELECT note_context_id, jtf_note_id, object_id_name, object_id_details FROM apps.ast_notes_contexts_v WHERE note_context_type_id = :p_party_id AND object_code = 'PARTY';

Because the view is a reporting convenience layer over JTF note contexts, it is suited to read-only inquiry, LOV population, and integration extraction, and should not be used as a target for DML.