Results for “az_product_phases”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AZ_PRODUCT_PHASES is a table in the AZ schema, which belongs to the Application Implementation product family in Oracle E-Business Suite. Its documented purpose is to store phase information for each installed product. In EBS Release 12.1.1 and 12.2.2, the AZ schema is associated with the Application Implementation (formerly Application Install) infrastructure used during rapid installation, upgrade, and patching of the E-Business Suite technology stack and its registered products.

The table is classified as VALID in the ETRM metadata and contains seven documented physical columns in the 12.2.2 schema definition. It is a narrow, product-scoped reference table whose grain is one row per installed product, keyed by APPLICATION_ID. From a Data Vault modeling perspective, the heuristic classification is standalone, meaning the mined foreign-key structure reveals no dependent relationships that would justify treating this object as a hub, link, or satellite within a formal Data Vault model. It is best treated as an isolated reference or control table rather than as a component in a connected dimensional or Data Vault topology.

Key Information Stored

The table's column set is small and focused, which reflects its role as a lightweight status and phase tracker rather than a transactional store. The documented columns are:

• APPLICATION_ID — The product identifier for the installed application. This column is both the primary key (AZ_PRODUCT_PHASES_PK) and a business-key candidate via the unique index AZ_PRODUCT_PHASES_U1, meaning the table permits at most one phase row per product.
• PHASE — The current implementation or installation phase for the product. This is the principal descriptive attribute and the column most likely to be referenced in operational and diagnostic queries.
• LAST_UPDATE_DATE — The timestamp of the most recent change to the row, used for audit and change-detection reporting.
• LAST_UPDATED_BY — The user or process identifier responsible for the most recent update.
• CREATION_DATE — The timestamp when the row was first inserted, establishing when the product phase record was created.
• CREATED_BY — The user or process identifier that created the row.
• LAST_UPDATE_LOGIN — The login or session identifier associated with the last update, used for forensic tracing.

The surrogate primary key is the composite of the documented PK columns, with APPLICATION_ID serving as the decisive business key. The WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) follow the standard Oracle EBS audit convention and are populated automatically by the application framework rather than by end users.

Common Use Cases and Queries

Typical use cases involve verifying which phase each installed product has reached, auditing when phases changed, and diagnosing installation or upgrade stalls. A common query is to list all products with their current phase:

• SELECT APPLICATION_ID, PHASE, LAST_UPDATE_DATE FROM AZ.AZ_PRODUCT_PHASES ORDER BY APPLICATION_ID;
• SELECT a.APPLICATION_ID, a.PHASE, f.APPLICATION_SHORT_NAME FROM AZ.AZ_PRODUCT_PHASES a, FND_APPLICATION f WHERE a.APPLICATION_ID = f.APPLICATION_ID;
• Change-tracking queries that filter on LAST_UPDATE_DATE to identify products whose phase changed within a maintenance window.

Because the table is standalone, reporting is straightforward and typically joins outward to product metadata in FND_APPLICATION rather than to dependent child objects.

Related Objects

The most significant related objects are those that share the APPLICATION_ID product identifier or that operate within the same implementation framework:

• FND_APPLICATION — The master registry of applications; joins on APPLICATION_ID to resolve product short names and base paths.
• FND_PRODUCT_INSTALLATIONS — Tracks installed products and their status; a natural companion for phase comparison.
• FND_PRODUCT_GROUPS — Defines product groupings used during installation and upgrade.
• AD_PRODUCT_DEPENDENCIES — Records dependency relationships between products, useful when validating phase sequencing.
• AZ_PRODUCT_PHASES_PK / AZ_PRODUCT_PHASES_U1 — The primary key constraint and unique index enforcing one phase row per APPLICATION_ID.

No foreign-key relationships were mined for this object, consistent with its standalone classification; joins to other tables are therefore implicit through the shared APPLICATION_ID business key rather than enforced referentially.