Search Results check_child_exists

Overview

PA_TASK_UTILS is an Oracle Projects utility package owned by the APPS schema that provides low-level, reusable PL/SQL helpers for querying and validating task (WBS element) data within Oracle EBS 12.1.1 and 12.2.2. It encapsulates the navigation logic of the task hierarchy — determining WBS levels, top tasks, and parent tasks — as well as a range of validation checks used before tasks are created, updated, or deleted. The package is classified as OTHER rather than a formal public API, meaning it is intended primarily for internal consumption by Oracle Projects forms, concurrent programs, and other PL/SQL packages. It is nonetheless widely reused: the ETRM metadata records that PA_TASK_UTILS is referenced by 108 other packages, confirming its role as a foundational building block in the Projects task-management layer. Its functions follow a consistent error contract: on success they return the requested value (or a 1/0 status flag), and on failure they generally return a value indicating the Oracle error number.

Key Procedures and Functions

The random searched term, get_parent_task_id, is one of the package's hierarchy-navigation functions. It accepts a task identifier and returns the parent task id of that task; if no parent exists (for example, the task is a top-level task) it returns null, and if an Oracle error occurs it returns the Oracle error number. Its purpose is to allow callers to walk upward through the WBS structure without issuing their own queries against PA_TASKS.

Hierarchy helpers include get_wbs_level, which returns the WBS level of a task (null if not found); get_top_task_id, which returns the top task id for a given task; and sort_order_tree_walk, which supports traversal and ordering of the task tree. Name and attribute lookups include get_task_name, get_task_number, get_resource_name, and get_resource_list_name.

Validation routines include check_unique_task_number (returns 1 if a task number is unused for a project, 0 if already used), check_last_task, check_last_child, check_child_exists, check_delete_task_ok, and check_create_subtask_ok. Additional checks cover percentages and costing: check_pct_complete_exists and check_labor_cost_multiplier. Structural change guards include change_lowest_task_num_ok, change_task_org_ok, change_task_org_ok1, and change_task_org_ok2. Twenty-five documented procedures/functions are registered in total.

Tables Accessed

The package reads and validates against task and project structures through APPS synonyms. PA_TASKS and PA_PROJ_ELEMENTS supply the core task/WBS rows used by the hierarchy and naming functions. PA_PROJECTS_ALL, PA_PROJECT_TYPES, and PA_PROJECT_TYPES_ALL provide project context. PA_PROJ_ELEM_VER_SCHEDULE supports versioned scheduling data. PA_PERCENT_COMPLETES and PA_EVENTS are used by the completion and event-related checks, while PA_RESOURCE_LISTS_ALL_BG and PA_RESOURCE_LIST_MEMBERS back the resource list and resource name lookups. PA_MASS_UPDATE_BATCHES participates in mass-update related validation, and DUAL and PLITBLM are used for standard PL/SQL expression and bulk-collection support.

Usage Notes

PA_TASK_UTILS is typically invoked from Oracle Projects task and project forms, from concurrent programs that build or validate WBS structures, and from other PL/SQL packages and APIs requiring task hierarchy or validation logic. Custom extensions in Oracle EBS commonly call get_parent_task_id and get_top_task_id to traverse the WBS without writing direct queries against PA_TASKS, which keeps navigation logic consistent with Oracle's own conventions. Developers should note that the functions carry PRAGMA RESTRICT_REFERENCES (WNDS, WNPS), reflecting their read-only intent, but they are not formally published APIs; behavior should be confirmed against the target release (12.1.1 versus 12.2.2) before relying on them in custom code.