Results for “igs_ps_tch_rsov_hist”

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

Overview

IGS_PS_TCH_RSOV_HIST is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema within the IGS – Student System product family (Oracle Student System, sometimes referenced as the Student Information Management module). The view exposes historical records of teaching resource allocations at the organisational unit level, where a teaching resource (staff member, instructor, or equivalent resource) has been assigned to a teaching activity and the assignment is subsequently closed and retained for audit and reporting purposes. The "_HIST" suffix signals that the rows are historical rather than current; records are created when a current teaching resource allocation changes or is superseded.

The object is registered as a VALID view in EBS 12.1.1 and 12.2.2. It supports reporting, extraction, and integration workloads that need to reconstruct teaching assignments as they existed over time, particularly with respect to effort allocation percentages and the organisational units responsible for delivery.

Underlying Base Objects

The view is defined over a single documented base object, IGS_PS_TCH_RSOV_HIST_ALL. The "_ALL" suffix indicates a multi-organisation (multi-org) table that carries an ORG_ID column, allowing records to be partitioned by operating unit or business unit. The view applies a Multi-Org security predicate against ORG_ID using USERENV('CLIENT_INFO'), extracting the first ten characters of the client info string and comparing it to the ORG_ID value; where the client info byte begins with a space, NULL is substituted, and both sides default to -99. This mirrors the standard EBS Multi-Org secured view pattern and means the visible row set is constrained to the organisation context of the session. The view does not introduce any joins or derived columns beyond selecting the columns of the base table and exposing the physical ROWID as ROW_ID.

Key Columns

• ROW_ID — the physical ROWID of the underlying row in IGS_PS_TCH_RSOV_HIST_ALL.
• UNIT_CD — the unit (course or teaching unit) code to which the teaching resource was assigned.
• VERSION_NUMBER — the version of the unit record associated with the allocation.
• CAL_TYPE — the calendar type (for example, standard academic year or teaching period) identifying the delivery cycle.
• CI_SEQUENCE_NUMBER — the calendar instance sequence number, tying the allocation to a specific teaching period instance.
• LOCATION_CD — the location where the teaching was delivered.
• UNIT_CLASS — the class or group within the unit to which the resource was assigned.
• ORG_UNIT_CD and OU_START_DT — the organisational unit code and its start date, defining the owning academic unit.
• HIST_START_DT, HIST_END_DT, HIST_WHO — the effective start and end dates of the historical record and the identifier of the user or process that created the historical version; these are the primary columns for point-in-time reporting.
• PERCENTAGE — the percentage of effort allocated to the resource for that assignment.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ORG_ID — the multi-org organisation identifier controlling row visibility.

Common Use Cases and Queries

Typical uses include auditing historical teaching allocations per organisational unit, reconciling effort percentages across teaching periods, and feeding downstream workload or costing models. A representative query filtered to a specific unit and period is:

• SELECT unit_cd, version_number, cal_type, ci_sequence_number, org_unit_cd, percentage, hist_start_dt, hist_end_dt FROM apps.igs_ps_tch_rsov_hist WHERE unit_cd = :unit_cd AND cal_type = :cal_type ORDER BY hist_start_dt;
• SELECT org_unit_cd, SUM(percentage) FROM apps.igs_ps_tch_rsov_hist WHERE hist_start_dt BETWEEN :from_date AND :to_date GROUP BY org_unit_cd;

Because the view is Multi-Org secured, queries executed under a valid organisation context return only rows for that operating unit; integrations that must span organisations should be executed in a context with appropriate access, or against the underlying _ALL table where policy permits.