Search Results usec_occur_id1

Overview

IGS.IGS_PS_FAC_TCFT_TMP is a temporary (staging) table in the Oracle E-Business Suite Student System / Student Records (IGS) schema. Its documented purpose is to hold details of instructor and time-conflicting unit section occurrences for a given instructor, which are then consumed by the Time Conflict report. In Oracle EBS 12.1.1 and 12.2.2, this object resides in the APPS_TS_TX_DATA tablespace and is exposed through the APPS synonym IGS_PS_FAC_TCFT_TMP.

The transaction data is transient by design: rows are typically populated by a concurrent program or PL/SQL process immediately before the Time Conflict report is run, and may be purged or regenerated on each execution. The heuristic Data Vault classification for this object is standalone, indicating it holds no foreign-key relationships to other IGS tables at the database level. From a modeling perspective, it behaves most like a link-style table recording conflicting pairs of unit section occurrences against a person, rather than a hub or satellite.

Key Information Stored

The table contains eight documented columns. The most operationally significant are:

• PERSON_ID (NUMBER 15) – the instructor for whom a time conflict exists.
• USEC_OCCUR_ID1 (NUMBER) – the first conflicting unit section occurrence.
• USEC_OCCUR_ID2 (NUMBER) – the second conflicting unit section occurrence.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard WHO audit columns recording the user and timestamp of row creation and modification, with LAST_UPDATE_LOGIN capturing the login session.

The primary key, IGS_PS_FAC_TCFT_TMP_PK, is a composite of PERSON_ID, USEC_OCCUR_ID1 and USEC_OCCUR_ID2, backed by a unique index in APPS_TS_TX_IDX. This composite key is also the documented business-key candidate: it enforces uniqueness of each instructor/conflicting-pair combination and prevents duplicate entries when the report process reruns.

Common Use Cases and Queries

The primary consumer is the Time Conflict report, which joins staged rows back to section occurrence and scheduling data to render conflicting pairs for an instructor. Typical patterns include:

• Listing all conflicts for a specific instructor:

  SELECT PERSON_ID, USEC_OCCUR_ID1, USEC_OCCUR_ID2
  FROM   IGS.IGS_PS_FAC_TCFT_TMP
  WHERE  PERSON_ID = :p_person_id;

• Detecting instructors with the highest number of conflicts:

  SELECT PERSON_ID, COUNT(*) conflict_count
  FROM   IGS.IGS_PS_FAC_TCFT_TMP
  GROUP  BY PERSON_ID
  ORDER  BY conflict_count DESC;

• Resolving occurrence identifiers to descriptive section data by joining USEC_OCCUR_ID1 and USEC_OCCUR_ID2 to the unit section occurrence table.
• Auditing when staged data was last refreshed using CREATION_DATE / LAST_UPDATE_DATE.

Because rows are transient, queries should be run immediately after the staging process. Reports should not treat this table as a persistent historical record.

Related Objects

The ETRM metadata records no foreign-key dependencies for this table, so relationships are logical rather than enforced. The significant associated objects are:

• APPS.IGS_PS_FAC_TCFT_TMP – the APPS synonym through which applications reference the underlying IGS table.
• Unit section occurrence table (referenced logically via USEC_OCCUR_ID1 / USEC_OCCUR_ID2) – supplies the schedule and timing detail used to determine conflicts.
• Person / instructor master data (referenced logically via PERSON_ID) – supplies the instructor name and related attributes.
• Time Conflict report concurrent program – the process that populates the table and consumes its rows as output.
• IGS_PS_FAC_TCFT_TMP_PK – the unique index underpinning the composite primary key.

Any custom extension should join on the three composite-key columns and treat all other attributes as descriptive metadata.