Results for “stop_id”

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

Overview

The view APPS.IGWBV_GRNT_PRPSL_ROUTG_LST_MBR is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Grants Proposal (IGW) product family. As its name implies, the view exposes member records associated with the routing list configuration used in grant proposal approval workflows. In the context of Oracle EBS 12.1.1 and 12.2.2, the IGW module governs the intake, review, approval, and award lifecycle of grant proposals. Approval routing within that lifecycle is driven by organizational mapping and routing-stop definitions, and this view provides a simplified, denormalized access point into those members.

The object is registered in ETRM with a VALID status, confirming it is a current, supported database object rather than a deprecated or invalidated artifact. Because it is a view rather than a base table, it carries no independent storage and cannot be directly modified; it exists solely to present a filtered, human-readable projection of the underlying organization mapping detail records. This makes it suitable for reporting queries, exploratory data retrieval, and integration points where application logic needs to enumerate routing list members without navigating the more complex normalized structures.

The view text begins with WHERE 1 = 1, a conventional placeholder predicate, and terminates with WITH READ ONLY. The WITH READ ONLY clause is significant: it explicitly guards the view against DML operations, reinforcing its role as a reporting and lookup artifact. Any attempt to insert, update, or delete through this view would fail, directing developers to the base table instead.

Underlying Base Objects

The ETRM metadata documents the view as being defined over a single base object: IGW_ORG_MAP_DETAILS, aliased in the view text as MPDTS. Although the metadata lists no additional referenced base objects, the IGW_ORG_MAP_DETAILS table is itself a detail-level construct within the IGW organizational mapping hierarchy. The prefix "ORG_MAP" indicates that it stores mapping entries linking approvers to organizational contexts, while "DETAILS" signals that it holds the individual member rows rather than header-level map definitions.

The relationship is a straightforward one-to-one projection: every column exposed by the view is sourced directly from IGW_ORG_MAP_DETAILS, and no joins, unions, or aggregations are applied. Consequently, the cardinality of the view equals the cardinality of the base table (subject to any row-level security or session-based filtering that may be enforced through the APPS schema or IGW application context). Because the view carries the WITH READ ONLY restriction, it functions strictly as a filter-and-rename layer rather than a transformation layer.

Key Columns

The view exposes eight columns, each inherited unchanged from the base table:

• USER_NAME — The identifier (typically an EBS username or FND_USER name) of the routing list member. This is the primary human-readable attribute of the view.
• APPROVER_TYPE — A classification code indicating the member's role or category within the approval routing scheme, distinguishing between types of approvers.
• MAP_ID — The organizational map identifier, foreign-key-like reference linking the member row to its parent mapping definition.
• STOP_ID — The routing stop identifier, indicating the specific sequential stop or stage at which this member participates in the approval flow.
• LAST_UPDATE_DATE — Standard EBS audit column recording when the row was last modified.
• LAST_UPDATED_BY — Standard EBS audit column recording the user ID responsible for the most recent modification.
• CREATION_DATE — Standard EBS audit column recording the original insertion timestamp.
• CREATED_BY — Standard EBS audit column recording the user ID that created the row.

The four WHO-columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY) follow Oracle EBS conventions and support auditing, incremental extraction, and data lineage requirements.

Common Use Cases and Queries

Typical uses include auditing routing list composition, diagnosing approval bottlenecks, and feeding downstream integration or reporting layers. A simple query to list all members for a given map and stop is:

• SELECT USER_NAME, APPROVER_TYPE, STOP_ID FROM APPS.IGWBV_GRNT_PRPSL_ROUTG_LST_MBR WHERE MAP_ID = :p_map_id ORDER BY STOP_ID;
• SELECT USER_NAME, COUNT(*) FROM APPS.IGWBV_GRNT_PRPSL_ROUTG_LST_MBR GROUP BY USER_NAME; — identifies members appearing across multiple stops or maps.
• SELECT * FROM APPS.IGWBV_GRNT_PRPSL_ROUTG_LST_MBR WHERE LAST_UPDATE_DATE >= :p_since; — supports incremental audit extracts.

Because the view is read-only and thinly projected, performance is essentially equivalent to querying IGW_ORG_MAP_DETAILS directly, making it a safe convenience interface for IGW grant proposal routing analysis.