Search Results end_satisfied_date




Overview
Explore in AI Chat

Overview

MSC_FLP_DEMAND_SUPPLY_V2 is a supplementary APPS view in Oracle E-Business Suite (12.1.1 and 12.2.2) that flattens the results of advanced supply chain planning pegging into a single, denormalized row set. It is owned by APPS and is registered under the FND design data MSC.MSC_FLP_DEMAND_SUPPLY_V2, with a status of VALID. The designation "FLP" refers to the full pegging engine within Oracle Advanced Supply Chain Planning (ASCP), and this view presents the relationships between demand and supply records produced by that engine, along with the "end" or terminal pegging attributes that identify the ultimate originating source of a demand. Because Oracle explicitly classifies this object as a supplementary view used to simplify forms coding, it carries a documented warning that Oracle does not recommend querying or altering data through it and that its definition "may change dramatically in subsequent minor or major releases." Practically, this means it is stable for read-only reporting on a given release but should not be treated as a permanent interface contract. It serves reporting and integration consumers who need a single-row, human-readable projection of pegging chains rather than the normalized MSC_FULL_PEGGING rows.

Underlying Base Objects

The documented referenced objects are MSC_DEMANDS, MSC_FULL_PEGGING, MSC_ITEMS, and MSC_SUPPLIES, all exposed as APPS synonyms, together with the MSC_GET_NAME package. The core join is the full pegging table (MSC_FULL_PEGGING), which holds a row per demand-supply pegging relationship keyed by PEGGING_ID and PREV_PEGGING_ID, linking a demand from MSC_DEMANDS to a supply from MSC_SUPPLIES. MSC_ITEMS supplies item and organization descriptive attributes, while the MSC_GET_NAME package resolves surrogate identifiers such as item, organization, project, and order names into display values (for example ITEM_ORG and ORDER_NAME). The "END_" prefixed columns reflect traversal of the pegging chain to its terminal node, providing the originating demand's characteristics.

Key Columns

Common Use Cases and Queries

The view supports pegging quantity reporting, demand-to-end-demand traceability, and downstream integration feeds. A typical pattern aggregates terminal pegged quantities by end item:

SELECT end_item_org, inventory_item_id, SUM(end_pegged_qty) pegged_total FROM apps.msc_flp_demand_supply_v2 WHERE plan_id = :p_plan_id GROUP BY end_item_org, inventory_item_id ORDER BY pegged_total DESC;

To trace a specific demand's pegging chain to its end source:

SELECT demand_id, pegging_id, prev_pegging_id, end_pegged_qty, end_demand_qty, end_demand_date, end_disposition FROM apps.msc_flp_demand_supply_v2 WHERE plan_id = :p_plan_id AND demand_id = :p_demand_id ORDER BY pegging_id;

Because of the supplementary-view warning, production queries should be pinned to a specific release, validated against the underlying MSC_FULL_PEGGING table, and re-tested before any upgrade.