Search Results generateexception_so




Overview
Explore in AI Chat

Overview

MSC_WS_OTM_BPEL is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an "OTHER" API. Its name indicates that it functions as a web services bridge layer between Oracle Advanced Supply Chain Planning (ASCP), the MSC schema objects it depends upon, and Oracle Transportation Management (OTM) through BPEL (Business Process Execution Language) orchestration. The package encapsulates the server-side logic that OTM and other external integration processes call when they need to read planner assignments, retrieve punchout URIs, insert order and line identifiers, refresh planning data stores (PDS), raise planning exceptions, and record key date or capacity changes back into the ASCP planning tables.

In EBS 12.1.1 and 12.2.2, this package participates in the collaborative planning and order promising flows that synchronize planning results with transportation and order management systems. Because its procedures are exposed as web service entry points, most of its routines use OUT parameters for status and tranzId to return processing outcomes to the calling BPEL process rather than raising exceptions.

Key Procedures and Functions

  • GetPlanner_1 — Returns the planner associated with a given source instance, inventory item, and organization, together with a status indicator.
  • GetPunchoutURI — Function that builds and returns the punchout URI for a source instance and OTM release GID, enabling navigation from OTM back into EBS planning screens.
  • AddLineId / AddLineSO — Insert line-level identifiers and arrival dates for a release or release line, creating corresponding transaction records and returning a transaction ID and status.
  • UpdatePDS — Refreshes the planning data store, returning a status code.
  • UpdatePDS_1 — Variant of the PDS refresh keyed by transaction ID and BPEL order type.
  • UpdatePDS_Order — Refreshes PDS for a specific transaction and order type.
  • UpdatePDS_PO — Updates PDS for purchase order related transactions using a plan ID and transaction ID.
  • UpdatePDS_SO — The sales order counterpart; updates PDS for a plan ID and transaction ID, which is the routine most relevant to searches for updatepds_so.
  • GenerateException / GenerateException_SO — Create planning exceptions for purchase order shipments and sales order transactions respectively.
  • UpdateNewColumnAndFirmDate_PO / _SO — Populate new planning columns and firm dates for PO and SO flows, returning shipment classification and status.
  • SendNotification_1 / GetDataForNotification — Assemble notification payloads and dispatch them.
  • UpdateKeyDateInCP / UpdateCP_1 / Update_CP / GetKeyDate — Maintain capacity and key date information in the collaborative planning structures.
  • AppsInit — Standard APPS initialization routine that sets the application context before the other APIs execute.

Tables Accessed

The package reads and writes a focused set of MSC planning tables through APPS synonyms. Planner resolution uses MSC_PLANNERS, MSC_SYSTEM_ITEMS, and FND_RESPONSIBILITY. Order and line processing touches MSC_SALES_ORDERS, MSC_DEMANDS, MSC_SUPPLIES, MSC_SUP_DEM_ENTRIES, MSC_DELIVERY_DETAILS, and MSC_TRADING_PARTNERS. Exception handling writes MSC_EXCEPTION_DETAILS and MSC_EXCEPTION_DETAILS_S (the DFF table) plus MSC_ITEM_EXCEPTIONS. Calendar and planning context come from MSC_CALENDAR_DATES, MSC_PLANS, and MSC_DESIGNATORS. Collectively these tables hold the planning, supply, demand, and exception records that the OTM/BPEL integration must keep synchronized.

Usage Notes

MSC_WS_OTM_BPEL is not invoked directly from Oracle Forms. It is designed as a web service backend, called by BPEL processes and external OTM integration flows that reach the database through the EBS SOA Gateway. Because the routines are exposed as APIs, callers must invoke AppsInit first to establish the APPS environment, and must inspect the OUT status parameters rather than relying on exceptions for error control. The package is referenced by zero other packages in the ETRM inventory, so custom code that calls it should treat it as a top-level integration entry point. Custom integrations extending the OTM-ASCP flow can use UpdatePDS_SO and UpdatePDS_PO to force a targeted planning data store refresh after order or shipment changes, while GenerateException_SO supports downstream exception visibility.