• SAP is a Total Business Solution. Includes Accounting, Distribution, Manufacturing, Sales Force Automation & Customer Service in one integrated solution with one code base, one database with a single installation. It’s your choice as to how much or little to use, but as you use more, its available with the one price per user. Since CRM is part of the standard solution, you can use it in all areas. For example, create to-do’s and followups regarding a purchase order, a General Ledger Entry, or collections activity against an invoice.
• MAS500 is only ERP, not CRM. You need to purchase Sage Saleslogix for CRM and then use their newly released (and still being debugged) integration. This is the 3^rd integration in 4 years as the prior ones have been terrible.

• The jury is still out on this one as it’s too new. Saleslogix is written in a different code base, different database, has a different user interface and doesn’t have nearly as many “integrations” since it is a separate program. It more than doubles your IT maintenance efforts with its own set of patches, OS installs, compatiblity issues etc. Most VAR’s need to different implementation teams and trainers as few people know both well. You call a different Arizona vs. California with a different process for support depending on if you problem relates to CRM or ERP.
• SAP is designed from the ground up to be a solution that is friendly to Third Party ISV’s to enhance the breadth and depth of the solution as well as open to end users with development talent to build their own solutions and integrations. SAP Business One is only 7 years old whereas MAS500 is 11 years old, yet SAP has at least 6 times more third party addons, all certified by SAP. Sage only has a small handful of “certified” add ons, and some additional non certified add-ons.
• All of SAP’s logic is managed in your .net development environment. SQL Stored procedures are used only where they are necessary to improve performance. With MAS500 about 50% of your logic and code is written in Transact SQL and 50% in VB 6. This makes it difficult to modify or trace where processes occur within the product. Add to that that most developers will say the product is “over normalized” to the point that you have over 17 tables being accessed while entering lines on a sales order. Modification is difficult and expensive and reporting can be complex because of this as well.
• SAP is designed as an object oriented layered architecture that does not allow end users or ISV’s to actually modify the core source code. Yet virtually everything about the system can be accessed and customized via the development tool of choice (usually VB.net or C##.net) through extremely well documented API’s, both User Interface (UI) and Data Interface API’s.
• MAS500 relies on the end user to use Visual Basic Version 6 to modify the application, and you are modifying the source code. Yes it does have an available extra cost customizer module but that primarily just allows access to tweaking existing screens and adding some user definable fields (but with little to know program logic behind these fields). You will rarely see a MAS500 installation with enhancements from more than 1 third party vendor due to the possibility of code conflicts.
• SAP is easier and safer to integrate with. You have 3 options.
• For simple initial data conversions, you can use the included Data Transfer Workbench. This is a tool that allows you to map source files to tables in SAP and import the data with full data validation
• For real time bidirectional integration by a developer, you can use our DI (Data Interface) API and directly read and write to our objects (i.e. Sales Invoice) via a .net enabled development environment.
• You can optionally use xFusion, which is priced about the same as the DI API, that allows you to use a drag and drop interface to map and transform source data into Business One and can be scheduled or called on demand.
• MAS500 does not support you writing directly to it’s tables or you void support. They do sell, function by function, some API’s that they wrote via their professional services group, not the regular development team. This PSG group recently had a 50% headcount reduction so long term support of the API’s is questionable.
• A brand new module, Data Import Manager, was just released (after more than 4 years of being promised). It is roughly comparable to SAP’s Data Transfer Workbench. But since MAS500 isn’t object oriented, the product only handles the entities they’ve hard coded into the tool. It supports a handful of documents but not all. For example, you can import a Sales Order, but not an Invoice.
• The biggest cost overruns and disappointment with MAS500 has always been around importing and integrating with the solution.
• SAP’s logic, screens and reports, both standard and customized are stored in the database. MAS500’s VB projects and Crystal RPT files are on the workstation and if you want to modify a report, you need to go to every single workstation and copy the modified .rpt file to each
• SAP is easier to use, more intuitive and faster to work with for most everyday users.
• SAP navigates much faster. It is one executable in which the various screens open within it. This means, once you log into the system, screens within it pop almost instantaneously. MAS500 are separate Visual Basic Projects that are tied to a common launcher. Each one that opens consumes memory and depending on network and hardware can take 4 to 10 seconds each to open. All of MAS500’s excutables are loaded on the local workstation. MAS500’s has strong drill down and around, but they are sluggish and not always unintuitive. It relies an proper right mouse clicking too often for average users. SAP, you simply follow the Orange Arrow to all related data. Since MAS500 is a separate application from Sage Saleslogix, you can’t drill back to items in the CRM solution. Thus from an Invoice, you can drill back to a quote, but not back to the opportunity and related conversations and communications.
• SAP is a “Real Time” solution. Most transactions are recorded and posted to all related tables upon entry. MAS500’s “Batch” design harkens back to the old MAS90 design in which you enter everything into a data entry “Batch”. You then must physically print a report to a printer to flag it as having an audit trail (unless you do a supervisory override). Then you must print a General Ledger audit report, then you must say to update where at that point it updates the related tables. All this extra clicking and process adds substantial time when looked at across all your users over the years you will be using the system.
• SAP provides basic end user Interactive Video training at no charge, and comprehensive consultant/developer level Interactive Video training for only $1,500. Other than the on-line help, there is virtually no training materials for MAS500 without you going to rarely held training classes and I don’t believe any video training is available. This makes SAP a lower cost product to implement and a lower cost long term as you add additional personnel.
• Like MAS500, SAP supports creating reports with Crystal Reports. In Addition to Crystal, it also includes out of the box, XLReporter which means anybody who is familiar with Excel can write Live Reports that pull from SAP as well as comprehensive Dashboards (over 40 samples come with the product) all running within Excel. Again, full Video Training is available. This means there is no need for complex additional portal servers or web servers. All of SAP comfortably runs on one single server. Remember that Crystal is owned by Business Objects who is owned by SAP.
• All reports all have live drill down capabilities so when you want to know more, just click the orange arrow. MAS500’s Crystal Report output are static.
• SAP includes the Patented Drag & Relate functionality that allows any user to “slice and dice” the data to see related trends. MAS500 includes “Business Insights Explorer” which is a different code base product they license from a 3^rd party that bolts onto the MAS500 launcher. It is very clumsy beyond the demo, very slow, and offers limited drill down. You’ll see some embedded Excel Pivot Tables and Charts, but they are pretty much fixed views of the data and are used much less than they are demonstrated.
• SAP Business One is supported in 42 countries and in 22 languages with over 20,000 installations. MAS500 has about 4,000 installations and is primarily only supported in the US. There are one or two additional language versions available through 3^rd parties, but no non-US Tax/Compliance support. Keep in mind Business One is about 7 years old and MAS500 is 11.
• SAP Business One has completely integrated Exception alerting, messaging and workflow with approvals. The only option for MAS500 is an extra cost 3^rd party solution called KnowledgeSync for alerting. There is no reasonable choice for workflow and approvals for MAS500.
• SAP Corporation is the 2^nd largest software company in the world. Sage is much smaller. Sage is basically a UK finance company that has acquired over 100 companies over the years and they operate mostly independently with limited sharing of best practices and solutions. They more often compete with each other rather than complement each other. Sage must spread their R&D over hundreds of different code bases. SAP currently only has 2 code bases. MySAP, the product for very large companies, and SAP Business One for small and mid-size companies. This means their rate of progress and enhancements can be substantially faster in terms of long term improvements.
• MAS500 has some built in functionality that doesn’t exist in SAP Business One. It has Inventory Replenishment logic for companies with many warehouses and strict adherence to specialized buying processes. It has out of the box Intercompany GL & AP processing, the available manufacturing modules go deeper on shop floor and work order controls, MAS500 has more advanced bin management as well, SAP cannot tell you what location in a warehouse an item is in, if its in more than one bin location. SAP’s vast third party library can address any of these issues but they aren’t out of the box.

Information on Crystal Reports and Xcelsius is also included.  Both these products work well with Sage MAS90 and MAS200.  Everything is wrapped up in an entertaining and visual video and avatar presentation format.

Click HERE to go to our sub-site.

You can view it within the blog, or click on the link above the document to download it.

Download or View SAP Business One To Go 2007 on Scribd

From that vision came an ERP system, rewritten and streamlined with all new code (500 thousand lines v. 2 million), based on N-Tier architecture and positioned to change as the market demands. New functionality has been added that expands FourthShift Edition’s market to include discrete and process manufactuers that function in make-to-order, make-to-stock, and configurable environments.

Listen for an audio sneak peek.

Thanks to Ed Monk of SBONotes.com

To process the payment for an AP Invoice that is "stuck", just go to the order and select the address to pay to from the list of addresses in the drop down control beside the address block and SAP Business One will populate it on the order (then click Update). To prevent this situation from occurring again, just set a default address for the customer in the Business Partner Master.

Thanks to Ed Monk of SBONotes.com

If you need to have all of your users have the same screen layouts (e.g., the same columns in the same order within the Purchase Order) you can use this qery to quickly copy the settings from one user to another. Obtain the UserID numbers with this query, run it in SBO or another tool:

SELECT UserID, U_Name FROM OUSR ORDER BY U_Name

I recommend that you create a dummy user name and set your screen formats for a group of people, just like you should when setting authorizations.

Declare @target as smallint
Declare @source as smallint
Declare @form as nvarchar(20)
/* Change this to the Target UserID (number from OUSR) */
Set @target = 2
/* Change this to the Form number obtained from the Sys Info Line at bottom of SBO */
Set @form = 142
/* Change this to the Source UserID */
Set @source = 22
/* Removes the temp table if it already exists. */
/* temp_settings is created and destroyed only for this operation */
if exists (select 1 from sysobjects where name = ‘temp_settings’)
Begin
drop table temp_settings
End
/*Copy from the source ID for a specific form */
Select * into temp_settings from CPRF where usersign = @source and FormID = @form
/* Remove the target info for the form and user */
Delete from CPRF where usersign = @target and FormID = @form
/* Change the UserID in the Temp table to the new user ID */
Update temp_settings Set usersign = @target
/* Put the information back into the SBO forms table */
Insert into CPRF Select * from temp_settings
/* Removes the table just in case! */
Drop Table temp_settings

Thanks to Ed Monk of SBONotes.com

• From the drop-down menus at the top of the screen, go to: Tools -> Queries -> Query Manager

• Click on the Query Manager icon located on the icon bar at the top of the screen.

The Query Manager window will appear…

Thanks to Ed Monk of SBONotes.com

1. Create a Query in SAP Business One
2. Open the Query Manager
3. Find your Report
4. Highlight your report (single click)
5. Click on the Create Report button at the bottom of the window.
6. A window appears with the name of your query at the top of the window.
7. Window is divided into two parts: Top is existing reports, bottom is a list of the report templates.
8. Click on the User Report (System) template in the bottom part of the window.
9. Click the OK button.
10. You are returned to the Query Manager
    (At this point you are probably thinking that nothing happened, but it did).
11. Click on the Create Report button once more.
12. The Create User Report window opens again. Now in the top part (the box under Name) of the window you will see the name of the report you were trying to create. This indicates that the initial report was created successfully.
13. Now…Double Click on the the name of your query in that section and the Print Layout Designer (PLD) windows will open and allow you to modify the layout of the query information on the report.

After you have completed your changes to the layout and have saved your work, you can see the actual printed document by accessing the Query Manager, highlighting your report name, and clicking the print preview icon at the top of the screen.

Thanks to Ed Monk of SBONotes.com