Results for “igw_org_map_details”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGW.IGW_ORG_MAP_DETAILS is a transactional detail table within the Oracle E-Business Suite IGW — Grants Proposal module. It stores the personnel associated with an organizational routing map, specifically the individuals designated to approve a proposal or receive notification at a given step in the routing definition. The table's stated description — "Details about personnel who approve or receive notifications" — confirms its role as the child of the routing header table, capturing the human actors that the routing engine resolves during proposal processing.

Because the metadata documentation is limited, the following Data Vault classification is offered as a heuristic modeling suggestion derived from the foreign key topology: link. The table's structure — a composite key formed from a parent reference (MAP_ID), a step ordinal (STOP_ID), and a resolving user (USER_NAME) — connects three distinct hubs (routing map, routing step, and user). The remaining columns supply descriptive and audit attributes rather than independent business identity, so a link classification best represents its purpose.

Key Information Stored

The table is owned by the IGW schema and, per the documented physical schema for release 12.1.1, contains nine columns. The primary key constraint IGW_ORG_MAP_DETAILS_PK spans the following three columns, and the unique index IGW_ORG_MAP_DETAILS_U1 enforces the same set — meaning the composite key is also the sole documented business-key candidate.

• MAP_ID — Foreign key to IGW_ORG_MAPS_ALL; identifies the parent routing map to which this approval or notification line belongs.
• STOP_ID — Identifies the ordered step or stop within the routing sequence where this personnel assignment applies.
• USER_NAME — Foreign key to FND_USER; the application user designated as the approver or notification recipient.
• APPROVER_TYPE — Classifies the nature of the assignment, distinguishing approver assignments from notification-only recipients.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording provenance and change history for each assignment row.

No surrogate single-column primary key is documented; MAP_ID participates both as part of the composite PK and as a business-key candidate via the unique index.

Common Use Cases and Queries

The principal use case is resolving the personnel assigned to a routing map when a Grants Proposal is submitted for approval. Application logic reads this table to determine which users receive notification and which users must approve at each step.

• Approver roster per map: join IGW_ORG_MAP_DETAILS to IGW_ORG_MAPS_ALL on MAP_ID to list every approver and recipient defined for a routing map.
• Filtering by assignment type: constrain on APPROVER_TYPE to separate decision-making approvers from informational recipients.
• User resolution and validation: join USER_NAME to FND_USER to obtain employee details, or to detect assignments referencing inactive users.
• Audit and change analysis: query LAST_UPDATE_DATE, LAST_UPDATED_BY, and CREATED_BY to track when routing assignments were configured or modified.

A representative query skeleton:

• SELECT d.MAP_ID, d.STOP_ID, d.USER_NAME, d.APPROVER_TYPE FROM IGW.IGW_ORG_MAP_DETAILS d WHERE d.MAP_ID = :map_id ORDER BY d.STOP_ID;

Related Objects

The following objects are the most significant dependents or references based on the documented key relationships:

• IGW_ORG_MAPS_ALL — Parent header table; joined via IGW_ORG_MAP_DETAILS.MAP_ID = IGW_ORG_MAPS_ALL.MAP_ID.
• FND_USER — Application user repository; joined via IGW_ORG_MAP_DETAILS.USER_NAME = FND_USER.USER_NAME.
• IGW_ORG_MAP_DETAILS_PK — Primary key constraint on (MAP_ID, STOP_ID, USER_NAME).
• IGW_ORG_MAP_DETAILS_U1 — Unique index on the same column set, enforcing business-key uniqueness.

Because the documented metadata lists only these related objects, additional IGW routing and notification tables should be validated against the live data dictionary before inclusion in reporting models.