Search Results revision_fnar_compute_date




Overview
Explore in AI Chat

Overview

APPS.IGF_AP_CSS_PROFILE is a reporting view within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 Financial Aid module. The IGF prefix identifies objects belonging to the Oracle Student Financial Aid / Institutional Financial Aid (IGF) product family. This view exposes College Scholarship Service (CSS) Profile data — the standardized financial aid application dataset collected by the College Board and historically consumed by higher-education institutions to determine a student's expected family contribution and eligibility for institutional need-based aid.

Functionally, the view acts as a flattened, read-only projection of an underlying CSS Profile staging or detail table. It surfaces institutional identifiers, student biographical detail, household and dependency information, and the full spectrum of parental and student income, asset, and expense data reported on the CSS Profile form. Because views in the APPS schema are granted to the APPS database account, they are accessible to concurrent programs, BI Publisher report definitions, Oracle Reports, and custom PL/SQL or SQL integrations without requiring direct table grants. The view therefore serves as the supported integration surface between EBS Financial Aid and downstream reporting, packaging, and analytics processes.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view, and the view text is presented as a straightforward SELECT of named columns (plus the pseudo-column ROWID aliased as row_id) from a single source. The inclusion of ROWID is a common EBS convention that allows consumers to uniquely identify each row for update-processing, de-duplication, or error reporting even when no explicit primary key is exposed.

Based on the naming convention, the view is almost certainly defined over a table such as IGF_AP_CSS_PROFILE or a closely related CSS Profile staging entity. Within students who submit CSS Profile data to an institution, the underlying record is keyed by CSSP_ID and associated to the student's record through CSS_ID_NUMBER, and to the institution or campus through ORG_ID and BASE_ID. Because no join is documented, the view should be treated as a single-table projection rather than a composite. Implementers should confirm the exact base table in their installation via USER_/ALL_DEPENDENCIES or DBMS_METADATA before writing code that assumes a join path.

Key Columns

The columns fall into several logical groupings:

Common Use Cases and Queries

The view is typically queried for packaging and needs-analysis reporting, verification audits, and electronic extract reconciliation. A representative query isolating investment assets for a given aid year follows:

  • Investment asset lookup: SELECT cssp_id, css_id_number, last_name, first_name, invest_value, invest_debt, cash_sav_check FROM apps.igf_ap_css_profile WHERE academic_year = :p_year AND org_id = :p_org AND invest_value > 0;
  • Active profiles by institution and college code: SELECT college_code, css_id_number, academic_year FROM apps.igf_ap_css_profile WHERE active_profile = 'Y' AND college_code = :p_college;
  • Extract reconciliation: SELECT cssp_id, electronic_extract_date, institutional_reporting_type FROM apps.igf_ap_css_profile WHERE electronic_extract_date BETWEEN :p_from AND :p_to;
  • Asset summary for needs analysis: SELECT cssp_id, cash_sav_check, invest_value, home_value, bus_farm_value FROM apps.igf_ap_css_profile WHERE academic_year = :p_year;

Because the view exposes individual SSN, date-of-birth, and detailed financial data, queries should be restricted by institution (ORG_ID or BASE_ID) and academic year, and access should be governed by the institution's data-privacy controls (FERPA and equivalent regulations). Always confirm the view definition against your specific EBS patch level before relying on column semantics.