Results for “mrp_orders_sc_v”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MRP_ORDERS_SC_V is an APPS-owned database view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. Its documented purpose is to provide a modified SCP (Supply Chain Planning) supply and demand view, constructed specifically for performance tuning. Unlike the standard MRP_ORDERS_V view, which presents planning recommendations and schedule dates in a broadly normalized form, MRP_ORDERS_SC_V restructures the same underlying supply and demand data to reduce the cost of repeated joins and lookups that occur when large planning result sets are queried for reporting, integration, or downstream SCP consumption.
The view returns one row per planning recommendation as sourced from MRP_RECOMMENDATIONS, enriched with item, organization, plan, order, vendor, line, and flexfield context. Because it consolidates attribute resolution and descriptive lookups at the view layer, it is a common access path for custom reporting on planned orders, reschedules, and firm planned supply, and for feeding external planning or analytics processes where query throughput matters.
Underlying Base Objects
The documented base objects for this view span planning, inventory, purchasing, work-in-process, and sales:
- Planning objects: MRP_RECOMMENDATIONS, MRP_PLANS, MRP_PLAN_ORGANIZATIONS, MRP_SYSTEM_ITEMS, MRP_GROSS_REQUIREMENTS, MRP_SUGG_REP_SCHEDULES, MRP_SCHEDULE_DATES, MRP_ITEM_PURCHASE_ORDERS, and MRP_ITEM_WIP_ENTITIES.
- Manufacturing and WIP: BOM_OPERATIONAL_ROUTINGS, WIP_ENTITIES, WIP_LINES, and WIP_SCHEDULE_GROUPS.
- Inventory and item masters: MTL_PARAMETERS, MTL_SYSTEM_ITEMS_B_KFV, and MTL_SALES_ORDERS.
- Purchasing: PO_VENDORS.
- Lookups and project context: MFG_LOOKUPS and the MRP_GET_PROJECT package.
Most planning and WIP tables are referenced through APPS synonyms (for example, MRP_RECOMMENDATIONS and WIP_ENTITIES), which is typical of MRP views. The MRP_GET_PROJECT package supplies project-related decoding, while MTL_SYSTEM_ITEMS_B_KFV provides the concatenated flexfield segment value (FLEX.CONCATENATED_SEGMENTS) used to present the item number in a single, user-readable column.
Key Columns
The projection begins with a literal source tag, 'MRP_RECOMMENDATIONS', followed by the RowID and standard audit columns (TRANSACTION_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN). Planning keys include INVENTORY_ITEM_ID, ORGANIZATION_ID, ORGANIZATION_CODE, COMPILE_DESIGNATOR, and PLANNER_CODE.
Order and schedule detail is exposed through columns such as ORDER_TYPE, NEW_SCHEDULE_DATE, OLD_SCHEDULE_DATE, NEW_WIP_START_DATE, RESCHEDULED_FLAG, FIRM_PLANNED_TYPE, FIRM_QUANTITY, FIRM_DATE, and RELEASE_STATUS. A DECODE over ORDER_TYPE surfaces the relevant document number: PO_NUMBER for purchase order types, WIP_ENTITY_NAME for discrete and repetitive work order types, and NULL where no document applies. DISPOSITION_ID, DISPOSITION_STATUS_TYPE, IMPLEMENT_DEMAND_CLASS, IMPLEMENT_AS, IMPLEMENT_WIP_CLASS_CODE, and IMPLEMENT_JOB_NAME carry implementation and disposition context.
Additional descriptive columns include VENDOR_ID, LINE_ID with LINE_CODE, CATEGORY_ID, and the item planning attributes MRP_PLANNING_CODE, PLANNING_MAKE_BUY_CODE, BOM_ITEM_TYPE, WIP_SUPPLY_TYPE, REPETITIVE_TYPE, BUILD_IN_WIP_FLAG, PURCHASING_ENABLED_FLAG, SOURCE_ORGANIZATION_ID, and BASE_ITEM_ID. A GREATEST expression yields days until the new order placement date, and several TO_NUMBER(NULL) placeholders preserve positional compatibility with the source SCP interface.
Common Use Cases and Queries
Typical uses include planned order reporting for a given plan and organization, review of reschedule exceptions, extraction of firm planned supply for downstream integration, and reconciliation of recommended versus implemented quantities.
- Planned order listing by plan and organization, filtering on ORDER_TYPE and FIRM_PLANNED_TYPE.
- Reschedule exception review using RESCHEDULED_FLAG, NEW_SCHEDULE_DATE, and OLD_SCHEDULE_DATE.
- Supply/demand extract for SCP or analytics keyed on INVENTORY_ITEM_ID and ORGANIZATION_ID.
A representative query:
SELECT ORGANIZATION_CODE, CONCATENATED_SEGMENTS, ORDER_TYPE,
NEW_ORDER_QUANTITY, NEW_ORDER_PLACEMENT_DATE, FIRM_PLANNED_TYPE
FROM APPS.MRP_ORDERS_SC_V
WHERE COMPILE_DESIGNATOR = :plan
AND ORGANIZATION_ID = :org
AND ORDER_TYPE IN (1,2,3,7);
-
View: MRP_ORDERS_SC_V 12.1.1
Modified SCP supply and demand view for Performance Tuning
APPS.MRP_ORDERS_SC_V·↳ BOM_OPERATIONAL_ROUTINGS·↳ MFG_LOOKUPS·↳ MRP_GET_PROJECT·Explore MRP module →
-
View: MRP_ORDERS_SC_V 12.2.2
Modified SCP supply and demand view for Performance Tuning
APPS.MRP_ORDERS_SC_V·↳ BOM_OPERATIONAL_ROUTINGS·↳ MFG_LOOKUPS·↳ MRP_GET_PROJECT·Explore MRP module →
-
VIEW: APPS.MRP_ORDERS_SC_V 12.1.1
-
VIEW: APPS.MRP_ORDERS_SC_V 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
SYNONYM: APPS.MRP_PLANS 12.2.2
-
SYNONYM: APPS.MRP_PLANS 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
SYNONYM: APPS.WIP_LINES 12.2.2
-
SYNONYM: APPS.WIP_LINES 12.1.1
-
SYNONYM: APPS.WIP_ENTITIES 12.2.2
-
SYNONYM: APPS.WIP_ENTITIES 12.1.1
-
VIEW: APPS.MFG_LOOKUPS 12.1.1
-
VIEW: APPS.MFG_LOOKUPS 12.2.2
-
VIEW: APPS.PO_VENDORS 12.1.1
-
VIEW: APPS.PO_VENDORS 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.1.1
-
Set Distribution Table.
-
eTRM - MRP Tables and Views 12.2.2
Recommendations based on user criteria selected in MRP Planner WorkBench