Search Results msc_supplies




Overview
Explore in AI Chat

Overview

The MSC_SUPPLIES table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It serves as the master table for storing all supply records generated for a specific planning run. Supplies represent the available or planned quantities of items that fulfill demands within a supply chain plan. These records can originate from various sources, including purchase orders, work orders, planned orders created by the planning engine itself, and on-hand inventory. The table's primary role is to act as the central supply-side dataset for the planning engine's calculations, pegging logic, and subsequent reporting, making it fundamental to the planning and fulfillment processes in Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table captures comprehensive metadata for each supply transaction. Its primary key uniquely identifies a record through the combination of PLAN_ID, SR_INSTANCE_ID, and TRANSACTION_ID. Essential columns include identifiers for the specific plan (PLAN_ID), the source instance (SR_INSTANCE_ID), and the item (INVENTORY_ITEM_ID, ORGANIZATION_ID). Critical supply attributes stored are the transaction type (e.g., planned order, purchase order), quantity (NEW_ORDER_QUANTITY), and key dates such as the NEW_SCHEDULE_DATE (the date the supply is available) and the ORDER_DATE. The table also supports Project Manufacturing through columns like PROJECT_ID and TASK_ID, and tracks disposition relationships via the DISPOSITION_ID, which links supplies to specific demands.

Common Use Cases and Queries

A primary use case is analyzing the output of a planning run to review planned order suggestions. Developers and planners frequently query this table to generate supply vs. demand reports, trace pegging, and validate plan feasibility. Common SQL patterns involve joining to MSC_SYSTEM_ITEMS for item details and filtering by plan and organization. For example, to list all planned order supplies for a specific item in a plan:

  • SELECT ms.supply_id, ms.transaction_id, ms.new_order_quantity, ms.new_schedule_date, msi.item_name FROM msc_supplies ms, msc_system_items msi WHERE ms.plan_id = 123 AND ms.inventory_item_id = msi.inventory_item_id AND ms.organization_id = msi.organization_id AND ms.sr_instance_id = msi.sr_instance_id AND ms.plan_id = msi.plan_id AND ms.transaction_type_name = 'Planned Order' ORDER BY ms.new_schedule_date;

Another critical scenario is investigating the pegging network by joining MSC_SUPPLIES to MSC_DEMANDS via the DISPOSITION_ID or to MSC_FULL_PEGGING via TRANSACTION_ID.

Related Objects

MSC_SUPPLIES maintains integral relationships with numerous other planning tables, as documented by its foreign keys. Key related objects include:

  • MSC_SYSTEM_ITEMS: Joined via INVENTORY_ITEM_ID, PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID to retrieve item master attributes.
  • MSC_DEMANDS: Linked via PLAN_ID and DISPOSITION_ID to identify the specific demand a supply is allocated to fulfill.
  • MSC_FULL_PEGGING: Joined on PLAN_ID and TRANSACTION_ID for detailed pegging analysis across multiple levels of the supply chain.
  • MSC_RESOURCE_REQUIREMENTS: Related via PLAN_ID and SUPPLY_ID to assess capacity consumption for manufacturing supplies.
  • MSC_PROJECTS & MSC_PROJECT_TASKS: Joined via PROJECT_ID and TASK_ID (and their implementation counterparts) for project-specific supply tracking.
  • MSC_DESIGNATORS: Joined via SCHEDULE_DESIGNATOR_ID to link to specific schedule versions.