Search Results g_reset_apps_context

Overview

The APPS.OE_STANDARD_WF package body provides the Workflow-enabled standard behavior layer for the Oracle Order Management (OM) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Unlike the Order Management public APIs, which perform discrete transaction operations, this package supplies the selector functions, message handling routines, and workflow context utilities that the seeded Order Management workflow processes call at runtime. It is classified as an OTHER API rather than a public or private API, reflecting its role as an internal support component of the OM workflow architecture rather than a callable integration interface.

The package holds a VALID status in the APPS schema and is documented in the ETRM repository with eighteen procedures and functions. It is referenced by forty-eight other database objects, confirming that it sits at the center of the Order Management workflow call graph. It does not reference any upstream EBS object outside the workflow and OM schemas.

Key Procedures and Functions

The documented entry points fall into four functional groups.

• Runtime mode controls: UPGRADE_MODE_ON, SAVE_MESSAGES_ON, SAVE_MESSAGES_OFF, RESET_APPS_CONTEXT_ON, and RESET_APPS_CONTEXT_OFF toggle package-level behavior flags. These allow the workflow engine or a test harness to enable upgrade compatibility mode, capture diagnostic messages, or force a reset of the Oracle Applications session context (via FND_GLOBAL / MO_GLOBAL) at defined points in processing.
• Message context management: SET_MSG_CONTEXT, CLEAR_MSG_CONTEXT, SAVE_MESSAGES, and SET_EXCEPTION_MESSAGE manipulate the internal message buffer. They capture and persist error or warning text generated during workflow execution so that it can be surfaced through the standard OM notification mechanism rather than lost to the log.
• Workflow selectors: OEOH_SELECTOR, OEOL_SELECTOR, OENH_SELECTOR, OEBH_SELECTOR, and OEAME_SELECTOR are used by the workflow engine to resolve the appropriate attribute values for the Order Header, Order Line, Negotiation Header, Blanket Header, and Amendment entities respectively. Selectors are the standard WF_ENGINE extension point used to dynamically return context values.
• Utility and diagnostic routines: GET_SUPPLY_SOURCE_TYPE and GET_LINE_CATEGORY derive classification values used by downstream workflow branches. STANDARD_BLOCK encapsulates the common blocking logic applied by OM workflow activities, and ADD_ERROR_ACTIVITY_MSG appends an error message to a workflow activity result.

Tables Accessed

The package reads from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, the base transaction tables, to satisfy selector requests and derive header/line context within a workflow. OE_BLANKET_HEADERS_ALL is queried to support the blanket order selector (OEBH_SELECTOR) and blanket-related supply source resolution. On the workflow side, WF_ITEMS and WF_PROCESS_ACTIVITIES are used to inspect the current workflow item and activity, enabling the selectors to return values appropriate to the currently executing activity. Additional dependencies documented against the package include FND_API, FND_MESSAGE, MO_GLOBAL, OE_MSG_PUB, OE_DEBUG_PUB, OE_GLOBALS, WF_CORE, and WF_ENGINE.

Usage Notes

OE_STANDARD_WF is not intended for direct invocation from external integrations. It is called internally by the seeded Order Management workflow processes — Order Flow, Order Line Flow, and the negotiation and blanket subflows — through the Workflow Engine's selector and activity mechanisms. Custom workflow activities that extend the standard OM flows typically reference these selectors indirectly by copying the seeded process definition. Developers troubleshooting workflow errors commonly enable message saving via SAVE_MESSAGES_ON in a diagnostic session to capture detailed failure text that would otherwise be suppressed. The APPS session context reset routines are used during concurrent workflow processing to prevent context leakage between workflow item executions. Because the package is referenced by forty-eight other objects and is not referenced by any external database object, changes to its specification or body can have broad impact across Order Management workflow behavior in both 12.1.1 and 12.2.2.