SAP Business One Custom Objects and Flexibility

This product is different and there no need to program when you need let’s say add new fields to core tables as well as introduce new user defined tables.  Sometimes old-good-days developers ask – how about user interface to these new objects?  The answer is – it is created automatically.  These objects are often used in integrations with external database or system as well as in all kinds of managerial reports (in Crystal Reports).  Another cool feature is the fact that these objects are stored in metadata which in turn is stored in SQL Server company database.  This architecture is immune to version upgrades.  In older accounting packages customization often required code revision – meaning consulting time and uncertainty.  Let’s take a look via client interface and create couple of objects:

1. Adding fields to Sales Order Line file.  Tools -> Customization Tools and select User Defined Fields Management.  Here expand ‘Marketing Documents’ and then Rows.  Click Add and you are about to add custom field.  Now let’s talk about simple automatic interface creation. It depends on the type.  In Sales documents you can add fields on the form via Form Settings icon and then Row Format.  In the case when you add field to master records such as Business Partner then select View User Defined Fields – and simple form should popup to the right next to Business One window

2. Now let’s create new table.  Tools -> Customization Tools -> User Defined Tables Setup and here create table header.   When it is done you can add fields the same way as described in paragraph above.  And for editing records follow this way: Tools -> User Defined Windows

3. There might be curious developers who want to know if the objects are expanding core table or they are kind of ‘virtual’ and stored somewhere outside.  You can take a look via SQL Server that the field is expanding the structure and is ‘real’

4. Software Development Kit.  When your project goes beyond the Crystal report design and you need new logic to be programmed.  You can do it in Microsoft Visual Studio by linking SAP B1 libraries and reviewing code samples exposed in SDK in VB or C#.  Methods described in SDK classes are safe to data corruption and compromising as they validate application business logic.  Business One has three tiers in its architecture: DB, application server and client.  Application server is responsible for such issues fix as rolling back incomplete transaction due to computer crush.  In such technology you should not use SQL Server procedures to push data directly to the database and bypassing application server

5. Before jumping into SDK coding we recommend you to check through ISV channel if third party product is available to do the job.  In SAP terminology it is often referred as add-on.  If there is nothing out there we would recommend you to minimize your ambitions and consider minimum and the work on ‘integration side’

6. Please call us 1-866-304-3265, 1-269-605-4904, help@efaru.com.  We have local presence in Chicagoland, Southern California, Atlanta Georgia, 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).  We are working on Brazilian ERP consulting market in Sao Paulo since 2004