OneFlo is capable of accepting an XML EDI file that must contain the following information:
- Shipper
- Carrier
- Consignment
- Details (Consignment level item count, weight, volume)
- Sender
- Receiver
- Package details (individual item dims, weight, volume, DG information)
Field Name | Type | Len | Mandatory | Comment |
---|
Generated | Text | 30 | |
|
Application | Text | 30 | | Name of your Application |
Version | Text | 20 |
|
|
DistributorId | Numeric | 10 | | EFM Distributor |
Shipper > | AddressType | 1 |
|
|
Id | Numeric |
| | Must be an account number provided by efm |
Name | Text | 30 |
|
|
Address1 | Text | 30 |
|
|
Address2 | Text | 30 |
|
|
Locality | Text | 30 |
|
|
State | Text | 3 |
|
|
Postcode | Text | 4 |
|
|
Carrier > Account | Numeric |
| | Must be an account number provided by efm |
Consignment > | Consignment | * | | Multiple |
Account | Numeric |
| | Must be an account number provided by efm |
Connote | Text | 20 | |
|
Consigned | DateTime |
| | Date/Time consignment was created. |
Released | DateTime |
| | Date/Time consignment was released/manifested/finalised. |
SRT | Text | 1 | | S = sender pays, R = receiver pays, T = third party pays |
CarrierAccount | Text | 20 |
| If SRT = {R | T}, this contains the carrier account of charged entity. |
Service | Text | 20 | | Carrier Service Provided by efm |
ATL | Bool |
|
| Authority to Leave Flag { True | False } |
Reference | Text | 20 | | Reference number. Allows multiple instances. |
Sender > | AddressType | 30 | |
|
Name | Text | 30 | |
|
Address1 | Text | 30 | |
|
Address2 | Text | 30 |
|
|
Locality | Text | 30 | |
|
State | Text | 3 | |
|
Postcode | Text | 4 | |
|
Contact | Text | 20 |
|
|
Phone | Text | 15 |
|
|
Email | Text | 50 |
|
|
Receiver > | AddressType | 30 | |
|
Name | Text | 30 | |
|
Address1 | Text | 30 | |
|
Address2 | Text | 30 |
|
|
Locality | Text | 30 | |
|
State | Text | 3 | |
|
Postcode | Text | 4 | |
|
Contact | Text | 20 |
|
|
Phone | Text | 15 |
|
|
Email | Text | 50 |
|
|
Items | Numeric |
| | Total Number of SUs for the consignment |
Weight | Numeric |
| | Weight in Kgs. Up to 2 decimal places. |
Cubage | Numeric |
| | Cubic metres (m3). Up to 3 decimal places. |
Description | Text | 40 |
|
|
Special Instructions | Text | 60 |
|
|
Delivery Instructions | Text | 60 |
|
|
UserField1 | Text | 50 |
|
|
UserField2 | Text | 50 |
|
|
UserField3 | Text | 50 |
|
|
UserField4 | Text | 50 |
|
|
UserField5 | Text | 50 |
|
|
Package > | PackageType | * | | Defines the Shipping Unit |
Type | Text | 20 | |
|
Number | Numeric |
| | The index (starting 1) or otherwise known as ordinal integer. e.g. if there are 3 packages, this will enumerate package 1, package 2, and package 3 |
Reference | Text | 20 |
|
|
Description | Text | 40 |
|
|
Weight | Numeric |
| | Weight of SU in Kgs. Up to 2 decimal places. |
Cubic | Numeric |
| | Cubic metres (m3). Up to 3 decimal places. |
Length | Numeric |
| | Length in centimetres (cm). Up to 2 decimal places. |
Width | Numeric |
| | Length in centimetres (cm). Up to 2 decimal places. |
Height | Numeric |
| | Length in centimetres (cm). Up to 2 decimal places. |
Barcode | Text | 50 | | Scannable barcode (Unique per shipping unit!) as printed on label |
DG > | DGType | * |
|
|
UN | Numeric | 4 | | UN Number for the Dangerous Goods |
Class | Text | 10 | | Classification of DG |
SubRisk | Text | 20 |
| Subsidiary hazard code |
Group | Text | 10 |
| Packing group (e.g. I , II, III ) or leave blank |
ProperShippingName | Text | 100 | | Identifiable DG name as specified in the code |
CommonName | Text | 100 | | Nickname for the DG |
Qty | Numeric |
| | Amount of DGs within the receptacle in the shipment (e.g. If there are 4 aerosol cans in this shipping unit, put 4 in this field) |
AggQty | Numeric |
| | Amount of DG in Unit (e.g if there are 4 aerosol cans that are 300 ml each, the value placed in this field must be 300 ml x 4 cans = 1.2 L) |
Units | Text | 10 | | Unit used in the AggQty (kg or L) |
Receptacle | Text | 50 | | Container for the DG (e.g. can, tank, box, bottle) |
Code Block |
---|
language | xml |
---|
theme | RDark |
---|
title | XML |
---|
linenumbers | true |
---|
|
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<EDI ManifestId="1" xmlns="http://www.opensys.com.au/schema/SCaRRS/1.1">
<Generated>
<Application>3PL_APPLICATION</Application> <!-- Place name of Application i.e. <3PL_SYSTEM> -->
<Version>VERSION</Version> <!-- Please input version of Application -->
<Created>MANIFESTDATE</Created> <!-- Include date of Manifest. Not mandatory -->
<DistributorId>101605</DistributorId> <!-- efm Logistics Services -->
</Generated>
<Shipper>
<Id>XXXXXX</Id> <!-- <Customer> ACCOUNT 6 digit number, will be provided-->
<Company>CUSTOMER NAME</Company> <!-- <Customer> trading name-->
<AddressLine1>ADDRESS LINE 1</AddressLine1>
<AddressLine2>ADDRESS LINE 2</AddressLine2>
<Locality>LOCALITY</Locality>
<State>STATE</State>
<Postcode>POSTCODE</Postcode>
<CountryCode>AU</CountryCode> <!-- 2 Character Country Code-->
<Country>AUSTRALIA</Country>
<Contact />
<Phone />
<Fax />
<Email />
</Shipper>
<Carrier>
<Id>Couriers Please Pty Ltd</Id>
<Account>102959</Account> <!-- <Carrier> 6 digit ID, will be provided by efm-->
</Carrier>
<Consignment>
<Account>XXXXXX</Account> <!-- <Customer> ACCOUNT 6 digit number, will be provided by efm-->
<ContainerID />
<Connote>CON00000000001</Connote>
<Consigned>2018-06-18T00:00:00</Consigned> <!-- Date of Consignment -->
<Released>2018-06-18T00:00:00</Released> <!-- Date of Release -->
<DeliverOn />
<Service>CPPCL</Service> <!-- Carrier Service – Must be the Service code provided by efm -->
<CarrierAccount /> <!-- Carrier Charge account (when third party pays) -->
<Reference />
<SRT>S</SRT> <!-- S = sender pays, R = receiver pays, T = third party pays -->
<Sender>
<Company>Sender Name</Company>
<AddressLine>SENDER ADDRESS LINE 1</AddressLine>
<AddressLine />
<Locality>LOCALITY</Locality>
<State>STATE</State>
<Postcode>POSTCODE</Postcode>
<CountryCode>AU</CountryCode> <!-- 2 Character Country Code-->
<Country>AUSTRALIA</Country>
<Contact />
<Phone />
<Fax />
<Email />
</Sender>
<Receiver>
<Company>Receiver Name</Company>
<AddressLine>RECEIVER ADDRESS LINE 1</AddressLine>
<AddressLine />
<Locality>LOCALITY</Locality>
<State>STATE</State>
<Postcode>POSTCODE</Postcode>
<CountryCode>AU</CountryCode> <!-- 2 Character Country Code-->
<Country>AUSTRALIA</Country>
<Contact />
<Phone />
<Fax />
<Email />
</Receiver>
<Items>2</Items>
<Weight>7</Weight>
<Instructions />
<SpecialInstructions />
<Description />
<GoodsValue>0.0000</GoodsValue>
<InsuranceClass />
<DutyTaxesPaid>False</DutyTaxesPaid>
<CustomsClearanceRequired>False</CustomsClearanceRequired>
<UserField1 />
<UserField2 />
<UserField3 />
<UserField4 />
<UserField5 />
<Package Type="ITEM"> <!-- Your Shipping Unit type e.g. CARTON, PALLET, SKID, etc -->
<Id>XXXXXXXXXXXXXXX1</Id>
<Number>1</Number> <!-- Ordinal number in reference to each consignment -->
<Reference /> <!-- Order reference for this shipping item -->
<Description>CARTON</Description>
<Weight>4.13</Weight>
<Cubic>.047</Cubic>
<Length>10</Length>
<Width>10</Width>
<Height>10</Height>
<Barcode>XXXXXXXXXXXXXXX1</Barcode> <!-- must be the actual barcode / sscc that is scannable on the label -->
</Package>
<Package Type="ITEM"> <!-- Your Shipping Unit type e.g. CARTON, PALLET, SKID, etc -->
<Id>XXXXXXXXXXXXXXX2</Id>
<Number>2</Number>
<Reference />
<Description>CARTON</Description>
<Weight>4.13</Weight>
<Cubic>.047</Cubic>
<Length>10</Length>
<Width>10</Width>
<Height>10</Height>
<Barcode>XXXXXXXXXXXXXXX2</Barcode> <!-- must be the actual barcode / sscc that is scannable on the label -->
<DG> <!-- Must follow ADG Code https://www.ntc.gov.au/heavy-vehicles/safety/australian-dangerous-goods-code/ -->
<UN>3090</UN>
<Class>9</Class>
<SubRisk>N/A</SubRisk>
<Group></Group>
<ProperShippingName>LITHIUM METAL BATTERIES CONTAINED IN EQUIPMENT</ProperShippingName>
<CommonName>LITHIUM BATTERIES</CommonName>
<Qty>1</Qty>
<AggQty>1</AggQty>
<Units>kg</Units>
<Receptacle>BOX</Receptacle>
</DG>
</Package>
</Consignment>
<Consignment>
...
</Consignment>
</EDI> |
We can customise other forms of EDI file but this is subject to cost and business approval. OneFlo has a selection of recognised EDI formats. please contact your IT Solutions consultant if your format is already recognised.
For ideas in improving the EDI data, please see EDI CCI - Data Efficacy.