Search Results is_pf_fcstable_for_item
Overview
MSD_DEM_COMMON_UTILITIES is a shared PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite, traditionally associated with the Demand Planning and Advanced Supply Chain Planning (ASCP/MSC) family of applications. In EBS 12.1.1 and 12.2.2 it functions as a foundational helper library rather than a business transaction API: it centralizes constants, profile lookups, logging routines, and cross-instance connectivity helpers that the wider MSD_DEM codebase depends upon. It is referenced by at least 40 other packages, indicating its role as a low-level building block consumed throughout the demand planning and collections infrastructure.
The package body declares a large set of PL/SQL constants that model the planning domain. These include entity type constants (hierarchy and series), hierarchy entity identifiers (item, ship-from, trading partner, demand class, sales channel, time), series identifiers (return history, backlog and on-hand variants, SRP usage and return history, install base history, total and past-due backlog, on-hand inventory, and actual production), level types, Yes/No flags, and collection type constants (refresh and net change). Constants also define standard values used in UOM conversion and calendar calculations.
Key Procedures and Functions
The package exposes 64 documented procedures and functions. The most frequently consulted members relate to diagnostics: LOG_MESSAGE writes an arbitrary text buffer to the concurrent request log file, while LOG_DEBUG writes a debug message but only when the profile option MSD_DEM_DEBUG is enabled (the package reads the profile MSD_DEM_DEBUG_MODE at initialization, defaulting to 'N' via NVL). These two routines are the reason the package appears in searches for "msd_dem_debug".
- GET_DBLINK and GET_DEST_DBLINK — resolve database link names used for distributed collections and cross-instance access.
- GET_INSTANCE_INFO and GET_SR_INSTANCE_ID_FOR_ZONE — retrieve source instance identity, including the single-row instance id mapped to a region/zone.
- GET_SCHEMA_NAME — returns the schema name appropriate for the calling context.
- REFRESH_PURGE_SERIES, UPDATE_SYNONYMS, CLEANUP_ENTITIES_INUSE — maintenance helpers used when refreshing data series, repointing synonyms, and releasing entities still marked in use.
- GET_ALL_ORGS, DM_TIME_LEVEL, GET_PARAMETER_VALUE, GET_LOOKUP_VALUE, GET_UOM_CODE, UOM_CONVERT, GET_SUPPLIER_CALENDAR, GET_SAFETY_STOCK_ENDDATE, IS_PF_FCSTABLE_FOR_ITEM, IS_PRODUCT_FAMILY_FORECASTABLE — general-purpose planners' helpers for organization lists, time-level derivation, profile/parameter retrieval, lookup decoding, UOM conversion, supplier calendar and safety-stock date resolution, and forecastability checks for items and product families.
Tables Accessed
The package reads and writes through APPS synonyms, primarily against MSC and FND objects: MSC_APPS_INSTANCES (source instance registration), MSC_PLANS and MSC_SYSTEM_ITEMS (planning definitions and item master), MSC_REGIONS (zone to instance mapping), MSC_CALENDAR_DATES, MSC_CAL_WEEK_START_DATES, and MSC_PERIOD_START_DATES (calendar and bucket boundary lookups), MSC_SAFETY_STOCKS (safety-stock end dating), MSC_ITEM_SUPPLIERS (supplier sourcing), MSC_CATEGORY_SET_ID_LID, MSC_TP_ID_LID, MSC_TP_SITE_ID_LID, and MSC_TRADING_PARTNERS (trading partner hierarchy identifiers), plus FND_LOOKUP_VALUES and FND_USER for lookup decoding and user context.
Usage Notes
MSD_DEM_COMMON_UTILITIES is invoked indirectly by the 40+ dependent packages rather than through end-user forms or standalone concurrent programs. It executes inside collections, demand planning, and purge/refresh concurrent requests, and is also callable from custom SQL or PL/SQL where consistent logging, instance resolution, UOM conversion, or lookup decoding is required. Because the debug behavior is governed by MSD_DEM_DEBUG_MODE, setting that profile to 'Yes' is the standard technique for obtaining LOG_DEBUG output during troubleshooting in both 12.1.1 and 12.2.2.