Results for “stu_record_type”

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

Overview

IGF_AP_LI_CSS_ACT_INTS is an interface (staging) table in the IGF – Financial Aid product family of Oracle E-Business Suite, owned by the IGF schema. Its documented description is "Interface table for Active Profiles." It serves as the landing area into which Active Profile records are loaded before validation and absorption into the core Financial Aid data model. In both Oracle EBS 12.1.1 and 12.2.2 the object is documented as VALID with a physical footprint of 17 columns and one unique index.

The table is structured as a batch-oriented interface: every row carries a BATCH_NUM that ties it back to a parent batch header, allowing a set of inbound rows to be grouped, validated, and purged as a unit. Because each row also references external business identifiers such as CI_ALTERNATE_CODE, PERSON_NUMBER, and CSS_ID_NUMBER_TXT, the table functions as the boundary between external College Scholarship Service (CSS) / Institutional Methodology source files and the internal Financial Aid repository.

The supplied metadata classifies the relationship profile as "satellite-leaning." In Data Vault terms this is a modeling suggestion rather than a physical designation: the object behaves as a descriptive satellite, holding attribute detail keyed to a batch/link parent, with a single-column surrogate primary key (CSAINT_ID) rather than a composite natural hub key.

Key Information Stored

• CSAINT_ID — surrogate primary key, enforced by the unique index IGF_AP_LI_CSS_ACT_INTS_PK. This is the only documented unique business-key candidate, so downstream processing should treat it as the row-level identifier.
• BATCH_NUM — foreign key to IGF_AP_LI_BAT_INTS; identifies the batch that owns the row and is the principal grouping and purge key.
• CI_ALTERNATE_CODE — alternate institutional identifier for the incoming record.
• PERSON_NUMBER — the student/applicant person number used to match the staged record to a party.
• CSS_ID_NUMBER_TXT — the CSS identifier carried in text form.
• ACADEMIC_YEAR_TXT — the academic year to which the Active Profile applies.
• STU_RECORD_TYPE — classifies the student record being imported.
• IMPORT_STATUS_TYPE — the current validation/import disposition of the staged row.
• PROGRAM_APPLICATION_ID / PROGRAM_ID — the program context associated with the record.
• PROGRAM_UPDATE_DATE — the effective update date reported by the source program.
• REQUEST_ID, PROGRAM_APPLICATION_ID — concurrent request identifiers enabling traceability back to the submitting run.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical usage centers on inbound concurrency processing, reconciliation, and error resolution. A common reconciliation query joins the interface rows to the batch header:

SELECT i.CSAINT_ID, i.BATCH_NUM, i.PERSON_NUMBER,
       i.STU_RECORD_TYPE, i.IMPORT_STATUS_TYPE
FROM   IGF.IGF_AP_LI_CSS_ACT_INTS i,
       IGF.IGF_AP_LI_BAT_INTS b
WHERE  i.BATCH_NUM = b.BATCH_NUM
AND    i.IMPORT_STATUS_TYPE = 'ERROR';

Support teams also profile a batch by year and request:

SELECT ACADEMIC_YEAR_TXT, IMPORT_STATUS_TYPE, COUNT(*)
FROM   IGF.IGF_AP_LI_CSS_ACT_INTS
WHERE  BATCH_NUM = :batch AND REQUEST_ID = :request_id
GROUP  BY ACADEMIC_YEAR_TXT, IMPORT_STATUS_TYPE;

Reporting use cases include batch success/failure trending, duplicate detection on PERSON_NUMBER plus ACADEMIC_YEAR_TXT, and auditing which program applications were refreshed by a given request.

Related Objects

• IGF_AP_LI_BAT_INTS — parent batch table; joined on IGF_AP_LI_CSS_ACT_INTS.BATCH_NUM = IGF_AP_LI_BAT_INTS.BATCH_NUM.
• IGF_AP_LI_CSS_ACT_INTS_PK — unique index on CSAINT_ID.
• IGF_AP_LI_BAT_INTS_PK — the batch header key referenced by the foreign key.
• Concurrent program and request metadata in FND_CONCURRENT_REQUESTS, correlated through REQUEST_ID.
• Financial Aid person and program entities resolved via PERSON_NUMBER and PROGRAM_ID during the import step.

No additional dependent views or PL/SQL APIs are documented in the supplied metadata; any such dependencies should be confirmed against the production data dictionary for the specific release.