Search Results igf_sl_cod_doc_dtls_pk

Overview

IGF_SL_COD_DOC_DTLS is a table in the IGF (Financial Aid) product schema of Oracle E-Business Suite, holding records of documents exchanged with the U.S. Department of Education's Common Origination and Disbursement (COD) system. In the student financial aid lifecycle, institutions send origination, disbursement, and change records to COD and receive acknowledgment and response files back. This table acts as the persistence layer for that exchange, tracking each transmitted or received document, its type, its directional flow, and its processing status. It is available in both EBS 12.1.1 and 12.2.2, where it remains a VALID object in the IGF schema.

The heuristic Data Vault classification mined from the foreign key structure is standalone, meaning the table does not participate in a parent-child hub-and-link pattern with other objects. As a modeling suggestion, it is best treated as a satellite-like detail store keyed on a single natural business identifier rather than as a hub or link. The single documented primary key, IGF_SL_COD_DOC_DTLS_PK, is defined over DOCUMENT_ID_TXT, which also serves as the sole business-key candidate. The remaining unique indexes, SYS_IL0000402622C00002$$ and SYS_IL0000402622C00003$$, are system-generated LOB indexes rather than business keys.

Key Information Stored

The table comprises 17 documented columns. The most significant are:

• DOCUMENT_ID_TXT — the primary key column and the business identifier for each COD document record.
• OUTBOUND_DOC and INBOUND_DOC — directional indicators distinguishing documents transmitted to COD from those received from COD.
• SEND_DATE — the date the document was dispatched to COD.
• ACK_DATE — the date an acknowledgment was received for the document.
• DOC_STATUS — the current processing state of the document within the COD exchange cycle.
• DOC_TYPE — the classification of the document, identifying the nature of the COD transaction.
• FULL_RESP_CODE — the complete response code returned by COD, used for reconciliation and error handling.
• CREATED_BY, CREATION_DATE — standard audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns capturing the most recent modification.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program context columns identifying the process that created or last updated the row.

The surrogate key is DOCUMENT_ID_TXT as enforced by IGF_SL_COD_DOC_DTLS_PK; no separate numeric surrogate exists in the documented metadata.

Common Use Cases and Queries

Typical usage centers on monitoring the COD exchange pipeline, reconciling acknowledgments, and troubleshooting failed transmissions. A common query retrieves all documents still awaiting acknowledgment:

• SELECT DOCUMENT_ID_TXT, DOC_TYPE, SEND_DATE, DOC_STATUS FROM IGF.IGF_SL_COD_DOC_DTLS WHERE ACK_DATE IS NULL AND OUTBOUND_DOC = 'Y';
• SELECT DOC_TYPE, DOC_STATUS, COUNT(*) FROM IGF.IGF_SL_COD_DOC_DTLS GROUP BY DOC_TYPE, DOC_STATUS;
• SELECT DOCUMENT_ID_TXT, FULL_RESP_CODE FROM IGF.IGF_SL_COD_DOC_DTLS WHERE FULL_RESP_CODE IS NOT NULL AND TRUNC(CREATION_DATE) = TRUNC(SYSDATE);

These patterns support daily operational dashboards, audit trails for compliance reporting, and root-cause analysis of COD rejection codes. Joining the concurrent program columns to FND_CONCURRENT_REQUESTS allows tracing a document back to the process that generated it.

Related Objects

Because the metadata classifies the table as standalone, no enforced foreign keys are documented. Interaction occurs chiefly through the concurrent program and request audit columns:

• FND_CONCURRENT_REQUESTS — join on REQUEST_ID to identify the originating process.
• FND_CONCURRENT_PROGRAMS — join on PROGRAM_ID and PROGRAM_APPLICATION_ID for program names.
• FND_APPLICATION — resolves PROGRAM_APPLICATION_ID to the owning application.
• FND_USER — join on CREATED_BY and LAST_UPDATED_BY for user attribution.
• Other IGF_SL_COD_* tables within the Financial Aid schema that share the COD document domain and are accessed by the same COD processing concurrent programs.

Queries against these related objects should be driven from DOCUMENT_ID_TXT as the stable correlation key.