Search Results delete_action_from_node

Overview

The APPS.IEU_WORK_ACTION_PVT package is a private PL/SQL API within the Oracle E-Business Suite Interaction & E-Service (IEU) module, specifically supporting the Universal Work Queue (UWQ) and the interaction work-action framework. Its purpose is to manage the definition and mapping of "work actions" — discrete operations that an agent or workflow may invoke against a node, such as launching a page, executing a concurrent request, or routing an interaction. The package provides the internal logic that the UWQ administrative layer uses to create action maps, register work actions, validate action labels, and remove action associations from nodes. Because it is declared AUTHID CURRENT_USER and classified as a private (PVT) API, it is intended for internal consumption by other IEU packages and administrative procedures rather than direct calls from external integrations. The header comment identifies it as an early-generation UWQ component (source version 115.8), which aligns with the maturation of the Interaction Center action framework across EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

• NODE_MAPPING — Establishes the mapping between an enumerator (identification of a node) and an application, given an action parameter set, a mapping application, and an action definition type flag. It returns standard x_return_status, x_msg_count, and x_msg_data out parameters.
• CREATE_ACTION_MAP — Private API that creates an action map. Per the source notes, the UWQ Admin layer uses this procedure to persist a new action map, accepting a records object of type SYSTEM.IEU_WP_ACTION_MAPS_OBJ.
• CREATE_WORK_ACTION — Persists a work action definition using a records object of type SYSTEM.IEU_WP_MACT_OBJ together with an action definition type flag.
• CREATEFROMACTION — Creates a work action derived from an existing action definition, accepting a definition identifier, language, label, description, and parameter set identifier.
• VALIDATE_ACTION_LABEL — Validates an action label against a parameter set, ensuring labels are unique and consistent within the related parameter set context.
• DELETE_ACTION_FROM_NODE — Removes an action assignment from a node. This procedure is the object referenced by the search term delete_action_from_node and is the inverse of the mapping/creation operations that bind an action to a node and its parameter set.

Tables Accessed

The package reads and writes the core UWQ and interaction work-action configuration tables, all accessed through APPS synonyms:

• Action definition tables: IEU_UWQ_MACTION_DEFS_B, IEU_UWQ_MACTION_DEFS_B_S1, and IEU_UWQ_MACTION_DEFS_TL hold the base and translated definitions of work actions.
• Parameter definition tables: IEU_WP_PARAM_DEFS_B, IEU_WP_PARAM_DEFS_TL, IEU_WP_ACT_PARAM_SETS_B, IEU_WP_ACT_PARAM_SETS_B_S1, and IEU_WP_ACT_PARAM_SETS_TL define action parameter sets and their translations.
• Mapping and section tables: IEU_WP_ACTION_MAPS and its sequence IEU_WP_ACTION_MAPS_S1, plus IEU_WP_NODE_SECTION_MAPS and IEU_WP_NODE_SECTION_MAPS_S1, store the node-to-action and section mappings manipulated by NODE_MAPPING and DELETE_ACTION_FROM_NODE.
• Node and enumerator tables: IEU_UWQ_NODE_DS and IEU_UWQ_SEL_ENUMERATORS identify the nodes being mapped.
• Action parameter instances: IEU_WP_ACTION_PARAMS stores the parameter values associated with an action.

Usage Notes

As a PVT-classified package, IEU_WORK_ACTION_PVT is not exposed as a public API. It is invoked by the UWQ administrative forms and by one other package (documented as referencing it) that orchestrates work-action configuration. Typical invocation patterns include:

• UWQ Admin form flows that create or remove node-to-action mappings.
• Setup-time operations that register work action definitions and parameter sets.
• Internal calls from the referencing package during action-map maintenance.

Custom code should avoid calling these procedures directly, since the private API may change between releases; supported customization should use the public IEU APIs or the UWQ administration UI. The standard triplet of x_return_status, x_msg_count, and x_msg_data out parameters means callers must inspect the returned status and use the FND message stack for diagnostics. All tables are referenced with APPS synonyms, so the executing user must have appropriate grants when invoking the package from a custom schema.