Search Results process_notif_batch_evt

Overview

CLN_NP_PROCESSOR_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite that forms the core processing engine of the Oracle Collaborative Logistics Network (CLN) notification framework. In both 12.1.1 and 12.2.2, the package is deployed with a VALID status and is classified as an OTHER API, distinguishing it from public Oracle APIs intended for direct customer invocation. Its primary business function is to consume notification events raised within the CLN and ECX (e-Commerce Exchange) integration layer, resolve the trading partners and transaction context associated with each event, evaluate the configured notification actions, and dispatch the resulting notifications or system actions to the appropriate destinations. Because it bridges workflow event infrastructure with the collaboration module's notification and action tables, it acts as the central orchestrator through which outbound business-document notifications — such as purchase order acknowledgements, invoice notifications, and rejection notices — are generated and routed. The package's dependency on WF_EVENT_T confirms that it operates against the Oracle Workflow Business Event System event queue.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions within the package:

• PROCESS_NOTIFICATION — the principal entry point that processes an inbound notification event, resolves its context, and drives the notification logic.
• TAKE_ACTIONS — evaluates and executes the actions configured against a notification, applying the rules defined in the notification action setup.
• GET_DELIMITER — returns the delimiter character used when parsing or assembling notification content, typically drawing on the standards configuration.
• GET_TRADING_PARTNER_DETAILS — resolves trading partner information from the ECX trading partner configuration so that the notification can be addressed and formatted correctly.
• NOTIFY_ADMINISTRATOR — generates an administrative notification, typically when processing fails or requires manual intervention.
• PROCESS_NOTIF_ACTIONS_EVT — an event-specific handler that processes notification action events delivered through the Business Event System.
• PROCESS_NOTIF_BATCH_EVT — a batch event handler that processes notification events in bulk mode.

Parameter lists are not documented in the available metadata and are therefore not reproduced here.

Tables Accessed

The package operates against a broad set of CLN and ECX tables via APPS synonyms. Notification setup and control data are read from CLN_NOTIFICATION_CODES and its translation table CLN_NOTIFICATION_CODES_TL, together with CLN_NOTIFICATION_ACTION_HDR and CLN_NOTIFICATION_ACTION_DTL, which define the actions to be taken. Display-label text is obtained from CLN_CH_DISPLAY_LABELS_HDR and CLN_CH_DISPLAY_LABELS_DTL_TL. Collaboration history is recorded in CLN_COLL_HIST_HDR and CLN_COLL_HIST_DTL, which capture the outbound and inbound document exchange records. Workflow state is held in CLN_NP_NOTIFICATION_WORKFLOW_S. Trading partner and standards configuration is drawn from ECX_TP_HEADERS, ECX_TP_DETAILS, ECX_STANDARDS, and ECX_EXT_PROCESSES, while ECX_DOCLOGS provides the document log used for auditing and troubleshooting. WF_EVENT_T supplies the workflow business event subscription context.

Usage Notes

CLN_NP_PROCESSOR_PKG is not intended for direct invocation by end users. It is invoked indirectly through the Oracle Workflow Business Event System, where event subscriptions raised by the CLN collaboration flows call PROCESS_NOTIF_ACTIONS_EVT and PROCESS_NOTIF_BATCH_EVT. It is also called programmatically by fourteen dependent packages, including CLN_ACK_PO_PKG, CLN_NTFYINVC_PKG, CLN_INV_REJECT_NOTIF_PVT, CLN_SYNC_ITEM_PKG, CLN_PO_CHANGE_ORDER, CLN_XMLG_EVENT_HANDLER_PKG, CLN_NP_UTILS_PKG, and the M4R/M4U WSM integration packages, indicating its role as a shared service across the collaboration and supply-chain messaging stack. Because it is an internal API, customizations should avoid modifying the package directly and should instead rely on supported configuration of notification codes and actions.