Results for “parent_object_id”

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

Overview

WIP_SCHED_RELATIONSHIPS is a Work in Process (WIP) module table in the Oracle E-Business Suite (EBS) that stores scheduling relationships between work orders. It is owned by the WIP schema and is classified as VALID in both 12.1.1 and 12.2.2. The table provides the persistence layer for dependency links that a scheduling engine consumes when sequencing production orders, enabling parent-child precedence constraints across the shop floor.

From a Data Vault modeling perspective, the table is heuristically classified as standalone. The metadata does not identify a strong hub-and-satellite or link pattern: the object carries no documented foreign keys to other business entities, and its identifying column (SCHED_RELATIONSHIP_ID) is a surrogate. The remaining columns are denormalized attributes describing the two endpoints of each relationship, which suggests the table functions as a self-contained relationship store rather than a traditional link table.

Key Information Stored

The table contains 14 documented columns. The most significant are:

• SCHED_RELATIONSHIP_ID — surrogate primary key (WIP_SCHED_RELATIONSHIPS_PK) and also the sole documented unique-index candidate (WIP_SCHED_RELATIONSHIPS_U1).
• PARENT_OBJECT_ID and PARENT_OBJECT_TYPE_ID — identify the predecessor work order and its object type in the scheduling graph.
• CHILD_OBJECT_ID and CHILD_OBJECT_TYPE_ID — identify the successor work order and its object type.
• RELATIONSHIP_TYPE — the nature of the dependency between parent and child (for example, finish-to-start style constraints).
• RELATIONSHIP_STATUS — lifecycle state of the link, used to filter active versus obsolete relationships.
• TOP_LEVEL_OBJECT_ID and TOP_LEVEL_OBJECT_TYPE_ID — reference the highest-level object the relationship rolls up to, supporting hierarchical scheduling rollups.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns for audit and concurrency tracking.

The surrogate key is a system-generated identifier; the unique index on SCHED_RELATIONSHIP_ID reinforces that no natural business key beyond the surrogate is documented. Because no formal foreign keys are recorded, joins to WIP entities are inferred from the paired _OBJECT_ID and _OBJECT_TYPE_ID columns.

Common Use Cases and Queries

The primary use case is retrieving the dependency graph for a work order so that scheduling logic or reports can determine which orders must complete before others may start.

• Find successors of an order: SELECT CHILD_OBJECT_ID FROM WIP_SCHED_RELATIONSHIPS WHERE PARENT_OBJECT_ID = :order_id AND RELATIONSHIP_STATUS = 'ACTIVE';
• Find predecessors of an order: the inverse query on CHILD_OBJECT_ID returning PARENT_OBJECT_ID.
• Recursive traversal: a CONNECT BY query over PARENT_OBJECT_ID and CHILD_OBJECT_ID resolves the full upstream or downstream chain for a top-level order (TOP_LEVEL_OBJECT_ID).
• Audit and troubleshooting: filtering on LAST_UPDATE_DATE and CREATED_BY identifies recently altered relationships that may explain unexpected scheduling results.

Typical reporting includes dependency listings per work order, blocked-order analysis, and consistency checks for cycles where an object appears as both parent and child.

Related Objects

Because the metadata documents no foreign keys, the following relationships are inferred from the object/type columns rather than enforced keys:

• WIP_DISCRETE_JOBS — work orders referenced by PARENT_OBJECT_ID and CHILD_OBJECT_ID.
• WIP_ENTITIES — the generic work order entity table from which scheduling objects derive.
• WIP_SCHEDULED_ACTIVITIES — scheduling detail aligned to the same object identifiers.
• WIP_SCHEDULING_EXCEPTIONS — exceptions generated by dependencies stored here.
• WIP_SCHEDULE_GROUPS — groupings used during scheduling runs.
• WIP_SCHEDULING_PLAN — planning structures the relationships feed.
• MTL_SYSTEM_ITEMS_B — item context for the participating work orders.
• SCHEDULING APIs — programmatic access used to create and update relationships.