configuration keys, conversion table, variants
The most smooth way to onboard new partners is found if you can reuse an already existing format made available by your own developer or by a Bizbrains developer at Bizbrains.
First step to achieve this is to make sure that you know the available formats (e.g. Edifact ORDERS D96A, Edifact INVOIC D96A, your own Custom XML) and which information you receive and send in these formats.
If the format is not applicable out of the box, Link has some possiblilities to adjust standard :
Afklar derfor om en eventuel afvigelse mellem dig og partneren kan løses ved:
Configuration keys – Vise hvordan
Conversion table – Vise hvordan
Varianter – forklare helt overordnet, da det er en udviklingsopgave?
Kopiere standard til nye versioner – forklare helt overordnet, da det er en udviklingsopgave?
Hvis ikke det kan løses ved ovenstående, skal udvikleren udvikle nyt format fra bunden(please be aware that this is something the developers should include in the mapping. The advantage is that they don’t need to hardcode it and once done, it can be reused with different data for different partners):
Conversion tables
The purpose of conversion tables is to convert a given value in the data received/sent to another value in the data going in/out. A perfect example of this is conversion between unit values (e.g. colli to/from cl or piece to/from pce). Description of how to set up new conversion tables: Conversions . For the developer: how to include it in the mapping…
When a conversion table is available, different values can be entered for different partners, and it also supports that one partner uses different values for the same information?
...
Configuration keys
Configuration keys are used to add data that is not available in the data received from the source system (your ERP, WMS, CRM etc) to a document for a partner. Examples: EDI Contract Number mandatory by the receiver + ---
When the configuration key is available and included in the mapping of a certain document format, the value for it can vary from partner to partner and from distribution to distribution.
NB! If the developers needs to see how to handle the configuration key and conversion table in the mapping, this is discribed in Webinar “Link for Developers” part 12 “Link REST API”: Link for Developers
Variants and versions
Existing formats can be used to build new ones.
If a format for at customer is close to an existing format and differences can’t be handled with conversions or configuration keys, the developer can use variants and versions to create new formats based on existing ones. To understand the different building blocks in link, see Link Basic Building Blocks - TDU: kræver korrektur.