Results for “int_occurs_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_PS_SCH_FACLT_ALL is a table in the IGS (Student System) product schema, owned by the IGS user in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores information about the facilities associated with a unit section occurrence for a particular transaction. In functional terms, this is the scheduling-facility assignment record that determines which physical rooms or resources are tied to a specific occurrence of a unit section, supporting room booking, capacity planning, and timetable reporting within the Student System.

The ETRM metadata classifies this object, by heuristic mining of its foreign key structure, as satellite-leaning. Under a Data Vault modeling approach, this suggests the table behaves as a satellite carrying descriptive attributes (facility code, description, and audit metadata) around a parent business key, rather than acting as an independent hub or a pure link. Its dependence on the parent occurrence identifier (INT_OCCURS_ID) reinforces this interpretation.

Key Information Stored

The table contains ten documented columns. The surrogate primary key is FACILITY_ID, enforced by the IGS_PS_SCH_FACLT_ALL_PK constraint. Unique index IGS_PS_SCH_FACLT_ALL_U1 also covers FACILITY_ID, which makes it the documented business-key candidate for uniqueness enforcement on the facility identifier.

• FACILITY_ID — surrogate primary key and business-key candidate; the unique internal identifier for each facility assignment record.
• FACILITY_CODE — the user-facing code used to reference the facility, typically a room or resource designation.
• FACILITY_DESCRIPTION — the descriptive name or textual detail of the facility associated with the occurrence.
• INT_OCCURS_ID — foreign key linking to IGS_PS_SCH_INT_ALL; identifies the specific unit section occurrence to which the facility belongs.
• ORG_ID — the operating unit or organization context, supporting multi-org partitioning of the record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns tracking who created and last modified the record and when.

Together, these columns establish both the identity of the facility assignment (FACILITY_ID) and its contextual anchor (INT_OCCURS_ID plus ORG_ID), with the audit columns providing the standard traceability required across IGS tables.

Common Use Cases and Queries

Typical reporting and integration scenarios resolve facilities for a given occurrence or locate all occurrences using a specific facility. A query joining the facility table to its parent occurrence follows the documented foreign key:

• Retrieve facilities for an occurrence: select f.FACILITY_ID, f.FACILITY_CODE, f.FACILITY_DESCRIPTION from IGS_PS_SCH_FACLT_ALL f where f.INT_OCCURS_ID = :occurrence_id.
• Join to the parent: select i.*, f.FACILITY_CODE from IGS_PS_SCH_INT_ALL i join IGS_PS_SCH_FACLT_ALL f on f.INT_OCCURS_ID = i.INT_OCCURS_ID.
• Org-scoped reporting: filter by ORG_ID to produce multi-org corrected facility utilization reports.
• Audit extraction: select FACILITY_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE for change-tracking or reconciliation processes.

These patterns support timetable publishing, room utilization analysis, and downstream interfaces that feed scheduling data into other systems.

Related Objects

The most significant related object is the parent occurrence table referenced by the documented foreign key.

• IGS_PS_SCH_INT_ALL — parent table referenced by IGS_PS_SCH_FACLT_ALL.INT_OCCURS_ID; the primary join partner for occurrence-level context.
• IGS_PS_SCH_FACLT_ALL_PK / IGS_PS_SCH_FACLT_ALL_U1 — the primary key constraint and unique index that enforce identity on FACILITY_ID.
• IGS_PS_SCH_FACLT_V — the conventional IGS validation view pattern for this table, used to enforce facility values in form-level validation (typical of _ALL base tables).
• Any IGS scheduling or term-based views and concurrent programs that consume unit section occurrence data typically read through this table via INT_OCCURS_ID.

Because the metadata documents only one foreign key, related-object coverage is intentionally narrow and centered on the occurrence parent and the table's own key constraints.