GA CPI User Guide
Overview
Certified/Classified Personnel Info (CPI) Report
The Certified/Classified Personnel Info (CPI) report is submitted at three different times throughout the year. These reporting periods are referred to as Cycles, and the terms "reporting period" and "cycle" can be considered synonymous.
Reporting Cycles
Cycle 1 (Fall Submission): October
Cycle 2 (Spring Submission): March
Cycle 3 (Fiscal Year End Submission): July
Each cycle has specific date ranges associated with it, which are published annually by the Georgia Department of Education (GA DOE).
Record Types
The Georgia CPI report consists of four different record types, labeled A through D. These record types are submitted based on the cycles:
Cycles 1 & 2: These cycles are identical and are intended to report salary and wage data for the specified date ranges. They include only record types A, B, and C.
Cycle 3: This cycle is unique and focuses solely on Accumulated Leave data for the entire fiscal year. It includes record types A, B, C, and D.
Due to the fact that BusinessPLUS does not track the data that is required for the C Record there will be no default support for creating the intermediate data. The client will be responsible for populating the intermediate table and ensuring that the data is correct.
Selection Criteria
The Georgia CPI report includes data on the following types of employees only: Regular Certified (CE), Regular Classified (CL), Rehired Retirees, Long Term Subs, Terminated Employees, and Third Party Contractors. For reporting purposes the employees are categorized as Certified, Classified, Active, and Terminated. The record types are included for the various employee types as follows:
Regular (CE & CL) | Rehired | Long Term Sub | Terminated | |
---|---|---|---|---|
A Record | Yes | Yes | Yes | Yes |
B Record | Yes | Yes | No | Yes |
C Record | Yes | Yes | No | No |
D Record | Yes | Yes | No | Yes |
GA Employee Type Code | <blank> | B | L | <blank> |
BusinesPlus Setup
BusinessPlus Setup All wages and required classifications of employees must be entered and completed before processing the GACPI Report.
Setup
Before you can generate reports, you must access the reporting interface to set up the data required to create these reports. This configuration information is also used by the extract load & submission. The following options need to be configured under the ‘Setup’ menu:
Site Profile
Crosswalk
Code Value
Mapping
Additional Setup
Site Profile
Click Site Profile to define the entities and their details. This information is used by the Load and Submission options for the defined entities. To add details about a ‘Site’, enter data in the fields of this window as described below.
Field | Description |
---|---|
Entity* | ID of the entity/employer. The entity should be a valid entry as defined in BusinessPLUS. Once saved, the value cannot be changed. |
Employer Name* | Name of the employer for whom the entity is defined. |
Employer Address* | First line of the employer’s address. |
Employer Address(2) | Second line of the employer’s address. |
Employer City | City in which the employer is located |
Employer State | State in which the employer is located. Click the down arrow for the list of states. |
Employer Zip Code* | Numeric zip code of the employer’s location. This field accepts only five numeric characters and does not accept if all the five characters are zeroes. |
Employer Zip Code Extension | Numeric zip code extension of the employer’s location. This field accepts only numeric characters of 4 digits or less. |
School System Code | A number that identifies an active school system code. This field accepts only numeric characters. |
Columns marked with * are required fields in edit mode.
Crosswalk
The Crosswalk tab can be used to map the setup values. The predefined Code Items appear as a list when the ‘Crosswalk’ screen is loaded.
Code Value
Click Code Value to define valid codes.
Mapping
Map BusinessPlus to State codes for Pay Step Mapping and Racecode Mapping.
Additional Setup
Click Additional Setup to define the entity’s ‘Setup’ details. This information is used by the Load and Submission processes.
Instance
Click Instance to configure a ‘Report Instance’ for each report to be created. Report instances need to be configured for the extract process.
Field | Description |
---|---|
Name* | User defined name of the report instance |
Fiscal Year* | Reporting period current Fiscal Year |
Start Date* | Start Date from which submission will happen. Ex: 01/01/2017 Once the report instance is created, the ‘Start Date’ cannot be edited |
End Date* | End Date to which submission will happen. The End Date should be valid (it should be later than Start Date) Once the report instance is created, the ‘End Date’ cannot be edited |
Cycle* | Desired Cycle: 1 = Oct Cycle 2 = March Cycle 3 = July Cycle |
Status* | Indicates the status of the report instance. Valid choices are: Active, Locked, and Submitted. |
Date Submitted* | Date time stamp when changing to the ‘Submitted’ status. |
Update | Used to update the selected status. |
Load
Click the Load option to extract and load the new hire employee records into the maintenance table. See the ‘Submission File Layout’ section for the source of the reported data. Note that recently hired employees are selected for the report based on their hire date. When setting up report instances, you may find it necessary to overlap hire date ranges to ensure that all recently hired employees are reported. When loading an employee, the system will check all previous report instances with submission dates to avoid reporting the same employee, based on social security number and hire date, multiple times.
To load data for an instance of a report, enter data in the fields as described below.
Field | Description |
---|---|
Report Instance* | Click for the list of report instances. Select the desired report instance. |
Notes | Enter a note related to report instance or load that is to be performed. |
Entity ID | Click to select a specific entity for which the load will be performed. Select ‘ALL’ to extract records of all entities |
Employee ID’s | If specific IDs are to be refreshed or reported on, enter in this line, separated by commas. |
Purge Existing Data | If all the existing data for the selected ‘Report Instance’ in the maintenance table needs to be deleted, this checkbox should be checked. This action will also remove new (recent) maintenance records added previously using the maintenance screen for the ‘Report Instance’. |
Load | Click to load maintenance records into maintenance table. |
Columns marked with * are required fields to Load.
Maintenance
The Maintenance option is used to make necessary changes to the extracted employee data and to view the errors generated during the load or submission. The table below describes the fields in the Maintenance view when selecting report instances.
Field | Description |
---|---|
Report Instance | Click down to select a specific instance. |
Filter By Criteria | Filter the maintenance records based on Employee ID or Employee Last Name. Clear fields to view all the results. |
Employee ID | ID of the employee. |
Employee Last Name | Last name of the employee. |
Apply | Select the ‘Apply’ button to filter on values entered in either the Employee ID or Employee Last Name. |
Total Record Count | Indicates the total number of maintenance records in the grid. |
Insert
The button is used to add new employee records to the maintenance table. A new window is displayed for the user to add employee details. An example of the new employee screen is shown below.
Submission
After confirming the maintenance data, click on ‘Submission’ option to create the file to be submitted to the state. To create a report file for submission, data is entered in the fields as described below.
Field | Description |
---|---|
Click for the list of report instances. Choose the report instance which is to be submitted. | |
Any notes applicable to the submission job. | |
File name depending on state filename may require a specific layout, If file does not meet layout program will notify user of correct layout but allow user the freedom to name the file. | |
Click for the list of entities. If the maintenance records for all the entities are to be submitted, then ‘ALL’ should be selected. | |
Details for the selected ‘Report Instance’. | |
The date (Last Submission) and user (Created By) who performed the last submission and the note that was entered for submitting the selected ‘Report Instance’. | |
Create report file with data from maintenance table. | |
View the submission file report. |
Columns marked with * are required fields to ‘Generate Report’. If required fields are empty or have an invalid value, an error is logged which can be corrected from the ‘Maintenance’ screen.
Submission File Layout
The following tables show the field numbers, field names, and source within BusinessPLUS.
A – Record Format Cycles 1,2 and 3
Pos | Element | Len | Type | Source | Edits |
---|---|---|---|---|---|
1 | Fiscal Year | 4 | N | Regulatory.rr_run_def_mstr.fiscal_yr | E010 ‐ FISCAL YEAR must be all four digits of the current valid fiscal year |
5 | Report Period | 1 | A | Regulatoryreporting.rr_run_def_mstr.cycle | E020 ‐ REPORT PERIOD must be the current valid CPI period: "1" = October "2" = March "3" = July |
6 | System Code | 3 | A | Common Codes Category = “CPI”CD_Code = “SYSCODE” | E040 ‐ SYSTEM CODE must be an active system code |
9 | Employee Code | 9 | A | hr_empmstr.ssn | E064 – EMPLOYEE CODE must be employee's 9‐ digit Social Security Number, right justified with expressed leading zeros. |
18 | Record Type | 3 | A | Hard coded | E802 ‐ RECORD TYPE must = "A01". |
21 | Gender | 1 | A | hr_empmstr.gender | E200 ‐ GENDER must be one of the following valid values: "F" = Female "M" = Male |
22 | Filler | 31 | A | NA | No Edits |
53 | Birth Date | 8 | D | Hr_empmstr.bdt | E541 ‐ DATE OF BIRTH must be in format yyyymmdd; must not be blank. |
61 | Filler | 18 | A | NA | No Edits |
79 | Employee Type | 1 | A | Crosswalked from hr_empmstr.emp_type Setup/Additional Setup/Personnel Setup | E1013 ‐ EMPLOYEE TYPE must be one of the following valid values: |
80 | Ethnic Hispanic | 1 | A | Hr_empmstr.ethnic_cd Setup/Mapping/Race Code Mapping | E284 –ETHNIC HISPANIC must be ‘H’ or ‘N’. |
81 | Race Indian | 1 | A | Crosswalked from hr_emp_race.race_cd Setup/Mapping/Race Code Mapping | E285 – “I” or “N” |
82 | Race Asian | 1 | A | Crosswalked from hr_emp_race.race_cd Setup/Mapping/Race Code Mapping | E286 – “S” or “N” |
83 | Race Black | 1 | A | Crosswalked from hr_emp_race.race_cd Setup/Mapping/Race Code Mapping | E287 – “B” or “N” |
84 | Race Pacific | 1 | A | Crosswalked from hr_emp_race.race_cd Setup/Mapping/Race Code Mapping | E288 – “P” or “N” |
85 | Race White | 1 | A | Crosswalked from hr_emp_race.race_cd Setup/Mapping/Race Code Mapping | E289 – “W” or “N” |
86 | Last Name | 30 | A | hr_empmstr.lname | E3153 ‐ LAST NAME and/or FIRST NAME cannot be null. E3154 ‐ LAST NAME must be at least two characters |
116 | First Name | 30 | A | hr_empmstr.fname | E3153 ‐ LAST NAME and/or FIRST NAME cannot be null. W3107 ‐ FIRST NAME must be at least two characters |
146 | Mid Initial | 1 | A | Hr_empmstr.mname | E3102 ‐ MIDDLE INITIAL must be either alpha characters (A‐Z) or blank. |
147 | Filler | 4 | A | NA | No Edits |
B– Record Format Cycles 1 and 2 Only
Pos | Element | Len | Type | Source | Edits |
---|---|---|---|---|---|
1 | Fiscal Year | 4 | N | Regulatory.rr_run_def_mstr.fiscal_yr | See Fiscal Year A record |
5 | Report Period | 1 | A | Regulatory.rr_run_def_mstr.cycle | See Report Period code A record |
6 | System Code | 3 | A | Common Codes Category = “CPI” CD_Code = “SYSCODE” | See System Code code A record |
9 | Employee Code | 9 | A | hr_empmstr.ssn | See Employee code A record |
18 | Record Type | 3 | A | Hard Coded | EB02 – Record Type must = “B01” |
21 | Certified Employment Basis | 4 | N | Highest Basis for employee in hr_cntycred table | E622 – Indicates full time, part time, overtime status |
25 | Classified Employment Basis | 4 | N | Highest Basis for employee in hr_cntycred table | E626 – format as with implied decimal 1000 = 1.000, greater than zero and less than 2 |
29 | Payroll Years of Experience for Certified Employee | 2 | N | Calculated from highest step in hr_slrytble for each employee’s PM Assignment
| E630 – if Years > 0 C record is required. If AssignType = “N” then years exp = 0 pad with leading zeros |
31 | Certificate Level | 1 | A | Highest hr_cntycred_agency_res with highest hr_cntycred.cred_end | W630 - required if C record exists Valid values = |
32 | State Pay Step | 2 | A | hr_slrytble.state_step | E643 – If C Record valid value = “E” “1” “2” “3” “4” “5” “6” “7” “L1” “L2” “L3” “L4” “L5” “L6” pay step level must correspond to GDOE Annual Salary Schedule |
34 | Filler | 1 | A | NA | No Edits |
35 | Annual Contract Salary For Certified Employee | 9 | N | hr_emppay.actl_ann | W403 ‐ ANNUAL CONTRACT SALARY FOR CERTIFIED EMPLOYEE divided by EMPLOYMENT BASIS must be equal to or greater than State Minimum Salary for the employee's CERTIFICATE LEVEL and STATE PAY STEP, except where ASSIGNMENT JOB CODE = 80, 115, 155, 157, 403, 413, 415, 417‐419, 421‐424, 426, 427, 434‐437, 439, 442, 445, 447, 455, 460, 465, 466, 470, 471, 473, 480, 482‐485, or 495 or where CERTIFICATE LEVEL = '2' and ASSIGNMENT CERTIFICATE TYPE = 'BT'. |
44 | Total Annual Salary for Classified Employee | 9 | N | hr_emppay.actl_ann | E1004 ‐ TOTAL ANNUAL SALARY FOR CLASSIFIED EMPLOYEE must be greater than zero if CLASSIFIED EMPLOYMENT BASIS is greater than zero. |
53 | Contract Days for Certified Emloyee | 3 | N | hr_emppay.actl_days | E660 ‐ CONTRACT DAYS FOR CERTIFIED EMPLOYEES must be greater than zero and less than or equal to 260. |
56 | Annual Work Days For Classified Employee | 3 | N | hr_emppay.actl_days | E663 ‐ If ANNUAL WORK DAYS FOR CLASSIFIED PERSONNEL exists, there must be at least one ASSIGNMENT TYPE = "N". |
59 | Temination Code | 1 | A | Hr_empmstr.enddt | E670 ‐ TERMINATION CODE must be one of the following valid values: "1" = Retirement "2" = Death "3" = Family "4" = Advanced Study "5" = Nonrenewal of Contract "6" = Acceptance of Position in other Georgia School System "7" = Reduction in Force "8" = Failure to Meet Certification Requirements "9" = Resignation "0" = Active employees only. E629 ‐ If TERMINATION CODE is valid for termination, and a TERMINATION DATE exists, all other non‐key data elements should be blank/null. ASSIGNMENTS; if active, remove TERMINATION CODE. |
68 | Filler | 2 | A | NA | No Edits |
70 | State Health Plan | 1 | A | If employee has a cdh that has col py_cdh_misc_cd04 = “HLTH” then we mark record “Y” | E634 ‐ Must be one of the following: Y = Employee is participating in the State Health Plan N = Employee is NOT participating in the STATE HEALTH PLAN O=Other plan provided by the district ‘O’ pertains to ANY health insurance “provided by the district” that is taken by the employee and is not State Health (See Data Elements for more details). |
C– Record Format Cycles 1 and 2 only
Pos | Element | Len | Type | Source | Edits |
---|---|---|---|---|---|
1 | Fiscal Year | 4 | N | Regulatory | See Fiscal Year A record |
5 | Report Period | 1 | A | Regulatory run_def_mstr | See Report Period code A record |
6 | System Code | 3 | A | Common Codes | See System Code code A record |
9 | Employee Code | 9 | A | hr_empmstr.ssn | See Employee code A record |
18 | Record Type | 3 | A | Hard Coded | EB02 – Record Type must = “C01” |
21 | Assignment School Code | 4 | A | hr_mstrschd.sitecd | E680 ‐ ASSIGNMENT SCHOOL CODE must be a valid CPI school/location code in the Facilities Database. W691 ‐ If ASSIGNMENT SCHOOL CODE is less than 6000 and LIFE STAGE = '4' or '7' in the Facilities Database, then ASSIGNMENT JOB CODE = "610" must exist at ASSIGNMENT SCHOOL CODE. |
25 | Assignment Percentage of Time | 4 | N | Ratio calc based on hr_crsetble.core_area And hr_mstrschd.class_prd | E681 ‐ ASSIGNMENT PERCENTAGE OF TIME must be equal to or less than 100.0. |
29 | Assignment Type Code | 1 | A | Setup/ | E683 ‐ ASSIGNMENT TYPE CODE must be one of the following valid values: "C" = Certified or "N" = Classified |
30 | Assignment Field Status | 1 | A | If employee certified then value = “I” otherwise Highest hr_cntycred.county_res with highest cred_end | E688 ‐ ASSIGNMENT FIELD STATUS must be one of the following valid values: "I” = In‐Field "O" = Out‐of‐Field E679 ‐ If ASSIGNMENT FIELD STATUS = "O", ASSIGNMENT JOB CODE must = 085‐ 199, 400‐499, 600, 610, 615, 621, or 641 |
31 | Assignment Certificate Type | 3 | A | hr_cntycred.cred_type | E690 ‐ ASSIGNMENT CERTIFICATE TYPE must have "Currently Issued" = "Y" in the Certificate Type Table. |
34 | Assignment Job Code | 3 | A | hr_pcntble.asmt_job_code | E692 ‐ ASSIGNMENT JOB CODE missing or not valid: · ASSIGNMENT JOB CODE must exist in every RECORD TYPE = "C0N". · and ASSIGNMENT JOB CODE must exist in the Job Code Table. E696 ‐ If ASSIGNMENT JOB CODE = 141, 142, 149, 153, or 158‐171, then third character of ASSIGNMENT SUBJECT MATTER CODE must = "8" or ‘1’. (Special Ed. teachers with special education or remedial subjects) |
37 | Assignment Subject Matter Code | 3 | A |
| E694 ‐ ASSIGNMENT SUBJECT MATTER CODE must be in Subject Matter Code Table. E1009 ‐ When ASSIGNMENT JOB CODE = ‘445’, Technology Specialist, the SUBJECT MATTER CODE must = blank/null or ‘999’. |
40 | Assignment Field Code | 3 | A | cred_ma_mi_code | E697 ‐ ASSIGNMENT FIELD CODE must be in Certificate Field Code Table. |
43 | Assignment Fund Code | 2 | A | glk_key_mstr.glk_sec_part07 | E699 ‐ ASSIGNMENT FUND CODE must be in Secondary Fund Code Table. E1115 ‐ ASSIGNMENT FUND CODE 56 (IDEA – GNETS Federal Grant) is not valid for teacher Job Codes (Job Codes less than 200). FY2018: New Codes added for Consolidated Funding: 01‐For APPROVED CONSOLIDATED FUNDING SITES ONLY: Use this ASSIGNMENT FUND CODE for all certified and classified staff accounted for within the Resource Allocation Plan. Certified staff with this fund WILL earn T&E 02‐ For APPROVED CONSOLIDATED FUNDING SITES ONLY: Use this ASSIGNMENT FUND CODE for all certified and classified staff NOT accounted for within the Resource Allocation Plan. Certified staff with this fund WILL NOT earn T&E |
45 | Assignment Consolidated Fund Flag | 1 | A | No Consolidated Funding so always “N” | E1022‐ ASSIGNMENT JOB CODE not valid for Consolidated Funding. E1023‐ ASSIGNMENT SCHOOL CODE not listed on approved Consolidated Funding List. E1024 – District total for Consolidated Funding is greater than the Resource Allocation. See report CP050 for more information. E1025‐ IF ASSIGNMENT CONSOLIDATED FUND FLAG = “Y” ASSIGNMENT FUND CODE must = 01 or 02. Indicates if employee should be counted in the Consolidated Funding. Valid Values: “Y” = Yes “N” = No |
46 | Filler | 40 | A |
| No Edits |
D– Record Format Leave Information Cycles 3 only
Pos | Element | Len | Type | Source | Edits |
---|---|---|---|---|---|
1 | Fiscal Year | 4 | N |
| See Fiscal Year A record |
5 | Report Period | 1 | A |
| See Report Period code A record |
6 | System Code | 3 | A |
| See System Code code A record |
9 | Employee Code | 9 | A |
| See Employee code A record |
18 | Record Type | 3 | A | Hard Coded | EB02 – Record Type must = “D01” |
21 | Filler | 9 | A |
| No Edits |
30 | Primary Assignment Job Code | 3 | A | hr_pcntble.asmt_job_code | E692 ‐ PRIMARY ASSIGNMENT JOB CODE must exist in the Job Code Table. |
33 | Sick Leave | 3 | N | Accumulators in pyx_xtd_dtl based on CDH for sick leave. CDH’s are identified thru crosswalk. | E602 ‐ SICK LEAVE must be less than "240". Note: SICK LEAVE will be reported in whole numbers. If it is accumulated in fractions of days at the local district, the local district will round it to the nearest whole number |
36 | Staff Development | 3 | N | Accumulators in pyx_xtd_dtl based on CDH for dev leave. CDH’s are identified thru crosswalk. | E603 ‐ STAFF DEVELOPMENT LEAVE must be less than "120". Note: STAFF DEVELOPMENT LEAVE will be reported in whole numbers. If it is accumulated in fractions of days at the local district, the local district will round it to the nearest whole number. |
39 | Vacation | 3 | N | Accumulators in pyx_xtd_dtl based on CDH for vacation eave. CDH’s are identified thru crosswalk. | E604 ‐ VACATION LEAVE must be less than "120". Note: VACATION LEAVE will be reported in whole numbers. If it is accumulated in fractions of days at the local district, the local district will round it to the nearest whole number |
42 | Other Leave | 3 | N | Accumulators in pyx_xtd_dtl based on CDH for Other leave. CDH’s are identified thru crosswalk. | E605 ‐ OTHER LEAVE must be less than or equal to "240". Note: OTHER LEAVE will be reported in whole numbers. If it is accumulated in fractions of days at the local district, the local district will round it to the nearest whole number. |
About
The About screen displays system level information about the report such as the version, report name and database details.
Appendix A: BusinessPLUS Configuration
CPI Data Element | Record Type | Required Business PLUS Configuration |
---|---|---|
EMPLOYEE TYPE | A Record | CPI Report requires employee grouped into 3 categories (Powerschool is not processing 3rd party contractors). In order to accomplish this, we require the sites in GA to use Bargaining Type and/or Employee Type to specify the following CPI employee types: |
CERITIFIED/CLASSIFIED EMPLOYEE BASIS | B Record | Employee basis as defined by the GA DOE is calculated based on Pay Assignment type. Full Time hours are defined as being the sum of the default hours for all non-supplemental pay assignments. The Additional hours are defined as being the sum of all default hours for all supplemental pay assignments. See the RR Profile tab for details about specifying supplemental record types. |
PAYROLL YEARS OF EXPERIENCE FOR CERTIFIED EMPLOYEE | B Record | Payroll Years of Experience is calculated using a sum of the hr_exprinfo.PREEMP_YRS info for the given employee. |
CERTIFICATE LEVEL: | B Record | Certificate Level is taken from the hr_cntycred_mstr.spec_grade field for the given employee. |
NATIONAL TEACHER CERTIFICATION (NBPTS) | B Record | NBPTS is taken from the hr_cntycred.cred_type. Credential Types are set up in HR and the value for cred_type must be NBCT. |
ANNUAL CONTRACT SALARY FOR CERTIFIED EMPLOYEE | B Record | Annualized salary information for a given pay assignment as required by the state of Georgia is stored in the Misc tab, Num Code 2 (hr_emppay.num_02) field on the HRPYPA screen. |
TOTAL ANNUAL SALARY FOR CLASSIFIED EMPLOYEE | B Record | Same as ANNUAL CONTRACT SALARY FOR CERTIFIED EMPLOYEE. |
CONTRACT DAYS FOR CERTIFIED EMPLOYEE | B Record | Contract Days is read directly from the Pay Assignment default days field. |
ANNUAL WORK DAYS FOR CLASSIFIED EMPLOYEE | B Record | Same as CONTRACT DAYS FOR CERTIFIED EMPLOYEE. |
TERMINATION CODE | B Record | Georgia state term codes are defined as being 1 thru 9 inclusive. The BusinessPLUS setup requires that this value be padded with a '0' (zero). Thus, Business PLUS, a term code of '01' must be defined as being the equivalent of the Georgia State Code of '1'. etc. |
LOCAL YEARS OF SERVICE | B Record | Local years of service is calculated as a sum of the hr_exprinfo.INHOUSE_YR info for the given employee. |
PRIMARY ASSIGNMENT JOB CODE | D record | Primary job assignment code is stored in the PCN table data in hr_pcntble.cbeds. Only the first three characters of this field are used. |
Additional Setup | ||
Pay Assignments | Pay Assignments are designated are broken in to two categories:
For group #1 above we use Pay Assignment Record Types PM - Z0 job code-1 PM rec (c rec) other fields- all rec |