Search Results resp_code

Overview

IGF.IGF_SL_RS_RESP_DTLS is a transactional table in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment, owned by the IGF schema. It stores the Reporting School Tag Response Elements parsed from a response XML file exchanged with student lending and reporting-school data flows. The table captures the discrete response elements returned by reporting schools and associates each response with the originating document and reporting entity, making it a repository of inbound response detail records rather than a configuration or setup object.

In Data Vault terms, the object is classified as satellite-leaning based on its foreign-key structure. This design recommendation reflects that the table primarily carries contextual, descriptive attributes tied to a parent response transaction—such as the response code, document identifier, and reporting entity identifier—rather than acting as a pure hub of distinct business keys or a many-to-many link between hubs. The full qualified name is IGF.IGF_SL_RS_RESP_DTLS, and its physical storage resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, while its unique index lives in APPS_TS_TX_IDX.

Key Information Stored

The table has thirteen documented columns. The most significant are:

• REP_SCHL_RESP_ID — A NUMBER column that serves as the surrogate primary key, enforced by the unique index IGF_SL_RS_RESP_DTLS_PK. It identifies each reporting school response record.
• DOCUMENT_ID_TXT — VARCHAR2(30); the document ID of the document that reported this reporting school tag. It also participates in a foreign-key relationship to IGF_SL_CR_RESP_DTLS.
• REP_ENTITY_ID_TXT — VARCHAR2(30); the Entity ID of the reporting school.
• RESP_CODE — VARCHAR2(30); the response code returned for the reporting school tag. This is the column most frequently selected when users search for "resp_code," since it holds the classification or disposition value returned by the reporting institution.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns recording the audit trail of row creation and modification.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Standard concurrent program and request columns identifying the process that last touched the row.

The unique index IGF_SL_RS_RESP_DTLS_PK on REP_SCHL_RESP_ID establishes the documented business-key candidate for row-level identification.

Common Use Cases and Queries

Because the table retains parsed response elements, it is commonly queried to validate, audit, or report on the outcomes returned by reporting schools. A frequent pattern filters by RESP_CODE to isolate specific response dispositions:

• Response code analysis: SELECT REP_SCHL_RESP_ID, DOCUMENT_ID_TXT, REP_ENTITY_ID_TXT, RESP_CODE FROM IGF.IGF_SL_RS_RESP_DTLS WHERE RESP_CODE = :code;
• Document-level traceability: Join DOCUMENT_ID_TXT to IGF_SL_CR_RESP_DTLS to trace response details back to their originating document.
• Reconciliation and audit: Reconstruct the audit trail using the standard Who columns and concurrent request columns to determine which ETRM process generated or updated a response record.
• Reporting: Aggregate counts by RESP_CODE or REP_ENTITY_ID_TXT to produce reporting-school response summaries.

The full projection query documented for this object selects all thirteen columns ordered by the surrogate key, which is a convenient starting point for ad hoc investigation.

Related Objects

Dependency metadata indicates that IGF_SL_RS_RESP_DTLS does not reference other database objects directly, but it is referenced by the APPS synonym IGF_SL_RS_RESP_DTLS. The most significant related object is the foreign-key counterpart on DOCUMENT_ID_TXT to IGF.IGF_SL_CR_RESP_DTLS, which links reporting-school response details to their corresponding core response detail records. Together, these objects form part of the IGF student lending response data model, and joining on the document identifier is the primary mechanism for correlating response elements across the two tables.