Search Results az_groups_pk




Overview
Explore in AI Chat

Overview

AZ_GROUPS is a transactional configuration table owned by the AZ schema (Application Implementation product) in Oracle EBS 12.1.1 and 12.2.2. It stores process group definitions used by Oracle Application Implementation's setup and process modeling framework, which organizes the many setup steps, product flows, and dependencies required to implement an EBS instance. Each row represents a group of processes that share a common behavior, ordering, and dependency relationship within the implementation lifecycle.

The ETRM metadata classifies AZ_GROUPS as hub-leaning under a heuristic Data Vault model. This is a modeling suggestion rather than a physical constraint: the table acts as a hub because it is a self-referencing entity referenced by other process tables (AZ_PROCESSES, AZ_PRODUCT_FLOWS), and because its primary key is a business-meaningful composite rather than a pure surrogate. A Data Vault implementation could reasonably treat AZ_GROUPS as a hub with satellites for the descriptive attributes such as color, display order, and lookup values.

Key Information Stored

The table has 16 documented columns. The composite primary key, AZ_GROUPS_PK, is defined on GROUP_ID and PROCESS_TYPE, and a unique index AZ_GROUPS_U1 also covers (GROUP_ID, PROCESS_TYPE), confirming this combination as the business key. GROUP_ID is the identifier for a process group; PROCESS_TYPE distinguishes the category or flavor of group (for example, a setup process versus a flow process) so that the same GROUP_ID can exist across multiple process types without collision.

Self-referencing columns encode the group's position in the process graph. HIERARCHY_PARENT_ID and HIERARCHY_PARENT_PROCESS_TYPE together identify the parent group in a hierarchical (containment) relationship, while DEPENDENCY_PARENT_ID and DEPENDENCY_PARENT_PROCESS_TYPE identify a parent in a sequencing or prerequisite relationship. Both pairs point back into AZ_GROUPS itself, forming recursive foreign keys.

Descriptive and control columns include DISPLAY_ORDER, which controls presentation sequence in the implementation UI; COLOR_CODE, used for visual differentiation of groups; COMPLETE_FLAG, indicating whether the group has been completed; and LOOKUP_CODE, linking the row to a lookup value. APPLICATION_ID associates the group with a specific EBS application. Standard audit columns—CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN—support change tracking and WHO-column auditing.

Common Use Cases and Queries

Typical uses include reporting setup progress across a multi-application implementation, tracing prerequisite chains before executing a process, and reconstructing the hierarchy of process groups for a given product. A hierarchical query retrieves the parent chain:

  • SELECT GROUP_ID, PROCESS_TYPE, HIERARCHY_PARENT_ID FROM AZ.AZ_GROUPS START WITH GROUP_ID = :id CONNECT BY PRIOR GROUP_ID = HIERARCHY_PARENT_ID AND PRIOR PROCESS_TYPE = HIERARCHY_PARENT_PROCESS_TYPE;
  • Completion reporting: SELECT APPLICATION_ID, COUNT(*) FROM AZ.AZ_GROUPS WHERE COMPLETE_FLAG = 'Y' GROUP BY APPLICATION_ID;
  • Ordering a group listing: SELECT GROUP_ID, PROCESS_TYPE, DISPLAY_ORDER, COLOR_CODE FROM AZ.AZ_GROUPS ORDER BY DISPLAY_ORDER;

Because both FK pairs are composite, joins must include both the ID column and the matching PROCESS_TYPE column; omitting PROCESS_TYPE risks incorrect matches.

Related Objects

AZ_GROUPS participates in a tightly coupled graph with several AZ objects:

  • AZ_GROUPS (self-reference) via HIERARCHY_PARENT_ID/HIERARCHY_PARENT_PROCESS_TYPE and DEPENDENCY_PARENT_ID/DEPENDENCY_PARENT_PROCESS_TYPE — defines containment and prerequisite relationships.
  • AZ_PROCESSES via PARENT_ID/PROCESS_TYPE — processes belonging to a group.
  • AZ_PRODUCT_FLOWS via PARENT_ID/PROCESS_TYPE — product flow definitions anchored to a group.
  • AZ_GROUPS_PK and AZ_GROUPS_U1 enforce uniqueness on GROUP_ID and PROCESS_TYPE.

These relationships establish AZ_GROUPS as a central hub for implementation process configuration, referenced by both the process and product-flow tables that consume its grouping structure.