Search Results igs_ps_fac_tcft_tmp

Overview

IGS_PS_FAC_TCFT_TMP is a temporary (staging) table within the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to hold the instructor and time-conflicting unit section occurrences associated with a faculty member, so that the data can be consumed by the Time Conflict report. In practice, the table acts as an intermediate work area: a reporting or batch process populates it with pairs of section occurrences that clash in time for a given instructor, the report reads those rows, and the temporary content is subsequently cleared. The product designation is flagged as Obsolete, and the implementation metadata explicitly states that the object is "Not implemented in this database," meaning any deployment relying on it must confirm its physical existence and state in the target environment before use.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. This should be read as a modeling suggestion rather than a prescriptive design: the table does not participate in a documented hub, link, or satellite hierarchy. It is a transient, report-oriented structure rather than a persistent entity within the institutional data model. Because it is temporary in nature, its rows are not intended for historical retention, audit, or long-term analytics.

Key Information Stored

The documented physical schema (ETRM 12.1.1) includes eight columns owned by the IGS schema. The most important of these are the three that constitute the composite primary key, which are the business-meaningful identifiers:

• PERSON_ID — identifies the instructor (faculty member) whose schedule is being evaluated for conflicts.
• USEC_OCCUR_ID1 — the first unit section occurrence identifier involved in the conflict pair.
• USEC_OCCUR_ID2 — the second unit section occurrence identifier involved in the conflict pair.

The primary key is documented as IGS_PS_FAC_TCFT_TMP_PK, defined over (PERSON_ID, USEC_OCCUR_ID1, USEC_OCCUR_ID2). This constraint is simultaneously the unique index and the business-key candidate, so there is no separate surrogate key column; the natural business key of the conflict pair plus instructor is the identity of the row. The remaining documented columns are the standard Oracle EBS audit (WHO) columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These support row-level traceability of when and by whom the temporary records were generated, which is useful for debugging report runs.

Common Use Cases and Queries

The principal use case is the Time Conflict report. A typical pattern is to populate the table through a PL/SQL batch routine that compares an instructor's assigned section occurrences and inserts any pair whose time ranges overlap. Reporting then joins the occurrence identifiers back to the section occurrence tables to render human-readable detail:

• Confirming that a faculty member is double-booked between two section occurrences.
• Producing a per-instructor conflict listing for scheduling administrators before term publication.
• Reconciling conflicts after timetable adjustments.

A representative query retrieves conflict pairs for a specific instructor:

SELECT person_id, usec_occur_id1, usec_occur_id2 FROM igs_ps_fac_tcft_tmp WHERE person_id = :p_person_id;

A diagnostic query looks for stale or unprocessed rows by creation date:

SELECT * FROM igs_ps_fac_tcft_tmp WHERE creation_date >= TRUNC(SYSDATE);

Because the object is a temporary work table, queries should generally be scoped to the current batch run and not used for long-term reporting.

Related Objects

Join relationships derive from the key columns. The most significant related objects include:

• IGS_PS_SECTION_OCCURRENCE (or the corresponding unit section occurrence entity) — joined on USEC_OCCUR_ID1 and USEC_OCCUR_ID2 to resolve conflict detail.
• IGS_PS_FACULTY / instructor assignment tables — joined on PERSON_ID to retrieve faculty context.
• PER_ALL_PEOPLE_F — the HR person source behind PERSON_ID for names and status.
• The Time Conflict report concurrent program — the consumer that reads this temporary table.
• IGS_PS_FAC_TCFT and related conflict-resolution tables — persistent counterparts that may hold resolved outcomes.

Since the documented relationship classification is standalone, no enforced foreign keys are recorded; joins are logical and based on the business-key columns listed above.