Search Results ieu_wp_action_maps




Overview
Explore in AI Chat

Overview

The IEU_WP_ACTION_MAPS table resides in the IEU schema and belongs to the Universal Work Queue (UWQ) module of Oracle E-Business Suite. It stores the configuration that maps work items presented in the Universal Work Queue to the actions, parameters, and responsible applications or responsibilities that govern how those items are processed. In practical terms, it is a configuration and control table that determines which action a UWQ user can launch against a given work item, in what sequence, and under what security context.

The table is physically documented in ETRM 12.2.2 with eighteen columns and a surrogate primary key, IEU_WP_ACTION_MAPS_PK, defined on WP_ACTION_MAP_ID. A unique index, IEU_WP_ACTION_MAPS_U1, is defined on the combination of WP_ACTION_MAP_ID and ZD_EDITION_NAME, which serves as a business-key candidate and reflects the editioning support introduced for multi-tenant and online patching environments. Heuristic Data Vault classification mined from the foreign-key structure suggests this object is satellite-leaning: it carries descriptive and configuration attributes that depend on a parent identity rather than acting as an independent hub or an associative link between two business entities.

Key Information Stored

The most significant columns fall into identity, scope, action definition, and audit categories:

  • WP_ACTION_MAP_ID — the surrogate primary key, generated by the IEU_WP_ACTION_MAPS_PK sequence. It uniquely identifies each action-map record and is the column other objects use to reference a mapping.
  • ACTION_MAP_CODE and ACTION_MAP_TYPE_CODE — the business name and category of the action being mapped. These codes drive which action launcher, function, or navigation target the UWQ invokes.
  • ACTION_MAP_SEQUENCE — controls the display or execution ordering of actions when multiple maps qualify for the same work item.
  • ACTION_PARAM_SET_ID — a foreign-key reference identifying the parameter set associated with the action map. This column defines the runtime arguments passed to the action.
  • APPLICATION_ID and RESPONSIBILITY_ID — scope the mapping to a specific application and responsibility, allowing the same work queue to present different actions depending on the logged-in responsibility.
  • SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS, enforcing row-level access control consistent with EBS security group conventions.
  • PANEL_SEC_CAT_CODE — categorises the panel or security grouping used to render the action in the UWQ user interface.
  • NOT_VALID_FLAG and DEV_DATA_FLAG — status flags that mark a mapping as inactive or as development-only seed data.
  • OBJECT_VERSION_NUMBER — the optimistic-locking column used by the EBS framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard "WHO" audit columns present on nearly all EBS transactional and configuration tables.
  • ZD_EDITION_NAME — the editioning column supporting online patching and multi-tenant deployments, and part of the unique business-key index.

Common Use Cases and Queries

Administrators and developers query this table when troubleshooting why a particular action does or does not appear in the Universal Work Queue, or when auditing the configuration of actions per responsibility. A typical retrieval lists active mappings for a given application and responsibility, ordered by sequence:

  • Identifying all action maps available to a responsibility: SELECT ACTION_MAP_CODE, ACTION_MAP_TYPE_CODE, ACTION_MAP_SEQUENCE FROM IEU.IEU_WP_ACTION_MAPS WHERE RESPONSIBILITY_ID = :resp_id AND APPLICATION_ID = :app_id AND NOT_VALID_FLAG = 'N' ORDER BY ACTION_MAP_SEQUENCE;
  • Locating the parameter set bound to a specific action: SELECT ACTION_PARAM_SET_ID FROM IEU.IEU_WP_ACTION_MAPS WHERE WP_ACTION_MAP_ID = :id;
  • Auditing recently modified configuration: querying LAST_UPDATED_BY and LAST_UPDATE_DATE to trace which administrator changed a mapping.
  • Reporting mappings by security group by joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID.

Because the table is configuration rather than transactional, reporting is generally low-volume and focused on validation, migration, and impact analysis.

Related Objects

Several objects reference or depend on IEU_WP_ACTION_MAPS:

  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID, providing the security grouping context for each mapping.
  • The action parameter set object referenced by ACTION_PARAM_SET_ID, which supplies the runtime arguments for the mapped action.
  • Other IEU Universal Work Queue configuration tables that consume WP_ACTION_MAP_ID as a foreign key to associate work items, actions, or user-interface panels with a mapping.
  • FND_APPLICATION and FND_RESPONSIBILITY — logically referenced via APPLICATION_ID and RESPONSIBILITY_ID to scope mappings to the correct navigation context.

Together these relationships make IEU_WP_ACTION_MAPS the central configuration point that links UWQ work items to the actions, parameters, and security context required to process them.