Search Results end_demand_class




Overview
Explore in AI Chat

Overview

APPS.MSC_FLP_END_DEMAND_V is a reporting and integration view within the Oracle Advanced Supply Chain Planning (ASCP) schema, exposed through the APPS account. The suffix "FLP" denotes its association with the Full Pegging and end-demand analysis functionality used in the MSC (MSC = Manufacturing Scheduling and Constraint) planning tables. The view consolidates end-demand records against their associated supply, pegged requirement, and item context, producing a flattened, human-readable representation of planning pegging relationships. It is consumed by planner workbenches, pegging reports, and downstream supply-demand reconciliation queries that need to translate numeric type codes (order types, demand types, supply types) into descriptive lookup meanings.

Because the view calls the MSC_GET_NAME package and applies DECODE logic, it is one of the mechanisms by which internal supply-demand type codes are surfaced as readable labels. This makes it directly relevant to the search term mrp_order_type, since the view resolves MRP_ORDER_TYPE lookup meanings for supply records.

Underlying Base Objects

The view is defined over the following documented base objects:

  • MSC_DEMANDS (synonym) — source of demand records.
  • MSC_FULL_PEGGING (synonym) — the core pegging table holding allocated quantities, pegging IDs, and prior pegging references (aliased MFP in the view text).
  • MSC_SUPPLIES (synonym) — supply records referenced through pegging.
  • MSC_ITEMS (synonym) — item master information used for item names and descriptions.
  • MSC_GET_NAME (package) — supplies lookup_meaning, supply_order, org_code, item_desc, project, and task functions used to decode codes into labels.

The view joins the pegging table (MFP) to demand/requirement rows (aliased MGR/MR) so that each pegged allocation is presented alongside its originating requirement quantity, order quantity, and associated dates.

Key Columns

  • ORGANIZATION_ID, PLAN_ID — planning context for the record.
  • PEGGING_ID, DEMAND_ID, TRANSACTION_ID — pegging and demand identity keys.
  • INVENTORY_ITEM_ID — item reference, resolved via MSC_ITEMS.
  • Allocated / Using Requirement / New Order Quantity — numeric measures rounded to two decimals, providing supply-demand quantities.
  • Date column — returns schedule date or assembly demand date depending on whether DEMAND_ID equals -1.
  • Type label column — a DECODE-driven string combining MRP_FLP_SUPPLY_DEMAND_TYPE and MRP_ORDER_TYPE lookup meanings. This is the column most closely tied to the mrp_order_type search, since supply types 10, 13, 18, and others are translated via MRP_ORDER_TYPE.
  • Order number / supply order — resolved by MSC_GET_NAME.supply_order.
  • Item name / org code — concatenated display field from MSC_ITEMS and org_code.
  • Item description — first 20 characters of the item description.
  • Project / Task — project and task context carried from pegging or requirement rows.

Common Use Cases and Queries

Typical uses include end-demand pegging reports, supply-demand reconciliation, and translating supply type codes for planners. Sample SQL:

  • SELECT organization_id, plan_id, inventory_item_id, allocated_quantity, new_order_quantity FROM apps.msc_flp_end_demand_v WHERE plan_id = :plan;
  • SELECT inventory_item_id, mrp_order_type_label FROM apps.msc_flp_end_demand_v WHERE organization_id = :org; (using the decoded type label column to inspect MRP_ORDER_TYPE meanings).
  • SELECT project, task, demand_id, allocated_quantity FROM apps.msc_flp_end_demand_v WHERE project IS NOT NULL;

Because the view invokes package functions for each row, performance on large plans can be significant; filters on PLAN_ID and ORGANIZATION_ID should always be applied to constrain the pegging set.