Search Results msc_st_util




Overview
Explore in AI Chat

Overview

MSC_ST_UTIL is a utility package body in the APPS schema that supports the Oracle Advanced Supply Chain Planning (ASCP) and Strategic Network Optimization (SNO) staging and interface layer within Oracle E-Business Suite 12.1.1 and 12.2.2. Its classification as a UTIL object indicates that it does not expose a public business API for external callers; instead it provides shared helper routines consumed internally by planning data-collection, staging, and load programs. The package centralises two broad categories of work: derivation of surrogate keys and identifiers required to populate MSC staging tables, and consistent error and message handling for batch planning jobs. The ETRM metadata records the object as VALID, with 43 documented procedures and functions, and notes that although it is not referenced by any database object directly, it is referenced by 14 other packages, confirming its role as a common dependency in the ASCP staging code base.

Key Procedures and Functions

The documented routines fall into several functional groups.

No parameter lists are documented in the ETRM record; callers should inspect the package specification in the target instance before invoking these routines directly.

Tables Accessed

The package body references FND_RESPONSIBILITY, FND_USER_RESP_GROUPS, FND_PROFILE, and FND_GLOBAL for session, responsibility, and profile context, and uses FND_FILE for log output. Planning-specific data is drawn from MSC_APPS_INSTANCES, MSC_COMPANIES, MSC_COMPANY_USERS, MSC_ERRORS, MSD_ST_TIME, and MSD_TIME, which supply instance configuration, company and user mapping, error logging, and staging time-window information. DUAL and the STANDARD package are used for trivial SQL evaluations and standard operations.

Usage Notes

MSC_ST_UTIL is not intended for direct invocation from forms or custom code. It is called by the planning data-collection and staging packages that populate the MSC_ST_* interface tables, and its LOG_ERROR and LOG_MESSAGE routines surface in concurrent program logs and request output. Because 14 packages depend on it, changes to its specification can cascade across ASCP staging code; it should be treated as an internal, version-sensitive dependency. In 12.1.1 and 12.2.2 the package ships as a VALID APPS object and is not referenced by any database object, so troubleshooting should focus on its calling packages rather than on database-level dependencies.