Search Results ytds_id




Overview
Explore in AI Chat

Overview

The table IGF.IGF_DB_YTD_SMR_ALL is a transaction data table within the Oracle E-Business Suite (EBS) schema IGF, which supports the Financial Aid module and related disbursement processing. It stores the summary of year-to-date disbursement data, consolidating both Year-To-Date Summary and Monthly Summary information as defined by the Direct Loan File Format. The table is registered as valid in both Oracle EBS 12.1.1 and 12.2.2, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, reflecting its role as a high-volume transactional store.

The object is owned by the IGF schema and is referenced by the FND Design Data entry IGF.IGF_DB_YTD_SMR_ALL. Based on the mined foreign key structure, the data vault classification for this table is standalone, meaning it is not directly joined to other tables through enforced referential constraints. Under a dimensional or Data Vault modeling heuristic, this table would most naturally be modeled as a satellite, since it captures descriptive and quantitative attributes associated with a disbursement summary keyed by a single surrogate identifier, rather than acting as a hub (unique business entity) or a link (relationship between entities). This classification is a modeling suggestion rather than a documented physical constraint.

Key Information Stored

The table contains 29 documented columns. The primary surrogate key is YTDS_ID (NUMBER, length 15), which uniquely identifies each summary record. This column is enforced by the unique index IGF_DB_YTD_SMR_PK on the APPS_TS_TX_IDX tablespace. No additional business-key candidate indexes are documented beyond this primary key.

  • YTDS_ID — Surrogate primary key uniquely identifying the summary of year-to-date disbursement data.
  • DL_VERSION — Direct Loan File Format Version (VARCHAR2, 30).
  • RECORD_TYPE — Indicates whether the record represents Year-To-Date Summary or Monthly Summary information.
  • BATCH_ID — Unique identifier for the batch (VARCHAR2, 30).
  • SCHOOL_CODE — School code associated with the disbursement summary.
  • STAT_END_DT — Statement end date for the report (DATE).
  • PROCESS_DT — Process date (DATE).
  • DISB_SMR_TYPE — Disbursement summary type.
  • BKD_GROSS, BKD_FEE, BKD_INT_REBATE, BKD_NET — Booked gross, fee, interest rebate, and net amounts (NUMBER, 15).
  • UNBKD_GROSS, UNBKD_FEE, UNBKD_INT_REBATE, UNBKD_NET — Corresponding amounts for the not-booked portion.
  • ORG_ID — Operating Unit identifier (NUMBER, 15), enabling multi-org reporting.
  • REQUEST_ID — Concurrent program request identifier (standard Who column).

Standard Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent program columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present, along with REGION_CODE, STATE_CODE, and REC_COUNT.

Common Use Cases and Queries

Typical usage centers on disbursement reconciliation and federal Direct Loan reporting. The summary data can be aggregated by operating unit, school, or batch to reconcile booked versus not-booked amounts, or to produce Year-To-Date and Monthly Summary reports required by the Direct Loan File Format.

Illustrative query retrieving summary totals by batch:

  • SELECT BATCH_ID, SCHOOL_CODE, DISB_SMR_TYPE, SUM(BKD_NET), SUM(UNBKD_NET) FROM IGF.IGF_DB_YTD_SMR_ALL WHERE ORG_ID = :org_id AND PROCESS_DT BETWEEN :start_dt AND :end_dt GROUP BY BATCH_ID, SCHOOL_CODE, DISB_SMR_TYPE;
  • Filtering on RECORD_TYPE distinguishes YTD from monthly summary rows.
  • Joining on REQUEST_ID to FND_CONCURRENT_REQUESTS supports tracing the concurrent program that populated the summary.

Related Objects

The Data Vault classification indicates no enforced foreign key relationships, so dependencies are best understood through shared columns and standard EBS conventions rather than PK/FK constraints:

  • FND_CONCURRENT_REQUESTS — related via REQUEST_ID to attribute the summary row to its generating concurrent program.
  • FND_CONCURRENT_PROGRAMS — related via PROGRAM_ID and PROGRAM_APPLICATION_ID.
  • Operating Unit objects (for example HR_OPERATING_UNITS) — related via ORG_ID for multi-org reporting.
  • Direct Loan disbursement tables within the IGF schema — related via BATCH_ID and SCHOOL_CODE to source disbursement records.
  • Standard Who columns align with the EBS audit convention shared across all transaction tables.