Results for “implement_as”

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

Overview

MRP_ORDERS_V is an APPS-owned database view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family, documented as the "MRP supply and demand view." It consolidates planned supply and demand records generated by the MRP planning engine into a single, uniformly shaped result set. The view is a UNION-style construct: the excerpt shows the first branch selecting from MRP_RECOMMENDATIONS, and the referenced base objects indicate additional branches spanning gross requirements, suggested repetitive schedules, schedule dates, sales orders, purchase orders, WIP entities, and WIP lines. This design lets planners and integration developers query a single object to retrieve every discrete MRP supply and demand recommendation without joining each source table individually.

Because the view exposes recommendation-level attributes such as order type, schedule dates, disposition status, and the rescheduled_flag, it is the primary SQL-level interface used for MRP exception reporting, plan implementation review, and custom planning dashboards.

Underlying Base Objects

The documented ETRM metadata for release 12.2.2 lists the following referenced objects: MFG_LOOKUPS (VIEW), MRP_GROSS_REQUIREMENTS, MRP_ITEM_PURCHASE_ORDERS, MRP_ITEM_WIP_ENTITIES, MRP_RECOMMENDATIONS, MRP_SCHEDULE_DATES, MRP_SUGG_REP_SCHEDULES, MRP_SYSTEM_ITEMS, MTL_ITEM_FLEXFIELDS (VIEW), MTL_PARAMETERS, MTL_SALES_ORDERS, WIP_ENTITIES, and WIP_LINES.

• MRP_RECOMMENDATIONS supplies the primary rescheduling and new-order recommendation columns, including rescheduled_flag, new/old schedule dates, and disposition attributes.
• MRP_GROSS_REQUIREMENTS and MTL_SALES_ORDERS contribute demand rows.
• MRP_ITEM_PURCHASE_ORDERS, MRP_ITEM_WIP_ENTITIES, WIP_ENTITIES, and WIP_LINES contribute supply rows with document identifiers such as PO numbers and WIP entity names.
• MRP_SYSTEM_ITEMS and MTL_ITEM_FLEXFIELDS provide item and organization context; MRP_SUGG_REP_SCHEDULES supplies repetitive schedule data; MFG_LOOKUPS and MTL_PARAMETERS resolve lookup meanings and operating unit defaults.

Key Columns

• RESCHEDULED_FLAG — indicates whether an existing order or schedule is recommended for rescheduling rather than release or cancellation. Central to reschedule exception reports.
• ORDER_TYPE and L1.MEANING — the numeric planning order type (e.g., 1/2 purchase order, 3/7 WIP job, 11/12 planned order) and its decoded lookup meaning.
• NEW_SCHEDULE_DATE, OLD_SCHEDULE_DATE, NEW_ORDER_PLACEMENT_DATE, NEW_DOCK_DATE — old and recommended dates for the planning suggestion.
• NEW_ORDER_QUANTITY, OLD_ORDER_QUANTITY, IMPLEMENTED_QUANTITY, IMPLEMENT_DATE — quantity and implementation tracking.
• DISPOSITION_ID, DISPOSITION_STATUS_TYPE, IMPLEMENT_STATUS_CODE — disposition and implementation status for the recommendation.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, ITEM_NUMBER, PLANNER_CODE — item and planner context.

Common Use Cases and Queries

Typical uses include reschedule-in exception reports, planned order review before implementation, and pegging-style supply/demand extracts.

• Identify all records flagged for rescheduling for a given planner and organization.
• Report new versus old schedule dates for purchase order and WIP recommendations.
• Feed downstream reporting or integration processes with a unified supply and demand extract.

Sample query:

SELECT inventory_item_id, organization_id, order_type, new_schedule_date, old_schedule_date, new_order_quantity, rescheduled_flag FROM apps.mrp_orders_v WHERE rescheduled_flag = 'Y' AND organization_id = :org_id ORDER BY planner_code, new_schedule_date;