Search Results ieu_wp_node_section_maps_u1

Overview

The table IEU.IEU_WP_NODE_SECTION_MAPS is a seed data object within the Interaction and Escalation (IEU) product family of Oracle E-Business Suite. It stores the configuration that binds Work-Node and Universal Work Queue (UWQ) session actions to the user-interface sections in which those actions are rendered. In practical terms, the table defines which sections of a work node or UWQ session are presented to a given responsibility, and in what sequence. The object resides in the APPS_TS_SEED tablespace, which is consistent with its role as a reference and configuration table rather than a high-volume transactional store.

Access to this object is restricted. Oracle documents it as Internal Use Only, meaning that it must not be queried or modified directly outside of standard Oracle Applications programs. Custom integrations that bypass the supported APIs risk invalidating seeded configuration and producing inconsistent action-map behavior at runtime.

Applied to a Data Vault modeling heuristic, the mined foreign-key structure classifies this table as satellite-leaning. The presence of descriptive and qualifying attributes, together with a single-column surrogate primary key and references outward to other parent objects, suggests a satellite attached to a hub or link rather than an independent hub in its own right.

Key Information Stored

The table contains fourteen documented columns. The most significant are as follows:

• WP_NODE_SECTION_MAP_ID (NUMBER, 15) — the surrogate primary key, defined by constraint IEU_WP_NODE_SECTION_MAPS_PK and enforced through the unique index IEU_WP_NODE_SECTION_MAPS_U1. This is also the only documented business-key candidate.
• SECURITY_GROUP_ID (NUMBER) — used in hosted environments; documented as a foreign key to FND_SECURITY_GROUPS.
• APPLICATION_ID (NUMBER) — identifies the application that owns the mapped data.
• RESPONSIBILITY_ID (NUMBER) — identifies the responsibility for which the mapping is valid. When null, the row functions as a default mapping for the combination.
• ENUM_TYPE_UUID (VARCHAR2, 32) — the action-map type code. Documented values include NODE (actions mapped and populated on work-node click) and UWQ (actions always mapped and populated on login to the UWQ session).
• SECTION_ID (NUMBER, 15) — the section to be mapped to the work node; referenced as a foreign key.
• SECTION_MAP_SEQUENCE (NUMBER) — controls the display order of the mapped section.
• NOT_VALID_FLAG (VARCHAR2) — indicates whether the row is valid or should be ignored.
• OBJECT_VERSION_NUMBER (NUMBER) — the standard concurrency column used by HTML utilities.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Because the table is flagged Internal Use Only, legitimate use centers on diagnostics, validation, and reporting against a supported extract rather than direct manipulation. Administrators diagnosing a missing or mis-ordered action section can inspect the seeded rows for a given responsibility and action-map type. A representative query pattern is:

• Filter by ENUM_TYPE_UUID to separate work-node mappings from UWQ session mappings.
• Join on RESPONSIBILITY_ID and APPLICATION_ID to isolate the effective configuration for a responsibility, noting that rows with a null responsibility act as defaults.
• Order by SECTION_MAP_SEQUENCE to reproduce the display order that the runtime presents to the user.
• Exclude rows where NOT_VALID_FLAG indicates an inactive mapping.
• Use OBJECT_VERSION_NUMBER to detect rows that have changed since a prior extract, supporting controlled comparisons across environments.

Reporting usage typically answers the question of which sections are enabled per responsibility and action-map type, and whether default mappings are being overridden.

Related Objects

The most significant related objects, based on the documented key structure, include the following:

• FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID; join on that column for hosted-environment scoping.
• IEU_WP_NODE_SECTION_MAPS (SECTION_ID reference) — the documented foreign-key relationship from SECTION_ID links the mapped section to its originating section definition.
• FND_APPLICATION / FND_RESPONSIBILITY — the sources for APPLICATION_ID and RESPONSIBILITY_ID, used when resolving effective mappings.
• IEU_WP_NODES and the IEU work-node action-map tables — the runtime consumers that read the mapped sections when a node is clicked.
• The IEU Universal Work Queue session components — which consume ENUM_TYPE_UUID = 'UWQ' rows at login.

Any integration should resolve these relationships through supported application APIs rather than direct table joins, in keeping with the object's Internal Use Only status.