Results for “igf_sl_dl_chg_send_all_pk”

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

Overview

IGF_SL_DL_CHG_SEND_ALL is a transaction table in the IGF (Financial Aid) product of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It maintains the changed values for Direct Loan records that must be transmitted to the Loan Origination Center (LOC). When financial aid staff modify Direct Loan data within Oracle, the system records the nature of the change and the replacement value in this table so that the change payload can be assembled and delivered to the LOC in a subsequent outbound transmission.

The object resides in the IGF schema and is registered as VALID in ETRM. From a dimensional modeling perspective, the heuristic Data Vault classification derived from its foreign key structure is satellite-leaning. This suggests the table behaves as a descriptive satellite attached to a parent business key — specifically the Direct Loan batch — capturing attribute-level change history rather than acting as an independent hub or a many-to-many link.

Key Information Stored

The table comprises sixteen documented columns. Its surrogate primary key, enforced through IGF_SL_DL_CHG_SEND_ALL_PK, is CHG_NUM, a system-generated identifier for each change record. A unique index, IGF_SL_DL_CHG_SEND_ALL_U1, also exists on CHG_NUM, confirming it as the sole documented business-key candidate.

• CHG_NUM — Surrogate primary key uniquely identifying each recorded change.
• DBTH_ID — Foreign key to IGF_SL_DL_BATCH_ALL, tying each change to its originating Direct Loan batch.
• LOAN_NUMBER — The Direct Loan identifier to which the change applies.
• CHG_CODE — Code classifying the type of change made to the loan data.
• NEW_VALUE — The replacement value that must be communicated to the LOC.
• STATUS — Processing state of the change record (for example, pending, sent, or errored).
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program context identifying the process that created or updated the row.
• ORG_ID — Operating unit identifier supporting multi-org data segregation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking row creation and modification.

Common Use Cases and Queries

The primary use case is reconciliation and troubleshooting of Direct Loan change transmissions. Financial aid administrators and technical support teams query this table to determine which changes are outstanding, which have been transmitted, and which failed. A representative query listing pending changes for a batch is:

• SELECT chg_num, loan_number, chg_code, new_value, status FROM igf_sl_dl_chg_send_all WHERE dbth_id = :batch_id AND status = 'PENDING';
• SELECT dbth_id, COUNT(*) FROM igf_sl_dl_chg_send_all GROUP BY dbth_id; to profile change volume per batch.
• Joining to IGF_SL_DL_BATCH_ALL on DBTH_ID to associate changes with batch-level attributes.

Reporting scenarios include audit trails of Direct Loan modifications, monitoring of change send status for compliance, and diagnostics when the LOC rejects or does not acknowledge a transmitted change.

Related Objects

The most significant relationship is with the parent batch table. The documented foreign key IGF_SL_DL_CHG_SEND_ALL.DBTH_ID references IGF_SL_DL_BATCH_ALL, making the batch the controlling object for change records.

• IGF_SL_DL_BATCH_ALL — Parent batch table; join on DBTH_ID.
• IGF_SL_DL_CHG_SEND_ALL_PK — Primary key constraint on CHG_NUM.
• IGF_SL_DL_CHG_SEND_ALL_U1 — Unique index on CHG_NUM.

Downstream, the concurrent programs and interfaces that read this table to construct the outbound LOC transmission depend on the STATUS and REQUEST_ID columns to select eligible rows. Direct Loan setup and loan master tables in the IGF schema provide the LOAN_NUMBER context referenced by each change record.