Results for “validate_object_type”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.JTF_TASK_UTL is a utility package within the Oracle E-Business Suite Task Manager (JTF) module, providing shared validation and lookup services consumed throughout the task management framework. In Oracle EBS 12.1.1 and 12.2.2, the package acts as the central repository of low-level routines that other task-related APIs rely on for validating contacts, parties, locations, currencies, dates, lookups, object types, and escalation data before a task record is committed to the database. Its source header identifi es it as jtfptkls.pls, with the last recorded revision 120.5 dated 2006/07/13, indicating a mature and stable component reused across the release family.
The user search term get_territory_name points to the territory- and resource-related helper logic that JTF_TASK_UTL exposes to callers needing territory or owner context. Although the documented excerpt does not enumerate a standalone GET_TERRITORY_NAME function, the package's extensive family of GET_OWNER, GET_ESCALATION_OWNER, and GET_ESCALATION_LEVEL routines performs the equivalent responsibility of resolving ownership and territory-derived names for task escalation and assignment processing. Applications such as Service Requests, TeleService, and Field Service call this package wherever a task must inherit ownership or territory context from its associated resource or party.
Key Procedures and Functions
The package exposes 86 documented procedures and functions. The most significant, consistent with the ETRM metadata, include:
- G_YES / G_NO — Accessor functions returning the standard 'Y'/'N' indicator constants after bug fix 4866066 replaced the original CONSTANT declarations.
- VALIDATE_SHIFT_CONSTRUCT — Confirms a shift construction identifier is valid before scheduling logic proceeds.
- CALL_INTERNAL_HOOK — Invokes a named internal hook package and API for a given processing type, returning a status.
- GET_ESCALATION_OWNER / GET_ESCALATION_LEVEL — Resolve the owner and escalation level of a task, supporting territory and resource-based ownership resolution.
- VALIDATE_LOCATION_ID, VALIDATE_CONTACT, VALIDATE_CONTACT_POINT, VALIDATE_DISTANCE — Validate address, contact, phone, and geographic references associated with a task.
- VALIDATE_LOOKUP, VALIDATE_OBJECT_TYPE, VALIDATE_PARTY, VALIDATE_PARTY_SITE, VALIDATE_CUST_ACCOUNT, VALIDATE_COSTS, VALIDATE_DATES, VALIDATE_TASK_TEMPLATE_GROUP — Enforce referential and business-rule integrity on the corresponding task attributes.
- GET_OWNER, CURRENCY_CODE, CHECK_DUPLICATE_CONTACT — Return owner identity, valid currency codes, and detect duplicate contact associations.
Each routine follows the standard ETRM convention of returning BOOLEAN or a VARCHAR2 status, and several use OUT NOCOPY parameters for performance in 11g-and-later database environments.
Tables Accessed
The package reads and writes through APPS synonyms to the following documented tables:
- JTF_TASKS_B, JTF_TASK_ALL_ASSIGNMENTS, JTF_TASK_REFERENCES_B, JTF_TASK_CONTACTS — Core task, assignment, reference, and contact data validated by the package.
- JTF_RS_RESOURCE_EXTNS — Resource extension attributes used for owner and escalation resolution.
- HZ_RELATIONSHIPS — Party relationship data supporting contact and territory validation.
- MTL_UNITS_OF_MEASURE — Time UOM class validation via the g_uom_time_class profile.
- FND_APPLICATION, FND_FORM_FUNCTIONS, FND_GRANTS, FND_LOOKUP_VALUES, FND_MENUS, FND_MENU_ENTRIES, FND_OBJECTS, FND_USER, FND_CURRENCIES — Application, security, lookup, menu, currency, and user reference validation.
Usage Notes
JTF_TASK_UTL is invoked primarily from Task Manager forms, Service Request workflows, concurrent programs that validate bulk task imports, and custom PL/SQL code requiring the same integrity checks as the base application. Because 128 other packages reference it, changes to its signatures carry significant regression risk. The package relies on FND profile options such as JTF_TIME_UOM_CLASS, and its privilege constants JTF_TASK_READ_ONLY and JTF_TASK_FULL_ACCESS govern access to task records. Customizations should call the documented procedures rather than duplicating validation logic, ensuring consistent behavior across EBS 12.1.1 and 12.2.2.
-
PACKAGE: APPS.JTF_TASK_UTL 12.2.2
-
PACKAGE: APPS.JTF_TASK_UTL 12.1.1
-
PACKAGE: APPS.JTF_TASK_UTL 12.1.1
-
PACKAGE: APPS.JTF_TASK_UTL 12.2.2