Recommended: System Errors? Click here to Fix your PC »
Microsoft Great Plains, former Great Plains Software Dynamics/eEnterprise should beconsidered as ERP platform for midsize and large business, so SQL data maintenanceand repair is normal IT procedure, this is why table structure and MRP architectureshould be familiar to SQL DB administrator. We will begin with architecture andtable name coding and then go down to typical data repair Setup Tables. These tables have 4 prefix. IV40100  this is Inventory ControlModule setup table. Setup tables may have only one record, if this is module setupor multiple records, if this is something like Inventory Class setup (vendor,customer class setup to give additional examples) History Tables. These tables have 3 prefix. SOP30200  this is Sale TransactionHeader history table. When you post transactions  they go to open (optional phase)and history Open Tables. These tables have 2 prefix. GL20000  this table stores all youropen year posted GL transactions. For some of the module open stage is skipped(Sales Order Processing  here transactions when posted go to the history tablesdirectly) Work Tables. These tables have 1 prefix. These tables are present in eachmodule: GL, Inventory Control, Invoicing, Receivable Management, Payroll, PayableManagement, Purchase Order Processing, Bill of Material. Great Plains has batchposting module  this feature allows you to save and store work (or unposted)transactions in the batch. SOP10100  this is Sales Transaction Header Work table Master Tables. These tables have 0 prefix. We will give you several examples:IV00101  inventory item master stores all your inventory items, RM00101  customermaster table, IV00200  vendor master table, GL00100  General Ledger account mastertable Table repair technique. When you consider to repair one of GP tables, you dobackup of the table, execute this SQL statement:
Select * into IV00101_Backup from IV00101
Then do you data repair. If you need to roll back to old backed up version of thetable, do this:1. Clean your original table: delete IV001012. Restore it from backup: alter table IV00101_Backup drop column DEX_ROW_ID insertinto IV00101 select * from IV00101_Backup
Some additional hints. Microsoft Great Plains is Dexterity application. Dexinternal logic adds autoid column DEX_ROW_ID, so you have to drop it prior torestoring the table from backup
Andrew Karasev, Alba Spectrum Group, http://www.albaspectrum.comhe lp@albaspectrum.com 1-866-528-0577, 1-630-961-5918, serving GP customers in USAand Canada nationwide via remote support: California, Alberta, Ontario, Quebec,Minnesota, New York, Virginia, Washington, New Jersey, Florida, Georgia, California,Nebraska, Utah, Nevada, Iowa, Wyoming. Local service is available in Houston /Dallas Texas as well as in Chicago / Springfield, Illinois: Naperville, Aurora,Joliet, Plainfield, Lisle, Downers Grove, Wheaton, Warrenville, Batavia, St,Charles, Elgin, Rockford, Morris, Ottawa, Montgomery, Romeoville, University Park,Hinsdale, Lincoln Woods, De Kalb, LaSalle, Seneca.
