Search Results create_snap2

Overview

MSC_UTIL is a foundational utility package in the APPS schema of Oracle E-Business Suite, belonging to the Advanced Supply Chain Planning (ASCP/MSC) product family. Its header identifies the source as MSCUTILS.pls, version 120.24.12010000.3, last shipped in 2008. The package serves as a shared service layer for the MSC schema, centralizing constants, diagnostic logging, staging infrastructure management, and DDL helpers that would otherwise be duplicated across planning modules. It is classified as a UTIL API, indicating it is not a business-facing interface but an internal building block consumed by other PL/SQL units. The reference metadata records 94 dependent packages, confirming its role as a horizontal dependency across supply chain planning and collections processing. The constants declared in the specification span task types, collection modes, ASL handling, SCE company scoping, and staging table status, providing a single canonical vocabulary for the MSC codebase.

Key Procedures and Functions

The 42 documented procedures and functions fall into several functional clusters. Diagnostic and logging routines include LOG_MSG, MSC_LOG, MSC_OUT, MSC_DEBUG, CHECK_MSG_LEVEL, PRINT_MSG, MSC_SET_DEBUG_LEVEL, and PRINT_TOP_WAIT, which together implement the package’s message emission and debug-level control, driven by the MRP_DEBUG profile option read into G_MSC_DEBUG. Diagnostic reporting is extended by PRINT_CUM_STAT, PRINT_BAD_SQLS, PRINT_ODS_PARAMS, PRINT_PULL_PARAMS, PRINT_TRACE_FILE_NAME, and GET_STORAGE_PARAMETERS. The procedure the user searched for, PRINT_PULL_PARAMS, belongs to this diagnostic group: it prints the parameters associated with a data pull operation, allowing a developer or support analyst to inspect what was passed into a collection or refresh invocation.

Infrastructure and DDL helpers include CREATE_SNAP, CREATE_SNAP2, CREATE_SNAP2_AS, CREATE_SNAP_LOG, CREATE_INDEX, and COMPARE_INDEX. These support snapshot table creation, logging of snapshot activity, and index comparison or replication across planning instances, drawing on the ALL_INDEXES, ALL_IND_COLUMNS, ALL_TABLES, ALL_TRIGGERS, ALL_MVIEWS, and DBA_TABLESPACES dictionary views exposed through the referenced table list.

Tables Accessed

The package reads and writes a range of dictionary and application tables through APPS synonyms. FND_APPLICATION, FND_PRODUCT_INSTALLATIONS, FND_ORACLE_USERID, and FND_TABLESPACES supply environment and installation context, particularly for the snapshot and storage-parameter routines. MSC_APPS_INSTANCES supports multi-instance and collections configuration, while MSC_CATEGORY_SETS, MSC_ITEM_SUPPLIERS, and MSC_ITEM_TYPE_DEFINITIONS provide planning data domain references. AD_DDL is used by DDL-generating routines, and the ALL_* and DBA_TABLESPACES views back the index and snapshot comparison logic.

Usage Notes

MSC_UTIL is not intended for direct end-user invocation. It is called from concurrent programs, planner workbench logic, and other MSC packages during collections, plan generation, and snapshot maintenance. Diagnostic procedures such as PRINT_PULL_PARAMS and PRINT_ODS_PARAMS are typically invoked under debug conditions, often gated by MRP_DEBUG, to emit parameter traces into log or output files. Because 94 packages reference it, changes to its public specification carry broad impact; customizations should call the documented routines rather than replicating constant values or DDL logic. The static SQL testing flag, STATSQL, is set to FALSE in the shipped specification and should not be altered in production.