Results for “mrp_web_planned_supply_v”

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

Overview

APPS.MRP_WEB_PLANNED_SUPPLY_V is a VALID database view owned by the APPS schema and delivered as part of the Oracle Master Scheduling/MRP (MRP) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose supply information for items — that is, the firm and planned supply recommendations generated by the planning engine, presented in a web-friendly, denormalized form suitable for the Planner Workbench (HTML/Java UI) and for custom reporting or integration against the planning recommendation tables.

The view is effectively a reporting projection over MRP_RECOMMENDATIONS, joined to item, plan, vendor, and lookup reference data. Because it surfaces NEW_DOCK_DATE alongside NEW_ORDER_PLACEMENT_DATE and NEW_SCHEDULE_DATE, it is the standard consumer interface for users investigating dock-date behaviour on buy recommendations — for example the query term "new_dock_date" that leads to this object. It is a read-only view and carries no materialized or cached storage of its own.

Underlying Base Objects

The documented base objects referenced by the view are: MRP_RECOMMENDATIONS (SYNONYM — the driving table, aliased REC), MRP_SYSTEM_ITEMS (SYNONYM), MRP_PLANS (SYNONYM), MRP_PLAN_ORGANIZATIONS (SYNONYM), MRP_ITEM_PURCHASE_ORDERS (SYNONYM), MTL_ITEM_FLEXFIELDS (VIEW) for the concatenated item number, MFG_LOOKUPS (VIEW) three times (aliases L1, L2, L3) for order type, action type, and yes/no meanings, PO_VENDORS and PO_VENDOR_SITES_ALL (both VIEWs) for source vendor and site detail, plus the packages MRP_GET_PROJECT and FND_GLOBAL.

Planning recommendations are keyed by COMPILE_DESIGNATOR, ORGANIZATION_ID, and INVENTORY_ITEM_ID; the joins to MRP_SYSTEM_ITEMS and MTL_ITEM_FLEXFIELDS follow the same key. The purchase-order join to MRP_ITEM_PURCHASE_ORDERS is outer (+) on transaction, designator, organization, and item, so recommendations that have no associated PO still appear. Vendor and vendor-site joins are likewise outer-joined on the source vendor columns, ensuring planned supplies without an identified source remain visible. The project and task columns are wrapped in MRP_GET_PROJECT.PROJECT / .TASK with NVL(...,-1) defaults, reflecting Projects-aware planning.

Key Columns

• TRANSACTION_ID — primary identifier of the recommendation row in MRP_RECOMMENDATIONS.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, ORGANIZATION_CODE — item and planning organization context.
• COMPILE_DESIGNATOR — the MRP plan identifier under which the recommendation was compiled.
• NEW_DOCK_DATE — the recommended dock (receipt) date for the planned supply; central to supply-timing analysis.
• NEW_ORDER_PLACEMENT_DATE, NEW_SCHEDULE_DATE — the recommended order release date and the new schedule date used in the action-type lookup derivation.
• NEW_ORDER_QUANTITY — recommended supply quantity.
• ORDER_TYPE and L1.MEANING — numeric order type with its decoded MRP_ORDER_TYPE meaning.
• DISPOSITION_STATUS_TYPE and L2.MEANING — action type decoded from MRP_ACTION_TYPE.
• FIRM_PLANNED_TYPE and L3.MEANING — firm/planned flag decoded from SYS_YES_NO.
• VENDOR_ID, VENDOR_NAME, SOURCE_VENDOR_SITE_ID, VENDOR_SITE_CODE — source vendor and site detail.
• PROJECT_ID, TASK_ID (NVL to -1) and their decoded descriptions — project/task attribution.
• PLANNING_GROUP (NVL to '-') — grouping attribute for the planner.
• ITEM_NUMBER — concatenated flexfield item number from MTL_ITEM_FLEXFIELDS.

Common Use Cases and Queries

Typical usage includes Planner Workbench supply listings, custom BI Publisher or OBIEE reports on planned receipts by dock date, and integrations that push planned supply to external scheduling systems. A representative query retrieving buy recommendations with dock dates for a given plan and organization:

SELECT item_number, vendor_name, vendor_site_code,
       new_order_quantity, new_order_placement_date,
       new_schedule_date, new_dock_date, meaning
FROM   apps.mrp_web_planned_supply_v
WHERE  compile_designator = :plan
AND    organization_id    = :org
ORDER BY new_dock_date;

To isolate supplies where the dock date drives late/early action messages, filter on the difference between dock and schedule dates, or join back to MRP_RECOMMENDATIONS via TRANSACTION_ID for the full message context. Because the view performs outer joins and lookup decoding at runtime, performance is best when queries are restricted on COMPILE_DESIGNATOR, ORGANIZATION_ID, and INVENTORY_ITEM_ID to leverage the underlying recommendation indexes.