Search Results msc_collection_s




Overview
Explore in AI Chat

Overview

MSC_X_RECEIVE_CAPACITY_PKG is an Oracle Advanced Supply Chain Planning (ASCP) utility package body owned by the APPS schema. It supports the collection, calculation, and staging of supplier capacity data for inbound (receiving) capacity within the MSC (Advanced Planning) schema. Its central business role is to translate externally defined supplier capacity definitions and supply schedules into the planning data model so that capacity constraints on supplier-to-manufacturer receiving operations are properly modelled during plan runs. The "X_" prefix conventionally denotes a custom or extension package built on top of the standard ASCP collection infrastructure; the object status is VALID, confirming it is compiled against the 12.1.1 / 12.2.2 ETRM schema. It is classified as an OTHER API rather than a formal public interface, indicating it is invoked by collection and planning processes rather than exposed for general application use. Notably, the package is not referenced by any other database object, and it references no downstream packages other than within its own dependency chain.

Key Procedures and Functions

The package exposes seven documented procedures:

  • RECEIVE_CAPACITY — Entry-point procedure that accepts and validates received capacity data into the package's staging structures.
  • CALCULATE_CAPACITY — Derives effective capacity values from supplier capacity records, calendar working days, and supply schedules.
  • POPULATE_CAPACITY — Builds the working capacity data set prior to persistence, applying company, supplier, and item relationships.
  • INSERT_CAPACITY — Writes the computed capacity records into the MSC supplier capacity tables.
  • LOAD_SUPPLY_SCHEDULE — Loads supply schedule rows relevant to inbound capacity planning.
  • INSERT_MPS_DESIGNATOR — Inserts MPS designator information linking capacity rows to the correct planning designators.
  • INSERT_SUPPLY_SCHEDULE — Persists supply schedule entries derived during collection.

Detailed parameter signatures are not part of the documented metadata; only these procedure names and their functional intent are published.

Tables Accessed

The package reads and writes tables via APPS synonyms. Supplier capacity definition and staging is handled through MSC_SUPPLIER_CAPACITIES and MSC_SUPPLIER_CAPACITIES_S. Supply schedule and supply data flow through MSC_SUPPLIES, MSC_SUPPLIES_S, MSC_SUP_DEM_ENTRIES, and MSC_SUP_DEM_ENTRIES_V. Planning calendar logic uses MSC_CALENDAR_DATES, MSC_CAL_WEEK_START_DATES, MSC_CALENDAR (via package reference), and MSC_PERIOD_START_DATES. Party and item master relationships rely on MSC_COMPANIES, MSC_COMPANY_RELATIONSHIPS, MSC_COMPANY_SITES, MSC_TRADING_PARTNERS, MSC_TRADING_PARTNER_MAPS, MSC_TRADING_PARTNER_SITES, MSC_ITEMS, MSC_SYSTEM_ITEMS, MSC_ITEM_SUPPLIERS, MSC_DESIGNATORS, and MSC_DESIGNATORS_S. MSC_COLLECTION_S provides the collection staging substrate. The package also depends on standard utilities such as FND_DATE, FND_FILE, FND_GLOBAL, FND_MESSAGE, FND_PROFILE, MSC_SCE_LOADS_PKG, and MSC_X_CP_FLOW, using DUAL and STANDARD from the SYS/PUBLIC schemas.

Usage Notes

MSC_X_RECEIVE_CAPACITY_PKG is typically executed as part of ASCP data collection rather than from standard application forms. It is most commonly invoked by concurrent collection programs, either directly or through MSC_SCE_LOADS_PKG, to populate supplier receiving capacity into the planning schema before a plan run. Because it is an extension ("X_") package with no inbound references from other database objects, customisations and customer-specific collection logic are the usual callers. Implementers invoking it manually should observe the dependency order — capacity must be calculated and populated before insertion, and supply schedules loaded before designator linkage — and should run it in conjunction with the standard MSC collection cycle to maintain consistency of the MSC_COLLECTION_S staging data.