eADM

Visma HR+8 - Mappings

This document provides detailed field mappings for integrating the Visma HR+8 system with Identum's eADM . The mappings specify how data from the source JSON files (grp_ImportHierarchy.json and emp_ImportHR.json) is processed and mapped to the corresponding fields in eADM.

The guide is divided into two main sections:

  • Department Mappings: Defines the correlation between Visma HR+8 department data and eADM unit fields.

  • User Mappings: Defines the mapping between Visma HR+8 employee data and eADM account fields.



Department Mappings

Department data is imported from the grp_ImportHierarchy.json file.

eADM

Visma HR+8 Source Field

Notes

Cost Center

GroupGenerationItemDepartmentDescription

Example: "37109 VC Gothenburg 9"

Department

GroupItemDescription

Example: "37,109 Employees"

Department Number

GroupItemId

Example: 1535

Manager

GroupGenerationItemGroupManagerUserId

Note: This field requires a derived value. The User ID (e.g., 96336) must be used to look up and populate the manager's full name.

Order No.

GroupItemUnitCode

Example: "10"

OrgUnitNo

GroupItemId

Example: 1535

OrgUnitType

GroupItemType

Example: "Employable"

Parent Department Number

GroupGenerationItemParentGroupId

Note: The original mapping considered using GroupGenerationItemParentId, but it is recommended to use GroupGenerationItemParentGroupId for greater accuracy.

SourceID

ID

Example: 1542



User Mappings

User data is primarily imported from the emp_ImportHR.json file, with some fields originating from ImportHR.json.

eADM

Visma HR+8 Source Field

Source File

Notes

ABusinessNumber

Company Code

emp_ImportHR.json

Example: "7032"

ACostCentre1

Account Part 1

emp_ImportHR.json

Example: "37161"

ACostCentreName1

Organizational Concept 1

emp_ImportHR.json

Example: "FrPA"

ACostCentreName2

Organizational Concept 2

emp_ImportHR.json

Example: "Gbg"

ALocation

Workplace Description

emp_ImportHR.json

Example: "Gothenburg"

Position End Date

EmploymentGroups.EndDate

emp_ImportHR.json

The value may be null.

APositionTypeName

Employment Type Description

emp_ImportHR.json

Example: "Hourly employment (G)"

APositionTypeValue

EmploymentTypeId

emp_ImportHR.json

Example: 14

AUnitId

UnitCode

ImportHR.json

Example: "10"

AWorkClassificationName

Employment Type Description

emp_ImportHR.json


AAuthorizedPositionName

Long Description

emp_ImportHR.json

Maps from positions.longDescription. Example: "Personal Assistant"

Company / ACompany

Employer Name

ImportHR.json

Example: "Saltkråkan Personal Assistance AB"

Department / Parent Department

Group Description

emp_ImportHR.json

Example: "37,109 Employees"

Department Number / Parent Department Number

GroupId

emp_ImportHR.json

Note: This value should match the Department Number from the Department Mappings.

Employee Number

WorkNumber

ImportHR.json

Example: "100001"

Employee Status Code

Salary Form Description

emp_ImportHR.json

Example: "Hourly wage"

Employee Type

Agreement Category Name

emp_ImportHR.json

Example: "Personal Assistance, Needs"

Employee Type Code

Agreement Category Code

emp_ImportHR.json

Example: "e59"

External Initials

Username

ImportHR.json

Example: "9999970065"

First Name

First Name

ImportHR.json

Example: "Ole"

Email

EmailWork

ImportHR.json

The value may be null.

Mobile

Cell Phone

ImportHR.json

Example: "0677221144"

PositionCode / APositionCodeId

PositionCode

emp_ImportHR.json

Example: "5002"

Personal Email

EmailHome

ImportHR.json

Example: “identum@hotmail.com”

Private Phone

HomePhone

ImportHR.json

Example: "12341234"

SalaryCode

SalaryFormId

ImportHR.json

Example: 4

Social Security number

Social Security Number

ImportHR.json

Example: "12345612345"

SourceId

Person ID

emp_ImportHR.json

Example: 106517

Start

HireDate

ImportHR.json

Example: "January 1, 2021"

Job Openings (Positions)

Employment groups

emp_ImportHR.json

Note: You should consider using a filter to exclude closed positions from the import.

Stop

End Date

ImportHR.json

The value may be null.

Last name

Last Name

ImportHR.json

Example: "Identum"

Title / APositionCodeName

Description

emp_ImportHR.json

Maps from position description. Example: "Personal Assistant"