Overview

All of the processes documented here are self-contained within the CEREPORTS and impact data that is stored locally on the database server. This can include processes that create lookup tables, or clean and process data in some way, and is triggered by an automated execution either on the server or externally.

Process List

Table Creation

Technical Details

Build procedure: vw_table_build

Dependencies:

• Procedures: vw_admissions_summary_build, vw_sps_enrollment_build, vw_sps_enrollment_trcl_build, vw_mkt_unified_build
• Views: a1_admissions_summary, a1_sps_enrollment, a1_sps_enrollment_trcl
• Tables: sys_logging

Cadence: Runs each morning at 7:30am

Trigger: Executed through Crystal Reports scheduler (DEV)

Location: Crystal / All Folders / SPS - School of Professional Studies / Feeds

Overview

This is a centralized procedure developed to create local tables based on views of data that are used regularly as the basis for SPS reporting and queries. These tables are then indexed to improve performance across the reporting landscape.

Outputs

The following tables are created when the procedure is successfully executed:

• Daily
  • vw_admissions_summary
    • All admissions related data in a consolidated table. Used in Power BI reports such as the ASR, and any others that require admissions statuses, such as admits, commits, etc.
    • This table is a drop-in replacement for any procedure using the a1_admissions_summary view as a source
  • vw_sps_enrollment
    • All SPS students across terms based on courses in the TOOK table
    • This table is a drop-in replacement for any procedure using the a1_sps_enrollment view as a source
  • vw_sps_enrollment_trcl
    • All SPS students across terms based on transactions in the TRCL table (regardless of TOOK attendance)
    • This table is a drop-in replacement for any procedure using the a1_sps_enrollment_trcl view as a source
• Weekly
  •  RPT_MKT_UNIFIED
    • Static aggregation table of marketing related information from imported Slate tables (RPT_%)

The following table is updated when the procedure is successfully executed:

• sys_logging
  • Results of each execution are stored in the the sys_logging table for troubleshooting and validation of each build