Search Results alternate_code




Overview
Explore in AI Chat

Overview

IGS_CA_INST_ADM_PERD_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Student System / Enterprise Transaction Management (ETRM) calendar functionality. It presents admission calendar instances together with their related academic calendar instances, exposing both the subordinate admission period and the superordinate (parent) academic period on a single row. The view is restricted to calendar types whose calendar category (S_CAL_CAT) is 'ADMISSION' for the primary instance and 'ACADEMIC' for the related instance, using an outer join so that admission periods without a linked academic parent are still returned.

Its role is primarily read-only reporting and integration: it allows reports, concurrent programs, OAF pages, and external interfaces to retrieve admission period data, including status, start and end dates, and the alternate code, without having to re-implement the multi-table join logic. The presence of the ALTERNATE_CODE column, and the derived concatenation of the parent and child alternate codes, makes the view particularly relevant to searches involving "alternate_code," since it surfaces the descriptive identifier assigned to each calendar instance.

Underlying Base Objects

The view is defined over five base tables, joined as follows:

No additional base objects are documented in the ETRM metadata; the view is a straightforward projection over the calendar instance and calendar type tables.

Key Columns

  • CAL_TYPE / SEQUENCE_NUMBER — composite key identifying the admission calendar instance.
  • DESCRIPTION — description of the admission calendar type.
  • START_DT / END_DT — effective start and end dates of the admission period.
  • CAL_STATUS — status of the admission calendar instance.
  • ALTERNATE_CODE — the user-defined alternate identifier for the admission instance. This is the column most commonly used to search or reference a period by a recognizable code rather than by a numeric sequence.
  • PRIOR_CI_SEQUENCE_NUMBER — reference to the preceding calendar instance in the admission sequence.
  • SUP_CAL_TYPE / SUP_CI_SEQUENCE_NUMBER — the parent academic calendar type and instance sequence.
  • The two additional date columns — the parent academic instance START_DT and END_DT (from ci2).
  • ALTERNATE_CODE (parent) and ALTERNATE_CODE || '/' || ALTERNATE_CODE (child) — the parent's alternate code, plus a derived concatenated path of parent and child alternate codes, useful for hierarchical display.
  • Audit columns — WHO columns from ci1 for change tracking.

Common Use Cases and Queries

Typical usage includes listing all admission periods for a given academic year, validating admission period dates before term setup, and resolving an alternate code back to a calendar sequence for integration payloads.

  • Retrieve admission periods by alternate code: 
    SELECT cal_type, sequence_number, alternate_code,
       start_dt, end_dt, cal_status
FROM   apps.igs_ca_inst_adm_perd_v
WHERE  alternate_code = :p_alternate_code;
  • List admission periods with their parent academic period: 
    SELECT alternate_code, description, start_dt, end_dt,
       sup_cal_type, sup_ci_sequence_number
FROM   apps.igs_ca_inst_adm_perd_v
WHERE  cal_status = 'ACTIVE';
  • Report the concatenated parent/child alternate code path for hierarchical reporting: 
    SELECT alternate_code, description,
       ci2_alternate_code_display
FROM   apps.igs_ca_inst_adm_perd_v;

Because the relationships to the parent academic instance are outer joins, queries should not assume a parent row always exists; SUP_CAL_TYPE, SUP_CI_SEQUENCE_NUMBER, and the parent alternate code may be NULL for admission periods that have no defined academic parent. The view is a query-only object and should be used for reads; inserts and updates must target the underlying IGS_CA_INST and IGS_CA_INST_REL tables directly.