Results for “black_females”

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

Overview

IGW_PRPO_SUBJECT_INFO_V is a reporting view in the Oracle E-Business Suite Grants Proposal (IGW) module, owned by the APPS schema. It is classified as a VIEW object with VALID status and is documented in Oracle EBS releases 12.1.1 and 12.2.2. The view is designed to display details of human subjects involved in a proposal, presenting demographic information that is captured on study titles associated with a grant proposal. This allows sponsored programs offices, principal investigators, and compliance personnel to review the composition of proposed study populations directly from the database layer.

The view does not store data itself; it derives all of its output at runtime by invoking a server-side PL/SQL function, IGW_REPORT_PROCESSING.GET_SUBJECTS. Because of this function-based design, the view behaves as a computed reporting interface rather than a conventional join view. It surfaces aggregated subject counts broken out by gender and race/ethnicity categories, which aligns with the demographic data typically requested in human subjects research and institutional review board (IRB) reporting.

Underlying Base Objects

The view text selects from a single documented base table: IGW_STUDY_TITLES, aliased as ST. Every row in the view corresponds to a study title record, keyed by ST.PROPOSAL_ID and ST.STUDY_TITLE_ID. No additional base objects are documented in the ETRM metadata. All remaining columns are populated by repeated calls to IGW_REPORT_PROCESSING.GET_SUBJECTS, which accepts four arguments: the proposal identifier, the study title identifier, a subject category code, and a gender or grouping indicator. The function returns the count of subjects for that category and grouping.

Because the view depends on this function, its performance and correctness are tied to the logic inside IGW_REPORT_PROCESSING. Organizations extending or troubleshooting the view should inspect that package body. The view is also read-only in practice; no DML is supported against it.

Key Columns

• PROPOSAL_ID — Identifier of the grant proposal to which the study title belongs.
• STUDY_TITLE — The descriptive title of the human subjects study.
• AMERICAN_INDIAN_FEMALES, ASIAN_FEMALES, BLACK_FEMALES, HISPANIC_FEMALES, WHITE_FEMALES, OTHER_FEMALES — Female subject counts by the six reported race/ethnicity categories.
• AMERICAN_INDIAN_MALES, ASIAN_MALES, BLACK_MALES, HISPANIC_MALES, WHITE_MALES, OTHER_MALES — Corresponding male subject counts.

Each demographic column is produced by a distinct GET_SUBJECTS call using category codes 1 through 6 and grouping values 1 (females) and 2 (males).

Common Use Cases and Queries

Typical uses include proposal demographic reporting, IRB submission preparation, and reconciliation of subject counts across studies. A basic query lists all subject information for a proposal:

• SELECT proposal_id, study_title, american_indian_females, asian_females, black_females, hispanic_females, white_females, other_females, american_indian_males, asian_males, black_males, hispanic_males, white_males, other_males FROM igw_prpo_subject_info_v WHERE proposal_id = :p_proposal_id;

Because the demographic columns are function-generated, filtering or aggregating on them in large reports may incur performance overhead. Restricting queries by PROPOSAL_ID is recommended. The view is suitable for use in custom concurrent programs, BI Publisher data templates, and ad hoc SQL, but it should not be relied upon for transactional processing.