Results for “igs_fi_fd_src_rstn_h”

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

Overview

The view IGS_FI_FD_SRC_RSTN_H belongs to the Oracle E-Business Suite Student System (IGS) product family, a module that has since been classified as obsolete in the ETRM reference for releases 12.1.1 and 12.2.2. The view exposes historical funding-source restriction data tied to academic course offerings, presenting rows drawn from the underlying history table that carries the _H suffix convention used throughout EBS for audit and version-tracking purposes. Its role in reporting and integration is to provide a filtered, organization-secured projection of funding source restriction records so that downstream forms, concurrent programs, and reporting queries can retrieve restriction history without directly accessing the base table. The view applies a multi-tenant security predicate on ORG_ID, ensuring that only records belonging to the current operating unit context are visible to the session.

Underlying Base Objects

The view is defined over a single base object, IGS_FI_FD_SRC_RSTN_H_ALL, which stores the historical rows for funding source restrictions with an _ALL designation indicating that the table is partitioned by operating unit. The view does not introduce any joins or aggregations; instead, it projects every column of the base table and attaches a ROWID alias exposed as ROW_ID. The _H suffix on both the table and the view denotes a history or audit construct. In typical EBS date-tracked designs, a corresponding _ALL table holds current rows while the history table stores prior versions created when records are date-tracked or updated. The WHERE clause enforces row-level security by comparing ORG_ID to a value decoded from the USERENV('CLIENT_INFO') session attribute, defaulting to -99 when no valid organization context is present. This pattern is the standard multi-org view (MORG) security mechanism generated by the Oracle Application Object Library.

Key Columns

• ROW_ID — The physical ROWID of the underlying history row, useful for direct row identification and de-duplication.
• COURSE_CD — The academic course code to which the funding source restriction applies.
• VERSION_NUMBER — The version of the course offering associated with the restriction record.
• FUNDING_SOURCE — The funding source identifier being restricted.
• HIST_START_DT / HIST_END_DT — The effective date range for this historical version of the restriction record.
• HIST_WHO — The user or process that created the historical version.
• DFLT_IND — A flag indicating whether the funding source is the default for the course/version.
• RESTRICTED_IND — A flag indicating whether the funding source is restricted.
• ORG_ID — The operating unit that owns the record; drives the view's security predicate.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns providing audit traceability.

Common Use Cases and Queries

The view is typically queried to audit how funding source restrictions on courses have changed over time, to reconcile historical student funding eligibility, or to support migration and data-conversion programs that must reconstruct prior restriction states. Because the view enforces ORG_ID security, queries must be run within a session that has an appropriate operating unit context, otherwise the ORG_ID comparison resolves to -99 and no rows are returned. A representative query retrieving restriction history for a specific course and version is:

SELECT course_cd, version_number, funding_source, dflt_ind, restricted_ind, hist_start_dt, hist_end_dt FROM igs_fi_fd_src_rstn_h WHERE course_cd = :course AND version_number = :version ORDER BY hist_start_dt DESC;

To identify all restricted funding sources currently flagged as default, an analyst might filter as follows:

SELECT course_cd, version_number, funding_source FROM igs_fi_fd_src_rstn_h WHERE restricted_ind = 'Y' AND dflt_ind = 'Y';

These patterns recur in IGS funding and registration reporting. Given the module's obsolete status, new development should target supported successor objects, but legacy reports and interfaces may still reference this view.