Skip to content
Guide

Search the Guide

Enter a query to search the Guide.

Íslenska
Menu
On this page

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

  1. Open RDN CC EDI Maps.
  2. 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.
  3. Open a map to see its lines. The fields are explained below.

EDI maps

FieldWhat it does
CodeThe message code, for example CUSDEC or CUSRES.
StandardThe EDIFACT standard of the message.
Standard VersionThe version of the standard, for example 96A.
DescriptionDescription of the standard.
ImportedSays 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.

EDI map

FieldWhat it does
Line No.Line number in the message.
Segment GroupThe line's segment group.
Line TagThe tag in the message.
Trans. Line TagThe tag after translation.
ElementThe data element.
Column and Sub ColumnPosition of the data element in the line.
Trans. Starting Column and Trans. Ending ColumnPosition after translation.
MandatoryCustoms rejects the message if the field is empty.
NumericThe 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.