Search Results msc_hub_query_s




Overview

MSC_ITEM_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. It is a core component of the Oracle Advanced Supply Chain Planning (ASCP) and related MSC (Supply Chain Planning) modules. Its principal business function is to manage the summarization, export, and import of item-level inventory and order data used by the planning engine. The package consolidates detailed transactional records into planning-friendly summary tables and provides the transfer mechanisms that move item inventory and order information between source systems and the planning repository. In EBS 12.1.1 and 12.2.2, this package is marked VALID, and its metadata classifies it as an OTHER-type API rather than a formal public interface. The presence of the MSC_HUB_QUERY and MSC_HUB_QUERY_S dependencies — the latter being the object the searcher referenced — indicates that the package relies on hub query views to source and stage planning data.

Key Procedures and Functions

The documented procedures therefore follow a consistent pattern: populate, summarize, export, and import of item inventory and order facts. Parameter lists are not documented in the available metadata and are not reproduced here.

Tables Accessed

The package reads and writes a broad set of planning tables through APPS synonyms, including:

Standard dependencies on FND_GLOBAL, FND_LOG, FND_PROFILE, and Msc_phub_util support logging, profile lookups, and utility operations.

Usage Notes

MSC_ITEM_PKG is not referenced by any other database object in the metadata, indicating it is invoked directly rather than as a utility library. In practice it is typically called from ASCP concurrent programs (such as planning data collection and item summarization workers) and from planning-related forms or custom code performing export/import of item inventory and order facts. It executes under the APPS schema and relies on standard FND profile values to determine plan and organization context. Because it is a package body with no documented API classification, customizations should treat it as an internal implementation package and invoke it only through supported concurrent program entry points.