Search Results show_flag




Overview
Explore in AI Chat

Overview

IGW.IGW_PROP_PERSON_BIOSKETCH is an Oracle E-Business Suite table within the IGW schema, historically associated with the Oracle Grants/Proposals (IGW) application family used for grant and proposal management. The table stores information about a person's biosketch for a specific proposal, and this information is printed as part of the submitted proposal document. Each row represents one biosketch line associated with a proposal, with user-controllable attributes that determine whether the line is printed and the order in which it appears.

From a Data Vault modeling perspective, the object is classified heuristically as satellite-leaning. This suggests it functions primarily as a descriptive, context-bearing structure attached to a parent business key (the proposal–person combination), rather than as a standalone hub or an associative link. The satellite classification reflects the presence of descriptive attributes such as SHOW_FLAG and LINE_SEQUENCE that qualify and condition the core relationship rather than define new entities.

Key Information Stored

The table contains ten documented columns and is governed by the composite primary key IGW_PROP_PERSON_BIOSKETCH_PK, defined on (PROPOSAL_ID, PERSON_BIOSKETCH_ID). This pairing is also the sole unique index (IGW_PROP_PERSON_BIOSKETCH_U1), making it the definitive business-key candidate for the object.

  • PROPOSAL_ID (NUMBER, 15) — Proposal identifier; the first component of the composite primary key and the principal business-key anchor.
  • PERSON_BIOSKETCH_ID (NUMBER, 10) — Person biosketch line identifier; second component of the primary key and a foreign key to IGW_PERSON_BIOSKETCH.
  • SHOW_FLAG (VARCHAR2) — Indicates whether the biosketch line is printed in the proposal; documented values are Y and N.
  • LINE_SEQUENCE (NUMBER) — Controls the ordering of the biosketch line within the proposal; the default sequence can be changed by the user.
  • RECORD_VERSION_NUMBER (NUMBER) — Locking sequence number supporting optimistic concurrency control.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO/audit columns recording creation and modification metadata.

The composite nature of the primary key distinguishes the surrogate identifier from the business-key candidate; in this object they coincide, as both columns are required to uniquely identify a row.

Common Use Cases and Queries

Typical reporting scenarios include producing the printed biosketch section of a proposal, auditing which lines are suppressed, and reordering biosketch content before submission. The SHOW_FLAG filter controls inclusion, while LINE_SEQUENCE defines presentation order.

The documented extraction pattern is:

  • SELECT PROPOSAL_ID, PERSON_BIOSKETCH_ID, SHOW_FLAG, LINE_SEQUENCE, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, RECORD_VERSION_NUMBER FROM IGW.IGW_PROP_PERSON_BIOSKETCH;
  • Filter for printable lines: WHERE SHOW_FLAG = 'Y'.
  • Order presentation: ORDER BY LINE_SEQUENCE.
  • Isolate a proposal's content: WHERE PROPOSAL_ID = :proposal_id.

These patterns support canned reports, concurrent programs generating proposal documents, and validation queries confirming that all desired biosketch lines are flagged for printing.

Related Objects

  • IGW.IGW_PERSON_BIOSKETCH — Parent table referenced via PERSON_BIOSKETCH_ID; supplies the underlying biosketch definition.
  • IGW.IGW_PROP_PERSON_BIOSKETCH (APPS synonym/view) — The APPS-layer object referencing this table for application-level access.
  • Proposal master tables (IGW_PROPOSALS and related) — Linked through PROPOSAL_ID, though the metadata does not document an explicit FK constraint on this column.

Note that the ETRM metadata states this table references only IGW_PERSON_BIOSKETCH and does not itself reference any other database object; dependencies are therefore narrow and centered on the biosketch and proposal domains.