Search Results pa_lifecycle_usages_u1

Overview

PA.PA_LIFECYCLE_USAGES is a transaction data table in the Oracle E-Business Suite Projects (PA) schema. It stores the usage type assignments associated with a project lifecycle definition, effectively recording which usage categories — for example PRODUCT or PROJECT — are valid for a given lifecycle. A lifecycle in Oracle Projects governs the set of statuses and transitions that a project, task, or other project element passes through during its existence. The usage type attached at this level determines the business context in which the lifecycle applies. The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and its indexes are placed in APPS_TS_TX_IDX, reflecting a standard transactional configuration.

From a Data Vault modeling perspective, the mined heuristic classifies PA_LIFECYCLE_USAGES as satellite-leaning. Its primary key, LIFECYCLE_USAGE_ID, is a surrogate identifier, while LIFECYCLE_ID acts as a foreign key to PA_PROJ_ELEMENTS. This pattern suggests the table behaves as a descriptive child of a lifecycle hub, carrying the attribute USAGE_TYPE plus standard audit columns. Modeling this as a satellite attached to a lifecycle hub is therefore a reasonable design suggestion, though the table also exhibits link-like characteristics through its relationship to PA_PROJ_ELEMENTS.

Key Information Stored

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

• LIFECYCLE_USAGE_ID — NUMBER(15), the primary key and the column indexed by the unique index PA_LIFECYCLE_USAGES_U1. This is the surrogate identifier and the most likely business-key candidate for unique row resolution.
• LIFECYCLE_ID — NUMBER(15), a foreign key to PA_PROJ_ELEMENTS. It ties each usage record to a specific lifecycle definition and is indexed by the non-unique index PA_LIFECYCLE_USAGES_N1.
• USAGE_TYPE — VARCHAR2(30), holding the lookup code for the usage type, such as PRODUCT or PROJECT. This is the primary descriptive attribute of the row.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who columns that provide audit trail and multi-user concurrency context.
• RECORD_VERSION_NUMBER — NUMBER(15), a sequence number used for the optimistic locking strategy.

No mandatory flags are documented for individual columns; the primary key constraint establishes uniqueness on LIFECYCLE_USAGE_ID.

Common Use Cases and Queries

The principal use case is determining which usage types are permitted for a given lifecycle. A typical query joins PA_LIFECYCLE_USAGES to PA_PROJ_ELEMENTS on LIFECYCLE_ID to resolve lifecycle metadata:

• Enumerating usage types for a lifecycle: SELECT lifecycle_id, usage_type FROM pa.pa_lifecycle_usages WHERE lifecycle_id = :id;
• Joining to parent project elements: SELECT u.usage_type, e.* FROM pa.pa_lifecycle_usages u JOIN pa.pa_proj_elements e ON u.lifecycle_id = e.element_id;
• Audit and change-tracking reports using LAST_UPDATE_DATE, LAST_UPDATED_BY, and RECORD_VERSION_NUMBER.
• Data validation extracts confirming that USAGE_TYPE values match the expected lookup codes for PRODUCT and PROJECT.

Because PA_LIFECYCLE_USAGES_U1 is unique on LIFECYCLE_USAGE_ID, it supports point lookups by surrogate key, while PA_LIFECYCLE_USAGES_N1 accelerates access by LIFECYCLE_ID for parent-driven browsing and reporting.

Related Objects

The most significant related objects, based on the documented foreign key and reference data, are:

• PA.PA_PROJ_ELEMENTS — referenced by LIFECYCLE_ID; the parent entity supplying lifecycle definitions.
• APPS.PA_LIFECYCLE_USAGES — the APPS-layer synonym/view through which the base table is typically accessed.
• PA.PA_LIFECYCLE_USAGES_U1 — the unique index on LIFECYCLE_USAGE_ID supporting key-based access.
• PA.PA_LIFECYCLE_USAGES_N1 — the non-unique index on LIFECYCLE_ID supporting parent joins.
• FND lookup tables — supply the valid lookup codes for USAGE_TYPE.

These relationships position PA_LIFECYCLE_USAGES as a dependent detail table within the Projects lifecycle configuration model.