Search Results cln_np_notification_workflow_s

Overview

CLN_NP_PROCESSOR_PKG is the notification processing engine within the Oracle E-Business Suite Collaboration Messaging (CLN) module, part of the ECX/Exchange family of applications. In releases 12.1.1 and 12.2.2, the package body implements the runtime logic that interprets inbound and outbound collaboration notifications, evaluates their associated actions, and drives Business Event System (WF_EVENT) activity between trading partners. Whereas the header declares the public interface, the body contains the procedural implementation that orchestrates notification parsing, action resolution, collaboration history capture, and error logging.

Functionally, the package sits between the Collaboration Messaging infrastructure (ECX_STANDARDS, ECX_TRANSACTIONS, ECX_TP_HEADERS) and the notification configuration layer (CLN_NOTIFICATION_ACTION_HDR and its detail tables). It converts a recognized notification into a set of executable actions, records the outcome in collaboration history tables, and dispatches workflow events or administrator alerts when processing fails.

Key Procedures and Functions

• PROCESS_NOTIFICATION — The primary entry point. It accepts a notification, resolves the corresponding notification code and action configuration, and coordinates the downstream processing flow.
• TAKE_ACTIONS — Executes the actions defined for a notification, applying the action detail rows retrieved from the notification action configuration tables.
• GET_DELIMITER — Returns the delimiter used when parsing notification content, derived from profile or configuration settings.
• GET_TRADING_PARTNER_DETAILS — Retrieves trading partner header and detail information (ECX_TP_HEADERS, ECX_TP_DETAILS) required to route or interpret the notification.
• NOTIFY_ADMINISTRATOR — Sends an administrative alert, typically via workflow or FND_MESSAGE, when processing encounters an exception.
• PROCESS_NOTIF_ACTIONS_EVT — Event-handler procedure invoked for the notification-actions business event; it drives action processing from the event subscription.
• PROCESS_NOTIF_BATCH_EVT — Event-handler procedure supporting batch-oriented notification processing triggered through the Business Event System.

Tables Accessed

The package reads and writes configuration and history tables through APPS synonyms. Notification definitions are resolved from CLN_NOTIFICATION_CODES and CLN_NOTIFICATION_CODES_TL, with multilingual display text supplied by CLN_CH_DISPLAY_LABELS_HDR and CLN_CH_DISPLAY_LABELS_DTL_TL/VL. Action configuration is sourced from CLN_NOTIFICATION_ACTION_HDR and CLN_NOTIFICATION_ACTION_DTL. Processing outcomes and audit trails are written to CLN_COLL_HIST_HDR and CLN_COLL_HIST_DTL. Trading partner and standard context is drawn from ECX_TP_HEADERS, ECX_TP_DETAILS, ECX_STANDARDS, ECX_TRANSACTIONS and ECX_EXT_PROCESSES. Diagnostics use ECX_DOCLOGS and ECX_ERRORLOG, while workflow integration relies on WF_EVENT_T. The staging table CLN_NP_NOTIFICATION_WORKFLOW_S, referenced by the user search term, holds notification-workflow records consumed during processing.

Usage Notes

The package is not referenced by other database objects directly for DDL purposes, but it is invoked by 14 dependent packages and by seeded business event subscriptions. PROCESS_NOTIF_ACTIONS_EVT and PROCESS_NOTIF_BATCH_EVT are registered as event-handler procedures in the Workflow Business Event System; they are therefore triggered automatically when the corresponding notification events are raised. PROCESS_NOTIFICATION is typically called from Collaboration Messaging concurrent programs and from custom extensions that submit or replay notifications. NOTIFY_ADMINISTRATOR is invoked internally on failure paths. Developers extending the collaboration flow should treat PROCESS_NOTIFICATION as the supported entry point and avoid direct modification of the configuration tables outside the standard notification setup. Workflow directory and role lookups (WF_DIRECTORY, WF_ROLES, WF_USERS) support notification recipient resolution, and FND_GLOBAL supplies the application and session context.