Report Parameters | |
---|---|
Report Type | Mandatory, LOV available Annual or EE Transaction Report |
Report Date | Mandatory, Date, and LOV available The ‘Report Date' is the date printed in the file. |
Action Begin Date | Mandatory, Date, LOV available The ‘Action' date range will be used to determine which pay components within the element to report on. |
Action End Date | Mandatory, Date, LOV available The ‘Action' date range will be used to determine which pay components within the element to report on. |
Directory Name | Mandatory, text Must be a directory on the server for which the current user (as signed onto the client’s network) has write capability. For example the entry ‘C:\TEMP’ accesses the ‘TEMP’ directory on the server, not the local directory for the computer terminal being used. |
Media File Name | Optional, Text |
Write or Append | Mandatory, LOV available If the file already exists should the current information overwrite it or append to it? |
Entity | Mandatory, LOV available Limits the process to the entity specified. |
Fiscal Hours Element | Mandatory, LOV available |
Fiscal Earn Element | Mandatory, LOV available |
Calendar Hours Element | Mandatory, LOV available |
Calendar Earn Element | Mandatory, LOV available |
EERC Element | Mandatory, LOV available |
BAC Element | Mandatory, LOV available |
Add'l Contrib Fix Elem | Optional, LOV available |
Add'l Contrib Var Elem | Optional, LOV available |
Tax Def Add'l Fix Elem | Optional, LOV available |
Tax Def Add'l Var Elem | Optional, LOV available |
ER Add'l Fix Elem | Optional, LOV available |
ER Add'l Var Elem | Optional, LOV available |
Exception Level | Optional, LOV available A ‘trace’ report of exception messages may be produced to assist in the testing phase. If necessary, choose from 0 – 9 (highest) level of trace. Please note that this is a voluminous report and will cause very slow performance. |
Report Filters | |
---|---|
People List Code | |
Person | |
Department | |
Org Level Type | |
Org Level | |
Authorization Area | |
Unit | |
Group | |
Payroll | |
Status |
People List Code Mandatory, Multiple selection, LOV available, <ALL>
A people list may be used to indicate specific employee transaction to be processed.
Person Code Mandatory, Multiple selection, LOV available, <ALL>
The person code(s) of specific employee(s) to be processed.
Department Mandatory, Multiple selection and LOV available
Org Level Type Mandatory, LOV available
Org Level Mandatory, Multiple selection and LOV available
Authorization Mandatory, Multiple selection and LOV available
Unit Mandatory, Multiple selection and LOV available
Group Mandatory, Multiple selection and LOV available
Payroll Mandatory, Multiple selection and LOV available
Status Mandatory, Multiple selection and LOV available
Mandatory means that the field must have something in it. <ALL> is fine.
Calendar Earn Elem Mandatory, LOV available
EE Add Amt Fix Elem Mandatory, LOV available
EE Add Amt Vary Elem Mandatory, LOV available
See WRS Set up - Pay Elements
Interface Code Mandatory, LOV available
Only those reports of the format “Wisconsin Retirement” will display. Choose from the report formats created. The format “HL$WRS” has been provided as a sample, but should be copied, and the copy edited, by the client before running this report. The report definition selected will determine the format of the output file (if any), as well as the columnar content of the report.
File Name Mandatory, text Enter the name of the file that will be created in the interface directory specified.
Output Header/Trailer Mandatory, LOV available If the file is to contain a header and trailer record then indicate <Yes>.
Trial Mandatory, LOV available The report may be run in trial mode (Yes) or update mode (No)
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation