Search Results set_attributes_of_workflow




Overview
Explore in AI Chat

Overview

CLN_PO_CHANGE_RESPONSE_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Procurement change-order collaboration process. Its business purpose is to interpret supplier responses to purchase order change requests and to prepare the corresponding workflow attributes and status values used by the Order Collaboration workflow. The package header comment identifies it as the body of the response package for purchase order changes, first created in June 2003 by Rahul Krishan and last carried under the $Header tag CLNPOCHB.pls 115.6.

The package operates primarily within Oracle Workflow, where item attributes must be populated before downstream activities evaluate acknowledgements, reasons, and statuses. A package-level variable, l_debug_level, is initialized from the profile option CLN_DEBUG_LEVEL (defaulting to 5), and diagnostic messages are written through CLN_DEBUG_PUB. The API classification is recorded as OTHER, reflecting its role as a supporting utility rather than a public concurrent interface.

Key Procedures and Functions

  • SET_ATTRIBUTES_OF_WORKFLOW — The central procedure, and the object referenced in the search term. It sets workflow item attributes based on the change request group identifier passed to it, and its result output is initialized to indicate successful defaulting of attributes. It declares local variables for the sales order number, header identifier, revision number, release identifier, header and consolidated line statuses, header response reason, document number, change request group identifier, header acknowledgement code, party and party site identifiers, XML Gateway document identifier, and event key.
  • GET_CHANGE_REQUEST_GROUP_ID — Retrieves the change request group identifier associated with the workflow context, providing the key input consumed by the attribute-setting logic.
  • SET_REQUEST_GRP_ID_AND_COLL_ID — Establishes the request group identifier and collection identifier on the workflow item, ensuring subsequent activities and queries operate against the correct grouping.
  • CALC_ACKCODE_CONDITIONALLY — Conditionally derives the acknowledgement code, applying business rules that determine the supplier acknowledgement outcome rather than assigning a value unconditionally.
  • GET_ADDITIONAL_DATA — Fetches supplementary attribute data required to complete the workflow item, complementing the values populated by SET_ATTRIBUTES_OF_WORKFLOW.

These five documented units form a cohesive sequence: resolve the identifiers, populate the item, compute the acknowledgement, and supply remaining data.

Tables Accessed

The package reads and writes the following objects through APPS synonyms:

  • PO_HEADERS_ALL — Supplies header-level details such as document number, revision, and header status.
  • PO_RELEASES_ALL — Provides release-level information where the change affects a release.
  • PO_CHANGE_REQUESTS — Holds the change request records that drive the response and acknowledgement logic.
  • CLN_COLL_HIST_HDR and CLN_COLL_HIST_DTL — Store collaboration history at header and detail level, used to record or derive response and collection status.
  • CLN_GENERIC_S — A generic sequence used to generate identifiers such as the event key.
  • DUAL — Used for single-row evaluations and default assignments.

Usage Notes

The package is invoked from Oracle Workflow during the purchase order change response cycle. SET_ATTRIBUTES_OF_WORKFLOW is called with the standard workflow procedure signature (item type, item key, activity identifier, function mode, and result out), making it suitable for a Workflow function activity. It is also referenced by one other package, indicating reuse within the collaboration module. Typical invocations occur when a supplier response is received and processed through XML Gateway, and customers may call these procedures from custom workflow definitions or extensions. Debugging is controlled through the CLN_DEBUG_LEVEL profile, and the package body is dated 2004, so it remains unchanged across EBS 12.1.1 and 12.2.2.