Search Results igs_as_gpc_aca_stndg




Overview
Explore in AI Chat

Overview

IGS_AS_GPC_ACA_STNDG is a table within the Oracle E-Business Suite Student System (IGS) product family, historically used to store grading period cohort academic standing details. In the context of Oracle EBS 12.1.1 and 12.2.2, this object belongs to the academic standing and progression tracking area of the Student System module, where institutions record the standing status of a cohort of students within a specific grading period. The table associates a progression status outcome with a grading period code, enabling academic administrators to evaluate whether groups of students met defined standards for advancement, probation, or dismissal during a given grading or academic period.

The ETRM documentation classifies this table as obsolete and confirms that it is not implemented in the reference database. Consequently, it exists only as a legacy or seed metadata definition rather than an active physical object in most 12.1.1 and 12.2.2 instances. Under the heuristic Data Vault classification supplied in the metadata, the table is identified as standalone, meaning its columns do not participate in the foreign key network of surrounding fact or link tables. As a modeling suggestion, this pattern is closest to a satellite-like structure keyed by a business attribute (grading period and progression status) rather than a true integration hub or link.

Key Information Stored

The documented physical schema contains eight columns. The most significant are:

The combination of GRADING_PERIOD_CD and PROGRESSION_STATUS is captured by the business-key candidate unique index IGS_AS_GPC_ACA_STNDG_U2, indicating that the pair is expected to be unique across the table. The remaining columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — are standard Oracle Applications who-columns providing audit and concurrency tracking for each row.

Common Use Cases and Queries

Because the table is obsolete and absent from active schemas, direct querying is generally limited to legacy data migration, archival reporting, or historical data model reviews. Where the object is present, typical query patterns retrieve academic standing by grading period or progression status:

  • Listing all progression statuses recorded for a given grading period.
  • Identifying grading periods associated with a particular progression status, such as a probationary standing.
  • Auditing who created or last updated specific academic standing rows for compliance purposes.

A representative SQL pattern joins the surrogate key to its business attributes:

SELECT GPC_ACA_STNDG_ID, GRADING_PERIOD_CD, PROGRESSION_STATUS FROM IGS_AS_GPC_ACA_STNDG WHERE GRADING_PERIOD_CD = :period_code;

Reporting use cases center on cohort-level standing summaries for academic review boards. Analysts should verify table existence and row counts before relying on these queries, as the metadata documents no implemented data.

Related Objects

The metadata classifies this table as standalone, so no foreign key dependencies are documented either to or from it. In practice, the business columns reference conceptual lookups rather than enforced constraints:

  • Grading period definitions — the IGS grading period lookup or related period table supplying GRADING_PERIOD_CD values.
  • Progression status lookups — the reference list providing valid PROGRESSION_STATUS codes.
  • Academic standing tables — related IGS_AS academic standing and cohort objects sharing the GPC_ACA_STNDG_ID naming convention.
  • Student progression records — student-level standing transactions that aggregate into cohort-level definitions represented here.

Because no enforced relationships exist, joins must be constructed manually against these reference objects, and any integration effort should confirm the object's availability in the target instance before proceeding.