Search Results igf_sl_as_resp_dtls




Overview
Explore in AI Chat

Overview

IGF_SL_AS_RESP_DTLS is a transaction-detail table within the IGF (Financial Aid) product family of Oracle E-Business Suite, owned by the IGF schema. Its documented purpose is to store the Attending School Tag Response Elements parsed from the response XML file exchanged during the Title IV student loan and grant processing lifecycle. In practical terms, the table captures the attendee-side (school) response payload returned by the Common Origination and Disbursement (COD) processing flow, complementing the state-level and result-level records held in adjacent IGF tables.

The heuristic Data Vault classification for this object is hub-leaning. Within a Data Vault 2.0 modeling convention, this suggests the table behaves primarily as a hub that anchors a durable business key (ATD_SCHL_RESP_ID) and is referenced by satellites and downstream detail tables. Modelers designing a warehouse layer over EBS should treat ATD_SCHL_RESP_ID as the stable grain and expect the surrounding descriptive attributes to be sourced from dependent structures.

Key Information Stored

The table carries 13 documented columns. The surrogate primary key is ATD_SCHL_RESP_ID, enforced by the unique index IGF_SL_AS_RESP_DTLS_PK. This same column is the sole documented business-key candidate, which means the identifier is both the technical and the natural anchor for joins.

  • ATD_SCHL_RESP_ID — Primary key and unique index column; the attending-school response identifier.
  • REP_SCHL_RESP_ID — Foreign key column linking to the reporting-school response context; documented as an FK reference.
  • ATD_ENTITY_ID_TXT — Textual identifier of the attending entity, typically the school or institution code returned in the response XML.
  • RESP_CODE — Response code indicating the disposition of the attending school tag.
  • CREATED_BY, CREATION_DATE — Who-created audit columns populated by EBS.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Who-updated audit columns, including the login context.
  • PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrent program context columns identifying the requesting application, the concurrent program, its update timestamp, and the specific request ID that loaded or modified the row.

The PROGRAM_* and REQUEST_ID columns are particularly valuable for tracing data lineages back to a specific concurrent request run.

Common Use Cases and Queries

Typical reporting scenarios include reconciliation of attending-school responses against reporting-school submissions, audit of response codes for a given request, and diagnosis of XML load failures by joining request context back to the concurrent manager.

A representative pattern joins the detail table to the state-level response table:

  • SELECT d.ATD_SCHL_RESP_ID, d.RESP_CODE, s.ATD_SCHL_RESP_ID FROM IGF.IGF_SL_AS_RESP_DTLS d JOIN IGF.IGF_SL_ST_RESP_DTLS s ON s.ATD_SCHL_RESP_ID = d.ATD_SCHL_RESP_ID
  • Filtering by d.REQUEST_ID isolates records loaded by a single concurrent request; filtering by d.CREATION_DATE supports daily or batch-level extracts.
  • Joining to IGF_SL_ED_PRC_RSLTS on EDIT_ID provides the edit-result context for validation reporting.

Extracts designed for downstream COD reconciliation typically select ATD_ENTITY_ID_TXT and RESP_CODE as the reporting dimensions.

Related Objects

The following objects are the most significant documented relationships:

  • IGF_SL_ST_RESP_DTLS — Child of this table; FK via IGF_SL_ST_RESP_DTLS.ATD_SCHL_RESP_ID referencing this table's primary key.
  • IGF_SL_ED_PRC_RSLTS — References this table via EDIT_ID, carrying edit-processing outcomes.
  • IGF_SL_AS_RESP_DTLS.REP_SCHL_RESP_ID — Documented foreign key column that ties this record to the reporting-school response context.
  • IGF_SL_AS_RESP_DTLS_PK — The unique index enforcing the primary key.

Together these objects form the response-processing cluster within the IGF Financial Aid schema, where the attending-school response detail is the anchor point for state-level and edit-result records.