Search Results lort_id

Overview

IGF.IGF_SL_LOAD_FILE_T is a temporary (staging) table in the IGF schema, used by Oracle E-Business Suite components that process student loan response and acknowledgment files. As documented, the table "indicates temporary table into which data is loaded from the response files." In Oracle EBS 12.1.1 and 12.2.2, it serves as a landing zone within the interface layer, receiving raw records from inbound response files before downstream validation, parsing, and application. It is stored in the APPS_TS_INTERFACE tablespace with a PCT Free of 10, consistent with transient interface data that is periodically truncated or purged.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone. Because no foreign key dependencies are documented (it neither references nor is referenced by other database objects at the constraint level), it is best modeled as an isolated staging or hub-like structure rather than a link or satellite. This classification is a modeling suggestion only; functionally the table behaves as a raw file-load buffer.

Key Information Stored

The table contains eight documented columns. The most significant are:

• LORT_ID (NUMBER, 15) — Identifier for records in acknowledgment files. This is the surrogate primary key, enforced by index IGF_SL_LOAD_FILE_T_U1 (UNIQUE) and referenced as PK IGF_SL_LOAD_FILE_T_PK. Because the unique index covers LORT_ID alone, it also serves as the sole business-key candidate.
• RECORD_DATA (VARCHAR2, 4000) — Contains each of the lines in the file. Each row holds one raw line from the inbound response file, up to the 4000-character limit.
• FILE_TYPE (VARCHAR2, 30) — Indicates the type of response file, allowing multiple response formats to coexist in the same staging table.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Who columns capturing audit and concurrency information for each loaded row.

There is no separate business key beyond LORT_ID, and no natural key columns (such as a file name or sequence number) are documented.

Common Use Cases and Queries

The principal use case is staging and inspection of inbound response files prior to application processing. Typical operations include counting loaded lines per response type, isolating records for a specific identifier, and truncating the table after successful processing.

Representative query patterns:

• Retrieve all staged lines for a given LORT_ID:
  SELECT LORT_ID, FILE_TYPE, RECORD_DATA FROM IGF.IGF_SL_LOAD_FILE_T WHERE LORT_ID = :p_lort_id;
• Summarize load volume by file type:
  SELECT FILE_TYPE, COUNT(*) FROM IGF.IGF_SL_LOAD_FILE_T GROUP BY FILE_TYPE;
• Audit recent loads:
  SELECT CREATED_BY, CREATION_DATE, FILE_TYPE FROM IGF.IGF_SL_LOAD_FILE_T ORDER BY CREATION_DATE DESC;

Reporting use cases center on load reconciliation — verifying that all lines of a response file arrived intact, and confirming that staging rows were consumed before the next processing cycle. Because records are transient, reporting should generally target downstream applied tables once parsing is complete.

Related Objects

Per the documented dependency data, IGF.IGF_SL_LOAD_FILE_T does not reference any database object, and it is referenced only by the APPS synonym IGF_SL_LOAD_FILE_T. No foreign keys or dependent views, packages, or APIs are recorded in the ETRM metadata.

Consequently, join relationships must be inferred from shared identifiers rather than enforced constraints. The most relevant associated objects are:

• APPS.IGF_SL_LOAD_FILE_T — The APPS-layer synonym through which concurrent programs and forms access the IGF table.
• Downstream IGF student loan processing tables that consume RECORD_DATA, joined indirectly on LORT_ID or on the acknowledgment identifier carried within the record line.

Because the relationship data classifies this object as standalone, integrators should not assume referential integrity; joins to downstream tables must be validated against the actual parsing logic used by the associated student loan concurrent programs.