Search Results msc_flp_supply_demand_v2




Overview
Explore in AI Chat

Overview

MSC_FLP_SUPPLY_DEMAND_V2 is an APPS-owned database view in the Oracle Advanced Supply Chain Planning (MSC) module. It presents a flattened, denormalized representation of supply and demand pegging relationships produced by the Oracle Advanced Supply Chain Planning engine. Rather than exposing raw pegging rows, the view joins demand and supply records against the planning pegging infrastructure and resolves surrogate identifiers into human-readable descriptions using the MSC_GET_NAME package. The "_V2" suffix indicates this is a later revision of the original supply/demand pegging view, with revised logic for deriving supply-side demand context — most notably the DECODE branches that treat DEMAND_ID values of -1, -2, and -3 as special supply-originated rows and resolve them through the MRP_FLP_SUPPLY_DEMAND_TYPE lookup, while all other rows resolve through the MRP_DEMAND_ORIGINATION lookup.

The view is typically consumed by planners, supply chain analysts, and custom reporting layers that need to trace which supply is pegged to which demand, along with the associated allocation quantity, assembly demand date, and project context.

Underlying Base Objects

The documented base objects underlying MSC_FLP_SUPPLY_DEMAND_V2 are:

Key Columns

  • PLAN_ID, ORGANIZATION_ID — planning scenario and inventory organization context.
  • PEGGING_ID, PREV_PEGGING_ID — the pegging chain identifiers linking supply to demand.
  • DEMAND_ID, TRANSACTION_ID — the demand record and originating transaction.
  • INVENTORY_ITEM_ID — item key, displayed alongside ITEM_NAME concatenated with the organization code.
  • ALLOCATED_QUANTITY — quantity of supply allocated to the pegged demand, rounded to two decimals.
  • END_ITEM_USAGE — usage quantity of the end item; the view derives a per-unit allocation by dividing ALLOCATED_QUANTITY by END_ITEM_USAGE.
  • USING_REQUIREMENT_QUANTITY / NEW_ORDER_QUANTITY — demand-side and order-side quantities, both rounded.
  • ORIGINATION_TYPE and derived lookup meaning — resolved via MRP_DEMAND_ORIGINATION or, for supply-originated rows (-1/-2/-3), via MRP_FLP_SUPPLY_DEMAND_TYPE.
  • PROJECT and TASK — project/task names returned by MSC_GET_NAME, relevant to project-driven supply chains (including lending/borrowing and inter-project transfer scenarios).
  • USING_ASSEMBLY_DEMAND_DATE / SUPPLY_DATE — the demand date or, for supply rows (DEMAND_ID = -1), the supply date.

Common Use Cases and Queries

The primary use case is pegging analysis: determining, for a given plan and item, which demands consume which supplies, and under what project or task context. Because PROJECT and TASK are surfaced as resolved names, the view is frequently used to audit project-based material movements, including lending and borrowing between projects where reference identifiers such as a lending project identifier are used to attribute demand back to the borrowing project.

Example query retrieving pegged supply/demand detail for a plan:

SELECT plan_id, organization_id, inventory_item_id,
       allocated_quantity, using_requirement_quantity,
       using_assembly_demand_date, demand_id, project, task
FROM   apps.msc_flp_supply_demand_v2
WHERE  plan_id = :plan_id
AND    organization_id = :org_id
AND    inventory_item_id = :item_id;

To isolate project-specific pegging, filter on the resolved project column, and correlate with MSC_DEMANDS.PROJECT_ID when a numeric project identifier is required. Performance is generally governed by the underlying MSC_FULL_PEGGING and MSC_DEMANDS access paths, so filtering on PLAN_ID and ORGANIZATION_ID is advisable.