Results for “map_description”

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

Overview

The view APPS.IGWFV_GRNT_PRPSL_APRV_APVL_LST is a read-only reporting object within the Oracle E-Business Suite (EBS) Grants Proposal module (IGW). It presents a denormalized listing of proposal approval workflow assignments, combining proposal header attributes with the routing metadata that governs how each proposal is approved. In EBS 12.1.1 and 12.2.2, this view is registered in the APPS schema with a status of VALID and is exposed through the ETRM (E-Business Suite Tables and Views Reference Manual) as a documented, queryable object.

The view is defined WITH READ ONLY, meaning it is intended strictly for query and reporting purposes and cannot be used as the target of DML. Its role is to support reporting and integration scenarios in which implementers, developers, or external systems need to inspect the approval routing configuration and current approval status of proposals without navigating the underlying normalized tables directly.

Underlying Base Objects

The view is defined over two base tables in the APPS schema:

• IGW_PROPOSALS_ALL — the master proposal table, aliased as PR, which supplies the proposal number and proposal identifier.
• IGW_PROP_MAPS — the proposal approval mapping table, aliased as PMP, which supplies the approval routing metadata, status, and audit columns.

The join is an inner join on PR.PROPOSAL_ID = PMP.PROPOSAL_ID, so only proposals that have at least one mapped approval record in IGW_PROP_MAPS appear in the result set. The ETRM metadata lists no additional referenced base objects beyond these two tables.

Key Columns

The view projects the following columns, drawn directly from the two base tables:

• PROPOSAL_NUMBER — the user-facing identifier of the proposal, sourced from IGW_PROPOSALS_ALL.
• MAP_DESCRIPTION — the description of the approval mapping, sourced from IGW_PROP_MAPS.DESCRIPTION.
• MAP_TYPE — the classification of the mapping record. This is the column most relevant to searches for "map_type"; it distinguishes the type of approval mapping associated with the proposal.
• MAP_SEQUENCE_NUMBER — the ordering of the mapping step within the approval sequence.
• APPROVAL_STATUS — the current status of the mapped approval action.
• RUN_ID — the identifier correlating the mapping to a workflow or concurrent process run.
• PROPOSAL_ID and PROP_MAP_ID — the respective primary keys of the proposal and the mapping record, useful for joining back to base tables.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns describing who created and last modified each mapping record and when.

Common Use Cases and Queries

Typical use cases include approval workflow reporting, auditing of routing configuration, and integration extracts that need proposal approval status by map type. A representative query filtering on the map type, which directly addresses the "map_type" search term, is:

• SELECT PROPOSAL_NUMBER, MAP_DESCRIPTION, MAP_TYPE, MAP_SEQUENCE_NUMBER, APPROVAL_STATUS FROM APPS.IGWFV_GRNT_PRPSL_APRV_APVL_LST WHERE MAP_TYPE = :p_map_type ORDER BY PROPOSAL_NUMBER, MAP_SEQUENCE_NUMBER;
• SELECT PROPOSAL_NUMBER, APPROVAL_STATUS, RUN_ID FROM APPS.IGWFV_GRNT_PRPSL_APRV_APVL_LST WHERE PROPOSAL_ID = :p_proposal_id;
• SELECT PROPOSAL_NUMBER, MAP_TYPE, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM APPS.IGWFV_GRNT_PRPSL_APRV_APVL_LST ORDER BY LAST_UPDATE_DATE DESC;

Because the view is read-only, all such queries are safe for ad hoc reporting and BI Publisher data sources. When more detail is required than the view exposes, it can be joined back to IGW_PROPOSALS_ALL or IGW_PROP_MAPS on PROPOSAL_ID or PROP_MAP_ID.