This import mapping is specifically designed for the Mepco source system. It extends the general import rules with special business logic and data identifiers.
This mapping is primarily intended for CSV file format without a header row. However, all other file formats are supported, and a header row can be included if desired.
Fields
Below is a list of the special identifiers and behaviours of fields related to this import mapping. Additional person information fields can be imported using the general import documentation.
| Identifier | Import Column Index | Mapped to Nepton Field | Description |
|---|---|---|---|
| Username | 1 | Username | |
| Firstname | 2 | Firstname | |
| Lastname | 3 | Lastname(s) | |
| Employee Number | 4 | Employee Number | |
| 5 | |||
| Cost Center | 6 | Person group | |
| ContractStart | 7 | Contract Start Date | |
| ContractEnd | 8 | Contract End Date | |
| Worktime calculation group | 9 | WT User Setting Group | |
| Primary supervisor | 10 | Primary supervisor | |
| Valid from | 11 | Valid from | This field includes the work contract start date in Mepco. Changes during the work contract needs to be updated to Nepton |
Business logic
- If using supervisor - import field instead of 'primary supervisor'
If a primary supervisor is set, it will replace existing primary supervisor assignments. Empty supervisors will not be imported.- The only way to empty a persons' primary supervisor assignment is using the RESET keyword
- Extend working contract length
- If a person has an existing working contract start date, imported start date can zero out the existing start date value, but start date value can't be changed to another value
- If a person has an existing working contract end date, imported end date can zero out the the existing end date value, or change the end date value to later date, but end date value can't be changed to earlier date
- These limitations ensure persons who have multiple contract dates can be viewed and managed properly in the service