The distinction between abstract business system transactions and abstract business system processes

The distinction between abstract business system transactions and abstract business system processes is this: transactions are the direct result of some user performing some business activity, and processes are periodic events that do things with data that is already known to the system from transactions and other processes. Some abstract business processes will correspond very closely to real ERP processes – for example, MRP. Some abstract business processes are nothing more than data transformations that must occur sometime after one event and before another.

In the actual ERP system, some of these latter processes may turn out to be built into a query or report that returns the data: the abstract business system doesn’t care when the ERP system calculates total purchase order value , only that it does calculate it according to very specific rules, and does so in time to use it in a particular transaction, process, query or report.

In spite of the number of things that the abstract business system does not specify, many of the requirements it includes will be too specific to fit the way a particular ERP package actually works. When this happens, the ownership of requirements matters very much.