Traditional approach of small and mid-sized ERP implementation suggests consultant to stay in your office while installing, migrating your accounting data, setting up user workstations and Database maintenance plans.
Often, however you figure out that your ERP consulting partner changes coming onsite consultants at its discretion, and you are in disadvantage by being exposed to pretty various consulting styles and often see poor communication between previous and next specialist. We recommend you new methodology, which is now possible due to advances in such technologies as VPN, web sessions and remote SQL setup and support:
1. SB1 Sales cycle. Here you more likely want to face SAP BO sales engineer in your office. However, even the best salesperson could not theoretically be exposed to all functional and technical details. So, sales engineer appeals to centrally located SB1 support team, who can address virtually all the questions during the presentation, being in the web session. This speeds up your clarification on ERP selection and implementation
2. SB1 deployment. Contrary to pure traditional approach, we recommend you to combine centralized SB1 installation, which includes SQL Server db creation, modules settings, your data conversion (beginning balances, master records: business partners, chart of accounts to name a few). Then this pre-implemented ERP is transferred to your office, where technical consultant implants it on your server and connects your user workstations to your pre-implemented SBO
3. SB1 integration with your legacy applications. In ideal world we would like our customers to install SB1 out of the box and use its standard features. However in real world, customers have to practice IT system phased approach, where you change your IT infrastructure parts in evolutional way. SB1 has several integration options, including workbench, SAP Business One SDK, plus you can with certain cautions use direct select SQL statement for data export. These tools address such often challenging for small accounting applications requirements as EDI (electronic document interchange), eCommerce (where SAP B1 has integrated module, however if you have established e-commerce website, you can connect it to SB1 via software development kit or SDK)
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
