Results for “igs_as_cal_conf”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_AS_CAL_CONF is a configuration table within the IGS (Student System) product family, historically associated with the Oracle Student System applications that were delivered alongside Oracle E-Business Suite 12.1.1 and, where still present, 12.2.2. Its documented description states that it holds control calendar reference details, meaning the table stores the date-alias bindings that govern how key academic calendar milestones are resolved for assessment processing. In the ETRM 12.1.1 documentation the object is flagged as obsolete, and the implementation note states that it is not implemented in the reference database, so it should be treated as a legacy or dormant object in most environments.

From a dimensional or Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is a link table. This suggestion is consistent with its role: the table does not carry a natural business attribute hierarchy of its own, but rather connects a control identifier to a set of calendar date definitions held in a separate reference table. Under a hub/link/satellite model, IGS_AS_CAL_CONF would sit as an associative link joining the control context to calendar date aliases, with descriptive and audit attributes belonging in a satellite.

Key Information Stored

The documented physical schema for 12.1.1 shows the table owned by IGS with 13 columns. The most important of these are:

• S_CONTROL_NUM — the surrogate primary key column, named in the primary key constraint IGS_AS_CAL_CONF_PK and also carried by the unique index IGS_AS_CAL_CONF_U1, making it both the surrogate identifier and the primary business-key candidate.
• ASS_ITEM_CUTOFF_DT_ALIAS — the calendar date alias marking the assessment item cutoff point.
• MID_MGS_START_DT_ALIAS and MID_MGS_END_DT_ALIAS — aliases delimiting the mid-term mark/grading start and end window.
• EFINAL_MGS_START_DT_ALIAS and EFINAL_MGS_END_DT_ALIAS — aliases for the early final mark/grading start and end window.
• FINAL_MGS_START_DT_ALIAS and FINAL_MGS_END_DT_ALIAS — aliases for the final mark/grading start and end window.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard EBS audit columns recording row creation and last modification.

All seven date alias columns reference the IGS_CA_DA table, so the table itself stores alias keys rather than literal dates. The unique index IGS_AS_CAL_CONF_U1 on S_CONTROL_NUM enforces one calendar configuration row per control number.

Common Use Cases and Queries

The principal use case is resolving the assessment calendar windows for a given control context during grading and assessment processing. A typical reporting query joins the configuration row to the date alias table to translate aliases into actual dates:

• Configuration lookup: SELECT * FROM igs_as_cal_conf WHERE s_control_num = :control_num;
• Alias resolution for final grading: join igs_as_cal_conf c to igs_ca_da d on c.final_mgs_start_dt_alias = d. and similarly for the end alias, to obtain the active start and end dates.
• Audit reporting: filter on LAST_UPDATE_DATE or CREATED_BY to identify when calendar control configurations were last changed.
• Completeness checks: confirm that no alias column is null for a populated control number, since nulls would break downstream date resolution.

Because the object is documented as not implemented, these queries are primarily relevant to legacy data migrations, historical analysis, or environments where the Student System tables were retained.

Related Objects

The dominant relationship is to the calendar date alias table, which is referenced seven times from this object. The significant related objects are:

• IGS_CA_DA — referenced by ASS_ITEM_CUTOFF_DT_ALIAS, MID_MGS_START_DT_ALIAS, MID_MGS_END_DT_ALIAS, EFINAL_MGS_START_DT_ALIAS, EFINAL_MGS_END_DT_ALIAS, FINAL_MGS_START_DT_ALIAS, and FINAL_MGS_END_DT_ALIAS.

These seven foreign keys all target the same reference table and represent the primary dependency path for any join. Because the ETRM excerpt does not enumerate inbound references to IGS_AS_CAL_CONF, no additional child tables, views, or APIs can be asserted from the documented metadata.