The transaction concept in enterprise systems

Many enterprises risk business transactions based on information systems that are incomplete or misleading, given that 80-85% of all corporate information remains outside of the processing scope of such systems. Computer technology nonetheless continues to become more and more predominant, illustrated by SAP A.G. recognising that 65-70% of the world‟s transactions are run on their technology thus “have to do a good job”. Using SAP as the illustrative case study, the benefits of Service-Oriented Architecture (SOA) and associated technologies are explored. Together with Business Process Management / Modelling (BPM), social media, Business Intelligence (BI), semantic, multi-agent systems (MAS) and other technologies, enterprise architecture frameworks, principles such as Moore‟s core-context, and conceptual structures, a practical roadmap is identified to TOA (Transaction-Oriented Architecture (TOA). TOA picks up POA (Process-Oriented Architecture) along the way, and is predicated on the Transaction Concept (TC). The TC builds upon work in Resources, Events, Agents (REA) and the Transaction Graph (and Lattice). The TC is the essence of enterprise systems that allow SAP, their competitors, customers,suppliers and partners to do an ever better job with the world‟s transactions.