Search Results jtf_task_security_pvt




Overview
Explore in AI Chat

Overview

JTF_TASK_SECURITY_PVT is a private PL/SQL package body in the APPS schema that implements the task-level security engine for the Oracle E-Business Suite Task Manager (JTF) subsystem. Its business purpose is to determine which users or resources may view, update, assign, or delete a given task record, and to render the corresponding privilege checks available to the Task Manager forms, personalization framework, and dependent APIs. Because the package is classified as PVT, its program units are not intended for direct external invocation; they are consumed by the public Task Manager APIs and by the forms layer that presents tasks in the Resource Manager and TeleSales/Sales applications.

The package sits at the intersection of three concerns: application object grants (FND_GRANTS, FND_MENUS, FND_FORM_FUNCTIONS, FND_OBJECTS), resource-team membership (JTF_RS_TEAM_MEMBERS, JTF_RS_GROUP_MEMBERS), and the task data model itself (JTF_TASKS_B, JTF_TASK_ALL_ASSIGNMENTS). The result is a privilege model for tasks that mirrors the object-grant model used elsewhere in EBS.

Key Procedures and Functions

The documented API surface comprises eight program units:

  • GET_PRIVILEGES — Returns the set of privileges available to the current user for task objects, derived from the object grant model.
  • CHECK_PRIVELEGE_FOR_TASK — Evaluates whether the caller holds a specific privilege against a given task; the core entry point used by forms and dependent code before permitting an action.
  • CHECK_PRIVATE_TASK_PRIVELEGE — Additional evaluation for tasks flagged as private, applying the stricter visibility rules that govern tasks not shared with the user's resource group or team.
  • PRIVELEGES_FROM_OTHER_RESOURCE — Determines privileges the current user inherits indirectly, for example through assignment to another resource or team.
  • GET_OBJECT_NAME — Resolves the application object name associated with a task or privilege context, bridging task records to FND_OBJECTS entries.
  • GET_DEFAULT_QUERY — Supplies the default security predicate or query used to restrict task lists to records the user is permitted to see.
  • GET_CATEGORY_ID — Returns the category identifier used in task categorization and in the associated security and personalization lookups.
  • DELETE_CATEGORY — Removes a task category, including any related security or personalization metadata.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms. Grant, menu, and function metadata are read from FND_GRANTS, FND_MENUS, FND_MENU_ENTRIES, FND_FORM_FUNCTIONS, and FND_OBJECTS; FND_DATA_SECURITY and FND_TABLE_OF_VARCHAR2_30 (PLITBLM) support the security predicate plumbing. Task and assignment data come from JTF_TASKS_B and JTF_TASK_ALL_ASSIGNMENTS. Team and group membership is resolved through JTF_RS_TEAM_MEMBERS and JTF_RS_GROUP_MEMBERS. Personalization and query metadata are drawn from JTF_PERZ_DATA, JTF_PERZ_PROFILE, JTF_PERZ_QUERY, and JTF_PERZ_QUERY_PARAM. Address and object-translation lookups use JTF_CAL_ADDRESSES, JTF_OBJECTS_B, and JTF_OBJECTS_TL. Messages are raised via FND_MSG_PUB.

Usage Notes

JTF_TASK_SECURITY_PVT is not referenced by any database object and is not called directly from custom code; it is invoked internally by the Task Manager public APIs, by dependent packages (three packages reference it), and by the Oracle Forms that display and modify tasks. Form-level navigation and button enablement typically call CHECK_PRIVELEGE_FOR_TASK or CHECK_PRIVATE_TASK_PRIVELEGE, while list views and LOVs use GET_DEFAULT_QUERY to constrain results. The package depends on JTF_TASK_UTL for shared utility logic. Because it depends on FND_GRANTS, FND_MENUS, and FND_FORM_FUNCTIONS, changes to function or menu grants affect task security behavior immediately. Both 12.1.1 and 12.2.2 expose the same eight documented program units; 12.2.2 preserves the package with VALID status. The misspelling of PRIVELEGE in procedure names is retained in the shipped code and must be referenced exactly if reading dependent code.