Search Results get_project_finish_date_src

Overview

APPS.PA_PROJECT_DATES_UTILS is a utility PL/SQL package in the Oracle E-Business Suite Projects (PA) module, declared with AUTHID CURRENT_USER and shipped under the header PARMPDUS.pls. Its business purpose is to centralize the derivation, retrieval, validation, and defaulting of project, task, and assignment date information used throughout Oracle Projects. Rather than embedding date logic directly in forms, concurrent programs, or other APIs, Oracle EBS routes these operations through this single package so that date rules — such as copying dates, deriving dates from schedules or structures, and validating assignment or resource date ranges — are applied consistently regardless of the calling module. The package is referenced by 15 other packages, confirming its role as a foundational dependency for date-related processing in Oracle Projects, and is classified in the ETRM metadata as type OTHER (utility rather than a business API such as an update or create interface).

Key Procedures and Functions

The package exposes 21 documented functions and procedures. Each is a utility with no prerequisites declared in the source header; parameter lists should be treated as documented below rather than inferred.

• GET_PROJECT_START_DATE — Returns the start date for a given project. This is the function most directly associated with the search term get_project_start_date_src; note, however, that the actual documented function bearing the SRC suffix is GET_PROJECT_START_DATE_SRC.
• GET_PROJECT_START_DATE_SRC — Returns the source (origin/basis) of the project start date rather than the date value itself, allowing callers to know how the date was determined.
• GET_PROJECT_FINISH_DATE and GET_PROJECT_FINISH_DATE_SRC — Return the project finish date and the source of that finish date, respectively.
• GET_TASK_START_DATE and GET_TASK_FINISH_DATE — Procedures that return task-level start and finish dates along with the corresponding "as of" date, using project, project element, and parent structure version identifiers.
• GET_TASK_DERIVED_DATES and GET_TASK_COPY_DATES — Derive task dates from project structure or copy dates from a source task.
• GET_DEFAULT_PROJ_START_DATE and GET_DEFAULT_ASSIGN_START_DATE — Return default start dates for projects and assignments.
• GET_STRUCT_SCHEDULE_DATES — Retrieves schedule dates for a structure.
• GET_TASK_DERIVED_DATES — Documented under the utility API type and enumerated in the ETRM procedure list.
• CHECK_FINANCIAL_TASK_EXISTS — Returns a VARCHAR2 indicator of whether a financial task exists for a project element.
• CHEK_ALL_TSK_HAVE_ACT_FIN_DT and CHEK_ONE_TASK_HAS_ACT_ST_DATE — Validation checks confirming that all tasks have actual finish dates, or that at least one task has an actual start date.
• IS_VALID_ASSIGN_START_DATE — Validates a proposed assignment start date.
• VALIDATE_PROJECT_DATES, VALIDATE_RESOURCE_DATES, and VALIDATE_RESOURCE_DATES_BULK — Validate date ranges for projects and resources, with a bulk variant for set-based processing.
• VALIDATE_ASSIGNMENT_DATES_BULK — Bulk validation of assignment date ranges.
• VALIDATE_TEMPLATE_TEAM_DATES — Validates dates for team templates.

Tables Accessed

The package reads and writes project scheduling and structure data through APPS synonyms. Core project data resides in PA_PROJECTS_ALL. Task and element definitions are read from PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_TASKS, and PA_PROJ_ELEM_VER_SCHEDULE (schedule dates). Structure relationships are resolved through PA_PROJ_ELEM_VER_STRUCTURE, PA_PROJ_STRUCTURE_TYPES, and PA_STRUCTURE_TYPES. Workplan attributes come from PA_PROJ_WORKPLAN_ATTR. Assignment data is read from PA_PROJECT_ASSIGNMENTS, and team template data from PA_TEAM_TEMPLATES. PLITBLM is a PL/SQL index-by table type used internally for bulk processing, notably by the BULK validation procedures.

Usage Notes

PA_PROJECT_DATES_UTILS is invoked from Oracle Projects forms and concurrent programs wherever date defaults, validation, or derivation are required, and it is called by other PA packages — the metadata records 15 referencing packages. Because it is declared AUTHID CURRENT_USER, invocations execute with the privileges of the calling schema, so callers should be granted appropriate access to the underlying PA tables. Custom code should call the documented functions and procedures rather than querying the tables directly, in order to inherit Oracle's date rules and validation logic. In EBS 12.1.1 and 12.2.2 the package ships with the standard Projects patch set; it is not a public, versioned business API, so Oracle does not guarantee backward compatibility of individual signatures across releases and callers should avoid direct modification.