Search Results igw_prop_approval_runs
Overview
The IGW_PROP_APPROVAL_RUNS table is a core data object within the Oracle E-Business Suite (EBS) Grants Proposal module (IGW). It functions as a historical audit trail, systematically recording each execution of the approval workflow for grant proposals. In the context of EBS 12.1.1 and 12.2.2, this table is critical for managing the complex, multi-step approval processes common in research administration and grant management. It enables users and system administrators to track the status, participants, and outcomes of every approval cycle initiated for a proposal, providing a complete audit history for compliance and reporting purposes.
Key Information Stored
The table's primary purpose is to log each distinct approval run. Its central column is the RUN_ID, which serves as the primary key and uniquely identifies a specific approval process instance. A crucial foreign key is the PROPOSAL_ID, which links the approval run to its parent record in the IGW_PROPOSALS_ALL table. While the provided metadata does not list all columns, typical data stored in such a table would include timestamps for the run's initiation and completion, the identity of the user who initiated the approval, the overall status of the run (e.g., PENDING, COMPLETE, CANCELLED), and potentially a reference to the specific workflow process definition used. Each row represents a snapshot of an approval cycle for a given proposal.
Common Use Cases and Queries
This table is primarily accessed for audit reporting, troubleshooting, and status tracking. Common use cases include generating reports to show the approval history for a specific proposal, identifying proposals stuck in a pending approval state, or analyzing approval cycle durations. A fundamental query involves joining with the proposals table to get proposal details:
- SELECT p.proposal_number, r.run_id, r.creation_date, r.status FROM igw_prop_approval_runs r, igw_proposals_all p WHERE r.proposal_id = p.proposal_id AND p.proposal_id = :1;
Another critical pattern is identifying the most recent approval run for monitoring current status:
- SELECT * FROM igw_prop_approval_runs WHERE proposal_id = :1 AND creation_date = (SELECT MAX(creation_date) FROM igw_prop_approval_runs WHERE proposal_id = :1);
Related Objects
The IGW_PROP_APPROVAL_RUNS table is centrally connected to other key entities in the Grants Proposal schema through documented foreign key relationships. It has a direct parent-child relationship with the IGW_PROPOSALS_ALL table via the PROPOSAL_ID column, anchoring each approval run to a specific grant proposal. Furthermore, it serves as a parent table to IGW_PROP_MAPS, which is linked through the RUN_ID column. This suggests that IGW_PROP_MAPS stores more granular details about the approval steps, rules, or participants for each run, forming a detailed hierarchy where IGW_PROPOSALS_ALL -> IGW_PROP_APPROVAL_RUNS -> IGW_PROP_MAPS.
-
Table: IGW_PROP_APPROVAL_RUNS
12.2.2
product: IGW - Grants Proposal (Obsolete) , description: History of proposal approval process , implementation_dba_data: Not implemented in this database ,
-
View: IGWFV_GRANT_PROPOSAL_APPROVAL
12.2.2
product: IGW - Grants Proposal (Obsolete) , implementation_dba_data: Not implemented in this database ,
-
View: IGWBV_GRANT_PROPOSAL_APPROVAL
12.2.2
product: IGW - Grants Proposal (Obsolete) , implementation_dba_data: Not implemented in this database ,
-
Table: IGW_PROP_MAPS
12.2.2
product: IGW - Grants Proposal (Obsolete) , description: Details about maps used for notification or routing a specific proposal for approval , implementation_dba_data: Not implemented in this database ,
-
Table: IGW_PROPOSALS_ALL
12.2.2
product: IGW - Grants Proposal (Obsolete) , description: Core information about proposals , implementation_dba_data: Not implemented in this database ,
-
View: IGW_PRPO_HEADERS_V
12.2.2
product: IGW - Grants Proposal (Obsolete) , description: View displays core proposal information , implementation_dba_data: Not implemented in this database ,