Before you can import loads from either a Bulk Handler or Grain Trader Transport defined format file you need to prepare your Grain Trader database so that the data for each load can be correctly matched to its Grain Trader equivalent. This data matching occurs in four areas:

• Suppliers (for Bulk Handler files) or Customer (for GT Transport)
• Commodities
• Storages
• Metrics

If you will be importing load data from Bulk Handler defined format files you need to ensure that the growers as identified in the Bulk Handler file can be matched to those in your Grain Trader database using either their NGR Number, or another number that is unique to each supplier that suits your purposes (eg a Bulk Handler-specific supplier number). These are entered on the Supplier window, Other tab, as shown below:

If you will be importing load transport data exported from a Grain Trader trader entity database into a Grain Trader transport entity database you need to create a Customer in the Grain Trader Transport database for the Trading entity. In this way when the Trading entity uses the Transport entity as the carrier for a load, the details will be exported from the Trading database and when imported into the Transport entity database, a load will be created that charges the Trading entity for the freight cost.

In the Transport (importing) database just create a Customer in the normal way, recording the XRef code used for the next step: Setting Up Grain Trader For Transport Export.

Commodities are matched using the Cross Ref code entered on the Commodity window:

For Bulk Handler imports, it is assumed that all bulk handlers use the same code to identify the same commodity and grade eg APW for APW Wheat. You may need to create a commodity for each Bulk Handler if required.

For GT Transport import you need to create a Transport commodity and note the Cross Ref code for use in the next step: Setting Up Grain Trader For Transport Export.

For Bulk Handler import, each Handler will have their own codes for the storage sites used. Our recommendation is that you create a storage for each Commodity and Bulk Handler you use; this will make it easier for you to keep track of who owns what and where over time. You need to obtain the Storage cross-reference codes used by the Bulk Handler you are dealing with from them. If later you no longer wish to use a combination you can just make that storage Inactive and it won't be available for selection from drop-down lists etc.

For GT Import, you need to create a default storage site to be used just to make the Load record complete. Our recommendation is to use either the word “Default” or your town name for both the Site name and cross-reference code, but it's entirely up to you. Again, note the value you enter for use in the next step: Setting Up Grain Trader For Transport Export.

Enter the cross-reference code(s) in the XRef column of the grid on the Storages tab of the Commodity window, as shown below:

Even if you're not using metrics to classify the grade or make bonuses or deductions based on their values, you may wish to record them for potential use in the future. Grain Trader recalculates a weighted average of up to the first five metrics for the commodity in each storage on every incoming load, so you can tell at a glance the overall storage averages.

Because there are different import file types available from some Bulk Handlers (notably GrainCorp), but all the formats from one handler can use the same cross-reference terms, Grain Trader allows you to define the terms only once for each Bulk Handler and Commodity (however the system is flexible enough to allow for a different list of terms should this be needed in the future). To configure these you first need to give each Bulk Handler schedule of terms a name of your own choosing, then allocate the file format(s) they provide to their schedule. Select the Utility | Import | Manage Defined Import Formats menu to display the Manage Defined Import Formats window:

The names you give to Schedules are used as the column headings on the Bonuses & Deductions grid on the Commodity window. The order of the Schedule names on the Manage Defined Import Formats window top-to-bottom corresponds to the order left-to-right on the Commodity window.

To add a new Schedule, click New and enter the name you want to use in the grid, then click Apply.

You can also delete a Schedule if it is no longer required. Deleting a Schedule removes the column with that heading from all Commodity windows, and all its XRef values from the database. Existing loads are not affected in any way, but you will not be able to import additional loads using that Bulk Handler Schedule.

You then need to associate the import File Format(s) to its Schedule as appropriate. CDA Software provides a file for each type of Bulk Handler import file, whose contents define how Grain Trader is to interpret the import file. These definition files have an extension of .idf and reside in the same folder as your Grain Trader program, usually

C:\Program Files\CDA Software\CDA Grain Trader

on 32-bit systems or

C:\Program Files (x86)\CDA Software\CDA Grain Trader

on 64-bit systems. Grain Trader automatically finds these files if they exist on your computer (or terminal server) and stores information about them in your database. If the file is later deleted from disk, the stored data is not automatically removed, but the checkbox in the Found column of the Formats grid will be unticked, and you will not be able to import files of this type from the workstation you are using. Definition files for all currently-supported formats are installed when you install Grain Trader or a patch upgrade. You can download additional or missing formats from the CDA Software website if needed.

To associate an import File Format with a Bulk Handler Schedule, click in the Metrics XRef Schedule column cell of the Formats grid for the Format you want to associate and select the Schedule from the drop-down list, then click Apply.

You can also delete a format definition (.idf) file from your disk, and all its associated data from your database, by clicking Delete. Existing loads are not affected in any way, but you will not be able to import additional loads using that file format. Note however that if the format is still supported by Grain Trader, the next time you install a patch update the format definition file will be re-installed, automatically found and added again.

When you have finished configuring the Bulk Handler import formats you can enter the Bulk Handler's cross-reference codes for each metric on the Commodity window. Scroll the Bonuses & Deductions grid across to the right to see the column(s) for each Schedule you have defined, and enter the values in the cells for each Bulk Handler and Metric as required.