Search Results msc_flp_end_demand_v




Overview
Explore in AI Chat

Overview

MSC_FLP_END_DEMAND_V is an APPS-owned database view within the Advanced Supply Chain Planning (MSC) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the final (end) demand picture produced by the FLP (Fast Planning / flow planning) pegging engine, joining the full pegging structure against the demand and supply records that constitute the plan. The view is a reporting and diagnostic surface rather than a transactional entry point: it presents pegged end-demand rows, their associated supply order types, quantities, dates, items, organizations, projects, and tasks in a single denormalized projection.

The user search term mrp_flp_supply_demand_type is directly relevant because the view resolves its demand and supply type labels through MSC_GET_NAME.LOOKUP_MEANING('MRP_FLP_SUPPLY_DEMAND_TYPE', ...) and related lookups such as MRP_ORDER_TYPE and MRP_DEMAND_ORIGINATION. In other words, the descriptive "type" text that a planner sees in FLP-based output is generated inside this view's SELECT list.

Underlying Base Objects

The view is defined over the following documented base objects: MSC_DEMANDS (SYNONYM), MSC_FULL_PEGGING (SYNONYM), MSC_SUPPLIES (SYNONYM), MSC_ITEMS (SYNONYM), and the MSC_GET_NAME (PACKAGE). The pegging alias MFP supplies the driving rows (ORGANIZATION_ID, PLAN_ID, PEGGING_ID, DEMAND_ID, INVENTORY_ITEM_ID, ALLOCATED_QUANTITY, SUPPLY_TYPE). Demand detail such as using requirement quantity, assembly demand date, origination type, project, task, order number, and SR instance is drawn through the MGR alias (the pegged demand record), while MR contributes NEW_ORDER_QUANTITY and NEW_SCHEDULE_DATE. MSC_ITEMS provides ITEM_NAME and description via MIF. The MSC_GET_NAME package supplies lookup translation, organization codes, project/task resolution, and supply order generation.

Key Columns

  • ORGANIZATION_ID / PLAN_ID / PEGGING_ID — the planning context and pegging identity for each row.
  • DEMAND_ID / TRANSACTION_ID / INVENTORY_ITEM_ID — the demand record and item linkage; DEMAND_ID = -1 marks internally generated demand.
  • PREV_PEGGING_ID — prior link in the pegging chain, defaulted to -1 via NVL.
  • Allocated / New Order / Requirement quantities — ROUND(MFP.ALLOCATED_QUANTITY,2) and, depending on DEMAND_ID, either ROUND(MGR.USING_REQUIREMENT_QUANTITY,2) or ROUND(MR.NEW_ORDER_QUANTITY,2).
  • Date column — MR.NEW_SCHEDULE_DATE or MGR.USING_ASSEMBLY_DEMAND_DATE depending on the demand branch.
  • Type / label column — the DECODE expression that calls LOOKUP_MEANING on MRP_FLP_SUPPLY_DEMAND_TYPE, MRP_ORDER_TYPE, and MRP_DEMAND_ORIGINATION.
  • Order number — MGR.ORDER_NUMBER for origination type 6, otherwise MSC_GET_NAME.SUPPLY_ORDER(...).
  • Item / org — ITEM_NAME||'/'||ORG_CODE, plus a SUBSTR of the item description to 20 characters.
  • Project and Task — resolved through MSC_GET_NAME.PROJECT and MSC_GET_NAME.TASK.

Common Use Cases and Queries

Typical uses include end-demand reporting, pegging diagnostics, and translating raw supply/demand codes into planner-readable text.

  • List end demands per plan and organization.
  • Inspect pegging chains for a specific item.
  • Report demand type labels for a given MRP_FLP_SUPPLY_DEMAND_TYPE code.
  • Reconcile allocated versus requirement quantities.
  • Extract project/task-tagged demand for project-driven planning.
SELECT organization_id, plan_id, inventory_item_id,
       demand_id, allocated_quantity, new_order_quantity
FROM   apps.msc_flp_end_demand_v
WHERE  plan_id = :plan_id
AND    organization_id = :org_id;

Because the view joins pegging to demand and supply and invokes MSC_GET_NAME for every descriptive column, queries should always filter on PLAN_ID and ORGANIZATION_ID to avoid full scans across large planning datasets.