Following is one example of a database that could not be used properly in PayEval:
Effective
Date |
Employee
ID |
Field
Name |
Field
Value |
7/22/2002 |
372 |
JOB TITLE |
Cheerleader |
7/22/2002 |
281 |
GENDER |
"F" |
7/22/2002 |
281 |
HIRE DATE |
7/22/2002 |
7/22/2002 |
281 |
RACE |
"H" |
12 Dec.04 |
296 |
PAY CHANGE |
502,988.79 |
This table is laid out in such a way that it would be unusable by PayEval. Some of the problems with this table are: there are multiple entries per employee, the characteristics for a single employee are spread across multiple entries at different effective dates, the header takes up two rows, the dates are given in different formats, and the "Field Value" column includes multiple data types (numbers, dates, and strings). Any one of these problems could make the data unusable by PayEval.
Go to PayEval contacts and send a question for assistance with data export and import issues.
|