Results for “igs_ps_tch_resp_hist”
19 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IGS_PS_TCH_RESP_HIST is a reporting view belonging to the IGS (Student System) product family in Oracle E-Business Suite. It exposes the historical records of teaching responsibility assignments, capturing how the distribution of teaching responsibility for a given unit and version has changed over time. In the Oracle EBS data model, teaching responsibility data links academic units to the organizational units (and by extension, the persons or departments) responsible for delivering them. The history view preserves each prior state of that relationship as a dated, auditable record.
The ETRM metadata classifies this object under "IGS - Student System (Obsolete)," and the implementation note for the documented environment states "Not implemented in this database." This is a critical point: the view is legacy and may or may not be deployed depending on the specific installation and patch level. Customers on 12.1.1 or 12.2.2 should verify existence against ALL_VIEWS or the data dictionary before relying on it in custom reporting or integration code. Where it does exist, its role is confined to read-only reporting and historical analysis; it is not a transactional entry point.
Underlying Base Objects
The view is defined over a single documented base object, IGS_PS_TCH_RESP_HIST_ALL. The _ALL suffix indicates that the base table is partitioned by operating unit, carrying an ORG_ID column. The view applies a Multi-Org security predicate that filters rows against the operating unit resolved from the client_info session attribute, using the standard Oracle Applications NVL/DECODE/SUBSTRB pattern. Records are compared against the current operating unit value (or -99 when none is resolvable), so the view returns only rows visible to the caller's Multi-Org context.
No additional base tables, synonyms, or joins are documented for this view. Because the view supplies rows via the base table's ROWID (aliased ROW_ID) and selects directly from a single _ALL table, it functions as a thin, security-filtered projection rather than a denormalized reporting layer. Consequently, the view inherits the temporal semantics of the base table: each row represents a versioned history segment, bounded by HIST_START_DT and HIST_END_DT, rather than a live assignment.
Key Columns
- ROW_ID — the physical ROWID of the underlying history row; useful for direct row identification but not a business key.
- UNIT_CD — the code of the academic unit or teaching unit to which the responsibility applies.
- VERSION_NUMBER — the version of the unit record; teaching responsibility history is versioned alongside the unit itself.
- ORG_UNIT_CD — the code of the organization unit responsible for the unit at that point in time.
- OU_START_DT — the effective start date of the organization unit relationship.
- HIST_START_DT / HIST_END_DT — the validity window of the historical row; the pair defines when this version of the responsibility record was in effect. A null HIST_END_DT typically denotes the current segment.
- HIST_WHO — the user or process that created the historical record, providing an audit trail.
- PERCENTAGE — the share of teaching responsibility attributed to the organization unit; useful for workload or contribution reporting.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle Applications who-columns for audit and change tracking.
- ORG_ID — the operating unit identifier used by the Multi-Org security predicate.
Common Use Cases and Queries
Typical usage centers on reconstructing the historical allocation of teaching responsibility for a unit, auditing changes to organizational ownership, and feeding downstream workload or accreditation reports. A basic as-of query selects the segment active on a given date:
SELECT unit_cd, version_number, org_unit_cd, percentage, hist_start_dt, hist_end_dt
FROM igs_ps_tch_resp_hist
WHERE unit_cd = :unit_cd
AND :as_of_date BETWEEN hist_start_dt AND NVL(hist_end_dt, :as_of_date);
To identify the current effective segment, filter on a null end date:
SELECT unit_cd, version_number, org_unit_cd, percentage
FROM igs_ps_tch_resp_hist
WHERE hist_end_dt IS NULL
AND unit_cd = :unit_cd;
An audit query listing all changes for a unit, ordered chronologically by history window, supports change-tracking and reconciliation reporting. Because the view enforces Multi-Org security automatically, reports should not add their own ORG_ID predicate unless intentionally cross-operating-unit analysis is required. Given the object's obsolete classification and possible non-implementation, applications should treat IGS_PS_TCH_RESP_HIST as a legacy artifact, validate its presence in the target environment, and prefer current student-system APIs or tables for new development.
-
View: IGS_PS_TCH_RESP_HIST 12.1.1
APPS.IGS_PS_TCH_RESP_HIST·↳ IGS_PS_TCH_RESP_HIST_ALL·Explore IGS module →
-
View: IGS_PS_TCH_RESP_HIST 12.2.2
Not implemented in this database·Explore IGS module →
-
View: IGS_PS_TCH_RESP_HIST_V 12.1.1
This view is used to merge teaching responsibility history with the current teaching responsibility details enabling all details to be accessed over time, up till the current day.
APPS.IGS_PS_TCH_RESP_HIST_V·↳ IGS_AU_GEN_004·↳ IGS_PS_TCH_RESP·↳ IGS_PS_TCH_RESP_HIST·Explore IGS module →
-
View: IGS_PS_TCH_RESP_HIST_V 12.2.2
This view is used to merge teaching responsibility history with the current teaching responsibility details enabling all details to be accessed over time, up till the current day.
Not implemented in this database·Explore IGS module →
-
PACKAGE: APPS.IGS_AU_GEN_004 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.