Search Results max_terms

Overview

The view APPS.IGS_EN_STDNT_PS_INTM_V is a supplementary database view within the Oracle E-Business Suite (EBS) Student System (IGS) product family. As documented in the ETRM metadata, the object is a VIEW owned by the APPS schema, registered under the FND Design Data reference IGS.IGS_EN_STDNT_PS_INTM_V, and carries a status of VALID. Its designated purpose is to simplify forms coding within the Student System, exposing student program intermission data in a denormalized, presentation-ready form.

The view presents records relating to student program intermissions — periods during which a student's enrollment in a program is temporarily suspended. Its role in Oracle EBS reporting and integration is to provide a single, transaction-level read interface for intermission records, enriched with descriptive attributes such as intermission type descriptions, institution names, and approver details, so that developers need not re-implement joins against multiple base tables. Oracle explicitly cautions that this is a supplementary view intended for forms coding, and that direct querying or alteration of its data is not recommended, since the view definition may change substantially between minor or major releases.

Underlying Base Objects

The ETRM metadata for this object does not document any referenced base objects. In practice, the column set indicates that the view is defined over intermission records in the Student System, with joins to person, course, institution, and intermission-type lookup entities to resolve the descriptive columns. The leading columns — ROW_ID (ROWID), PERSON_ID, and COURSE_CD — identify the owning student and the course context of the intermission. The presence of standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and a full Descriptive Flexfield column set (ATTRIBUTE_CATEGORY and ATTRIBUTE1 onward) confirms that the view is built on a transactional, DFF-enabled base table rather than an interface or staging table. Because the concrete base tables are not documented here, integration code should treat the view as an opaque, release-versioned contract and avoid assuming the existence of any specific underlying table names.

Key Columns

• ROW_ID — ROWID of the underlying row, exposed for forms row-identification purposes.
• PERSON_ID / COURSE_CD — Identity of the student and the course to which the intermission applies.
• INTERMISSION_TYPE / DESCRIPTION — Coded value and its decoded description for the type of intermission.
• APPROVED / APPROVER_ID / APPROVER_NUMBER / APPROVER_NAME — Approval status, and the identifier, number, and name of the approving party.
• INSTITUTION_CD / INSTITUTION_NAME — Code and name of the institution associated with the record.
• MAX_TERMS — Maximum number of terms accepted for Advanced Standing. This is the column most directly relevant to the search term "max_terms", and it typically holds the cap on terms that may be granted toward the student's program.
• MAX_CREDIT_PTS / ANTICIPATED_CREDIT_POINTS — Maximum credit points accepted for Advanced Standing, and the credit points anticipated to be completed at the other institution.
• START_DT / END_DT — Start and end dates of the intermission; LOGICAL_DELETE_DATE indicates logical deletion.
• VOLUNTARY_IND / COMMENTS — Voluntary-indicator flag and free-text remarks.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1…ATTRIBUTE_n — Descriptive Flexfield segments.

Common Use Cases and Queries

Typical uses include forms-based maintenance of intermission and advanced-standing data, reporting on approved intermissions by institution, and verification of advanced-standing limits. Standard practice is to filter on LOGICAL_DELETE_DATE IS NULL to exclude logically deleted rows.

A representative query retrieving maximum terms for a student's intermissions:

• SELECT person_id, course_cd, intermission_type, max_terms, max_credit_pts, approved
• FROM  apps.igs_en_stdnt_ps_intm_v
• WHERE person_id = :p_person_id
• AND   logical_delete_date IS NULL;

For aggregated advanced-standing reporting by institution:

• SELECT institution_cd, institution_name, COUNT(*) intermissions, SUM(max_terms) total_max_terms
• FROM  apps.igs_en_stdnt_ps_intm_v
• WHERE approved = 'Y' AND logical_delete_date IS NULL
• GROUP BY institution_cd, institution_name;

Because the view is documented as supplementary and subject to change, production integrations should encapsulate access within a wrapper view or PL/SQL API rather than binding directly to it.