• N/A

1. The SQR loads a data file expected to hold transactions for all CSU campuses.
2. The data is extracted from the electronic file and loaded into a data-file history table.
3. For campuses with no data from a prior load in the staging tables, the staging table load processing proceeds.
4. A row is inserted into the tracking table to track that the data file for a campus has been loaded into the staging tables for processing.
5. The PIMS action is evaluated, and the correct procedure is called for either Prob-to-Perm or SSI/GSI transactions.
6. If the PIMS action is Prob-to-Perm and the validations are passed a row is inserted into the JOB records and the Prob-to-Perm loaded to JOB audit record, if the validations are not passed a row is inserted into the Prob-to-Perm exception record.
7. If the PIMS action is SSI/GSI a series of validations take place.
8. A temporary table is then loaded with all the SSI/GSI rows (even the rows that didn’t pass the validations).
9. The values are then selected out of the temporary table and the correct effective sequencing is determined (the greater effective sequencing is set to the greater comp rate).
10. The rows are then inserted into the SSI/GSI staging table. Transactions are given a status of Ineligible, Approved, Proposed or No Increase Given.
11. File reconciliation counts for the campus are calculated and stored in the tracking table.

1. This program is run only if the staging tables for a current load were not empty because the Campus is already working on a previous file.
2. The SQR selects data from the file history table for processing into the staging tables for a specific campus.
3. If the campus has no data from a prior load in the staging tables, the staging table load processing proceeds.
4. The PIMS action is evaluated, and the correct procedure is called for either Prob-to-Perm or SSI/GSI transactions.
5. If the PIMS action is Prob-to-Perm and the validations are passed a row is inserted into the JOB records and the Prob-to-Perm loaded to JOB audit record, if the validations are not passed a row is inserted into the Prob-to-Perm exception record.
6. If the PIMS action is SSI/GSI a series of validations take place.
7. A temporary table is then loaded with all the SSI/GSI rows (even the rows that didn’t pass the validations).
8. The values are then selected out of the temporary table and the correct effective sequencing is determined (the greater effective sequencing is set to the greater comp rate).
9. The rows are then inserted into the SSI/GSI staging table. Transactions are given a status of Ineligible, Approved, Proposed or No Increase Given.
10. File reconciliation counts for the campus are calculated and stored in the tracking table.

Navigation to the FTP Utility: CSU Tech Mods 🡪 FTP 🡪 FTP Utility

1. A user with Systemwide HR (SWHR) will Upload the file from SCO to the server folder using the delivered FTP process. This should only be accomplished by a central user to run the initial load. Campuses will not have access to run the initial load – CSUHR03A.
2. It is recommended that the user view the file prior to loading.
3. To Upload file, use the CSUID file folder since multiple campuses are included in the file
4. Ensure the file name is correct and has an extension = .txt – NOTE the txt file type is case sensitive and must be entered as lower case.

1. Central user will select the UPLOAD button once the correct folder and the file name has been entered.
2. A message will appear “STCMP_GEN_TEST.txt (name of test file) uploaded successfully”
3. When CSUHR03A initial load is complete, this import text file will be immediately removed from the location on the server where it has been placed.
4. User running the initial load MUST validate that this has happened by reviewing the log file generated in the View Log/Trace under details of the process monitor.

Navigation: Workforce Administration 🡪 CSU Workforce Admin Process 🡪CSU SSI/GSI, Prob-to-Perm 🡪 CSU Central L15 Load

A central person in SWHR will run the load (CSUHR03A) once the FTP process has uploaded the file for processing.

1. The Run control has a section to define the path and file name of the imported file from PIMS. The file path is /CSUFTPD/chr/chrftphdv/CSUID/filename.txt.
2. User can set a 14-character description (SSI-GSI Load Remarks) that will be inserted for the PAY increases to the employee history remarks (CSU_ITEM_215) located in PS_CSU_JOB. The remarks will NOT update the Prob-to-Perm (430) transactions.
3. The transactions are loaded into staging tables for evaluation and validations as long as the staging tables are empty. If Campuses are working on another file, the new rows will be loaded into a history table for use by Campuses later.
   1. Prob-to-Perm transactions will be inserted directly in the Job Data/Load to Job pages or Exception record depending on passing program validations
   2. All SSI/GSI rows are loaded to a central staging table even if the rows did not pass validations so that all rows are accounted for as long as staging tables are empty. If empty, the program will begin it’s line by line evaluation and validation for setting processing status and messages. If staging tables are not empty rows will be written to a history table for processing by Campus later when running CSUHR03B.

File Path

Update to CSU Item 215 on CSU Job

Check button for Action/Action Reason

After the file has been loaded to central staging tables, the file is deleted from the server location. User must check the out file to validate that the deletion has occurred within the text of the “%.out% file

“…File to delete: /CSUFTPD/chr/chrftphdv/STCMP/stcmp_gen.txt

Status of data file deletion = 0.000000

*** Successfully deleted data file. *** “

Navigation: Workforce Administration 🡪 CSU Workforce Admin Process 🡪CSU SSI/GSI, Prob-to-Perm 🡪 CSU Campus L15 Load

1. Campus can run CSUHR03B when they are ready to process transactions previously loaded as history rows when SWHR ran the initial load (CSUHR03A). However, once this process is run, Campuses cannot start another file until the current one is completed, and rows removed from the staging table using the last step in this Guide.
2. This process has the same evaluations and validations as CSUHR03A when reading the history table.
   1. Run only if the Current Date Loaded field is populated and there isn’t a message “file is in process”. Running CSUHR03B will pull the Campus specific transactions for the loaded date from history table into the Staging tables.
      1. Prob-to-Perm transactions will automatically process that are in file for this Campus when the CSUHR03A is run and will be loaded to the exception or loaded directly to job pages for the Prob-to-Perm transaction (430 transaction on file).
      2. General or Service Salary increases will be loaded to the SSI GSI Data page – and any transaction that passes the initial validation will be automatically set to APPROVED, even if there are retro rows after the insert of the increase by the program.
         1. Statuses will be set to Ineligible, Approved, Proposed or No Increase Given. Rows marked with a status other than Approved, can be manually fixed in Job and the process (CSUHR03B) rerun. No changes to rows in the SSI/GSI Data Page are available.
         2. The intent of this processing is that the program should load all approved transactions and stop retroactive updates when a change in the new job row warrants it.
         3. All stops will be written to the Exception record for review and manual updates to be done by the campus user.
         4. Transactions cannot be updated in the SSI/GSI Data page. The update is done manually. In Job.
         5. If the campus has completed all manual updates and reviews, then they should immediately close out the load date so that they can process the next file that had been loaded for them.

Navigation: Workforce Administration 🡪 CSU Workforce Admin Process 🡪CSU SSI/GSI, Prob-to-Perm 🡪 CSU L15 File Reconciliation

1. CSU L15 File Reconciliation page is delivered so that by the date loaded, a campus can see what they have processed and what is yet to be processed. They can see the total number of rows in the file-by-file load date.
2. There are two reconciliation tabs:
   1. Prob-to-Perm Reconciliation
   2. SSI/GSI File Load Summary
3. On both pages, there are two sections:
   1. Data File Row Totals
      1. The Data File Row Totals will display the total number of transactions that exist in the file loaded for the run date:
         1. Total File Row Count
            Total number of transactions
         2. Prob-to-Perm Row Total
            Total number of transactions sent for Prob-to-Perm for load date that is processed. Note: if no processing has begun, this will be zero.
         3. SSI/GSI Row Total
            Total number of transaction sent for either SSI and/or GSI increases for load date that is processed. Note: if no processing has begun, this will be zero.
   2. Subtotals
      1. Once the Campus has begun processing a load date, the counts for the Prob-to-Perm and/or SSI/GSI increase amounts will be displayed in the Load Sub-total section.
      2. The counts are updated with the CSUHR03A/B SQR, and the counts only will NOT be updated thereafter.
4. If, as in the snapshot below, the Reconciliation page indicates a total file row count, but no counts for either Prob-to-Perm or SSI/GSI Row totals -- this means that this file was loaded on the date indicated but is yet to be processed using CSUHR03B. The counts will be updated once the Campus part of the process (CSUHR03B SQR) is run.
5. The Reconciliation snapshot below shows that the Date Loaded has been processed and the counts are indicated for both Prob-to-Perm and SSI/GSI that have been processed.
6. This means that both the CSUHR03A and B SQRs have been processed.

Navigation: Workforce Administration 🡪 CSU Workforce Admin Process 🡪CSU SSI/GSI, Prob-to-Perm 🡪 CSU Prob to Perm Loaded to Job or CSU Prob to Perm Exceptions

A list of transactions that were loaded to Job for Prob to Perm are displayed on the Load to Job page for Campuses to review.

Transactions that may require Campus manual intervention are listed on the Exceptions page.

Navigation: Workforce Administration 🡪 CSU Workforce Admin Process 🡪CSU SSI/GSI, Prob-to-Perm 🡪 CSU SSI/GSI Loaded to Job or CSU SSI/GSI Retro Exceptions or CSU SSI/GSI Data

As part of the staging table load in CSUHR03B, Salary and General Service Increase transactions are loaded to the Campus Specific SSI GSI Data table. Status values Ineligible or No Increase Given are set for exception transactions. All other processable transactions are either set with a status of Approved or Proposed.

Campus users review all the transactions SSI GSI Data page. If applicable, exception transactions need to be researched and corrected manually via Job related data entry pages. Proposed transactions also need manual review and possible Job data modification. Once corrected, the status for Proposed transactions can be changed to Approved by re-running CSUHR03B. The PIMS Pay Change Update process will ignore the transaction without a status of Approved. The PIMS Pay Change Update process can be run multiple times, allowing the campus to work Proposed transactions in sub-sets.

Once all transactions have been addressed, through manual entry, the PIMS Pay Change Update process is run. The campus completes their processing by requesting the Clear Staging Tables process.

Campuses can review the pages above and if necessary, perform manual intervention.

Navigation: Workforce Administration 🡪 CSU Workforce Admin Process 🡪CSU SSI/GSI, Prob-to-Perm 🡪 CSU PIMS Pay Change Update

1. The CSUHR004 SQR will update Job data records for all “Approved” increase transactions from the SSI/GSI Salary Data staging table.
2. The Run control for the update to Job requires a Business Unit selection from for the user’s campus only.

1. The last step in the process is to remove selected history rows from the staging/temporary tables by Business Unit for the “Current Date Loaded” indicated in the field box.
2. If no date exists, then there is nothing to close, and no action is needed.
3. The run control will require a Business Unit selection from the user’s security access only.
4. When the record is selected in the run control, the history values will be removed by Business Unit and Load Date if the Completed flag is checked ON.

1. The following tables will have their values deleted/updated by Business Unit, Date Loaded, and Completed Flag = Yes:
   1. PS_CSU_SAL_PLN_AUD Delete: SSI/GSI audit table
   • PS_CSU_SAL_EXCPTN Delete: SSI/GSI exception table
   • PS_CSU_SALARY_PLAN Delete: SSI/GSI staging table
   • PS_CSU_PRB_PRM_EXC Delete: Prob-to-Perm exception tbl
   • PS_CSU_PRB_PRM_AUD Delete: Prob-to-Perm audit table
   • PS_CSU_L15_TRACK Update: Track file processing