| Panel | |
|---|---|
|
...
Building Code contains the building codes the position is worked in. Building Codes can be added under SYSTEM/CUSTOM FIELD DEFINITIONS. Search for Building Code in Display Names, select edit. From here you can add or delete building codes. **Note** If editing/updating a current Building Code in Custom Field Definitions, a Mass Change procedure will need to be done in Position to update the employee's with the old codes to the new codes.
Department Code contains the department codes the position is worked in. Department Codes can be added under SYSTEM/CUSTOM FIELD DEFINITIONS. Search for Department Code in Display Names, select edit. From here you can add or delete building codes. **Note** If editing/updating a current Department Code in Custom Field Definitions, a Mass Change procedure will need to be done in Position to update the employee's with the old codes to the new codes.
...
For more detail information on the Mass Change option, please click on the Mass Change documentation link to find the How to Steps: Mass Change
Delete Option
This option deletes the new contract information from the New Contract maintenance file. If no specific selection options are entered, all new contracts will be deleted. A count of the number of contracts deleted will appear on the screen after the program runs to completion:
...
Enter a date to only Include Active Compensations 
in the Selected Compensation grid. This will eliminate of including both old and new compensations for an employee. The included compensations, active as of date, looks for compensations with a start date that is either empty, or before or equal the date entered AND a stop date that is either empty, or after or equal the date entered. If the compensation meets these criteria, then it is displayed in the grid. The grid updates when the date is changed.
Select Pay Groups options using the 
to select Available Pay Groups to Selected Pay Groups.
...
Click on 
to activate all contract information into the Compensation records, then deletes it from New Contract maintenance file.
Import New Contracts
| Note |
|---|
**Please be aware the header columns listed below are case sensitive** |
...
There are four required fields: employeeId, jobNo, contractType and newCompensation.labelompensationLabel- is only required if the employee has more then one Compensation for a Position. The remainder of the data is optional and will be dependent upon the contract type being imported. For example, if importing a mid-year contract change with retro-spread, the days since raise should also be included in the import file. Information not specified in the fields for the spreadsheet will be pulled in from the existing Compensation.
...
To create a template spreadsheet using the Compensations fields, which can assist in creating new contracts, you can import this json file into Reports - New Contract Compensation Worksheet.rpd-json (can specify start date specific pay groups)With some manipulation to the spreadsheet this will then allow you to create new contracts using the Import option in Processing/ New Contracts.
...
| Redesign Import File Column Heading Name | Redesign Field Location | New Contract Description and Values | Classic Field Name | Classic Field Location | Classic New Contract Description |
|---|---|---|---|---|---|
| employeeId | Compensation | Employee Number
| EMPLOYEE_ID | ||
| jobNo | Compensation | Position Number | JOB_NO | JOBSCN | Job# |
| contractType | N/A | Type 1 - Mid-year change with no Retro 2 - Mid-year change with Retro spread over pays 3 - Mid-year change with lump sum retro 4 - New Contract from existing Compensation | CONTRACT_TYPE | ||
newCompensationLabel Label is only required if the employee has more then one Compensation for a Position. | Compensation | New Label
| JOBSCN | Check stub desc | |
| calendarType | Compensation | Job Calendar | CALENDAR_TYPE | JOBSCN | Calendar type |
| firstName | Employee | First Name | |||
| lastName | Employee | Last Name | |||
| raiseDate | N/A | Raise Date
| DAYS_SINCE_RAISE | Days since raise | |
| compensationDescription | Compensation | New Description | Title | ||
| contractStartDate | Compensation | New Compensation Start Date
| CONTRACT_START_DATE | JOBSCN | Cont start |
| contractStopDate | Compensation | New Compensation Stop Date
| CONTRACT_STOP_DATE | JOBSCN | Cont stop |
contractWorkDays | Compensation | New Contract Work Days
This value currently can only be loaded for new contracts. | WORK_DAYS_IN_CONTRACT | JOBSCN | Work Days |
payPlan Not an option at this time. Use Mass Change in New Contract to update Pay Plan.
| Compensation | New Pay Plan
| PAY_PLAN | JOBSCN | Pay Plan |
| payUnit | Compensation | New Pay Unit
| PAY_UNIT | JOBSCN | Pay unit |
unitAmount | Compensation | New Unit Amount
| JOBSCN | Daily rate | |
| retireHours | Compensation | New Retirement Hours | RETIRE_HOURS | JOBSCN | Retire hours |
Accrued Wages Not Loaded | Compensation | New Accrued Wages
| |||
Amount Earned Not Loaded | Compensation | New Amount Earned
| |||
Amount Paid Not Loaded | Compensation | New Amount Paid
| |||
Amount Docked Not Loaded | Compensation | New Amount Docked
| |||
payPerPeriod | Compensation | New Pay Per Period
| |||
contractAmount Required for Stretch Paid Compensations | Compensation | New Contract Amount
| CONTRACT_AMOUNT | JOBSCN | New contract |
contractualObligation | Compensation | New Contract Obligation
| CONTRACTUAL_OBLIGATION | JOBSCN | Obligation |
| userContractType | Compensation | New Contract Type | USER_CONTRACT_TYPE | JOBSCN | Contract type |
| paysInContract | Compensation | New Pays In Contract | PAYS_IN_CONTRACT | JOBSCN | '# pays |
Pays Paid Not Loaded | Compensation | New Pays Paid
| |||
| equalPays | Compensation | New Stretch Pay
| EQUAL_PAYS | JOBSCN | Equal pays |
retroNextPay Not Loaded | New Retro Next Pay
| ||||
| salaryScheduleColumn | Compensation | New Salary Schedule Column
| SALARY_SCHEDULE_COLUMN | ||
| salaryScheduleId | Compensation | New Salary Schedule Id
| SALARY_SCHEDULE_ID | ||
| salaryScheduleStep | Compensation | New Salary Schedule Step
| SALARY_SCHEDULE_STEP | ||
Local Contract Code Not Loaded | Compensation | Local Contract Code
| |||
| calendarStartDate | Compensation | New Calendar Start Date
| CALENDAR_START_DATE | JOBSCN | Calendar start |
| calendarStopDate | Compensation | New Calendar Stop Date
| CALENDAR_STOP_DATE | JOBSCN | Calendar stop |
| hoursInDay | Compensation | New Hours in Day
| HOURS_IN_DAY | JOBSCN | Hours per day |
| retirementCode | Position | Retirement System | RETIREMENT_CODE | ||
jobTitle | Position | Position Description | |||
| jobStatus | Position | Job Status
| JOB_STATUS | ||
| payGroup | Position | Pay Group | PAY_GROUP | ||
| building | Position | Building Code
| BUILDING | ||
| department | Position | Department Code
| DEPARTMENT | ||
| extendedService | Position | Extendend Service | EXTENDED_SERVICE | ||
| fte (must be all lower case) | Position | FTE
| FTE | ||
| positionCode | Position | Position Code | POSITION_CODE | ||
| buildingIrn | Position | Building IRN | BUILDING_IRN | ||
| assignmentArea | Position | Assignment Area | ASSIGNMENT_AREA | ||
| positionStartDate | Position | Position Start Date | POSITION_START_DATE | ||
| positionStopDate | Position | Position Stop Date | POSITION_STOP_DATE | ||
| paraprof (must be all lower case) | Position | Paraprofessional
| PARAPROF | ||
| emisHoursInDay | Position | EMIS Hours In The Day
| EMIS_HOURS_IN_DAY | ||
| emisWorkDaysInContract | Position | EMIS Work Days | EMIS_WORK_DAYS_IN_CONTRACT | ||
| emisFteUnit | Position | EMIS FTE
| EMIS_FTE_UNIT | ||
| checkDistribution | Employee | Employee Check Distribution | CHECK_DISTRIBUTION |
...
| Info | ||||
|---|---|---|---|---|
The New Reportable to EMIS checkbox can only be mass updated using Mass Change in New Contract. The Mass Change definitions below can be used to mass uncheck or check the New Reportable to EMIS checkboxs.
|
Example of an Import.csv:
Creating New Non Contract Compensations
To create new non contract compensation record the Reports/Report Manager/SSDT Non Contract Compensation Mass Load Extract can be processed to create an excel file with the appropriate headers. The file then can then be updated-removing unwanted records, updating unit amount, start/stop date, etc. Once the file has been updated it will need to be saved in csv format. This will then allow the file to be loaded directly to Compensation. using Utilities/Mass Load/Compensation.
There is an available Non Contract Compensation Mass Load Worksheet available that contains the Pay Group and excludes archived employees.
...
Example of New Contract under New Contract Maintenance option:
Salary Notices
This program produces salary notices that can be distributed to employees with New Contract information.
Creating Salary Notices
The Salary Notices are created using the New Contracts that are listed under New Contract Maintenance.
...
Districts have the option to create a custom salary notice. To create a custom form, you can begin with the default form and then customize it. To download the default salary notice, click here. This follows the same rules as creating a customizing a direct deposit form. Several template forms can be found in the Public Shared Reports Library>Custom Form Templates section. Click here for a list of available downloadable forms. For further instructions in customizing forms, click here.
...
| Info | ||
|---|---|---|
| ||
By default, the Default form will be used. However, a custom default salary notice form can be set. Go to System>Configuration>Salary Notice Configuration and in the Default Salary Notice Form, select the custom form from the drop down.
Click Save. When in Compensation>Salary Notice or New Contracts>Salary Notices, the salary notice selected as the default salary notice form will be the form that you see. Use the drop down to change the form, if desired. Please click here for more information on setting a Custom Salary Notice as default under Configuration/Salary Notice Configuration. |
...
Setup to Send Salary Notices
First, theEmail Notifications module must be installed. To install the module, go to System>Modules and click the + sign next to the Email Notification Services. Click the 
option to refresh the page. Once the module is installed, the Email Salary Notices button will be enabled in New Contract>Salary Notices. Also, go to System>Configuration>Email Configuration and add or verify there is a value in the 'Smtp Host.'
The next step is setting up the System>Configuration>Salary Notice Configuration.
The From Email will be the email address of the person sending the notifications. This should be an valid email that your Stmp email server will recognize.
...
This report list the data from New Contract maintenance
Mid Year Contract Change
See Checklist USPS-R Mid Year Contract Change Checklist#RMidYearContractChangeChecklist
...
Mid-Contract With No Retro
Click here to see Mid Year Contract with No Retro calculations
...
| Note |
|---|
New Contract will NOT adjust the dock for the new rate. This will have to be done manually using Compensation Adjustment>Amount Dock or a Future Pay entry. |
Click here to see Mid Year Retro Spread calculations
...
| Note |
|---|
New Contract will NOT adjust the dock for the new rate. This will have to be done manually using Compensation Adjustment>Amount Dock or a Future Pay entry. |
Click here to see Lump Sum Retro calculations
...
| Note |
|---|
The contract obligation field will reflect the amount to be earned on the new contract plus the amount already earned on the old contract plus the lump sum retro amount. The Days Since Raise field will be automatically populated, utilizing the raise date, when the Calculate button is clicked. |
...
To create a report from the Grid, please click on the Report documentation link to find the How to Steps: Report
Field name for compensation fields are now labeled with "Old" and "New" before the heading. This appears for New Contracts and Mid-Year Contracts.
...