Search Results jtf_notes_s




Overview

JTF_NOTES_PKG is the core PL/SQL package body in the Oracle E-Business Suite Applications (APPS) schema that implements the Notes infrastructure for the CRM Foundation (JTF) module. Notes are the free-text annotations that end users attach to essentially any EBS entity — customers, contacts, opportunities, service requests, tasks, and other objects registered in the JTF_OBJECTS repository. The package encapsulates the server-side logic that governs creation, retrieval, modification, deletion, locking, context handling, and language translation of note records. It is classified in ETRM as an OTHER API, meaning it is primarily a private implementation layer rather than a formally published interface; the companion package JTF_NOTES_PUB exposes the supported public entry points, while JTF_NOTES_PKG supplies the underlying DML and LOB manipulation routines. In the Oracle EBS 12.1.1 and 12.2.2 releases the object is documented as VALID in the APPS schema, and its dependencies confirm tight coupling to the Notes base table, the translation table, and the note context model.

Key Procedures and Functions

The ETRM metadata documents nine stored procedures and functions. Their documented purposes are as follows:

  • INSERT_ROW — Creates a new note record, populating the base note row and any associated context or LOB content required for a complete note.
  • LOCK_ROW — Acquires a row-level lock on an existing note, providing concurrency control before an update or delete operation.
  • UPDATE_ROW — Modifies the attributes of an existing note record, including its text content and descriptive fields.
  • DELETE_ROW — Removes a note and its dependent rows (translations, contexts) from the Notes tables.
  • ADD_LANGUAGE — Inserts a translated version of a note for a specific language into the translation table, supporting multilingual deployments.
  • WRITEDATATOLOB — Writes note content into a LOB column, using DBMS_LOB for chunked handling of large note bodies that exceed VARCHAR2 limits.
  • GET_NOTE_CONTEXT_VALUE — Retrieves a context attribute value for a note, resolving the JTF_NOTE_CONTEXTS key-value pairs used to classify and categorize notes.
  • LOAD_ROW — Loads a note row during data migration, setup, or interface loads, typically invoked from concurrent or seed-data processes.
  • TRANSLATE_ROW — Populates translated note content, generally used alongside ADD_LANGUAGE in language-installation and translation workflows.

Tables Accessed

The package operates against the Notes schema objects through APPS synonyms:

  • JTF_NOTES_B — The base note table holding note identifiers, source object references, and core attributes; the primary target of INSERT_ROW, UPDATE_ROW, and DELETE_ROW.
  • JTF_NOTES_TL — The translation table storing language-specific note text; manipulated by ADD_LANGUAGE and TRANSLATE_ROW.
  • JTF_NOTES_S — The sequence used to generate unique note identifiers; referenced directly by the package body for primary-key assignment.
  • JTF_NOTE_CONTEXTS — Stores context name/value pairs associated with a note; read by GET_NOTE_CONTEXT_VALUE.
  • JTF_OBJECTS_B / JTF_OBJECTS_VL — The object registry identifying the entity type a note is attached to.
  • JTF_OBJECT_USAGES — Defines which note usages or categories apply to a given object type.
  • FND_LANGUAGES — Provides installed language codes for translation handling.
  • DBMS_LOB / DBMS_SQL — Oracle-supplied packages used for LOB writes (WRITEDATATOLOB) and dynamic SQL.

Usage Notes

JTF_NOTES_PKG is not intended for direct invocation by customer extensions. Application forms within CRM Foundation and dependent modules (Service, Sales, Interaction Center) call Notes functionality through JTF_NOTES_PUB, which in turn delegates to this package body. Because ETRM records that the package is referenced by eleven other packages, any modification carries broad regression risk across the Notes-enabled application surface. Custom code should use the published JTF_NOTES_PUB interface rather than calling JTF_NOTES_PKG procedures directly. Batch operations such as note migration or multilingual loads invoke LOAD_ROW and TRANSLATE_ROW, while runtime user actions rely on INSERT_ROW, UPDATE_ROW, DELETE_ROW, LOCK_ROW, and WRITEDATATOLOB. Given its use of DBMS_LOB and DBMS_SQL, DBMS_LOB privileges must be granted appropriately in any cloning or migration to 12.2.2.