Combination of Microsoft CRM with SAP B1 is pretty unusual, however consulting companies often offer both products and we have seen customers where this tandem was implemented.
And we had it deployed several years ago in our own consulting practice for internal timesheet submission and automatic transfer to accounting system. Let’s begin with workflow description and go down to code. Please note that this code is presented here just to feel the level of programming complexity or simplicity and it requires initialization files and supplementary SQL scripts. Now let’s go to details:
1. Timesheet entry in Microsoft CRM. We do not have any customization in CRM itself and we do not have ISV add-ons as well. Sales process begins with lead entering and then if we got the deal then lead is transferred into account and contact. We prefer Contract and Contract Line creation as it allows us to track budget on the Contract Line level and have consulting rates pinned to the Contract. When contract is invoiced we open the case and have our consultants and software developers submit their time in Tasks linked to the case. When project manager closed the case then it is scheduled to be transmitted to SAP Business One in the form of Sales Invoice. Integration is running tonight via Windows Scheduler
2. SQL Scripts. We do not provide them in this publication. Their logic is simple. They pull newly closed cases and place them into the queue table in custom SQL database. Following Microsoft recommendation we do not create custom objects directly in CRM database and instead we have created custom database where all views and tables are hosted. If you review CRM database in SQL Server Management Studio you can probably agree that table names are self-evident
3. SAP BO Software Development Kit part. SB1 deploys three tiers architecture with database layer, application server and client interface. It is not recommended to feed data via SQL insert statements and this is why you have to appeal to Software Development Kit where code snippets are available in VB or C#. In our case we have chosen C#. This is DOS application without user interface and we believe that it makes it straightforward for being used as the sample in your programming efforts. It was originally created for version 2005A but we believe that code review to make it compatible to 2007A or even for 8.8X is simple enough for somebody who treats himself as Microsoft Visual Studio programmer with reasonable exposure to SAP BO architecture. If you do not see the code below then please find this publication directly on EFaru website
4. Some tips. Version update requires SDK project to be recompiled in the Microsoft Visual Studio in the environment where new version workstation is installed as the installation brings new DDLs. We also consider this code as ‘the solution’ and not as canned software product. Again in our opinion SAP BO and MS CRM tandem is rare combination and the market is too narrow to support canned add-on. So feel free to contact us, but do not bother with technical details
5. 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 and Canada nationwide and internationally via web sessions and phone conferences (Skype is welcomed)
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
