Results for “net_quantity”

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

Overview

MRP_WIP_COMPONENTS is a Master Scheduling/MRP (MRP) schema table that stores work in process (WIP) component requirements — the demand for component inventory items needed to satisfy discrete jobs, repetitive schedules, and their associated operations. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the planning-side mirror of the WIP component demand generated by the manufacturing execution and MRP planning engines. Each row links a component inventory item to a specific WIP entity and operation sequence, expressing quantities required, issued, allocated, and net, together with operation start dates and offsets used by the planner.

From a Data Vault modeling perspective, the mined metadata classifies this object heuristically as a link table. This is consistent with its structure: the composite primary key, MRP_WIP_COMPONENTS_PK, largely consists of foreign-key references (item, organization, compile designator, WIP entity, operation sequence, job reference item) rather than descriptive attributes, which is characteristic of a relationship table connecting component items to WIP entities.

Key Information Stored

The documented physical schema contains 26 columns. The most significant are:

• INVENTORY_ITEM_ID — the component item being planned; part of the primary key and a foreign key to MRP_SYSTEM_ITEMS.
• ORGANIZATION_ID — the inventory organization context; part of the primary key and FK relationship.
• COMPILE_DESIGNATOR — identifies the MRP plan/compilation that produced the row; part of the PK and unique index.
• WIP_ENTITY_ID — the discrete job or repetitive schedule requiring the component.
• OPERATION_SEQ_NUM — the routing operation at which the component is consumed.
• JOB_REFERENCE_ITEM_ID — the parent assembly item the job builds; also FK to MRP_SYSTEM_ITEMS.
• QUANTITY_REQUIRED / QUANTITY_ISSUED — required versus issued component quantities.
• ALLOCATED_QUANTITY / NET_QUANTITY — allocated and net-of-issue quantities used in planning.
• OPERATION_START_DATE / OPERATION_OFFSET_DAYS — scheduling timing for the operation.
• WIP_ENTITY_TYPE / SUPPLY_DEMAND_TYPE — job classification and demand categorization.
• PLANNING_GROUP — grouping attribute for reporting.
• PROJECT_ID / TASK_ID — project and task references for project manufacturing.

The surrogate-style primary key MRP_WIP_COMPONENTS_PK spans INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR, WIP_ENTITY_ID, OPERATION_SEQ_NUM, and JOB_REFERENCE_ITEM_ID. A separate unique index, MRP_WIP_COMPONENTS_U1, covers the same business-key columns and serves as the documented business-key candidate.

Common Use Cases and Queries

Typical scenarios include reconciling planned component demand against actual WIP issues, analyzing shortfalls where QUANTITY_REQUIRED exceeds QUANTITY_ISSUED, and reviewing net requirements by organization and plan. A representative query joins to the parent item table:

• Select component requirements for a given WIP_ENTITY_ID, filtering by OPERATION_SEQ_NUM and COMPILE_DESIGNATOR to view a single plan.
• Aggregate NET_QUANTITY by INVENTORY_ITEM_ID and ORGANIZATION_ID for component shortage reporting.
• Join MRP_WIP_COMPONENTS to MRP_SYSTEM_ITEMS on INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR to obtain item descriptions.
• Filter by OPERATION_START_DATE window to produce time-phased component requirement reports.

Related Objects

• MRP_SYSTEM_ITEMS — referenced twice: once via INVENTORY_ITEM_ID (component) and once via JOB_REFERENCE_ITEM_ID (parent assembly), joined on ORGANIZATION_ID and COMPILE_DESIGNATOR.
• MRP_WIP_COMPONENTS_PK / MRP_WIP_COMPONENTS_U1 — the primary key constraint and unique index enforcing row uniqueness.
• WIP-related entities referenced by WIP_ENTITY_ID for job and schedule detail.
• Project manufacturing tables linked via PROJECT_ID and TASK_ID.