Differences

This shows you the differences between two versions of the page.

--- gt3:loads:import:defined:gtdatabase [11/05/2012 06:00]
Ian Davidson [Grain Trader Database]
+++ gt3:loads:import:defined:gtdatabase [20/08/2018 04:24] (current)
@@ Line 1: / Line 1: @@
 {{indexmenu_n>1}}
-====== Grain Trader Database ======
+====== Setting Up Grain Trader For Transport Export ======
+{{indexmenu_n>2}}
-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. Using the **Transport Export** functions in the trading database, processing the load also creates a transaction entry in a defined format file that can be imported into the transport entity database, where it creates a load with the trading entity as the Buyer. In this way one load creates transactions separately in both the trading and transport entity databases, without any redundant data entry.
+Before you can transfer load data from your Grain Trader Trading database into your Grain Trader Transport database you need to configure both databases, starting with the Transport (importing) database, as described in [[gt3:loads:import:defined:gtimportsetup]]. After you have completed that step you should have made a note of the following details:
+  - The Customer XRef code in the Transport database assigned to the Trading entity customer;
+  - The Commodity XRef code in the Transport database for the transport commodity, and;
+  - The Storage XRef code in the Transport database for the default storage for the transport commodity.
+You can then configure the Trading (exporting) database to create the transfer file.
+Select the **Utility | Global Options** menu,
+{{ :gt3:loads:import:globaloptionsmenu.png?nolink |}}
+Then select the Loads - Transport Export branch from the tree menu.
+{{ :gt3:loads:import:transportexport.png?nolink& |}}
+Check the //Use Transport Export Functions// checkbox, select the Transport supplier from the //Select Carrier// drop-down list and enter the details from the Trading database you have noted as described above into their respective boxes, as shown, then click OK.
+From that point onwards, any load that uses the selected carrier in the Trading database will, when processed, generate a record in the import file.
+<note important>**Note:** It is not possible to generate the transfer data retrospectively.</note>
-This documentation outlines the procedures necessary to implement this Transport Export functionality, in both the trading and transport entity databases.