Suomi
Platform status: -
  1. Nepton Support
  2. Support
  3. Integration
  4. Events

Mepco scheduled event import

  • Updated
 

Following events can be imported to Nepton: Training, Temporary lay-off, Annual leave, Worktime shortening leave, Balance leave, Bank leave, Sick leave and Absence. Mepco event import settings are configured in: Worktime -> Administration -> Working community settings / Setting groups -> Integrations -> Accountor Mepco HRM absence import

A file in csv-format must be generated for the SFTP server for the given data. The dataset to import must include all valid events for the transfer period. The filename of the dataset must contain a timestamp indicating the creation time of the file.

Import can be scheduled to occur automatically. Scheduling settings can be found in Work time -> Administration -> Working community settings -> Integrations -> Integration scheduling. Read more about scheduling here

File should be saved with ISO-8859-1 encoding. Records are separated with a semicolon (;). Line break is marked with a line feed (LF). This type of line break is generated by default by almost all information systems.

File does not contain a header row. One event and its period are presented on a single row.

The import of events is performed by the user defined in the settings as Person used to create event, and changes will appear in the service as made by that user. Integration performs the deletion, updating and inserting of events in the order below.

  1. Events missing from the dataset will be removed from the person’s calendar if the calendar event was created by the same user performing the import. The service sets a number of days for which the imported data is considered for historical interpretation. This number of days is compared to the event's end date. Events will be deleted for the period during which they are valid in the person’s calendar for the updated time frame, and if they are not present in the dataset to import. This means the event must be present in the transfer file for its entire duration, extended by the number of days set for past updates. If no time limit is set, a value of 0 days is used.

  2. New events are added to the person’s calendar if they are not already there. Events in the dataset that start after the specified time limit and up to 10 years into the future from the current date will be established in the transfer.

    For example, if the run is performed on January 20 and the time limit is set to 20 days, events valid in the previous year will not be transferred to the service. If an event partially occurs in January, it will be added to the calendar. In this example, events will be deleted starting from January 1 if they are not included in the transfer dataset.

  3. Events present in both the calendar and the import file for the updated period will remain in the service.

Interpretation of event times

Basic fields for absences only include start and end dates. The start and end times for an event added via basic fields are set as follows:

  1. If the day has a planned shift or expected working times, times of the absence are set based on its start and end. Note: for night shifts the setting 'Event rendering' (Worktime > Administration > Work hours > Rendering options) defines which day the shift is associated with.
  2. The start time is set to 00:00 and end time to 24:00

Optional fields can be used to specify start and end times and/or duration. If the duration is provided via alternative additional fields but no start time is specified, the event is scheduled for the user’s workday as follows:

  1. If there are no events on that day, use 8:00 as the start time.
  2. If there is an open or all-day event, use 8:00 as the start time.
  3. If the first event of the day starts at 12:00 or later and the event to be imported is less than 5 hours long, place the event at the beginning of the day.
  4. If placing the imported event at the end of the day would exceed 18:00 but it fits between 8:00 and the day’s first event, place it there.
  5. If none of the above apply, start the imported event after the last event of the day.

Integration file fields

Below is a list of the fields in the integration file and their details

Column Field Description
A Last name Person's last name. Not used by Nepton in import.
B First name Person's first name. Not used by Nepton in import.
C Person number The Mepco ID/person number of the person
D Absence start date Start date of the event, format YYYY-MM-DD or DD.MM.YYYY
E Absence end date End date of the event, format YYYY-MM-DD or DD.MM.YYYY
F Absence code Event code. A list of supported codes is below. If a code is not listed or is one that isn’t processed, the event is imported as an absence by default.
G Absence type Possible values:
  • L – leave
  • P – absence.
Not used by Nepton in import.
H Paid until date The date until which the event is paid. If the event ends later than its paid period, Nepton extends it as unpaid. This field is blank for completely unpaid events. Format YYYY-MM-DD or DD.MM.YYYY

Optional fields

Optional fields in the list below are not available in Mepco. They are intended to add flexibility for using Mepco-format data with other systems.

Sarake Kenttä Kuvaus
I Absence start time The time the event starts, format HH:MM
J Absence end time The time the event starts, format HH:MM
K Paid until time The time until which the event is paid. If the event ends later than its paid period, Nepton extends it as unpaid. This field is blank for unpaid events. Format HH:MM
L Absence duration Duration of the event in hours and minutes. If provided, it overrides the information in columns J and K. Format HH:MM.

Supported codes

Absence code Description

4
4.1
4.2
4.3
4.4
04
04.1
04.2
04.3
04.4

 Training

5.0
05.0

 Temporary lay-off
6.1
6.1.1
6.3
6.7
6.8
6.9
06.1
06.1.1
06.3
06.7
06.8
06.9		 Annual leave
6.2
06.2		 Worktime shortening leave
6.5
06.5		 Balance leave
6.6
06.6		 Bank leave

6.10

06.10

11.0

11.3

11.5

 Absence, other reason
8.0
8.1
8.2
8.3
8.4
8.4.1
8.5
8.6
08.0
08.1
08.2
08.3
08.4
08.4.1
08.5
08.6		 Sick leave

9.0
9.1
09.0
09.1

 Sick leave, accident at work

10.2
10.10
10.11
010.2
010.10
010.11

 Absence, parental leave

10.3
010.3

 Absence, nursing leave
10.5
010.5		 Sick leave, child sick
10.55
010.55		 Absence, family care leave
11.2
011.2		 Absence, study leave
11.3.1
011.3.1		 Absence, absence due to compulsory family reason
11.4
011.4		 Absence, job alternation leave
11.8
011.8		 Absence, military or civil service time
11.9
011.9		 Absence, military refresher course
Unknown Code (not listed here or in codes not to process) Absence

Absence codes not processed

Events with following absence codes are not imported to Nepton.

  • 8.7
  • 10.4
  • 10.8
  • 13.1
  • 13.2
  • 08.7
  • 010.4
  • 010.8
  • 013.1
  • 013.2

Example files

Example without optional columns:

Esimerkki;Erika;1109;24.01.2014;24.01.2014;06.1;L;
Hollola;Heidi;2404;01.10.2014;03.10.2014;08.0;P;
Hollola;Heidi;2404;22.09.2014;26.09.2014;08.0;P;
Hollola;Heidi;2404;22.10.2014;26.10.2014;010.3;P;
Hollola;Heidi;2404;03.11.2014;05.11.2014;04.3;P;
Hollola;Heidi;2404;06.11.2014;06.11.2014;06.6;P;06.11.2014

Example with optional columns:

Esimerkki;Erika;1109;24.01.2014;25.01.2014;06.1;L;;;;;
Hollola;Heidi;2404;01.10.2014;01.10.2014;08.0;P;01.10.2014;08:00;10:00;10:00;
Hollola;Heidi;2404;22.09.2014;26.09.2014;08.0;P;;06:00;;;04:00