Search Results load_changes

Overview

CLN_PO_CHANGE_ORDER is a PL/SQL package in the APPS schema of Oracle E-Business Suite (available in both 12.1.1 and 12.2.2) that supports Oracle Collaborative Planning / Supply Chain Collaboration functionality for outbound purchase orders. The package facilitates updating purchase orders in response to collaboration messages exchanged between a buying organization and its trading partners, and it maintains the associated collaboration history. It is declared AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking user rather than the definer.

The header history notes creation in August 2002 by Viswanthan Umapathy, with the current source revision dated November 2003. Within the ETRM (E-Business Suite Technical Reference Manual) classification scheme, the package is categorized as "OTHER" rather than a fully public, supported API, indicating it is intended primarily for internal use by Oracle Collaboration components.

Key Procedures and Functions

The package exposes eight documented procedures and functions:

• PROCESS_ORDER_HEADER — Validates PO header details and updates the collaboration based on the PO header information. It accepts ordering, trading partner, PO/SO number, release, type, and revision inputs, and returns error identifier and status values.
• PROCESS_ORDER_LINE — Processes order line details by updating the purchase order through the standard "Change PO" APIs and records collaboration history. Line price is modified as part of this processing, with supplier part number, SO line details, and reason supplied as inputs.
• PROCESS_ORDER_LINE_SHIPMENT — Handles shipment-level processing for PO lines, applying shipment detail changes to the collaboration and the underlying order.
• LOAD_CHANGES — The procedure matching the user's search term. It loads pending change records into the collaboration processing flow so that header, line, and shipment changes can be applied and propagated to the purchase order.
• GET_TRADING_PARTNER_DETAILS — Resolves trading partner metadata, such as identifiers and site information, required to route collaboration messages.
• RAISE_UPDATE_COLLABORATION — Raises or records a collaboration update event against the existing collaboration record.
• RAISE_ADD_MESSAGE — Creates and posts an additional collaboration message, typically used to communicate change notifications or errors.
• CALL_TAKE_ACTIONS — Invokes the take-action logic that follows message processing, such as updating collaboration status or triggering downstream workflow.

Tables Accessed

The package references the following tables through APPS synonyms:

• CLN_GENERIC_S — The collaboration generic sequence, used to generate unique identifiers for collaboration records created during change processing.
• ECX_TP_HEADERS — Holds trading partner header definitions; consulted to validate the trading partner and retrieve communication/connection details.
• WF_PARAMETER_LIST_T — The Workflow parameter list type used to pass structured name/value parameters into workflow or message-processing calls.
• DUAL — Used for single-row evaluations, such as sequence lookups or simple computations.
• PLITBLM — A PL/SQL index-by table of VARCHAR2 used for message buffering and error/text handling.

Usage Notes

CLN_PO_CHANGE_ORDER is not a public, standalone API. It is invoked as part of the Oracle Collaborative Planning flow, typically driven by concurrent programs or internal Collaboration modules that consume inbound collaboration responses (such as price or schedule changes) and translate them into "Change PO" API calls against the purchase order. The metadata records no other packages referencing it, indicating that its callers are Oracle-internal components rather than published APIs relied upon by customer extensions.

Customizations should avoid calling these procedures directly, as the interface is unsupported and may change between releases. When troubleshooting change-loading behavior, the LOAD_CHANGES procedure is the relevant entry point, and the G_ERROR_ID and G_ERROR_MESSAGE package globals, along with the OUT error parameters, provide diagnostic information for failures during header, line, or shipment processing.