Integration guide for CONSIGNOR
– Integration with your ERP system.
This document contains a description of CONSIGNOR transport administrative solution and how CONSIGNOR integrates with an ERP system.
It is our aim that you observe how your company currently handles the logistics function including which types of packages are sent out and with which carrier. This information will be requested of you in a schema that we send to you.
Should questions arise when reading through this document, you are most welcome to either e-mail them to us at [email protected] or call us on 23 24 94 80. You can also find more information regarding integration between CONSIGNOR and your ERP system on our website at the following address www.edi-soft.no.
1. Concept
CONSIGNOR is a system designed for easy and efficient printing of labels, to address and send goods which are to be handled and delivered by a range of carriers, for example Posten Norge, Bring, Schenker, Tollpost, DSV, DHL, Nor Lines, Ramberg, and many more who use EDI data. CONSIGNOR may also be used to print labels for carriers who are not set up to handle EDI data. For an updated list of EDI supported carriers, please see our website www.edi-soft.no.
To avoid retyping a receiver address, CONSIGNOR contains two types of address catalogues into which receiver data can be saved.
1. The first catalogue (Address Register) is designed to contain addresses which are imported during the installation of CONSIGNOR, and is maintained as CONSIGNOR is used for production.
2. The second catalogue (Order Register) is dynamically updated during the import of data from your ERP system, and can be used to register information from an order form or requisition. It is also possible for CONSIGNOR to save this imported data in a fixed address catalogue, and thereby simplify the task of creating manual shipments.
(A Microsoft Excel file, or similar, may be used should you require that a fixed address catalogue be imported for use as a fixed address catalogue. This catalogue can be continually updated by CONSIGNOR’s ability to save data to this catalogue when printing labels).
Most ERP systems handle mainly financial data, and therefore often have their databases protected against other users or systems from having READ access to them. EDI-Soft has therefore chosen to build the CONSIGNOR solution to dynamically update it’s data via import of ASCII files which are generated by the ERP system, and which are dropped into a folder by your ERP system for CONSIGNOR to import.
CONSIGNOR can also export shipping information back to your ERP system by saving shipping data into files in a folder available to your ERP system. (See Appendix 3. for further information). There is therefore no direct connection between CONSIGNOR and your ERP system.
Usually there is some form of documentation to accompany shipments; Order number, Requisition number, package receipt or invoice. Most ERP systems are very flexible as regards printing these documents. Customers and suppliers of ERP systems should therefore agree upon a suitable document, which when printed from the ERP system, will generate an ASCII file with delivery information from the ERP system to CONSIGNOR. Typically, there will be specific information used in the formation of this file, the description of which is specified in the article “ASCII file requirements”.
A specially designed import routine developed by EDI-Soft, imports data from ASCII files to the CONSIGNOR database. This means that printing of labels is easily and efficiently performed by the CONSIGNOR user being required to supply very little data or no data at all.
CONSIGNORoffers manual, half-automatic or fully automatic printing solutions.
In a half-automatic solution, data is imported into CONSIGNOR by typing in a unique reference number, e.g. Order or invoice number, where after the user may choose how many labels are to be printed, select the different the shipment weights and choose which carrier is going to handle the shipment etc.
In a fully automatic solution, ALL receiver and shipping- related data is sent to CONSIGNOR from the ERP system. The ASCII file therefore needs to contain codes to determine the shipping method (carrier, product, pallet type (as required by carrier), recycle pallet type (as required by carrier), how many recycle pallets (as required by carrier), carrier services (as required by carrier), goods type (as required by carrier), receiver address, number of labels, weight, volume (as required by carrier) etc. In this fully automatic mode, the user does not need to interact with CONSIGNOR at all – files are sent with a COMPLETE set of required delivery data from the ERP system to CONSIGNOR’s import folder. These are automatically imported into
CONSIGNOR and labels are automatically printed once the data is read into CONSIGNOR. Note:-
It is of primary importance when using either half or fully-automatic printing solutions, that all of the required data (for the printing method in use) is saved into the file by the ERP system which is to be imported into CONSIGNOR and that the data is placed into the correct fields in the file. If this is not done, labels will not print as planned, but can still be manually printed with little data manipulation in CONSIGNOR.
E.g.:-
1- The ERP system sends a file to CONSIGNOR with no shipment weight specification for a carrier requiring that weight be specified. If, in CONSIGNOR, this carrier requires WEIGHT as a mandatory value, then a label for that carrier with no weight specification cannot be printed from CONSIGNOR.
2- The ERP system sends data to incorrect fields, E.g. Telephone number placed into the country name field. If the file sent to CONSIGNOR by the ERP system does not have sufficient or valid information to create a shipment and print a label and CONSIGNOR is running a fully-automatic import, the data is still imported into the CONSIGNOR database, but it remains in CONSIGNOR’s INBOX for further correction and the next delivery is handled by CONSIGNOR. CONSIGNOR simply stores the incorrect shipment data and begins automatically processing the next delivery with no interruption to your shipping process. The CONSIGNOR user can then manually correct the delivery information stored in the INBOX and print the label.
For more information about CONSIGNOR’s import, please see Appendix 1 “Scenario…”
ERP, web,
or other
system.
CONSIGNOR
2. ASCII file requirements
As concerns delivery, most information on an invoice is of relevance.
When considering an import file format, we require that you send us a description of which data is to be written to the file, and into which field order the information is to be placed. We strongly recommend that you do not use data fields which are of no relevance to the way in which your deliveries are to be handled. There are over 240 different fields of data, which CONSIGNOR can import, but only very few are usually necessary.
Below is a list of the current possible fields, containing necessary data, recommended data and possible data. It is important to note that should you require CONSIGNOR to run in fully-automatic mode, then some of the data which exists in the possible data section, becomes mandatory, and is therefore required. This has been marked in bold typeface in the table. Most CONSIGNOR installations that use fully-automatic printing require no more than 30 fields from the table below, even in complex setup environments.
The following data is required in the ASCII file.
Field
Number Fields group Field name
Felt navn
Field Description
1
Line
OrderNumber
Ordrenummer
Unique key (order number, invoice no.)
2
Receiver
Name1
Navn 1
Receiver name – Company or private person
3
Receiver
Name2
Navn 2
C/O or department .
4
Receiver
Address1
Adresse 1
Street/Road – must be delivery address.
5
Receiver
Address2
Adresse 2
Department, building, Port etc.
6
Receiver
PostBox
Postboks
Only if this exists.
7
Receiver
PbxNo
Postboks
postnummer
Only if this exists.
8
Receiver
PbxCity
Postboks by
Only if this exists.
9
Receiver
City
By
Name of delivery city.
The following data is recommended in the ASCII file.
Field
Number
Fields
group
Field name
Felt navn
Field description
11
Receiver
CustNo
Kundenummer
Receiver customer number.
12
Reference
Attention
Kontaktperson
Receiver or sender contact person.
13
Receiver
E-mail adresse
Required if mail back function is used in
CONSIGNOR.
14
Reference
Receivers
Reference
Mottaker
referanse
Requisition/invoice number.
The following data is possible in the ACSII file.
Fields group Field name
Felt navn
Field description
15
Line
Number
Antall kolli
Number of labels to print. Required
for fully-automatic printing.
16
Line
Marking
Merking
Marking given as text, but rarely used.
17
Line
Contents
Innhold
Parcel or pallet contents.
18
Line
Weight
Vekt
Parcel or pallet weight Required for
fully-automatic printing.
Eg. Schenker.
19
Line
LineWeight
Linje vekt
Total shipment weight.
20
Line
Height
Høyde
Height – used for volume calculation.
21
Line
Length
Lengde
Length – used for volume calculation.
22
Line
Width
Bredde
Width – used for volume calculation.
23
Line
Volume
Volum
Volume – Eg. Pallet volume.
24
Line
LineVolume
Linje volum
Total volume for the shipment.
25
Line
Loadmeter
Lastemeter
Loadmeter value.
26
Line
RecycleType
Retur gods type
Recycle pallet type (PL1, PL2 etc).
28
Line
GoodsType
Gods type (art)
PL1, PL2 etc.
29
Line
SpecialGoods
Spesial gods
Special goods, required if agreed with
carrier.
30
Line
ReceiverRef
Mottaker referanse
Receiver reference – often
invoice/requisition number.
31
Line
OrderNumber
Ordrenummer
Unique search key (Order number,
invoice number).
32
Line
Additional
Ekstra
No specific description.
33
Package
Label
Kollinummer
(Track'n Trace
nummer)
Contains shipment number usually
exported back to ERP system, to
facilitate ERP system’s track and trace
function.
34
Package
ReceiverRef
Mottaker referanse
Receivers reference.
35
Package
OrderNumber
Ordrenummer
Order number.
36
Package
Additional
Ekstra
No description as yet.
37
Package
PackageNo
Pakkenummer
Package number 1/3, 2/3, 3/3 etc.
38
Receiver
CustNo
Kundenummer
Receiver’s customer number.
39
Receiver
Name1
Navn 1
Name of receiver – company or private
40
Receiver
Name2
Navn 2
Evt. C/O .
41
Receiver
Address1
Adresse 1
Street/Road or delivery address.
42
Receiver
Address2
Adresse 2
Department, building, Port etc.
43
Receiver
PostNo
Postnummer
4 digits in Norway.
44
Receiver
City
By
Name of delivery city.
45
Receiver
Country
Landekode
Necessary for international deliveries.
46
Receiver
PostBox
Postboks
Only if this exists.
47
Receiver
PbxNo
Postboks
postnummer
Postcode of receiver postbox.
49
Receiver
Phone
Telefonnummer
Required when sending COD
shipments with Posten Norge.
50
Receiver
Mobile
Mobilnummer
Used for example with SMS service for
carrier Posten Norge.
51
Receiver
Fax
Faksnummer
Receiver’s fax number.
52
Receiver
E-mail adresse
Required when sending e-mail
notification to receivers.
53
Sender
CustNo
Kundenummer
ERP system’s customer number.
54
Sender
Name1
Navn 1
Alternative sender name.
Note:- ”Dynamic Sender” is only
possible for use with those carriers
who permit ad hoc changing of sender
names on labels and in EDI files.
55
Sender
Name2
Navn 2
Sender department, section etc.
56
Sender
Address1
Adresse 1
Sender street/road.
57
Sender
Address2
Adresse 2
Sender Department, building, port etc.
58
Sender
PostNo
Postnummer
4 digits in Norway.
59
Sender
City
By
Sender’s city.
60
Sender
Country
Landekode
Sender country code. Required for
international shipments.
61
Sender
PostBox
Postboks
Provided when sending from a post
box address.
62
Sender
PbxNo
Postboks
postnummer
Required when sending from a post
box address.
63
Sender
PbxCity
Postboks by
Required when sending from a post
box address.
64
Sender
Phone
Telefonnummer
Sender phone number.
65
Sender
Mobile
Mobilnummer
Sender mobile phone number.
66
Sender
Fax
Faksnummer
Sender fax number.
67
Sender
E-mail adresse
Sender e-mail address.
68
Payer
CustNo
Kundenummer
Customer number.
70
Payer
Name2
Navn 2
Payer department, section etc.
71
Payer
Address1
Adresse 1
Payer street/road of payer address.
72
Payer
Address2
Adresse 2
Payer department, building, port etc.
73
Payer
PostNo
Postnummer
4 digits in Norway.
74
Payer
City
By
Payer’s city name.
75
Payer
Country
Landekode
Payer’s country code – e.g. DK, DE,
NO.
76
Payer
PostBox
Postboks
Only if this exists.
77
Payer
PbxNo
Postboks
postnummer
Postcode of payer’s post box.
78
Payer
PbxCity
Postboks by
Payer’s city name of post box.
79
Payer
Phone
Telefonnummer
Payer phone number.
80
Payer
Mobile
Mobilnummer
Used for example with SMS service for
carrier Posten Norge.
81
Payer
Fax
Faksnummer
Payer’s fax number.
82
Payer
E-mail adresse
Payer’s e-mail address.
83
Buyer
CustNo
Kundenummer
Buyer’s customer number.
84
Buyer
Name1
Navn 1
Buyer name – company or private.
85
Buyer
Name2
Navn 2
Buyer’s department, section, etc.
86
Buyer
Address1
Adresse 1
Buyer’s street/road address.
87
Buyer
Address2
Adresse 2
Department, building, port etc.
88
Buyer
PostNo
Postnummer
4 digits in Norway.
89
Buyer
City
By
Buyer’s city name.
90
Buyer
Country
Landekode
Buyer’s country code: e.g. DK, DE, NO.
91
Buyer
PostBox
Postboks
Only if this exists.
92
Buyer
PbxNo
Postboks
postnummer
Buyer’s post box number.
93
Buyer
PbxCity
Postboks by
Buyer’s city name of post box.
95
Buyer
Mobile
Mobilnummer
Used for example with SMS service for
carrier Posten Norge.
96
Buyer
Fax
Faksnummer
Buyer’s fax number.
97
Buyer
E-mail adresse
Buyer’s e-mail address.
98
Product
Service Groups
Service grupper
No description of this field.
99
Dangerous
UNNumber
Un nummer
Contains the UN number of Dangerous
Goods type.
These are Transport
standards that must be adhered to.
EDI-Soft does not have these.
100
Dangerous
Kind
Type
Dangerous goods type kind.
These are
Transport standards that must be
adhered to. EDI-Soft does not have
these.
101
Dangerous
Name
Navn
Name of Dangerous goods
102
Dangerous
Templates
Kladd
No description of this field.
103
Dangerous
Description
Beskrivelse
Dangerous goods type description.
These are Transport standards that
must be adhered to. EDI-Soft does not
have these.
104
Dangerous
Class
Klasse
Dangerous goods classification.
These
are Transport standards that must be
adhered to. EDI-Soft does not have
these.
105
Dangerous
Classification
Code
Klassifikasjons kode
Dangerous goods classification code.
These are Transport standards that
must be adhered to. EDI-Soft does not
have these
106
Dangerous
PackingGroup
Pakkegruppe
Dangerous goods packing group
specification.
These are Transport
standards that must be adhered to.
EDI-Soft does not have these
107
Dangerous
Identification
Identifikasjon
Dangerous goods identification.
These
are Transport standards that must be
adhered to. EDI-Soft does not have
these.
109
Dangerous
NetWeight
Nettovekt
Nett weight of dangerous goods.
110
Dangerous
Volume
Volume
Volume of dangerous goods.
111
Dangerous
Number
Pakkenummer
Contains shipment barcode number of
dangerous goods.
112
Dangerous
EMSNumber
EMS nummer
Contains EMS number of dangerous
goods. .
These are Transport standards
that must be adhered to. EDI-Soft does
not have these.
113
Dangerous
MfagNumber
Mfag nummer
Contains Mfag number of dangerous
goods.
These are Transport standards
that must be adhered to. EDI-Soft does
not have these.
114
Dangerous
PageNumber
Sidetall
Contains a page count of dangerous
goods papers.
115
Dangerous
FlashPoint
Flammepunkt
Contains the minimum temperature
that the Dangerous goods will begin to
ignite and/or burn. (Combustion point)
116
Dangerous
Stowing
Category
Pakkningskategori
Category of how goods are to be
packed and stored. .
These are
Transport standards that must be
adhered to. EDI-Soft does not have
these.
117
COD
Amount
Beløp
COD amount. Given in whole numbers
without a thousand separators, e.g.
10000,00.
118
COD
Reference
Betalingsreferanse
Usually invoice number, or a number
used for bookkeeping purposes. Only
used by a few carriers.
119
COD
KID
KID kode
KID code follows EDI-Soft’s message to
Posten Norge.
120
COD
Account
Kontonummer
Account number, GIRO number used
121
Insurance
Amount
Beløp
Insurance amount.
122
Insurance
Contents
Innhold
Insured package contents.
123
Insurance
Category
Kategori
Insured package category.
124
Insurance
E-mail adresse
Sender’s e-mail contact address.
125
Insurance
PolicyNo
Policenummer
Insurance policy number.
126
Reference
Ordernumber
Ordrenummer
Sender’s order number as a receiver
reference.
127
Reference
ReceiverRef
Mottaker referanse
Reference requested by the receiver.
Usually an order/requisitions/invoice
number.
128
Reference
Operator
Betjenings
medarbeider
Staff member who created the order.
129
Reference
Project
Prosjekt
Name/number of a given project
running between a sender and
receiver.
130
Reference
Attention
Kontaktperson
Contact person name of sender or
receiver.
131
Reference
Delivery Date
Leveringsdato
Delivery date of shipment. This is
information given by the sender, and is
not something that the carrier will
guarantee.
132
Reference
Receivers
Reference
Mottaker referanse
Receiver reference. E.g. Invoice
number.
133
Reference
Receivers
Customer
No at Sender
Mottakers
kundenummer
hos avsender
Receiver’s Customer number at
Sender.
134
Reference
Receivers
Customer
No at Carrier
Mottakers
kundenummer
hos transportør
Receiver’s Customer number at Carrier
135
Reference
Senders
Reference
Avsenders referanse Sender’s reference, often an order
number.
136
Reference
KID
KID kode
KID code reference follows EDI-Soft’s
message to Posten Norge.
137
Reference
Project Name
Prosjekt navn
Name/number of a given project
running between a sender and
receiver.
138
Reference
Goods Type
Gods type
PL1, PL2, CLL etc.
139
Reference
Agent number
Agent nummer
If there is an agent associated with a
shipment, their ID number can be
given here.
140
Reference
Terminal
Terminal
141
Reference
Carrier Account
Transportør
kontonummer
Contains sender’s account number
with the carrier. Used for e.g. With
payment of COD amount.
142
Reference
Custom Field 1
Spesial felt 1
Free reference field that may be used
for custom labels.
143
Reference
Custom Field 2
Spesial felt 2
-||-
144
Reference
Custom Field 3
Spesial felt 3
-||-
145
Reference
Custom Field 4
Spesial felt 4
-||-
146
Reference
Custom Field 5
Spesial felt 5
-||-
147
Reference
Custom Field 6
Spesial felt 6
-||-
148
Reference
Custom Field 7
Spesial felt 7
-||-
149
Reference
Custom Field 8
Spesial felt 8
-||-
150
Reference
Custom Field 9
Spesial felt 9
-||-
151
Reference
Custom Field 10 Spesial felt 10
-||-
152
Reference
Payer Agent
Number
Frakt betalers
agent nummer
Shipment’s agent ID number can be
given here.
153
Reference
Additional
ordernumbers
Flere Ordrenumre
Used with many orders in the same
shipment container. Makes combined
shipping easier to control.
154
Message
Driver
Sjåfør
Message to driver. Carrier may not
support this. This will not be printed to
the label
155
Message
Carrier
Transportør
Message to carrier. Carrier may not
support this. This will not be printed to
the label
156
Message
Receiver
Mottaker
Message to receiver. Carrier may not
support this. This will be printed to the
label.
157
Price
FixedPrice
Fastpris
Price is primarily used when
shipping/freight price is to be sent
from CONSIGNOR to ERP system and
can be used in the receiver invoicing
process. This requires that there is a
price calculation module set up in
CONSIGNOR. Not all carriers can use
this, given their pricing structure.
158
Price
Price 1
Pris 1
-||-
159
Price
Price 2
Pris 2
-||-
160
Price
Price 3
Pris 3
-||-
161
Pickup
Pickupdate
Avhentningsdato
Collection/Pickup date of shipment.
162
Shipment
CarrierCode
Sendingsmåte
One single code to select shipping
method. EG. Code ”10” = Posten
Norge, Bedriftspakke dør-dør.
One code will be assigned to the
complete shipping combination.
REQUIRED FOR FULL-AUTOMATIC
PRINTING. We require that you have
on hand, a list of all carrier codes, as
well as a list of all shipping
combinations that will be used in
sending shipments with these codes.
163
Shipment
ShipmentKeyNo Forsendelsesnøkkel
nummer
No description of this field.
164
Shipment
Pickup Date
Avhentningsdato
Collection/Pickup date of shipment.
Used with predating shipments.
E.g. A parcel with a label printed on 1st
March, but to be collected by the
carrier on 1st April.
165
Shipment
Height (mm)
Høyde (mm)
Total shipment height in millimetres
166
Shipment
Width (mm)
Bredde (mm)
Total shipment width in millimetres
167
Shipment
Length (mm)
Lengde (mm)
Total shipment length in millimetres
168
Shipment
Senders Account
Number
Avsenders
kontonummer
Senders account number, GIRO
number used for payment of COD
amount.
169
Shipment
Number
Sendingsnummer
(Track'n Trace)
Used when shipping barcode numbers
are imported from the ERP system.
170
Shipment
Senders
Customer
No at Carrier
Avsenders
kundenummer
hos transportør
Customer number at carrier.
171
Shipment
LinesCount
Linjeantall
Total number of lines.
172
Shipment
Dangerous
Farlig gods
Denotes whether dangerous goods are
contained within the total shipment.
174
Shipment
Carriage Payer
Forsendelses betaler No description of this field.
175
Shipment
Actor Alias
Klient alias
No description of this field.
176
Shipment
PrinterKey
Printer nøkkel
Printer key alias used with fully
automatic printing to more than one
printer. This code denotes which
printer the print job is to be sent to.
3. ASCII file format.
One order per line. Fields can be separated by comma, semi-colon or other character or the data can be separated by a fixed field length. If data is character-separated, the fields should start and end with “. Each line should close with a line break. 8-Bit ASCII character set must be used. Other file formats can only be used by further agreement with EDI-Soft.
An example import file format could be:
"10026","Audio Visuel Information ASA","31121","Stålfjøra 9","Postboks 106”,”NO” or
10026 Audio Visuel information ASA 31121 Stålfjøra 9 postboks 106 NO
First example is comma-separated; the second is of fixed field length.
4. Order and length.
Every import setup is customised to each customer’s requirements, therefore there will be a difference between file length and field order from one customer to another. What is important is that your ERP system generates delivery data into the CONSIGNOR import file in the same order each time an order is processed. CONSIGNOR’s field-mapping can be created and mapped according to your own ordered data file.
Similarly, carrier and printer alias codes need to be sent consistently from the ERP system to CONSIGNOR.
5. Naming of ASCII files.
Importing of ASCII files into CONSIGNOR is not synchronised when saving the files to CONSIGNOR’s import folder. Therefore it is necessary to observe file-naming conventions to avoid the ERP system overwriting previous files saved to CONSIGNOR’s import folder. This task is the responsibility of the ERP system administrator. The following solutions to this problem are as follows:-
One file – same name:
Some ERP systems wish to write to the same file with the same name each time a delivery is to to be registered, e.g. RUBICON ERP system. If the file does not exist, a new one will be created with a predefined filename. If the file is found, a new line will be appended within the existing file. CONSIGNOR imports and deletes this file after a successful import.
One file for each order:
Other ERP systems place each order into their own file. These files can advantageously be named with their order number and a fixed predefined extension. e.g. 214565.txt
CONSIGNOR imports all files automatically and either deletes or moves the file to a backup folder after a successful import.
Many files with many orders in each file:
Other ERP systems write many orders into files with unique file names. In this case, naming files after their order number is not a good idea, as there is a real risk of the ERP system overwriting files with the same order number before CONSIGNOR can import them. Unique file names should therefore be used. One solution is to use a running number series for file names, e.g. A date and time format “DDTTMMSS”, for Date, Hour, Minute, Second”, where theoretically, there will be one full month before the ERP system can possibly overwrite the file, but by this time, and usually after less than a minute, the file will have been imported by CONSIGNOR.
6. Placement of ASCII files:
A folder, which ConsignorServer Service has full control rights to, should be created on the network, for example ...\\CONSIGNORServer\EDISOFT\IMPORT. Both the ERP system and ConsignorServer service should have full control rights to this shared folder.
7. What needs to be done before installation of CONSIGNOR?
As mentioned previously, the ERP system needs to be set up so that it generates a file to CONSIGNOR’s import folder on the network (see appendix 1). Once it is able to save a file to this location, and once you are sure that the file is in the correct format for your purposes, and according to the requirements of all of the carriers that you wish to use in CONSIGNOR, send us a copy of a test file, along with a description of all of the field contents to [email protected]. It is important that we receive both a test file and a description of the test file fields so that we know which fields contain what value. Once we have approved the test file, and have
tested that it can be used with your required carrier and infrastructural setup, will it be possible for us to set up CONSIGNOR’s import module. This will be done without affecting your production, apart from a very short restart of the CONSIGNOR server service. Import does not need to be set up on the day of installation of CONSIGNOR, as this can be set up at a later date, but it usual for EDI-Soft to install an import module, should mention be made of using CONSIGNOR’s import capabilities.
You are always welcome to call or e-mail us with any queries you may have. We have a well grounded understanding of universal ERP systems, and will gladly discuss the deeper aspects of technical integration with you.
With Kind Regards EDI-Soft Norge AS Tel. 23 24 94 80 [email protected]
Appendix 1 – Scenario for automatic label printing
In this scenario, we illustrate how CONSIGNOR imports data and we also familiarise you and/or your EDB supplier with an example of CONSIGNOR-ERP integration.
Case: A company called EDI-Soft Norge AS sends shipments with Posten Norge. They have previously hand-written their labels as well as any other required accompanying papers. They now wish to
centralise the printing of all documents and labels through CONSIGNOR, and also make use of EDI-data. At EDI-Soft Norge AS, orders are processed using the following procedure:-
A telephone order is called in from a customer, and an order is created for the customer in the ERP system. When a warehouse staff member locates the required product, it is packed in a box and a message is given to the sales department that the package is ready and that an invoice may now be written out to the customer.
Task: After an order is processed in the ERP system, an automatic label is to be printed with all the necessary shipping information. This happens as follows:- The Warehouse staff member decides how many packages/parcels/containers/boxes need to be sent, as well as which carrier sending method is to be used, as well as any other requirements, for example shipment weight. Once the order is completed with this information in the ERP system, this information is sent to CONSIGNOR.
The comma-seperated file could look like this:-
"10101010","86701000"," The Super Fish Restaurant ","Spireaveien 6","0580",”NO”,"Oslo","Svend Jørgensen"," Package must not be left in the sun","1","867,00","10"
10101010 = Order number
86761000 = Customer Number
The Super Fish Restaurant = Receiver Name
Spireaveien 6 = Receiver Addresse
0580 = Receiver postcode
Oslo = Receiver city
NO = Country code for Norway. Can also be a 3-digit ISO code, or another alias if required
Svend Jørgensen = Receiver Reference
Package must not be left in the sun = Message on label
1 = Amount of packages
867,00 = This is package send with COD of NOK 867,00
10
= Carrier code ”10” which means in this case that it is a Posten Norge Bedriftspakke
dør-dør.
The above is merely an example. CONSIGNOR can import a large amount of different fields, in different orders which may vary from one CONSIGNOR customer to another. It is however, important that the
information is always given in the same fields every time the ERP generates a file. (If field order changes, the fields will no longer be mapped with the correct values and labels may not print) This example contains a simple import file setup, but it may be more complex in reality. Converse to the above task, it could also be required that only the delivery address be imported into CONSIGNOR, whilst shipping/delivery information is manually typed in, such as number of parcels, and product choice. This could be advantageous in a situation where only the warehouse staff will know the number of required boxes to send the shipment in, and the weight of the shipments. Thereafter they can manually print the label in CONSIGNOR.
Further data handling is executed within CONSIGNOR’s own database. Information on the label regarding carrier, product, services, and receiver is sent to the carrier in an EDI file. The physical label, together with this EDI information, ensures that the shipment can be delivered more effectively.
Appendix 2 – Recommendation for Carrier Codes in import files
The CarrierCode field in the import file concerns the method (Carrier + Product + services) that will be used to send the shipment from A to B.
These CarrierCodes are completely your choice. Below are examples of Carrier Codes
Carrier Code description Code sent from ERP system
Posten Bedriftspakke dør-dør 10
Posten Servicepakke 11
EDI-Soft Norge AS | Spireaveien 6 | 0580 Oslo www.edi-soft.no | [email protected] | tlf. 23249480
Appendix 3 – Export of data from CONSIGNOR to ERP System
CONSIGNOR can export data back to the ERP system when a label is printed. Either one large file or small single files per shipment can be exported by CONSIGNOR. These export files should be saved to a location where your ERP system can import them. CONSIGNOR can also send these files via FTP.
Files are saved once Export has been activated and configured, and exporting of files occurs seamlessly when labels are printed with no user-interaction.
The setting up of the export function in CONSIGNOR is done under the menu item SETUP, but given CONSIGNOR’s complexity, it’s a good idea to contact EDI-Soft to discuss your export requirements, and to hear EDI-Soft’s advice on the best installation location for this export module within your CONSIGNOR setup.
The Export module looks like this:- Folder/Filename Tab
Export is activated here
Path where files are saved
Export file is saved either when a label is printed, or when EDI files are transferred to the carrier
Explorer option to browse and select to browse and select the Export folder. (Should be created in advance)
It is possible to export to the same file every time. The file becomes larger as information is continually
appended to it in the order that it is saved to the file.
If this file is either deleted or moved, a new file is created with the next export from CONSIGNOR. In the field to the right, you can type in the required export file name.
Required file type .txt, .inh, .csv etc.
It is possible to save export data to a new file or to the same file with each label printed. If saving to a new file, you can choose either a unique filename or a consecutive number allocated by CONSIGNOR or your own order number as a file name.
Layout Tab Text separator to be used between export values i.e.: Comma, Semi-colon etc. It is possible to select a fixed field length instead if a character separator. The field length is defined under the Setup Fields options
The Setup Fields option allows you to select which data is to be saved to the export file. The screen dump on the next pages is a small excerpt of some of the options. It is here where field length may be defined should you require a fixed field length export format.
Select the file layout: One line per shipment is one line regardless of how many packages are in the shipment. One line per package is just exactly that. 3 packs = 3 lines One line per order means that CONSIGNOR checks how many packages are sent to a receiver and creates one line for all orders sent.
Not yet available It is possible to have a start and end character saved in every field, e.g. ””.
When ”Setup Fields” is selected, you can select the same field values which exist in CONSIGNOR’s import module. NOTE: Ordering must start with 0, 1, 2, 3 as an order for exported field data.
Units Tab
It is possible to change between Kilograms, grams and tons
Decimal separator, e.g. 100,00 or 0,1. This is seldom used, but it is nevertheless a possibility. It is possible to change between cubic millimeters, cubic centimeters, cubic decimeters and cubic meters. It is possible to change between millimeters, centimeters, decimeters and meters.
Transmission Tab
You are welcome to contact us should you have any questions arising from this document.
EDI-Soft Norge AS Tlf. 23 24 94 80 [email protected] Activate export via FTP Name or IP address of destination server FTP port to use, usually 21. Specify a folder on the FTP server into which, export files are to be saved, if this is a requirement. Check, if authentication is required FTP Username FTP Password Test the FTP connection