Search Results set_io_plan_options




Overview
Explore in AI Chat

Overview

MSC_WS_IO is the Internal Operations (IO) batch package within Oracle Advanced Supply Chain Planning (ASCP), part of the MSC (Materials and Supply Chain) schema family in Oracle E-Business Suite. The package body drives the IO plan run process, which is used to validate and publish sourcing, demand schedule, and service-level data for a given plan. The header comment captured in the source shows $Header: MSCWIOPB.pls 120.5 2008/03/20 15:57:58 bnaghi noship $, confirming this is a shipped (non-"noship"-excluded in the file tag context) PL/SQL unit that has been maintained across successive ASCP releases for 12.1.1 and 12.2.2.

The package name places it alongside other MSC_WS_* "worksheet/IO" packages that orchestrate batch validation and plan-data preparation. Its role is to accept user-supplied plan parameters, validate the caller's user/responsibility context, verify the target plan and designator, and then launch the IO batch run that reads sourcing rules, demand schedules, service levels, and calendar dates to produce the outputs consumed by downstream planning.

Key Procedures and Functions

The ETRM metadata documents four procedures:

  • LAUNCH_IO_BATCH — The core entry point that validates the user/responsibility, resolves and validates the plan identifier (including compile designator, organization, SR instance, inventory ATP flag, and production flag), and launches the IO batch. It returns an outbound process ID and status. Internal error-tracking numbers (e.g., 3010 for user/resp validation, 3020 for plan validation) are assigned at each validation stage, indicating structured error reporting.
  • LAUNCH_IO_BATCH_PUBLIC — The public wrapper exposing LAUNCH_IO_BATCH functionality to external callers such as concurrent programs or forms, providing a supported, decoupled entry point.
  • SET_IO_PLAN_OPTIONS — Sets IO plan options prior to a run, including archive-plan and related flags used during batch initialization.
  • SET_IO_PLAN_OPTIONS_PUBLIC — The public wrapper for SET_IO_PLAN_OPTIONS, allowing callers outside the package to configure IO plan options.

The source excerpt also references package-level globals such as g_IGlbDmdSchTbl and g_ILocDmdSchTbl, which store global and local demand-schedule data during the run, and g_ErrorCode.

Tables Accessed

  • MSC_PLANS — plan definition, compile designator, organization, and SR instance used for plan validation.
  • MSC_DESIGNATORS — designator attributes (inventory_atp_flag, production, disable_date) used to confirm the plan is active and valid.
  • MSC_PLAN_SCHEDULES — plan schedule and anchor-date information.
  • MSC_ITEM_SOURCING — sourcing rules read during IO processing.
  • MSC_CALENDAR_DATES — calendar data for date and bucket calculations.
  • MSC_SERVICE_LEVEL_SETS — service-level definitions applied to the IO run.
  • MSC_TRADING_PARTNERS — partner data used in sourcing/demand validation.
  • MSD_DP_SCENARIO_OUTPUT_LEVELS — demand-planning scenario output-level configuration.
  • DUAL and PLITBLM — utility objects for single-row selection and PL/SQL table support.

Usage Notes

MSC_WS_IO is typically invoked indirectly through ASCP concurrent programs and planning forms rather than called directly by end users. Custom code should prefer the *_PUBLIC wrappers (LAUNCH_IO_BATCH_PUBLIC, SET_IO_PLAN_OPTIONS_PUBLIC) to insulate against internal signature changes. The package is not referenced by other documented packages (Referenced by: 0), so its callers are external — concurrent manager, oracle forms, and OAF pages for plan launch. When diagnosing errors, note the error-tracking numbers (3010, 3020, etc.) emitted by LAUNCH_IO_BATCH to pinpoint the failing validation stage.