Results for “acad_ci”
9 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IGS_PR_PERIOD_V is a reporting and integration view within the Oracle E-Business Suite student system (the Oracle Student System / OSS, historically delivered as the "IGS" schema). It presents progress calendar instances — the calendar periods that drive progression, progression-points calculation and related academic rules — enriched with the identity of the parent academic calendar instance to which each progress period is attached. In EBS 12.1.1 and 12.2.2 the view is owned by APPS and is queried from the APPS schema, so it is directly usable by concurrent programs, BI Publisher data templates, OAF pages, and interfaces without requiring qualification of the IGS base tables.
The view is essentially a join resolver: rather than forcing every report author to re-derive the relationship between a progress calendar instance and its superior academic calendar instance through IGS_CA_INST_REL, the view returns the progress period together with a concatenated academic/progress alternate code, its start and end dates, and its status. This makes it a convenient source for term- and period-listing pages where the academic year must be displayed alongside each progress period.
Underlying Base Objects
The view is defined over six base entities from the calendar model:
- IGS_CA_TYPE PRG_CAT — the calendar type of the progress calendar; restricted to rows where S_CAL_CAT = 'PROGRESS'.
- IGS_CA_INST PRG_CI — the progress calendar instance, supplying sequence number, dates, status, and audit columns.
- IGS_CA_STAT PRG_CS — the calendar status definition table, supplying the display status (S_CAL_STATUS).
- IGS_CA_INST_REL CIR — the instance relationship linking the progress instance (sub) to its academic instance (superior).
- IGS_CA_INST ACAD_CI — the superior academic calendar instance.
- IGS_CA_TYPE ACAD_CAT — the calendar type of the academic calendar; restricted to S_CAL_CAT = 'ACADEMIC'.
Joins are carried on CAL_TYPE and SEQUENCE_NUMBER throughout, and PRG_CI.CAL_STATUS is matched to PRG_CS.CAL_STATUS. Only progress instances that participate in an IGS_CA_INST_REL relationship with an academic instance are returned, so the view is effectively an inner-join projection and will not expose orphan progress periods.
Key Columns
- CAL_TYPE / SEQUENCE_NUMBER — the progress calendar type and its instance sequence number; together they form the instance surrogate key.
- START_DT / END_DT — the start and end dates of the progress period.
- ACAD_CI.ALTERNATE_CODE || '/' || PRG_CI.ALTERNATE_CODE — a composite display value combining the academic instance alternate code and the progress instance alternate code, useful for user-facing lists.
- CAL_STATUS / S_CAL_STATUS — the internal status code and its descriptive status text.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns, enabling change tracking and interface reconciliation.
Common Use Cases and Queries
Typical scenarios include generating lists of progression periods per academic year for validation before rollover, feeding BI Publisher reports that display progress period windows, and providing LOV/data sources for OAF pages that let administrators select a progress period.
A basic listing by academic year:
SELECT cal_type, sequence_number, start_dt, end_dt FROM apps.igs_pr_period_v WHERE start_dt BETWEEN :p_from AND :p_to ORDER BY start_dt;SELECT * FROM apps.igs_pr_period_v WHERE cal_status = 'ACTIVE';
Because the view drives off the relationship table, it is safe to join it to IGS_CA_INST or to attendance/assessment tables on CAL_TYPE/SEQUENCE_NUMBER when reconciling progress data against academic periods. Note that the view exposes no ORGANIZATION_ID or business-unit column, so it is not operating-unit secured; row-level restriction must be applied by the caller. It also does not surface academic-calendar dates directly — those must be obtained from IGS_CA_INST if required alongside the progress dates.
-
VIEW: APPS.IGS_PR_PERIOD_V 12.1.1
-
View: IGS_PR_PERIOD_V 12.2.2
Not implemented in this database·Explore IGS module →
-
View: IGS_CA_INST_PR_PERD_V 12.2.2
Not implemented in this database·Explore IGS module →
-
View: IGS_CA_INST_PR_PERD_V 12.1.1
APPS.IGS_CA_INST_PR_PERD_V·↳ IGS_CA_INST·↳ IGS_CA_INST_REL·↳ IGS_CA_STAT·Explore IGS module →
-
View: IGS_PR_PERIOD_V 12.1.1
APPS.IGS_PR_PERIOD_V·↳ IGS_CA_INST·↳ IGS_CA_INST_REL·↳ IGS_CA_STAT·Explore IGS module →
-
View: IGS_PR_SDT_PROG_PRD_V 12.2.2
Not implemented in this database·Explore IGS module →
-
View: IGS_PR_SDT_PROG_PRD_V 12.1.1
APPS.IGS_PR_SDT_PROG_PRD_V·↳ IGS_AS_SC_ATMPT_ENR·↳ IGS_CA_INST·↳ IGS_CA_INST_REL·Explore IGS module →