Search Results igf_ap_li_css_ints_pk

Overview

IGF_AP_LI_CSS_INTS is an interface (staging) table in the IGF — Financial Aid product schema of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. Its documented description is "Interface table for Profile." Operationally, it holds inbound CSS Profile records — the institutional methodology financial aid application data collected by the College Scholarship Service — prior to validation, computation, and posting into the permanent financial aid tables. Records arrive via a batch load process, are keyed to a batch identifier, and carry an import status that governs whether each row has been staged, processed, or rejected.

The table is extremely wide, with 719 documented columns. This is characteristic of a flat interface staging structure that mirrors a paper/electronic form layout, in which repeating data groups (schools, household members, question-and-answer blocks) are flattened into numbered column families rather than normalized child rows.

Under the heuristic Data Vault classification derived from the foreign key structure, this object is satellite-leaning. It chiefly carries descriptive attributes tied to a parent batch key, rather than acting as a hub of independent business entities. This is a modeling suggestion only; in EBS terms the table functions as a conventional staging interface driven by a concurrent program and the standard interface control columns.

Key Information Stored

The documented surrogate primary key is CSSINT_ID, enforced by the unique index IGF_AP_LI_CSS_INTS_PK. This is the single documented unique index on the table, so no separate business-key unique constraint is recorded in the ETRM metadata; candidate business identifiers such as CSS_ID_NUMBER_TXT, PERSON_NUMBER, and BATCH_NUM are not constrained as unique at the database level. BATCH_NUM is documented as the foreign key to IGF_AP_LI_BAT_INTS.

• CSSINT_ID — surrogate primary key of the interface row.
• BATCH_NUM — foreign key linking the row to its controlling batch in IGF_AP_LI_BAT_INTS.
• PERSON_NUMBER — student identifier used to match the incoming record to an existing person.
• COLLEGE_CD and ACADEMIC_YEAR_TXT — institutional and award-year context for the application.
• STU_RECORD_TYPE and CSS_ID_NUMBER_TXT — application record classification and the CSS-assigned identifier.
• APPLICATION_RECEIPT_DATE and REGISTRATION_RECEIPT_DATE — key processing milestones on the source form.
• LAST_NAME, FIRST_NAME, MIDDLE_INITIAL_TXT, SOCIAL_SECURITY_NUM — student demographic data used for matching and audit.
• IMPORT_STATUS_TYPE — the interface processing status used to control selection of rows for load.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — standard concurrent program request traceability columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• FNAR_MESSAGE_*_FLAG — a large family of message indicator flags recording exceptions raised during need-analysis processing.
• IM_P_BAS_*, IM_S_BAS_*, FM_P_*, FM_S_* — computed institutional methodology and federal methodology figures for parent and student.
• ASSUMPTION_MESSAGE_*_FLAG and OPTION_* columns — data-assumption notices and processing options associated with the record.

Common Use Cases and Queries

The dominant use case is monitoring and troubleshooting the CSS Profile interface load. Operational staff query rows by batch and status to determine which records are pending, loaded, or in error.

• Batch status review: SELECT IMPORT_STATUS_TYPE, COUNT(*) FROM IGF.IGF_AP_LI_CSS_INTS WHERE BATCH_NUM = :batch GROUP BY IMPORT_STATUS_TYPE;
• Locating a student's staged record for reconciliation: SELECT CSSINT_ID, BATCH_NUM, PERSON_NUMBER, APPLICATION_RECEIPT_DATE, IMPORT_STATUS_TYPE FROM IGF.IGF_AP_LI_CSS_INTS WHERE PERSON_NUMBER = :person_number;
• Tracing a load run back to its concurrent request: filter on REQUEST_ID and PROGRAM_ID to identify the program that created the rows.
• Exception reporting on need-analysis messages: aggregate the FNAR_MESSAGE_*_FLAG columns to identify records requiring manual review.
• Audit and retention queries using CREATION_DATE and LAST_UPDATE_DATE to isolate rows from a given processing window.

Because the table is a staging interface, reporting is normally directed at the downstream permanent tables after load; queries here are principally diagnostic. Any direct DML should be treated carefully, as rows are purged or reloaded by the interface program on subsequent runs.

Related Objects

• IGF_AP_LI_BAT_INTS — the batch header table. Joined on IGF_AP_LI_CSS_INTS.BATCH_NUM = IGF_AP_LI_BAT_INTS.BATCH_NUM. This is the only documented foreign key relationship and identifies the parent of each Profile interface row.
• IGF_AP_LI_CSS_INTS_PK — the unique index on CSSINT_ID that enforces row uniqueness and supports primary key lookups.
• FND_CONCURRENT_REQUESTS — referenced indirectly through REQUEST_ID and PROGRAM_ID for load-run traceability.
• FND_APPLICATION / FND_PROGRAM — resolve PROGRAM_APPLICATION_ID and PROGRAM_ID to the interface concurrent program.
• PER_ALL_PEOPLE_F — used to resolve PERSON_NUMBER to a person record during and after load.
• IGF_AP_LI_* profile staging peers — sibling interface tables loaded by the same financial aid batch framework, useful when reconciling a complete submission.
• Downstream IGF need-analysis tables — the permanent institutional methodology and federal methodology result tables to which validated rows are posted after processing.