Search Results secure_update_note

Overview

JTF_NOTES_PUB_W is a public wrapper package in the Oracle E-Business Suite application schema APPS that provides a stable, technology-agnostic interface to the Oracle Notes (JTF Notes) infrastructure. Notes are the free-form, contextual annotations attached to business entities throughout EBS, such as leads, opportunities, service requests, tasks, and interactions. The package exists to shield callers from the internal JTF_NOTES_PUB implementation and from its underlying PL/SQL table types, which are transported across the interface as indexed numeric and character table parameters.

The _W suffix indicates that this is the wrapper used by the Oracle EBS integration layer. It exposes the same core note operations as JTF_NOTES_PUB while accepting and returning data in the generic JTF_NUMBER_TABLE, JTF_DATE_TABLE, and JTF_VARCHAR2_TABLE_300 collection types. This design makes the API consumable from environments that cannot easily pass strongly typed record sets, including SOA/XML gateway integrations and Java-based adapters. Note that the package header carries the $Header: jtfntsws.pls 120.2 2006/04/26 tag, indicating the specification has been stable since release 12.0 and remains valid in 12.1.1 and 12.2.2.

Key Procedures and Functions

• SECURE_CREATE_NOTE — the object of the user's search. Performs the same note-creation work as CREATE_NOTE but is intended for use where the caller's identity and organization context must be enforced for security. It is the appropriate entry point for creating a note tied to a specific source object (source_object_id and source_object_code) under the responsibility of the calling user. Values such as entered_by, created_by, last_updated_by, and org_id are passed explicitly so that the audit columns and multi-org context are set correctly regardless of the session in which the call executes.
• SECURE_UPDATE_NOTE — the companion to SECURE_CREATE_NOTE, applying the same security-aware handling of audit and organization columns when modifying an existing note.
• CREATE_NOTE — inserts a new note record and returns the generated jtf_note_id. The full parameter set in the header defines parent_note_id, note status, note text, entered-by/date, context, the p_note_type value, and fifteen DFF attribute columns (attribute1 through attribute15 plus p_context), plus the standard API framework parameters p_api_version, p_init_msg_list, p_commit, p_validation_level, x_return_status, x_msg_count, and x_msg_data.
• UPDATE_NOTE — modifies the mutable columns of an existing note using the same API framework and DFF parameter conventions.
• CREATE_NOTE_CONTEXT — creates an association between a note and the business context (source object) with which it is linked, allowing a single note to be referenced from multiple contexts.
• UPDATE_NOTE_CONTEXT — updates that association.
• ROSETTA_TABLE_COPY_IN_P1 — converts JTF_NUMBER_TABLE, JTF_DATE_TABLE, and JTF_VARCHAR2_TABLE_300 collections received from the caller into the internal jtf_note_contexts_tbl_type used by the wrapped API.
• ROSETTA_TABLE_COPY_OUT_P1 — performs the reverse conversion, transforming the internal table type back into the generic collection types for return to the caller.

Tables Accessed

According to the ETRM metadata, the package references the APPS synonym PLITBLM, a standard PL/SQL table-to-message/utilization helper used by the Rosetta conversion routines. The actual note data is persisted by the underlying JTF notes tables (JTF_NOTES and JTF_NOTE_CONTEXTS), which are accessed indirectly through the wrapped implementation rather than being declared directly in this wrapper specification.

Usage Notes

SECURE_CREATE_NOTE is normally invoked from EBS Forms (notes canvases in CRM and service modules), from concurrent programs that migrate or import notes, and from custom PL/SQL or Java integration code that needs to attach a note to a business object. When calling it, supply p_api_version, set p_init_msg_list and p_commit appropriately for transaction control, and always check x_return_status after the call — values other than 'S' (success) indicate validation or processing errors whose text is available through x_msg_data or the FND_MSG_PUB message stack. Because SECURE_CREATE_NOTE manages org_id and audit columns explicitly, it should be preferred over CREATE_NOTE whenever the calling session relies on MOAC or user-based security.