Search Results az_processes_u1

Overview

AZ.AZ_PROCESSES is a valid Oracle E-Business Suite table owned by the AZ schema (FND Design Data: AZ.AZ_PROCESSES) that stores information about the runnable workflow processes associated with different context names and context types. In EBS 12.1.1 and 12.2.2, this table functions as the catalogue of processes presented through the Implementation Wizard, allowing implementers and administrators to track which workflow processes exist, which organizational context they apply to, and whether each process has been started, completed, or left inactive.

Each row represents a single process within a specific context. The table records the item type, process name, context ID, context name and context type, together with the complete flag, the parent process group it belongs to, its display order in the hierarchy tree, and any user-entered comments captured from the Implementation Wizard form. From a heuristic Data Vault perspective, the mined FK structure classifies this object as satellite-leaning: it holds descriptive and state attributes keyed to a business key, anchored to a group/hierarchy parent rather than acting as a pure transactional hub.

Key Information Stored

The table is defined with eleven columns stored in the APPS_TS_ARCHIVE tablespace (PCT Free 10). The documented primary key is AZ_PROCESSES_PK over (ITEM_TYPE, PROCESS_NAME, CONTEXT_ID), which is also the business-key candidate enforced by the unique index AZ_PROCESSES_U1 on the same three columns. There is no separate surrogate key column in the documented schema, so the primary key columns serve as the identifying business key.

• ITEM_TYPE – Workflow item type; part of AZ_PROCESSES_PK and AZ_PROCESSES_U1.
• PROCESS_NAME – Internal name of the process activity; part of the primary key and unique index.
• CONTEXT_ID – Context identifier; part of the primary key and unique index.
• CONTEXT_NAME – Human-readable name of the context (up to 80 characters).
• CONTEXT_TYPE – Context classification: BG for business group, IO for inventory organization, OU for operating unit, SOB for set of books.
• PROCESS_TYPE – Indicates whether the process belongs to a fresh implementation or an upgrade; indexed non-uniquely via AZ_PROCESSES_N1 alongside PARENT_ID.
• STATUS_CODE – Process status: A for Active, N for Not Started, C for Complete.
• COMPLETE_FLAG – Flag indicating whether the process is complete.
• PARENT_ID – Parent process group the process is associated with; foreign key to AZ_GROUPS and part of the AZ_PROCESSES_N1 index.
• DISPLAY_ORDER – Sequence of the process within the hierarchy tree.
• COMMENTS – User-entered comments (up to 2000 characters) captured from the Implementation Wizard form.

Common Use Cases and Queries

The most common access path is by primary key or by parent group. The AZ_PROCESSES_N1 index on (PARENT_ID, PROCESS_TYPE) supports retrieval of all child processes under a given group, which is the standard pattern for rendering the Implementation Wizard hierarchy tree. The AZ_PROCESSES_U1 unique index supports point lookups for a specific item type and process within a context — the lookup pattern implied by the user's search term az_processes_u1.

• Context-filtered process listing: SELECT PROCESS_NAME, CONTEXT_TYPE, CONTEXT_NAME, STATUS_CODE FROM AZ.AZ_PROCESSES WHERE CONTEXT_ID = :p_context_id AND CONTEXT_TYPE = 'OU'.
• Hierarchy reconstruction: SELECT PROCESS_NAME, PARENT_ID, DISPLAY_ORDER FROM AZ.AZ_PROCESSES WHERE PARENT_ID = :p_parent ORDER BY DISPLAY_ORDER.
• Completion reporting: SELECT ITEM_TYPE, PROCESS_NAME, COMPLETE_FLAG FROM AZ.AZ_PROCESSES WHERE COMPLETE_FLAG = 'N'.
• Implementation vs. upgrade split: aggregate counts by PROCESS_TYPE to assess the mix of fresh-implementation and upgrade processes configured.
• Status dashboard: GROUP BY STATUS_CODE to summarise Active, Not Started, and Complete processes per context.

Related Objects

• AZ.AZ_GROUPS — Referenced through the foreign key AZ_PROCESSES.PARENT_ID → AZ_GROUPS. This is the primary parent/child relationship, joining on the group identifier to resolve the process hierarchy.
• AZ.AZ_PROCESSES_PK — The primary key constraint over (ITEM_TYPE, PROCESS_NAME, CONTEXT_ID), enforcing row uniqueness.
• AZ.AZ_PROCESSES_U1 — The unique index over (ITEM_TYPE, PROCESS_NAME, CONTEXT_ID); the business-key access path.
• AZ.AZ_PROCESSES_N1 — The non-unique index over (PARENT_ID, PROCESS_TYPE), supporting hierarchy and process-type queries.
• FND Design Data (AZ.AZ_PROCESSES) — The application registration under which the table and its dependent wizard forms are delivered.

The Implementation Wizard form and the workflows it drives reference this table to display, launch, and update process state. Because AZ_PROCESSES is satellite-leaning and keyed by context, any process modification should be performed through the supported wizard or API rather than by direct DML, preserving the integrity of the primary key and the parent-group relationship.