Search Results check_delete_access

Overview

JTF_NOTES_SECURITY_PVT is a private (PVT-classified) PL/SQL package owned by APPS that implements the security enforcement layer for the Oracle E-Business Suite Notes subsystem, part of the CRM Foundation / JTF (Java Technology Foundation) technology stack. Its purpose is to evaluate the current user's privileges against the Notes data model and to return predicate fragments that calling code can embed in queries against the JTF_NOTES and JTF_NOTE_TYPES objects. Rather than exposing a public API surface, the package acts as an internal helper that translates Oracle Application Object Library (AOL) function-based security grants into runtime SQL predicates and access flags.

The package is declared AUTHID CURRENT_USER, meaning its unqualified references are resolved against the invoking schema's privileges rather than the APPS schema. This is significant because the security evaluation must reflect the effective privileges of whoever is executing the note operation, not the privileges of the package owner.

Key Procedures and Functions

ETRM documents eight procedures and functions in this package. Names reflect the header excerpt and the recorded object metadata; parameter lists are not reproduced here.

• CHECK_NOTES_ACCESS — The primary entry point. It accepts a note identifier and returns, by output parameter, a select predicate for the Notes object, a predicate for note types, and discrete numeric access flags covering select, create, update-note, update-note-details, update-secondary, and delete rights, together with standard FND_API return status, message count, and message data outputs.
• GET_SECURITY_PREDICATE — Produces the SQL predicate text used to restrict note queries to rows the current user is permitted to see.
• GET_FUNCTIONS — The routine the user searched for. It resolves the AOL security function names relevant to note operations. The package declares constants for these functions, including JTF_NOTE_CREATE, JTF_NOTE_SELECT, JTF_NOTE_DELETE, JTF_NOTE_UPDATE_NOTES, JTF_NOTE_UPDATE_NOTE_DETAILS, JTF_NOTE_UPDATE_SECONDARY, and JTF_NOTE_TYPE_SELECT, mapped to the objects JTF_NOTES and JTF_NOTE_TYPES.
• CHECK_FUNCTION — Tests whether the current user holds a specific named function, returning the boolean or numeric outcome consumed by the remaining checks.
• CHECK_NOTE_TYPE — Evaluates note-type-level access, corresponding to the JTF_NOTE_TYPE_SELECT function and the x_note_type_predicate output.
• CHECK_UPDATE_SEC_ACCESS — Determines whether the user may modify the secondary attributes of a note.
• CHECK_UPDATE_PRIM_ACCESS — Determines whether the user may modify the primary content of a note.
• CHECK_DELETE_ACCESS — Determines whether the user may delete the note.

Tables Accessed

The only documented table reference, resolved through an APPS synonym, is PLITBLM. This is the AOL function/security lookup used by function-based security checks and by GET_FUNCTIONS to validate and enumerate the note-related functions registered for the user's responsibilities. The Notes and note-type objects referenced by the package's constants are queried through predicates returned to the caller rather than being read directly, which keeps the security logic centralized while allowing the calling queries to remain set-based.

Usage Notes

Because this is a private package, it is invoked indirectly. Typical callers are the JTF Notes public APIs and the Notes-related Oracle Forms, which pass the predicate and access-flag outputs into their own queries before displaying or mutating note records. ETRM records that the package is referenced by one other package, consistent with a single public wrapper that delegates all authorization decisions here. Customizations should not call JTF_NOTES_SECURITY_PVT directly, since its interface is not guaranteed across releases; custom code needing equivalent behavior in 12.1.1 or 12.2.2 should call the supported public Notes API, which in turn invokes these private checks.