null

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

Overview

OneFlo is capable of accepting an XML EDI file that must contain the following information:

  1. Shipper
  2. Carrier
  3. Consignment
    1. Details (Consignment level item count, weight, volume)
    2. Sender
    3. Receiver
    4. Package details (individual item dims, weight, volume, DG information)

Data Specifications

Field NameTypeLenMandatoryComment
GeneratedText30
Y

ApplicationText30
Y
Name of your Application
VersionText20

DistributorIdNumeric10YEFM Distributor
Shipper >AddressType 1

   IdNumeric
YMust be an account number provided by efm
   NameText30

   Address1Text30

   Address2Text30

   LocalityText30

   StateText3

   PostcodeText4

Carrier > AccountNumeric
YMust be an account number provided by efm
Consignment >Consignment*
Y
Multiple
   AccountNumeric
YMust be an account number provided by efm
   ConnoteText20YTracking Number (used by carrier to provide tracking events to efm)
   ConsignedDateTime
YDate/Time consignment was created.
   ReleasedDateTime
YDate/Time consignment was released/manifested/finalised.
   SRTText1Y

Freight movement:

S = Outbound, 

R = Returns, 

T = Transfer Movement (3rd party)

   CarrierAccountText20
If the consignment involves a third-party or receiver paying, this must contain the carrier account of charged entity.
This must adhere to the payor's charge entity registered on the prescribed carrier.
   ServiceText20YCarrier Service Provided by efm
   ATLBool

Authority to Leave Flag { True | False }
   ReferenceText20Y

Reference number. Allows multiple instances.

Consolidated consignments, for example, may contain multiple references in the form:
<Reference>PO0001</Reference>
<Reference>PO0002</Reference>

   Sender >AddressType30
Y

      NameText30
Y

      Address1Text30
Y

      Address2Text30

      LocalityText30
Y

      StateText3
Y

      PostcodeText4
Y

      ContactText20

      PhoneText15

      EmailText50

   Receiver >AddressType30
Y

    NameText30
Y

      Address1Text30
Y

      Address2Text30

      LocalityText30
Y

      StateText3
Y

      PostcodeText4
Y

      ContactText20

      PhoneText15

      EmailText50

   ItemsNumeric
Y
Total Number of SUs for the consignment
   WeightNumeric
Y
Weight in Kgs. Up to 2 decimal places.
   CubageNumeric
Y
Cubic metres (m3). Up to 3 decimal places.
   DescriptionText40

   Special InstructionsText60

   Delivery InstructionsText60

   UserField1Text50

   UserField2Text50

   UserField3Text50

   UserField4Text50

   UserField5Text50

   Package >PackageType*YDefines the Shipping Unit
      TypeText20Y

Warehouse specific code to determine a package type (different from PackagingType defined later)

This could be any code to identify within the warehouse (i.e. SMLCTN for small cartons, or SAT1KG for a 1 kg Satchel).

      NumberNumeric
Y

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

      ReferenceText20
Recommended for consolidated consignments.
If you're consignment contains multiple references, it's best to highlighed individual items associated to which order reference.
      DescriptionText40

      WeightNumeric
YWeight of SU in Kgs. Up to 2 decimal places.
      CubicNumeric
YCubic metres (m3). Up to 3 decimal places.
      LengthNumeric
YLength in centimetres (cm). Up to 2 decimal places.
      WidthNumeric
YLength in centimetres (cm). Up to 2 decimal places.
      HeightNumeric
YLength in centimetres (cm). Up to 2 decimal places.
      PackTypeText
YCode for the OneFlo defined packaging type: See Shipping Items - Packaging Type
      BarcodeText50YScannable barcode (Unique per shipping unit!) as printed on label
      DG >DGType*

         UNNumeric4YUN Number for the Dangerous Goods
         ClassText10YClassification of DG
         SubRiskText20
Subsidiary hazard code
         GroupText10
Packing group (e.g. I , II, III ) or leave blank
         ProperShippingNameText100YIdentifiable DG name as specified in the code
         CommonNameText100YNickname for the DG
         QtyNumeric
YAmount 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)
         AggQtyNumeric
YAmount 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)
         UnitsText10YUnit used in the AggQty (kg or L)
         ReceptacleText50YContainer for the DG (e.g. can, tank, box, bottle)

XML Structure

XML
<?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-->
    <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>PO001234</Reference>
    <SRT>S</SRT> <!-- Freight movement, see options above -->
    <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>
	<Cubic>.12</Cubic>
    <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>
      <PackType>CTN</PackType>  <!-- Must adhere to https://flipgroup.atlassian.net/wiki/spaces/OIUG/pages/961445944/Shipping+Items+-+Packaging+Type -->
      <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>
      <PackType>CTN</PackType> 
      <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>

Customisation

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.


Efficacy of the CCI File

For ideas in improving the CCI data, please see CCI - Data Efficacy.

  • No labels