Search Results xdpcore_error




Overview
Explore in AI Chat

Overview

XDPCORE_ERROR is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM registry as an OTHER API. Its header identifies the package as AUTHID CURRENT_USER, meaning that all SQL statements it executes run with the privileges of the invoking user rather than the package owner. The source header revision ($Header: XDPCORRS.pls 120.2 2006/04/10) indicates the package has been part of the Oracle E-Business Suite distribution for many release cycles, including the 12.1.1 and 12.2.2 codelines.

The package belongs to the XDP family of modules, which support Oracle's order-capture and fulfillment integration flows — the same functional area served by the XDP_ORDER_HEADERS and XDP_ORDER_LINE_ITEMS tables referenced through APPS synonyms. Within that architecture, XDPCORE_ERROR functions as the central error-handling and notification utility. It provides the workflow-enabled business event procedures that detect processing failures, assemble human-readable error messages, record session-level errors, and route notifications to parties outside the originating system. It also declares a package-level exception, e_NullValueException, along with global message variables x_ErrMsg and x_DebugMsg used to carry diagnostic text between calls.

Key Procedures and Functions

The documented interface exposes six procedures; all but LOG_SESSION_ERROR follow the standard Oracle Workflow business event signature (itemtype, itemkey, actid, funcmode, resultout).

  • FE_ERROR_PROCESS_OPTIONS — Workflow activity that evaluates the configured error-processing options for a failed order or transaction, returning a result to the workflow engine.
  • NOTIFY_OUTSIDE_SYSTEM_OF_ERROR — Workflow activity that generates and dispatches error notifications to recipients or systems external to the originating application.
  • PREPARE_ERROR_MESSAGE — Workflow activity that assembles the formatted error message text from the available diagnostic context.
  • FE_ERR_NTF — Workflow notification activity dedicated to front-end error notification, driving the appropriate notification template for a failed event.
  • SET_ERROR_CONTEXT — Establishes the error context (item type, item key, activity) so that subsequent error-handling activities operate on the correct workflow instance.
  • LOG_SESSION_ERROR — Records a session-level error of a supplied error type, providing the persistence point for diagnostic information.

Tables Accessed

The package operates against three documented tables referenced through APPS synonyms. XDP_ERROR_COUNT is used to track and tally error occurrences, supporting the error-processing option logic. XDP_ORDER_HEADERS and XDP_ORDER_LINE_ITEMS supply the order header and line context from which failed transactions are identified and for which error messages, notifications, and context values are prepared. Access to these tables is performed under the invoker's privileges, so the calling user must hold the necessary grants.

Usage Notes

XDPCORE_ERROR is designed to be invoked from Oracle Workflow as part of a business event or error-handling process rather than called directly by end users. The five workflow procedures are entered by the Workflow engine at activity execution time, with funcmode determining whether the activity is being run, canceled, or queried. Typical entry points include order-capture and fulfillment workflows in the XDP module, and the package is referenced by two other packages in the ETRM registry, confirming its role as a shared error-handling dependency. Customizations that extend or replace the standard error notification process should preserve the documented signatures and the AUTHID CURRENT_USER semantics, and developers invoking LOG_SESSION_ERROR directly from custom code should ensure the session has the privileges required to reach the XDP tables. Because the package is marked proprietary and shipped with the applications code, it should not be modified; extensions belong in custom wrapper packages that call the documented procedures.