Results for “schedule_designator_id”

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

Overview

MSC_SUPPLY_PEGGING_V is an APPS-owned database view within the MSC (Advanced Supply Chain Planning) product module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It exposes the pegging relationships that link supply orders to the demand they satisfy, resolved to a single row per allocated supply-to-demand link. The view is used by planning reports, dashboards, and integration extracts that need to trace where a given scheduled receipt or order is consumed, and, conversely, which supply is committed against a particular demand.

The view is particularly relevant for users searching on supply_date. Rather than returning a raw supply date column from the base supplies table, the view aliases S.NEW_SCHEDULE_DATE as SUPPLY_DATE, making the rescheduled planning date the authoritative date attribute for the supply side of the peg. This distinction matters because MSC_SUPPLIES stores multiple date attributes, and NEW_SCHEDULE_DATE reflects the plan-adjusted schedule date used by the planning engine rather than the original order date.

Underlying Base Objects

The view is defined over three referenced base objects, all exposed in the APPS schema as synonyms: MSC_DEMANDS, MSC_FULL_PEGGING, and MSC_SUPPLIES. MSC_FULL_PEGGING is joined twice in the view text, aliased PEG1 and PEG2, because pegging is stored as a chained structure. PEG1 identifies the demand-side end of the peg, while PEG2 identifies the supply-side end, and the two are linked by the condition PEG2.END_PEGGING_ID = PEG1.PEGGING_ID within the same plan.

MSC_DEMANDS is joined on PLAN_ID, DEMAND_ID, SR_INSTANCE_ID, and INVENTORY_ITEM_ID to recover demand attributes such as DEMAND_CLASS. MSC_SUPPLIES is joined on PLAN_ID, TRANSACTION_ID, and SR_INSTANCE_ID to recover supply attributes including the schedule date, order type, and order number. The joins are inner joins, so only fully resolved pegging chains with matching demand and supply records are returned. Because the objects are synonyms in APPS rather than physical tables, the view is portable across planning schemas and instances without hard-coding a physical owner.

Key Columns

• PLAN_ID — The planning plan instance; every column predicate in the view is scoped to a single plan.
• INVENTORY_ITEM_ID — The planned item for which pegging is resolved.
• ORGANIZATION_ID — The inventory organization associated with the supply record.
• SR_INSTANCE_ID — Identifies the source instance, typically the source ERP system feeding the planning instance.
• DEMAND_CLASS — Demand classification derived from MSC_DEMANDS; the view applies NVL(..., '-1') so unclassified or null demand classes surface as the literal value '-1' rather than null.
• SUPPLY_DATE — Aliased from MSC_SUPPLIES.NEW_SCHEDULE_DATE; the plan-adjusted schedule date of the supplying order.
• ALLOCATED_QUANTITY — The quantity of the supply pegged to this demand.
• TRANSACTION_ID — Identifier of the supply transaction, useful for drill-through to the supply record.
• ORDER_TYPE and ORDER_NUMBER — Descriptive identifiers of the supplying order, supporting human-readable reporting.
• SCHEDULE_DESIGNATOR_ID — The schedule designator for the supply order, relevant for repetitive and supplier scheduling environments.

Common Use Cases and Queries

The most frequent requirement is time-phased pegging analysis: identifying all supplies pegged to open demand within a date window, which is exactly why SUPPLY_DATE is aliased rather than referenced directly. A representative query filters by plan and date range and aggregates allocated quantity by item and date:

• SELECT inventory_item_id, supply_date, SUM(allocated_quantity) FROM msc_supply_pegging_v WHERE plan_id = :p_plan_id AND supply_date BETWEEN :p_from AND :p_to GROUP BY inventory_item_id, supply_date ORDER BY supply_date;

Other practical scenarios include tracing a specific supply order back to its consuming demands using ORDER_NUMBER and ORDER_TYPE, reconciling demand class consumption by filtering on DEMAND_CLASS while excluding the '-1' placeholder, and building integration extracts that feed downstream reporting for supply chain planners. Because ORGANIZATION_ID and SR_INSTANCE_ID are exposed, the view supports multi-organization and multi-instance reporting in a single query.

Performance considerations follow from the double join to MSC_FULL_PEGGING: queries should always restrict on PLAN_ID, which is indexed and participates in every join condition, and apply item or date filters where possible to limit the pegging chain traversal.