Search Results msc_phub_util




Overview
Explore in AI Chat

Overview

APPS.MSC_PHUB_UTIL is a utility package body in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module, residing in the APPS schema and carrying a VALID status in both 12.1.1 and 12.2.2. Its name reflects its role as a shared helper library for the Planning Hub (PHUB) presentation layer and associated planning data extraction routines. The package consolidates low-level services that other planning packages depend upon, including session validation, profile and lookup resolution, currency conversion retrieval, logging infrastructure, and key-decoding helpers used when constructing planning hub queries.

The ETRM documentation records the package as owned by APPS with an API classification of UTIL and lists 43 documented procedures and functions. It references a broad set of FND foundation objects (APP_SESSION, FND_GLOBAL, FND_MESSAGE, FND_PROFILE, FND_RESPONSIBILITY, FND_USER, FND_USER_RESP_GROUPS, FND_WEB_SEC) together with planning data objects (MSC_PLANS, MSC_PLAN_RUNS, MSC_SCENARIOS, MSC_SCENARIO_PLANS, MSC_SYSTEM_ITEMS, MSC_DEMANTRA_F, MSC_HUB_QUERY, MSC_PHUB_ITEM_CATEGORIES_MV, MSD_DP_ASCP_SCENARIOS_V, MFG_LOOKUPS). The package is referenced by 16 other database objects but does not itself reference any that are undocumented beyond the standard SYS/STANDARD dependencies.

Key Procedures and Functions

The documented subprograms fall into several functional clusters. Session and security helpers include VALIDATE_ICX_SESSION, which confirms that an ICX web session is active before planning hub data is served, and GET_USER_NAME, which resolves the display name of the current FND user. Profile and metadata accessors include GET_REPORTING_CURRENCY_CODE, GET_CONVERSION_RATE, GET_PLAN_TYPE, IS_PLAN_CONSTRAINED, and GET_LIST_PRICE, which surface planning configuration and pricing information to callers. Exception classification routines comprise GET_EXCEPTION_GROUP and GET_EXCEPTION_DRP_GROUP, used to categorise planning exceptions for reporting.

UI and message support is provided by GET_PLANNING_HUB_MESSAGE, which retrieves user-facing messages, and by key-decoding routines DECODE_ORGANIZATION_KEY and DECODE_ITEM_KEY, which translate encoded planning hub identifiers back into their inventory organization and item equivalents. A dedicated logging subsystem includes INIT_LOG, DELETE_LOG, SET_LOG_FILE, SET_LOG_LEVEL, LOG_FILE, LOG, LOG_SQL, and SUFFIX, enabling diagnostic tracing and SQL statement capture during planning operations. All of these are utility-oriented and are intended for internal reuse rather than direct end-user invocation.

Tables Accessed

The package reads from planning and foundation tables through APPS synonyms. Planning context is obtained from MSC_PLANS, MSC_PLAN_RUNS, MSC_SCENARIOS, and MSC_SCENARIO_PLANS, which define the plan and scenario against which hub queries execute. Item and organisation context comes from MSC_SYSTEM_ITEMS. Hub query construction draws on MSC_HUB_QUERY and MSC_HUB_QUERY_S, while partner and supply data may be sourced from MSC_TRADING_PARTNERS, MSC_SUPPLIES, MSC_DEMANDS, MSC_NET_RESOURCE_AVAIL, and MSC_RESOURCE_REQUIREMENTS. Security and profile resolution use FND_USER, FND_RESPONSIBILITY, and FND_ORACLE_USERID, and metadata inspection uses AD_DDL and ALL_INDEXES.

Usage Notes

MSC_PHUB_UTIL is invoked indirectly by higher-level ASCP planning hub packages and by Oracle Forms and OAF pages that render planning workbenches. Because it is not referenced by external interfaces, custom code should treat it as an internal dependency rather than a public API. Its logging routines are commonly enabled during troubleshooting of planning hub performance and query generation, while the session validator ensures that planning data is only exposed to authenticated ICX users with appropriate responsibility assignments.