Search Results set_io_plan_options_public

Overview

MSC_WS_IO is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified in the ETRM repository under the "OTHER" API category. The package forms part of the Oracle Advanced Supply Chain Planning (ASCP) module within the MSC (Manufacturing Supply Chain) product family. Its core business function is to support the planning engine's input/output (I/O) batch processing for supply chain plans — that is, it provides the programmatic entry points through which a planning run is launched, and through which planner-facing plan options are captured and applied to that run. In EBS 12.1.1 and 12.2.2 the object carries a VALID status, confirming that the package compiles cleanly against the standard APPS database objects referenced through public synonyms. The package exposes both public and internal variants of its principal entry points, a convention typical of Oracle's MSC APIs where the _PUBLIC procedures are intended for external invocation and the non-suffixed procedures serve as the underlying implementation.

Key Procedures and Functions

The documented interface comprises four procedures, exposed in two paired sets:

• LAUNCH_IO_BATCH — the internal implementation routine that initiates the input/output batch job associated with a supply chain planning run. It is the core worker procedure driven by the corresponding public wrapper.
• LAUNCH_IO_BATCH_PUBLIC — the externally callable wrapper for LAUNCH_IO_BATCH. This is the entry point exposed for use by other application components, concurrent program logic, or custom code wishing to trigger an I/O batch.
• SET_IO_PLAN_OPTIONS — the internal routine that establishes, populates, or resets the planning options governing the I/O batch, such as plan, schedule, and planner configuration values.
• SET_IO_PLAN_OPTIONS_PUBLIC — the externally callable wrapper for SET_IO_PLAN_OPTIONS, providing the supported, public-facing means of configuring plan options prior to launching a batch.

In keeping with Oracle MSC API design, these procedures are expected to be invoked in a coordinated sequence: plan options are set first via the SET_IO_PLAN_OPTIONS entry point, and the batch is then launched via LAUNCH_IO_BATCH. No parameter signatures are documented in the ETRM metadata and should be confirmed against the deployed package specification.

Tables Accessed

The package reads and writes planning data through APPS synonyms over the following MSC/MSD tables, all of which are central to the planning data model:

• MSC_PLANS and MSC_PLAN_SCHEDULES — identify the target plan and its execution schedule for the I/O batch.
• MSC_CALENDAR_DATES — supplies calendar dates used in planning bucket definition.
• MSC_DESIGNATORS — provides designator/attribute information relevant to planning output.
• MSC_ITEM_SOURCING — holds item sourcing rules consumed or validated during batch setup.
• MSC_SERVICE_LEVEL_SETS — defines service-level targets applied to the plan.
• MSC_TRADING_PARTNERS — supplies partner information used in the planning model.
• MSD_DP_SCENARIO_OUTPUT_LEVELS — configures Demand Planning scenario output granularity.
• DUAL and PLITBLM — a standard Oracle single-row source, and the PL/SQL internal table (index-by table) memory structure used for transient processing.

Usage Notes

MSC_WS_IO is a backend package rather than a user-facing UI object. It is normally invoked indirectly — for example, from the Oracle Advanced Supply Chain Planning launch and plan-option flows, from concurrent programs that orchestrate planning runs, or from custom PL/SQL code that needs to start an I/O batch programmatically. Because the public procedures are the sanctioned entry points, customizations should call LAUNCH_IO_BATCH_PUBLIC and SET_IO_PLAN_OPTIONS_PUBLIC rather than the internal routines. The ETRM metadata records zero other packages referencing MSC_WS_IO, indicating that its consumers are primarily forms, concurrent programs, and external callers rather than sibling PL/SQL packages. Its direct dependencies on the ODMD schema tables MSCGLBIODMDSCHTBL and MSCLOCIODMDSCHTBL confirm that the package participates in the ASCP Open Demand/planning I/O interface layer, where plan output is written to and read from these staging structures. As with all MSC APIs, EBS patch-level changes may alter signatures, so the package specification in the target instance should be treated as authoritative.