This article describes how to use the Table Import tool to import data into Microsoft Dynamics GP and into Microsoft Business Solutions - Great Plains.
To use the Table Import feature to import data, follow these steps:
- Determine what data will be imported and which tables will be accessed. To do this, follow these steps:
- Use the Software Development Kit (SDK) Master document and the Transaction Work Flow document to determine what data will be imported and which tables will be accessed. Run the SDK.msi file from the Tools folder on the Microsoft Dynamics GP CD2 disc.
The SDK documents explain the tables and the fields that are involved in importing data into the Microsoft Dynamics GP modules. Additionally, the documents include a flow chart diagram for the Transaction Entry process in the appropriate module.
- Use the online table and field descriptions to view the table description and the field information for any table in the selected product. To do this, click Tools, click Resource Descriptions, and then click Tables.
- View the existing data in the "Fabrikam, Inc." sample company. To do this, create a custom report in Report Writer that lists all the fields in a table. Connect to a table through ODBC in Microsoft Access, in Microsoft Query, or in Microsoft Excel. Use SmartList to export specific data to Microsoft Excel. Or, use SQL Query Analyzer to select records from a specific table. Additionally, you can use the Select A Table window that opens when you access the Table Import Utility when a Microsoft Dynamics GP form is open. The Select A Table window shows the tables that are used for that window. You can also use the Show Required Fields option in Microsoft Dynamics GP.
- Use the following guidelines to determine both the field structures and the data types of the fields that are to be imported:Note Account Numbers are stored as a composite of each segment. When you import account numbers, each segment must be separated by a tab or by a comma so that the Table Import tool treats each segment as a separate field.
- Determine which fields are required for import. To do this, use the Software Development Transaction document and the Master Flow document.
Some required field information is also listed in the Table Descriptions window.
- Always test the import definitions in the Fabrikam, Inc. sample company before you run the import in the live company.
- Manipulate the data within the Fabrikam sample company. To do this, you can print reports, post transactions, run check links, and so on.
- Make a backup of the live company before you perform the import procedure.
- Review the required fields, and then check for duplicate records in the source file. A record is considered a duplicate if the key values are the same as the key values of another record that already exists in the system or in the source file. Duplicate records will not be imported.
- Define the import. Then, perform the import.
- After the import is finished, perform file maintenance on the tables that are imported into Microsoft Dynamics GP. Print any relevant setup lists or edit lists. Then, perform the necessary reconcile procedures.
Article ID: 856667 - Last Review: July 12, 2011 - Revision: 3.0
- Microsoft Dynamics GP 2010
- System Manager, when used with:
- Microsoft Dynamics GP 10.0
- Microsoft Dynamics GP 9.0
- Microsoft Business Solutions–Great Plains 8.0
- Microsoft Business Solutions–Great Plains 7.5
- Microsoft Great Plains Dynamics 7.0
- Microsoft Great Plains eEnterprise 7.0
- Great Plains Dynamics 6.0
- Great Plains eEnterprise 6.0
|kbhowto kbmbsmigrate KB856667|
Contact us for more help
Connect with Answer Desk for expert help.