Usage > Interfaces > Setup 

This function allows to set up and to define the flow exchanges in import/export of the « interfaces » type.

A certain number of interfaces are pre defined and delivered as standard on the application.

Interface direction

Interface code

Description

L3

L3 to L2

ITM

Import items and its containers

X

L3 to L2

EIN

Import expected inputs

X

L2 to L3

XEIN

Receipt Report

X

L3 to L2

INP

Import direct inputs

X

L2 to L3

XINP

Storing Report 

X

L3 to L2

DLO

Import delivery orders

X

L2 to L3

XDLO

Preparation Report

X

L2 to L3

XSHP

Delivery Report

X

L2 to L3

XAJM

Stock adjustments report

X

L2 to L3

XISO

Stock image

X

L3 to L2

INISLO

Locations assignment

X

L3 to L2

INISKO

Stock initialization

X

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

The definition of the interfaces is keyed in for each flow.

It is recommended to duplicate the existing one to conserve the reference setting.

The interfaces in the direction of Warehousing to level 3 are prefixed X (for  export).

The interfaces in the direction of Level 3 to  Warehousing are not prefixed.

Entry screen

Presentation

Setting : name of the file such as it is transmitted or created by Warehousing.

Interface

So that it can be generated or integrated, the setting should be active.

The sequence allows to order the import and the exports for each of the flow.

It is also possible to define a time bracket during which the interface will be active.

Environment

For each interface setting, it is possible to limit the list of sites/depositors concerned by the interface.

Thus, the different files linked to the different templates according to the couple (sites, depositors) could be defined if necessary.

Flat files

The name of the template linked to the interface should be specified.

The sequence number is active only for the interfaces in export.

Lastly, it is possible to define a pathway  different to that defined on the default value (chapter INT) so as to locate the interface files to be processed and that rejected.

Close

 

Fields

The following fields are present on this tab :

Block number 1

Name of the interface file

  • Description (field ITADESAXX)

 

Interface

  • Active (field ENAITA)

If checked, the interface will be managed in emission/receipt mode (based on the emission movement code).

Code of the interface on which the template is based.

  • Sign (field ITRTYP)

 

  • Sequence (field ORN)

Number making it possible to use the rules defined in this screen

by order of priority.

  • Start time (field HOUDEB)

No help linked to this field.

  • End time (field HOUFIN)

 

Grid Environment

Code of the site for which the report interface is generated. This makes it possible, among other things, to manage different files on receipt based on the site and/or the depositor.

The value '*' makes it possible to use this template for all the sites of the folder.

Code of the depositor for which the report interface is generated.

The value '*' makes it possible to use this template for all the depositors of the site.

Written files

  • Active (field FILFLG)

This flag needs to be checked for any receiving and/or issuing interface. only the generation of flat files is available to date.

Name of the template used to generate the interface.

Name of the counter used to generate the interface files.

  • File path (field FILMAC)

Mentions the physical directory where to find the integrated files or the files to be integrated.

Used to short-circuit the IMPREP and EXPREP general parameters of the INT chapter.

  • Reject path (field ERRMAC)

For the receipt interfaces, used to short-circuit the IMPERRREP general parameter of the INT chapter, in case of file integration error.

Close

 

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Template for interface XXX.

A control is carried out between the interface type and the template of the interface type keyed in.  

Tables used

SEEREFERTTO Refer to documentation Implementation