Matchmodes in the XML file are used to determine how data is matched in our TMS. E.g matchmode 0 indicates that the primary key for a record in a table is provided in the XML file to find a specific record. This is unlikely, because an third party normally doesn’t have the knowledge about the primary key.
More likely is to use matchmode 1, which gives the flexibility to our TMS, where a table determines which record belongs to the value in the XML file.
| 0 | Primary key (default) Primary key value of record in database |
| 1 | Lookup via EDI provider -> default in most cases |
| 2 | Match on ISO-2 code |
| 3 | Find on code/description |
| 4 | Find city on cityname and country |
| 5 | Find address/relation using special function |
| 6 | (not in use) |
| 7 | Find country based on cityname and zipcode |
| 8 | Match on relationId |
| 9 | Match on debtorId/creditorId |
| 10 | Match using ediprovider depot table |
| 11 | Find address using xServer aliases/Strict matching |
| 12 | Find VAT code |
| 13 | Find Chamber of Commerce number |
The matchmode is an attribute of an element. Use the matchmode like this:
<customer_id matchmode=”1“>1425</customer_id>
This example indicates a customer with nr 1425 which will be linked via a table in Transpas to an already existing customer. Based on the assumption that the supplying party does not know the customer number or id in the Transpas Enterprise system.
<customer_id matchmode=”8“>1425</customer_id>
This examples indicates that a customer in Transpas Enterprise has the RelationID 1425.