Search Results set_ascp_plan_buckets

Overview

MSC_WS_SNO_PUBLISH is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Advanced Supply Chain Planning (ASCP) module and supports the Web Services / Supply Chain Node (SNO) publishing infrastructure within the MSC (Material Planning) product family. Its primary business purpose is to expose planned supply chain data — system items, planning buckets, demands, supplies, safety stocks, alerts, departmental resources, resource summaries, inventory details, and sourcing recommendations — to an external publish target, typically a web service or staging layer such as the Supply Chain Node.

The package gathers planning results for a specific plan (identified by PlanIdVar) and stages them through interface tables so they can be consumed by downstream reporting, collaboration, or portal components. It uses the R12 NOCOPY parameter convention for OUT parameters, which is characteristic of performance-oriented EBS internal APIs.

Key Procedures and Functions

• LOG_MESSAGE — Writes a diagnostic message for tracing package execution.
• SET_UP_SYSTEM_ITEMS — Stages system item master data associated with the plan.
• SET_ASCP_PLAN_BUCKETS — Publishes planning bucket data, including the export buckets used as the time-bucketed output structure.
• SET_ASCP_DEMANDS — Publishes demand records, including dependent demand, for the plan.
• SET_ASCP_SUPPLIES — Publishes planned supply records for the plan.
• SET_ASCP_SAFETY_STOCKS — Publishes safety stock levels.
• SET_ASCP_ALERTS — Publishes exception/alert details generated during the plan run.
• SET_APCC_FACILITY_COST — Publishes facility cost data used by the Advanced Planning Command Center.
• SET_ASCP_DEPARTMENT_RESOURCES — Publishes departmental resource information.
• SET_ASCP_RES_SUMMARY — Publishes a resource summary; returns the scenario name through an OUT parameter.
• SET_ASCP_BIS_INV_DETAIL — Publishes BIS inventory detail.
• SET_ASCP_SRC_RECOMMEND_DETAIL — Publishes sourcing recommendation detail; receives an assignment set output identifier.
• GET_PLAN_NAME_BY_PLAN_ID — Helper function that resolves a plan name from a plan identifier. This is the object referenced by the search term "get_plan_name_by_plan_id". A copy of the equivalent helper also exists in MSC_WS_COMMON.
• VALIDATE_USER_RESP — Validates the combination of user and responsibility.
• PUBLISH_SNO_RESULTS — Top-level orchestrator that publishes Supply Chain Node results for a plan and returns a process identifier.
• VALIDATE_FOR_PUBLISH_SNO_RES — Validates preconditions before the publish runs.
• PUBLISH_SNO_RESULTS_WITH_VAL — Publish variant that performs validation.
• PUBLISH_SNO_RESULTS_SOP — Publish variant oriented to Sales and Operations Planning output.

Tables Accessed

The package reads and writes planning data primarily through APPS synonyms. Core planning tables include MSC_DEMANDS and MSC_DEMANDS_S, MSC_DEPARTMENT_RESOURCES, MSC_EXCEPTION_DETAILS and MSC_EXCEPTION_DETAILS_S for alerts, and the BIS reporting tables MSC_BIS_INV_DETAIL, MSC_BIS_ORG_DETAIL, and MSC_BIS_RES_SUMMARY. Interface/staging tables used for output include MSC_INT_ASCP_DEMANDS, MSC_INT_ASCP_DEPENDENT_DEMAND, MSC_INT_ASCP_EXCEPTION_DETAILS, MSC_INT_ASCP_EXPORT_BUCKETS, and MSC_INT_APCC_ORG_DETAIL. Security validation accesses FND_USER and FND_RESPONSIBILITY.

Usage Notes

MSC_WS_SNO_PUBLISH is an internal, implementation-support package rather than a public EBS API. It is typically invoked from the Supply Chain Node publish flow in Advanced Supply Chain Planning, triggered through concurrent programs or planner-facing web pages, and indirectly through PL/SQL calls made on behalf of those screens. Because it references interface tables and the _S staging tables, custom integrations that need to publish ASCP plan results to an external collaboration or portal target can call the PUBLISH_SNO_RESULTS family of procedures, passing a valid plan identifier. The ETRM metadata shows no other packages referencing this one, indicating it sits at the terminal end of the planning publish chain. Parameter lists for individual procedures should be confirmed against the deployed source, as signatures vary by release.