With the introduction of the version 8.8, where A and B releases are merged into one we expect the spark in implementing SB1 for multinational corporations.
As you know in SAP BO you can switch user interface language within the same session. To give you additional details – such user interfaces and company SQL collations could be combined on the same server for Chinese, Brazilian, Japanese, Korean versions (historically separated into 2005B or 2008B). The A version for USA, Canada (and other English speaking countries), Russian Federation, most of the West, East and South Europe could be now implemented on the same SQL Server, exposed to Worldwide operations via VPN, Citrix or Remote Desktop Connections (Microsoft Windows Terminal Server). We are specializing in SB1 custom programming in SDK, Microsoft Visual Studio C# or VB.Net projects, DI Server. We would like to give you initial introduction and recommendation in SAP B1 technology partner selection:
1. SB1 SDK. Here we assume that you already explored Custom tables, custom fields addition to existing SAP BO tables and you feel that these instruments do not do the job and you would like to explore SDK programming. SDK has code samples in C# and VB. The natural way is to create customization or integration project in Microsoft Visual Studio and then include SDK libraries. Integration is one of the most popular, however you can even modify or alter existing user interface, if this is your objective. There might be really exotic cases in deploying SDK libraries, for example we have a customer who requested programming to be conducted in Delphi (former Borland Pascal). There is one observation that we would like to mention. It seems like SDK programming requires programmer awareness about the best methods to provide adequate performance (number of documents integrated per hour, for example)
2. Work Bench. Of course every consultant should be able to help you with text (coma, or tab delimited) file integration. However Workbench power goes beyond. You can integrate ODBC compliant tables. We were able to update item catalogs with substitution and obsolete items via Workbench
3. Crystal Reports. This seems to be very popular modification request. If you are software developer you can review tables structure in SDK or simply enable system info in view and then open the document in question (such as Sales Invoice), place the cursor on the fields, where you would like to known the table and field and the info should be read on the left bottom area of the user interface
4. Disassembling Bill of Materials. This is what we like in small manufacturing, and this feature is available in the native business logic. Imagine the scenario, where you are manufacturing on customer order, ship the final assembly to the customer address and then get it back as return. If you think that parts could be reused and placed back into in stock inventory quantities, SB1 offers direct solution via Disassembly
5. Warranty Contracts. If you are selling with Warranty (typically the items with Serial Number), consider implementing this functionality in SAP Business One Warranty Contracts, which could be further customized in SB1 SDK
6. Implementation in Spoke and Hub Scenarios. If you are multinational corporation with SAP R3, mySAP or non SAP ERP application in USA based Headquarters, such as Dynamics GP, AX, SL, NAV and your core ERP application is not localized in the country where the subsidiary is hosted, consider SAP Business One. GL Trial Balance report could be exported to Excel and then used as the source in consolidated Balance Sheet or P&L in FRx or Microsoft Management Reporter
7. Versions. The newest one is 8.8 (with patches released up to the point, where we are composing this paper in May 2011), precious versions were 2008A and B flavors, 2005 A and B. If you are on older version and would like to recover your implementation and upgrade it all the way to 8.8, you may expect upgrade path (as it is patch level sensitive)
8. Special attention to Brazilian customers. We have our SDK Software Development Factory based in Sao Paulo, Brazil, where we are happy to provide the highest quality local service. This fact makes our company attractive to multinational corporations expanding from USA, Canada, South Africa to Brazil. To remind you – this application is localized for Brazilian market (translated to Brazilian Portuguese and made compliant to local business legislation)
9. International Projects. We do recommend the approach where you host your Corporate ERP application on the same SQL Server in USA and enable remote access to your international offices and facilities via Citrix, RDC, VPN. We are especially excited about the fact that even Chinese manufacturing facility could be seeded to your centralized MS SQL Server (in version 8.8 and newer)
10. Please call us 1-866-304-3265, 1-269-605-4904. help@efaru.com We have local presence in Chicagoland, Southern California, 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
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
