Results for “mrp_flp_supply_v”
32 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MRP_FLP_SUPPLY_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the MRP (Master Scheduling/MRP) product family and is documented with the description "View of supply information." The view exposes a consolidated, reporting-friendly projection of supply recommendations generated by the Oracle MRP / Master Scheduling planning engine, drawn primarily from MRP_RECOMMENDATIONS where ORDER_TYPE identifies the nature of the supply. It joins lookup, project, item, organization, purchasing, and work-in-process entities to translate raw numeric codes and identifiers into meaningful business attributes.
The view is intended for reporting and integration rather than transactional processing. Because Oracle's planning tables store supply and demand in coded numeric form, MRP_FLP_SUPPLY_V is typically the object referenced by custom reports, Discoverer workbooks, and interface extracts that require human-readable supply details such as order name, project, task, item/organization concatenation, and descriptive text. Its status is VALID in the ETRM metadata, confirming it is a supported database object.
Underlying Base Objects
The view is defined over a set of documented base objects, combined through inner and outer joins. The driving table is MRP_RECOMMENDATIONS (a synonym), which supplies the core recommendation rows, including TRANSACTION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, ORDER_TYPE, and the scheduling columns.
- MFG_LOOKUPS (VIEW) — joined on LOOKUP_TYPE = 'MRP_ORDER_TYPE' to resolve MR.ORDER_TYPE into a display MEANING.
- MRP_ITEM_PURCHASE_ORDERS (SYNONYM) — outer-joined via MIP.TRANSACTION_ID(+) = MR.DISPOSITION_ID to retrieve PO_NUMBER for purchase-order type supplies.
- WIP_ENTITIES (SYNONYM) — outer-joined via WE.WIP_ENTITY_ID(+) = MR.DISPOSITION_ID to retrieve WIP_ENTITY_NAME for work-order type supplies.
- MTL_ITEM_FLEXFIELDS (VIEW) — supplies ITEM_NUMBER and DESCRIPTION, joined on INVENTORY_ITEM_ID and ORGANIZATION_ID.
- MTL_PARAMETERS (SYNONYM) — provides ORGANIZATION_CODE, joined on ORGANIZATION_ID.
- MRP_GET_PROJECT (PACKAGE) — its PROJECT and TASK functions derive the project and task numbers from MR.PROJECT_ID and MR.TASK_ID.
- MRP_SYSTEM_ITEMS (SYNONYM) — documented as a referenced base object, supporting item-level context.
Key Columns
- TRANSACTION_ID — unique identifier of the recommendation row.
- INVENTORY_ITEM_ID / ORGANIZATION_ID — item and organization keys.
- NEW_PROCESSING_DAYS — the recomputed processing/lead time in days associated with the new schedule. Users frequently search this column to analyze planned lead-time adjustments for supply orders.
- NEW_SCHEDULE_DATE / NEW_ORDER_QUANTITY — the recommended (rescheduled) date and quantity; also exposed under the documented column names ORDER_DATE and SUPPLY_QUANTITY.
- ORDER_TYPE / MEANING — numeric order type and its MRP_ORDER_TYPE lookup meaning.
- ORDER_NAME — a DECODE-driven column returning PO_NUMBER (types 1, 2, 8, 11, 12) or WIP_ENTITY_NAME (types 3, 7, 14, 15, 27, 28), otherwise blank.
- PROJECT_NUMBER / TASK_NUMBER — project and task from MRP_GET_PROJECT.
- ITEM_ORG — ITEM_NUMBER concatenated with ORGANIZATION_CODE.
- DESCRIPTION — first 20 characters of the item description.
- UNIT_NUMBER / DISPOSITION — end-item unit number and disposition reference linking to PO or WIP records.
Common Use Cases and Queries
Typical uses include supply/demand reporting, lead-time analysis, and feeding external planning extracts. A representative query that focuses on processing days is:
SELECT transaction_id, item_org, order_type, meaning, new_processing_days, new_schedule_date, new_order_quantity, order_name FROM apps.mrp_flp_supply_v WHERE new_processing_days IS NOT NULL ORDER BY new_processing_days DESC;- Filtering by
organization_idoritem_orgto isolate reschedule recommendations for a specific item or plant. - Joining to MRP_GROSS_REQUIREMENTS or MRP_RECOMMENDATIONS for full supply/demand pegging analysis.
- Extracting
order_nameto reconcile recommended supplies against actual purchase orders and WIP jobs.
-
View: MRP_FLP_SUPPLY_V 12.2.2
View of supply information
APPS.MRP_FLP_SUPPLY_V·↳ MFG_LOOKUPS·↳ MRP_GET_PROJECT·↳ MRP_ITEM_PURCHASE_ORDERS·Explore MRP module →
-
View: MRP_FLP_SUPPLY_V 12.1.1
View of supply information
APPS.MRP_FLP_SUPPLY_V·↳ MFG_LOOKUPS·↳ MRP_GET_PROJECT·↳ MRP_ITEM_PURCHASE_ORDERS·Explore MRP module →
-
VIEW: APPS.MRP_FLP_SUPPLY_V 12.2.2
-
VIEW: APPS.MRP_FLP_SUPPLY_V 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
SYNONYM: APPS.WIP_ENTITIES 12.2.2
-
SYNONYM: APPS.WIP_ENTITIES 12.1.1
-
VIEW: APPS.MFG_LOOKUPS 12.2.2
-
VIEW: APPS.MFG_LOOKUPS 12.1.1
-
SYNONYM: APPS.MTL_PARAMETERS 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.1.1
-
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 - INV Tables and Views 12.2.2
-
eTRM - INV Tables and Views 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
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 - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2