Search Results msc_sup_dem_entries_s




Overview
Explore in AI Chat

Overview

The APPS.MSC_PUBLISH_SAFETY_STOCK_PKG package body is a PL/SQL program unit within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module, part of the MSC (Manufacturing Supply Chain) schema family. Its principal business function is to publish safety stock quantities computed during a planning run into the supply/demand interface tables consumed by downstream planning and execution processes. Safety stock represents buffer inventory held to absorb demand variability and supply uncertainty; this package extracts safety stock definitions and calculated quantities from the planning engine's internal tables and writes them into the open interface structures MSC_SUP_DEM_ENTRIES and MSC_SUP_DEM_ENTRIES_S, from which they are subsequently processed as supply or demand records. The package is classified as a standard valid database object owned by the APPS schema and is documented across both Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package body exposes eight documented procedures and functions. Descriptions follow the documented names; no parameter signatures are asserted.

  • PUBLISH_SAFETY_STOCKS — The primary entry point. It drives the overall publication process, orchestrating the retrieval of safety stock data for a plan and invoking the supporting routines that transform and insert records into the supply/demand interface tables.
  • GET_OPTIONAL_INFO — Retrieves ancillary or configuration-level information required during publication, such as plan or organization attributes used to qualify the safety stock records.
  • GET_TOTAL_QTY — Calculates the total safety stock quantity for a given item, organization, or bucket combination, consolidating values across time buckets or sources.
  • INSERT_INTO_SUP_DEM — Performs the write operation that inserts the assembled safety stock records into MSC_SUP_DEM_ENTRIES and its companion MSC_SUP_DEM_ENTRIES_S table.
  • DELETE_OLD_SAFETY_STOCK — Removes previously published safety stock entries so re-execution of the publication process does not produce duplicate or stale records.
  • LOG_MESSAGE — Writes diagnostic, informational, and error messages to the concurrent program log via FND_FILE, supporting traceability of the publication run.
  • GET_MESSAGE — Retrieves a formatted message text, typically resolving message names through FND_NEW_MESSAGES for language-specific output.
  • GET_ORDER_TYPE — Determines the applicable order or entry type classification used when constructing supply/demand rows, drawing on lookup definitions such as MFG_LOOKUPS.

Tables Accessed

The package reads and writes a broad set of planning and foundation tables. Documented references include MSC_SAFETY_STOCKS, which holds the source safety stock definitions and quantities; MSC_SUP_DEM_ENTRIES and MSC_SUP_DEM_ENTRIES_S, which receive the published output rows; and MSC_DEMANDS and MSC_SUPPLIES, which represent the broader supply and demand streams the entries integrate with. Item and sourcing context is drawn from MSC_ITEMS, MSC_SYSTEM_ITEMS, MSC_ITEM_SUPPLIERS, and MSC_ITEMS. Organizational and partner scope is supplied by MSC_PLANS, MSC_PLAN_ORGANIZATIONS, MSC_PLAN_ORGANIZATIONS_V, MSC_PLAN_BUCKETS, MSC_COMPANIES, MSC_COMPANY_SITES, MSC_COMPANY_RELATIONSHIPS, MSC_TRADING_PARTNERS, MSC_TRADING_PARTNER_MAPS, and MSC_TRADING_PARTNER_SITES. Calendar and refresh context comes from MSC_CALENDAR_DATES and MSC_CL_REFRESH_S. Foundation references include FND_APPLICATION, FND_LANGUAGES, FND_NEW_MESSAGES, FND_PREFERENCE, MFG_LOOKUPS, and MSC_APPS_INSTANCES.

Usage Notes

Because the package is owned by APPS and declared VALID, it is invoked in the standard EBS manner through concurrent program requests, typically as part of the safety stock publication or planning data extraction flow within ASCP. It is not referenced by any other database object, indicating it is called directly by a concurrent program executable or an application-level driver rather than from a dependent PL/SQL API. The user search term msc_sup_dem_entries_s reflects the interface table this package populates; that table is the staging point for downstream consumers of safety stock supply and demand records. Customizations should avoid direct manipulation of the interface tables and instead invoke the packaged procedure to preserve interface integrity and logging behavior.