It looks like Microsoft Great Plains is growing in popularity, partly because of the Microsoft muscles behind it. Now it caters to the full spectrum of horizontal and vertical market clientele. Small businesses use Small Business Manager (which is based on the same technology – Great Plains Dexterity Dictionary and Runtime), Great Plains Standard on MSDE is intended for small to medium-sized customers, and then Great Plains serves the rest of the market up to large enterprises. There are several reporting tools available and it is important to know which one to use for different types of reports.
If you’re a database administrator asked to import some data into Great Plains, or to fix or copy data from one company to another, read this and you’ll have pointers where to look further.
1. Microsoft Great Plains Table Structure – Start Great Plains and go to Tools->Resource Description->Tables. Find the table in the correct row. If you search for the customers – it should be RM00101 – customer master file.
2. DEX_ROW_ID. This is an identity column and every Great Plains table has it – this is due to Great Plains skill technology. This column is never used as a key field – so don’t try to join your tables on DEX_ROW_ID. In case you need to transfer the spreadsheet from one company to another, you should use these queries:
Select * in GL00100_BAK of TWO.dbo.GL00100
Modify the GL00100_BAK table and delete the DEX_ROW_ID column
insert into GL00100 * select from GL00100_BAK
Drop table GL00100_BAK
The queries above transfer GL00100 (Account Master Table) from TWO companies to your current company. Then you need to run Checklinks – see GP manual – to rebuild the rest of the account master related tables.
3. Don’t change the table – sometimes it seems nice if you just append a few extra columns to the table – like in IV00101 – Inventory Master File, why wouldn’t you just add a few extra descriptions? If you do this, the Great Plains Dexterity engine will not be able to read all of your items because DYNAMICS.DIC (main Great Plains dictionary file) contains an accurate description of each table and Dexterity uses it to read and write to each table
4. Feel free to create SQL views or stored processes. If you’re helping your in-house developers create Crystal Reports, good SQL Views are a real help to them. Let me give you an example, the view below shows working and historical SOP invoices – then Crystal can just use it
Create SOP_WORK_HIST view
Select SOPNUMBE, CUSTNMBR, CUSTNAME, DOCAMNT from SOP30200, where SOPTYPE=3 and VOIDSTTS=0
Select SOPNUMBE, CUSTNMBR, CUSTNAME, DOCAMNT from SOP10100, where SOPTYPE=3 and VOIDSTTS=0
The view above shows all working and historical non-canceled invoices (SOP type = 3 stays for invoice)
5. Some repair/unlock tips:
Running the above query against the DYNAMICS database will unlock the user who accidentally shut down the computer without logging out of Great Plains:
Delete ACTIVITY where USERID=’JOHN’
Next, the hanging batch is unlocked:
update SY00500 set BCHSTTUS=0 where BACHNUMB = ‘JULYINVOICES04’
Have fun asking! If you want us to do the work – give us a call 1-866-528-0577! firstname.lastname@example.org