Search Results igs_pe_std_todo_ref_pk

Overview

IGS_PE_STD_TODO_REF is a reference (satellite) table within the Oracle E-Business Suite Student System (IGS) product family. It stores supplementary reference information attached to a to-do item placed against a student. A to-do item represents an administrative action pending against a learner record, such as assigning default assessment items against a student in a unit for a particular teaching period. Where the parent to-do record (IGS_PE_STD_TODO) captures the existence and type of the outstanding action, IGS_PE_STD_TODO_REF captures the contextual detail that qualifies that action — the course, unit, calendar type, and other identifiers the action applies to.

The table is registered in the IGS schema with a status of VALID and is documented at 20 columns in the ETRM 12.1.1 physical schema. Under a heuristic Data Vault classification mined from its foreign key structure, this object is satellite-leaning: it hangs off a parent entity keyed by PERSON_ID, S_STUDENT_TODO_TYPE and SEQUENCE_NUMBER, and carries descriptive context rather than acting as a hub or a resolving link. This classification is a modeling suggestion only; in the operational EBS schema the object is a conventional child table.

Key Information Stored

The primary key, IGS_PE_STD_TODO_REF_PK, is composite and comprises PERSON_ID, S_STUDENT_TODO_TYPE, SEQUENCE_NUMBER and REFERENCE_NUMBER. A unique index, IGS_PE_STD_TODO_REF_U1, exists on the same four columns, confirming that the business key and the primary key coincide — each reference line is uniquely identified by the student, the to-do type, the to-do sequence, and the reference number.

• PERSON_ID — the student against whom the to-do and its reference detail are recorded; also the leading FK column linking to IGS_PE_STD_TODO.
• S_STUDENT_TODO_TYPE — the to-do category (for example, an assessment-assignment action), participating in both PK and FK.
• SEQUENCE_NUMBER — distinguishes multiple to-do instances of the same type for the same person; the third PK/FK column.
• REFERENCE_NUMBER — the ordinal that separates multiple reference records beneath a single to-do item.
• CAL_TYPE — the calendar type, typically identifying the teaching period or academic calendar context.
• COURSE_CD — the course to which the referenced to-do action applies.
• UNIT_CD — the unit (subject) within the course relevant to the action.
• CI_SEQUENCE_NUMBER — a sequence that aligns the reference to a course/unit instance or version.
• OTHER_REFERENCE — a free-form or secondary reference value for context not covered by the structured columns.
• UOO_ID — an internal identifier, generally correlating to a unit offering option or organisational unit reference.
• LOGICAL_DELETE_DT — a soft-delete marker; a non-null value indicates the reference line has been logically removed without physical deletion.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent-program traceability columns identifying the process that created or last modified the row.

Common Use Cases and Queries

Typical usage centres on reconciling outstanding student to-do items with the academic structures they reference — reporting which assessment items or unit actions remain pending for a cohort, per teaching period. A common pattern joins the reference rows back to the parent to-do using the full composite key:

• SELECT r.PERSON_ID, r.S_STUDENT_TODO_TYPE, r.SEQUENCE_NUMBER, r.COURSE_CD, r.UNIT_CD, r.CAL_TYPE FROM IGS_PE_STD_TODO_REF r WHERE r.LOGICAL_DELETE_DT IS NULL;
• Filtering by CAL_TYPE and COURSE_CD to enumerate all to-do references for a given teaching period and course offering.
• Joining to IGS_PE_STD_TODO on PERSON_ID, S_STUDENT_TODO_TYPE and SEQUENCE_NUMBER to retrieve the to-do description alongside its reference detail.
• Audit queries using REQUEST_ID and the PROGRAM_* columns to trace which concurrent process generated reference rows.
• Excluding logically deleted rows via LOGICAL_DELETE_DT in all reporting extracts to preserve historical integrity.

Related Objects

• IGS_PE_STD_TODO — the parent to-do table; joined on PERSON_ID, S_STUDENT_TODO_TYPE and SEQUENCE_NUMBER. This is the only formally documented foreign key relationship for IGS_PE_STD_TODO_REF.
• IGS_PE_STD_TODO_REF_PK / IGS_PE_STD_TODO_REF_U1 — the primary key constraint and unique index enforcing the composite business key.
• Student Academic Structure tables (course and unit definitions referenced by COURSE_CD and UNIT_CD) — used to resolve descriptive course and unit names.
• Calendar / teaching period tables referenced by CAL_TYPE — used to translate the calendar code into a period description.
• WHO audit and concurrent program dictionaries (FND_USER, FND_CONCURRENT_REQUESTS) — used with CREATED_BY, LAST_UPDATED_BY and REQUEST_ID for traceability.