It has Dexterity interface in Great Plains, does integration to single company at the time. This integration is maintained by Microsoft Business Solutions and allows you to synchronize SOP and Customers in Great Plains with Microsoft CRM Quotes and Orders. If your company is ISV and implements eCommerce product, integrating to Great Plains - you would rather prefer set of open and simple stored procedures, moving data to and retrieving from Microsoft Great Plains Sales Order Processing (SOP) module. Here we need to mention interesting thing, The product, created and dedicated to eCommerce developers - Great Plains eConnect is often considered as a bit expensive and licensing-restricting solution. However you can have successful bridge between non-Microsoft ERP and Great Plains.
Great Plains Integration Manager - this is rather end-user tool - it is very intuitive, it validates 100% of business logic, brings in/updates master records (accounts, employees, customers, vendors. Launch Great Plains and go to Tools->Resource Description->Tables. You need to know Great Plains tables structure and data flow. Looks like Microsoft Great Plains becomes more and more popular, partly because of Microsoft muscles behind it. It was initially created for eCommerce application integration to Great Plains.
Clients who migrated to Great Plains standard are now in the feeling that they paid for something that is free now. As you probably know, when Microsoft purchased Great Plains Software - the whole strategy for Great Plains Dynamics/eEnterprise line was changed. You will be given Migration Tool quote - then install MSDE and Great Plains with exactly the same accounts structure that you have on Pervasive/Ctree. Until early 2004 you could see support expiration date for Great Plains 7. So - Great Plains was running on MS SQL Server, Ctree (Faircom - if you remember 1995-96 Macintosh era), Pervasive SQL (Btrieve.
Here we need to give you highlights on Great Plains Dynamics initial design. The second principle - Great Plains would never allow you to post the batch of transactions behind the scene - only via the user interface - checked and approved by the user. Later on eConnect was extended on the majority of Great Plains modules, including distributions. MS SQL Server, Ctree and Btrieve (later on Pervasive SQL 2000), in 1998 Great Plains Software made it available for MS SQL server only. As you see above - Great Plains allows you to address work tables only - this means that you can not post transactions using eConnect.
Great Plains Accounting is in phasing out -Great Plains Software began this process back in 1995, when it did introduce Great Plains Dynamics and then Great Plains Dynamics/CS. This is a short article, written in question/answer/FAQ style to give IT Specialist/developer/programmer balanced top level information on Great Plains Accounting migration to Microsoft Business Solutions Great Plains. You can use Great Plains VAR/Partner - in this case your cost is usually lower - but you need to do due diligence - find the partner who has experience and has done at least couple of migrations. If you have Great Plains Accounting as main accounting and ERP system you need to know some technical details on the migration to Great Plains and what is going on behind the scenes. As of right now it is reasonable to upgrade to Microsoft Great Plains 8.
Great Plains Dexterity (requires some training and experience), Crystal Reports, Visual Studio. The customization you need is Great Plains Dexterity sales pad and instant item sales inquiry. Author is a Great Plains specialist in Alba Spectrum Technologies ( http. In Microsoft Great Plains you have reserved 5 digits in the currency datatype to be able to track 5 decimals of the . Microsoft Business Solutions Great Plains serves to the wide spectrum of horizontal markets and could be also considered as generic ERP/MRP/Accounting platform for light and advanced customization to fit verticals.
This is Great Plains Dexterity customization, which provides parallel unit of measure, associated with the lot number. We'll describe industry requirements and the way them to be implemented in Great Plains. In this small article we will show you the possible way of deploying Microsoft Business Solutions Great Plains for the market niche of large, mid-size and small reselling and distribution business in carpeting and floor covering, textile & fabric. Microsoft Great Plains itself in our case should be considered as a platform for light customization and modification. This is realized via custom Dexterity table, having Item Number, Lot Number, Initial Length in Yards, Current Length in Yards.
Great Plains, Solomon, Navision and Axapta - and so has different priorities. Dexterity, VBA/Modifier, SQL, ReportWriter, Crystal Reports. Mekorma, Kampdata, Horyzon, Wennsoft, Avalara, Truepay, Trinity, Intellisol to name a few. Third party modules may have their own utility for upgrade. SOP Blank Invoice form, SOP Blank Picking ticket, etc.
He is Microsoft Great Plains certified master, Great Plains Dexterity, Microsoft CRM SDK C. Plus you will need Great Plains Dexterity or. In Great Plains you should use customer/vendor consolidation, available for Great Plains Professional version. This makes eConnect (Microsoft Great Plains SDK) very popular among logistics companies. In the case when you ship to limited number of large customers - you are focusing on the profitability of the shipments and looking at Great Plains as the core system.
This is classical Great Plains Dexterity customization, which should be tuned to your specific customer needs and this work could be done by Great Plains Dexterity Source Code partner only. Typical solution in Great Plains is to have Great Plains Dexterity custom logic to associate the cask with Serial or Lot Number and record it in your inventory in pounds or kilograms. This small article describes you how you could deploy Microsoft Great Plains Bill or Materials in process manufacturing. Microsoft Great Plains has full-featured Manufacturing suite of modules. At the same time Great Plains fits to mid-size companies, where manufacturing processes might be categorized as light assembly.
DIC dictionary (original Great Plains) into custom dictionary, created by Dexterity developer. These are modified via Great Plains Reporting tool. Users has nothing to do with MS SQL Logins, however if you are on SQL version - users are translated to SQL as logins and given access to all Great Plains related database. Setup->System->Security select user id, company, product (Great Plains), type as Modified Reports, series Sales and you will see SOP Invoice Long form available in the list, mark it and you will have it available for this user. Microsoft Business Solutions Great Plains is very good fit for mid-size company and probably good budget solutions for large corporation.
It should be done in Great Plains Dexterity to provide seamless interface for GP users. Software extensions makers may disagree with this simplification, but budget solution works exactly like barcoding extension and is usually done via Great Plains Dexterity, Modifier with VBA and SQL stored procedures. However if you just envision your warehouse workers with barcode scanners - then read this article to understand your options with Microsoft Business Solutions Great Plains. This is typical customization for Inventory, Sales Order Processing (SOP) and Purchase Order Processing (POP) modules in Great Plains. Good luck and you can always seek our help in customization, implementation, integration and support.
This is now Microsoft Great Plains, Great Plains Standard and Microsoft Small Business Manager (scaled down Great Plains version, using he same technology - Great Plains Dexterity. If you remember successful mid-size application - Great Plains Dynamics, pioneered on Mac and Windows graphical platforms in the mid 1990th. You should consider Microsoft Great Plains if you are in. USA, Canada, Latin America, UK, South Africa, Australia - these are markets, where former Great Plains Software had successful penetration. Net, MS SQL Server, Active Directory, BizTalk (integration with Great Plains), C# and VB.
In Microsoft Great Plains borrowers are usually customers in the Accounts Receivables module (RM00101 table - customer master. At the same time Great Plains, now being moved on MS SQL Server platform allows you to deploy standard tools to customize and fit to these requirements, when you don't need rich custom functionality, just few touches. Microsoft Business Solutions Great Plains is very generic accounting application out of the box and has multiple modules to address specific horizontal or vertical market requirements. In Great Plains you naturally use Receivables Management invoices for this purpose. Reporting could be based on both sources - Microsoft Great Plains customer records and loan tracking database, even if the last one sits in different platform, such as Microsoft Access.
ReportWriter will allow you also do new reports - simple option if you want to export all the records from one Great Plains table - use it. You should use this tool if you would like to modify existing Great Plains reports, such as Blank Invoice Form - here you can place your company logo, change the positioning, fonts, colors, etc. All the original report in Great Plains are written in ReportWriter. Smart List - Export to Excel - this is nice feature in Great Plains - you could create a list with simple criteria and then export it to Excel. Obviously flexibility requires you to know Great Plains table structure.
|
|
Three Steps To Windows Safety Heaven
Integrating Microsoft Great Plains Accounting/ERP: RMS, CRM, eCommerce, Lotus Domino - overview