Search Results igw_org_maps_all_pk

Overview

IGW_ORG_MAPS_ALL is a configuration table within the Oracle E-Business Suite Grants Proposal (IGW) module. It stores organization-level mapping definitions that govern how grant proposals are routed or how notifications are delivered to the appropriate recipients during the proposal approval cycle. In practical terms, the table defines which organizational unit a given routing or notification rule applies to, providing the linkage between an HR organization and the business rules that determine approval workflow behavior.

The object is documented as obsolete and is flagged as "Not implemented in this database" in the ETRM metadata. This status is significant: IGW itself was a legacy module that Oracle de-supported, and specific tables such as IGW_ORG_MAPS_ALL may not exist in a given 12.1.1 or 12.2.2 environment depending on patch level, module licensing, or whether the obsolete IGW schema was ever installed. Consultants should verify existence in the target instance before designing any dependency.

From a Data Vault modeling perspective, the metadata heuristic classifies IGW_ORG_MAPS_ALL as hub-leaning. This reflects the presence of a single-column surrogate primary key (MAP_ID) that is referenced by child tables, a pattern typical of a hub entity serving as the anchor for downstream relationships rather than a pure transactional satellite.

Key Information Stored

The table contains eleven documented columns. The most functionally important are:

• MAP_ID — Surrogate primary key, enforced by IGW_ORG_MAPS_ALL_PK. It also appears in the unique index IGW_ORG_MAPS_ALL_U1, making it the definitive row identifier and the target of all foreign key references into this table.
• ORGANIZATION_ID — Foreign key to HR_ALL_ORGANIZATION_UNITS, identifying the organization unit to which the map applies.
• DESCRIPTION — Business-meaningful label for the map; it is the second documented business-key candidate via unique index IGW_ORG_MAPS_ALL_U2.
• ORG_ID — Multi-tenant operating unit identifier, enabling the standard EBS multi-org security model.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Date-effective range controlling the validity window of the map. These columns support the standard EBS date-tracked configuration pattern.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns providing audit lineage for every row.

The presence of both a surrogate key (MAP_ID) and a unique business key (DESCRIPTION) is characteristic of a hub table with an alternate key defined at the descriptive level.

Common Use Cases and Queries

Typical usage involves resolving which organization maps are active for a given operating unit, or tracing a business rule back to its governing organization. A representative query joins the map to its parent organization and child rules:

• Filter active maps by operating unit: SELECT map_id, organization_id, description FROM igw_org_maps_all WHERE org_id = :p_org_id AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• Resolve the organization name behind a map: join ORGANIZATION_ID to HR_ALL_ORGANIZATION_UNITS.
• Trace rule membership: join MAP_ID to IGW_BUSINESS_RULES_ALL and IGW_ORG_MAP_DETAILS to enumerate routing or notification detail lines.
• Audit reporting: report CREATED_BY, CREATION_DATE, and LAST_UPDATE_DATE for change-tracking dashboards.

Related Objects

The most significant related objects, grounded in the documented foreign key structure, are:

• HR_ALL_ORGANIZATION_UNITS — Referenced via IGW_ORG_MAPS_ALL.ORGANIZATION_ID; supplies organization attributes.
• IGW_BUSINESS_RULES_ALL — References this table through IGW_BUSINESS_RULES_ALL.MAP_ID; holds the approval routing business rules.
• IGW_ORG_MAP_DETAILS — References this table through IGW_ORG_MAP_DETAILS.MAP_ID; stores detail lines of each map.

These three dependencies define the core IGW routing configuration cluster surrounding the map header.