Search Results todo_dt

Overview

IGS.IGS_PE_STD_TODO is a transactional table in the Oracle E-Business Suite Student System (the IGS product family, delivered under the FND Design Data namespace IGS.IGS_PE_STD_TODO). It records a "to-do" item placed against a student. Typical examples cited in the object documentation include re-assessing fees or producing an outcome notification. Each todo may carry a date before which it must not be actioned, and each may be logically deleted rather than physically removed. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its unique index IGS_PE_STD_TODO_U1 is stored separately in APPS_TS_TX_IDX.

From a dimensional-modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. In Data Vault terms, this suggests the table is best modeled as a satellite hanging off a party/student hub (via PERSON_ID referencing HZ_PARTIES), capturing descriptive and status attributes of the student's todo state, rather than as an independent hub or a relationship link.

Key Information Stored

The table contains fourteen documented columns. The most significant are summarized below.

• PERSON_ID (NUMBER, 15) — Identifies the student the todo item relates to; also a component of the primary key and the unique index, and a foreign key to HZ_PARTIES.
• S_STUDENT_TODO_TYPE (VARCHAR2, 30) — Describes the nature of the todo for the student; a component of the business key.
• SEQUENCE_NUMBER (NUMBER) — Uniquely identifies the student todo item; the third component of the business key.
• TODO_DT (DATE) — The date on which the todo item is to be actioned, and the effective "not before" date.
• LOGICAL_DELETE_DT (DATE) — The date the item was logically deleted, supporting soft-delete semantics.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide audit and concurrency tracking.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE record the last concurrent program that updated the record.

The surrogate/business primary key is IGS_PE_STD_TODO_PK, defined on (PERSON_ID, S_STUDENT_TODO_TYPE, SEQUENCE_NUMBER). The unique index IGS_PE_STD_TODO_U1 enforces the same three-column business key on the APPS_TS_TX_IDX tablespace, confirming it as the primary business-key candidate.

Common Use Cases and Queries

The table is commonly queried to surface outstanding actions for a student, to drive notification or fee-reassessment workflows, and to report on pending versus logically deleted todos.

• Retrieve all active todos for a student: SELECT PERSON_ID, S_STUDENT_TODO_TYPE, SEQUENCE_NUMBER, TODO_DT FROM IGS.IGS_PE_STD_TODO WHERE PERSON_ID = :p_person AND LOGICAL_DELETE_DT IS NULL;
• Identify todos due to be actioned by a cutoff date: filter on TODO_DT where LOGICAL_DELETE_DT is null.
• Audit concurrent-program updates using REQUEST_ID and the PROGRAM_* columns.
• Join to HZ_PARTIES to resolve party details for reporting.

The documented query text supports a straightforward SELECT over all fourteen columns, ordered by the business key for deterministic output.

Related Objects

• HZ_PARTIES — referenced via IGS_PE_STD_TODO.PERSON_ID; resolves the underlying party/student.
• IGS_PE_STD_TODO_REF — references this table via PERSON_ID; a dependent reference table.
• IGS_PE_STD_TO — appears as a related dependency within the IGS student-todo object family.
• IGS_PE_STD_TODO_PK / IGS_PE_STD_TODO_U1 — the primary key constraint and unique index enforcing the three-column business key.