Search Results msc_ws_notification_bpel




Overview
Explore in AI Chat

Overview

MSC_WS_NOTIFICATION_BPEL is an APPS-owned PL/SQL package within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. Its principal business function is to support workflow-driven notification processing for BPEL (Business Process Execution Language) web service integrations, specifically those tied to supply chain planning and order-to-movement (OTM) workflows. The package name indicates a bridging role between Oracle Workflow and BPEL-based outbound notification services, enabling planning exceptions, approval routing, and escalation messages to be assembled and dispatched to external or internal recipients.

In EBS 12.1.1 and 12.2.2, ASCP relies heavily on Oracle Workflow for exception messaging and approver routing. This package exposes wrapper procedures that resolve role assignments, plan context, and escalation rules before handing off notification payloads. It is classified under the ETRM API classification of OTHER, indicating it is a supporting utility package rather than a public documented open interface. The package is marked VALID in the APPS schema, and it sits alongside related packages such as MSC_WS_OTM_BPEL, which references it directly.

Key Procedures and Functions

The package exposes six documented procedures and functions:

  • SET_WF_APPROVER_ROLE — Establishes the Oracle Workflow approver role to be used for a notification, ensuring that approvals are routed to the correct recipient role before dispatch.
  • LOOKUP — Provides a general lookup utility used internally by the notification logic to resolve reference values required during message assembly.
  • LOOKUP_PLAN — Resolves the planning context for a notification, identifying the relevant plan associated with the message being processed.
  • LOOKUP_ESCALATION — Determines escalation settings so that time-sensitive notifications can be escalated to higher-level recipients when required.
  • SENDFYINOTIFICATION — Assembles and sends a notification payload to a specified recipient, functioning as the primary outbound notification routine.
  • SENDFYINOTIFICATIONPUBLIC — A public variant of the notification procedure, intended for invocation from external or non-restricted callers.

Tables Accessed

The package references the following tables through APPS synonyms:

  • FND_USER — Used to resolve user identity and recipient information for notifications.
  • MSC_PLANS — Supplies plan metadata so that notifications carry correct planning context.
  • MSC_FORM_QUERY_S — Provides saved query definitions used when building notification content or filtering.
  • WF_LOCAL_ROLES — Resolves workflow role definitions for approver and escalation routing.
  • DUAL — Used for single-row utility operations and lookups.
  • PLITBLM — A PL/SQL internal table type used for bulk collection handling within the procedural logic.

The package also declares a dependency on the MSGTOKENVALUEPAIRLIST type, reflecting its use of token/value pairs in notification message construction.

Usage Notes

MSC_WS_NOTIFICATION_BPEL is not a standalone interface intended for direct end-user invocation. It is typically called internally by ASCP BPEL integration flows and is referenced by MSC_WS_OTM_BPEL, indicating use in OTM-related web service notifications. In practice it is invoked when a planning exception, approval request, or escalation event must be transmitted to a recipient outside the standard workflow path, such as an external BPEL process or partner system.

Customizations should avoid modifying this package directly; instead, extensions should leverage the public SENDFYINOTIFICATIONPUBLIC wrapper. Because the package depends on Workflow role resolution and ASCP plan data, any caller must ensure that role and plan context are correctly established. It is recommended to test thoroughly in both 12.1.1 and 12.2.2 environments, as workflow and BPEL integration behavior can vary between releases.