Search Results tba_status




Overview

APPS.IGS_PS_SCH_INT is an Oracle E-Business Suite interface view belonging to the Student System (IGS) product family, owned by the APPS schema and registered under FND Design Data IGS.IGS_PS_SCH_INT. Its name denotes a schedule interface object for unit (course) sections, and the presence of TRANSACTION_TYPE, TRANSACTION_ID, SCHEDULE_STATUS, and ERROR_TEXT columns confirms that the view is designed to stage, validate, and process inbound scheduling records rather than to serve purely as a passive reporting construct. The object holds status VALID in ETRM 12.2.2 and is documented for both 12.1.1 and 12.2.2. As a multi-org view, it restricts returned rows to the operating unit identified by ORG_ID for the session's current organization context, automatically excluding data belonging to other operating units. Users searching on "tba_status" reach this view because TBA_STATUS is one of its exposed columns, recording the "To Be Advised" scheduling state when a unit section's time, day, building, or room assignment has not yet been finalized.

Underlying Base Objects

The ETRM metadata records no referenced base objects for IGS_PS_SCH_INT. In practice, the view is defined over staging table IGS_PS_SCH_INT_ALL and its allied interface objects, with the multi-org clause appended automatically by the applications dictionary. The _ALL suffix convention indicates a table partitioned by ORG_ID, which the view exposes directly through its ORG_ID NUMBER(15) column. Several surviving columns preserve the legacy pre-relational interface design: UNIT_SECTION_OCCURRENCE_ID, INT_OCCURS_ID, and INT_USEC_ID identify the interface occurrence and usage calendar entries being processed; UNIT_SEC_CROSS_UNIT_SEC_ID and UOO_ID link the cross-unit scheduling relationship and its parent unit offering option. ROW_ID returns the ROWID pseudo-column for each staged row, allowing procedural code to address records directly.

Key Columns

Common Use Cases and Queries

Typical uses include pre-import validation, error recovery, and auditing schedule changes from legacy or external systems. A query isolating rows flagged for TBA holds is the most direct response to the "tba_status" lookup:

  • SELECT ROW_ID, UNIT_CD, VERSION_NUMBER, SCHEDULE_STATUS, TBA_STATUS, ERROR_TEXT FROM APPS.IGS_PS_SCH_INT WHERE TBA_STATUS IS NOT NULL AND SCHEDULE_STATUS = 'ERROR';
  • SELECT UNIT_CD, UNIT_TITLE, TRANSACTION_TYPE, SCHEDULE_STATUS FROM APPS.IGS_PS_SCH_INT WHERE TRANSACTION_ID = :p_transaction_id ORDER BY SEQUENCE_NUMBER;
  • SELECT BUILDING_ID, ROOM_ID, START_TIME, END_TIME FROM APPS.IGS_PS_SCH_INT WHERE UNIT_SECTION_OCCURRENCE_ID = :p_uso_id;
  • SELECT COUNT(*), SCHEDULE_STATUS FROM APPS.IGS_PS_SCH_INT GROUP BY SCHEDULE_STATUS;

Because the view is multi-org enabled, operators must set the correct operating unit before execution or results will silently exclude rows belonging to other units.