Search Results az_groups_u1

Overview

AZ.AZ_GROUPS is a seeded Oracle E-Business Suite table owned by the AZ schema, which supports the Application Implementation Wizard (AIW) framework delivered with EBS 12.1.1 and 12.2.2. Each row in AZ_GROUPS represents a process group — a logical container of implementation tasks presented to the user during a guided setup interview. The table is registered in FND Design Data as AZ.AZ_GROUPS, resides in the APPS_TS_ARCHIVE tablespace with PCT Free 10, and is marked VALID in the ETRM repository.

The metadata classifies AZ_GROUPS as hub-leaning under a Data Vault heuristic. In modeling terms, this suggests treating GROUP_ID combined with PROCESS_TYPE as the natural hub key, with hierarchical and dependency relationships modeled as self-referencing links or recursive edges rather than as simple satellite attributes. The recursive foreign keys — AZ_GROUPS.HIERARCHY_PARENT_ID and AZ_GROUPS.DEPENDENCY_PARENT_ID, both pointing back to AZ_GROUPS — reinforce this interpretation, since the table stores both tree structure and execution prerequisites within a single physical object.

Key Information Stored

GROUP_ID (VARCHAR2 240) stores the group identifier, and PROCESS_TYPE (VARCHAR2 30) identifies the implementation type for the process — together these form the composite primary key AZ_GROUPS_PK and are the business-key candidates also enforced by unique index AZ_GROUPS_U1. HIERARCHY_PARENT_ID and HIERARCHY_PARENT_PROCESS_TYPE define the parent node in the process group tree, while DEPENDENCY_PARENT_ID and DEPENDENCY_PARENT_PROCESS_TYPE capture execution prerequisites — the process type is explicitly described as upgrade versus fresh implementation. COMPLETE_FLAG marks whether a process group is considered complete, and COLOR_CODE drives the visual presentation of the group in the Implementation Wizard form. DISPLAY_ORDER sequences groups across hierarchy levels. APPLICATION_ID links the group to an Oracle application, and LOOKUP_CODE holds the associated quickcode. The standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — provide audit lineage.

Common Use Cases and Queries

Typical usage involves reconstructing the AIW navigation tree, filtering groups by implementation type, or reporting setup completion status. The non-unique indexes AZ_GROUPS_N1 (HIERARCHY_PARENT_ID, HIERARCHY_PARENT_PROCESS_TYPE) and AZ_GROUPS_N2 (DEPENDENCY_PARENT_ID, DEPENDENCY_PARENT_PROCESS_TYPE) are the intended access paths for these queries.

• List top-level groups: SELECT GROUP_ID, DISPLAY_ORDER, COLOR_CODE FROM AZ.AZ_GROUPS WHERE HIERARCHY_PARENT_ID IS NULL ORDER BY DISPLAY_ORDER;
• Find children of a node: SELECT GROUP_ID, COMPLETE_FLAG FROM AZ.AZ_GROUPS WHERE HIERARCHY_PARENT_ID = :p_group_id AND HIERARCHY_PARENT_PROCESS_TYPE = :p_type;
• Filter by implementation type: SELECT GROUP_ID, PROCESS_TYPE FROM AZ.AZ_GROUPS WHERE PROCESS_TYPE = 'FRESH' ORDER BY DISPLAY_ORDER;
• Report incomplete groups: SELECT GROUP_ID, APPLICATION_ID, LOOKUP_CODE FROM AZ.AZ_GROUPS WHERE NVL(COMPLETE_FLAG,'N') = 'N';
• Recursive hierarchy walk: a CONNECT BY PRIOR GROUP_ID = HIERARCHY_PARENT_ID query traverses the process group tree.

Related Objects

AZ_GROUPS participates in two categories of relationships. As a parent in the AIW hierarchy, it is referenced by AZ_PROCESSES.PARENT_ID and AZ_PRODUCT_FLOWS.PARENT_ID, so process and product flow records are rooted in the groups defined here. Self-referentially, AZ_GROUPS.HIERARCHY_PARENT_ID and AZ_GROUPS.DEPENDENCY_PARENT_ID both resolve to AZ.AZ_GROUPS itself, enabling n-level nesting and cross-group dependency chains. From a querying perspective, AZ_PROCESSES is the primary child table for task-level detail beneath a group, and AZ_PRODUCT_FLOWS provides the alternate flow-oriented decomposition. The AIW form and concurrent program layer that consumes these tables present them through the standard EBS responsibility and menu structure rather than a public API.