The specific package types that you use (including those for hazardous goods) must first be defined in Carrier Connect. The descriptions of your package types are always specific to each customer. That’s why it’s necessary for you to define your own package types in your system.
Entering package types manually
Proceed as follows:
- You must have the role of I_CAI_EDITMASTERFILEDATA.
- We recommend always assigning the package type property. In many scenarios such as with DHL Express or for ocean freight, the property is used to validate services, weights, and dimensions.
- With many carriers, you’ll need to convert your package types (and any hazardous goods package types) to the carrier’s package type codes so that the correct data is transmitted in the EDI message to the carrier. For information on how to convert your package types, see: Converting package types.
- Any routine changes or additions you make to the master data in your host system need to be synced to Carrier Connect. One example of this is when you use new or different package types in your host system.
Importing package types as a CSV file
AEB can import your package types into Carrier Connect using a CSV file that you provide.
CSV file format specifications:
- Use the ISO-8859-1 character set or the Windows default character set CP1252.
- Use the semicolon (“;”) as the separator.
- End all records (rows) with CRLF.
- Ensure the CSV field formats match those in the table below.
Field formats for importing package types
The following describes the mandatory field formats. Please refer to the table below for details.
Field no. (column)
Functionally required field
The code for your organization’s package type (for example: “KT”)
Unit of measure
Possible values: cm, dm, ft, in, km, m, mi, mm, nm, µm
Package type icon
Possible values: TYPESTD (standard), TYPCON (container), TYPEENV (envelope), TYPEEP (euro pallet), TYPEINDP (industry pallet), TYPENONRETP (non-returnable), TYPESEMFP (semi-pallet)
Freely selectable: e.g., Karton
Freely selectable: e.g., Carton
Explanations of field formats:
- Functionally required field: An “X” indicates a functionally required field.
- Field format: “an..” indicates an alphanumeric field format. “..” means that up to X characters may be transmitted. The entry “an.. 10” therefore indicates an alphanumeric field of up to 10 characters.