SAP B1 implementation is typically goes pretty smooth, assuming that you do not require extensive programming in SDK and data conversion. Local implementation firms might be small in size and not affording to have SDK programmer in staff.
Excel CSV templates are also simple to fill and conduct minor data migration. Custom objects, such as new user defined tables or additional fields for the existing table are easy to set and they even get instant user interface to access these objects. This level of flexibility might lead to the attempt of the initial sales person to oversell customizability simplicity. However new table or additional field often require animation via Software Development Kit programming. In the case of data migration limbo we often see that original reseller was not able to export data from your legacy accounting, cleanse it in Excel or custom MS SQL Server table and view. This is not the end of the world and you need to consider getting second opinion from technology oriented consulting company. Let’s take a look at details:
1. SB1 SDK programming. It is normally done in Microsoft Visual Studio VB or C#. These two programming languages have sample codes and projects. Technically it is possible to program SDK for generic Visual Studio developer. SAP however requires special certification and doing programming work through partner channel. Small consulting firm typically has its profit coming from software licenses margin and functional consulting hours. In this scenario they might not be positioned to carry programmer in staff and outsource coding job to subcontractor and this route is prone to potential problems. If you recognize your scenario try to find VAR who features its SDK programming services with proven success records
2. Data Import. Filling up Excel templates is not really a challenge. Project failures are typically associated with challenging connection to legacy ERP database and challenging data cleansing. Let’s review both scenarios. Natural migration path is from something oriented to small business, such as QuickBooks, MYOB, Peach Tree or archaic versions of Great Plains Accounting on DOS, Windows and Mac to SAP BO. Small business packages usually have to deploy proprietary database to avoid paying licenses to SQL vendors, such as Microsoft, Oracle, Sybase, IBM. Here you have to extract data from reports printed into text files. We found that QuickBooks is very advanced in exporting via reporting and the work is doable. Let’s look at GPA for DOS now. It is Btrieve based accounting application. Btrieve and its successor Pervasive SQL 2000 have ODBC connection option via Pervasive SQL ODBC driver. You will need to produce so-called DDF (Data Definition Files). All these steps might be categorized as ABC. The real challenge begins later when you realize that GPA stores multiple tables in the single file and this is why high percentage of records in the table looks like filled with unknown characters. Also due to the fact that customers on Great Plains for DOS have at least ten twelve years of history, the export itself might be up to several millions of historical documents. It is very difficult to compile Excel document with million lines, modern computer is not ready to such a challenging job
3. Historical Data Migration. SAP B1 doesn’t use batch documents processing and as soon as you save something like AR Invoice it is posted to GL accounts. However even considering that batch transaction handling is not present historical documents import is something that you should try to avoid. Let’s take a look at the following approach. You keep your old accounting system running on the old server or transferred to the small computer for lookup only. If customer calls and request the statement with past year invoices – your people are probably OK to do it from the old interface
4. Some facts about SAP Business One. Current version is 8.81 (we are composing this paper in July 2011). In the United States we also see customers with two previous versions 2007A and 2005A. SAP requires annual support contract, due in the beginning of the year. If you do not extend your contract you lose access to the next version licenses. It seems to be extremely popular is such countries as Brazil, where it might be implemented in mid-market environment. It also supports Unicode characters and by doing so makes itself open to such countries as Korea, Japan, China, where alphabets are based on hieroglyphs. There are numerous implementations in multinational companies to automate accounting for their foreign facilities with modest operation volumes
5. Please call us 1-866-304-3265, 1-269-605-4904 (for international customers, where our representative pick up the phone in St. Joseph, MI call center). 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, Brazil nationwide and internationally via web sessions and phone conferences (Skype is welcomed). Our consultants speak English, Spanish, Portuguese, Russian, Chinese. Our core expertise is in International Business
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
