Search Results create_lifecycle




Overview
Explore in AI Chat

Overview

APPS.PA_LIFECYCLES_PVT is a private PL/SQL package body within the Oracle Projects (PA) module of Oracle E-Business Suite. It provides the internal implementation logic for managing project lifecycles, the top-level containers that organize project structures such as workplans, phases, and tasks into reusable definitions. In Oracle Projects, a lifecycle defines the sequence and allowed relationships of project elements across their versions, and this package encapsulates the create, update, and delete operations required to maintain those definitions. The package is a runtime validation API whose procedures accept a standard Oracle EBS API parameter set, including an API version, commit flag, validate-only flag, validation level, calling module, debug mode, and maximum message count.

As a PVT (private) API, PA_LIFECYCLES_PVT is not intended for direct customer invocation. It is invoked by other packages—the ETRM metadata records that it is referenced by one other package—and typically sits beneath the public lifecycle APIs and the self-service project forms. The source header identifies the package as a shared, non-shipped development object, and the default calling module parameter is SELF_SERVICE, indicating its primary use by the self-service project lifecycle UI.

Key Procedures and Functions

The package exposes eight documented procedures, organized as four lifecycle operations plus their phase-level counterparts and their associated delete-validation checks.

  • CREATE_LIFECYCLE — Creates a new lifecycle definition, including its short name, name, description, project usage type, and product usage type, returning the generated lifecycle identifier and standard API return status, message count, and message data.
  • CREATE_LIFECYCLE_PHASE — Adds a phase to an existing lifecycle, using project element and structure relationship records to position the phase within the lifecycle hierarchy.
  • UPDATE_LIFECYCLE — Modifies the descriptive and usage-type attributes of an existing lifecycle.
  • UPDATE_LIFECYCLE_PHASE — Modifies the attributes or ordering of a phase already associated with a lifecycle.
  • DELETE_LIFECYCLE — Removes a lifecycle definition from the system.
  • DELETE_LIFECYCLE_PHASE — Removes a phase from a lifecycle.
  • CHECK_DELETE_LIFECYCLE_OK — Validates whether a lifecycle is eligible for deletion, checking for dependencies before permitting removal.
  • CHECK_DELETE_LCYL_PHASE_OK — Validates whether a specific lifecycle phase may be deleted without violating referential or usage constraints.

Tables Accessed

The package reads and writes a set of Projects foundation tables through APPS synonyms. Lifecycle identity and usage classification are stored in PA_LIFECYCLE_USAGES and its _S table. Project element definitions, their versions, and version schedules are maintained through PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEMENT_VERSIONS_S, PA_PROJ_ELEM_VER_SCHEDULE, and PA_PROJ_ELEM_VER_SCHEDULE_S. The hierarchical placement of phases uses PA_PROJ_ELEM_VER_STRUCTURE and PA_PROJ_ELEM_VER_STRUCTURE_S. Structure type metadata is resolved from PA_STRUCTURE_TYPES, PA_PROJ_STRUCTURE_TYPES, and PA_PROJ_STRUCTURE_TYPES_S; the source declares a cursor selecting the structure_type_id for the LIFECYCLE class. Cross-object links are recorded in PA_OBJECT_RELATIONSHIPS and PA_OBJECT_RELATIONSHIPS_S, while PA_PROJ_WORKPLAN_ATTR holds workplan attributes associated with the lifecycle definition.

Usage Notes

PA_LIFECYCLES_PVT is normally invoked indirectly. Project administrators working in the self-service project lifecycle forms trigger these procedures through the parent lifecycle API layer, which performs the public-level validation and then delegates to this private package. Because the procedures honor the P_commit and P_validate_only flags, callers can execute them in validation-only mode to check input before committing, or leave commit control to the surrounding transaction. The debug mode and message-count parameters support the standard Oracle EBS error-stack pattern, and callers must inspect the returned X_return_status, X_msg_count, and X_msg_data values to retrieve messages. Custom extensions should not call this package directly; they should use the corresponding public Projects APIs, since internal signatures and behavior are subject to change between releases such as 12.1.1 and 12.2.2.