Search Results pa_lifecycle_usages_pk

Overview

PA_LIFECYCLE_USAGES is a Projects (PA) module table in Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It stores information about the usage types associated with an existing project lifecycle. In the EBS project management data model, a lifecycle defines the sequence of phases and gates that a project passes through, and this table records how each lifecycle is used — for example, whether it is designated for a specific usage context such as a project template, a contract project, or a capital project.

From a dimensional modeling perspective, the ETRM data vault classification for this object is satellite-leaning. This classification is a heuristic suggestion: the table behaves as a satellite attached to a parent hub, since its primary key is a surrogate identifier and its principal foreign key points upward to a lifecycle parent. It carries descriptive and versioning attributes about lifecycle usage rather than representing an independent business entity or an associative link between two hubs.

Key Information Stored

The table contains nine documented columns. The most significant are:

• LIFECYCLE_USAGE_ID — The surrogate primary key, enforced by PA_LIFECYCLE_USAGES_PK and also backed by the unique index PA_LIFECYCLE_USAGES_U1. This is the technical row identifier, not a business key.
• LIFECYCLE_ID — The foreign key referencing PA_PROJ_ELEMENTS, identifying the lifecycle to which the usage record belongs. This is the join path to the parent lifecycle definition.
• USAGE_TYPE — The descriptive attribute identifying the category of usage for the lifecycle. This is the column that gives the table its name and business purpose.
• CREATION_DATE and CREATED_BY — Standard EBS audit columns recording when and by whom the row was created, based on the FND_STANDARD audit convention.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification, its actor, and the login session responsible.
• RECORD_VERSION_NUMBER — An optimistic locking / concurrency control column used by the application to detect conflicting updates.

The only documented unique index, PA_LIFECYCLE_USAGES_U1, is on LIFECYCLE_USAGE_ID, meaning no separate business-key candidate is exposed in the provided metadata. LIFECYCLE_ID carries a foreign key but is not documented as unique, implying a lifecycle may have multiple usage rows.

Common Use Cases and Queries

Typical usage centers on determining which lifecycles can be applied in a given project context. For example, retrieving all usage types for a lifecycle:

• SELECT usage_type FROM pa_lifecycle_usages WHERE lifecycle_id = :lifecycle_id;
• Joining to the parent lifecycle definition in PA_PROJ_ELEMENTS on LIFECYCLE_ID to resolve lifecycle names and attributes.
• Reporting query enumeration of lifecycles filtered by a specific USAGE_TYPE to support project template setup and validation.
• Audit-style queries selecting CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE for data governance review.

Because the row set is small and configuration-oriented, these queries are typically used in setup validation, migration scripts, and configuration reports rather than high-volume transaction processing.

Related Objects

The most significant relationships for this object are:

• PA_PROJ_ELEMENTS — The parent referenced through PA_LIFECYCLE_USAGES.LIFECYCLE_ID, providing the lifecycle definition and likely lifecycle name.
• PA_LIFECYCLE_USAGES_PK — The primary key constraint on LIFECYCLE_USAGE_ID.
• PA_LIFECYCLE_USAGES_U1 — The unique index, also on LIFECYCLE_USAGE_ID.

Beyond these documented links, Projects lifecycle setup screens and related lifecycle configuration tables in the PA schema depend on this table to constrain and populate the available usage types presented to users. Any custom reporting or integration touching project lifecycle configuration should reference PA_LIFECYCLE_USAGES through its LIFECYCLE_ID join to PA_PROJ_ELEMENTS.