If you undergone MRP implementation in the past, you probably was a bit disappointed or not utterly happy. If you now look back on technology progress, when graphical operating systems, such as Microsoft Windows made their changes, you may recognize historical drawbacks.
Yes, Windows was nicely looking, comparing to text DOS version, however it had its cost – the application performance went down, plus computer applications, even developed by the same software vendor began to fault in mutual communication. Also, today you have such a strange professions as virus protection specialist, data repair technician, software troubleshooter. SAP Business One or SB1 is in essence breaking through the myths of ERP implementation and following support. Let’s come through the myths one-by-one:
1. Myth one. “ERP has modular structure, you install and integrate these modules, based on your purchased license. It is not an easy task to integrate modules, you have to read complex installation guides and appeal to known issues knowledge base”. SB1 designers tried to make it self-contained and so autonomous. For you this means that internal integration works out of the box as it should
2. Myth two. “ERP business logic, such as entering invoices, posting batches often fails due to various hardware and software related reasons. To recover faulted ERP you should have database administrator, who is familiar with ERP table structure to fix faulted data records in the database. ” In SAP Business One we saw customers, who are entering their daily routines and never saw such things as data consistency problems. System itself efficiently rolls back transactions if hardware related problem happens: such as user workstation crash due to power outage or similar things
3. Myth three. “Technology has multiple layers in its stack. This explains and advocates poor performance of ERP user interface”. Here again we see the opposite. Even the obsolete and naturally slow computers show decent performance when user navigates through SB1. Interface itself doesn’t use too many layers of interconnected technologies, as it is written as self contained application
4. Myth four. “ERP business logic is too complex, this is why software vendor has to support it or in other words fix new version bugs with multiple and regular service packs. These service packs should be patched on regular base by certified ERP technician”. I don’t think we should comment this no longer true suggestion…
Dexterity Customization for Dynamics GP Evaluation Level Paper
When you are developer it is always a good idea to read technical manuals. But if you was just assigned to the IT team to decide if Dexterity is the right tool to customize your ERP application then first you need something which is in style of ‘easy reading papers’ or FAQ
Planning Dynamics GP Customization in Large Corporation
If you are reading this page then chances are high that you were not able to find ISV add-on and need customization project. Let’s talk about planning, quality assurance and future event such as version updates.
Dynamics GP Invoice Logo Attributed to Specific Company or Crossing the Borders of Three SOP Forms
Initial Great Plains Dynamics architecture had three SOP Invoice forms: Long, Short and Blank. Modern GP is popular in scenarios where you have more than three companies under one business entity umbrella
