Search Results prev_demand_id




Overview
Explore in AI Chat

Overview

APPS.MSC_FLP_SUPPLY_DEMAND_V2 is a supplementary view in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) schema. The ETRM metadata classifies it as a view whose stated purpose is "to simplify forms coding," and it carries Oracle's standard caution that it should not be queried or altered directly because its definition may change dramatically across minor or major releases. The view exposes a combined supply-and-demand pegging picture for a given plan, joining demand records to the supplies and pegging relationships that satisfy them, and it additionally surfaces predecessor ("PREV_") and end ("END_") attribute sets that describe upstream and terminating nodes in the pegging chain.

The "V2" suffix and the presence of unit-number columns reflect an evolved definition aligned with project- and unit-level tracking. For the search term prev_unit_number, the view exposes a dedicated column of datatype VARCHAR2(30). This column carries the unit number associated with the previous pegging node — the predecessor supply, demand, or reservation in the same pegging thread — and parallels UNIT_NUMBER and END_UNIT_NUMBER. In EBS 12.1.1 and 12.2.2 the object is reported as VALID with owner APPS and FND design data MSC.MSC_FLP_SUPPLY_DEMAND_V2.

Underlying Base Objects

The documented base objects are:

  • MSC_DEMANDS (synonym) — source of demand rows and demand attributes.
  • MSC_SUPPLIES (synonym) — source of supply rows satisfying those demands.
  • MSC_FULL_PEGGING (synonym) — the pegging relationships linking demands to supplies, and providing the predecessor identifiers used to derive the PREV_ and END_ column groups.
  • MSC_ITEMS (synonym) — item master/plan item attributes supplying ITEM_ORG, ITEM_DESC, and their END_/PREV_ counterparts.
  • MSC_GET_NAME (package) — name-resolution package used to translate identifiers into display names for origination, project, task, order, and customer fields.

Because the view consolidates these objects, it functions as a denormalized pegging read model rather than a base storage object; all data is inherited from the underlying planning tables and package logic.

Key Columns

Common Use Cases and Queries

Typical scenarios include tracing why a demand is satisfied by a given supply, inspecting upstream pegging for unit-numbered project demands, and building exception reports on demand disposition. A representative query locating records by predecessor unit number follows:

  • SELECT plan_id, organization_id, demand_id, supply_qty, unit_number, prev_unit_number, prev_project_number, prev_task_number FROM apps.msc_flp_supply_demand_v2 WHERE plan_id = :p_plan AND prev_unit_number = :p_unit;
  • Pegging-chain reconstruction using PREV_PEGGING_ID and PEGGING_ID to walk from supply to originating demand.
  • Disposition reporting on END_DISPOSITION and END_SATISFIED_DATE for late or unfulfilled demand.

Given Oracle's documented warning, direct queries against this view should be confined to diagnostics and reporting, not to production integrations that assume a frozen column set.