Results for “msc_demands_mv_v”

24 results




Overview
Explore in AI Chat

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

Overview

MSC_DEMANDS_MV_V is a read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, delivered as part of the MSC (Advanced Supply Chain Planning) product family. Its status is documented as VALID. The view exposes a filtered subset of the planning demand records held in the MSC_DEMANDS base object, restricted to specific origination types. It is an MV-suffixed view, indicating that it is associated with materialized-view based extraction used by Advanced Supply Chain Planning for high-volume planning data movement and refresh.

Because the view is owned by APPS and references a synonym name in its metadata, it is accessible to reporting tools, custom Concurrent Programs, Oracle Discoverer workbooks, and BI Publisher data models in the same manner as other deployed MSC database objects. It carries no business logic of its own beyond a projection and a filter, so it inherits the transactional and planning state of MSC_DEMANDS at query time.

Underlying Base Objects

The view's documented base object is a synonym whose underlying object is MSC_DEMANDS in the MSC schema. The view text is:

Only nine columns are projected from what is a very wide base table. The ORIGINATION_TYPE predicate restricts output to a hard-coded list of thirteen type codes, which correspond to planning-relevant demand sources such as sales orders, inter-org transfers, and related supply-chain demand streams. Records originating from other demand sources are excluded.

Key Columns

  • DEMAND_ID — Primary identifier of the demand record, unique within MSC_DEMANDS.
  • PLAN_ID — Identifier of the plan to which the demand record belongs; essential for scoping queries to a single planning run.
  • ORGANIZATION_ID — Inventory organization that owns the demand.
  • SR_INSTANCE_ID — Source instance identifier, used to distinguish data sourced from different ERP instances in a multi-instance planning setup.
  • ASSEMBLY_DEMAND_COMP_DATE — Assembly demand completion date as recorded on the demand record; may be null.
  • USING_ASSEMBLY_DEMAND_DATE — Derived column applying NVL over the completion date, so a non-null value is always returned for downstream comparison. This is the effective date column for most reporting purposes.
  • INVENTORY_ITEM_ID — Planned item affected by the demand.
  • PROJECT_ID — Project context for project-driven planning demands.
  • TASK_ID — Task context within a project, where applicable.

Common Use Cases and Queries

This view is typically used when reporting on planning demand lines without burdening the full MSC_DEMANDS table, and to leverage the standardized origination-type filter. A common query joins to the item master to produce a readable demand report:

  • SELECT d.demand_id, d.plan_id, d.organization_id, d.inventory_item_id, d.using_assembly_demand_date FROM apps.msc_demands_mv_v d WHERE d.plan_id = :p_plan_id ORDER BY d.using_assembly_demand_date;

A second pattern reconciles demand volumes by source instance in a multi-instance environment:

  • SELECT d.sr_instance_id, COUNT(*) demand_count FROM apps.msc_demands_mv_v d WHERE d.plan_id = :p_plan_id GROUP BY d.sr_instance_id;

A third pattern restricts output to project-related demands:

  • SELECT d.demand_id, d.project_id, d.task_id FROM apps.msc_demands_mv_v d WHERE d.project_id IS NOT NULL AND d.plan_id = :p_plan_id;

Because the view composes no new columns beyond the NVL expression, partitioning predicates on PLAN_ID and ORGANIZATION_ID are the most effective way to control query cost.