Search Results associated_structure

Overview

PA_PROJECT_STRUCTURE_UTILS is a utility PL/SQL package owned by the APPS schema in Oracle E-Business Suite, defined as an AUTHID CURRENT_USER package so that name resolution occurs under the invoking schema's privileges. It supports the Project Management (PA) module's Project Workplan and Structure functionality by centralizing common validation, lookup, and derivation logic used when creating, modifying, publishing, and deleting project structures and structure versions. The package source header indicates creation in June 2001 and ongoing maintenance through Release 12.1.1 and 12.2.2.

Rather than exposing a single business transaction, the package provides reusable helper routines consumed by other PA APIs, forms, and concurrent programs. This is consistent with its 83 documented procedures/functions and its reference by 92 other packages, making it an infrastructure-level dependency within the ETRM project structures feature set.

Key Procedures and Functions

The package exposes several categories of utility routines. The user search term CHECK_STRUCTURE_NAME_UNIQUE corresponds to one of these documented functions.

• CHECK_DELETE_STRUCTURE_VER_OK — Validates whether a structure version may be deleted for a given project and version.
• CHECK_STRUCTURE_NAME_UNIQUE — Determines whether a structure name already exists, returning Y if unique and N if a duplicate is found. Accepts a structure name, structure id, and project id so the current record can be excluded from the check.
• CHECK_STRUC_VER_NAME_UNIQUE — Analogous uniqueness check for structure version names.
• CHECK_STRUCTURE_TYPE_EXISTS — Confirms that a specified structure type is defined.
• GET_STRUC_TYPE_FOR_STRUCTURE and GET_STRUC_TYPE_FOR_VERSION — Retrieve the structure type associated with a structure or structure version.
• CHECK_PUBLISH_STRUC_VER_OK and CHECK_STRUC_VER_PUBLISHED — Validate publish prerequisites and published status of structure versions.
• GET_NEW_STRUC_VER_NAME — Derives a candidate name for a new structure version.
• STRUCTURE_VERSION_NAME_OR_ID and STRUCTURE_NAME_OR_ID — Resolve identifiers from names or vice versa.
• IS_STRUC_VER_LOCKED_BY_USER and IS_STRUC_VER_LOCKED_BY_USER1 — Determine lock ownership/status for structure versions.
• GET_APPROVAL_OPTION — Returns approval configuration relevant to publication.
• IS_STRUC_TYPE_LICENSED and PRODUCT_LICENSED — Check licensing for structure types and products.
• CHECK_PUBLISHED_VER_EXISTS — Confirms existence of a published version.
• ASSOCIATED_STRUCTURE — Identifies structures associated with a given context.
• GET_ROLLUP_DATES — Derives rollup date information.
• GET_WORKPLAN_VERSION — Retrieves the workplan version for a project.

Tables Accessed

The package reads and writes project-structure and related configuration data through APPS synonyms. Core entities include PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_STRUCTURE, PA_PROJ_ELEM_VER_SCHEDULE, PA_STRUCTURE_TYPES, and PA_PROJ_STRUCTURE_TYPES, which hold projects, structure elements, versions, hierarchies, schedules, and type definitions used by uniqueness, existence, and retrieval routines. PA_PROJECT_STATUSES, PA_IMPLEMENTATIONS, PA_PROJ_FP_OPTIONS, PA_PERCENT_COMPLETES, PA_OBJECT_RELATIONSHIPS, PA_PJI_PROJ_EVENTS_LOG, and PA_PROJ_WORKPLAN_ATTR support status, implementation, financial-plan option, progress, relationship, event-log, and workplan attribute lookups. FND_USER is referenced for user-related validations such as structure version locking.

Usage Notes

PA_PROJECT_STRUCTURE_UTILS is typically invoked indirectly. Oracle Project Management forms and other PA APIs call these functions to validate names, verify licenses, confirm publish/delete eligibility, and resolve structure or version identifiers before performing DML. Concurrent programs operating over project workplans and structure versions also rely on these helpers. Because the routines are pure utility APIs, custom extensions in PA — such as CEMLI components or wrapper APIs — commonly call them to enforce the same business validations. Developers should note that the functions return simple flags such as 'Y'/'N' rather than raising exceptions, so callers are responsible for interpreting results and handling errors; procedures such as CHECK_DELETE_STRUCTURE_VER_OK use x_return_status and x_error_message_code OUT parameters for error reporting.