Results for “dp_only”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_WS_ASCP is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under ETRM as an OTHER API. Its principal role is to expose Oracle Advanced Supply Chain Planning (ASCP) plan-launch functionality to web service clients. The package header carries the version stamp $Header: MSCWASCS.pls 120.3 2008/03/20 15:54:43 bnaghi noship $, confirming it as a shipping, non-customization object. Rather than reimplementing planning logic, MSC_WS_ASCP acts as a thin web-service wrapper around the Launch Plan concurrent program. It accepts the same parameters as that concurrent program and submits a batch of child concurrent requests on the caller's behalf. The package is declared AUTHID CURRENT_USER, so all SQL inside executes with the privileges of the invoking session rather than the definer, meaning callers must hold appropriate grants on the underlying MSC tables and on concurrent manager submission.

Key Procedures and Functions

Six procedures are documented for this package:

• LAUNCH_ASCP_BATCH — the core batch submission routine. It mirrors the Launch Plan concurrent program parameters and returns a concurrent program request id plus a status value. Child programs it can spawn include Memory-Based Snapshot, Snapshot Monitor, Snapshot Delete Worker, Memory-Based Snapshot Worker, Loader Worker With Direct Load Option, Memory-Based Planner, Post Plan Program for UI, and Refresh One KPI Summary Table. Typical inputs include launchSnapshot (FULL, NO, DP_ONLY), launchPlanner, releaseReschedules, snapStaticEntities (Y/N), anchorDate, archiveCurrVersPlan, and enable24x7Atp (YES_PURGE, NO, YES_NOPURGE). Documented status outputs include INVALID_PLANID, INVALID_ANCHORDATE, INVALID_LAUNCH_SNAPSHOT, INVALID_LAUNCH_PLANNER, INVALID_ENABLE24X7ATP, INVALID_RELEASE_RESCHEDULES, INVALID_FND_USERID, and INVALID_FND_RESP.
• LAUNCH_ASCP_BATCH_PUBLIC — the public wrapper of the batch routine, providing the supported external entry point.
• RELEASE_ASCP — releases a plan, corresponding to the Release Plan workflow operation in ASCP.
• RELEASE_ASCP_PUBLIC — the public wrapper of the release routine.
• SET_ASCP_PLAN_OPTIONS — sets or updates options associated with an existing ASCP plan.
• SET_ASCP_PLAN_OPTIONS_PUBLIC — the public wrapper for setting plan options.

The consistent _PUBLIC pairing indicates a private/public API layering convention: internal logic resides in the base procedure, while the public variant is the contract exposed to external consumers.

Tables Accessed

All table access occurs through APPS synonyms. MSC_PLANS is the central table, holding plan definitions referenced by planId. MSC_PLAN_SCHEDULES stores plan scheduling attributes used during batch submission and release. MSC_CALENDAR_DATES supplies calendar information tied to anchor dates and plan scheduling. MSC_ITEM_SOURCING provides sourcing rules consumed when planning runs are launched. MSC_DESIGNATORS and MSC_TRADING_PARTNERS supply planning designators and partner data used by the plan configuration. DUAL is used for scalar evaluations, and PLITBLM is the PL/SQL integer-table type used internally for array handling. Because the package is AUTHID CURRENT_USER, the invoking session must resolve these synonyms and hold the necessary object privileges.

Usage Notes

MSC_WS_ASCP is not typically invoked from Oracle Forms. It is designed for programmatic invocation from web services, integration middleware, or custom PL/SQL that needs to trigger an ASCP plan run or release without navigating the ASCP user interface. Callers supply a valid FND user id and responsibility id, which are validated and can produce INVALID_FND_USERID or INVALID_FND_RESP statuses. The procedure returns immediately after submitting concurrent requests, so callers should poll FND_CONCURRENT_REQUESTS using the returned request id rather than assume synchronous completion. The package is referenced by zero other packages, so it sits at the top of the dependency chain and is safe to call directly. Custom code integrating with this package should handle every enumerated status code and should avoid direct writes to the MSC_WS_ASCP-owned logic, preferring the _PUBLIC procedures for forward compatibility.