Results for “az_archive”

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

Overview

AZ_ARCHIVE is a table owned by the AZ schema within the Oracle E-Business Suite, belonging to the AZ - Application Implementation product family. The documented description states that it "stores wizard data," indicating that the table functions as a persistence layer for the step-by-step configuration or setup wizards exposed through Oracle Application Implementation (formerly Application Install / Rapid Install configuration tooling). Each row represents a node within a wizard structure, capturing both the navigational context and the operational status of a given wizard step or archive entry.

The table is defined with 17 columns and is constrained by the primary key AZ_ARCHIVE_PK, which is bound to the NODE_ID column. A unique index, AZ_ARCHIVE_U1, also exists on NODE_ID, confirming it as the singular business-key candidate in the documented schema. From a heuristic Data Vault modeling perspective, the FK structure — a self-referencing parent/child relationship plus child references from AZ_ARCHIVE_STEPS — suggests a hub-leaning classification, with AZ_ARCHIVE acting as the central node entity to which dependent satellite-style step records attach. This classification should be treated as a modeling suggestion rather than a normative design statement.

Key Information Stored

The table's most significant columns describe node identity, context, workflow state, and ownership:

• NODE_ID — The surrogate primary key and the single documented business-key candidate (via AZ_ARCHIVE_U1). Uniquely identifies each wizard node or archive record.
• PARENT_NODE_ID — Self-referencing foreign key to AZ_ARCHIVE.NODE_ID, enabling a hierarchical tree of wizard nodes.
• NODE_NAME and NODE_TYPE — The descriptive label and structural classification of the node within the wizard tree.
• CONTEXT_TYPE, CONTEXT_TYPE_NAME, CONTEXT_ID, and CONTEXT_NAME — The contextual anchor (type, identifier, and display names) that scopes the wizard data to a particular setup or configuration context.
• STATUS_CODE and STATUS_NAME — The workflow state of the node, distinguishing completed, in-progress, or pending wizard steps.
• ITEM_KEY — A logical key correlating the archive record to the underlying wizard item.
• ASSIGNED_USER and ASSIGNED_USER_NAME — The user accountable for the node's completion.
• START_DATE, END_DATE, and DURATION — Temporal tracking of when a wizard step began, ended, and how long it took.
• COMMENTS — Free-text annotation captured during the wizard run.

Common Use Cases and Queries

Typical usage centers on audit and progress reporting for implementation wizards. Analysts traverse the node hierarchy to reconstruct the sequence of configured steps, identify stalled nodes, and measure elapsed time. A common pattern joins each node to its parent and its associated steps:

SELECT a.NODE_ID, a.NODE_NAME, a.STATUS_NAME,
       a.ASSIGNED_USER_NAME, a.DURATION,
       s.NODE_ID AS STEP_NODE_ID
FROM   AZ.AZ_ARCHIVE a
LEFT   JOIN AZ.AZ_ARCHIVE_STEPS s ON s.NODE_ID = a.NODE_ID
WHERE  a.PARENT_NODE_ID = :parent_id
ORDER BY a.START_DATE;

Recursive hierarchical queries (CONNECT BY PRIOR NODE_ID = PARENT_NODE_ID) are frequently used to expand the full wizard tree. Reporting use cases include duration analysis by node type, outstanding-node dashboards filtered on STATUS_CODE, and attribution reports grouped by ASSIGNED_USER. Because CONTEXT_ID scopes records, multi-context filtering is essential in any report to avoid cross-contamination between setup efforts.

Related Objects

• AZ_ARCHIVE_STEPS — The principal dependent table. Its NODE_ID column references AZ_ARCHIVE, defining the step-level detail beneath each archived node.
• AZ_ARCHIVE (self-reference) — Via PARENT_NODE_ID, the table references itself to model the node hierarchy; recursive queries on this relationship are the standard traversal mechanism.
• AZ_ARCHIVE_PK — The primary key constraint on NODE_ID, guaranteeing node uniqueness.
• AZ_ARCHIVE_U1 — The unique index on NODE_ID, reinforcing the business-key candidate status of the column.

Because the ETRM metadata documents only these relationships, all join logic should be grounded in the NODE_ID and PARENT_NODE_ID columns rather than assumed foreign keys to other AZ schema objects.