Search Results resume_adapter

Overview

XDP_APPLICATION is the administrative control package for Oracle E-Business Suite's e-Commerce Gateway / EDI adapter infrastructure, delivered under the APPS schema with AUTHID CURRENT_USER semantics. It governs the lifecycle of "adapters" — the runtime processes that move messages between the Advanced Queuing transport layer and the fulfillment trading partner framework (the XDP_* objects). The package provides the programmatic interface used to start, suspend, resume, stop, and shut down adapters, to inspect their registration and runtime state, and to clean up associated queue pipes. In the context of EBS 12.1.1 and 12.2.2, it is categorized as an OTHER API rather than a public transactional interface, meaning it is generally reserved for internal administration, diagnostics, and carefully controlled customization. The common search term resume_adapter maps directly to one of the package's principal lifecycle operations: the RESUME_ADAPTER routine used to reactivate an adapter whose processing has been suspended, either explicitly or as a result of an error condition.

Key Procedures and Functions

The package exposes roughly forty documented procedures and functions, organized around adapter lifecycle and state management.

• STARTUP_ADAPTER / STARTUP_NEW_ADAPTER — initialize and register adapter activity, including creation of a new adapter definition.
• RESUME_ADAPTER — reactivates an adapter that has been suspended. Two overloaded forms exist: one driven by a RequestID, and one accepting ChannelName, FeName, FeID, User, Freq, Reqdate, and RequestID. This is the operation most commonly associated with the search term "resume_adapter."
• SUSPEND_ADAPTER — places an adapter into a suspended state, using the same overload pattern (RequestID, or ChannelName/FeName context).
• STOP_ADAPTER — terminates adapter processing, with a parameter identifying whom to stop.
• CONNECT_ADAPTER / DISCONNECT_ADAPTER — establish or tear down the adapter's queue connection.
• SHUTDOWN_ADAPTER — performs a full adapter shutdown.
• CLEANUP_ADAPTER_PIPE — removes residual Advanced Queuing pipes associated with a channel.
• ADMINISTER_ADAPTER — provides a general administrative entry point for adapter management.
• GET_ADAPTER_INFO / GET_ADAPTER_STATUS — return registration and runtime status details for an adapter.
• LOCK_ADAPTER_REG_STATUS / UPDATE_ADAPTER_REG_STATUS — serialize and persist changes to adapter registration state.
• UPDATE_ADAPTER_ADMIN_STATUS — records administrative status transitions.
• LOCK_ADAPTER_CTRL — locks the adapter control record prior to status updates.
• CHECK_FREQUENCY — validates the scheduling frequency associated with an adapter request.
• FTP_ADAPTER_FILE — supports file transfer operations for the adapter.
• SUBMITCONTROLLERREQ / VERIFYCONTROLLER — submit and verify the controller concurrent request that drives adapter processing.

Tables Accessed

The package operates on both configuration and transactional tables via APPS synonyms. Adapter registration and runtime state are held in XDP_ADAPTER_REG, XDP_FA_RUNTIME_LIST, and XDP_FES (fulfillment execution systems), while fulfillment work is tracked in XDP_FULFILL_WORKLIST and XDP_ORDER_HEADERS. Concurrent scheduling data is read from FND_CONCURRENT_PROCESSES and FND_CONCURRENT_QUEUES. Message transport relies on Advanced Queuing tables including AQ$XDP_FA_QTAB, AQ$XDP_ORDER_PROCESSOR_QTAB, AQ$XDP_WF_CHANNEL_QTAB, AQ$XDP_WORKITEM_QTAB, and the XNP inbound/outbound queue tables (AQ$XNP_IN_EVT_QTAB, AQ$XNP_IN_MSG_QTAB, AQ$XNP_IN_TMR_QTAB, AQ$XNP_OUT_MSG_QTAB).

Usage Notes

XDP_APPLICATION is typically invoked from the Concurrent Managers and adapter administration forms, from the concurrent controller process, or from controlled custom PL/SQL that manages message-based integration. Because it is classified as OTHER rather than a public API, direct calls should be limited to administrative and diagnostic scenarios, with status changes always funneled through the locking and status-update procedures to avoid concurrent corruption. The package is referenced by one other package, reinforcing its role as an internal control layer rather than a standalone interface.