Results for “sibling_rules_flag”

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

Overview

The AHL.AHL_RELATIONSHIPS_B table belongs to the AHL - Complex Maintenance Repair and Overhaul product module in Oracle E-Business Suite. It stores the position hierarchy of the master configuration, capturing the structural relationships that define how positions within a configuration relate to one another in a parent-child arrangement. Per the ETRM documentation, this object is an obsoleted table as of release 11.5.10, meaning it is retained for historical and backward-compatibility purposes rather than for active transactional processing in EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the heuristic classification for AHL_RELATIONSHIPS_B is hub. This classification is inferred from its role as the central anchor of the relationship graph, holding the unique RELATIONSHIP_ID and serving as the target of multiple foreign key references from downstream entities. The table functions as a master reference for the configurable position structure that other AHL business objects consume.

Key Information Stored

The primary key of the table is AHL_RELATIONSHIPS_B_PK, defined on the surrogate identifier RELATIONSHIP_ID. A unique index, AHL_RELATIONSHIPS_B_U1, is also defined on RELATIONSHIP_ID, while AHL_RELATIONSHIPS_B_UK1 provides an additional business-key candidate on NAME. Notable columns include:

• RELATIONSHIP_ID — surrogate primary key identifying each relationship node.
• PARENT_RELATIONSHIP_ID — self-referencing foreign key that establishes the recursive hierarchy of positions.
• NAME — business identifier for the relationship node; a candidate unique key.
• POSITION_REF_CODE — reference code describing the position within the configuration.
• ITEM_GROUP_ID — foreign key to AHL_ITEM_GROUPS_B, linking the node to an item group.
• COUNTER_GROUP_ID — foreign key to CS_COUNTER_GROUPS, associating the node with a counter group.
• UOM_CODE and QUANTITY — unit of measure and quantity applicable to the node.
• DISPLAY_ORDER — sequencing attribute controlling presentation of sibling nodes.
• SIBLING_RULES_FLAG and COUNTER_RULE_FLAG — rule indicators governing sibling and counter behavior.
• CONFIG_STATUS_CODE, ACTIVE_START_DATE, and ACTIVE_END_DATE — lifecycle and effective-dating attributes.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for row-level security partitioning.
• POSITION_NECESSITY_CODE and NODE_STATUS_FLAG — status and necessity indicators for the node.
• Standard WHO columns (LAST_UPDATE_DATE, CREATED_BY, OBJECT_VERSION_NUMBER, and the ATTRIBUTE1–15 flexfield set).

Common Use Cases and Queries

Because the table is obsoleted, query use is largely historical or analytical. Typical patterns include reconciling the recursive position hierarchy and joining to related counter-group definitions. A representative query to traverse the self-referencing hierarchy is:

• Hierarchy traversal: SELECT r1.NAME AS node, r2.NAME AS parent FROM AHL_RELATIONSHIPS_B r1, AHL_RELATIONSHIPS_B r2 WHERE r1.PARENT_RELATIONSHIP_ID = r2.RELATIONSHIP_ID;
• Counter-group linkage: SELECT r.NAME, cg.* FROM AHL_RELATIONSHIPS_B r, CS_COUNTER_GROUPS cg WHERE r.COUNTER_GROUP_ID = cg.COUNTER_GROUP_ID;
• Item-group reporting: joining ITEM_GROUP_ID to AHL_ITEM_GROUPS_B to report position-to-item-group assignments.

Reporting use cases focus on reconstructing configuration structures for audit, migration analysis, or historical maintenance plans.

Related Objects

Several objects reference or depend on AHL_RELATIONSHIPS_B through documented foreign keys:

• AHL_RELATIONSHIPS_B (self) — via PARENT_RELATIONSHIP_ID, forming the recursive hierarchy.
• AHL_ITEM_GROUPS_B — referenced through ITEM_GROUP_ID.
• CS_COUNTER_GROUPS — referenced through COUNTER_GROUP_ID; this is the object connected to the user's search term.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID.
• AHL_RELATIONSHIPS_TL — depends on RELATIONSHIP_ID for translated names.
• AHL_EVENT_ASSOCIATIONS — references RELATIONSHIP_ID for event linkage.
• AHL_MR_EFFECTIVITIES — references RELATIONSHIP_ID for effectiveness data.
• AHL_PART_CHANGES — references MC_RELATIONSHIP_ID for part-change tracking.