Search Results msc_exception_details_s

Overview

MSC_WS_OTM_BPEL is a PL/SQL package body owned by APPS and classified under the OTHER API category. Its name indicates that it provides web-service-facing logic (WS) that bridges Oracle Advanced Supply Chain Planning (MSC) with Oracle Transportation Management (OTM) through BPEL orchestration. In the EBS 12.1.1 and 12.2.2 releases, the package serves as the server-side integration layer for exchanging order, demand, supply, and planning data between the planning schema and external transportation or order-promising workflows. It exposes a set of public procedures and functions that construct, validate, update, and notify the planning tables in response to inbound BPEL calls, and it encapsulates calendar, lead-time, and key-date calculations that the planning engine depends upon.

The package also contains private helper functions, including GetLeadTime, getLastRefreshNumber, and GetProfilePlanId. The search term "get_last" corresponds to getLastRefreshNumber, a private utility that determines the most recent refresh sequence number for a given order number, line number, and release number. This function supports idempotent processing of inbound messages by allowing the caller to compare the incoming refresh identifier against the last processed value.

Key Procedures and Functions

• GETPLANNER_1 — Retrieves planner information used to route or validate planning data associated with an incoming request.
• GETPUNCHOUTURI — Returns the punch-out URI used when redirecting to an external OTM or supplier system during web-service interaction.
• ADDLINEID / ADDLINESO — Insert or resolve line identifiers for sales order lines received through the integration, ensuring each line is uniquely identified before downstream updates.
• UPDATEPDS / UPDATEPDS_1 / UPDATEPDS_ORDER / UPDATEPDS_PO / UPDATEPDS_SO — Update planning data store records for generic, order, purchase order, and sales order contexts, applying inbound changes to demand and supply rows.
• GENERATEEXCEPTION / GENERATEEXCEPTION_SO — Create planning exception records, including sales-order-specific exceptions surfaced to planners.
• UPDATENEWCOLUMNANDFIRMDATE_PO / UPDATENEWCOLUMNANDFIRMDATE_SO — Set newly introduced columns and firm dates on purchase order and sales order planning records.
• SENDNOTIFICATION_1 / GETDATAFORNOTIFICATION — Assemble notification payloads and dispatch planner notifications for exceptions and key events.
• UPDATEKEYDATEINCP / UPDATECP_1 / UPDATE_CP / GETKEYDATE — Maintain key dates and collaborative planning attributes on planning records, including retrieving key dates for a given entity.
• APPSINIT — Initializes the session context (such as the global user identifier) required before other package routines execute.

Tables Accessed

The package reads and writes the core planning and integration tables through APPS synonyms. MSC_SYSTEM_ITEMS supplies item, organization, plan, and lead-time attributes; MSC_CALENDAR_DATES supports date and lead-time offset calculations; MSC_TRADING_PARTNERS provides the organization calendar code used in scheduling. MSC_DELIVERY_DETAILS, MSC_DEMANDS, MSC_SUPPLIES, and MSC_SUP_DEM_ENTRIES hold the demand and supply records updated by the UPDATEPDS family. MSC_SALES_ORDERS holds sales order header and line context, while MSC_PLANS and MSC_PLANNERS identify the plan and planner for exceptions and notifications. MSC_EXCEPTION_DETAILS, MSC_EXCEPTION_DETAILS_S, and MSC_ITEM_EXCEPTIONS store exception output, MSC_DESIGNATORS and FND_RESPONSIBILITY support responsibility and designer lookups, and MSC_CALENDAR_DATES is reused across scheduling logic.

Usage Notes

MSC_WS_OTM_BPEL is not intended for ad hoc invocation. It is typically called from BPEL or web-service mediation layers, or from concurrent programs and custom integration code that synchronize planning data with OTM. Because it is referenced by zero other packages in the ETRM metadata, it functions as an entry-point package rather than a shared utility library. Callers should invoke APPSINIT prior to other routines to establish session context. Dependencies on FND_RESPONSIBILITY and profile options mean the package must execute within an APPS session with the appropriate responsibility and planning profile settings.