Tous nos rayons

Déjà client ? Identifiez-vous

Mot de passe oublié ?

Nouveau client ?

CRÉER VOTRE COMPTE
Sap Process Analysis with Knowledge Maps
Ajouter à une liste

Librairie Eyrolles - Paris 5e
Indisponible

Sap Process Analysis with Knowledge Maps

Sap Process Analysis with Knowledge Maps

Jürgen Röhricht, Thomas Teufel, Birgit Teufel-Weiss, Peter Willems

304 pages, parution le 15/08/2000

Résumé

This book forms the basis of the SAP Process Library and is a kmustm for those who want to understand the general methods of process analysis, knowledge management, and working with knowledge maps. The book explains what knowledge maps are, how they were derived from the MindMapping method, and how they can be used to reflect real-life situations. It describes in detail the theoretical background of process analysis within the framework of business engineering and knowledge management. An overview of mySAP.com is also included.

A short theoretical introduction gives an overview of the mySAP.com product and the basics for working with processes and knowledge maps. The book explains the wide range of sales and distribution processes from quotation processing to billing. In the customer service section, it describes all the processes from notification processing to order settlement with the help of EnjoySAP. Knowledge maps are used to explain organizational units.

An important feature of mySAP.com is the business scenarios which show a process-oriented view of the mySAP.com components. These are the standard SAP products such as the SAP system (R/3), the Advanced Planner and Optimizer, the Business Information Warehouse, Business-to-Business Procurement, etc. All these separate software solutions are part of the overall concept of mySAP.com. The core functionality, however, will remain the same. The SAP system in particular retains its importance because, as a back-end system, it integrates central processes such as financial accounting, logistics, and human resources. With the new components, these integrated internal processes will be based on cooperation and lead to collaborative process integration across enterprises. The first book of this SAP Process Library deals primarily with structured process analysis within the framework of business engineering and organizational knowledge management. This method can be applied to the complete mySAP.com product. Books 2, 3, and 4 discuss in detail the analysis of the process flows in the mySAP.com SAP back-end system and provide the knowledge required in the form of knowledge maps.

The MindMapping method and the EnjoySAP user interface have been used to enable structured and simple explanations of these SAP processes. Specific ways are also shown for expanding the knowledge gained within the framework of business engineering to achieve process-oriented knowledge management. The authors also include over 200 knowledge maps in the complete Process Library. They combine general documentation, questions about process analysis, tips and tricks, and consultant experience. This enables faster process analysis and more independence for the customer. The books in this series are interconnected but each one can also be useful on its own.

Process analysis is a central task in the implementation of business software. We, the authors, have jointly dealt with this topic in SAP implementation projects during our long experience as SAP consultants. The experience gained led us to rethink the process analysis procedure. New potential in the area of knowledge management directed us to a fresh approach. In particular the reference-based implementation of the SAP system calls for software knowledge, and other knowledge from both external and internal project team members, to be used more productively. Organizational knowledge within a company is considered as an additional production factor today. It is all the more important, therefore, that knowledge management be put to good use during SAP implementation.

This series of books is intended for the following groups:

  • decision makers in different departments
  • project managers
  • process owners
  • management consultants, particularly SAP consultants
  • SAP project teams
  • SAP users
  • students
  • anyone interested in knowing more about the SAP system.

 

Our roles as management consultants and our work with the target groups listed above have shown us again and again that, despite the high level of complexity shown by integrated processes, a simple form of representation must be found. The idea of using the well-known MindMapping method developed by Tony Buzan to describe standard business software inspired us to write this Process Library.

Our aims were to:

  • explain the SAP back-end system in simple terms,
  • provide exclusive consultant expertise for business engineering,
  • show innovative ways to structure knowledge management.

We refer to this comprehensive SAP knowledge, represented using the MindMapping method, as knowledge maps. This is a pragmatic and visual method of presentation and is used to build up a companyms knowledge pool during SAP implementation.

A whole range of information becomes evident when structured in a knowledge map, and we have tried to include our consultant experience in the form of notes (see light bulbs on the branches of the knowledge maps section 4.2.4 of this book). Before we discuss the process area of knowledge maps in the second part of the book, the reader can learn about the theory behind process analysis. In Chapter 5 we describe the procedure behind a process analysis workshop. Every project is different of course, and the process analysis steps described here should be seen as suggestions. We welcome your feedback and invite you to visit us on the internet at www.knowledge-map.de. Each of the process knowledge maps included in the series of books is shown as a LEGO brick. This is another method of simplifying the visual display of business processes. They can be joined together as LEGO chains. In Sophiems World, Jostein Gaarder refers to LEGO as lthe greatest toy in the world.n We decided to use this method for business (re)engineering and have been given permission by LEGO GmbH to use this graphic symbol.

Contents Acknowledgements.
1. Motivation.
Current Issues in the Life Cycle of an R/3 System.
Business Process Re-engineering.
Business Engineering.
Process-oriented Implementation.
Continuous (System) Engineering.
Change Management.
Knowledge Management.
Total Cost of Ownership.
Return on Investment.
Business Processes on the Internet.

What are Knowledge Maps?
Benefits of Using Knowledge Maps.

2. mySAP.com.
EnjoySAP.
What Is mySAP.com and One-step Business?
mySAP.com <241> evolution phases.
mySAP.com <241> components.
mySAP.com: business scenarios.
mySAP.com: workplace.
mySAP.com: marketplace.
mySAP.com: application hosting.

mySAP.com Software Components <241> Relationships.
mySAP.com <241> process modules.
Example of a Business Scenario on the Internet with mySAP.com Marketplace, B2B Procurement, and the SAP Back-end System.

3. Basics.
The MindMapping Method.
What We have in Common with Mozart, Einstein, and Picasso.
Basics of the MindMapping Method.
kFire, thunder, and lightningm.
kLeft, right <241> right, left?m <241> the human brain.
Memorable Pictures.
Structure <241> Basic Rules.
Where to use Mind Maps.

Processes within the R/3 System.
What is a businessprocess?
Enterprise Process Areas.
Scenario Processes.
Process Group.
Process.
Method.

AcceleratedSAP (ASAP).
Introduction.
The Concept behind AcceleratedSAP.

Business Solution Maps.
SAP Industry-oriented Solutions.
Business Solution Map Structure.


4. Knowledge Maps.
LEGO Chain Structure.
Knowledge Map Structure.
Root.
Main Branches.
Side Branches.
Symbols.
Links.

Knowledge Map Types.
Overview Knowledge Map.
Scenario Knowledge Map.
Organizational Knowledge Map.
Business Object Knowledge Map.
Process Knowledge Map.

Knowledge Maps and AcceleratedSAP.
Feasibility Study.
Business Blueprint.
Realization.
Continuous Change.
Knowledge Management.


5. Process Analysis with Knowledge Maps.
Process Analysis Results.
Detailed Process Selection (scoping).
Adaptation and Visualization of Process Chains and Organizational Structures.
Target Concept/Business Blueprint.
Determining Optimization Potential.
Verification using the SAP System at Application Level (optional).
Harmonizing the Terminology of the Department and SAP System.
Identification of knewm Roles (change management).

The Concept behind Process Analysis.
Starting point.
No Re-engineering.
No as-is-analysis.
Target Process Analysis.
Areas of Application.

Workshops.
The Definition of Strategies/Goals.
Workshop on the Definition of an Organization.
Workshop on the Process Analysis with Knowledge Maps.


6. Knowledge Management.
Basics.
The Master Knowledge Map.
From Master Knowledge Map to Task Level Menu.
From Master Knowledge Map to Documentation.
From Master Knowledge Map to Process Integration.
From Master Knowledge Map to Training Material.
From Master Knowledge Map to Process Flow Logic.
From Master Knowledge Map to Authorizations.
From Master Knowledge Map to R/3 Customizing.
From Master Knowledge Map to Testing.
From Master Knowledge Map to Technical Specifications.

Master Knowledge Maps for Uniform Enterprise Documentation.

7. Knowledge Map Database.
Financial Accounting <240> Example: Customer Dunning Notice.
How Is Your Dunning Run Organized?
How do You Intend to Control Your Dunning Runs?
How do You Intend to Handle the Individual Dunning Levels?
What are Your Dunning Notices going to Look Like?
Which Items are to be Considered in the Dunning Run?
Are there any Specific Business Transactions in Your Enterprise that Need to be Considered in the Dunning Procedure?

Revenue and Cost Controlling <240> Example: Sales Planning.
Do You Plan Your Sales and Revenue in the Profitability Analysis (CO-PA)?
Will Your Sales and Revenue Plan be used in Other Functional Areas such as Production?
At what Level do You Plan Specific Values for Sales and Revenue Planning?
Do You Pursue a Top-down or Bottom-up Strategy in Your Sales and Revenue Planning?
Where does Your Planning Data come from (planning data origin)?
For which Planning Horizon(s) do You Plan Sales and Revenue Figures?
Do You need to Maintain Several Parallel Planning Data Sets for one and the same Profitability Segment?

Logistics Planning <240> Example: Demand Management.
Production <240> Example: Production Order Processing.
Procurement <240> Example: Purchase order Processing.
Sales and Distribution <240> Example: Condition Processing.
Customer Service <240> Example: Service Contract.

Authors.
References.
Index.

Caractéristiques techniques

  PAPIER
Éditeur(s) Addison Wesley
Auteur(s) Jürgen Röhricht, Thomas Teufel, Birgit Teufel-Weiss, Peter Willems
Parution 15/08/2000
Nb. de pages 304
Format 17,5 x 24
Couverture Relié
Poids 626g
Intérieur Noir et Blanc
EAN13 9780201715125
ISBN13 978-0-201-71512-5

Avantages Eyrolles.com

Livraison à partir de 0,01 en France métropolitaine
Paiement en ligne SÉCURISÉ
Livraison dans le monde
Retour sous 15 jours
+ d'un million et demi de livres disponibles
satisfait ou remboursé
Satisfait ou remboursé
Paiement sécurisé
modes de paiement
Paiement à l'expédition
partout dans le monde
Livraison partout dans le monde
Service clients sav@commande.eyrolles.com
librairie française
Librairie française depuis 1925
Recevez nos newsletters
Vous serez régulièrement informé(e) de toutes nos actualités.
Inscription