Search Results ahl_mc_path_position_nodes_pk

Overview

The AHL_MC_PATH_POSITION_NODES table is a core data object within the AHL (Complex Maintenance Repair and Overhaul) product family of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. Its documented purpose is to store Path Position Nodes — the discrete steps that make up a path position definition used in complex MRO routing, overhaul workflow modeling, and maintenance execution sequencing. Each row represents a single node occupying an ordered slot within a parent path position, allowing maintenance planners to define multi-step operations such as disassembly, inspection, repair, reassembly, and test sequences.

From a Data Vault modeling perspective, the FK structure mined from the schema suggests a satellite-leaning classification. The table carries a surrogate primary key, descriptive attributes, and the standard EBS audit and attribute-flex columns characteristic of a satellite that hangs off the PATH_POSITION business key. It does not behave as a pure hub (no independent business key of its own) nor as a pure link, since it stores descriptive and sequencing attributes rather than resolving a many-to-many relationship.

Key Information Stored

The table exposes 29 documented columns. The most significant are outlined below.

• PATH_POSITION_NODE_ID — the surrogate primary key, defined by AHL_MC_PATH_POSITION_NODES_PK and reinforced by unique index U1. This is the row identifier referenced by downstream child tables.
• PATH_POSITION_ID — foreign key to the parent path position; the business anchor of the satellite.
• SEQUENCE — the ordinal position of the node within its parent path position. Along with PATH_POSITION_ID it forms unique index U2, the primary business-key candidate that prevents duplicate ordering within a path.
• MC_ID — identifier linking the node to the maintenance/overhaul context.
• VERSION_NUMBER — supports versioned definitions of the parent path position.
• POSITION_KEY — the human-meaningful position code or key used at execution time.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org / data-security partitioning.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS who-column audit set.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (Descriptive Flexfield) block, enabling customer-specific extensions without schema change.

Common Use Cases and Queries

Typical usage centers on retrieving the ordered node list for a given path position, validating that sequence values are unique, and joining node data to parent path metadata for reporting.

• List all nodes for a path position in execution order:

SELECT path_position_node_id, sequence, position_key, mc_id
FROM   ahl.ahl_mc_path_position_nodes
WHERE  path_position_id = :p_path_position_id
ORDER  BY sequence;

• Detect duplicate or missing sequence numbers within a path position (data-quality reporting).
• Version comparison: filter by VERSION_NUMBER to identify node changes between revisions.
• Security-scoped extracts: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to limit output by operating unit.
• Flexfield reporting: query ATTRIBUTE_CATEGORY plus the relevant ATTRIBUTEn columns for customer-defined node classifications.

Related Objects

The FK and UK metadata pin the most significant related objects:

• AHL_MC_PATH_POSITIONS — the parent entity; join on PATH_POSITION_ID from child to parent PK.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID to enforce data-level security.
• AHL_MC_PATH_POSITION_NODES_PK / _U1 / _U2 — the primary key and unique indexes that define node identity and business-key uniqueness.
• AHL_MC_* sibling MRO tables sharing the MC_ID context (e.g., path, position, and route definition tables).
• FND_* audit and flexfield infrastructure — LAST_UPDATED_BY / CREATED_BY resolve to FND_USER; the attribute block is served by the standard DFF framework.