Search Results igs_ps_fld_of_study




Overview

The view IGS_PS_FLD_OF_STUDY belongs to the IGS – Student System product family within Oracle E-Business Suite. In the ETRM documentation set for releases 12.1.1 and 12.2.2, this object is explicitly flagged as Obsolete, and the documented implementation status is "Not implemented in this database." This status is significant for any implementer or report developer encountering the object: the view is a legacy artifact preserved in the data dictionary documentation rather than an active, supported database object in the current environment.

Functionally, the view was designed to present the institution's catalog of fields of study (also known as programs of study or academic subject areas) alongside a decoded description of each field's type. It joins the base table that stores field-of-study definitions with the generic Oracle lookups table so that the single-letter-ish type code (FOS_TYPE_CODE) is resolved to its human-readable meaning. This decoding pattern is typical of EBS reporting views, which are intended to shield report writers and integration interfaces from having to perform the lookup join themselves. Because the object is documented as obsolete, it should be treated as a reference for understanding legacy data models rather than as a component to build new reports against.

Underlying Base Objects

The documented view text defines the object over two sources joined with an equality predicate:

  • IGS_PS_FLD_OF_STUDY_ALL, aliased as TAB — the primary base table holding the field-of-study records, including the organization identifier ORG_ID. The presence of ORG_ID and the _ALL naming convention indicate multi-organization (partitioned) data, where each operating unit owns its own set of rows.
  • IGS_LOOKUP_VALUES, aliased as US — the standard EBS lookup values table, restricted to LOOKUP_TYPE = 'PS_FOS_TYPE_CD'.

The join condition is TAB.FOS_TYPE_CODE = US.LOOKUP_CODE. The ETRM record lists no further referenced base objects beyond these two, and the ROW_ID column is sourced from the underlying ROWID of IGS_PS_FLD_OF_STUDY_ALL. Of particular note is the documented status that no base objects are implemented in the database, consistent with the obsolete classification of the view itself. Consequently, any historical dependency on these tables must be verified against the actual instance rather than assumed from documentation.

Key Columns

The view exposes the following documented columns:

  • ROW_ID — the physical row identifier of the underlying base table row.
  • FOS_TYPE_CODE — the code classifying the field of study, drawn from the base table.
  • FOS_TYPE_CODE_DESC — the decoded meaning of the type code, sourced from IGS_LOOKUP_VALUES.MEANING.
  • FIELD_OF_STUDY — the name or code of the field of study itself.
  • DESCRIPTION — a longer textual description of the field of study.
  • GOVT_FIELD_OF_STUDY — the government-designated classification for the field, used for regulatory reporting.
  • CLOSED_IND — a flag indicating whether the field of study is closed to new enrolment or use.
  • ORG_ID — the operating unit that owns the record, enabling multi-organization filtering.
  • Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Historically, this view would have been used to populate validation lists of fields of study on student enrolment forms, to decode field-of-study types in extract reports, and to supply government reporting extracts where a mapping between institutional and governmental classifications is required. A representative query, filtered for active fields within a single operating unit, follows:

SELECT fos_type_code_desc, field_of_study, description, govt_field_of_study FROM igs_ps_fld_of_study WHERE closed_ind = 'N' AND org_id = :p_org_id ORDER BY field_of_study;

Because the object is documented as obsolete and not implemented, developers should confirm its existence before use and prefer any current replacement object supplied by the Student System module. Where the view remains present in a legacy instance, restricting queries by ORG_ID and CLOSED_IND is essential to avoid returning closed or cross-organization records.