SAP to Buy Sybase for $5.25 Billion
dealbook.blogs.nytimes.com
dealbook.blogs.nytimes.com
SAP is meant to automate business processes. In particular, it focuses on general business processes that cross industries, plus specific business process that apply generally within an industry.
For instance, cross-cutting processes might be procurement, accounts receivable, accounts payable, asset management, general ledger, invoicing, payroll, time and expense entry, contract management etc. Each of these single functions has a set of common forms that can be customized with the master data of the specific implementation (select box 1 has values Product A, Product B and Product C), plus any custom business rules (field A value X means field B is disabled).
And for your next trick, get everyone to agree on the set of forms, the transitions between forms, the required validations, the exact right set of master data, and other business rules.
And that is barely scratching the surface.
There's a database abstraction layer, which works around some limitations of the underlying databases. What SAP sees as a table might be a set of tables in the database.
It's not an unpleasant system to work with.
I feel out of touch. The only enterprise DBs I run into these days are Oracle and MSSQL.
When I was there at BGI, almost all the business logic was encoded in Sybase triggers & stored procs. It was pretty painful debugging a trade due to all the triggers.