Results for “creation_dt”

50+ results




Overview
Explore in AI Chat

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

Overview

IGS_GE_S_LOG_ENTRY is a table in the IGS (Student System) product schema of Oracle E-Busines Suite, holding detail-level log entry records generated by the Student System's general engine logging framework. Per the ETRM metadata, the object describes "log entry details" and is owned by the IGS schema with a VALID status. Its structure—a primary key composed of S_LOG_TYPE, CREATION_DT, and SEQUENCE_NUMBER combined with a foreign key back to IGS_GE_S_LOG—indicates that each row represents one discrete message appended to a parent log header. Based on the mined foreign key topology, the heuristic Data Vault classification for this object is satellite-leaning, suggesting that in a dimensional or Data Vault model it would typically be modeled as a satellite table attached to the IGS_GE_S_LOG hub, capturing descriptive and sequential attributes over time rather than serving as an independent business entity or a pure relationship link.

Key Information Stored

The table's identity is defined by the composite primary key IGS_GE_S_LOG_ENTRY_PK on (S_LOG_TYPE, CREATION_DT, SEQUENCE_NUMBER). The matching unique index IGS_GE_S_LOG_ENTRY_U1 shares these same three columns, reinforcing this triplet as the business-key candidate that uniquely positions an entry within a given log run. The most significant columns include:

  • S_LOG_TYPE – Log type identifier; part of the primary key and the foreign key column joining to IGS_GE_S_LOG.
  • CREATION_DT – Creation date of the log entry; part of the composite key and FK to the parent log.
  • SEQUENCE_NUMBER – Ordinal within the log, preserving message ordering.
  • KEY – Key value associating the entry with the specific record or process being logged.
  • MESSAGE_NAME – Name of the message template or event that produced the entry.
  • TEXT – Free-form message text or detail payload of the log entry.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS WHO columns for auditability and concurrency control.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE – Concurrent program context identifying the batch job that generated the entry.

These 15 columns distinguish the surrogate/business keys from the descriptive payload and provide full audit and concurrent-manager lineage.

Common Use Cases and Queries

Because the table records detailed log messages, the typical queries filter by log type and date to reconstruct the sequence of events for a batch or process. A standard pattern joining to the parent header is:

  • SELECT e.s_log_type, e.sequence_number, e.message_name, e.text FROM igs_ge_s_log_entry e WHERE e.s_log_type = :p_type AND e.creation_dt = :p_date ORDER BY e.sequence_number;
  • Diagnostic reporting by concurrent request: filter on REQUEST_ID, PROGRAM_ID, or PROGRAM_APPLICATION_ID to trace which program wrote the entries.
  • Correlation by business record: use the KEY column to find all log messages relating to a particular student, application, or record.
  • Time-series analysis: aggregate entries by CREATION_DT to detect error spikes or throughput trends per log type.

Reporting use cases include error-triage dashboards for Student System batch processes, audit trails for data changes, and reconciliation reports tied back to the originating concurrent request.

Related Objects

The dominant relationship is the foreign key from IGS_GE_S_LOG_ENTRY (S_LOG_TYPE, CREATION_DT) to the parent table IGS_GE_S_LOG, which stores the log header. The key related objects are:

  • IGS_GE_S_LOG – Parent log header; joined on S_LOG_TYPE and CREATION_DT.
  • IGS_GE_S_LOG_ENTRY_PK – Primary key constraint enforcing uniqueness on (S_LOG_TYPE, CREATION_DT, SEQUENCE_NUMBER).
  • IGS_GE_S_LOG_ENTRY_U1 – Unique index supporting the business-key candidate.
  • Concurrent program reference objects (FND_CONCURRENT_REQUESTS, FND_CONCURRENT_PROGRAMS) – linked logically via REQUEST_ID and PROGRAM_ID.

These objects collectively support the logging, retrieval, and audit lifecycle of Student System processes in Oracle EBS 12.1.1 and 12.2.2.