Search Results g_queue_disabled

Overview

XNP_ERRORS is a centralized error-handling specification package within the Oracle E-Business Suite APPS schema. Its principal business function is to provide a single, authoritative repository of error codes and their associated descriptions for the XNP family of modules, which support the Oracle Advanced Supply Chain Planning and related planning/execution integration components. Rather than scattering literal error numbers and message strings throughout the codebase, XNP_ERRORS defines them once as package-level constants. This ensures consistent interpretation of failures across all dependent programs and simplifies maintenance when error semantics require adjustment. The package header carries the version marker $Header: XNPERRPS.pls 120.0 2005/05/30 11:45:59 appldev noship $, indicating it is a server-side PL/SQL construct compiled with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the defining user.

Key Procedures and Functions

The ETRM 12.2.2 metadata records zero documented procedures or functions for this package. Consistent with the source listing, XNP_ERRORS functions primarily as a constants-only specification. It declares CONSTANT NUMBER values that enumerate error conditions and CONSTANT VARCHAR2 values that supply human-readable descriptions. Representative codes include:

• Mandatory-data and structural faults: G_MISSING_MANDATORY_DATA (-20001), G_NO_MSG_STRUCTURE (-20003), and G_NO_DESTINATION (-20002), which signal missing required inputs or undefined message routing.
• Workflow and messaging faults: G_INVALID_WORKFLOW (-20007), G_INVALID_FE_ATTRIBUTE (-20008), G_DEQUEUE_TIMEOUT (-20004), and G_ADAPTER_NOT_READY (-20530).
• Pipe and queue conditions: G_QUEUE_DISABLED (-20510), G_SHUTDOWN_RECEIVED (-20520), G_NO_MSG_IN_PIPE (-20531), and G_PIPE_WRITE_FAILURE (-20532).
• Timer, delay, and interval errors: G_INVALID_DELAY_SOURCE (-20534) through G_TIMER_NOT_FOUND (-20540), covering scheduling reference problems.
• Configuration and SQL errors: G_NO_DATA_SOURCE (-20543), G_NULL_SQL_SOURCE (-20544), G_SEMI_COLON_ERROR (-20545), G_UNDEFINED_FUNCTION (-20547), and G_DUPLICATE_OBJECT (-20550).
• Descriptive text: G_NO_DESTINATION_DESC and related VARCHAR2 constants carry the message text surfaced to users.

No procedural bodies are exposed; the value of the package lies entirely in the stable naming and numbering it imposes.

Tables Accessed

The ETRM metadata lists no tables referenced through APPS synonyms, and none are declared in the documented source. As a constants specification, XNP_ERRORS performs no DML or queries. Callers construct error records in their own structures and pass the package constants as the error code, relying on XNP_ERRORS only for definitions.

Usage Notes

XNP_ERRORS is referenced by 73 other packages, reflecting its role as a shared dependency across the XNP integration and planning stack. It is typically invoked from PL/SQL packages, concurrent program logic, and interface programs that must raise or interpret an error using the canonical code. The package is not associated with a form-based interface or a standalone concurrent program; it is a compile-time dependency resolved at parse time. Administrators and developers should treat it as read-only reference data: changes to constant values ripple across all 73 dependents, so recompilation and regression testing are required after modification. Because it is compiled AUTHID CURRENT_USER, execution respects invoker privileges.