Search Results update_wp_calendar

Overview

APPS.PA_PROJECT_STRUCTURE_PVT1 is a private PL/SQL package in the Oracle E-Business Suite Projects (PA) module that encapsulates the core business logic for managing project workplan structures and their versions. Within the broader Oracle Projects architecture, this package acts as the internal engine underlying the public workplan APIs, handling the creation, maintenance, versioning, publishing, and lifecycle management of project structures and workplan element hierarchies. It is classified as an internal ("PVT") package, meaning it is not intended for direct invocation by external integrators but instead services higher-level public packages such as PA_PROJECT_PUB, PA_PROJECT_STRUCTURE_PUB1, PA_TASK_PUB1, PA_TASK_PVT1, PA_WORKPLAN_AMG_PUB, and PA_STRUCT_TASK_ROLLUP_PUB. Its responsibilities span structural definition (projects, tasks, and their hierarchy), version control across the workplan lifecycle, baseline and publish operations, and integration with the workplan approval workflow.

Key Procedures and Functions

The package exposes 31 documented procedures and functions covering the full workplan structure lifecycle. Core structural operations include CREATE_STRUCTURE, UPDATE_STRUCTURE, and DELETE_STRUCTURE, which manage the fundamental project structure record. Version-level operations are handled by CREATE_STRUCTURE_VERSION, UPDATE_STRUCTURE_VERSION_ATTR, DELETE_STRUCTURE_VERSION, COPY_STRUCTURE_VERSION, and COPY_STRUCTURE, allowing structures to be duplicated and versioned over time.

Structure version attributes are managed through CREATE_STRUCTURE_VERSION_ATTR and DELETE_STRUCTURE_VERSION_ATTR. Publishing and baseline functions include PUBLISH_STRUCTURE, UPDATE_LATEST_PUB_LINKS, and BASELINE_STRUCTURE_VERSION, which govern the transition of workplan versions from working to published or baselined states. Workplan execution functions include SPLIT_WORKPLAN, SUBMIT_WORKPLAN, CHANGE_WORKPLAN_STATUS, and REWORK_WORKPLAN, supporting submission, approval-driven status transitions, and rework cycles. Setup and configuration routines include UPDATE_STRUCTURES_SETUP_OLD, UPDATE_WORKPLAN_VERSIONING, and UPDATE_WP_CALENDAR. Together these procedures enforce the integrity rules that keep project structures consistent with workplan versioning and approval requirements.

Tables Accessed

The package reads and writes the principal Oracle Projects workplan tables via APPS synonyms. Structural and version data reside in PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEMENT_VERSIONS_S, PA_PROJ_ELEM_VER_STRUCTURE, and PA_PROJ_ELEM_VER_SCHEDULE (with its _S shadow table), which collectively store workplan elements, their versioned attributes, hierarchy links, and scheduling information. PROJECT-level context is drawn from PA_PROJECTS_ALL, PA_PROJECT_STATUSES, and PA_PROJECT_PARTIES, while PA_OBJECT_RELATIONSHIPS and its _S table track relationships between structural objects. Temporary processing uses PA_PROJ_ELEMENTS_TMP. Reference data is obtained from FND_USER and HR_ALL_ORGANIZATION_UNITS, and UI-related attributes from PA_PAGE_CONTENTS.

Usage Notes

Because PA_PROJECT_STRUCTURE_PVT1 is a private package, it is invoked indirectly through Oracle Projects forms, concurrent programs, and public APIs rather than called directly by custom code. Ten documented packages reference it, notably PA_PROJECT_PUB, PA_PROJECT_STRUCTURE_PUB1, PA_WORKPLAN_AMG_PUB, PA_TASK_PUB1, PA_TASK_PVT1, and PA_WORKPLAN_WORKFLOW, confirming its role as a shared internal service layer. It depends on FND_API for the standard API error-handling framework and on PA_INTERFACE_UTILS_PUB for interface utilities. The presence of workflow-related procedures indicates tight integration with the workplan approval workflow. Customers extending workplan or project structure functionality should invoke the public packages (for example PA_PROJECT_STRUCTURE_PUB1) rather than this private package, preserving upgrade safety. In Oracle EBS 12.1.1 and 12.2.2 the object is documented as VALID, with the 12.2.2 ETRM listing 31 procedures and functions.