Search Results publish_sno_plan




Overview
Explore in AI Chat

Overview

APPS.MSC_WS_SNO is a web-service-oriented PL/SQL package body in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. Its principal business function is to initiate Supply Network Operations (SNO) planning model generation from external or web-service callers, most notably Oracle BPEL process flows, without requiring the caller to navigate the standard EBS Forms interface. The package authenticates the invoking user and responsibility, validates the target plan, and submits the SNO concurrent program on behalf of the caller.

The package body header ($Header: MSCWSNOB.pls 120.8.12010000.1 2008/05/02) confirms delivery as part of the 12.1.1 code line and its retention in 12.2.2. The package is classified as OTHER in ETRM 12.2.2 and is owned by APPS.

Key Procedures and Functions

  • GENERATE_SNO_MODEL — The core worker routine. It accepts an internal user identifier, responsibility identifier, plan identifier, and a solve-on-server flag, and returns an out processId plus a status string. It performs authentication, resolves the plan name, and submits the SNO concurrent program, returning a request ID on success or a diagnostic status on failure.
  • GENERATE_SNO_MODEL_PUBLIC — The public web-service entry point. Rather than accepting numeric IDs, it takes character-based UserName, RespName, RespApplName, SecurityGroupName, and Language parameters, resolving them internally to the numeric user and responsibility identifiers required by the private routine. This design supports loosely coupled external callers such as BPEL.
  • PUBLISH_SNO_PLAN — Publishes a generated SNO plan, operating on internal identifiers in the same manner as GENERATE_SNO_MODEL.
  • PUBLISH_SNO_PLAN_PUBLIC — The public counterpart to PUBLISH_SNO_PLAN, exposing plan publication to external callers using descriptive user, responsibility, application, security group, and language parameters.

The private/public pairing is a deliberate pattern: internal routines work with numeric surrogate keys, while public routines shield web-service consumers from the need to resolve EBS identity columns themselves.

Tables Accessed

The package references MSC_PLANS through the APPS synonym. In GENERATE_SNO_MODEL, the COMPILE_DESIGNATOR column is selected from MSC_PLANS filtered by PLAN_ID and constrained to PLAN_TYPE = 6, which identifies the SNO plan type. This lookup serves two purposes: it confirms that the supplied plan identifier corresponds to a valid SNO plan, and it supplies the plan name required as an argument to the concurrent program submission. A NO_DATA_FOUND condition produces the status value INVALID_PLANID and terminates processing.

Usage Notes

MSC_WS_SNO is intended for programmatic invocation rather than interactive use. It is typically called by BPEL orchestration flows or custom integration code that needs to trigger SNO plan generation or publication remotely. The package relies on FND_REQUEST.SUBMIT_REQUEST to launch the MSCSCPSNO concurrent program and returns the resulting request ID as processId; a return of zero signals submission failure and yields a status message derived from FND_MESSAGE.GET.

Regarding the search term validate_user_resp_func: the documented source shows that the call to VALIDATE_USER_RESP_FUNC is commented out at line 21, with the accompanying developer note that the BPEL flow has trouble validating the form function. The active authentication call is instead MSC_WS_COMMON.VALIDATE_USER_RESP, which validates only the user and responsibility pair. Callers therefore should not assume that form-function-level security is enforced by GENERATE_SNO_MODEL. ETRM records no other packages as referencing MSC_WS_SNO, indicating it sits at the boundary of the integration layer rather than being reused by internal EBS modules.