Search Results msc_cl_refresh_s




Overview
Explore in AI Chat

Overview

APPS.MSC_SCE_PUBLISH_PKG is a valid PL/SQL package body owned by the APPS schema that supports Supply Chain Execution (SCE) publishing within the Oracle Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. Its principal business function is to publish planned supply and demand data — plan orders, forecasts, and related scheduling information — out of the planning tables and into the supply/demand interface so that downstream execution systems and planning consumers can act on the plan output. The package bridges the planning engine's internal model (MSC_SUPPLIES, MSC_DEMANDS, MSC_PLAN_BUCKETS) with the published supply/demand entries held in MSC_SUP_DEM_ENTRIES and its interface table MSC_SUP_DEM_ENTRIES_S. It reads planning results, company and site definitions, items, suppliers, and trading partner relationships, and writes the resulting records that publication consumers rely upon.

Key Procedures and Functions

The ETRM metadata documents seven procedures/functions in the package body:

  • PUBLISH_PLAN_ORDERS — The primary entry point; publishes planned orders, coordinating the read of plan data and the generation of supply/demand publish records.
  • GET_OPTIONAL_INFO — Retrieves optional or supplementary information required during publication, supporting conditional enrichment of the published records.
  • INSERT_INTO_SUP_DEM — Inserts supply/demand entry records into the publishing interface table (MSC_SUP_DEM_ENTRIES / MSC_SUP_DEM_ENTRIES_S).
  • DELETE_OLD_FORECAST — Removes previously published forecast records so that refreshed forecast data replaces stale entries.
  • INSERT_INTO_SUP_DEM_RF_DOS — Inserts supply/demand records associated with the release-forecast / due-order-schedule flow used for supplier scheduling publication.
  • LOG_MESSAGE — Writes diagnostic or status messages, typically to the concurrent program log via FND_FILE, for traceability during publication runs.
  • GET_MESSAGE — Retrieves formatted or translated messages, leveraging FND_NEW_MESSAGES and FND_LANGUAGES for multilingual output.

The documentation does not expose parameter signatures; the descriptions above reflect the documented naming and observed dependencies only.

Tables Accessed

The package reads and writes a range of ASCP and foundation tables (referenced through APPS synonyms). Planning data is sourced from MSC_SUPPLIES, MSC_DEMANDS, MSC_PLAN_BUCKETS, MSC_PLANS, MSC_PLAN_ORGANIZATIONS, and MSC_SALES_ORDERS. Reference data is read from MSC_SYSTEM_ITEMS, MSC_ITEMS, MSC_ITEM_SUPPLIERS, MSC_COMPANIES, MSC_COMPANY_SITES, MSC_COMPANY_RELATIONSHIPS, MSC_TRADING_PARTNERS, MSC_TRADING_PARTNER_SITES, and MSC_TRADING_PARTNER_MAPS. Publication output is written to MSC_SUP_DEM_ENTRIES and MSC_SUP_DEM_ENTRIES_S. MSC_CL_REFRESH_S is a significant dependency, referenced in the user's search context; it relates to the refresh/collection status of planning data and is used to determine which published data is current. Foundation tables include FND_APPLICATION, FND_LANGUAGES, FND_NEW_MESSAGES, FND_PREFERENCE, FND_PROFILE, FND_GLOBAL, FND_DATE, and FND_LOOKUP_VALUES, supporting message resolution, profile options, multilingual handling, and logging.

Usage Notes

MSC_SCE_PUBLISH_PKG is typically invoked through ASCP concurrent programs that publish plan output to execution systems and supplier scheduling. It is called within the planning publication cycle rather than from standard forms. Because the package body is not referenced by any other database object and is dependent on MSC_SCE_LOADS_PKG, MSC_X_CP_FLOW, MSC_X_UTIL, and MSC_X_WFNOTIFY_PKG for load and notification handling, custom integrations generally call the published procedures indirectly through the concurrent manager. When diagnosing publication issues, notably around MSC_CL_REFRESH_S status, DBAs should review the LOG_MESSAGE output in the concurrent request log.