Results for “msc_reservations”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MSC_RESERVATIONS is a material reservations table in the MSC schema, owned by the Advanced Supply Chain Planning (ASCP) product within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the reservation records collected from source inventory systems and staged for planner consumption, capturing the linkage between on-hand material, demands, and the sources that have committed supply to those demands. In the ASCP data model, the table functions as a planning-side repository of reservation activity, refreshed during the data collection and plan run cycle and used to understand how inventory is earmarked against requirements before netting and pegging logic executes.
From a Data Vault modeling perspective, the mined relationship structure suggests a link classification. The table sits between item, subinventory, and demand entities and carries two significant foreign key relationships outward, making it a natural candidate for a link construct rather than a hub or satellite.
Key Information Stored
The documented physical schema contains 35 columns. The most significant are outlined below.
- PLAN_ID, ORGANIZATION_ID, SR_INSTANCE_ID, TRANSACTION_ID — the composite primary key (MSC_RESERVATIONS_PK). These four columns identify the plan, inventory organization, source instance, and transaction that uniquely define a reservation row.
- INVENTORY_ITEM_ID — the reserved item; references MSC_SYSTEM_ITEMS.
- SUBINVENTORY — the subinventory in which the reservation resides; participates in the MSC_SUB_INVENTORIES foreign key.
- RESERVATION_TYPE — categorizes the reservation and forms part of the unique business-key index MSC_RESERVATIONS_U1 (PLAN_ID, RESERVATION_TYPE, TRANSACTION_ID, SR_INSTANCE_ID, ORGANIZATION_ID).
- RESERVATION_DATE, REQUIREMENT_DATE — the date the reservation was created and the date the underlying demand is required.
- RESERVED_QUANTITY, NONNET_QUANTITY_RESERVED — the quantity reserved and the portion excluded from netting calculations.
- PARENT_DEMAND_ID, DEMAND_SOURCE_LINE_ID, DEMAND_CLASS — identifiers and classification linking the reservation to its originating demand.
- SUPPLY_SOURCE_HEADER_ID, SUPPLY_SOURCE_TYPE_ID — the supply document from which the reservation draws.
- REPAIR_LINE_ID, REPAIR_PO_HEADER_ID — depot repair context; REPAIR_LINE_ID references CSD_REPAIRS.
- SERIAL_NUMBER, REVISION — instance-level and revision attributes where applicable.
- PROJECT_ID, TASK_ID — project and task attribution for project-driven reservations.
- REFRESH_NUMBER, REQUEST_ID — collection/refresh and concurrent request audit columns.
Common Use Cases and Queries
Planners and developers query MSC_RESERVATIONS to reconcile planning reservations against execution-side reservations in MTL_RESERVATIONS, to diagnose netting anomalies where reserved quantity unexpectedly offsets supply, and to build pegging or supply-demand reports for a given plan.
SELECT plan_id, organization_id, inventory_item_id,
subinventory, reserved_quantity, reservation_date
FROM msc_reservations
WHERE plan_id = :plan_id
AND organization_id = :org_id;
A second common pattern joins reservations to MSC_SYSTEM_ITEMS to resolve item names and concatenated segments for reporting:
SELECT r.transaction_id, i.segment1, i.description,
r.reserved_quantity, r.requirement_date
FROM msc_reservations r,
msc_system_items i
WHERE r.inventory_item_id = i.inventory_item_id
AND r.plan_id = i.plan_id
AND r.organization_id = i.organization_id
AND r.sr_instance_id = i.sr_instance_id
AND r.plan_id = :plan_id;
Related Objects
- MSC_SYSTEM_ITEMS — joined on INVENTORY_ITEM_ID, PLAN_ID, ORGANIZATION_ID, SR_INSTANCE_ID. Provides item master attributes.
- MSC_SUB_INVENTORIES — joined on SR_INSTANCE_ID, PLAN_ID, ORGANIZATION_ID, SUBINVENTORY. Resolves subinventory definitions.
- CSD_REPAIRS — referenced via REPAIR_LINE_ID for depot repair reservations.
- MTL_RESERVATIONS — the execution-side reservation table used for reconciliation against collected ASCP data.
- MSC_SUPPLY and MSC_DEMANDS — the supply and demand collections that reservations peg to via SUPPLY_SOURCE_HEADER_ID and PARENT_DEMAND_ID.
- MSC_PLANS — supplies PLAN_ID context for every row.
- MSC_ORG_ASSIGNMENTS — defines the organization context referenced by ORGANIZATION_ID.
-
Material reservations
-
Material reservations
-
TABLE: MSC.MSC_RESERVATIONS 12.1.1
-
TABLE: MSC.MSC_RESERVATIONS 12.2.2
-
VIEW: MSC.MSC_RESERVATIONS# 12.2.2
-
VIEW: MSC.MSC_RESERVATIONS# 12.2.2
-
Lookup Type: MSC_ODS_TABLE 12.2.2
List of ODS tables used by Collections
-
Lookup Type: MSC_ODS_TABLE 12.1.1
List of ODS tables used by Collections
-
The staging table used by the collection program to validate and process data for table MSC_RESERVATIONS.
-
Table: MSC_ST_RESERVATIONS 12.1.1
The staging table used by the collection program to validate and process data for table MSC_RESERVATIONS.
-
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.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
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 - MSC Tables and Views 12.1.1
This table contains the mapping between user-defined zone and included regions
-
eTRM - MSC Tables and Views 12.2.2
This table contains the mapping between user-defined zone and included regions
-
eTRM - MSC Tables and Views 12.1.1
This table contains the mapping between user-defined zone and included regions
-
eTRM - MSC Tables and Views 12.2.2
This table contains the mapping between user-defined zone and included regions
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1