Microsoft Dynamics Gp Table structure overview
Microsoft Great Plains, former Great Plains Software Dynamics/eEnterprise should be determined as Erp platform for midsize and large business, so Sql data maintenance and heal is normal It procedure, this is why table buildings and Mrp architecture should be familiar to Sql Db administrator. We will begin with architecture and table name coding and then go down to typical data repair
Microsoft Dynamics Gp Table structure overview
Microsoft Dynamics Gp Table structure overview
Microsoft Dynamics Gp Table structure overview
Microsoft Dynamics Gp Table structure overview
o Setup Tables. These tables have 4 prefix. Iv40100 - this is catalogue operate Module setup table. Setup tables may have only one record, if this is module setup or complicated records, if this is something like catalogue Class setup (vendor, customer class setup to give supplementary examples)
o History Tables. These tables have 3 prefix. Sop30200 - this is Sale Transaction Header history table. When you post transactions - they go to open (optional phase) and history
o Open Tables. These tables have 2 prefix. Gl20000 - this table shop all your open year posted Gl transactions. For some of the module open stage is skipped (Sales Order Processing - here transactions when posted go to the history tables directly)
o Work Tables. These tables have 1 prefix. These tables are gift in each module: Gl, catalogue Control, Invoicing, Receivable Management, Payroll, Payable Management, purchase Order Processing, Bill of Material. Great Plains has batch posting module - this feature allows you to save and store work (or unposted) transactions in the batch. Sop10100 - this is Sales Transaction Header Work table
o Master Tables. These tables have 0 prefix. We will give you any examples: Iv00101 - catalogue item expert shop all your catalogue items, Rm00101 - customer expert table, Iv00200 - vendor expert table, Gl00100 - normal Ledger catalogue expert table
o Table heal technique. When you think to heal one of Gp tables, you do backup 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 the table, do this:
1. Clean your customary table: delete Iv00101
2. Restore it from backup: alter table Iv00101_Backup drop column Dex_Row_Id insert into Iv00101 make your mind up * from Iv00101_Backup
Some supplementary hints. Microsoft Great Plains is Dexterity application. Dex internal logic adds autoid column Dex_Row_Id, so you have to drop it prior to restoring the table from backup.
Microsoft Dynamics Gp Table structure overview
