Grain Trader has the capability to import load data from plain text files sourced from various bulk handlers, or another Grain Trader database. Each bulk handler uses their own system and codes for setting out the data within the text file, and these will be different again to the contents of the file that can be exported from another Grain Trader database. Defined Format means that CDA Software supplies you with a configuration file that is specific to one type of file containing load data. For example the contents and layout of a Graincorp Payrun file will be different to a Graincorp Acquistions file or a Viterra Acquisitions file, so each file type requires a different format definition file. By separating the format definitions from the program code we can use a generic procedure to import the load data, making the whole process easier because you only have to learn one way of doing things. It also means that introducing an additional bulk handler format may be able to be done as easily as by downloading the tiny definition file and placing it in the same folder as the Grain Trader program file, rather than changing the program itself.

CDA Software will continue to provide the Format Definition files for the most common bulk handler formats at no additional charge to clients with current Software Subscriptions. For other handlers or purposes, at the request of a client we may be able to produce definition files, at the client's cost, provided the client can arrange to supply us with documentation about the new format.

You need to do some preparatory work in Grain Trader before being able to successfully import load data. Select the Setting Up Grain Trader For Import link below to learn more about what you need to do.

Why would you want to import load data from another Grain Trader database?

The most common reason is that the client operates two entities: a trading entity and a transport entity. When a load in the trading entity uses the transport entity as the carrier, this creates a Supplier transaction in the trading entity database in the usual and familiar way. Using the Transport Export functions in the trading database, processing the load also creates a record in a defined format file that can be imported into the transport entity database, where it is used to create a load with the trading entity as the Buyer. In this way one load creates both a Supplier transaction in the trading entity database and a Buyer transaction in the transport entity database, without any redundant data entry.

If you want to learn more about how to set up both the exporting and importing databases in Grain Trader prior to importing the file select the Setting Up Grain Trader For Transport Export link, otherwise you can ignore that section.

If you just want to learn how to actually import the load data from either a bulk handler file or a Grain Trader export file, select the Importing The File link below.