Results for “msc_flp_end_demand2_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_FLP_END_DEMAND2_V is a seeded Oracle E-Business Suite view owned by the APPS schema and shipped as part of the MSC – Advanced Supply Chain Planning (ASCP) product family. Its name references the "FLP" (Flow/Planning) end-demand presentation layer used by ASCP reporting and diagnostic tooling. The view presents a flattened, user-readable projection of end-item demand records held in the planning tables, resolving raw foreign-key identifiers into descriptive values through the MSC_GET_NAME package. It joins the demand transaction table MSC_DEMANDS to the planning item master MSC_ITEMS to produce a single denormalized row per demand line. The view is documented as VALID in both EBS 12.1.1 and 12.2.2 and is commonly leveraged by ASCP planners, functional analysts, and technical consultants who need to inspect unmet, satisfied, and component-level demand without navigating the normalized planning schema directly.

Underlying Base Objects

The view is defined over two documented base objects and one package:

• MSC_DEMANDS (SYNONYM) — aliased as MGR, the primary driver of the query, providing demand quantities, dates, and type/priority attributes.
• MSC_ITEMS (SYNONYM) — aliased as MIF, joined on INVENTORY_ITEM_ID to supply the item name used in the ITEM_ORG concatenation.
• MSC_GET_NAME (PACKAGE) — a utility package that resolves codes such as lookup meanings, organization codes, project/task numbers, supply order numbers, and customer names.

The join condition is a simple equality on INVENTORY_ITEM_ID, meaning the view only returns rows where the demand item exists in MSC_ITEMS. The MSC_GET_NAME functions execute at query time and introduce per-row overhead, so filtering on PLAN_ID, ORGANIZATION_ID, and INVENTORY_ITEM_ID before fetching descriptive columns is strongly advised.

Key Columns

Notable columns returned by the view include:

• USING_REQUIREMENTS_QUANTITY — the requirement quantity consumed by a dependent (component) demand; it is wrapped in ROUND(...,2) in the view text, so values are returned with two decimal places. This is the column most commonly referenced by the search term "using_requirements_quantity".
• USING_ASSEMBLY_DEMAND_DATE and ASSEMBLY_DEMAND_COMP_DATE — the assembly demand date and its completion counterpart.
• DEMAND_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, PLAN_ID, SR_INSTANCE_ID — the primary planning keys.
• DEMAND_TYPE, ORIGINATION_TYPE, ORIGINATION_NAME — demand classification; ORIGINATION_NAME is decoded via LOOKUP_MEANING('MRP_DEMAND_ORIGINATION', ...).
• DISPOSITION — supply order reference; where ORIGINATION_TYPE = 6 it returns ORDER_NUMBER, otherwise it is derived by SUPPLY_ORDER.
• ITEM_ORG, DESCRIPTION — item name concatenated with org code, and a 20-character truncated description.
• PROJECT_NUMBER, TASK_NUMBER, LENDING_PROJECT_NUMBER, LENDING_TASK_NUMBER, UNIT_NUMBER — project/contract manufacturing context.
• SATISFIED_DATE, CUSTOMER, DEMAND_PRIORITY, ATTRIBUTE1 — satisfaction timing, customer identity, priority, and a flexible attribute.

Common Use Cases and Queries

Typical scenarios include analyzing component ("using") requirements against their parent assembly, reviewing end demand by plan and organization, and reconciling satisfied versus unsatisfied demand. A representative query is:

• SELECT demand_id, inventory_item_id, organization_id, plan_id, using_requirements_quantity, demand_type, origination_type, disposition, item_org, satisfied_date FROM apps.msc_flp_end_demand2_v WHERE plan_id = :p_plan AND organization_id = :p_org AND using_requirements_quantity > 0 ORDER BY using_assembly_demand_date;
• Filtering by origination_type or demand_priority to isolate specific demand classes or escalation scenarios.
• Joining the view to MSC_ITEMS or plan tables on INVENTORY_ITEM_ID/PLAN_ID for extended reporting or extract construction.

Because MSC_GET_NAME is invoked repeatedly, queries returning large demand sets should constrain the driving key predicates first. The view is intended for read-only planning analysis and should not be used as a target for DML.