Search Results ap_att_code




Overview
Explore in AI Chat

Overview

IGF_AP_ATTEND_MAP_ALL is a Financial Aid (IGF) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the mapping between Attendance Types defined by the institution in Oracle Student System (OSS) and the standardized Attendance Types required by the Financial Aid processing engine for Pell Grants, FFELP Loans, and Application Processing. In effect, the table translates institution-specific attendance or enrollment status values into the codes that the federal aid subsystems recognize.

The object resides in the IGF schema and is documented as VALID with 13 columns. Under a heuristic Data Vault classification mined from its foreign key structure, the table is satellite-leaning: its primary key ATM_ID identifies individual rows, while the descriptive attributes (attendance mapping codes and context identifiers) describe a referenced entity. This is a modeling suggestion only; in native EBS terms the table functions as a multi-organization (ALL-suffixed) setup and mapping entity. The _ALL suffix and the presence of ORG_ID indicate that rows are partitioned by operating unit, so mappings can differ across organizations.

Key Information Stored

The table's structure centers on surrogate identification, business-key uniqueness, and three federal attendance code mappings.

The business-key candidate is defined by unique index IGF_AP_ATTEND_MAP_ALL_U2 over ATTENDANCE_TYPE, ORG_ID, CAL_TYPE, and SEQUENCE_NUMBER, meaning an attendance type may only be mapped once per operating unit and calendar instance/sequence combination. The three *_ATT_CODE columns hold the destination side of the mapping; ATTENDANCE_TYPE holds the source side.

Common Use Cases and Queries

The primary use case is validating and maintaining the translation between institutional attendance codes and federal aid attendance codes. Financial Aid administrators query the table to confirm how a given OSS attendance type will be interpreted for each aid program, and to troubleshoot mismatches that cause incorrect enrollment status reporting.

SELECT atm.attendance_type,
       atm.pell_att_code,
       atm.cl_att_code,
       atm.ap_att_code,
       atm.cal_type,
       atm.sequence_number
FROM   igf.igf_ap_attend_map_all atm
WHERE  atm.org_id = :p_org_id
ORDER  BY atm.attendance_type;

A second pattern joins to the calendar instance to resolve calendar context for reporting:

SELECT atm.attendance_type,
       atm.pell_att_code,
       ci.cal_type
FROM   igf.igf_ap_attend_map_all atm,
       igs_ca_inst_all ci
WHERE  atm.cal_type = ci.cal_type
AND    atm.sequence_number = ci.sequence_number
AND    atm.org_id = :p_org_id;

Typical reporting scenarios include auditing the completeness of federal attendance mappings before a disbursement cycle and comparing institution-defined attendance categories against the three federal code columns to detect unmapped or duplicated configurations.

Related Objects

The following objects are most significant in relation to this table.

  • IGS_CA_INST_ALL — Referenced by the foreign key on CAL_TYPE and SEQUENCE_NUMBER. This is the calendar instance table that supplies the academic calendar context for each mapping row and is the only documented foreign key target.
  • IGF_AP_ATTEND_MAP_ALL_PK / IGF_AP_ATTEND_MAP_ALL_U1 — Primary key and unique index on ATM_ID that enforce row identity.
  • IGF_AP_ATTEND_MAP_ALL_U2 — Unique index over ATTENDANCE_TYPE, ORG_ID, CAL_TYPE, SEQUENCE_NUMBER that enforces the business key.
  • IGF Financial Aid attendance and enrollment processes — The Pell Grant, FFELP Loan, and Application Processing routines consume the *_ATT_CODE values to determine enrollment status for federal aid.
  • OSS attendance type setup — The source definitions for ATTENDANCE_TYPE originate from the institution's Student System attendance configuration and must exist before mapping rows are created.
  • ORG_ID / operating unit configuration — Determines row visibility and partitioning across organizations.

Because the table is a multi-org configuration entity, maintenance should be performed through the supported Financial Aid setup forms rather than by direct DML, ensuring ORG_ID and audit columns remain consistent with the surrounding IGF configuration.