Results for “igf_sl_rs_resp_dtls”

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

Overview

IGF_SL_RS_RESP_DTLS is a table owned by the IGF schema (Financial Aid product family) in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its documented purpose is to store the Reporting School Tag Response Elements parsed from an inbound response XML file exchanged with the federal financial aid processing infrastructure. In practice this is a child/detail table that captures the granular elements returned for a reporting-school response, keyed at the response level by REP_SCHL_RESP_ID.

Applying a Data Vault classification heuristic against the documented foreign-key structure yields a satellite-leaning classification. The table is descriptive rather than an independent business entity: its primary key is a surrogate response identifier (REP_SCHL_RESP_ID) that links back to a broader response structure, and one of its business columns (DOCUMENT_ID_TXT) participates in the foreign-key relationship. The modeling suggestion is therefore to treat IGF_SL_RS_RESP_DTLS as a satellite/detail table hanging beneath the parent response hub, holding attribute values extracted from the XML payload, rather than as a standalone hub.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• REP_SCHL_RESP_ID — the primary key column (IGF_SL_RS_RESP_DTLS_PK). It is the surrogate identifier for a reporting-school response row and the principal join key to parent records.
• DOCUMENT_ID_TXT — a text column carrying the document identifier and the documented foreign-key column that references IGF_SL_CR_RESP_DTLS. This ties the response detail to the corresponding Common Record response data.
• REP_ENTITY_ID_TXT — a text identifier for the reporting entity, i.e., the school or reporting organization associated with the response element.
• RESP_CODE — the response code value returned in the XML payload, used to interpret the outcome of the reporting-school tag.
• CREATED_BY, CREATION_DATE — standard Oracle EBS who-columns capturing the user and timestamp of initial row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording the last modifying user, timestamp, and login session.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — the standard concurrent-program audit set identifying which application, program, and concurrent request last populated or updated the row.

The only unique index documented is IGF_SL_RS_RESP_DTLS_PK (REP_SCHL_RESP_ID), so REP_SCHL_RESP_ID is both the physical primary key and the sole documented business-key candidate. No other unique constraint is recorded in the metadata.

Common Use Cases and Queries

Typical usage centers on troubleshooting and reconciling inbound federal aid responses. Practitioners query this table to confirm that response elements were parsed and persisted correctly, to trace a specific document back to its Common Record response, and to audit which concurrent request loaded the data.

A representative join against the parent Common Record response detail table:

SELECT r.REP_SCHL_RESP_ID, r.DOCUMENT_ID_TXT,
       r.REP_ENTITY_ID_TXT, r.RESP_CODE,
       r.LAST_UPDATE_DATE, r.REQUEST_ID
FROM   IGF.IGF_SL_RS_RESP_DTLS r,
       IGF.IGF_SL_CR_RESP_DTLS c
WHERE  r.DOCUMENT_ID_TXT = c.DOCUMENT_ID_TXT;

To audit a specific load batch by concurrent request:

SELECT REP_SCHL_RESP_ID, DOCUMENT_ID_TXT, RESP_CODE, PROGRAM_ID
FROM   IGF.IGF_SL_RS_RESP_DTLS
WHERE  REQUEST_ID = :request_id;

Reporting use cases include error analysis by RESP_CODE, volume tracking of reporting-school responses by entity (REP_ENTITY_ID_TXT), and reconciliation of response counts against the originating Common Record response set. Because the table is a detail/satellite structure, summation or aggregation should always be grouped by the parent response or document identifier.

Related Objects

The relationship data identifies the following significant associations:

• IGF_SL_CR_RESP_DTLS — the documented foreign-key parent. The join is IGF_SL_RS_RESP_DTLS.DOCUMENT_ID_TXT → IGF_SL_CR_RESP_DTLS.DOCUMENT_ID_TXT. This is the principal related table, holding Common Record response detail against which reporting-school response elements are matched.
• IGF_SL_RS_RESP_DTLS_PK — the primary-key unique index on REP_SCHL_RESP_ID, enforcing row uniqueness and supporting parent lookups by response identifier.

The parent response header implied by REP_SCHL_RESP_ID (the reporting-school response entity above these details) is the natural upward relationship and should be consulted when reconstructing a complete response. Inbound XML processing, the concurrent programs referenced through PROGRAM_ID and REQUEST_ID, and any Financial Aid response-inquiry forms or concurrent reports that display reporting-school tag outcomes all depend on this table. Direct DML is not recommended; data is populated programmatically by the response-parsing process, and the standard who-columns and request-audit columns should be preserved to maintain traceability of every loaded payload.