Search Results xnp_adapter




Overview
Explore in AI Chat

Overview

XNP_ADAPTER is a PL/SQL package body owned by the APPS schema that functions as an integration and control adapter within Oracle E-Business Suite's event and messaging infrastructure. It belongs to the XNP component family, which in Oracle EBS provides the runtime plumbing for inter-process messaging, event subscription, and message queue handling used by applications such as Oracle Advanced Supply Chain Planning, Oracle Process Manufacturing, and other modules that rely on asynchronous message exchange.

The package is classified as an OTHER API, indicating it is not a public, formally supported application programming interface but rather an internal utility invoked by framework components. The object is VALID, meaning it compiles cleanly against the referenced dependencies. Its dependency list includes XDP_ADAPTER, XDP_TYPES, XNP_CONTROL_U, XNP_ERRORS, XNP_MESSAGE, XNP_PIPE, and XNP_XML_UTILS, along with Workflow engine components WF_CORE and WF_ENGINE, and the FND_MESSAGE utility. This dependency profile confirms that XNP_ADAPTER coordinates message dispatch, control signaling, XML parsing, and Workflow integration from a central point.

Key Procedures and Functions

Ten documented procedures and functions are exposed by the package, covering the lifecycle control and communication operations of the adapter:

  • OPEN — Initializes the adapter and establishes the resources needed to begin processing messages or events.
  • CLOSE — Terminates the adapter session and releases the resources acquired by OPEN.
  • SUSPEND — Places the adapter into a paused state, halting further processing without fully terminating the session.
  • RESUME — Reverses SUSPEND, allowing the adapter to continue processing from its paused state.
  • SHUTDOWN — Performs an orderly stop of the adapter, distinct from CLOSE in that it shuts down the broader processing context.
  • CLOSE_FILE — Closes a file handle associated with adapter file-based operations, likely used when messages are exchanged via flat files.
  • FTP — Manages file transfer operations, supporting the movement of message or data files between systems.
  • USER_CONTROL — Processes user-initiated control actions, allowing external callers to influence adapter behavior.
  • NOTIFY_FMC — Sends notification events to the FMC (Forecast Management or similar) component, integrating the adapter with downstream consumers.

Tables Accessed

XNP_ADAPTER reads and writes through APPS synonyms for three documented tables:

  • XNP_MSGS — The core message repository. The adapter reads pending messages and updates their status as they are processed.
  • XNP_MSG_TYPES_B — The base table defining message types. The adapter consults this table to determine how each message should be handled.
  • PLITBLM — A PL/SQL internal table used for bulk message processing, supporting array-based operations.

Usage Notes

XNP_ADAPTER is an internal framework package and is not intended for direct invocation by end users or custom extensions. It is typically called by Oracle's internal messaging and concurrent processing infrastructure rather than by forms running in the EBS user interface. It is referenced by one other package in the database, confirming its role as a dependent component rather than a top-level entry point. Because it depends on Workflow engine components and FND_MESSAGE, integration points with Workflow notifications and error reporting should be expected. Any customization touching XNP_ADAPTER carries upgrade risk, as no public API commitment exists for this object across EBS 12.1.1 and 12.2.2. Developers should prefer documented APIs in the XNP or XDP families when extending functionality.