Skip to Content


Today’s, in a time where competition is strongly pushed by globalisation the market situation is characterized by cost competition, increasing quality and customer relationship and shortening product lifecycle („Time-To-Market“ und „Time–To-Customer“). Consequences of globalisation are increasing costs, time reduction and decreasing product competitiveness. Time pressure lead into savings in those parts which are essential for innovations. Knowledge within SAP nowadays are documented and represented in several Wikis. Thus the knowledge transfer via Wikis is a very important point for all of employees. 

Definitions of knowledge transfer:

  • Within a modern, knowledge driven economy, knowledge transfer is about transferring good ideas, research results and skills between universities, other research organisations, business and the wider community to enable innovative new products and services to be developed. (
  • Effective sharing of ideas, knowledge, or experience between units of a company or from a company to its customers. The knowledge can be either tangible or intangible. (Process)
  • Knowledge transfer in the fields of organizational development and organizational learning, is the practical problem of getting a packet of knowledge from one part of the organization to another (or all other) parts of the organization. It is considered to be more than just a communications problem. If it were merely that, then a memorandum, an e-mail or a meeting would accomplish the knowledge transfer.

Problem area

First, the large number of Wiki-spaces at SAP without relation from one Wiki to other:   



 Second, no process modeling within the own enterprise. Work is often done twice, documents are generated unnecessarily or in the worst case employees are instructed to solve problems whereas the solution already exists in the enterprise itself. Here is focussed to define a process oriented knowledge transfer on the basis of SAP Wikis.   


The situation today on SAP Wikis: 



 • Knowledge is distributed in each development and support department as statical knowledge. It’s no correlation between the contents of one Wiki with other Wikis -> Missing of interdisciplinary access of information

• No structured Knowledge about the components/moduls and Processes -> Work is often done twice

• It needs more time to find correct information on the Wikis -> no motivation to use Wikis as a tool for knowledge transfer   

To solve the problems we have to define the business process with links to the statical knowledge. The main goal is a wiki- and process-based knowledge transfer to increase efficiency and effectiveness knowledge transfer at SAP. The following example should show the correlation between a process “Mapping execute” and the related information on the Wikis.  




1)    Define your process modeling with the Wiki. A plugin muss be installed to enable the flowchart makro. For Wiki Confluence e.g. we have to install the plugin GrphViz and Apache Ant.( 

2)    Define all of the actions as parts of your processes within following information:


3) Make the correlations between your defined action information (Control, Input, Output, resources) and the source of information (statical information on SAP Wikis).

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Richard Hirsch

    You might want to take a look at Gliffy Plug-in (The specified item was not found.) instead of the FLowChart plug-in. We have had good experience using the tool.



Leave a Reply