Search Results igs_ge_s_log_u1

Overview

IGS.IGS_GE_S_LOG is a system log table within the Oracle E-Business Suite 12.1.1 / 12.2.2 IGS (Student Systems / Higher Education) schema. Its documented purpose is to describe system log details — head or header records that group log entries generated by IGS processing routines such as calendar, enrollment, and academic record programs. The table is registered in FND Design Data as IGS.IGS_GE_S_LOG, is marked VALID, and its storage resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10.

The table is physically defined by a composite primary key, IGS_GE_S_LOG_PK (S_LOG_TYPE, CREATION_DT), and a unique index, IGS_GE_S_LOG_U1 (S_LOG_TYPE, CREATION_DT) in the APPS_TS_TX_IDX tablespace. The uniqueness index duplicates the primary key columns, confirming that the natural business key is the pair "log type plus creation date." From a heuristic Data Vault perspective, this object is classified as hub-leaning: S_LOG_TYPE and CREATION_DT behave as stable business keys, while the remaining descriptive and WHO columns (KEY, CREATED_BY, REQUEST_ID, PROGRAM_ID, etc.) are satellite-type attributes. The DATA VAULT modeling suggestion is therefore to treat the table as a hub keyed on S_LOG_TYPE/CREATION_DT, with dependent attributes held in a satellite. Practically, the table functions as the parent log header, with child entries stored in IGS_GE_S_LOG_ENTRY via the S_LOG_TYPE column.

Key Information Stored

The most significant columns are:

• S_LOG_TYPE (VARCHAR2 30, mandatory) — the type of system log the record belongs to. This is the primary business discriminator and the column targeted by the unique index IGS_GE_S_LOG_U1.
• CREATION_DT (DATE, mandatory) — the creation date of the log. Together with S_LOG_TYPE it forms the composite primary key (IGS_GE_S_LOG_PK) and unique business key.
• KEY (VARCHAR2 255) — an optional key record inserted by the process maintaining the log. It typically holds concatenated identifying information; for example, a calendar type and sequence number such as "ACAD-YR, 28".
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns recording user and timestamp audit information.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent manager columns identifying the last concurrent program (and its application) that inserted or updated the record.

The surrogate primary key is not a sequence-generated column but a composite business key: S_LOG_TYPE plus CREATION_DT. There is no separate surrogate ID, so referencing child tables carry at least S_LOG_TYPE to link back to the parent log.

Common Use Cases and Queries

The typical use case is diagnostic and audit reporting: identifying which processes raised logs, when, and under which concurrent request. A common pattern is to list log headers by type and date:

• SELECT S_LOG_TYPE, CREATION_DT, KEY, REQUEST_ID, PROGRAM_ID FROM IGS.IGS_GE_S_LOG WHERE S_LOG_TYPE = :p_type ORDER BY CREATION_DT DESC;
• SELECT S_LOG_TYPE, COUNT(*) FROM IGS.IGS_GE_S_LOG GROUP BY S_LOG_TYPE;

A frequent query joins the header to its entries (IGS_GE_S_LOG_ENTRY) on S_LOG_TYPE to retrieve the detailed line-level messages. Another uses REQUEST_ID to correlate logs with the concurrent program run, or PROGRAM_APPLICATION_ID/PROGRAM_ID to identify the originating program. Reporting use cases include error-rate trending by log type, identifying processes with abnormal log volumes, and auditing the KEY field to trace a specific calendar type and sequence number that produced a log. The CO interface (IGS_GE_S_LOG) is used for upload, validation, or bulk maintenance of these records.

Related Objects

The documented dependency data identifies IGS_GE_S_LOG_ENTRY as the principal dependent object: its S_LOG_TYPE foreign key column references this table, forming a header-to-entry relationship. In the APPS synonym layer, IGS_GE_S_LOG is the APPS-owned synonym for IGS.IGS_GE_S_LOG and is the name used in queries and concurrent programs.

The broader related set includes:

• IGS_GE_S_LOG_ENTRY — child log detail rows, joined on S_LOG_TYPE.
• IGS_GE_S_LOG_U1 — unique index enforcing the S_LOG_TYPE / CREATION_DT business key.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to resolve concurrent program run context.
• FND_CONCURRENT_PROGRAMS — joined on PROGRAM_APPLICATION_ID, PROGRAM_ID to identify the logging program.
• FND_USER — joined on CREATED_BY / LAST_UPDATED_BY for user audit detail.
• IGS_GE_S_LOG (APPS synonym) — the application-facing synonym used by IGS concurrent programs.

Because the table does not itself reference other database objects, its referential role is that of a parent hub for log entries and a diagnostic anchor for concurrent processing within the IGS product family.