EDI maps
This page is for administrators and consultants who set up Customs. It describes the EDI maps for the messages to and from customs.
Purpose
The RDN CC EDI Maps page records how the EDI messages to and from customs are structured. This is base data that users don't need to change. The assisted setup sets the maps up, but you can also choose Install CUSDEC 96A and Install CUSRES 96A on the page. Import imports a map file.
Prerequisites
- Customs has been set up with the assisted setup, or you have a map file from Rue de Net.
Permissions
You need the TOLLAKERFI RDN (Tollakerfi RdN) permission set.
Steps
- Open RDN CC EDI Maps.
- If CUSDEC or CUSRES is missing from the list, choose Install CUSDEC 96A or Install CUSRES 96A. If you received a map file, choose Import and select the file.
- Open a map to see its lines. The fields are explained below.

| Field | What it does |
|---|---|
| Code | The message code, for example CUSDEC or CUSRES. |
| Standard | The EDIFACT standard of the message. |
| Standard Version | The version of the standard, for example 96A. |
| Description | Description of the standard. |
| Imported | Says whether the map has been imported. |
EDI map
When you open a map, you see how the message is built by the standard, one line for each data element.

| Field | What it does |
|---|---|
| Line No. | Line number in the message. |
| Segment Group | The line's segment group. |
| Line Tag | The tag in the message. |
| Trans. Line Tag | The tag after translation. |
| Element | The data element. |
| Column and Sub Column | Position of the data element in the line. |
| Trans. Starting Column and Trans. Ending Column | Position after translation. |
| Mandatory | Customs rejects the message if the field is empty. |
| Numeric | The field may only contain digits. |
Verify
CUSDEC and CUSRES are on the list. The error check and sending a declaration to customs work without a map error.