Mappings

The mapping connects the partner message to the internal data model: which segment and data element becomes which field? There is one definition per direction and per partner – plus a default that applies when a partner needs no deviation of their own.

What is this for?

• Map segments and data elements onto the fields of the data model.
• Encapsulate partner deviations without touching the default.
• Describe the inbound and outbound direction separately.

How to set it up

1. Mapping files live per tenant under Tenants\<tenant>\mappings\.
2. The file name follows the pattern <partner|_default>_<message>_<direction>.map.json – for example _default_ORDERS_in.map.json for the default of incoming orders.
3. If a partner deviates, a file carrying their partner code is created; it takes precedence over the default.
4. Values that differ between partner and your own system do not belong in the mapping but in the code lists.
5. A fixed function library is available for conversions – deliberately not a free scripting language, so mappings stay reviewable.