Custom Import Mappings

Use this tab to import data from an external source.

The supported sources are:

• An Excel file, which can contain one or more worksheets.
• A CSV file.
• SQL Server / Oracle.

This task type can be used as a supplement to the existing Maconomy integration, or it can be used to build an integration to a third-party system, such as a SAP system.

Note: You can only use this to import data into People Planner. If you need to export data from People Planner to a third-party system, you should use the External Views instead.

When setting up such a task, you start by defining a custom import mapping. The purpose of a custom import mapping is to act as a translator between the data formats of the external source and those of the internal People Planner tables.

When you have defined the custom import mapping, you can use it to define the task specification, and you can add a scheduled task on top of that to provide automated execution:

A Word of Caution

Custom import mappings import external data almost directly into the tables in the People Planner database. In certain cases, a custom import mapping may partially bypass the normal business logic built into the People Planner application. This can result in the creation of data structures that would not normally be possible-or at least are highly unusual-and in a way that results in People Planner not performing very well.

As with any powerful tool, the custom import mapping requires expert knowledge of how to use it properly, or it can result in unforeseen issues. In the case of custom import mappings, some extra knowledge about the business logic of People Planner is certainly required.

To put it in another way: Just because your custom import mapping seems to be working, this is not a guarantee that it works well.