Results for “mrp_reservations”
28 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MRP_RESERVATIONS is a Master Scheduling/MRP (MRP) product table owned by the MRP schema. Its documented description is "Material reservations," and it stores firm or planned inventory reservations that the planning engine raises against on-hand supply in order to satisfy specific demand. Each row records the reservation of a quantity of an item, in a defined organization and subinventory, to a particular disposition — typically a sales order line — across a specific compile designator (plan) and planning group. In Oracle EBS 12.1.1 and 12.2.2 the table is marked VALID and exposes 26 documented columns. Within MRP, reservations feed the planner's view of supply that is already committed and therefore unavailable for other demand, supporting ATP-style visibility and end-item allocation during the planning cycle.
The metadata carries a heuristic Data Vault classification of link, mined from its foreign-key structure. As a modeling suggestion rather than an Oracle-defined attribute, this reflects that MRP_RESERVATIONS primarily associates several independent business entities — item, subinventory, and sales order disposition — rather than holding an unchanging descriptive payload. The table behaves as a transactional association of item/supply to demand.
Key Information Stored
The declared primary key is MRP_RESERVATIONS_PK, composed of TRANSACTION_ID, COMPILE_DESIGNATOR, and ORGANIZATION_ID. A unique index, MRP_RESERVATIONS_U1, covers the same three columns, making them the strongest business-key candidates in the documented schema.
- TRANSACTION_ID — Unique identifier for the reservation transaction; part of the primary key.
- COMPILE_DESIGNATOR — Identifies the plan/compile run the reservation belongs to; part of the primary key.
- ORGANIZATION_ID — Inventory organization scope; part of the primary key.
- INVENTORY_ITEM_ID — The reserved item (references MRP_SYSTEM_ITEMS and MTL_ITEM_REVISIONS_B).
- REVISION — Item revision reserved, aligned to item master revisions.
- SUBINVENTORY — Subinventory where the reserved supply resides (references MRP_SUB_INVENTORIES).
- RESERVED_QUANTITY — Quantity reserved against the supply.
- NONNET_QUANTITY_RESERVED — Portion excluded from netting in the plan.
- RESERVATION_DATE and REQUIREMENT_DATE — When the reservation was created versus when demand is required.
- DISPOSITION_TYPE and DISPOSITION_ID — The demand disposition; DISPOSITION_ID references MTL_SALES_ORDERS.
- PARENT_DEMAND_ID — Links to the parent demand record supplying context.
- DEMAND_CLASS and PLANNING_GROUP — Planning classification and grouping attributes.
- PROJECT_ID and TASK_ID — Project and task references for project-driven reservations.
- Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and concurrent program columns REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID.
Common Use Cases and Queries
Typical usage includes reconciling firm reservations to sales orders, auditing reserved versus non-netted quantity by plan, and verifying that planned supply is not double-counted. A representative pattern joins to the item and sales order entities:
- Reservations by plan and organization:
SELECT transaction_id, inventory_item_id, reserved_quantity FROM mrp.mrp_reservations WHERE compile_designator = :plan AND organization_id = :org_id; - Reservation to sales order: join DISPOSITION_ID to
mtl_sales_ordersfor order/line context. - Reservation to item master: join INVENTORY_ITEM_ID and ORGANIZATION_ID to
mrp_system_itemsto attach item descriptions and planning attributes. - Subinventory reporting: group by SUBINVENTORY after joining
mrp_sub_inventories.
Related Objects
The documented foreign-key relationships define the principal related objects:
- MRP_SYSTEM_ITEMS — join on (INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR).
- MRP_SUB_INVENTORIES — join on (SUBINVENTORY, ORGANIZATION_ID, COMPILE_DESIGNATOR).
- MTL_SALES_ORDERS — join on DISPOSITION_ID for the demand disposition.
- MTL_ITEM_REVISIONS_B — join on (INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION) for revision detail.
These four relationships, combined with the primary key and unique index, form the documented relational footprint of MRP_RESERVATIONS as a link-style association in the MRP planning schema.
-
Material reservations
-
Material reservations
-
TABLE: MRP.MRP_RESERVATIONS 12.1.1
-
TABLE: MRP.MRP_RESERVATIONS 12.2.2
-
VIEW: MRP.MRP_RESERVATIONS# 12.2.2
-
VIEW: MRP.MRP_RESERVATIONS# 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - MRP Tables and Views 12.2.2
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - MRP Tables and Views 12.1.1
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - MRP Tables and Views 12.2.2
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - MRP Tables and Views 12.1.1
Recommendations based on user criteria selected in MRP Planner WorkBench
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1