Search Results update_lifecycle
Overview
APPS.PA_LIFECYCLES_PUB is a public PL/SQL API package within the Oracle E-Business Suite Projects (PA) module. It provides the programmatic interface for creating, maintaining, and removing project lifecycles — the configurable containers that group project phases and are used to drive project status progression and project structure across the Projects application. In Oracle EBS 12.1.1 and 12.2.2, lifecycle definitions underpin how project managers and administrators standardise project execution, so the procedures in this package are the supported entry points for managing that configuration data.
The package follows Oracle's standard API conventions, using the FND_API framework for message handling, validation levels, and commit control. Its header declares the standard missing-value constants (G_MISS_NUM, G_MISS_CHAR, G_MISS_DATE) and identifies the package as G_PKG_NAME. The ETRM documentation classifies it as a PUBLIC API, meaning it is intended for invocation from forms, concurrent programs, and custom extensions rather than internal-only use.
Key Procedures and Functions
The documented package exposes six procedures, organised as three paired create/update/delete operations across two object levels:
- CREATE_LIFECYCLE — Creates a new lifecycle for a given lifecycle name and short name. It accepts API framework parameters (API version, init message list, commit flag, validate-only flag, validation level, calling module, debug mode, maximum message count) alongside the lifecycle business attributes: short name, name, description, project usage type, and product usage type. It returns the generated lifecycle identifier and standard return status, message count, and message data.
- CREATE_LIFECYCLE_PHASE — Creates a phase record belonging to an existing lifecycle, allowing the ordered structure of a lifecycle to be assembled programmatically.
- UPDATE_LIFECYCLE — Modifies the attributes of an existing lifecycle definition. This is the procedure most commonly targeted by the search term "update_lifecycle".
- UPDATE_LIFECYCLE_PHASE — Modifies the attributes of an existing lifecycle phase.
- DELETE_LIFECYCLE — Removes a lifecycle definition.
- DELETE_LIFECYCLE_PHASE — Removes a phase from a lifecycle.
All six procedures return the standard X_return_status, X_msg_count, and X_msg_data outputs and honour the P_commit and P_validate_only parameters, enabling callers to validate before committing.
Tables Accessed
The package interacts with the following base tables, referenced through APPS synonyms:
- PA_LIFECYCLE_USAGES — Stores the usage type assignments (project and product) associated with each lifecycle.
- PA_PROJECT_STATUSES — Holds the project status definitions tied to lifecycle phases.
- PA_PROJ_ELEMENTS — Holds the project element (phase) definitions that make up a lifecycle.
- PA_PROJ_ELEMENT_VERSIONS — Stores versioned records of project elements, maintaining historical integrity as lifecycle phases change.
- DUAL — Used for single-row utility queries within the PL/SQL logic.
Usage Notes
PA_LIFECYCLES_PUB is invoked whenever lifecycle configuration must be created or maintained outside of the standard setup forms. Typical callers include the Projects setup forms for project lifecycles, concurrent programs that seed or migrate lifecycle data, and custom extensions or integrations that synchronise lifecycle definitions between environments. The ETRM metadata records that the package is referenced by zero other packages, indicating it is a top-level public API invoked directly rather than a dependency of other delivered code.
For the "update_lifecycle" use case, custom code should call UPDATE_LIFECYCLE after querying the target lifecycle identifier, and should pass P_validate_only initially to confirm that the requested change is valid before committing. Because validation follows FND_API conventions, callers must check X_return_status and inspect the message stack on error. Commit scope is controlled by the caller through P_commit, which supports multi-step transactions that create a lifecycle and its phases atomically.
-
APPS.PA_LIFECYCLES_PUB SQL Statements
12.2.2
-
APPS.PA_LIFECYCLES_PUB SQL Statements
12.1.1
-
APPS.PA_LIFECYCLES_PVT SQL Statements
12.1.1
-
APPS.PA_LIFECYCLES_PVT SQL Statements
12.2.2
-
PACKAGE: APPS.PA_LIFECYCLES_PUB
12.1.1
-
PACKAGE: APPS.PA_LIFECYCLES_PUB
12.2.2
-
PACKAGE: APPS.PA_LIFECYCLES_PVT
12.1.1
-
PACKAGE: APPS.PA_LIFECYCLES_PVT
12.2.2
-
PACKAGE BODY: APPS.PA_LIFECYCLES_PUB
12.2.2
-
PACKAGE BODY: APPS.PA_LIFECYCLES_PUB
12.1.1
-
PACKAGE BODY: APPS.PA_LIFECYCLES_PVT
12.2.2
-
PACKAGE BODY: APPS.PA_LIFECYCLES_PVT
12.1.1
-
APPS.PA_LIFECYCLES_PVT dependencies on PA_LIFECYCLES_PVT
12.1.1
-
APPS.PA_LIFECYCLES_PVT dependencies on PA_LIFECYCLES_PVT
12.2.2
-
APPS.PA_LIFECYCLES_PVT dependencies on FND_MSG_PUB
12.2.2
-
APPS.PA_LIFECYCLES_PVT dependencies on FND_MSG_PUB
12.1.1
-
APPS.PA_LIFECYCLES_PVT dependencies on FND_API
12.1.1
-
APPS.PA_LIFECYCLES_PUB dependencies on FND_MSG_PUB
12.1.1
-
APPS.PA_LIFECYCLES_PVT dependencies on FND_API
12.1.1
-
APPS.PA_LIFECYCLES_PVT dependencies on FND_API
12.2.2
-
APPS.PA_LIFECYCLES_PUB dependencies on FND_MSG_PUB
12.2.2
-
APPS.PA_LIFECYCLES_PUB dependencies on PA_LIFECYCLES_PUB
12.2.2
-
APPS.PA_LIFECYCLES_PUB dependencies on PA_LIFECYCLES_PUB
12.1.1
-
APPS.PA_LIFECYCLES_PVT dependencies on FND_API
12.2.2
-
APPS.PA_LIFECYCLES_PUB dependencies on FND_API
12.2.2
-
APPS.PA_LIFECYCLES_PUB dependencies on FND_API
12.1.1
-
APPS.PA_LIFECYCLES_PUB dependencies on FND_API
12.2.2
-
APPS.PA_LIFECYCLES_PUB dependencies on FND_API
12.1.1
-
APPS.PA_LIFECYCLES_PVT dependencies on PA_DEBUG
12.1.1
-
APPS.PA_LIFECYCLES_PUB dependencies on PA_DEBUG
12.2.2
-
APPS.PA_LIFECYCLES_PVT dependencies on PA_DEBUG
12.2.2
-
APPS.PA_LIFECYCLES_PUB dependencies on PA_DEBUG
12.1.1