Search Results msc_log

Overview

MSC_LOG is a utility package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Advanced Supply Chain Planning (ASCP) product family, as indicated by the MSC prefix, and is classified as an OTHER API in the ETRM repository. The package provides a centralized diagnostic logging facility used by planning engine and workflow-related components to capture messages, messages with contextual metadata, and string values during execution. Its purpose is to standardize how ASCP modules emit trace and debug information, rather than embedding ad hoc logging logic in each consumer. In the documented 12.2.2 metadata, MSC_LOG is marked VALID and exposes five procedures or functions.

Key Procedures and Functions

The package exposes five documented callable units. Their names and intent are as follows:

• STRING — Writes a single string value to the logging target. Used for simple textual trace output where no additional context is required.
• STRING_WITH_CONTEXT — Writes a string value together with contextual information, allowing callers to associate the message with a specific program, entity, or execution scope.
• MESSAGE — Emits a formatted log message, typically for structured diagnostic or informational output.
• MESSAGE_WITH_CONTEXT — Emits a formatted log message accompanied by contextual data; the contextual variant of MESSAGE.
• TEST — A self-test or validation entry point used to verify that the logging facility is operational within a given environment or session.

Parameter lists are not disclosed in the documented metadata and are therefore intentionally omitted; callers should reference the package specification in the database for exact signatures.

Tables Accessed

The documented metadata does not list any tables referenced through APPS synonyms. The recorded dependencies consist of the SYS schema and the STANDARD package, which indicates that MSC_LOG relies on PL/SQL built-in functionality (such as DBMS_OUTPUT or standard string handling inherited from STANDARD) rather than persistent database tables for its core logging operations. In practice, logging output of this type is usually directed to the concurrent program log file, a debug table, or an output buffer; where no table dependency is documented, the package should be treated as a lightweight, buffer- or file-oriented utility.

Usage Notes

MSC_LOG is consumed by other ASCP packages rather than invoked directly by end users. The documented reverse dependency identifies MSC_REL_WF as a referencing package, confirming its role as a supporting utility within the supply chain planning module stack. It is not exposed through a Forms-based user interface or a standalone concurrent program, and it should not be registered as a concurrent executable. Custom code extending ASCP functionality may legitimately call these procedures to align diagnostic output with Oracle's own trace conventions, but such calls should be wrapped so that logging failures never interrupt business processing. Because the package is classified as OTHER rather than a public API, Oracle does not guarantee backward compatibility of its signatures across patches or releases; any custom invocation of MSC_LOG should be validated after applying ASCP patch sets, particularly when moving between 12.1.1 and 12.2.2.