HT-NewsSAP Business One: extending it with SDK overview for consultant Alba Spectrum
It is always a good advise to adopt procedures and functionality available in out-of-the-box version of any ERP application, including SB1, however it is common, when standard logic doesn"t allow to automate unique business processes
/Software News Articles/ - NAPERVILLE, IL, April 26, 2008 - It is always a good advise to adopt procedures and functionality available in out-of-the-box version of any ERP application, including SB1, however it is common, when standard logic doesn"t allow to automate unique business processes, in this case you have to program modified logic in Software Development Kit. Let"s review SDK in the format of this small article:
1. Programming Language and IDE. You can use either VB or C#.Net and Microsoft Visual Studio will be your tool, assuming that you are on Windows and MS SQL Server platforms. Generic C# programmers are available on the market, however it is recommended to consider contracting certified SB1 SDK developer, who has expertise in B1 objects structure and technical side of business logic
2. SDK integrations. Before considering changing existing or adding new screens to SB1, try to design your customization just to integrate external application. This is good example - imagine, that you have legacy Sales Order Processing system, then when order is ready to be sent over to SB1, deploy SDK programming to create AR Invoice or Sales Order in SAP Business One. If implementing integration logic, try not to communicate with SB1 in real time mode (as if you are uploading 50 objects in one minute from 50 SB1 users), instead try to implement batch upload custom logic. Batch upload logic and SDK programming is common in Barcoding scenarios
3. Implementation with custom add-ons. If you plan to launch SB1 in production, please budget some time for custom tables historical data conversion, here as you can expect you can not use such nice tools as Work Bench to move data in