Search Results msc_item_pkg




Overview
Explore in AI Chat

Overview

APPS.MSC_ITEM_PKG is a PL/SQL package in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privilege set of the calling user rather than the package owner, which is a standard convention for ASCP planning engine packages invoked from concurrent manager sessions. The package, whose header carries the source identifier MSCHBITS.pls at version 120.8 (dated 2011/05/04), acts as the item-level data management routine for the MSC (Supply Chain Planning) schema. It orchestrates the movement of item inventory and order data between the planning staging tables and the planning fact tables, and supports the export and import of that data across instances — for example, between a source transaction system and a planning server, or between two EBS instances in a supply chain hub configuration.

Key Procedures and Functions

The package exposes seven documented procedures, invoked as concurrent program entry points with the standard errbuf and retcode out parameters:

  • POPULATE_DETAILS — Populates detailed planning data for a given plan and plan run. It is the foundational routine that seeds lower-level item details consumed by the summarize and export procedures.
  • SUMMARIZE_ITEM_INVENTORY_F — Aggregates inventory level data into the MSC_ITEM_INVENTORY_F planning fact table for a specified plan and run.
  • SUMMARIZE_ITEM_ORDERS_F — Aggregates supply and demand order data into the MSC_ITEM_ORDERS_F planning fact table.
  • EXPORT_ITEM_INVENTORY_F — Extracts item inventory data for a source transaction ID and plan run, writing it across a database link (p_dblink) to a target instance, tagged with a source version.
  • EXPORT_ITEM_ORDERS_F — Performs the equivalent extraction for order data, again across a database link.
  • IMPORT_ITEM_INVENTORY_F — Imports previously exported inventory data into the local planning tables. This is the procedure most commonly associated with the search term import_item_inventory_f. It accepts a transaction ID, plan and run identifiers, plan type, plan start and cutoff dates, an upload mode, an overwrite-after date, and a default instance code, which together govern how incoming records are merged and how stale data is replaced.
  • IMPORT_ITEM_ORDERS_F — Mirrors the inventory import for order data, using the same controlling parameters.

Tables Accessed

The package references a broad set of ASCP tables via APPS synonyms. MSC_PLANS and MSC_PLAN_RUNS provide plan definition and run context. MSC_ITEM_INVENTORY_F, MSC_ITEM_ORDERS_F, MSC_ST_ITEM_INVENTORY_F, and MSC_ST_ITEM_ORDERS_F are the planning fact and staging tables that are written during summarize and import operations. MSC_INVENTORY_LEVELS and MSC_SAFETY_STOCKS supply on-hand and safety stock inputs, while MSC_DEMANDS and MSC_DEMANDS_F hold demand data. MSC_EXCEPTIONS_F, MSC_FULL_PEGGING, MSC_APCC_ITEM_D, MSC_BIS_INV_DETAIL, and MSC_HUB_QUERY are consulted or updated during detail population and pegging analysis.

Usage Notes

In practice, MSC_ITEM_PKG procedures are registered as concurrent programs and invoked by the ASCP planning manager rather than called interactively. The export and import procedures are central to distributed planning or multi-instance supply chain deployments, where data is staged, transferred over a database link, and merged using the upload mode and overwrite-after-date parameters. Custom code should call these procedures only through a concurrent request or a similarly controlled session, supplying valid plan, run, and transaction identifiers, and should respect the AUTHID CURRENT_USER security model by ensuring the invoking user has the necessary privileges on the referenced MSC tables.