Chronology: Great Plains Dynamics - Microsoft Great Plains - Microsoft Dynamics GP - Overview

In this small article, following the rules of article format we will give you chronology of current Microsoft Dynamics GP 9.0. ERP System usually has its life cycle and it should be considered as market newcomer, matured or phasing out MRP. The ERP life cycle is usually 15 years, however in the conditions of modern computer programming/software life cycle the life cycle could be reduced to 10 years (with the option of capital software redesign). We are not talking here about GPS Accounting - or also known as Great Plains DOS version - call us if you need help with DOS version.

o Graphical/DB platforms independent ERP. In the beginning of 1990th Great Plains Software pioneered with Great Plains Dynamics/Great Plains Dexterity. The idea behind was typical for those good old days - to protect ERP from OS battle: Mac/Windows/Solaris/Unix, plus database SQL battle: MS SQL Server/Sybase/Oracle/ingress/IBM DB2. Great Plains Dynamics/Dynamics C/S+/eEnterprise core was Great Plains Software Dexterity - IDE and programming language/shell, written on C programming language. In fact Great Plains Software switched C vendor to and proved the reliability of Dexterity in 1998.

o Acquisition. Microsoft decided to move into ERP arena at the end of 20th century and purchased Great Plains Software. At this moment Great Plains Software was owning also Solomon IV - its long time competitor. One year later Microsoft Great Plains Business Solutions (renamed into Microsoft Business Solutions) acquired Denmark based ERP software development company - Navision Software - as the result of this operation Microsoft was the owner of several MRP packages: Great Plains Dynamics/eEnterprise, Navision Attain, Navision Axapta, Solomon

o Microsoft Great Plains. Microsoft .Net platform was introduced and all Microsoft ERP applications were aimed to be rewritten in .Net/C#/VB - which was probably premature statement. Future development confirmed that software world is too complicated and software unification is not that simple

o Great Plains Dexterity Source Code Programming. DYNAMICS.DIC is the dexterity dictionary and if the MBS was in the source code subscription - it had DYNAMICS.DIC with sanscript Dexterity scripts and its developers could align their code with Great Plains Software/MBS. The program was closed for new VAR in 1999, so assuming you are Offshore Indian MBS software shop - your customization capabilities were limited. Plus if you are MBS Dynamics GP eCommerce ISV vendor - the source code programming is still the must for you, you should know how these tables are populated: GL00101, SOP30200, SOP30300, SOP10200, RM00101, PM00200.

o Microsoft Dynamics GP. In September 2005 Microsoft initiated with Microsoft Dynamics renaming project (who knows - maybe Microsoft Dynamics was associated with Great Plains Dynamics name)

o Microsoft CRM initiative. Microsoft Dynamics CRM 3.0 is projected front end for Great Plains, Navision, Axapta. Plus if you consider multinational operations - MS CRM is Worldwide initiative.
Please visit here for Microsoft Dynamics NAV.