Search Results igs_ge_gen_002




Overview
Explore in AI Chat

Overview

The view IGS_GE_S_LOG_ENTRY_V belongs to the IGS (Student System) product family, which is documented in Oracle E-Business Suite as obsolete. It is a reporting-oriented view defined over the general-purpose log entry table used by the IGS processing framework. Its principal purpose is to expose the contents of the S_LOG_ENTRY table while decomposing the concatenated KEY column into twenty individually addressable fields, thereby making the log data readable and queryable without requiring application-side parsing.

IGS log entries are written by the Student System's generic engine to record processing events, exception conditions, and diagnostic messages. In the raw table the identifying information for each entry is stored in a single delimited string. The view applies the database function IGS_GE_GEN_002.GENP_GET_DELIMIT_STR repeatedly to that string, splitting it on the pipe (|) character into FIELD_1 through FIELD_20. This design allows EBS reporting tools and integration interfaces to select specific positional components of the log key as discrete columns.

Underlying Base Objects

According to the ETRM metadata, the view is defined over a single base object: IGS_GE_S_LOG_ENTRY, aliased as SLE in the view text. The ETRM record notes that no base objects are separately documented as referenced, although the view SQL clearly identifies the source table. The view also depends on the PL/SQL function IGS_GE_GEN_002.GENP_GET_DELIMIT_STR, which is an IGS general utility packaged in the IGS_GE_GEN_002 package. That function accepts the delimited source string, an ordinal position, and a delimiter, and returns the corresponding token.

The ETRM implementation note states that the view is "Not implemented in this database," meaning it is not deployed in the environment from which the metadata was harvested. Consequently, no owner is recorded and the implementation status should be verified against the target instance before the view is referenced in custom code.

Key Columns

  • CREATION_DT — Creation date attribute carried forward from the base log entry record.
  • S_LOG_TYPE — Classifies the type of log entry written by the engine.
  • SEQUENCE_NUMBER — Ordering sequence for entries of the same log type.
  • FIELD_1 through FIELD_20 — Positional tokens extracted from the delimited KEY string using the pipe delimiter. Each field corresponds to a defined position within the composite key.
  • MESSAGE_NAME — Name of the message or event associated with the log entry.
  • TEXT — Free-text message body or detail recorded with the entry.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns for auditing.

Common Use Cases and Queries

The view is typically used to investigate processing errors, trace message flows, and build ad hoc reports on Student System activity. A minimal query retrieves recent entries with their decomposed key fields:

  • SELECT creation_dt, s_log_type, sequence_number, FIELD_1, FIELD_2, MESSAGE_NAME, TEXT FROM IGS_GE_S_LOG_ENTRY_V ORDER BY creation_dt DESC;
  • SELECT * FROM IGS_GE_S_LOG_ENTRY_V WHERE s_log_type = :type AND MESSAGE_NAME = :msg;
  • SELECT FIELD_1, COUNT(*) FROM IGS_GE_S_LOG_ENTRY_V GROUP BY FIELD_1;

Because the view is reported as obsolete and not implemented, references to it should be validated against the actual database, and any new development should target the underlying table and utility package directly.