Table of contents

• Abstract
• Why do we need configs?
• The Config in detail
• Schedules
• Direct mapping
• Direct mapping example
• Value transformations
• Value transformation examples

Abstract

A Config is a file that specifies how the information defined in a Template can be either pulled from or sent to a Connector. This is done by mapping the ILAP Terms in the template to the Host fields in the Connector. Two matching Configs enable the data transfer across planning systems and organisations. Configs are created and managed by Setup users.

Conceptual visualisation of a Config, consisting of a Template with ILAP terms, a Connector with Host field values and Mappings and transformations to connect the ILAP Terms to the Host field values.

Why do we need configs?

Today, host fields in different plannings system are not compatible. The Configs specify how the planning system specific host fields relate to the ILAP Terms. This way, the Host fields from planning system A can be transformed into ILAP terms, where after they van be transformed into Host fields from planning system B. The Configs also define where exactly the correct host field values are pulled from or sent to. This means that one Config can be used to create ILAP exchange agreements (IEAs) for all schedules that have the same setup.

The Config in detail

Other than a Template and a Connector, a Config also has a direction (either sending or receiving), a set of schedules that the config applies to, direct mapping of fields, values transformations for fields and Host system parameters. Below, more information about the latter four concepts can be found.

Schedules

Configs can be used my multiple schedules, as long as they reside in the same Connector and have the same setup. The list of these schedules can be found on the first page of a connector

The “Schedules” page of a config.

Direct mapping

Most field values can be imported or exported in its original format. In these cases “direct mapping” applies. The Setup user simply has to define what Host field corresponds with the ILAP Term in the selected schedule(s). These Host fields can be found on this page. If Direct mapping is turned off, it means a Value transformation is required.

Direct mapping example

Example

The “Direct mapping” page of a config.

Value transformations

Values in the planning systems that do not comply to the Content Control of the ILAP terms, require a value transformation. Value transformations can be done with a formula and/or with a value map. All the information about value transformations can be found in this screen. More about mapping formulas and value maps can be found in the article about defining value transformations.

Value transformation examples

Example

The “Value transformation” page of a config.

Host system parameters

Host system parameters are settings to control the data that is being transferred. These settings differ for each host system and for the direction the data is being transferred.

The “Host system parameters” page of a config