PIMS data files are loaded centrally (CSUHR03A). All campuses PIMS data will be contained in a single file. The data file is loaded to staging tables if another file is not in progress. If another file is in progress rows are written to a history table so that campuses can request previously loaded files at a future date. This feature allows campuses to work their data files independently of the file load schedule.

If the staging tables have been cleared by a campus, the central load (CSUHR03A) will load the staging tables for that campus. If a campus has not cleared their staging tables prior to the centralized load, or if they have prior data files that need to be worked first, the central load will not load the staging tables but will write history rows for that campus. When the Campus has cleared the staging tables, they will run (CSUHR03B) to pull the history rows from the initial load into the staging tables where validations will be done.

The system forces data files to be loaded in the order they were centrally uploaded. The campus can manually request staging table loads any time after the centralized data file has been uploaded using CSUHR03B.

Example

Weekly files are typically Prob to Perm and you will receive an email from [email protected] that lists each campus and the number of transactions that campus will have. These files load automatically clear through Job Data: You are only verifying what loaded and what created exceptions that you will need to manually key.

If we have SSI/GSI’s there will typically be a CO Tech Letter accompanying these files and communication will happen at the Sub-Committee calls leading up to file delivery.

The following diagram shows the process flow for the campus user.