Introduction

Application EDI-Profiles enables activation, configuration and mappings of EDI interfaces. Depending on the interface, the mappings can be set for partners, charge types, UNLocode, containers or products.

Description

The overview displays maintained entries with their respective interface type. Using New and edit entries can be modified.

EDI Profile edit

Code

Unique codes to identify the EDI profile. The code can mostly be chosen freely, but some interfaces require a specific code.

Reference type ID

The reference type ID determines which kind of data serves as identifying reference. In this example, DQ is an external reference so incoming data is selected by this reference. Another example can be PTT which selects by shipment number. Which reference type ID is selected depends on the interface.

Attention

There is no validation regarding spelling or availability of the reference type. Setup of the initial EDI profile should only be done by users trained in Scope EDI communication.

Type of Interface

The kind if interface can be selected per Drop-Down. The following interface are currently available:

n/a
Generic
FCL Logisitk
WinWeb Connect
alH4
TOCS Interface
Aramex
TNT GL+
Sovex
Sovex Line Haul
Sovex Special
TTH/TTL

Most of these interfaces are customer specific interfaces, for our Scope generic interfaces the option Generic is used.

Contact EMail

In case an interface creates an error job in Scope, an email can be sent to the contact email address maintained in this field. One example would be missing EDI mappings.

Address mappings

Table address mappings displays maintained partner mappings for interface. New partner can be mapped using the Scope partner selection and the external ID. External ID is the ID known by the recipient of the interface.

In this example, Scope Partner A-TRANS is mapped to value 1234. 1234 is the "name" of the partner in the recipients interface.