Results for “msc_pdr_vert_list_v”

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

Overview

MSC_PDR_VERT_LIST_V is a reporting view owned by the APPS schema within the Oracle Advanced Supply Chain Planning (MSC) module. Its name reflects its purpose: it presents a "vertical list" of the planning data surfaced by the Planner Workbench and the Pegging, Distribution, and Rescheduling (PDR) functions. In Oracle EBS 12.1.1 and 12.2.2 it is a read-only view, reported as VALID, and is intended for query and reporting rather than for direct DML.

The view consolidates supply-side planning records into a flattened structure combining item, organization, and category context with scheduling and implementation detail. Each row describes a planned supply (a discrete job, purchase order, or planned order) at a given calendar date, together with the reschedule or expedite action recommended by the planning engine and the quantities involved. Because it exposes calculated columns such as action names, daily rates, and net quantities, it is principally used by planners, report developers, and integration extracts that need to surface plan output in a tabular, schedule-oriented form.

The column most often searched in connection with this view is the outstanding quantity — the open, unimplemented portion of a planned supply, expressed in the view text as the net of planned quantity less the quantity already in process.

Underlying Base Objects

The view is defined over a set of MSC synonyms, several of which resolve to the planning engine's global temporary tables. The documented base objects are MSC_SUPPLIES, MSC_DEMANDS, MSC_SYSTEM_ITEMS, MSC_ITEM_CATEGORIES, MSC_CALENDAR_DATES, MSC_PLANS, MSC_TRADING_PARTNERS, MSC_PDR_PARAMETERS, MFG_LOOKUPS, and FND_GLOBAL, together with the packages MSC_GET_NAME and MSC_GET_NAME.ACTION.

MSC_SUPPLIES is the driving table, supplying order type, order number, dates, firm and new-order quantities, implemented quantity, quantity in process, disposition status, and schedule designator. It is joined to MSC_SYSTEM_ITEMS for item attributes (item name, organization code, BOM item type, WIP supply type) and to MSC_ITEM_CATEGORIES for category name. MSC_CALENDAR_DATES provides the CALENDAR_DATE column that gives the view its vertically expanded, date-per-row shape. MFG_LOOKUPS and the MSC_GET_NAME package supply decoded meaning text for order types and recommended actions, while FND_GLOBAL supplies the runtime session context.

Key Columns

• ORGANIZATION_CODE, ITEM_NAME, CATEGORY_NAME — identification of the planned item and its planning organization and category.
• PLANNING_GROUP, PROJECT_ID, TASK_ID — planning and project/task classification of the supply.
• ORDER_NUMBER / TRANSACTION_ID — the supply document reference, with order type 5 decoded to the transaction identifier.
• CALENDAR_DATE — the schedule bucket date for the row.
• OLD_SCHEDULE_DATE, NEW_SCHEDULE_DATE, NEW_DOCK_DATE, NEW_WIP_START_DATE — current versus recommended dates driving the reschedule action.
• FIRM_QUANTITY, NEW_ORDER_QUANTITY, DAILY_RATE — planned quantities; NVL(DAILY_RATE, NEW_ORDER_QUANTITY) yields the effective planned quantity.
• IMPLEMENTED_QUANTITY, QUANTITY_IN_PROCESS — the portion already firmed or released versus work in progress.
• Outstanding quantity — computed as NVL(DAILY_RATE, NEW_ORDER_QUANTITY) - NVL(QUANTITY_IN_PROCESS, 0), the open balance still to be actioned.
• IMPLEMENT_AS, DISPOSITION_STATUS_TYPE, action meaning — the recommended disposition (release, reschedule in/out, cancel) returned by MSC_GET_NAME.ACTION.
• SCHEDULE_COMPRESS_DAYS, SOURCE_ORGANIZATION_ID, SUPPLIER — compression guidance and sourcing/supplier context.

Common Use Cases and Queries

Typical uses include Planner Workbench-style reschedule exception reports, outstanding supply extracts feeding downstream scheduling systems, and dashboards comparing old and new schedule dates. A representative query for outstanding quantity by item is:

• SELECT organization_code, item_name, calendar_date, order_number, NVL(daily_rate, new_order_quantity) - NVL(quantity_in_process,0) outstanding_qty FROM msc_pdr_vert_list_v WHERE NVL(daily_rate, new_order_quantity) - NVL(quantity_in_process,0) > 0 ORDER BY organization_code, item_name, calendar_date;
• SELECT organization_code, item_name, old_schedule_date, new_schedule_date, implement_as FROM msc_pdr_vert_list_v WHERE new_schedule_date <> old_schedule_date;
• SELECT plan_id, item_name, SUM(NVL(daily_rate, new_order_quantity) - NVL(quantity_in_process,0)) outstanding_total FROM msc_pdr_vert_list_v GROUP BY plan_id, item_name;

Because the view references global temporary planning tables, results are meaningful only within an active planning session and after the plan has been run; queries issued outside that context return no rows.