Search Results map_description




Overview
Explore in AI Chat

Overview

IGWBV_GRANT_PRPSL_ROUTING_LIST is an Oracle E-Business Suite view owned by the APPS schema and registered under the FND design data IGW.IGWBV_GRANT_PRPSL_ROUTING_LIST. It is classified as a Business Intelligence System (BIS) view, meaning it exists primarily to expose Oracle Grants Management data to reporting, analytics, and integration layers rather than to support online transaction entry. In EBS 12.1.1 and 12.2.2 this object has a VALID status, confirming that it is compiled and resolved against its underlying dependencies at the time the metadata was captured.

The view presents a flattened list of "maps" used in grant proposal routing. A map in the IGW schema represents a routing configuration — the definition of how a proposal, award, or related approval entity travels through an organizational approval hierarchy. Because the view exposes descriptive and date-effective attributes alongside the map identifier and operating unit context, it is well suited to answering the question that generated the search term map_description: it lets a report or integration read the human-readable name of a routing map together with its activation window.

Underlying Base Objects

The documented dependency for this view is APPS.IGW_ORG_MAPS_ALL, the base table that stores routing map definitions across organizations. The view is defined over that object and is not referenced by any other database object, so it sits at the top of its dependency chain. The "_ALL" designation on the base table indicates that, at the table level, rows are owned by organization/operating unit context; the view surfaces both ORGANIZATION_ID and ORG_ID columns so consumers can apply the appropriate multi-org filter. Because the DDL of the view is granted to APPS and marked as FND design data, it is treated as a seeded, upgrade-replaceable object and should not be modified in place.

Key Columns

  • MAP_DESCRIPTION (VARCHAR2(30)) — the descriptive name of the routing map; this is the column most frequently requested when searching for "map_description."
  • MAP_ID (NUMBER(10)) — the primary identifier of the map, used for joining to routing detail and approver hierarchy tables.
  • START_DATE_ACTIVE / END_DATE_ACTIVE (DATE) — the effective-dating window that determines when a map is active and usable for routing.
  • ORGANIZATION_ID (NUMBER(15)) — inventory/organization context associated with the map.
  • ORG_ID (NUMBER(15)) — the operating unit identifier, used for multi-org security filtering.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS WHO columns for audit and change tracking.

Common Use Cases and Queries

Typical uses include validating routing configurations after an upgrade, listing active maps for an operating unit, and joining map descriptions onto proposal or award routing records for reporting. A simple listing of currently effective maps:

SELECT map_id, map_description, start_date_active, end_date_active
FROM apps.igwbv_grant_prpsl_routing_list
WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
AND NVL(end_date_active, SYSDATE)
AND org_id = :p_org_id;

To resolve a map name during integration, select MAP_DESCRIPTION by MAP_ID and ORG_ID. As with all APPS BIS views, queries should be run through the APPS schema or a synonym, with the correct org_id context, and treated as read-only.