Results for “igs_en_std_warnings”

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

Overview

The IGS_EN_STD_WARNINGS table belongs to the IGS (Student System) product family within Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its documented purpose is to contain the self-service warning details presented to a student, capturing the messages, actions, and destinations surfaced to the learner through self-service pages. In the documented reference environment the table is marked "Not implemented in this database," indicating that it is a legacy or optional structure whose presence depends on whether the IGS enrollment self-service feature set was ever deployed and configured.

From a dimensional modeling perspective, the mined heuristic classification places this object as a standalone structure, meaning it does not participate in a formal foreign-key hub or link pattern within the documented schema. In Data Vault terms, it is best treated as a satellite-like record keyed by a single surrogate identifier, since its business content (warning text, message metadata, and session context) is descriptive rather than relational. This classification should be treated as a modeling suggestion rather than a mandated design, given that the object carries twenty documented columns and only one unique index.

Key Information Stored

The table is anchored by its documented primary key, IGS_EN_STD_WARNINGS_PK, defined on the surrogate column WARNING_ID. This is the only documented unique index, and there is no separate business-key candidate recorded, so WARNING_ID serves as both the physical and logical access path.

• PERSON_ID — identifies the student to whom the warning applies and is the principal link back to the person/party model.
• COURSE_CD — the course code associated with the warning context.
• UOO_ID — the unit of offering identifier, tying the warning to a specific deliverable offering.
• TERM_CAL_TYPE and TERM_CI_SEQUENCE_NUMBER — the academic term calendar type and sequence, establishing the term in which the warning was raised.
• MESSAGE_FOR — indicates the intended recipient or audience of the warning message.
• MESSAGE_ICON, MESSAGE_NAME, and MESSAGE_TEXT — the presentation attributes and body of the self-service message.
• MESSAGE_ACTION, DESTINATION, and P_PARAMETERS — the navigational action, target page, and parameter string used to render a call-to-action link.
• STEP_TYPE and SESSION_ID — the self-service step within which the warning was generated and the originating session identifier.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard Oracle EBS who-columns supporting audit and concurrency tracking.

Common Use Cases and Queries

The principal use case is retrieving the outstanding self-service warnings displayed to a student, typically filtered by person and term. A representative query joins the warning rows to the term context and orders by creation date to present the most recent message first:

SELECT w.warning_id, w.message_name, w.message_text, w.message_icon, w.destination
FROM igs_en_std_warnings w
WHERE w.person_id = :p_person_id
AND w.term_cal_type = :p_cal_type
ORDER BY w.creation_date DESC;

Reporting use cases include auditing which warnings were issued per course or offering, measuring message delivery by STEP_TYPE, and diagnosing self-service navigation failures by inspecting DESTINATION and P_PARAMETERS. Because the table is documented as standalone, queries rarely require complex join graphs; most access is by WARNING_ID or PERSON_ID with a term qualifier. Administrators also use the table to verify that warning text and icons have been updated after a message configuration change.

Related Objects

The documented schema exposes no formal foreign keys, so relationships are inferential. The most significant objects that reference or depend on this table are:

• IGS_EN_STD_WARNINGS_PK — the primary-key constraint and unique index on WARNING_ID.
• Person/party tables joined via PERSON_ID, such as HZ_PARTIES or PER_ALL_PEOPLE_F, to resolve student identity.
• Course catalog tables keyed by COURSE_CD, such as IGS_PS_COURSES or its versioned equivalents.
• Unit-of-offering tables referenced through UOO_ID, such as IGS_PS_UNIT_OFR_OPT or the offering instance tables.
• Academic calendar tables referenced by TERM_CAL_TYPE and TERM_CI_SEQUENCE_NUMBER, such as IGS_CA_INSTANCES.
• Self-service session and step infrastructure, correlated through SESSION_ID and STEP_TYPE.

Because the object is documented as not implemented in the reference database, all dependent joins should be validated against the target instance before use.