Search Results rcampus_id




Overview
Explore in AI Chat

Overview

The table IGF.IGF_GR_REPORT_PELL is a transaction data object within the Oracle E-Business Suite IGF schema, which supports the Student Systems and Financial Aid grant reporting functionality. As its internal documentation states, the table is the "entity holding reporting pell identifiers," meaning it stores the Pell Grant reporting identifiers and related organizational context required for federal Pell Grant reporting for higher-education institutions. Each row associates a campus or organization unit with the reporting Pell code, the calendar instance under which the award is reported, and the reporting entity identifier used to satisfy U.S. Department of Education reporting obligations.

In terms of Data Vault modeling heuristics derived from the foreign key structure, this object leans toward a satellite. Its primary key, RCAMPUS_ID, is a surrogate identifier, and the table's descriptive attributes (the reporting Pell code, OPE code, and reporting entity text) are the kind of contextual descriptors typically modeled as satellite attributes keyed to a parent hub. The dependency metadata confirms that the table references the Oracle Student System calendar instance table IGS_CA_INST_ALL, and that it is referenced by IGF_GR_ATTEND_PELL, reinforcing its role as a supporting satellite in the Pell reporting subject area.

Key Information Stored

The table contains eleven documented columns. The most significant include:

  • RCAMPUS_ID (NUMBER) — the surrogate primary key and unique identifier of a reporting Pell record. This is also the sole column in unique index IGF_GR_REPORT_PELL_U1, making it the business-key candidate in the physical schema.
  • CI_CAL_TYPE (VARCHAR2(10)) — the name of the calendar type used within the organization.
  • CI_SEQUENCE_NUMBER (NUMBER) — the unique identifier for the calendar instance, which together with CI_CAL_TYPE forms a foreign key to IGS_CA_INST_ALL.
  • REPORTING_PELL_CD (VARCHAR2(30)) — the reporting Pell identifier assigned to the organization unit; this is the column most frequently targeted by searches such as the user's reporting_pell_cd.
  • OPE_CD (VARCHAR2(20)) — the Office of Postsecondary Education (OPE) identifier of the organization.
  • REP_ENTITY_ID_TXT (VARCHAR2) — text indicating the reporting entity identifier.
  • Standard WHO audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Two non-unique indexes, IGF_GR_REPORT_PELL_N1 and IGF_GR_REPORT_PELL_N2, support retrieval by calendar context and either the reporting Pell code or reporting entity identifier, which reflects the most common query patterns.

Common Use Cases and Queries

Typical use cases include resolving the reporting Pell code for a given campus and reporting period, validating OPE codes against the Organization Unit, and joining attendance records to their reporting entity. A representative query joining calendar context is:

SELECT p.REPORTING_PELL_CD, p.OPE_CD, p.REP_ENTITY_ID_TXT
FROM IGF.IGF_GR_REPORT_PELL p
WHERE p.CI_CAL_TYPE = :cal_type
AND p.CI_SEQUENCE_NUMBER = :seq_num;

Another common pattern links the reporting entity to attendance records via RCAMPUS_ID:

SELECT a.*, p.REPORTING_PELL_CD
FROM IGF.IGF_GR_ATTEND_PELL a, IGF.IGF_GR_REPORT_PELL p
WHERE a.RCAMPUS_ID = p.RCAMPUS_ID;

Reporting use cases frequently filter on REPORTING_PELL_CD to aggregate Pell disbursements for federal submission, and on OPE_CD to reconcile institutional identifiers.

Related Objects

  • IGF.IGF_GR_ATTEND_PELL — references this table through the shared column RCAMPUS_ID; holds Pell attendance records.
  • IGS.IGS_CA_INST_ALL — parent calendar instance table referenced by CI_CAL_TYPE and CI_SEQUENCE_NUMBER.
  • APPS.IGF_GR_REPORT_PELL — the APPS synonym/view layer exposing the base table.
  • Organization unit and reporting entity definitions in the IGF schema that supply OPE_CD and OPE context.
  • Standard WHO audit columns link to FND_USER via CREATED_BY/LAST_UPDATED_BY for change tracking.

Because the object is VALID in the ETRM 12.1.1 schema and carries forward into 12.2.2, no delta migration concerns apply beyond standard tablespace and index management.