Search Results raise_add_message

Overview

CLN_PO_CHG_ORDER_STATUS is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Oracle Collaborative Logistics Network (CLN) module. Its principal business function is to process and record purchase order (PO) status changes and propagate those changes to the collaborating trading partner community. Specifically, the package facilitates updates to the Purchase Order, as stated in its own header comments (line 11 of the source), and maintains the collaboration history that records the exchange of information between a buying organization and its suppliers.

The package belongs to the API classification "OTHER" in the ETRM 12.2.2 repository. Its source header identifies the file as CLNPOSSB.pls, version 120.5, last modified 20 November 2006, and notes it was created by Viswanthan Umapathy in August 2002. It is a non-shipped ("noship") object and is referenced by zero other packages, indicating that it operates as a leaf-level utility consumed by the CLN processing flow rather than as a shared library.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions in this package body:

• PROCESS_ORDER_HEADER — Processes order header details by creating and updating the collaboration history. It accepts PO and sales order (SO) details and returns status and message information through OUT parameters. This is the entry point for header-level change processing.
• PROCESS_ORDER_LINE — Processes individual purchase order lines and records the corresponding collaboration history entries.
• PROCESS_ORDER_LINE_SHIPMENT — Processes shipment-level details associated with an order line, maintaining the collaboration record at the lowest document granularity.
• LOAD_CHANGES — Loads the set of purchase order changes to be processed, populating the internal working structures consumed by the processing routines.
• GET_TRADING_PARTNER_DETAILS — Retrieves the trading partner information required to direct collaboration messages to the correct recipient.
• RAISE_UPDATE_COLLABORATION — Raises an update event to the collaboration framework so that changes are communicated to the trading partner.
• RAISE_ADD_MESSAGE — Raises a message-add event within the collaboration framework. This is the routine most directly associated with the search term "raise_add_message" and is commonly inspected when diagnosing CLN message-generation behavior.
• CALL_TAKE_ACTIONS — Invokes the take-action processing that applies the configured business actions for the transaction.

An additional private function, IS_ALREADY_PROCESSED_LINE, appears in the source excerpt. It uses a PL/SQL associative array (t_line_num_tab, indexed by BINARY_INTEGER) to detect duplicate line numbers within a single processing run, returning TRUE when a line has already been seen and FALSE otherwise.

Tables Accessed

The package references the following objects through APPS synonyms:

• CLN_GENERIC_S — The CLN generic sequence, used to generate identifiers for collaboration records. Note that the documented reference is to a sequence name rather than a table.
• ECX_TP_HEADERS — The e-Commerce Exchange trading partner header table, used by GET_TRADING_PARTNER_DETAILS to resolve partner configuration.
• WF_PARAMETER_LIST_T — The Oracle Workflow parameter list type, used to pass parameters into the raised collaboration events.
• DUAL — Used for singleton queries and sequence value retrieval.
• PLITBLM — The PL/SQL integer table type used for line-number collections.

Usage Notes

CLN_PO_CHG_ORDER_STATUS is typically invoked from the CLN collaboration processing flow rather than directly from an Oracle Forms screen. It is called when a purchase order is created, revised, or otherwise changes status and the change must be communicated to a trading partner through the collaboration framework. The package also honours a debugging profile, CLN_DEBUG_LEVEL, read via FND_PROFILE, which controls the verbosity of messages written through the CLN_DEBUG_PUB package; values of 1 and 2 gate the most detailed trace output in IS_ALREADY_PROCESSED_LINE.

Because the package is classified as "OTHER" and is not referenced by any other package, customizations should treat it as an internal implementation detail of the CLN module. Extensions that need to raise collaboration messages should prefer the supported ECX and Workflow APIs. When troubleshooting missing or duplicate partner notifications, RAISE_ADD_MESSAGE and IS_ALREADY_PROCESSED_LINE are the routines most often examined, particularly in environments where the same PO line may be submitted more than once in a single run.