Cargo-IMP

You need an additional licence for this parser. If you are interested, please contact our support or sales staff.

Note: The preparser CargoImpToEDIFormat is also available, which generates an EDIFACT message from a Cargo-IMP message.

(1) If this checkbox is set, the input fields are checked against their format templates during parsing. If a value violates the format template of the field or exceeds the field length, an error is created. If an error occurs, the profile job will not be aborted immediately in phase 2, but at the end of phase 2 or after 50 errors. Attention: The use of format checking puts a strain on performance and should only be used if absolutely necessary.

(2) Specifies whether to check the number of repetitions (of fields and nodes) in the source structure.

(3) Trims all field values. Example: a;" b " ;c becomes a;b;c

The configuration of this parser is described on the following pages.

To use the Lobster_data Cargo-IMP parser, you always need an XML configuration file cargo-imp_rules.xml in folder ./etc/admin/datawizard. This file tells the parser how to deal with all the special cases you will find in almost every single Cargo-IMP format definition. Per default, you will already find many specified formats, but there are a lot of older formats out there that you might have to specify yourself. If you do not want to spend time with this, you can, of course, always call our sales department and we can talk about doing that for you in a project.

• Cargo-IMP Message Specifications (PDF document)

• Structure of Cargo-IMP Data Files

• Structure of the Lobster_data Cargo-IMP XML Configuration File

• Splitting of Tokens

• Repeating Structures

• Special Handling Attribute continuousLineHandling="true"

• Special Handling Attribute useMC="true"

• Dealing with Dynamic Length Fields and Optional or Conditional Fields and Subsegments

• Manual Reload of Parser Rules for Testing