Semantic Business Process Mining of SAP Transactions

Semantic Business Process Mining of SAP Transactions

Jon Espen Ingvaldsen (Norwegian University of Science and Technology, Norway) and Jon Atle Gulla (Norwegian University of Science and Technology, Norway)
DOI: 10.4018/978-1-60566-669-3.ch017
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

This chapter introduces semantic business process mining of SAP transaction logs. SAP systems are promising domains for semantic process mining as they contain transaction logs that are linked to large amounts of structured data. A challenge with process mining these transaction logs is that the core of SAP systems was not originally designed from the business process management perspective. The business process layer was added later without full rearrangement of the system. As a result, system logs produced by SAP are not process-based, but transaction-based. This means that the system does not produce traces of process instances that are needed for process mining. In this chapter, we show how data available in SAP systems can enrich process instance logs with ontologically structured concepts, and evaluate techniques for mapping executed transaction sequences with predefined process hierarchies.
Chapter Preview
Top

Introduction

To describe the current situation in dynamic business process environments we need tools that can assist rapid modeling. Process mining tools meet this requirement by extracting descriptive models from event logs in the underlying IT-systems to construct the business process descriptions from actual data.

SAP systems are promising domains for process mining. SAP is the most widely used Enterprise Resource Planning (ERP) system with a total market share of 27 percent worldwide in 2006 (Pang, 2007). Even though there may be blue print models defined for how the systems should support organizational business processes, there are often gaps between how the systems are planned to be used and how the employees actually carry out the operations. The magnitude of data sources in a running ERP system is large, and within SAP there are several event and transaction logs that can be analyzed with process mining.

In this process mining work, we use transaction data that describe document dependencies between executed transactions. A transaction in a SAP system can be viewed a small application. An example of a transaction is “ME51 – Create Purchase Requisition”. As the name indicates, this transaction enables a user to create a purchase requisition. “ME51” is the unique identifier for this transaction, called the transaction code. Such a transaction would produce a purchase requisition, which further can be referred to by a purchase order created in another transaction, like “ME21 – Create Purchase Order”. By tracing such document dependencies, we are able to extract transaction sequences that can be explored and analyzed with use of process mining.

Data in the underlying databases of SAP systems contain

  • Transactional data – Daily operations, such as sales orders and invoices.

  • Master data – Business entities such as customers, vendors and users.

  • Ontological data – Metadata for interpretation and structuring of instances.

The transactional data are the basis building blocks for process mining analysis and describe events that are carried out. In the transactional data we typically find execution timestamps and relations to involved master data sources. The ontological data in SAP databases can be used to extract descriptions of the transactions and related entities. For instance, in the SAP database there are table structures that contain full text descriptions of transactions and business processes and their internal relationships.

Construction and maintenance of ontologies is work-intensive and has so far been a bottleneck to realization of many semantical technologies. Ontologies tend to grow huge and complex, and both domain expertise and ontology modeling expertise are needed in ontology engineering (Gulla, 2006). In the underlying databases of SAP systems there are lots of structured data that can be extracted to form and populate ontologies. In semantic business process mining of SAP transactions, we can exploit available data structures to limit the extent of ontology engineering work.

One particular challenge with process mining of SAP transactions is the many-to-many relationship between transactions and defined business processes. Figure 1 shows an example from the business process hierarchy in SAP. In SAP systems, business processes are defined at four levels, “Enterprise Area”, “Scenario”, “Group” and “Business Process”. At the second lowest level, Figure 1 shows two business processes, “Subsequent debit for empties and returnable packaging” and “Sales activity processing (standard)”. As shown in the hierarchy, both of these business processes can involve the transaction “V+01: Create Sales Call”. The transaction logs in SAP systems contain no information about business process context. If we do process mining on transaction logs where “V+01: Create Sales Call” occurs, there is no available data that explicitly states whether this transaction was carried out in the context of “Subsequent debit for empties and returnable packaging”, “Sales activity processing (standard)” or another business process.

Key Terms in this Chapter

Semantic Business Process Management (SBPM): An extension of BPM with semantic web and semantic web service technologies in order to increase and enhance the level of automation that can be achieved within the BPM life-cycle

Process Mining: Research area that aims at creating tools for discovering process, control, data, organizational and social structures from event logs.

SAP Systems: ERP solutions delivered by SAP for large organizations.

Transaction Log: Data source in a transaction based information system that describes historical events.

Transaction Sequence: An ordered chain of events that describe transaction carried out, how they depend on each, when they were executed, and relations to involved entities like users, vendors, products, etc.

Transaction: A small application within SAP systems that have a unique transaction code.

Complete Chapter List

Search this Book:
Reset