Search Results secure_delete_note

Overview

JTF_NOTES_PUB is the public PL/SQL interface for Notes Management within Oracle E-Business Suite, owned by the APPS schema and classified as a public (PUB) API. Its purpose is to provide a single, centralized entry point for creating, updating, and deleting notes attached to a wide range of business entities. The package header declares the supported business entity categories explicitly, including CAC_NOTE (the note entity itself), CS_SERVICE_REQUEST, AS_OPPORTUNITY, and AMS_LEAD, with an internal comment confirming applicability to Service Requests, Tasks, Customers, and similar records. This makes the package the standard mechanism by which notes authored in one functional area become visible against another, such as a note recorded on a service request that also references an opportunity or a lead.

The API follows Oracle's standard PL/SQL API conventions, exposing an initialization message list flag, a commit flag, a validation level parameter, and the standard return status and message count out parameters. In the 12.1.1 and 12.2.2 releases the package remains active and marked as compatible (S), and it is referenced by 78 other packages, which indicates how deeply it is embedded in the EBS application stack.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions. The primary business-facing entry points are:

• CREATE_NOTE — Inserts a note into the JTF_NOTES table, accepting an optional parent note identifier to support threaded or reply-style notes.
• UPDATE_NOTE — Modifies the attributes of an existing note record.
• SECURE_CREATE_NOTE, SECURE_UPDATE_NOTE, SECURE_DELETE_NOTE — Perform the same create, update, and delete operations while enforcing security validation against the performing user.
• VALIDATE_ENTERED_BY — Confirms that the user identified as the note author is valid.
• CREATE_NOTE_CONTEXT and UPDATE_NOTE_CONTEXT — Maintain the association records that link a note to a specific business entity through the JTF_NOTE_CONTEXTS table.
• VALIDATE_NOTE_TYPE and VALIDATE_OBJECT — Check that the supplied note type and the target business object are legitimate before the note is persisted.
• WRITELOBTODATA and WRITEDATATOLOB — Convert long note bodies between LOB and data storage representations.

The remaining routines — ADD_INVALID_ARGUMENT_MSG, ADD_MISSING_PARAM_MSG, ADD_NULL_PARAMETER_MSG, and TRUNC_STRING_LENGTH — are internal utility helpers that populate the API message stack and enforce string length limits.

Tables Accessed

The package reads and writes the base note tables JTF_NOTES_B, JTF_NOTES_S, and JTF_NOTES_TL, which hold the note header, its descriptive columns, and the translatable text respectively. JTF_NOTE_CONTEXTS stores the entity associations that determine which business object a note belongs to. FND_LOOKUP_VALUES supplies the valid note types, and FND_USER is consulted for author validation. JTF_OBJECT_USAGES records usage of notes against objects. DBMS_LOB is used for large-object handling, DUAL for trivial lookups, and PLITBLM for PL/SQL table-to-string conversion.

Usage Notes

JTF_NOTES_PUB is typically invoked from Oracle Forms-based note entry windows in Service, Sales, and Marketing modules, from concurrent programs that migrate or purge note data, and from custom PL/SQL integrations. Because AS_OPPORTUNITY is a declared category, callers working with Opportunity Center or similar sales objects should route note creation through this API rather than writing to the underlying tables directly.