Search Results get_optional_info

Overview

MSC_SCE_PUB_SUPPLY_COMMIT_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. It belongs to the MSC (Advanced Supply Chain Planning / Supply Chain Engine) product family and is classified as an OTHER API rather than a formal public interface. Its principal business function is the publication of supply commit records generated during the planning cycle. In a planning-to-execution flow, supply commitments represent the confirmed or proposed supply that a planning engine intends to release toward downstream execution systems. This package packages those commitments into planning demand records, manages the aging of obsolete forecast rows, and provides a set of utility routines for logging and diagnostic output. It is a component of the supply chain engine (SCE) publication layer rather than a transactional entry point.

Key Procedures and Functions

The package exposes ten documented procedures and functions:

• PUBLISH_SUPPLY_COMMITS — the primary entry point; orchestrates the publication of supply commitments for the current planning run.
• INSERT_INTO_SUP_DEM — inserts supply commit information into the planning demand structure (MSC_DEMANDS).
• DELETE_OLD_FORECAST — removes stale or superseded forecast rows as part of commitment maintenance.
• GET_OPTIONAL_INFO — retrieves supplemental attribute values used to enrich the commit records.
• GET_MESSAGE — returns a formatted message string, typically for an error or status condition.
• LOG_MESSAGE — writes diagnostic or status messages to the logging infrastructure.
• PRINT_DEBUG_INFO — emits debug-level trace information, generally gated by a debug flag or profile option.
• PRINT_USER_INFO — outputs user-oriented informational messages describing processing results.

The remaining documented routines follow the same utility pattern. No parameter lists are asserted here, as the ETRM metadata does not enumerate them.

Tables Accessed

Table access is defined through APPS synonyms. The core planning tables are MSC_DEMANDS (the target of commit publications and forecast deletions), MSC_SYSTEM_ITEMS and MSC_ITEMS (item validation and attribute resolution), and MSC_FULL_PEGGING (pegging relationships used to trace supply to demand). Organizational context is drawn from MSC_COMPANIES, MSC_COMPANY_SITES, MSC_COMPANY_RELATIONSHIPS, and MSC_TRADING_PARTNER_SITES, which establish the legal entity and site combinations relevant to each commitment. Customer-related data comes from MSC_ITEM_CUSTOMERS. Infrastructure and localization tables include FND_LOOKUP_VALUES, FND_APPLICATION, FND_LANGUAGES, FND_NEW_MESSAGES, MSC_APPS_INSTANCES, and MSC_CL_REFRESH_S (collection refresh state), the latter supporting multi-instance coordination and refresh tracking.

Usage Notes

The package is invoked during the supply chain planning collection and plan publication phases, most commonly from concurrent programs associated with the MSC planning engine rather than from interactive forms. It is referenced by no other documented packages and does not expose a customer-facing form or public API contract, which is consistent with its OTHER classification. Customizations extending or overriding planning publication behavior should call the documented procedures only through supported extension points; direct dependency on internal routines such as LOG_MESSAGE or PRINT_DEBUG_INFO is discouraged, as their signatures and output formats are not guaranteed across releases. When diagnosing planning output discrepancies on EBS 12.1.1 or 12.2.2, developers typically trace this package through the dependent MSC plan run logs and the MSC_DEMANDS table. Because the dependency listing shows the package referencing itself, recursive or nested invocation occurs internally and should be considered when profiling execution.