Search Results acad_alternate_code




Overview
Explore in AI Chat

Overview

The view IGS_AD_DES_BATCH_DEF_DET_V belongs to the IGS – Student System product family within Oracle E-Business Suite. It is documented in the ETRM reference material as Obsolete, and the ETRM metadata explicitly states that it is not implemented in this database. This status indicates that the view was shipped in earlier releases of the Student System (typically 11i and early 12.1.x) but was superseded or removed in the 12.2.2 documentation baseline; therefore, it should not be expected to exist in a freshly provisioned 12.2.2 environment unless legacy customizations or preserved objects carry it forward.

Functionally, the view exposes admission decision batch definition details — the header-level or row-level context for a batch of admission decisions — enriched with descriptive lookups. Its role in reporting and integration is to present a denormalized, human-readable projection of the underlying admission batch detail table, resolving calendar instance references and code identifiers into names and descriptions. The user search term "acad_alternate_code" corresponds directly to a derived column in this view, which explains why it surfaces in metadata searches: the view materializes academic calendar alternate codes derived from IGS_CA_INST.

Underlying Base Objects

The view text is defined primarily over the base table IGS_AD_BATC_DEF_DET (aliased ABDD in the SQL), which stores admission batch definition detail rows. The documented metadata lists no other base objects explicitly, but the view text references the following additional objects through inline scalar subqueries and joins:

  • IGS_CA_INST (aliased CI1) — the calendar instance table, queried twice to resolve academic and admission calendar alternate codes.
  • IGS_AD_CODE_CLASSES — the admission code/class lookup table, queried for decision reason and pending reason names and descriptions.
  • A person table referenced as PE (truncated in the excerpt), supplying person number and full name for the decision maker.

Because the view joins these objects via correlated scalar subqueries rather than outer joins, its result set is preserved on the driving table IGS_AD_BATC_DEF_DET. The ETRM record documents the owner, referenced base objects, and dependencies as "none documented", reflecting the fact that the object is marked obsolete and its metadata was not carried into the 12.2.2 repository.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing batches of admission decisions, reconciling calendar alternate codes for reporting, and extracting decision maker and reason data for analytics. A representative query filtering on the academic alternate code is:

  • SELECT BATCH_ID, DESCRIPTION, ACAD_ALTERNATE_CODE, DECISION_MAKE_NAME, DECISION_REASON, DECISION_DATE FROM IGS_AD_DES_BATCH_DEF_DET_V WHERE ACAD_ALTERNATE_CODE = :p_acad_alternate_code;
  • SELECT BATCH_ID, COUNT(*) FROM IGS_AD_DES_BATCH_DEF_DET_V GROUP BY BATCH_ID; — batch-level decision volumes.
  • SELECT ADM_ALTERNATE_CODE, PENDING_REASON_DESC, COUNT(*) FROM IGS_AD_DES_BATCH_DEF_DET_V GROUP BY ADM_ALTERNATE_CODE, PENDING_REASON_DESC; — pending-decision analysis.

Because the object is obsolete and reported as not implemented, any query should be preceded by a check for its existence (for example, against ALL_VIEWS) and, where absent, the equivalent logic should be re-derived directly from IGS_AD_BATC_DEF_DET and IGS_CA_INST.