Application date:

Managing Smart Bar Services

Validity date:

IDL_WMS_Description need for a specific

Page 1 of 6
IDL_WMS_Request for specifics

Nom Fonction Date Signature

Name Function Date Signature

Vérificateur Paul Groote

auditor
BIA
Schaarsberg
Approbateur
Validator

Auteur Date Version Description

Author Date Version Description

Paul Groote 23/03/2019 1.0 Creating the document

Schaarsberg
Paul Groote 08-06-2020 1.1 Update with detailed specs
Schaarsberg

INFORMATIONS WMS
Version éditeur
Editor version

Environmental information : INFOLOG U65

PARTITION :
- IDBX1PRD - 172.18.0.10 - IDBX1A01

Environnement :
- FGE50EMANL

Version English
 Application date:
Managing Smart Bar Services
Validity date:

IDL_WMS_Description need for a specific

Page 2 of 6
IDL_WMS_Request for specifics

1. BACKGROUND

Emesa and in the future also other customers of ID Logistics will use a cubiscanner solution for the registration
of product master data. This document is regarding the Zippcube from supplier Logitrade.
In this document the required process flow on the Zippcube is described including the data communication
between the Zippcube and the WMS.
The general specification of the Zippcube are not described in this document. This is part of the
documentation of Logitrade.

1.1. Process

This process has 2 touchpoints with IWMS.

1. Upload of product master data to a shared directory .
2. Pickup measured products from shared directory and process this data into the WMS.

2. CHANGE REQUEST

Create an extract of the product master data from the WMS. This export runs daily and is placed on a shared
network drive via XMS. The export can also be triggered manually in case of last minute new products.

Import the measured master data export from the Zippcube into IWMS. This with an interval of every minute.
In the WMS the product master data (GEPRO) needs to be updated.

Version English
 Application date:
Managing Smart Bar Services
Validity date:

IDL_WMS_Description need for a specific

Page 3 of 6
IDL_WMS_Request for specifics

As described earlier in this document the solution will be used for multiple clients. The output of the Zippcube
is fixed an can not be changed per client. Therefore the mapping must be done on XMS/WMS level. This
document describes the mapping for EMESA.
Summarized the following needs to be developed:
- Export of products
- XMS process to put the files on a network location.
- XMS process that takes files from a network location
- Import program that updates the product master data including logging.

Following the specifics per development:

2.1. Export of product

All GEPRO records that do not have the status 40 (ETAPRO) needs to be extracted for the WMS with the
format:

Daily export has the following layout.

CSV file semicolon separated.

Normal description:
Product EAN (main);Productcode;activity code;Product description;Processed.

INFOLOG names (GEPRO)

EDIPRO;CODPRO;CODACT;DS1PRO&DS2PRO;’If HAUUVC is greater than ‘zero’s’ = ‘Y’, otherwise = ‘N’

CSV name INFOLOG field Rules Example

Product EAN (main) GEPRO.EDIPRO 5023041289802
Product code GEPRO.CODPRO 4015
Activity code GEPRO.CODACT Select only ‘EMA’ EMA
Product description GEPRO.DS1PRO & Not spaces between the Liora marquise armband
GEPRO.DS2PRO two fields met swarovski
elementen (15527) || Pr
Processed GEPRO.HAUUVC If the product is already Y
processed (HAUUVC is
greater than ‘zeros’) the
value is ‘Y’ otherwise ‘N’

This file needs to be place on a newly created IFS locations.

Suggestion:
Version English
 Application date:
Managing Smart Bar Services
Validity date:

IDL_WMS_Description need for a specific

Page 4 of 6
IDL_WMS_Request for specifics

/IDBX1A01/FGE50EMANL/ZIPPCUBE/OUT

2.2. XMS process to put files on network location

A process in the XMS move the exported file from the WMS and puts it on designated network location within
the IDL network. When doing this, the ‘old file’ from yesterdays export will be overwritten by the XMS
process.

The file created in point 2.1 needs to be move to //NLETLFL01/FGE50EMANL/ZIPCUBE/IN

2.3. XMS process that takes from network location

An XMS process is polling in a location in the IDL network. If a file is placed with the prefix EMANL* and
extension *.txt, it is picked up by the XMS and moved to a backup directory.

The file created by the Zippcube needs to be move from //NLETLFL01/ FGE50EMANL/ZIPCUBE/OUT to the IFS
location of XMS. There it is processed as described with point 2.4.

2.4. Import program that updates the product master data

An import program needs to be created that update specific fields of the PRODUCT MASTER data GEPRO
This import program needs to map the data from the export lay out from the Zippcube to the correct fields in
the WMS.

It is required that also a logging record is created (GEPROJ1)

Structure of the import file:

HDR;update user;barcode;pallettype;colli per layer; no of layers;variable field 1; variable field 2; ...

UOM;type;lenght;width;height;weight;piece in UOM
Example:
HDR;123456;EURO;5;10;Yes;A01001003;
UOM;PCE;1225;1000;625;3000;1
UOM;BOX;2450;2000;625;12000;4

Mapping of fields of the CSV file into the WMS product codes :
HDR;update user;activity;barcode;pallettype;colli per layer; no of layers;variable field 1; variable field 2; ...
Version English
 Application date:
Managing Smart Bar Services
Validity date:

IDL_WMS_Description need for a specific

Page 5 of 6
IDL_WMS_Request for specifics

Notmapped;GEPROJ1.CODUTI;GEPRO.CODACT;GEPRO.CODPRO;GEPRO.CODEMB;GEPRO.COLCOU1;GEPRO.C
OUPAL1 ; GEPRO.CODMDS ;GEPRO.ZONPRF ;GEPRO.ABCSTS ;GEPRO.CODMDP ;GEPRO.CIRDET
Mapping HDR record
CSV name Infolog field Rules Example
Identifier N/A If HDR, map following HDR
HDR rules. IF UOM, map
following UOM rules
Update user GEPPOJ1.CODUTI Add time stamp based GSCHAARSBE
on import time of the
file
Activity GEPRO.CODACT EMA
Barcode GEPRO.CODPRO Always VALPRO = 00 4015
Pallettype GEPRO.CODEMB EUR
Colli per layer GEPRO.COLCOU1 12
No of layers GEPRO.COUPAL1 Calculate pallet weight / 20
layer heigt, width, etc
based on this and UOM
information
Variable field 1 GEPRO.CODMDS RAC
Variable field 2 GEPRO.ZONPRF A
Variable field 3 GEPRO.ABCSTS R
Variable field 4 GEPRO.CODMDP STD
Variable field 5 GEPRO.CIRDET PCK
Variable field 6 GEPRO.CIRPAL 999

UOM;type;lenght;width;height;weight;piece in UOM
If unit of mesure (type) is PCE
Notmapped ;seecondition ;GEPRO.LNGUVC;GEPRO.LRGUVC;GEPRO.HAUUVC;GEPRO.PDBUVC&GEPRO.PDNUV
C;
If unit of mesure (type) is BOX
Notmapped ;seecondition ;GEPRO.LNGCOL;GEPRO.LRGCOL;GEPRO.HAUCOL;GEPRO.PDBCOL&GEPRO.PDNCOL
;

Version English
 Application date:
Managing Smart Bar Services
Validity date:

IDL_WMS_Description need for a specific

Page 6 of 6
IDL_WMS_Request for specifics

Mapping UOM type PCE

CSV name Infolog field Rules Example
Identifier N/A If HDR, map following UOM
HDR rules. IF UOM, map
following UOM rules
Type N/A If type is PCE map PCE
following PCE rules. If
type is BOX map following
BOX rules.
All is linked with
CODACT,CODPRO,VALPR
O of connected HDR line
Lenght GEPRO.LNGUVC 19,50
Width GEPRO.LRGUVC 2,70
Height GEPRO.HAUUVC 12,00
Piece in UOM N/A PCE is smallest UOM. 1

Mapping UOM type BOX

CSV name Infolog field Rules Example
Identifier N/A If HDR, map following UOM
HDR rules. IF UOM, map
following UOM rules
Type N/A If type is PCE map BOX
following PCE rules. If
type is BOX map following
BOX rules.
All is linked with
CODACT,CODPRO,VALPR
O of connected HDR line
Lenght GEPRO.LNGCOL 37,00
Width GEPRO.LRGCOL 6,10
Height GEPRO.HAUCOL 20,40
Piece in UOM GEPRO.PCBPRO 6

Version English