Search Results igs_ge_s_log_entry_u1

Overview

IGS.IGS_GE_S_LOG_ENTRY is a transaction-oriented log table in the Oracle E-Business Suite IGS (Higher Education / Student Systems) schema. It stores discrete log entry records generated by IGS processes, such as bulk data loads, concurrent program executions, and integration routines that populate or validate student, course, and unit data. Each row represents a single logged event — a message, an informational note, or a diagnostic entry — tied to a named log type. The table resides in the APPS_TS_TX_DATA tablespace and is registered under FND Design Data as IGS.IGS_GE_S_LOG_ENTRY.

The primary key, IGS_GE_S_LOG_ENTRY_PK, is composed of S_LOG_TYPE, CREATION_DT, and SEQUENCE_NUMBER. The same three columns form the unique index IGS_GE_S_LOG_ENTRY_U1 in the APPS_TS_TX_IDX tablespace, making them both the physical key and the business-key candidate for this object. Mined from its foreign key structure, the table is classified as satellite-leaning: it predominantly captures descriptive, time-stamped attributes around a parent log definition rather than forming an independent business hub or association table. This classification is a heuristic modeling suggestion, not a normative ETRM designation.

Key Information Stored

The 15 documented columns fall into three functional groups: identification, payload, and the standard Who / concurrent-program audit columns.

• S_LOG_TYPE (VARCHAR2, 30) — The log type under which the entry exists; foreign key to IGS_GE_S_LOG and the first component of the primary key.
• CREATION_DT (DATE) — The date the log entry was created; second primary-key component.
• SEQUENCE_NUMBER (NUMBER) — An internal sequence number distinguishing entries of the same type created on the same date; third primary-key component.
• KEY (VARCHAR2, 255) — A concatenated business key assembled by the logging process, for example a person ID, course code, and unit code combined into a single string such as "9876543, A300, ABC123".
• MESSAGE_NAME (VARCHAR2, 30) — An optional message number used when the entry is a system message, avoiding repeated storage of the same text.
• TEXT (VARCHAR2, 2000) — The free-form text of the log entry.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who audit columns capturing user and timestamp information.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context identifying the request and program that last touched the record.

Common Use Cases and Queries

Typical uses include diagnosing failures in IGS data-load and validation programs, reviewing messages emitted during a specific concurrent request, and auditing which keys (person, course, or unit) triggered warnings. Because the Who and concurrent columns are present, log entries can be correlated directly with concurrent request output.

A basic query to retrieve all entries for a log type in chronological order:

SELECT S_LOG_TYPE, CREATION_DT, SEQUENCE_NUMBER, KEY, MESSAGE_NAME, TEXT
FROM IGS.IGS_GE_S_LOG_ENTRY
WHERE S_LOG_TYPE = :p_log_type
ORDER BY CREATION_DT, SEQUENCE_NUMBER;

Filtering by concurrent request to isolate output from a single run:

SELECT KEY, MESSAGE_NAME, TEXT
FROM IGS.IGS_GE_S_LOG_ENTRY
WHERE REQUEST_ID = :p_request_id;

Joining to the parent log definition for descriptive context:

SELECT e.S_LOG_TYPE, l.DESCRIPTION, e.KEY, e.TEXT
FROM IGS.IGS_GE_S_LOG_ENTRY e, IGS.IGS_GE_S_LOG l
WHERE e.S_LOG_TYPE = l.S_LOG_TYPE;

Related Objects

The most significant relationship is the foreign key from S_LOG_TYPE to IGS_GE_S_LOG, which defines the catalogue of valid log types and is the natural parent in most reporting joins. Concurrent program diagnostics commonly join to FND_CONCURRENT_REQUESTS via REQUEST_ID and to FND_APPLICATION / FND_CONCURRENT_PROGRAMS via PROGRAM_APPLICATION_ID and PROGRAM_ID. Because the table is satellite-leaning and the KEY column carries denormalized person, course, and unit identifiers, downstream queries frequently resolve those embedded keys against IGS student and curriculum tables. The unique index IGS_GE_S_LOG_ENTRY_U1 and primary key IGS_GE_S_LOG_ENTRY_PK govern direct lookups by log type, creation date, and sequence number.