Results for “mds_entry_id”
26 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.MRPBV_MDS_CONSUMPTIONS view is a Master Scheduling/MRP (MRP) reporting and integration object that exposes the consumption, or relief, activity applied against a Master Demand Schedule (MDS). In Oracle EBS planning, an MDS entry is "consumed" when actual demand — most commonly a booked sales order line — is relieved against the forecasted or planned demand quantity. The view presents a distinct row for each such relief event, joining the planning-side consumption record to the originating sales order line and its associated schedule date.
The view is defined with the WITH READ ONLY clause, confirming it is intended strictly for query, reporting, and downstream integration consumption rather than for DML. It is a subset view: the defining query filters on MRSC.RELIEF_TYPE = 1, which restricts output to sales-order-related relief. This makes the view a focused window into the MDS relief activity driven by order entry, and it is typically used in custom reports, interfaces, and reconciliation queries that must trace how much demand was relieved for a given sales order line on a given schedule date.
Underlying Base Objects
The view joins four principal base objects, three of which are exposed through synonyms in the APPS schema. The primary driving object is MRP_SCHEDULE_CONSUMPTIONS (synonym MRSC), which stores each consumption/relief record, its relief quantity, relief type, disposition, and line reference. It is joined to MRP_SCHEDULE_DATES (synonym MRSD) on MPS_TRANSACTION_ID = MRSC.TRANSACTION_ID, supplying the schedule and organization context; the documented text includes an organization predicate referencing MRSD.ORGANIZATION_ID.
The demand side is obtained from MTL_DEMAND_OMOE (synonym DEMAND), which links to the consumption record via DISPOSITION_ID and LINE_NUM. Finally, SO_LINES_ALL (synonym SOLINE) supplies the sales order line identity through LINE_ID = DEMAND.DEMAND_SOURCE_LINE. The documented metadata additionally lists the packages INV_DECIMALS_PUB, INV_SALESORDER, MRP_OE, and OE_INSTALL as referenced base objects, reflecting the view's dependency on order-entry and MRP utility logic such as unit-of-measure and quantity handling.
Key Columns
- SCHEDULE_DATE — The schedule date on which the MDS consumption occurred, taken from the schedule dates record.
- RELIEF_QUANTITY — The quantity relieved against the MDS entry; this is the column users most often search for when reconciling MDS consumption.
- TRANSACTION_ID — Identifier linking the consumption record to its MPS transaction/schedule date row.
- MDS_ENTRY_ID / SALES_ORDER_LINE_ID — Identifiers exposed for the associated MDS entry and originating sales order line.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard Oracle EBS audit columns describing when and by whom the consumption record was created and last modified.
The view text also derives a numeric value via TO_NUMBER(DEMAND.DEMAND_SOURCE_LINE), used to correlate the demand record with the sales order line, and applies SELECT DISTINCT to suppress duplication introduced by the multi-table join.
Common Use Cases and Queries
Typical scenarios include auditing MDS relief by date, reconciling relieved quantities back to booked sales orders, and feeding planning reports. A representative query retrieving relief activity for a schedule window follows:
SELECT schedule_date, relief_quantity, transaction_id, mds_entry_id, sales_order_line_id FROM apps.mrpbv_mds_consumptions WHERE schedule_date BETWEEN :from_date AND :to_date ORDER BY schedule_date;SELECT sales_order_line_id, SUM(relief_quantity) total_relieved FROM apps.mrpbv_mds_consumptions GROUP BY sales_order_line_id;
Because the view is read-only and filtered to relief type 1, it is well suited to summary dashboards and reconciliation extracts. For organization-specific reporting, join to MRP_SCHEDULE_DATES or supply the organization context supplied by the underlying schedule dates record.
-
View: MRPBV_MDS_CONSUMPTIONS 12.2.2
APPS.MRPBV_MDS_CONSUMPTIONS·↳ MRP_SCHEDULE_CONSUMPTIONS·↳ MRP_SCHEDULE_DATES·↳ MTL_DEMAND_OMOE·Explore MRP module →
-
View: MRPFV_MDS_CONSUMPTIONS 12.2.2
APPS.MRPFV_MDS_CONSUMPTIONS·↳ MRP_SCHEDULE_CONSUMPTIONS·↳ MRP_SCHEDULE_DATES·↳ MTL_DEMAND·Explore MRP module →
-
View: MRPFV_PLAN_DEMANDS 12.1.1
- Retrofitted
APPS.MRPFV_PLAN_DEMANDS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MRP_GROSS_REQUIREMENTS·Explore MRP module →
-
View: MRPBV_MDS_CONSUMPTIONS 12.1.1
APPS.MRPBV_MDS_CONSUMPTIONS·↳ MRP_SCHEDULE_CONSUMPTIONS·↳ MRP_SCHEDULE_DATES·↳ MTL_DEMAND_OMOE·Explore MRP module →
-
View: MRPFV_MDS_CONSUMPTIONS 12.1.1
APPS.MRPFV_MDS_CONSUMPTIONS·↳ MRP_SCHEDULE_CONSUMPTIONS·↳ MRP_SCHEDULE_DATES·↳ MTL_DEMAND·Explore MRP module →
-
View: MRPBV_MDS_ENTRIES 12.1.1
- Retrofitted
APPS.MRPBV_MDS_ENTRIES·↳ MFG_LOOKUPS·↳ MRP_SCHEDULE_DATES·↳ MRP_SCHEDULE_DESIGNATORS·Explore MRP module →
-
View: MRPBV_PLAN_DEMANDS 12.1.1
- Retrofitted
APPS.MRPBV_PLAN_DEMANDS·↳ MFG_LOOKUPS·↳ MRP_GROSS_REQUIREMENTS·↳ MRP_ITEM_PURCHASE_ORDERS·Explore MRP module →
-
View: MRPBV_MDS_ENTRIES 12.2.2
- Retrofitted
APPS.MRPBV_MDS_ENTRIES·↳ MFG_LOOKUPS·↳ MRP_SCHEDULE_DATES·↳ MRP_SCHEDULE_DESIGNATORS·Explore MRP module →
-
View: MRPBV_PLAN_DEMANDS 12.2.2
- Retrofitted
APPS.MRPBV_PLAN_DEMANDS·↳ MFG_LOOKUPS·↳ MRP_GROSS_REQUIREMENTS·↳ MRP_ITEM_PURCHASE_ORDERS·Explore MRP module →
-
View: MRPFV_MDS_ENTRIES 12.2.2
- Retrofitted
APPS.MRPFV_MDS_ENTRIES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MRP_SCHEDULE_DATES·Explore MRP module →
-
View: MRPFV_MDS_ENTRIES 12.1.1
- Retrofitted
APPS.MRPFV_MDS_ENTRIES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MRP_SCHEDULE_DATES·Explore MRP module →
-
View: MRPFV_PLAN_DEMANDS 12.2.2
- Retrofitted
APPS.MRPFV_PLAN_DEMANDS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MRP_GROSS_REQUIREMENTS·Explore MRP module →
-
VIEW: APPS.MRPBV_MDS_ENTRIES 12.1.1
-
VIEW: APPS.MRPBV_MDS_ENTRIES 12.2.2
-
VIEW: APPS.MRPFV_MDS_ENTRIES 12.1.1
-
VIEW: APPS.MRPFV_MDS_ENTRIES 12.2.2
-
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