Foreword |
|
xi | |
Preface |
|
xiii | |
Acknowledgements |
|
xvi | |
|
|
1 | (28) |
|
Current issues in the life cycle of an R/3 system |
|
|
1 | (20) |
|
Business process re-engineering |
|
|
1 | (1) |
|
|
2 | (2) |
|
Process-oriented implementation |
|
|
4 | (2) |
|
Continuous (system) engineering |
|
|
6 | (1) |
|
|
7 | (3) |
|
|
10 | (3) |
|
|
13 | (2) |
|
|
15 | (2) |
|
Business processes on the internet |
|
|
17 | (4) |
|
|
21 | (3) |
|
Benefits of using knowledge maps |
|
|
24 | (5) |
|
|
29 | (40) |
|
|
29 | (4) |
|
What is mySAP.com and one-step business? |
|
|
33 | (3) |
|
mySAP.com -- evolution phases |
|
|
36 | (2) |
|
|
38 | (13) |
|
mySAP.com: business scenarios |
|
|
39 | (2) |
|
|
41 | (3) |
|
|
44 | (4) |
|
mySAP.com: application hosting |
|
|
48 | (3) |
|
mySAP.com software components -- relationships |
|
|
51 | (2) |
|
mySAP.com -- process modules |
|
|
53 | (4) |
|
Example of a business scenario on the internet with mySAP.com marketplace, B2B procurement, and the SAP back-end system |
|
|
57 | (12) |
|
|
69 | (30) |
|
|
69 | (10) |
|
What we have in common with Mozart, Einstein, and Picasso |
|
|
69 | (1) |
|
Basics of the MindMapping method |
|
|
70 | (1) |
|
|
70 | (1) |
|
|
71 | (1) |
|
|
71 | (1) |
|
|
72 | (1) |
|
|
73 | (1) |
|
'Fire, thunder, and lightning' |
|
|
73 | (1) |
|
|
73 | (1) |
|
|
73 | (1) |
|
Structure and function of the memory |
|
|
74 | (1) |
|
'Left, right -- right, left?' -- the human brain |
|
|
74 | (1) |
|
Simplified representation |
|
|
74 | (1) |
|
Memories via neural pathways |
|
|
75 | (1) |
|
|
76 | (1) |
|
|
76 | (1) |
|
|
77 | (1) |
|
|
78 | (1) |
|
|
78 | (1) |
|
|
79 | (1) |
|
Processes within the R/3 system |
|
|
79 | (8) |
|
What is a business process? |
|
|
80 | (1) |
|
|
80 | (1) |
|
|
81 | (2) |
|
|
83 | (1) |
|
|
83 | (2) |
|
|
85 | (2) |
|
|
87 | (9) |
|
|
87 | (7) |
|
The concept behind AcceleratedSAP |
|
|
94 | (2) |
|
|
96 | (3) |
|
SAP industry-oriented solutions |
|
|
96 | (1) |
|
Business solution map structure |
|
|
97 | (2) |
|
|
99 | (18) |
|
|
99 | (2) |
|
|
101 | (6) |
|
|
101 | (1) |
|
|
102 | (2) |
|
|
104 | (1) |
|
|
104 | (3) |
|
|
107 | (1) |
|
|
107 | (5) |
|
|
107 | (1) |
|
|
108 | (1) |
|
Organizational knowledge map |
|
|
109 | (1) |
|
Business object knowledge map |
|
|
110 | (1) |
|
|
111 | (1) |
|
Knowledge maps and AcceleratedSAP |
|
|
112 | (5) |
|
|
112 | (1) |
|
|
113 | (1) |
|
|
114 | (1) |
|
|
114 | (1) |
|
|
115 | (2) |
|
Process analysis with knowledge maps |
|
|
117 | (56) |
|
|
117 | (7) |
|
Detailed process selection (scoping) |
|
|
117 | (2) |
|
Adaptation and visualization of process chains and organizational structures |
|
|
119 | (1) |
|
Target concept/business blueprint |
|
|
119 | (3) |
|
Determining optimization potential |
|
|
122 | (1) |
|
Verification using the SAP system at application level (optional) |
|
|
123 | (1) |
|
Harmonizing the terminology of the department and SAP system |
|
|
123 | (1) |
|
Identification of 'new' roles (change management) |
|
|
124 | (1) |
|
The concept behind process analysis |
|
|
124 | (6) |
|
|
125 | (1) |
|
|
126 | (3) |
|
|
129 | (1) |
|
|
129 | (1) |
|
|
129 | (1) |
|
|
130 | (43) |
|
The definition of strategies/goals |
|
|
130 | (7) |
|
Workshop on the definition of an organization |
|
|
137 | (1) |
|
Determining enterprise views |
|
|
138 | (4) |
|
External and internal reporting requirements |
|
|
142 | (1) |
|
General description of process areas |
|
|
143 | (3) |
|
Organizational definition |
|
|
146 | (8) |
|
Presentation and decisions |
|
|
154 | (1) |
|
Workshop on the process analysis with knowledge maps |
|
|
155 | (2) |
|
Determining the initial situation within the customer enterprise |
|
|
157 | (1) |
|
|
157 | (1) |
|
Identification and selection (general scoping) of SAP scenarios |
|
|
158 | (2) |
|
Preparation of the process analysis workshop by the customer |
|
|
160 | (1) |
|
Process analysis with knowledge maps |
|
|
160 | (10) |
|
|
170 | (3) |
|
|
173 | (22) |
|
|
173 | (4) |
|
|
177 | (11) |
|
From master knowledge map to task level menu |
|
|
179 | (1) |
|
From master knowledge map to documentation |
|
|
180 | (1) |
|
From master knowledge map to process integration |
|
|
181 | (2) |
|
From master knowledge map to training material |
|
|
183 | (1) |
|
From master knowledge map to process flow logic |
|
|
184 | (1) |
|
From master knowledge map to authorizations |
|
|
185 | (1) |
|
From master knowledge map to R/3 customizing |
|
|
186 | (1) |
|
From master knowledge map to testing |
|
|
187 | (1) |
|
From master knowledge map to technical specifications |
|
|
187 | (1) |
|
Master knowledge maps for uniform enterprise documentation |
|
|
188 | (7) |
|
|
195 | (50) |
|
Financial accounting -- example: customer dunning notice |
|
|
195 | (7) |
|
How is your dunning run organized? |
|
|
197 | (1) |
|
How do you intend to control your dunning runs? |
|
|
197 | (2) |
|
How do you intend to handle the individual dunning levels? |
|
|
199 | (1) |
|
What are your dunning notices going to look like? |
|
|
200 | (1) |
|
Which items are to be considered in the dunning run? |
|
|
201 | (1) |
|
Are there any specific business transactions in your enterprise that need to be considered in the dunning procedure? |
|
|
201 | (1) |
|
Revenue and cost controlling - example: sales planning |
|
|
202 | (8) |
|
Do you plan your sales and revenue in the profitability analysis (CO-PA)? |
|
|
202 | (2) |
|
Will your sales and revenue plan be used in other functional areas such as production? |
|
|
204 | (2) |
|
At what level do you plan specific values for sales and revenue planning? |
|
|
206 | (2) |
|
Do you pursue a top-down or bottom-up strategy in your sales and revenue planning? |
|
|
208 | (1) |
|
Where does your planning data come from (planning data origin)? |
|
|
208 | (1) |
|
For which planning horizon(s) do you plan sales and revenue figures? |
|
|
209 | (1) |
|
Do you need to maintain several parallel planning data sets for one and the same profitability segment? |
|
|
209 | (1) |
|
Logistics planning -- example: demand management |
|
|
210 | (6) |
|
Production -- example: production order processing |
|
|
216 | (8) |
|
Procurement -- example: purchase order processing |
|
|
224 | (8) |
|
Sales and distribution -- example: condition processing |
|
|
232 | (5) |
|
Customer service -- example: service contract |
|
|
237 | (8) |
Authors |
|
245 | (2) |
References |
|
247 | (8) |
Index |
|
255 | |