Search Results attending_pell_cd

Overview

IGF.IGF_GR_ATTEND_PELL is an Oracle E-Business Suite table in the IGF (Financial Aid / Student Financials) schema that stores the Attending Pell identifiers associated with an organization. It is a child data object in the financial aid grant (Pell) subsystem, capturing the relationship between a reporting Pell entity and the attending Pell campus record, qualified by calendar context. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_TX_DATA tablespace, carries FND Design Data registration IGF.IGF_GR_ATTEND_PELL, and is documented as VALID.

Under the heuristic Data Vault classification mined from its foreign key structure, this object is best modeled as a link: it resolves a many-to-many style association between a reporting Pell record (RCAMPUS_ID) and an attending campus or entity (ACAMPUS_ID / ATD_ENTITY_ID_TXT), with the calendar instance columns acting as the qualifying grain. It is not a descriptive hub; the descriptive payload of the Pell identifiers themselves is comparatively thin. Treat this classification as a modeling suggestion rather than a normative design rule.

Key Information Stored

The unique primary key is IGF_GR_ATTEND_PELL_PK, defined on ACAMPUS_ID, which holds the unique identifier for the Attending Pell record. ACAMPUS_ID is a surrogate key rather than a business identifier, and the table exposes no additional unique index that would qualify as a business-key candidate beyond this primary key.

• ACAMPUS_ID — surrogate primary key for the attending Pell record.
• RCAMPUS_ID — foreign key to IGF_GR_REPORT_PELL identifying the reporting Pell record this row is associated with.
• CI_CAL_TYPE — calendar type name (VARCHAR2(10)) establishing the academic calendar context.
• CI_SEQUENCE_NUMBER — unique identifier of the calendar instance, forming the second half of the calendar context.
• ATTENDING_PELL_CD — the attending Pell identifier (VARCHAR2(30)), the value most commonly sought when users search on attending_pell_cd.
• OPE_CD — the OPE (Office of Postsecondary Education) identifier of the organization, VARCHAR2(20).
• ATD_ENTITY_ID_TXT — text representation of the attending entity ID, captured as a string rather than a numeric key.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns applied to transactional tables in the APPS schema.

Three non-unique indexes support retrieval: IGF_GR_ATTEND_PELL_N1 on RCAMPUS_ID, IGF_GR_ATTEND_PELL_N2 on (CI_CAL_TYPE, CI_SEQUENCE_NUMBER, ATTENDING_PELL_CD), and IGF_GR_ATTEND_PELL_N3 on (CI_CAL_TYPE, CI_SEQUENCE_NUMBER, ATD_ENTITY_ID_TXT). These index definitions signal the access paths the application expects: lookup by reporting campus, by calendar plus attending Pell code, and by calendar plus attending entity.

Common Use Cases and Queries

The most frequent reporting need is resolving a Pell code to the organization, calendar instance, and reporting entity it belongs to. Because IGF_GR_ATTEND_PELL_N2 leads with ATTENDING_PELL_CD, filtering directly on that column is index-supported:

SELECT a.acampus_id,
       a.rcampus_id,
       a.ci_cal_type,
       a.ci_sequence_number,
       a.attending_pell_cd,
       a.ope_cd,
       a.atd_entity_id_txt
FROM   igf.igf_gr_attend_pell a
WHERE  a.attending_pell_cd = :p_pell_cd;

Reporting by calendar period uses the same leading columns and is efficient via N2 or N3:

SELECT a.ci_cal_type,
       a.ci_sequence_number,
       a.attending_pell_cd,
       a.atd_entity_id_txt
FROM   igf.igf_gr_attend_pell a
WHERE  a.ci_cal_type = :p_cal_type
AND    a.ci_sequence_number = :p_seq;

Additional scenarios include reconciling attending Pell assignments against the parent reporting Pell definition, auditing which entities carry a given OPE code in a calendar instance, and validating that every reporting campus (RCAMPUS_ID) has at least one attending record. Senior technical staff should note that direct DML against IGF tables is discouraged; changes should flow through the financial aid application or its concurrent processes.

Related Objects

The dependency metadata documents one outbound foreign key and one inbound reference. The outbound relationship is the significant one for join design.

• IGF.IGF_GR_REPORT_PELL — parent of the RCAMPUS_ID foreign key; join attend.rcampus_id = report_pell.rcampus_id (using the reporting Pell table's corresponding key column) to obtain reporting-level attributes.
• APPS.IGF_GR_ATTEND_PELL — the APPS synonym or view layer exposing the IGF table to application code and reports; query this name when running from an APPS session.
• Calendar instance objects in the IGF/FND calendar family — reached via CI_CAL_TYPE and CI_SEQUENCE_NUMBER to describe the academic period.
• Organization and campus reference objects referenced by ACAMPUS_ID, RCAMPUS_ID, and ATD_ENTITY_ID_TXT for entity descriptions.

The table does not reference any other database object directly, and the FK structure confirms it is a leaf-level association table. All access should respect the documented column list of twelve attributes rather than assuming additional columns exist in earlier releases.