When you plan to implement SAP B1 for small business, in most of the cases out-of-the-box installation with initial balances entry and following user training will do the job of placing your ERP into production. When, however you are mid-size business, where number of users is twenty or more, you will need such elements of implementation as modification, integration with legacy systems, EDI, possible initial historical data conversion and other custom programming adds-on.
Let’s review options and typical scenarios:
1. Licensing. SB1 deploys all-in-one license schema, meaning that each named user will have access to all native SBO modules. One exception is CRM only user, typically you purchase for your sales people these licenses at about 50% of the all-in-one license price. If you have third party add-ons then each ISV can have its own licensing policy and you need to check with them individually plus you will need to synchronize with them version upgrade schedule
2. Integration. Here you have two options to consider on the first place: Work Bench (where you can import master records and transaction into SB1 in Excel templates format) and SAP Business One SDK programmable integration, which is as you could expect very powerful and very flexible, but it requires custom C# or VB.Net programming
3. SB1 Customization. Here you need to familiarize your IT people with SB1 SDK. SDK allows you to do two types of modifications – user interface extensions as well as on demand or scheduled integrations (where you manipulate SBO objects behind the scenes without user intervention needed)
4. Implementation cost. You may think that customizing SAP Business One is unnecessary luxury, however think again. In essence you are saving on SAP user licenses and paying only small business user licenses price. As being mid-size you should have some room to pay for extending standard logic with required custom logic
5. Industries. SAP Business One should fit to the majority of industries, however if you are service oriented organization or light manufacturer or assembly – we recommend you to review SB1 Service and Production modules and see if you can capitalize on their simplicity and at the same time fitting to your business processes
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
