Results for “narrative_status”

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

Overview

IGW_PROP_COMPONENT_STATUSES is a legacy table belonging to the IGW – Grants Proposal module, a component of the Oracle E-Business Suite Grants Accounting and proposal-tracking footprint. The table records the statuses of individual proposal components, breaking a proposal down into its constituent parts — specifically budget and narrative components — and tracking the workflow or submission state of each component independently. The metadata explicitly flags IGW as obsolete, and the ETRM record notes that the table is "not implemented in this database," meaning installations on 12.1.1 or 12.2.2 will typically encounter the object only in historical, archived, or upgraded schemas rather than as an actively populated structure.

From a dimensional or Data Vault modeling perspective, the mined FK structure classifies this table as satellite-leaning. That classification is a heuristic suggestion rather than a formal declaration: the table carries descriptive, stateful attributes (component statuses) that describe a parent entity, and its relationship to IGW_PROPOSALS_ALL resembles a satellite describing a hub or parent record. A modeler rebuilding this structure would likely treat PROPOSAL_ID as the reference to the parent business key, with the status columns serving as time-stamped descriptive payload. The documented primary key is IGW_PROP_COMPONENT_STATUS_PK, defined over the PROPOSAL_ID column, and a unique index IGW_PROP_COMPONENT_STATUS_U1 also exists on PROPOSAL_ID, making that column both the surrogate and business-key candidate. The documented physical schema for 12.1.1 lists the owner as IGW with ten columns.

Key Information Stored

The table's documented column set is compact, with PROPOSAL_ID serving as the anchor. The most important columns and their roles are:

• PROPOSAL_ID — The primary key column and foreign key to IGW_PROPOSALS_ALL. It identifies the parent proposal whose component statuses are being recorded.
• BUDGET_STATUS — The status of the budget component of the proposal, tracking its progress through the proposal lifecycle.
• NARRATIVE_STATUS — The status of the narrative component, tracked separately from the budget.
• NARRATIVE_TYPE_CODE — A code classifying the narrative component type (for example, distinguishing narrative sections).
• NARRATIVE_SUBMISSION_CODE — A code indicating the submission disposition or method associated with the narrative component.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — Audit columns capturing when and by whom the record was most recently modified.
• CREATION_DATE, CREATED_BY — Audit columns capturing record creation.
• LAST_UPDATE_LOGIN — The login or session identifier associated with the last update, useful for concurrent-program and multi-user auditing.

The distinction between the surrogate and business key is nominal here: PROPOSAL_ID appears in both the primary key (IGW_PROP_COMPONENT_STATUS_PK) and the unique index (IGW_PROP_COMPONENT_STATUS_U1), so the table effectively enforces one status row per proposal at the business-key level.

Common Use Cases and Queries

Because the table is obsolete, its practical use is concentrated in historical reporting, data migration reconciliation, and upgrade validation. Typical scenarios include confirming that component statuses migrated cleanly during an upgrade, reporting on the completion of budget versus narrative components for archived proposals, and auditing who last touched a proposal's component state. A representative query joins the satellite to its parent:

• Component status by proposal: SELECT p.proposal_id, p.title, s.budget_status, s.narrative_status FROM igw_proposals_all p, igw_prop_component_statuses s WHERE p.proposal_id = s.proposal_id;
• Audit trail: SELECT proposal_id, last_update_date, last_updated_by, last_update_login FROM igw_prop_component_statuses ORDER BY last_update_date DESC;
• Gap analysis for missing status rows: compare the count of proposals against the count of status rows.

Related Objects

The most significant related object is the parent proposal table referenced by the documented foreign key:

• IGW_PROPOSALS_ALL — Joined on IGW_PROP_COMPONENT_STATUSES.PROPOSAL_ID = IGW_PROPOSALS_ALL.PROPOSAL_ID. This is the documented parent and the primary dependency.

Other IGW objects that historically reference proposal components — narrative and budget detail tables, component definition tables, and the proposal status lookups — are functionally associated even where not captured by a documented FK. Because IGW is obsolete, dependent objects are unlikely to be actively maintained, and the table should be treated as a read-only historical satellite for reporting and reconciliation rather than an integration target.