Results for “igw_prop_checklist”

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

Overview

IGW_PROP_CHECKLIST is a transactional table in the IGW schema belonging to the Oracle Grants Proposal (IGW) module, a component of Oracle E-Business Suite releases 12.1.1 and 12.2.2. The table records the status of individual proposal components — that is, the checklist items that must be satisfied for a grant proposal to be considered complete. Each row represents a specific document type required against a specific proposal, together with its completion state, submission and review dates, and reviewer identity. In this sense the table functions as a control record governing the progress of a proposal through its institutional review workflow.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as satellite-leaning. This is a heuristic suggestion rather than a mandated design: the table carries descriptive and status attributes (completion flags, dates, comments, reviewer) that are functionally dependent on the parent proposal, which makes it a natural candidate for a satellite attached to a proposal hub or link. The presence of both PROPOSAL_ID and DOCUMENT_TYPE_CODE in the primary key supports this interpretation, since the checklist item is only meaningful in the context of its parent proposal.

Key Information Stored

The table contains 19 documented columns. The most significant are as follows.

• PROPOSAL_ID — identifies the parent proposal; part of the composite primary key and the foreign key to IGW_PROPOSALS_ALL.
• DOCUMENT_TYPE_CODE — identifies the checklist item or document type required for the proposal; the second component of the composite primary key.
• CHECKLIST_ORDER — the display sequence of the item within the proposal checklist.
• COMPLETE — flag indicating whether the checklist item has been satisfied.
• NOT_APPLICABLE — flag indicating the item is not required for this proposal.
• STATUS — the workflow or processing status of the checklist item.
• DUE_DATE — the deadline by which the item must be completed.
• DATE_SUBMITTED — the date the item was submitted for review.
• DATE_RECEIVED — the date the item was received by the reviewing party.
• COMPLETED_DATE — the date the item was marked complete.
• REVIEWED_BY and REVIEW_DATE — the reviewer identity and the date of review.
• COMMENTS — free-text notes recorded against the checklist item.
• RECORD_VERSION_NUMBER — optimistic concurrency control column used by the IGW framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS WHO-column audit trail.

The primary key is IGW_PROP_CHECKLIST_PK over PROPOSAL_ID and DOCUMENT_TYPE_CODE. The unique index IGW_PROP_CHECKLIST_U1 covers the same two columns, confirming this pair as the business key and guaranteeing that no proposal carries duplicate entries for the same document type.

Common Use Cases and Queries

Functional users and developers typically query this table to determine which checklist items remain outstanding for a given proposal, to report on review-cycle durations, and to drive OAF pages or concurrent programs in the Grants Proposal module. A typical pattern joins the checklist to its parent proposal:

SELECT c.PROPOSAL_ID, c.DOCUMENT_TYPE_CODE, c.STATUS, c.COMPLETE, c.NOT_APPLICABLE, c.DUE_DATE, c.COMPLETED_DATE, c.REVIEWED_BY FROM IGW.IGW_PROP_CHECKLIST c WHERE c.PROPOSAL_ID = :p_proposal_id ORDER BY c.CHECKLIST_ORDER;

Reporting queries commonly filter on COMPLETE = 'N' and NOT_APPLICABLE = 'N' to isolate outstanding items, or compare DUE_DATE against COMPLETED_DATE to measure turnaround performance. Because the table participates in the standard EBS audit model, LAST_UPDATE_DATE and RECORD_VERSION_NUMBER are useful for incremental extract logic in data warehouse or OBIEE feeds.

Related Objects

• IGW_PROPOSALS_ALL — the parent proposal table; joined via IGW_PROP_CHECKLIST.PROPOSAL_ID = IGW_PROPOSALS_ALL.PROPOSAL_ID. This is the sole documented foreign key relationship.
• IGW_PROPOSAL_TYPES / IGW_DOCUMENT_TYPES — supply the meaning of DOCUMENT_TYPE_CODE for lookup and reporting joins.
• IGW_PROP_CHECKLIST_PK and IGW_PROP_CHECKLIST_U1 — the primary key and unique business-key indexes enforced on the table.
• Grants Proposal OAF pages and concurrent programs — the standard UI and batch components that insert and maintain checklist rows during proposal submission and review.