Search Results create_category

Overview

The APPS.JTA_SYNC_TASK_CATEGORY package body is a component of the Oracle E-Business Suite CRM foundation layer that manages task categories within the Tasks and Resource Management (JTA) schema. Task categories provide the classification framework for grouping tasks in the Task Manager and related Self-Service applications, and this package encapsulates the server-side logic required to create new category definitions, resolve category identifiers from descriptive names, and determine the profile context under which a given category is stored. The package resides in the proprietary profile data model (the JTF_PERZ_* tables), which stores user-definable personalization and lookup data used throughout CRM modules.

The source header indicates the original author is arpatel (12-Mar-2002), with subsequent fixes by sanjeev and cjang. Fix bug 2418798 introduced the TRUNCATE_CATEGORY_NAME helper and modified CREATE_CATEGORY and GET_CATEGORY_ID to truncate category names longer than the column limit. Fix bug 2540722 later increased the supported length of the category name to 240 bytes and adjusted the truncation logic accordingly. This package is present in both 12.1.1 and 12.2.2; the 12.2.2 ETRM metadata classifies it as an OTHER API with three documented routines. It is referenced by two other packages in the APPS schema, indicating it functions as a shared utility for category synchronization and lookup.

Key Procedures and Functions

• CREATE_CATEGORY — Creates a task category definition. The routine performs the validation and insertion work required to register a category in the profile data store. Because the underlying descriptive column has a length constraint, CREATE_CATEGORY applies the TRUNCATE_CATEGORY_NAME helper (not listed among the documented public routines, but defined in the package body) before persisting the name, ensuring names greater than 240 bytes are shortened and suffixed with an ellipsis rather than raising a value-too-large error.
• GET_CATEGORY_ID — Returns the numeric identifier (PERZ_DATA_ID) of a category given its name and the associated profile identifier. It opens a cursor against JTF_PERZ_DATA filtering by the descriptive column and profile. As of bug fix 2418798, the category name passed to the cursor is truncated first so that lookups succeed even when the stored value was itself truncated at creation time.
• GET_PROFILE_ID — Resolves the profile identifier that owns or scopes a given category. This identifier qualifies the category namespace and is the key passed to GET_CATEGORY_ID, allowing the same descriptive text to exist under different profiles without collision.

Tables Accessed

• JTF_PERZ_DATA — The core profile data table holding category rows. READ (GET_CATEGORY_ID) and WRITE (CREATE_CATEGORY) are performed against the PERZ_DATA_DESC and PROFILE_ID columns.
• JTF_PERZ_PROFILE — The profile definition table that provides the profile context returned by GET_PROFILE_ID and used to scope category lookups.
• JTF_TASK_CATEGORY_S — The task category sequence used to generate or validate category identifiers during creation.
• DUAL — Used for scalar evaluation in helper logic.

Usage Notes

The package is typically invoked indirectly. Task setup forms in Oracle Tasks Manager call the underlying logic to populate category lists, and concurrent or upgrade routines that seed task categories rely on CREATE_CATEGORY and GET_CATEGORY_ID. The two dependent APPS packages reference this body for synchronization of category data. Custom extensions should call the public routines rather than inserting into JTF_PERZ_DATA directly, since the truncation behavior and profile scoping are enforced only through this package. Developers diagnosing "value too large" or "no category found" errors should verify that category names conform to the 240-byte limit and that the correct profile identifier is supplied.