Search Results eng_change_actions_util




Overview
Explore in AI Chat

Overview

APPS.ENG_CHANGE_ACTIONS_UTIL is a utility PL/SQL package within the Oracle E-Business Suite Engineering (ENG) module. It provides the procedural infrastructure that supports Engineering Change Order (ECO) and Engineering Change Request life-cycle management. Its primary responsibilities include recording change-action history against engineering change objects, coordinating workflow notifications and responses, propagating ECO actions, and providing a lightweight debugging framework used during development and troubleshooting.

The package encapsulates a comprehensive vocabulary of change-action type constants. Workflow-related actions such as WF_STARTED, WF_COMPLETED, WF_APPROVED, WF_REJECTED, WF_ABORTED, WF_TIME_OUT, WF_TRANSFERRED, and WF_DELEGATED, together with implementation actions such as IMPLEMENTATION_FAILED and IMPLEMENT_IN_PROGRESS, and user-response actions such as APPROVED, REJECTED, COMPLETED, COMMENT, and REPLIED, are declared as global constants. These constants standardise how change-action rows are classified in the underlying tables, allowing other engineering packages and workflow processes to write and interpret history records consistently.

Key Procedures and Functions

  • OPEN_DEBUG_SESSION — Initialises a debug session so that subsequent diagnostic messages are captured for the calling session.
  • CLOSE_DEBUG_SESSION — Terminates an active debug session and releases associated resources.
  • WRITE_DEBUG — Writes a diagnostic message to the active debug output, used for tracing execution and inspecting intermediate values.
  • GET_DEBUG_MODE — Returns the current debug mode setting. This is the object the user searched for; it allows calling code to determine whether debug logging is enabled before expending effort to compose or emit messages.
  • CREATE_CHANGE_ACTION — Creates a new change-action history record against an engineering change, using one of the package's action-type constants.
  • UPDATE_WORKFLOW_INFO — Updates workflow-related information associated with a change action, such as notification or status details.
  • RESPOND_NOTIFICATION — Records a user response to a workflow notification (for example, approval, rejection, delegation, or transfer) and reflects it in the change-action history.
  • GET_WORKFLOW_NOTIF_ID — Retrieves the workflow notification identifier associated with a change action.
  • DELETE_LINE_ACTIONS — Removes change-action records associated with specific change lines, typically during rollback or cleanup.

Tables Accessed

  • ENG_CHANGE_ACTIONS — The principal table for change-action history. The package inserts new actions and updates or deletes existing ones.
  • ENG_CHANGE_ACTIONS_S — The sequence (or related shadow) object supplying unique identifiers for new change-action rows.
  • DUAL — Used for simple PL/SQL expressions and lookups that do not require a base table.
  • UTL_FILE — The Oracle-supplied file I/O package, used by the debug procedures to write diagnostic output to a server-side file.
  • V$PARAMETER — Interrogated to read database initialisation parameter values, typically in support of debug-mode determination or environment checks.

Usage Notes

ENG_CHANGE_ACTIONS_UTIL is referenced by four other packages within the engineering schema, making it a shared internal service rather than an end-user API. It is normally invoked indirectly: ECO workflow processes call it to record approvals, rejections, delegations, and time-outs; the change-order forms invoke it when users add comments or respond to notifications; and implementation logic calls it to log implementation failures or in-progress status. The debug procedures are intended for test and development use, with GET_DEBUG_MODE used by callers to gate diagnostic writes. Because the package writes directly to engineering change-action tables, customisations should call the documented procedures rather than manipulating those tables directly, preserving history integrity and workflow consistency. As with all APPS-owned packages, modifications should be confined to supported extension mechanisms, as internal signatures may change between maintenance releases.