Results for “phase_id”

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

Overview

EGO_LCPHASE_POLICY is a table in the EGO schema, owned by the Advanced Product Catalog (APC) module of Oracle E-Business Suite. Within the documented ETRM metadata for release 12.2.2, the table is explicitly flagged as obsoleted. This designation means that while the physical object may still exist in upgraded environments (status VALID at the database level), it is no longer an active component of the functional data model and should not be relied upon for new development, customization, or integration work. The table historically supported lifecycle phase policy configuration, governing how items transition through defined lifecycle phases in the product information management lifecycle.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone. This implies the table operates primarily as an independent reference or configuration entity rather than as a transactional hub, link, or satellite within a dependent chain. It carries its own surrogate key and a single documented foreign key relationship, positioning it as a self-contained policy definition table.

Key Information Stored

The documented physical schema contains ten columns. The most significant include:

• PHASE_ID — the surrogate primary key identifying each policy record. This is the column most likely to participate in joins and lookups.
• ITEM_CATALOG_GROUP_ID — the sole documented foreign key, referencing MTL_ITEM_CATALOG_GROUPS_B. This associates a lifecycle phase policy with a specific item catalog group, enabling catalog-scoped policy enforcement.
• LIFECYCLE_ID — identifies the lifecycle to which the policy applies, linking the phase definition to a broader lifecycle construct.
• POLICY_CODE — a coded value representing the policy type or rule applied to the phase, such as entry criteria or approval behavior.
• ACTION_CODE — specifies the action or operation triggered when the policy condition is met during a lifecycle phase transition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns capturing who created and last modified each row and when.

Business-key candidates are not separately documented as unique indexes in the provided metadata; however, the combination of ITEM_CATALOG_GROUP_ID, LIFECYCLE_ID, POLICY_CODE, and ACTION_CODE would logically form a composite business key defining a unique policy assignment. Absent documented unique constraints, consumers should treat PHASE_ID as the reliable access path.

Common Use Cases and Queries

Because the table is obsoleted, its primary legitimate use cases are migration auditing, upgrade impact assessment, and legacy data extraction during transitions to current APC lifecycle functionality. Typical investigative query patterns include joining the policy rows to the referenced catalog group:

• Enumerating policies for a catalog group: SELECT p.PHASE_ID, p.LIFECYCLE_ID, p.POLICY_CODE, p.ACTION_CODE FROM EGO.EGO_LCPHASE_POLICY p WHERE p.ITEM_CATALOG_GROUP_ID = :group_id.
• Joining to the catalog group master for validation: SELECT p.*, g.SEGMENT1 FROM EGO.EGO_LCPHASE_POLICY p, MTL_ITEM_CATALOG_GROUPS_B g WHERE p.ITEM_CATALOG_GROUP_ID = g.CATALOG_GROUP_ID.
• Auditing orphaned or stale policy rows by comparing CREATION_DATE and LAST_UPDATE_DATE against current lifecycle definitions.

Reporting use cases are limited and generally retrospective, focused on understanding pre-upgrade configuration rather than ongoing operations.

Related Objects

The most significant related object is MTL_ITEM_CATALOG_GROUPS_B, the direct foreign-key target via ITEM_CATALOG_GROUP_ID, with its _TL and _VL siblings used for translated and view-level catalog group data. Lifecycle definitions referenced through LIFECYCLE_ID typically reside in the EGO lifecycle tables. Related EGO objects include EGO_LIFECYCLE_DEFINITIONS, EGO_LIFECYCLE_PHASES, and the APC lifecycle APIs that now supersede this table's function. Integrators should verify current replacement structures in Oracle's lifecycle management documentation before attempting to reproduce any behavior formerly governed by EGO_LCPHASE_POLICY.