Search Results ucas_cycle




Overview
Explore in AI Chat

Overview

The IGS_UC_HRC_TIMSTMPS table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the UCAS (Universities and Colleges Admissions Service) integration modules. Owned by the IGS (iGrants) schema, this table functions as a control and audit mechanism for the Hercules data transfer process. Its primary role is to store individual timestamps for each distinct "Hercules View" within a specific UCAS application cycle. By tracking the last successful data extraction or synchronization timestamp per view and cycle, it ensures data integrity and prevents duplicate processing during the critical exchange of applicant information between the institution's EBS system and the UCAS service.

Key Information Stored

The table's structure is designed to capture the essential metadata for the Hercules view synchronization process. The key business columns are VIEW_NAME, UCAS_CYCLE, and TIMESTAMP. The VIEW_NAME (VARCHAR2(30)) identifies the specific Hercules data view or extract. The UCAS_CYCLE (NUMBER(15)) is a mandatory foreign key that links the timestamp to a specific admissions cycle, which is the central concept in the user's search context. The TIMESTAMP (DATE) records the point-in-time for that view's last successful data transfer. The table is secured by a unique primary key index (IGS_UC_HRC_TIMSTMPS_PK) on the combination of VIEW_NAME and UCAS_CYCLE, guaranteeing only one timestamp record per view per cycle. Standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide full auditability for all DML operations.

Common Use Cases and Queries

This table is primarily accessed by background concurrent processes responsible for generating and transmitting UCAS data extracts (Hercules files). A typical use case involves a process querying the table to determine if a specific view's data has changed since the last successful transmission for the active UCAS cycle. Common operational and reporting queries include retrieving the latest status for all views in a cycle or identifying views that may be stale or unsynchronized. A fundamental pattern is to join this table with the master UCAS cycle definition to filter for active cycles.

  • Check the last timestamp for all views in a specific UCAS cycle (e.g., 2025):
    SELECT VIEW_NAME, TIMESTAMP FROM IGS.IGS_UC_HRC_TIMSTMPS WHERE UCAS_CYCLE = 2025 ORDER BY VIEW_NAME;
  • Identify Hercules views that have not been updated within the last 24 hours for the current cycle:
    SELECT VIEW_NAME FROM IGS.IGS_UC_HRC_TIMSTMPS WHERE UCAS_CYCLE = 2025 AND TIMESTAMP < SYSDATE - 1;

Related Objects

Based on the provided dependency information, the IGS_UC_HRC_TIMSTMPS table does not reference other objects via foreign keys. However, it is a referenced object, meaning other application components depend on it. The metadata indicates it is referenced by an object named "IGS_UC_HRC_TIMSTMPS" under the APPS synonym. This typically implies the existence of a public synonym (IGS_UC_HRC_TIMSTMPS) pointing to the IGS.IGS_UC_HRC_TIMSTMPS table, which is used by EBS application code and reports. The most critical logical relationship is with the master table defining UCAS cycles (likely named IGS_UC_CYCLE or similar), where the UCAS_CYCLE column in this table is a foreign key. This relationship is essential for all cycle-specific timestamp queries.