Search Results az_processes_pk

Overview

The AZ_PROCESSES table is a repository of Workflow process information owned by the AZ schema, which falls under the AZ – Application Implementation product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores definitions of the workflow-driven processes that participate in the application implementation lifecycle, including process typing, ordering, and status tracking. Because the AZ module governs implementation and setup activities, this table underpins the metadata that drives configuration and process sequencing during an EBS deployment.

From a Data Vault modeling perspective, the heuristic classification of this object is satellite-leaning. The primary key is composite rather than a single surrogate identifier, and the table carries descriptive, non-key attributes (status, display order, comments) that describe a business entity rather than merely linking two hubs. This suggests it is best modeled as a satellite that captures attributes of an underlying process definition, though the presence of a self-referencing/foreign hierarchy via PARENT_ID introduces limited link-like behaviour that should be considered when building a warehouse model.

Key Information Stored

The table contains 11 documented physical columns in the ETRM 12.2.2 schema. The most significant columns are:

• ITEM_TYPE – The workflow item type that anchors the process definition; part of the composite primary key.
• PROCESS_NAME – The unique name identifying the workflow process; part of the composite primary key.
• CONTEXT_ID – A context discriminator (typically a context-organization or configuration scope); completes the composite primary key.
• PROCESS_TYPE – Categorizes the process; also referenced as a foreign key relationship to AZ_GROUPS.
• PARENT_ID – Establishes a hierarchical/containment link to AZ_GROUPS, indicating the group under which the process is organized.
• DISPLAY_ORDER – Controls the sequence in which processes are presented in implementation flows.
• STATUS_CODE – Current lifecycle status of the process definition.
• CONTEXT_TYPE and CONTEXT_NAME – Describe the context classification and its human-readable name, supporting multi-context deployments.
• COMPLETE_FLAG – Indicates whether the process has been completed.
• COMMENTS – Free-text annotations attached to the process.

The surrogate/business key is AZ_PROCESSES_PK over (ITEM_TYPE, PROCESS_NAME, CONTEXT_ID). A unique index, AZ_PROCESSES_U1, exists on the same three columns, confirming that this triple is the true business-key candidate and enforcing uniqueness independent of any generated surrogate.

Common Use Cases and Queries

Typical scenarios include identifying all processes attached to a given item type, auditing process status, and reconstructing the group hierarchy. A common query returns processes with their parent group:

• SELECT p.ITEM_TYPE, p.PROCESS_NAME, p.STATUS_CODE, g.* FROM AZ.AZ_PROCESSES p JOIN AZ.AZ_GROUPS g ON p.PARENT_ID = g.??
• Filtering by context: WHERE p.CONTEXT_ID = :ctx AND p.CONTEXT_TYPE = :ctx_type.
• Ordering for display: ORDER BY p.DISPLAY_ORDER.

Reporting use cases include completion tracking (COMPLETE_FLAG), status dashboards (STATUS_CODE), and BIPublisher extracts that list implementation processes by group and item type.

Related Objects

• AZ_GROUPS – referenced by AZ_PROCESSES.PARENT_ID and AZ_PROCESSES.PROCESS_TYPE; the primary hierarchical parent.
• AZ_PROCESSES_PK – primary key constraint and index.
• AZ_PROCESSES_U1 – unique index on (ITEM_TYPE, PROCESS_NAME, CONTEXT_ID).
• Workflow runtime tables (e.g., WF_ITEM_TYPES, WF_PROCESS_ACTIVITIES) that consume the ITEM_TYPE value.
• AZ configuration/context tables keyed by CONTEXT_ID/CONTEXT_TYPE.

These relationships make AZ_PROCESSES a central metadata node for implementation workflows in EBS.