Search Results create_structure_version

Overview

PA_PROJECT_STRUCTURE_PUB1 is a public PL/SQL package body in the APPS schema that provides the core API layer for managing the hierarchical structural elements of Oracle Projects. In Oracle EBS 12.1.1 and 12.2.2, the package governs the creation, versioning, publication, and maintenance of project structures, workplans, and financial structures. This encompasses both work breakdown structures (WBS) and task structures, together with the versioning model that allows project managers to maintain working, draft, and published versions of a structure over time.

The package follows the standard Oracle EBS API paradigm. It exposes a bundled public interface (PUB1) that wraps business logic implemented in the corresponding private package, PA_PROJECT_STRUCTURE_PVT1. It depends on FND_API for the standard return-status and message-stack conventions, and on FND_MSG_PUB for error handling. State is carried between calls through the SETGLOBALUSERID and GETGLOBALUSERID procedures, which persist the acting user identifier. The package is documented as VALID in a 12.2.2 ETRM repository and is not referenced by any database object, confirming its role as a top-level entry point rather than a utility.

Key Procedures and Functions

The documented interface exposes 24 procedures and functions, grouped by functional area:

• Structure lifecycle: CREATE_STRUCTURE, CREATE_STRUCTURE_VERSION, UPDATE_STRUCTURE, COPY_STRUCTURE, and COPY_STRUCTURE_VERSION create and clone structures and their versions.
• Version attributes: CREATE_STRUCTURE_VERSION_ATTR and UPDATE_STRUCTURE_VERSION_ATTR manage attribute data associated with a structure version.
• Publication and deletion: PUBLISH_STRUCTURE promotes a working version to published status, while DELETE_STRUCTURE_VERSION and DELETE_WORKING_STRUC_VER remove obsolete or draft versions.
• Workplan management: SUBMIT_WORKPLAN and REWORK_WORKPLAN drive the workplan approval workflow, and UPDATE_WORKPLAN_VERSIONING controls workplan version behavior.
• Financial structures: ENABLE_FINANCIAL_STRUCTURE, DISABLE_FINANCIAL_STRUCTURE, and CLEAR_FINANCIAL_FLAG toggle the financial tracking designation of a structure.
• Setup and configuration: UPDATE_STRUCTURES_SETUP_ATTR maintains project structure setup attributes.
• Session context and validation: SETGLOBALUSERID, GETGLOBALUSERID, and CHECK_ACTION_ALLOWED establish the acting user and validate whether a requested action is permitted against project security rules.

Tables Accessed

The package reads and writes the principal Projects structure tables. PA_PROJ_ELEMENTS and PA_PROJ_ELEMENT_VERSIONS store structural element definitions and their versioned instances, while PA_PROJ_ELEM_VER_STRUCTURE and PA_PROJ_ELEM_VER_SCHEDULE hold the hierarchy and date-scheduling relationships between element versions. PA_STRUCTURE_TYPES, PA_PROJ_STRUCTURE_TYPES, and PA_PROJ_STRUCTURE_TYPES_PKG define the allowed structure classifications. PA_TASKS and PA_OBJECT_RELATIONSHIPS link task records to related business objects. Workplan and progress behavior is supported through PA_PROJ_PROGRESS_ATTR, PA_PROJ_PROGRESS_ATTR_PKG, and PA_PROJ_WORKPLAN_ATTR. Project-level data is drawn from PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, and PA_PROJECT_CUSTOMERS, and budget references come from PA_BUDGET_VERSIONS. Commitment and expenditure integration reads PA_COMMITMENT_TXNS, PA_EXPENDITURE_ITEMS_ALL, AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, AP_EXP_REPORT_DISTS_ALL, and MTL_MATERIAL_TRANSACTIONS. FND_USER supplies user context and PA_SECURITY_PVT enforces role-based access.

Usage Notes

This package is a public interface intended to be called by Oracle Projects forms, concurrent programs, and customer-developed extensions rather than by end users directly. It is referenced by ten other packages, indicating that higher-level Projects modules, including workplan, task, and progress components, delegate structure maintenance to it. Standard FND_API conventions apply: callers should pass the initialization and commit parameters required by the underlying private layer and should inspect the returned status and message stack after every invocation. Because PUBLISH_STRUCTURE and SUBMIT_WORKPLAN interact with workflow and versioning logic, they should be invoked within an explicit transaction boundary so that version state remains consistent. Direct DML against the underlying structure tables should be avoided in favor of these APIs to preserve versioning integrity, security validation, and progress and workplan attributes.