Search Results update_maction

Overview

IEU_WP_ACTION_PVT is a private PL/SQL package in the APPS schema that underpins the Oracle E-Business Suite Universal Work Queue (UWQ) Work Panel. Its stated purpose, per the package header, is "to provide easy to use apis for UQW Work Panel." The package encapsulates the business logic that defines, maintains, and sequences the actions available to an agent working a queue item. Actions represent the discrete operations an agent can invoke from the Work Panel — for example, opening a source transaction, routing a lead, or launching a follow-up activity — and action maps determine which actions appear, in what order, and with which parameters.

The package is classified as PVT (private), meaning it is an internal implementation layer. It is not intended as a public integration API; the documented public surface is exposed through companion packages. ETRM records that IEU_WP_ACTION_PVT is referenced by three other packages, confirming its role as a shared internal service consumed by higher-level UWQ components. The source header carries a 2002 creation date and a 2005 revision, indicating the package has been stable across the 11i and R12 code lines, including 12.1.1 and 12.2.2.

Key Procedures and Functions

ETRM documents eleven program units in IEU_WP_ACTION_PVT:

• CREATE_ACTION_MAP — Creates an action map definition, taking an action-map object as input and returning standard return status and message outputs.
• UPDATE_MACTION — Updates a maintenance action definition. This is the object returned when a user searches for "update_maction." It operates on an action definition identifier together with user label and description attributes, and is the principal entry point for maintaining action metadata.
• UPDATE_ACTION_MAP — Modifies an existing action map record.
• DELETE_ACTIONS — Removes one or more action definitions.
• DELETE_ACTION_MAP — Removes an action map and its associated configuration.
• UPDATE_ACTION_MAP_SEQUENCE — Adjusts the display or execution ordering of actions within a map.
• UPDATEPARAMPROPS — Maintains action parameter properties, such as default values and display attributes.
• CREATEFROMACTION and CREATEFROMACTION2 — Create action maps derived from an existing action; the two variants reflect successive generations of the derivation logic.
• CREATEFROMQFILTER — Creates an action map derived from a quick filter definition.
• REORDERING — Re-sequences actions, typically after insertions or deletions.

All procedures follow the standard EBS API convention of returning x_return_status, x_msg_count, and x_msg_data to the caller.

Tables Accessed

The package reads and writes the core UWQ configuration tables. Action definitions reside in IEU_UWQ_MACTION_DEFS_B and its translation table IEU_UWQ_MACTION_DEFS_TL, which UPDATE_MACTION primarily targets. Action-to-queue relationships are held in IEU_WP_ACTION_MAPS, with IEU_WP_ACTION_MAPS_S1 used as a sequence source for map identifiers and IEU_WP_ACTION_PARAMS holding per-action parameters.

Parameter and property configuration is spread across IEU_WP_ACT_PARAM_SETS_B, IEU_WP_ACT_PARAM_SETS_TL, IEU_WP_PARAM_DEFS_B, IEU_WP_PARAM_PROPS_B, IEU_WP_PARAM_PROPS_TL, IEU_WP_PROPERTIES_B, and the IEU_WP_PARAM_PROPS_B_S1 sequence. IEU_UWQ_SEL_ENUMERATORS supplies enumerated selection values presented to the agent, while IEU_UWQ_NODE_DS supports the node data source used when deriving actions.

Usage Notes

Because IEU_WP_ACTION_PVT is private, it is not called directly from custom forms or concurrent programs. It is invoked by the UWQ Work Panel administration forms and by the three dependent packages recorded in ETRM, which wrap its procedures with public APIs. The "update_maction" search term corresponds to UPDATE_MACTION, the routine used whenever an administrator edits an action's label or description in the Work Panel setup UI.

Customizations should avoid direct calls to this package. The supported approach is to use the public UWQ APIs or the setup forms, since table structures and private signatures may change between releases. Where dependencies on the underlying tables are unavoidable, reference them only through the APPS synonyms listed above.