Results for “igf_ap_st_corr_text”

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

Overview

The IGF_AP_ST_CORR_TEXT table is a component of the Oracle E-Business Suite IGF (Financial Aid) module, which is documented as obsolete in release 12.1.1 and 12.2.2. The table stores custom correspondence text associated with individual students, providing a repository for free-form or template-driven letter content generated during financial aid processing. Its role in Oracle EBS is to persist the textual body of student-specific correspondence so that letters and notices can be reproduced, audited, or reprinted independently of the runtime process that originally produced them.

Under the heuristic Data Vault classification supplied in the ETRM metadata, this object is described as satellite-leaning. In modeling terms, this suggests the table behaves as a descriptive satellite attached to a parent business entity rather than as an independent hub or an associative link. The parent entity is represented by the foreign key to IGF_AP_FA_BASE_REC_ALL, which supplies the financial aid base record identity. The correspondence text table therefore carries context and descriptive attributes keyed to an existing business key held elsewhere.

Key Information Stored

The documented physical schema contains ten columns. The most significant are as follows:

• CORSP_ID — the surrogate primary key, enforced through the unique index IGF_AP_ST_CORR_TEXT_PK and additionally through IGF_AP_ST_CORR_TEXT_U1, which makes it both the technical identifier and the sole documented business-key candidate.
• BASE_ID — the foreign key referencing IGF_AP_FA_BASE_REC_ALL, tying each correspondence record to its financial aid base record.
• CUSTOM_TEXT — the primary payload column, holding the custom correspondence content for the student.
• RUN_DATE — the date associated with the correspondence run or generation event.
• ACTIVE — a status flag indicating whether the correspondence record is currently in effect.

The remaining columns are the standard Oracle EBS audit attributes: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These provide who-audit and when-audit traceability consistent with the conventional EBS column set.

Common Use Cases and Queries

Typical use is retrieval and reprinting of stored student correspondence, auditing of what text was produced for a given base record, and reporting on correspondence activity within a date range. A common pattern joins correspondence text to the parent base record:

• SELECT t.CORSP_ID, t.BASE_ID, t.CUSTOM_TEXT, t.RUN_DATE FROM IGF.IGF_AP_ST_CORR_TEXT t WHERE t.BASE_ID = :base_id AND t.ACTIVE = 'Y';
• SELECT COUNT(*) FROM IGF.IGF_AP_ST_CORR_TEXT WHERE RUN_DATE BETWEEN :from_date AND :to_date;
• Join to IGF_AP_FA_BASE_REC_ALL on BASE_ID to enrich correspondence text with the parent financial aid record attributes for reporting extracts.

Because the module is obsolete and the table is not implemented in the reference database, any SQL against it should be validated against the target instance before deployment.

Related Objects

The FK metadata identifies one referenced object, and its dominance reflects the satellite-style relationship:

• IGF_AP_FA_BASE_REC_ALL — referenced through IGF_AP_ST_CORR_TEXT.BASE_ID; the parent financial aid base record table.

The table's own primary key IGF_AP_ST_CORR_TEXT_PK and unique index IGF_AP_ST_CORR_TEXT_U1 govern row identity on CORSP_ID and constrain downstream references. Any dependent child tables or concurrent programs that consume correspondence text would resolve through CORSP_ID and BASE_ID respectively.