SAP B1 initial data migration and conversion is typically done through Data Transfer Workbench, where you basically use CSV Excel templates, fill them in with required fields, leave everything optional blank, build integration on the fly and run it with series of tests and rollbacks until you are satisfied with the data massage and migration quality.
It is also good idea to copy your production company database into the test company and probe the data import there first. Let’s try to break through MS Excel restrictions and see how you could place into production something more complex, ongoing integration, for example. In this publication we will just mention, that real time integration could be programmed in SAP Business One SDK, however this is outside of the scope
1. ODBC integration. At this time ODBC source integration could not be scheduled for automatic run via batch command, as SAP doesn’t support this and it doesn’t work. The way you do advanced ODBC integration – you create SQL view which has exactly the same column names as you see in CSV template for the intended objects. And you will have to provide enumerated column in your view for RecordKey
2. Scheduled Run. The work around to schedule ongoing integration is to create Data Transformation Package, which will import text file (try this nice construction: Microsoft.Jet.OLEDB.4.0, instead of creating linked server), then it will transform the data via SQL stored procedure (feel free to create temporary staged tables, SQL cursors, etc.). Then it will export your data from SQL to CSV file, ready for integration. You can build and save DTW integration, and schedule it in the batch file, assuming that it will work off the CSV templates
3. DTW limitations. Current SB1 version 2007A doesn’t have all the SAP Business One objects covered, or at least we found some objects, which we had to move into SAP BO through SDK small add-ons. Open Inventory, Item Management, Alternative Items – there are no template for Alternatives and you have to push them into SBO through SDK to avoid problems with Early Watch Alert
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 FAQPlanning 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