Results for “igs_ps_rsv_orgun_prf”

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

Overview

IGS_PS_RSV_ORGUN_PRF is a Student System (IGS) table in Oracle E-Business Suite that stores the preferences associated with a specific priority level for reserved seating at the organization unit level. Within the Academic Reservation model, it defines how reserved seats are allocated when a given organization unit and priority combination is evaluated. The table is documented as obsolete in the ETRM repository and is noted as "Not implemented in this database," meaning its presence depends on whether the relevant reservation functionality was ever deployed in a given environment.

From a Data Vault modeling perspective, the FK structure suggests this object behaves as a link table. It sits between the organization-unit reservation priority entity and several referenced lookup or version entities, capturing the associative relationships that define reservation preferences rather than functioning as a standalone hub.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• RSV_ORG_UNIT_PRF_ID — the surrogate primary key, defined by IGS_PS_RSV_ORGUN_PRF_PK and backed by the unique index IGS_PS_RSV_ORGUN_PRF_U1.
• RSV_ORG_UNIT_PRI_ID — the foreign key to IGS_PS_RSV_OGPRI_ALL, tying the preference to a reservation priority.
• PREFERENCE_CODE and PREFERENCE_VERSION — the referenced preference definition and its version, used together in multiple foreign key relationships.
• PREFERENCE_ORDER — the sequence in which preferences are applied.
• PERCENTAGE_RESERVED — the proportion of reserved seating allocated under the preference.
• GROUP_ID — groups related preference records.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

The business-key candidate is defined by IGS_PS_RSV_ORGUN_PRF_U2, a composite unique index on RSV_ORG_UNIT_PRI_ID and PREFERENCE_CODE, distinct from the surrogate primary key.

Common Use Cases and Queries

Typical use cases include reporting on which preferences apply to a given reservation priority, auditing percentage allocations, and tracing preference definitions to their source. A representative query joining to the priority table is:

• SELECT p.RSV_ORG_UNIT_PRF_ID, p.RSV_ORG_UNIT_PRI_ID, p.PREFERENCE_CODE, p.PREFERENCE_ORDER, p.PERCENTAGE_RESERVED FROM IGS_PS_RSV_ORGUN_PRF p WHERE p.RSV_ORG_UNIT_PRI_ID = :pri_id ORDER BY p.PREFERENCE_ORDER;
• Joining to IGS_PS_VER_ALL on PREFERENCE_CODE and PREFERENCE_VERSION to resolve preference descriptions.
• Aggregating PERCENTAGE_RESERVED by GROUP_ID to validate total allocation per group.

Because the object is obsolete, queries should be validated against the actual schema before being used in production reporting.

Related Objects

• IGS_PS_RSV_OGPRI_ALL — referenced via RSV_ORG_UNIT_PRI_ID; the parent priority entity.
• IGS_PS_VER_ALL — referenced via PREFERENCE_CODE and PREFERENCE_VERSION.
• IGS_PS_STAGE_TYPE — referenced via PREFERENCE_CODE.
• IGS_EN_UNIT_SET_ALL — referenced via PREFERENCE_CODE and PREFERENCE_VERSION.

These foreign key relationships define the preference resolution chain that governs organization-unit reserved seating behavior.