Results for “item_type_value”

50+ results




Overview
Explore in AI Chat

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

Overview

The MSC_VERTICAL_PLAN_V view is an Oracle E-Business Suite Advanced Supply Chain Planning (MSC) database object owned by the APPS schema. As its documentation states, the view "shows the vertical plan," meaning it presents planned supply and demand activity distributed vertically across calendar dates rather than aggregated into a single schedule row. Each row of the view represents a single item, organization, and calendar date combination, with the associated planned quantity exposed on that date.

The view sits within the MSC planning schema and draws exclusively on planning tables and staging data that are populated by the Advanced Supply Chain Planning engine. It is therefore a read-only reporting object rather than a transactional interface. Functional users, BI Publisher reports, and custom concurrent programs use it to inspect time-phased planned order quantities, firm planned orders, and dependent demand originating from sales orders and other demand sources.

The user's search term "mrp_demand_origination" is directly relevant: the view's UNION ALL second branch selects from MSC_DEMANDS, and the demand origination logic distinguishes demand records by source type, order number, and originating entity. Analysts searching on that term are typically attempting to trace where a given demand quantity originated within the vertical plan.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects, all accessed through APPS synonyms unless noted otherwise:

The view is a UNION ALL of a supply projection and a demand projection, so a single query can return both supply and demand rows for the same item and date. Order types 14, 15, and 27/28 map to WIP entity names, while types 1, 2, 3, 7, 8, 11, and 12 resolve to the order number.

Key Columns

  • TRANSACTION_ID / DEMAND_ID — the primary identifier from the originating supply or demand record.
  • INVENTORY_ITEM_ID, ORGANIZATION_ID, PLAN_ID, SR_INSTANCE_ID — the planning key that uniquely positions the record within a given plan and source instance.
  • ORGANIZATION_CODE, ITEM_NAME, DESCRIPTION — descriptive attributes denormalized from MSC_SYSTEM_ITEMS for reporting convenience.
  • CALENDAR_DATE — the vertical date bucket on which the quantity falls, bounded by the supply's new schedule date and last unit completion date.
  • ORDER_TYPE and the resolved MRP_ORDER_TYPE meaning — classifies the row as a planned order, WIP job, purchase order, sales order, or similar.
  • NVL(DAILY_RATE, NEW_ORDER_QUANTITY) — the planned quantity attributed to that date.
  • PLANNING_GROUP, PROJECT_ID, TASK_ID — planning and project accounting context.

The DISPOSITION_STATUS_TYPE predicate restricts non-firm records while retaining firm planned orders and specified WIP supply types, which affects which rows appear in a query result.

Common Use Cases and Queries

Typical uses include time-phased supply/demand reporting, pegging and origination analysis, and dashboard extracts. A representative query filters by plan and item:

  • SELECT inventory_item_id, organization_code, calendar_date, order_type, quantity FROM msc_vertical_plan_v WHERE plan_id = :p_plan AND inventory_item_id = :p_item AND calendar_date BETWEEN :p_from AND :p_to ORDER BY calendar_date;
  • To analyze demand origination, join to MSC_DEMANDS on TRANSACTION_ID or DEMAND_ID to retrieve the source order type and originating document.
  • To compare supply versus demand by day, aggregate the quantity column grouped by CALENDAR_DATE and ORDER_TYPE.

Because the view expands records across calendar dates, row counts can be large; always constrain by PLAN_ID and a date range to maintain acceptable performance.