Results for “assigned_user_name”

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

Overview

AZ_ARCHIVE_STEPS is a table in the AZ (Application Implementation) product schema within Oracle EBS 12.1.1 and 12.2.2. Its documented description states that it stores Wizard data pertaining to tasks. In practice, this table acts as the transactional detail layer for the Application Implementation Wizard and related archive operations, capturing the discrete steps, assignments, statuses, and timing of activities performed during an implementation or upgrade workflow.

From a Data Vault modeling perspective, the heuristic classification applied to this table is satellite-leaning. This suggests it may be best modeled as a satellite entity that describes the changing attributes and state of an activity over time, rather than as a pure hub or link. The presence of a BEGIN_DATE in the primary key, combined with a foreign key to AZ_ARCHIVE, supports this interpretation: the table captures step-level context and status history that drives from a parent wizard archive record.

Key Information Stored

The table is defined with 14 documented columns and is owned by the AZ schema. The primary key, AZ_ARCHIVE_STEPS_PK, is composed of ITEM_KEY, ACTIVITY_TYPE, STEP, and BEGIN_DATE. A unique index, AZ_ARCHIVE_STEPS_U1, covers the same four columns, making them the primary business-key candidate for uniquely identifying a step record. Notable columns include:

• ITEM_KEY — Identifies the item or unit of work being tracked; part of the primary key and unique index.
• ACTIVITY_TYPE — Classifies the kind of activity being performed; part of the key.
• STEP — Ordinal or identifier of the individual step within the activity; part of the key.
• STEP_NAME — Descriptive name of the step.
• ASSIGNED_USER / ASSIGNED_USER_NAME — The user responsible for executing the step, stored as both an identifier and a display name.
• FORM_NAME — The form or screen associated with the step.
• STATUS_CODE — Current status of the step.
• RESULT_CODE — Outcome of executing the step.
• BEGIN_DATE / END_DATE — Timestamps marking when the step started and finished.
• DURATION — Elapsed time for the step.
• COMMENTS — Free-text annotations.
• NODE_ID — Foreign key to AZ_ARCHIVE, linking the step to its parent archive record.

Common Use Cases and Queries

Typical reporting on this table answers questions about implementation progress, bottleneck identification, and user workload. A common pattern aggregates steps by status or result to show overall completion rates, while a time-based query examines DURATION to locate slow steps. Joining to AZ_ARCHIVE on NODE_ID allows the step detail to be reported alongside its parent archive context.

Representative SQL patterns include:

• A progress summary: SELECT ACTIVITY_TYPE, STATUS_CODE, COUNT(*) FROM AZ.AZ_ARCHIVE_STEPS GROUP BY ACTIVITY_TYPE, STATUS_CODE.
• A user workload view: SELECT ASSIGNED_USER_NAME, COUNT(*), SUM(DURATION) FROM AZ.AZ_ARCHIVE_STEPS GROUP BY ASSIGNED_USER_NAME.
• A parent/child join: SELECT s.ITEM_KEY, s.STEP_NAME, s.STATUS_CODE FROM AZ.AZ_ARCHIVE_STEPS s JOIN AZ.AZ_ARCHIVE a ON s.NODE_ID = a.NODE_ID.

Related Objects

The most significant relationship is the documented foreign key from AZ_ARCHIVE_STEPS.NODE_ID to the AZ_ARCHIVE table, which provides the parent archive context. This join is the primary access path for reporting step data in the context of its archive operation. Other supporting objects include the unique index AZ_ARCHIVE_STEPS_U1, which enforces the business key, and the primary key constraint AZ_ARCHIVE_STEPS_PK. Because the documented relationship data is limited, additional dependencies may exist within the AZ schema and should be confirmed against the current data dictionary.