Search Results igs_ca_inst_seq_num_s

Overview

IGS_CA_INS_ROLL_CI is a server-side PL/SQL package body owned by the APPS schema within the Oracle E-Business Suite student system, specifically the Student Records / Calendar and Attendance (IGS_CA) product family. The package encapsulates the business logic required to perform rolling of calendar instances — the process of advancing or re-deriving scheduled calendar instances such as teaching periods, attendance instances, and related date-driven records to reflect a new or revised calendar position. Its internal naming convention, in which multiple procedures share the prefix CALP_INS_ROLLVR, indicates that the package is a validation and rollover engine layered on top of the IGS_CA_INST entity and its associated API (IGS_CA_INST_PKG). A specialist validation procedure, CALP_VAL_APCOOD_ROLL, and a combined control procedure, CHK_AND_ROLL_RET, suggest the package is invoked not as an isolated utility but as part of a wider rollover process that must first check whether instances are eligible to roll. The object is classified as OTHER rather than a formally published public API, and it is referenced by no other database object, which indicates it is a leaf-level implementation package invoked by forms, concurrent processes, or higher-level calendar administration logic.

Key Procedures and Functions

The documented program units fall into two functional groups.

• CALP_INS_ROLLVR_DAIP — Rolls calendar instances in conjunction with date-adjustment or period-position data, coordinating the insertion and update of the underlying instance records.
• CALP_INS_ROLL_DAIOC — Performs the rollover of calendar instances for the DAIOC context, handling the offset/count relationship between parent and child instances.
• CALP_VAL_APCOOD_ROLL — Validates that the supplied attendance-period or calendar configuration data (APCOOD) is permissible before a rollover proceeds; it is the gatekeeper routine that prevents invalid rollover requests from reaching the instance tables.
• CALP_INS_ROLLVR_DAIO — Executes the rollover for the DAIO variant, applying offset logic across the instance hierarchy.
• CALP_INS_ROLLVR_DAI — Executes the core date-adjustment-instance rollover, propagating changed dates to dependent instance records.
• CALP_INS_ROLLVR_CIR — Handles rollover in relation to calendar instance relations (CIR), maintaining the integrity of parent/child and successor relationships after dates change.
• CALP_INS_ROLLVR_CI — The principal calendar-instance rollover routine, applying the cumulative roll logic across the instance set.
• CHK_AND_ROLL_RET — A control routine that checks return schedule conditions and performs the rollover; it is the entry point most likely to be invoked externally to validate and then roll a set of instances in a single call.

Tables Accessed

The package operates extensively on the Calendar and Attendance instance model. IGS_CA_INST is the primary instance table that is read and updated during rollover. IGS_CA_INST_REL and its supporting synonym IGS_CA_INST_REL_SUP_CI_SNO_S1 preserve relationships between rolled instances. Sequence and surrogate-key tables — IGS_CA_INST_SEQ_NUM_S, IGS_CA_INST_SEQ_NUM_S1, and IGS_CA_DA_INST_SEQ_NUM_S — supply instance sequence numbers. The DA-layer tables IGS_CA_DA_INST, IGS_CA_DA_INST_OFCNT, IGS_CA_DA_INST_OFST, and IGS_CA_DA_INST_PAIR hold instance offsets, counts, and pairing data used to propagate dates. Reference tables IGS_CA_STAT and IGS_CA_TYPE supply instance status and calendar type codes, while IGS_AD_PECRS_OFOP_DT provides attendance period/date reference data. IGS_FI_TP_RET_SCHD supports return-schedule logic, and IGS_GE_S_LOG_ENTRY records processing log entries. DUAL is used for single-row lookups.

Usage Notes

IGS_CA_INS_ROLL_CI is not a published public API and is not referenced by any other database object; it is therefore invoked indirectly. Typical entry points are Oracle Forms in the Calendar and Attendance administration set, and concurrent programs that perform mass calendar rollover for an academic period. Custom extensions should not call it directly, because parameter contract and internal validation sequence are undocumented; instead, invoke the supported IGS_CA_INST_PKG API and let it delegate to this package. Because the package writes to IGS_CA_INST and relation tables, it must be run within a controlled transaction, and callers should expect validation failures delivered through FND_MESSAGE and IGS_GE_MSG_STACK, with execution trace written to FND_LOG and IGS_GE_S_LOG_ENTRY.