SAP Business One Implementation Recovery

May 10
07:45

2011

Andrew Karasev

Andrew Karasev

  • Share this article on Facebook
  • Share this article on Twitter
  • Share this article on Linkedin

There might be situations when your small business ERP implementation was screwed and now you feel yourself in limbo.

mediaimage

Well,SAP Business One Implementation Recovery Articles now it is probably the time to look for second opinion.  We would like to describe some typical scenarios when you get your Corporate ERP implementation in danger.  Try to match them with your case and see how situation could be ruled out.  We’ll use some technical terms, meaning that this paper should be reasonably friendly to business owner as well as information technology department folks:

1. Data Conversion.  When you approach a reseller who is local to your headquarters – these people would probably take all leads coming their way, assuming that they will learn new features as project progresses.  And this is normal way in IT consulting.  Local partners typically are positioned to do generic CPA style implementation with modest data conversion and custom programming.  If you do not want to do your homework and when discussing data migration requirements simply order “bring over all my legacy accounting data” and your prospective consultant politely agrees – this might be the cause of the future failure.  Think about data massage and migration as something that requires rationing.  Every accounting system is different and in order to bring over transaction history you either have to have migration tool, or do it via custom coding or deploying integration module.  In the case of SB1 it is Data Transfer Workbench.  When SAP BO consultant gets her or his certification training they have a lab on creating CSV files (often referred as Excel templates).  These templates cover most of the master records and transactions, but filling them up with all your historical data requires consulting time and you should expect several attempts to bring you over to final production conversion.  If you feel that your initial migration crosses all the possible budgets, we recommend you to change your data conversion requirements.  Consider bringing over master records (business partners with addresses and contacts, inventory items, GL accounts) and General Ledger beginning balances.  The rest you could set up directly via user interface

2. Customization.  When you see sales presentation on this small business ERP and MRP you might get a feeling that it is modification friendly and no coding is required to reshape its user interface and business logic.  There is a culture of “sales pitches”, where something that is available is sold in the nicest wrapper.  It is true that customization could be done directly in user interface.  For example you can add custom tables and they are visible to the user.  You can also add fields to existing tables – add fields to Sale Invoice Line.  We agree with these statements, but how about animating these custom tables and extended fields to the existing files?  Yes, all that should be done in programing in such customization tools as Software Development Kit, DI Server.  Even if your SAP B1 application hosts its databases in Microsoft SQL Server and some of the programmers might think that they should be able to do coding in SQL Stored Procedures – it is not recommended.  There is Watch Dog utility which is supposed to observe if somebody is trying to update tables directly via SQL and report the violation

3. SDK Programming and Performance Issues.  This ERP system deploys three tiers architecture, where programming should respect the model.  Not every SAP Business One VAR has SDK certifications and programming requires expertise.  If you are taking customization route, we recommend you to check if your reseller is certified to program SDK.  User interface altering might be funny, but it requires revision when you are upgrading to the new version of the software.  In our experience custom modules where performance doesn’t meet expected standards are popular implementation failure cases

4. Please call us 1-866-304-3265, 1-269-605-4904. help@efaru.com  We have local presence in Chicagoland, Southern California, South West Michigan, Houston and Dallas areas of Texas. We serve customers USA, Canada, Mexico nationwide and internationally via web sessions and phone conferences (Skype is welcomed). Our consultants speak English, Spanish, Portuguese, Russian, Chinese