Search Results pa_project_dates_utils




Overview
Explore in AI Chat

Overview

PA_PROJECT_DATES_UTILS is a PL/SQL utility package body owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It centralizes the derivation, validation, and defaulting of project, task, and resource assignment dates within the Oracle Projects (PA) module. Project and task scheduling in Oracle Projects requires consistent handling of start and finish dates across multiple structural levels — project, project element (task), project element version, and resource assignment. Rather than embedding this logic in individual forms or concurrent programs, the ETRM development model consolidates it into this utility package so that date rules are applied uniformly.

The package is classified as an "OTHER" API object, meaning it is not a public, supported interface in the same sense as the Open Interfaces, but it is heavily used internally — the metadata records that it is referenced by 15 other packages. It exposes 21 documented procedures and functions covering date retrieval, defaulting, validation, and bulk validation. The package body was reported as VALID in the ETRM extract, confirming that all dependencies resolved correctly in the documented environment.

Key Procedures and Functions

The documented subprograms fall into four functional groups.

Date retrieval. GET_PROJECT_START_DATE and GET_PROJECT_FINISH_DATE return the start and finish dates for a project, with GET_PROJECT_START_DATE_SRC and GET_PROJECT_FINISH_DATE_SRC returning the source from which the date was derived. GET_TASK_START_DATE and GET_TASK_FINISH_DATE provide the equivalent for project elements (tasks). GET_TASK_DERIVED_DATES and GET_TASK_COPY_DATES support structure-level date propagation, the latter used when copying task definitions.

Defaulting. GET_DEFAULT_PROJ_START_DATE and GET_DEFAULT_ASSIGN_START_DATE supply default dates when a user or process has not supplied explicit values. GET_STRUCT_SCHEDULE_DATES returns scheduling dates from the structure definition, and GET_TASK_START_DATE / GET_TASK_FINISH_DATE interact with these defaults.

Validation. CHECK_FINANCIAL_TASK_EXISTS verifies the presence of a financial task before date operations proceed. IS_VALID_ASSIGN_START_DATE validates a single assignment start date. VALIDATE_PROJECT_DATES, VALIDATE_RESOURCE_DATES, and VALIDATE_ASSIGNMENT_DATES_BULK perform the corresponding checks at project, resource, and bulk levels. VALIDATE_RESOURCE_DATES_BULK and VALIDATE_TEMPLATE_TEAM_DATES extend validation to bulk resource loads and team template dates respectively.

Structural checks. CHEK_ALL_TSK_HAVE_ACT_FIN_DT and CHEK_ONE_TASK_HAS_ACT_ST_DATE (note the abbreviated "CHEK" spelling preserved from the source) examine whether tasks have actual finish or start dates populated, supporting date-consistency enforcement across the workplan.

Tables Accessed

The package reads and writes the primary Oracle Projects scheduling tables: PA_PROJECTS_ALL for project-level date attributes, PA_PROJ_ELEMENTS and PA_TASKS for task definitions, PA_PROJ_ELEMENT_VERSIONS and PA_PROJ_ELEM_VER_SCHEDULE for versioned schedule dates, and PA_PROJ_ELEM_VER_STRUCTURE with PA_PROJ_STRUCTURE_TYPES and PA_STRUCTURE_TYPES for structure and hierarchy context. PA_PROJECT_ASSIGNMENTS holds resource assignment dates, PA_PROJ_WORKPLAN_ATTR stores workplan-level attributes, and PA_TEAM_TEMPLATES supports template team date validation. A reference to PLITBLM indicates use of a PL/SQL index-by table type for bulk operations. FND_PROFILE is accessed to read profile option values that influence defaulting behavior.

Usage Notes

The package is not referenced by any database object directly per the ETRM dependency extract, but is invoked by other APPS packages — including PA_PROJECT_STRUCTURE_UTILS and PA_PROJ_ELEMENTS_UTILS — which in turn are called from Oracle Projects forms and concurrent programs during project creation, task definition, workplan maintenance, and resource assignment. Practically, custom code should not call this utility directly in place of supported public APIs; it is best treated as an internal helper. Because it is an "OTHER"-classified API, its signatures are not guaranteed stable across patches or upgrades, so any custom dependency on it should be reviewed when applying Oracle Projects patches.