Search Results invalid_planid

Overview

MSC_WS_SNO is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its name follows the Application Programming Interface naming conventions used by Oracle Advanced Supply Chain Planning (ASCP), where the MSC prefix denotes objects belonging to the MSC schema and WS indicates that the package is exposed as a web service entry point. The trailing SNO refers to "Supplies and Network Optimization," the optimization engine within ASCP that generates redistributed and optimized supply plans.

The package exists to expose the Supply Network Optimization functionality of the Launch SNO Plan and Publish SNO Plan concurrent programs as callable web services. It mirrors the parameters of those concurrent programs so that external systems—or internal middleware—can initiate an SNO plan solve or publish an existing SNO plan without navigating the EBS forms interface. The header comments explicitly note that procedures are invoked from web services to extract and publish the SNO plan model.

Key Procedures and Functions

The ETRM metadata documents four procedures, all of which are PL/SQL entry points. They are not functions and return no scalar value; instead, they deliver results through OUT parameters, principally a process identifier and a status code.

• GENERATE_SNO_MODEL — Initiates generation of an SNO plan model for a caller identified by user ID and responsibility ID. The sole documented output status values are INVALID_PLANID and INVALID_FND_USERID. The solveOnServer input may be conditionally set to Y or N.
• GENERATE_SNO_MODEL_PUBLIC — The public web-service wrapper. Rather than internal numeric IDs, it accepts user name, responsibility name, application name, security group name, and language, resolving those values internally before delegating to the core generation logic.
• PUBLISH_SNO_PLAN — Publishes an existing SNO plan, mirroring the parameters of the Publish SNO Plan concurrent program. Its documented outputs are again INVALID_PLANID and INVALID_FND_USERID.
• PUBLISH_SNO_PLAN_PUBLIC — The public wrapper for publishing, accepting the same human-readable identity parameters as the public generation procedure.

Across all four procedures, the repeated INVALID_PLANID status is the most significant documented failure signal.

Tables Accessed

The metadata records a single table reference: MSC_PLANS, accessed through an APPS synonym. This is the core ASCP plan definition table. It holds plan identifiers, plan names, and associated planning attributes. The package reads it primarily to validate the planId supplied by the caller. This validation is the origin of the INVALID_PLANID status returned by both the generation and publishing procedures.

Usage Notes

MSC_WS_SNO is invoked exclusively through web services, typically from external planning portals, integration middleware, or scheduled automation that needs to launch or publish SNO plans programmatically. The package is referenced by zero other packages within the documented scope, confirming its role as a leaf-level API rather than a shared utility.

The INVALID_PLANID status is the key diagnostic for users who search on that term. It indicates that the plan ID passed into the procedure could not be validated against MSC_PLANS—most commonly because the plan does not exist, was deleted, belongs to a different operating unit, or the caller supplied a stale identifier. Because the public procedures resolve plan ownership indirectly through user and responsibility context, an otherwise valid plan ID may still fail if the resolved identity lacks data access to that plan's security group.