Search Results inst_serial_number

Overview

APPS.AHL_UC_DETAILS_FOR_HGRID is a global temporary table within the Oracle E-Business Suite 12.1.1 / 12.2.2 ETRM (Enterprise Asset Management and Maintenance) schema. It belongs to the AHL application module, which supports complex asset hierarchies, upgrade configuration, and disposition processing. The table serves as a transient staging structure that materializes hierarchical grid (h-grid) node details used by the user interface when displaying and manipulating asset instance trees, upgrade paths, and disposition workflows.

As a global temporary table, the current session can see only data it placed in the table; other sessions cannot access that data. Its data duration is defined as SYS$TRANSACTION, meaning rows are removed upon transaction commit or rollback. This behavior makes the object ideal for session-scoped scratch data used during interactive tree rendering and bulk disposition operations without persisting intermediate results permanently.

From a modeling perspective, the heuristic Data Vault classification is standalone. This designation reflects that the table does not act as a durable hub, link, or satellite but rather functions as a transient, session-scoped working set. It should not be treated as a permanent integration point for downstream data vault modeling.

Key Information Stored

The table contains 72 documented columns. The most significant columns, grounded in the ETRM metadata, include:

• UNIT_NODE_ID — The surrogate primary key, enforced by unique index SYS_C00990626. It uniquely identifies each node within the hierarchical grid for the session.
• ROOT_INSTANCE_ID — Identifies the root instance of the asset hierarchy being displayed.
• PARENT_INSTANCE_ID / PARENT_INSTANCE_NUMBER — Reference the parent instance in the tree structure, supporting recursive navigation.
• NODE_LEVEL / HGRID_NODE_PATH / NOT_LEAF_NODE_FLAG — Define the node's position and depth within the hierarchy, enabling grid rendering logic.
• CURR_INSTANCE_ID / CURR_ITEM_ID / CURR_SERIAL_NUMBER — Describe the current instance, item, and serial number represented by the node.
• DISPOSITION_ID / DISPOSITION_OBJ_VER_NUM / DISPOSITION_STATUS — Capture disposition reference data, object version, and the disposition status (the term the user searched for). DISPOSITION_ID and DISPOSITION_OBJ_VER_NUM are foreign keys to AHL_PRD_DISPOSITIONS_B.
• DISPOSITION_QTY / DISPOSITION_COUNT — Store the quantity and count associated with disposition actions.
• IMMEDIATE_DISPOSITION_CODE / SECONDARY_DISPOSITION_CODE — Hold coded disposition outcomes for immediate and secondary processing.
• SEVERITY_ID / SEVERITY_NAME — Link to CSS_DEF_SEVERITIES_B for severity classification of the issue driving disposition.
• SERVICE_TYPE / SERVICE_TYPE_ID — Reference ZX_SERVICE_TYPES for the service type applicable to the node.

Business-key candidates are limited to the unique index on UNIT_NODE_ID; no other unique constraints are documented.

Common Use Cases and Queries

Typical usage centers on session-scoped queries that build or inspect an asset hierarchy before committing disposition changes. A representative query retrieves node details for a given root instance:

SELECT unit_node_id, node_level, hgrid_node_path, curr_instance_number, disposition_status, disposition_qty FROM apps.ahl_uc_details_for_hgrid WHERE root_instance_id = :p_root_instance_id AND not_leaf_node_flag = 'N' ORDER BY hgrid_node_path;

Reporting use cases include verifying disposition status distribution across a tree, auditing nodes with immediate versus secondary disposition codes, and validating severity and service type mapping prior to bulk disposition processing. Because the table is transaction-scoped, queries must execute within the same session that populated the table.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

• AHL_PRD_DISPOSITIONS_B — Joined via DISPOSITION_ID to resolve disposition definitions and object versions.
• AHL_MC_PATH_POSITIONS — Joined via PATH_POSITION_ID to resolve path position metadata.
• AHL_PART_CHANGES — Joined via PART_CHANGE_ID for part change context.
• CSS_DEF_SEVERITIES_B — Joined via SEVERITY_ID for severity definitions.
• ZX_SERVICE_TYPES — Joined via SERVICE_TYPE_ID for service type lookup.

These relationships position AHL_UC_DETAILS_FOR_HGRID as a transient integration point among disposition, hierarchy, severity, and service type data within the AHL module.