Results for “stu_1098t_id”

18 results




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

Overview

IGS_FI_1098T_DTLS is a transaction-detail table within the IGS (Student System) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the individual financial transactions that roll up into the IRS Form 1098-T tuition statement amounts reported in Boxes 2, 3, 4, and 5. Where the parent table IGS_FI_1098T_DATA captures the student-level statement, IGS_FI_1098T_DTLS records the underlying transaction lines and the box assignment each line contributes to, providing the audit trail that explains how a reported box total was derived.

From a dimensional modeling perspective, the mined foreign-key structure suggests this table is satellite-leaning. It hangs off the IGS_FI_1098T_DATA parent through STU_1098T_ID, extending the parent record with descriptive transaction-level attributes rather than acting as a pure hub or a many-to-many link. This classification is a heuristic suggestion only; the physical implementation is a standard EBS transactional detail table with WHO audit columns and concurrent-program tracking columns.

Key Information Stored

The table contains 14 documented columns. The surrogate composite primary key is IGS_FI_1098T_DTLS_PK, defined on the combination (STU_1098T_ID, BOX_NUM, TRANSACTION_ID, TRANSACTION_CODE). This composite structure is also the strongest business-key candidate, since it uniquely identifies a single 1098-T box assignment for a single transaction.

  • STU_1098T_ID — Foreign key to IGS_FI_1098T_DATA; identifies the student 1098-T statement record that this detail line belongs to.
  • BOX_NUM — The 1098-T box (2, 3, 4, or 5) to which the transaction amount aggregates.
  • TRANSACTION_ID — Reference to the underlying student financial transaction.
  • TRANSACTION_CODE — Code classifying the transaction type used in the box assignment logic.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework.
  • CREATED_BY, CREATION_DATE — Audit columns capturing row creation.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit columns capturing the most recent modification.
  • REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program context, identifying the process that created or last updated the row.

Common Use Cases and Queries

The primary use case is reconciliation and audit of 1098-T box totals. Reporters and financial aid staff query this table to trace which transactions contributed to a reported amount, and to confirm the box assignment logic was applied correctly. A typical reconciliation joins the detail lines to the parent statement:

  • Select all detail rows for a student's statement: SELECT d.BOX_NUM, d.TRANSACTION_ID, d.TRANSACTION_CODE FROM IGS_FI_1098T_DTLS d WHERE d.STU_1098T_ID = :p_stu_1098t_id ORDER BY d.BOX_NUM;
  • Aggregate detail counts by box across a population to validate statement totals against the parent IGS_FI_1098T_DATA amounts.
  • Trace a specific transaction to the 1098-T statements and boxes it feeds, using TRANSACTION_ID and TRANSACTION_CODE as the search predicates.
  • Audit row provenance by filtering on REQUEST_ID or PROGRAM_ID to determine which concurrent process populated a given set of detail lines.

Because the table stores only the transaction-to-box mapping, reporting is normally performed in conjunction with the parent statement table to retrieve student identity and reporting-year context.

Related Objects

  • IGS_FI_1098T_DATA — Parent table; joined on IGS_FI_1098T_DTLS.STU_1098T_ID = IGS_FI_1098T_DATA.STU_1098T_ID. This is the reported foreign key relationship and provides the student-level statement record.
  • IGS_FI_1098T_DTLS_PK — The primary key constraint/index over (STU_1098T_ID, BOX_NUM, TRANSACTION_ID, TRANSACTION_CODE), used for unique access paths and integrity enforcement.
  • IGS_FI_1098T_* setup and reporting objects — Additional IGS 1098-T family objects (statement generation, box configuration, and reporting views) depend on this detail data when producing and validating statements.
  • Student financial transaction tables — Referenced indirectly via TRANSACTION_ID and TRANSACTION_CODE to source the tuition and related-fee amounts that populate the box totals.