SAP B1 is focused to little and mid-measurement companies. This ERP and MRP enriched accounting software becomes far more and additional preferred, especially due to the fact the release of SB1 model 2007A. The intuitive and very easy SAP BO interface often comes with the simple fact, that SAP Business enterprise One certified advisor arrives devoid of strong technical track record in knowledge conversion, customization, SDK programming and also in earning ad-hoc SQL queries. We really should mention right here, that you can normally go and deploy SAP Business enterprise A person SDK programming in integration development, even so right here we will focus on "reduced profile". Let us start off:
1.SB1 Knowledge Transfer Workbench: CSV file and Excel templates. By our apply, big variety of Sap Enterprise 1 useful consultants suggests you simply to abide by template Excel files filling up and preserving them in CSV format as preferred way to do integration. Plus, they also endorse it for an individual-time integration only in the original info conversion and migration. If you don't want added discovery and looking for 2nd opinion in SAP Organization An individual partners community - this advise is beneficial and pretty trusted. However - what to do if you need ongoing and even scheduled integration?
2.Easy ODBC queries. Let's make phase aside and check out ODBC in Resource Knowledge Sort. If you are IT skilled, SQL DBA or programmer, you know, that ODBC connection opens the total new world of these good resources as MS SQL Server linked server, SQL See to bust by the limitations of text files
3.SQL Views Scenario. Now imagine, instead of depending on CSV files, established by hand, you develop SQL check out, which will be the base for the integration. If you have to integrate SB1 with entrance end legacy database (which include SQL linked server constructions to such platforms, as Oracle, DBII, Ctree, Pervasive SQL), you ought to lookup required SQL watch structure in Excel templates for the supposed SB1 objects and just produce them on Microsoft SQL Server level
4.Scheduling Workbench ongoing integration. Workbench assist suggests you to conserve integration framework in XML format (you do it on the stage 5: Operate the info import - click Help save button and you will be capable to save integration in XML schema). Develop -bat (DOS batch) file. Then schedule it in Get started->All Products->Accessories->System Equipment->Scheduled Tasks. This would be sample line in BAT file: C:Program FilesSAPData Transfer WorkbenchDTW -s C:Program FilesSAPData Transfer Workbenchconfig.xml.
Loading...