Results for “mrp_gross_requirements”

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

Overview

MRP_GROSS_REQUIREMENTS is a core scheduling table within the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. It stores the gross requirements generated by the planning engine for each planned item across a planning horizon. In Oracle EBS 12.1.1 and 12.2.2, this table is populated by the MRP/MPS planning run and serves as the demand-side input to the netting process. Each row represents a discrete demand entry — sales order demand, inter-org transfer demand, component demand from a parent assembly (dependent demand), safety stock replenishment, or forecast consumption — that the planner must satisfy through supply.

The table resides in the MRP schema and is maintained as an internal planning structure. It is not typically entered by users directly; rather, it is created and updated by concurrent programs such as the Memory-Based Snapshot and the Planner. Under the heuristic Data Vault classification mined from its foreign key structure, MRP_GROSS_REQUIREMENTS is satellite-leaning. Its single-column primary key (DEMAND_ID) behaves as a surrogate identifier, with foreign keys fanning out to dimension-like parent tables. In a Data Vault model, this object would be best represented as a satellite attached to a central demand hub/link, capturing the descriptive and quantity attributes that describe each gross requirement event.

Key Information Stored

The physical schema documents 39 columns. The most operationally significant are summarized below.

• DEMAND_ID — Surrogate primary key; uniquely identifies each gross requirement record via the MRP_GROSS_REQUIREMENTS_PK index and the unique index MRP_GROSS_REQUIREMENTS_U1. It is the single business-key candidate and the primary join target for downstream consumers.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — Identify the planned item and the inventory organization whose requirement is being recorded. Together with COMPILE_DESIGNATOR these form the composite foreign key to MRP_SYSTEM_ITEMS.
• COMPILE_DESIGNATOR — Distinguishes the specific planning compilation (plan) under which the requirement was generated.
• USING_ASSEMBLY_ITEM_ID, USING_ASSEMBLY_DEMAND_DATE, and USING_REQUIREMENTS_QUANTITY — Describe the parent assembly that consumes this item, the date it is required, and the quantity demanded (dependent demand).
• ASSEMBLY_DEMAND_COMP_DATE — The component demand completion date used for scheduling offsets.
• DEMAND_TYPE, ORIGINATION_TYPE, and DEMAND_CLASS — Classify the source and nature of the requirement (e.g., sales order, transfer, forecast).
• DISPOSITION_ID — Foreign key to MRP_RECOMMENDATIONS, linking the requirement to its planning disposition or recommendation.
• RESERVATION_ID and RESERVE_QUANTITY — Reference MTL_RESERVATIONS and quantify reserved supply against this demand.
• FIRM_QUANTITY and FIRM_DATE — Capture firmed demand quantities and dates as set by the planner.
• DAILY_DEMAND_RATE — Used for repetitive or rate-based planning scenarios.
• PROJECT_ID, TASK_ID, LENDING_PROJECT_ID, LENDING_TASK_ID — Support project/task-oriented (Oracle Projects) demand attribution and cross-charge lending.
• STATUS, APPLIED, UPDATED — Internal processing flags indicating whether the row has been applied and refreshed by the planning run.

Common Use Cases and Queries

Planners and developers query MRP_GROSS_REQUIREMENTS to inspect why a specific item shows demand in a plan, to trace pegging from a requirement up to its parent assembly, and to reconcile planned demand against MRP_RECOMMENDATIONS. A common pattern filters by plan and item:

• Item-level gross requirement detail: SELECT demand_id, inventory_item_id, organization_id, using_requirements_quantity, using_assembly_demand_date FROM mrp_gross_requirements WHERE inventory_item_id = :item_id AND organization_id = :org_id AND compile_designator = :plan;
• Dependent demand trace: join USING_ASSEMBLY_ITEM_ID back to MRP_SYSTEM_ITEMS to resolve the parent assembly description for a given component requirement.
• Disposition reconciliation: join DISPOSITION_ID to MRP_RECOMMENDATIONS to correlate each requirement with its recommended supply action.
• Pegging analysis: join DEMAND_ID to MRP_FULL_PEGGING to walk the supply/demand pegging chain.
• Reservation cross-check: join RESERVATION_ID to MTL_RESERVATIONS to validate reserved quantities against demand.

Reporting use cases include gross-to-net requirement analysis, capacity loading by demand date, firmed-order exception reporting, and project-based demand reporting using PROJECT_ID and TASK_ID.

Related Objects

The following tables participate in the documented foreign key relationships around MRP_GROSS_REQUIREMENTS.

• MRP_FULL_PEGGING — References this table via MRP_FULL_PEGGING.DEMAND_ID, enabling end-to-end pegging from demand to supply.
• MRP_RECOMMENDATIONS — Joined through MRP_GROSS_REQUIREMENTS.DISPOSITION_ID; holds the planning recommendation associated with each requirement.
• MRP_SYSTEM_ITEMS — Referenced twice: via INVENTORY_ITEM_ID (with ORGANIZATION_ID and COMPILE_DESIGNATOR) for the planned item, and via USING_ASSEMBLY_ITEM_ID for the consuming assembly.
• MTL_RESERVATIONS — Joined through RESERVATION_ID to link reserved inventory against the demand.
• MRP_GROSS_REQUIREMENTS_PK / MRP_GROSS_REQUIREMENTS_U1 — The primary and unique indexes over DEMAND_ID that enforce uniqueness and drive join performance.

Together these relationships position MRP_GROSS_REQUIREMENTS as the central demand-fact satellite of the MRP planning schema, joined by DEMAND_ID to pegging, disposition, item, and reservation entities.