Results for “map_sequence_number”

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

Overview

IGW_PROP_MAPS is a table within the Oracle E-Business Suite Grants Proposal (IGW) module, which is documented as obsolete in ETRM 12.1.1 and 12.2.2. The table stores details about maps used for notification or routing a specific proposal for approval. In practical terms, each row represents a routing or notification map instance associated with a proposal, capturing how a proposal is directed through an approval workflow and how related notifications are sequenced.

The object is owned by the IGW schema and contains 12 documented columns. Its primary key is defined by the constraint IGW_PROP_MAPS_PK on the surrogate column PROP_MAP_ID, and a unique index, IGW_PROP_MAPS_U1, also exists on PROP_MAP_ID. The ETRM documentation notes that this table is not implemented in the current database, reflecting the obsolescence of the IGW module. From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. This suggests that IGW_PROP_MAPS is best understood as a descriptive, attribute-bearing structure that hangs off a parent key, rather than as a pure hub or link table.

Key Information Stored

The table’s most significant columns capture the identity, routing behavior, and audit context of each map record:

• PROP_MAP_ID – The surrogate primary key. It uniquely identifies each map record and is the target of the IGW_PROP_MAPS_U1 unique index and the IGW_PROP_MAPS_PK constraint.
• PROPOSAL_ID – The business-key candidate linking the map to a specific proposal. This is the proposal being routed or notified through the map.
• DESCRIPTION – A textual description of the map, used to document its purpose or scope.
• MAP_TYPE – Classifies the map, distinguishing, for example, notification maps from routing maps.
• MAP_SEQUENCE_NUMBER – The ordinal position of the map within a sequence, governing the order in which stops or notifications are processed.
• RUN_ID – A foreign key to IGW_PROP_APPROVAL_RUNS, identifying the approval run during which the map was executed.
• APPROVAL_STATUS – The current status of the proposal’s approval process for this map.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – Standard EBS audit columns recording who created and last modified the record, and when.

Common Use Cases and Queries

Although the IGW module is obsolete, historical reporting and data migration efforts may still require querying IGW_PROP_MAPS. Typical scenarios include reconstructing the routing history of a proposal, auditing approval runs, or migrating legacy approval data.

A common pattern joins the table to its parent approval run:

• SELECT m.PROP_MAP_ID, m.PROPOSAL_ID, m.MAP_TYPE, m.MAP_SEQUENCE_NUMBER, r.RUN_ID
• FROM IGW_PROP_MAPS m
• JOIN IGW_PROP_APPROVAL_RUNS r ON m.RUN_ID = r.RUN_ID
• WHERE m.PROPOSAL_ID = :proposal_id
• ORDER BY m.MAP_SEQUENCE_NUMBER;

To inspect the stops belonging to a map, query the child table:

• SELECT s.* FROM IGW_PROP_MAP_STOPS s WHERE s.PROP_MAP_ID = :prop_map_id;

Reporting use cases include counting maps per proposal, grouping by MAP_TYPE, and identifying maps whose APPROVAL_STATUS is incomplete.

Related Objects

IGW_PROP_MAPS participates in a small, well-defined relationship set:

• IGW_PROP_APPROVAL_RUNS – Referenced by IGW_PROP_MAPS.RUN_ID. This parent table defines the approval run context in which a map is executed.
• IGW_PROP_MAP_STOPS – References IGW_PROP_MAPS.PROP_MAP_ID. Stops are child records describing the individual notification or routing steps within a map.
• IGW_PROP_MAPS_PK – The primary key constraint on PROP_MAP_ID, enforcing uniqueness of the surrogate key.
• IGW_PROP_MAPS_U1 – A unique index on PROP_MAP_ID, serving as a documented business-key candidate.

Because the module is obsolete, no active APIs are documented for IGW_PROP_MAPS, and direct SQL access should be treated as read-only historical analysis.