Results for “eam_wo_relationships_n4”

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

Overview

EAM.EAM_WO_RELATIONSHIPS is a transactional table in the Oracle E-Business Suite Enterprise Asset Management (EAM) schema that persists the directed links between work orders and other maintainable objects. According to the ETRM documentation, the table "is used for holding four types of relations in EAM. They are - Scheduling Child, Costing Child, End to Start Dependency, and Follow up work order." This makes the table the central repository of work order hierarchy and dependency semantics, supporting scheduling roll-ups, cost roll-ups, network-style predecessor/successor constraints, and follow-on work order chains.

The object resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and the documented physical schema comprises 13 columns. The heuristic Data Vault classification derived from the foreign-key structure is standalone; from a modeling perspective this suggests the table may be treated as a self-contained link-style object, since it records pairwise associations between parent and child entities rather than descriptive attributes of a single entity. The primary key is enforced by EAM_WO_RELATIONSHIP_ID_PK on WO_RELATIONSHIP_ID. The object is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The columns below constitute the functional core of the table; audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) follow standard EBS conventions and are omitted from this list.

• WO_RELATIONSHIP_ID — Surrogate primary key and work order relationship identifier. This is the only column on a unique index (EAM_WO_RELATIONSHIPS_N4), so it is the documented business-key candidate as well as the single-column unique key. EAM_WO_RELATIONSHIPS_N4 is listed as NORMAL and UNIQUE on APPS_TS_TX_IDX.
• PARENT_OBJECT_ID and PARENT_OBJECT_TYPE_ID — Identifier and object type of the parent in the relationship; the upstream anchor of a scheduling, costing, or dependency link.
• CHILD_OBJECT_ID and CHILD_OBJECT_TYPE_ID — Identifier and object type of the child in the relationship; the downstream work order or object being scheduled, costed, or constrained.
• PARENT_RELATIONSHIP_TYPE — Discriminator that distinguishes the four relationship categories (Scheduling Child, Costing Child, End to Start Dependency, Follow up work order). This column participates in the EAM_WO_RELATIONSHIPS_N1 and EAM_WO_RELATIONSHIPS_N2 composite non-unique indexes.
• RELATIONSHIP_STATUS — Status of the relationship between work orders, used to constrain reporting to active versus historical links.
• TOP_LEVEL_OBJECT_ID and TOP_LEVEL_OBJECT_TYPE_ID — Identifier and type of the object at the upper end of the hierarchy. These support flattened hierarchy traversal and are indexed by EAM_WO_RELATIONSHIPS_N3 on TOP_LEVEL_OBJECT_ID plus TOP_LEVEL_OBJECT_TYPE_ID, allowing an entire work order network to be retrieved from a single anchor.

The supporting non-unique indexes are EAM_WO_RELATIONSHIPS_N1 on (PARENT_OBJECT_ID, PARENT_OBJECT_TYPE_ID, PARENT_RELATIONSHIP_TYPE), EAM_WO_RELATIONSHIPS_N2 on (CHILD_OBJECT_ID, CHILD_OBJECT_TYPE_ID, PARENT_RELATIONSHIP_TYPE), and EAM_WO_RELATIONSHIPS_N3 on (TOP_LEVEL_OBJECT_ID, TOP_LEVEL_OBJECT_TYPE_ID).

Common Use Cases and Queries

Typical scenarios include retrieving all children of a work order for scheduling or cost roll-up, traversing an end-to-start dependency network for critical-path analysis, and tracing follow-up work orders generated from a completed asset activity.

Direct child lookup (driven by N1):

• SELECT CHILD_OBJECT_ID, CHILD_OBJECT_TYPE_ID, PARENT_RELATIONSHIP_TYPE, RELATIONSHIP_STATUS FROM EAM.EAM_WO_RELATIONSHIPS WHERE PARENT_OBJECT_ID = :parent_id AND PARENT_OBJECT_TYPE_ID = :parent_type AND PARENT_RELATIONSHIP_TYPE = :relationship_type;

Reverse parent lookup (driven by N2), used to determine why a work order appears in a schedule or cost set:

• SELECT PARENT_OBJECT_ID, PARENT_OBJECT_TYPE_ID FROM EAM.EAM_WO_RELATIONSHIPS WHERE CHILD_OBJECT_ID = :child_id AND CHILD_OBJECT_TYPE_ID = :child_type AND PARENT_RELATIONSHIP_TYPE = :relationship_type;

Whole-network extraction (driven by N3), suitable for reporting a complete structure without recursive SQL:

• SELECT WO_RELATIONSHIP_ID, PARENT_OBJECT_ID, CHILD_OBJECT_ID, PARENT_RELATIONSHIP_TYPE FROM EAM.EAM_WO_RELATIONSHIPS WHERE TOP_LEVEL_OBJECT_ID = :top_id AND TOP_LEVEL_OBJECT_TYPE_ID = :top_type;

Reporting use cases include work order hierarchy displays, dependency gap analysis, and cost distribution validation across parent and child work orders.

Related Objects

The metadata classifies this object as standalone with no documented foreign-key dependencies beyond its own primary key. The following objects are the most significant consumers or counterparts of the relationship data:

• EAM_WORK_ORDERS (and its 12.2.x variant EAM_WORK_ORDERS_ALL) — the primary entity referenced through PARENT_OBJECT_ID and CHILD_OBJECT_ID when the object type denotes a work order.
• EAM_WO_OPERATIONS — operations scheduled within the work order network defined by these relationships.
• EAM_WO_RELATIONSHIPS self-join — parent and child rows are joined on WO_RELATIONSHIP_ID, PARENT_OBJECT_ID, and CHILD_OBJECT_ID to reconstruct multi-level structures.
• EAM_SCHEDULING_* and scheduling engine packages — consume Scheduling Child and End to Start Dependency rows to sequence work.
• Costing processes in the EAM schema — consume Costing Child rows to roll costs from child to parent work orders.
• FND_OBJECTS / object type validation sets — resolve PARENT_OBJECT_TYPE_ID and CHILD_OBJECT_TYPE_ID to their underlying entity types.
• Standard EBS interfaces that create follow-up work orders and insert corresponding rows using the Follow up work order relationship type.