Results for “default_process”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XNP_ADAPTER_ERROR_U is an Oracle EBS applications-level PL/SQL package owned by APPS and classified within ETRM as an "OTHER" API. It belongs to the XNP messaging infrastructure, the internal publish/subscribe framework used by Oracle applications for inter-subsystem communication, workflow notification, and integration messaging. The package exists specifically to construct, publish, and process messages of type adapter error. When an adapter in the messaging chain fails — for example a transport, transformation, or connectivity adapter — this package supplies the standard message envelope that records which front-end or channel produced the failure, a status code, and a human-readable description. The signature AUTHID CURRENT_USER indicates the package executes with the privileges of the invoking user rather than the definer, which is consistent with a utility that is invoked from multiple runtime contexts across the E-Business Suite stack. The header revision ($Header: XNPADERS.pls 120.2 2006/02/13) shows the source has been stable across the 12.1.1 and 12.2.2 release lines, and the package remains documented in the 12.2.2 ETRM inventory.

Key Procedures and Functions

The package exposes five documented entry points, structured around the standard XNP message lifecycle:

• CREATE_MSG — Builds an adapter-error message in memory. It accepts the front-end name, channel name, status code, and description, and returns a message header record (of type XNP_MESSAGE.MSG_HEADER_REC_TYPE), the message text, and error-code/error-message outputs. Optional parameters allow the caller to attach sender, recipient list, version, reference identifiers, order and instance identifiers, and delivery delay/interval hints.
• PUBLISH — Takes the same identifying attributes and emits the adapter-error message onto the messaging bus, returning a generated message identifier plus error diagnostics. It additionally accepts a consumer list that controls message subscription targeting. This is the procedure most commonly associated with an adapter failure being surfaced to subscribers.
• PROCESS — Consumes an inbound adapter-error message. It receives a message header and message text and returns error-code and error-message outputs, with an optional process reference used to correlate the processing run.
• DEFAULT_PROCESS — The default handler invoked when a subscription does not specify a custom processing callback for the adapter-error message type.
• VALIDATE — Validates the adapter-error message payload, ensuring required fields such as front-end name, channel, and status code are present and well formed before the message is published or processed.

Tables Accessed

The ETRM metadata records a single referenced object for this package: DBMS_AQ, accessed through an APPS synonym. DBMS_AQ is the Oracle Advanced Queuing PL/SQL interface, and the package uses it to enqueue the adapter-error message onto the XNP queue when PUBLISH is called, and to dequeue it during PROCESS and DEFAULT_PROCESS. Message payload structure is governed by the XNP_MESSAGE record type referenced in the package specification, with the queue itself managed within the XNP schema. No application data tables are directly read or written by this package; its persistence is entirely mediated through the AQ infrastructure.

Usage Notes

XNP_ADAPTER_ERROR_U is generally not invoked directly by end users. It is called by the XNP messaging runtime and by adapter components when an outbound or inbound adapter reports a failure, so a search such as "event ID 4873 error virtual adaptor" typically reflects a runtime message generated via this package's PUBLISH procedure rather than an interactive form error. The EVENT ID correlates to a message identifier issued by the queue, while the "virtual adaptor" reference identifies the front-end or channel name passed into CREATE_MSG or PUBLISH. In custom integrations, developers may call CREATE_MSG followed by PUBLISH to raise a standardized adapter-error notification, or rely on DEFAULT_PROCESS when wiring a subscription. Because the package executes with AUTHID CURRENT_USER, custom callers must hold the necessary queue and XNP object privileges in their own schema context. Diagnosing adapter errors normally involves querying the XNP queue tables and message history for the returned message identifier and then examining the status code and description recorded by this package.