Search Results get_customer_transit_time




Overview
Explore in AI Chat

Overview

MSC_X_UTIL is a utility PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Within the Advanced Supply Chain Planning (ASCP) and Collaborative Planning product family, the "MSC" prefix denotes objects belonging to the MSC schema, and the "X" convention typically indicates extension or customization-support objects that bridge standard Supply Chain Planning functionality with trading-partner, VMI (Vendor Managed Inventory), and external-system integration flows. Consistent with its UTIL classification in the ETRM repository, MSC_X_UTIL is not a business-process entry point in its own right; it is a shared container of reusable helper routines invoked by other packages, views, and integration programs across the MSC schema.

The package's dependency footprint confirms this role. It is referenced by 25 other objects, including publish and forecast programs (MSC_CL_PUBLISH, MSC_PUBLISH_SAFETY_STOCK_PKG, MSD_SCE_PUBLISH_FORECAST_PKG), SCE (Supply Chain Execution) load and publish packages (MSC_SCE_LOADS_PKG, MSC_SCE_PUBLISH_PKG, MSC_SCE_PUB_SUPPLY_COMMIT_PKG), VMI and collaborative-planning packages (MSC_X_CVMI_PLANNING, MSC_X_CVMI_REPLENISH, MSC_X_VMI_UTIL_NEW), and the netting and planning engines (MSC_X_NETTING1_PKG through MSC_X_NETTING4_PKG, MSC_X_PLANNING, MSC_X_REPLENISH). Several views also depend on it, including MSC_CUST_BUCKET_V, MSC_SUP_DEM_ENTRIES_UI_V, MSC_VMI_ITEM_V, and MSC_EXCHANGE_BUCKETING. The package itself references only SYS.STANDARD, indicating that its logic is expressed primarily through SQL against APPS synonyms rather than through nested package APIs.

Key Procedures and Functions

The ETRM documentation records 14 procedures and functions. Their names indicate three broad functional groupings:

All routines are defined as a combined specification and body, with the body marked VALID in the deployed 12.2.2 environment.

Tables Accessed

MSC_X_UTIL reads and writes the MSC planning tables through APPS synonyms. Trading-partner resolution routines use HZ_PARTIES, MSC_TRADING_PARTNERS, MSC_TRADING_PARTNER_MAPS, and MSC_TRADING_PARTNER_SITES; company and organization context comes from MSC_COMPANIES, MSC_COMPANY_RELATIONSHIPS, and MSC_COMPANY_SITES. Item and category lookups draw on MSC_SYSTEM_ITEMS and MSC_ITEM_CATEGORIES, while unit-of-measure conversion operates against MSC_UNITS_OF_MEASURE. Calendar and transit-time logic uses MSC_CALENDAR_ASSIGNMENTS and MSC_CALENDAR_DATES. Identifier cross-references are resolved through MSC_TP_ID_LID and MSC_TP_SITE_ID_LID. Scheduling data — specifically for ATP-related checks — is accessed via MRP_ATP_SCHEDULE_TEMP_S.

Usage Notes

Because MSC_X_UTIL carries a UTIL classification, it is not typically invoked directly from Oracle Forms or exposed as a standalone concurrent program. It is called internally by the 25 dependent packages and views during publish, netting, planning, and VMI replenishment runs. Customizations that extend ASCP or VMI functionality can invoke these routines to obtain consistent party names, lookup meanings, UOM conversions, calendar codes, and shipping controls rather than reimplementing that logic. Developers should treat the package as an internal API: its procedures are subject to change between patch levels, and any custom call should be validated against the target 12.1.1 or 12.2.2 instance. The documented dependency set should be reviewed before applying patches, since changes to MSC_X_UTIL can cascade to publish, SCE, and collaborative-planning programs.