Search Results jtf_sr_note

Overview

APPS.CS_SR_NOTES_V is a service-request notes view in Oracle E-Business Suite, exposed under the APPS schema and documented in ETRM for releases 12.1.1 and 12.2.2. It presents a flattened, reporting-friendly projection of notes attached to Service Request (SR) incidents. The view consolidates records from the JTF Notes framework (JTF_NOTES_B / JTF_NOTES_TL) with the incident header (CS_INCIDENTS_ALL_B), resolves lookup meanings for note type and note status from FND_LOOKUPS, joins to FND_USER for the creator's username, and fabricates a human-readable SOURCE string from CS_LOOKUPS. Its role is to provide a denormalized, read-only channel for BI Publisher reports, OAF/ADF extensions, custom concurrent programs, and integration extracts that need SR note content without navigating the underlying note model directly. The presence of RECORD_SOURCE_TYPE = 'JTF_SR_NOTE' and TRUE_STMT = 'T' identifies this as one branch of a broader notes abstraction intended for uniform consumption across object types.

Underlying Base Objects

The documented base objects referenced by the view are:

• JTF_NOTES_B (SYNONYM) — base note table holding the note key, source object identity, note type, status, and audit columns.
• JTF_NOTES_TL (SYNONYM) — translation table holding the note text (NOTES) and the optional detailed body (NOTES_DETAIL), filtered by USERENV('LANG').
• CS_INCIDENTS_ALL_B (SYNONYM) — the Service Request incident header, supplying INCIDENT_ID and INCIDENT_NUMBER.
• FND_USER (SYNONYM) — resolves CREATED_BY to USER_NAME.
• FND_LOOKUPS (VIEW) — joined twice (outer) to resolve JTF_NOTE_TYPE and JTF_NOTE_STATUS meanings.
• CS_LOOKUPS (VIEW) — supplies the SR source-type lookup meaning used to decorate the SOURCE string.
• FND_GLOBAL (PACKAGE) — session/global context used indirectly by the user-environment language filter.
• DBMS_LOB (SYNONYM) — used in the IS_DETAIL decode to test whether NOTES_DETAIL has content.

The join predicates restrict SOURCE_OBJECT_CODE = 'SR' and equate NOTE.SOURCE_OBJECT_ID to INC.INCIDENT_ID, so only notes bound to an SR incident are returned. Lookup joins are outer ((+)), so notes with unmapped type or status still appear.

Key Columns

• INCIDENT_ID / OBJ_ID — primary incident key; OBJ_ID is an alias of the same value.
• ID — the JTF note identifier (JTF_NOTE_ID).
• APP_OBJ_ID / APP_OBJ_CODE — source object id and code copied from the note record ('SR').
• NOTE_TYPE_CODE / NOTE_TYPE_MEANING — note type code and its JTF_NOTE_TYPE lookup meaning.
• NOTE_STATUS / NOTE_STATUS_MEANING — note status code and its JTF_NOTE_STATUS lookup meaning.
• NOTE — the translatable note text from JTF_NOTES_TL.
• IS_DETAIL — 'Y' or 'N' derived from DBMS_LOB.GETLENGTH(NOTES_DETAIL), indicating whether a detailed body exists.
• SOURCE — concatenation of the CS_SR_SOURCE_TYPE lookup meaning and the incident number.
• OBJ_NUMBER, USER_NAME, TRUE_STMT, RECORD_SOURCE_TYPE, plus standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical uses include SR note extracts for reporting, note-audit queries, and populating integration payloads. A representative query:

• SELECT incident_id, id, note_type_meaning, note_status_meaning, note, is_detail, user_name, creation_date FROM apps.cs_sr_notes_v WHERE incident_number = :p_sr_number ORDER BY creation_date;
• Filtering by type: SELECT id, note FROM apps.cs_sr_notes_v WHERE note_type_code = 'CUSTOMER' AND is_detail = 'Y';
• Counting notes per SR: SELECT incident_id, COUNT(*) FROM apps.cs_sr_notes_v GROUP BY incident_id;

Because the view applies USERENV('LANG'), note text is returned in the session language; queries intended for cross-language extraction must account for that filter or query the base note tables directly. Read-only access via the APPS synonym is required, and no DML is supported on the view.