Accounting system selection, executive demos, licenses acquisition and initial implementation are just the first steps in your ERP application life cycle. Even if you believe that you did detailed homework in reviewing functionality, compiling and matching specifications later on you might decide to change procedures and deploy alternative business logic. In other words you are leaning toward something that could be categorized as second phase in your implementation project. And here you may think about such improvements as customizations, integrations, reporting and user interface modifications. You may also come to unexpected conclusion that your original reseller is not really excited about doing custom programming for your new Small Business ERP application even considering the fact that they sold you software licenses and did decent job in initial implementation. This is fine as every consulting firm has its own specialization and strong points:
1. Secondary ERP Market Consulting Specifics. Here you cannot feature your consulting company as strong in getting new customers via telemarketing followed by aggressive sales efforts. Instead you have to prove that you are expert in technology and ready to undertake custom software development project. If you cannot proof that you are guru in your consulting field there is no options for you to enter secondary market as here you have customers who are unhappy and need help with second opinion, failed customization recovery or similar problems
2. Customizations. Generally it is recommended to deploy native business logic and minimize custom software developing. Custom logic should be planned as small fraction of original functionality available out of the box. You should understand that such surgery as future version upgrade requires special attention to custom modules. They should be reviewed and recompiled as the minimum. However future version might introduce changes in the collection of the fields on the form or in table structure. All these mean that if you have custom business logic it is recommended to do test version update first and test all custom logic there. If you got a feeling that ERP application requires massive custom coding and even if you got very good recommendations from friends or business community we recommend you to look at alternative platforms where less customization is required
3. Unrealistic Data Conversions. Working with Corporate ERP data migration and cleansing projects we can certify that this is one of the most likely reasons for implementation project to hang in limbo or even fail completely. The relations with consulting organization should be manager. If you suggest something like 'migrate all the documents including all the history' then your consultant might be facing the dilemma on discouraging you from such massive migration or execute the order as it means high data migration consulting budget. Try to consider keeping legacy accounting running for just data inquiries and move only master records and beginning GL balances to the new accounting
4. Integrations. ERP application is not something isolated in its dedicated server computer. It has to talk to your peripheral applications, such as Ecommerce, EDI, POS and Retail or Client Relation Management. Some of these applications might be driven by SCM and Warehouse Management technologies including Barcode scanning or RFID tags. In integration implementing try to avoid custom coding and consider deploying native integration tools first. This approach should secure future version update projects to be smooth. Let us give you also couple of recommendations of cross-platform integrations where you have to import transactions from MySQL, Oracle, Sybase or another database platform. Try to deploy ODBC connection where records are cleansed via custom SQL View
5. We tried to make this small paper to be easy reading for managerial personnel and business owners. If you are programmer and need technical details please see our earlier publications from Alba Spectrum and Faru Corporation. Alba is dedicated to Dynamics GP and all the historical versions of Great Plains Accounting and Dynamics while Faru is about SAP Business One and Dynamics AX or formerly known as Axapta
6. Last Flint or international ERP consulting. Here you have to pay attention to fiscal policy of the local country as well as to business related legislation. In the United States we are enjoying one of the most liberal business codes where such risking folks as new business initiators are favored. In the foreign country you might find the opposite approach where small business owners are overtaxed. One of the typical hurdles is Unicode characters support required for hieroglyph based alphabets including Chinese, Japanese and Korean
7. Data export from Great Plains Accounting for DOS. This ERP application was popular in earlier 1990th and currently we are facing strong trend of migration from GPA to SAP Business One, Dynamics GP, Axapta and small business packages such as Peach Tree and QuickBooks
8. Please call us 1-866-304-3265, 1-269-605-4904 (for international customers, where our representatives pick up the phone in Naperville and St. Joseph, MI call centers). We have local presence in Atlanta, Chicago, Southern California, South West Michigan, Houston and Dallas areas of Texas. We serve customers USA, Canada, Mexico and Brazil nationwide and internationally via web sessions and phone conferences (Skype is welcomed). Our consultants speak English, Spanish, Portuguese, Russian and Chinese. One of our experiences is international Corporate ERP and Consolidated Financial reporting
iAutoblog the premier autoblogger software
沒有留言:
張貼留言