SAP Business One | SAP B1 Service Warranty

By: Andrew Karasev

SAP B1 is small to mid-size business ERP application, and please try to tune your expectations to simplicity and reasonable customizability of SB1. If it doesn't fit exactly to your business processes as they are in your legacy MRP, then you should adapt as much of SAP BO standard logic as possible and only reasonably small circle of required custom features should be implemented via modification and programming
1.Serial Numbers for Warranty contract item. You can have either your internal or manufacturer serial number.

2.Warranty contract types. SB1 supports unlimited number of contracts, where you can specify the duration, which expenses are billable or covered: items (or replacement parts), labor, travel. If expense seems to be outstanding, you can always reclassify it as billable on the specific invoice level

3.Rental Contracts. As everything in SAP Business One, you can find the alternative to deal with rental contracts, where item is not leaving your Inventory and GL balance. The options to consider would be creating special Rentals warehouse, allocating rental item through Sales Order (this allocates the item, but does keep it in your inventory)

4.Warranty service calls. This is where you can enter incurred expenses and turn them into Order, Invoice or other document

5.Multiple rentals per year. If you associate your renting items with Service Warranty contracts, as being allocated through Sales Order, you can track them via Service reports. In this case, you can even go beyond SB1 standard logic and enter such rentals related transactions, as Fixed Assets in rent depreciation in General Ledger

6.Sap Business One Licensing. At this time it is all-in-one, with the exception to CRM users. Also all licenses are per named user

7.Data conversion, customization, integration options. Here we recommend you to review Work Bench and SB1 SDK or Software Development Kit

8.SB1 technology. MS SQL Server 2000 or 2005 should be considered as DB platform, SDK will require Microsoft Visual Studio C# or VB programming, which should preferably be done through SB1 ISV or software development partner

Enterprise Information Systems
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 

» More on Enterprise Information Systems