STO Meeting

Solution Manager Adoption

Alba, 14.09.2007
 Agenda

• Solution Manager processes

• EWM Experience

• QM Experience

STO operating – p. 2
 Ferrero
SAP
Solution Manager Scenarios & Ferrero experiences
Next step

SAP

STO operating – p. 3
 Agenda

• Solution Manager processes

• EWM Experience
– EWM Project overview

– SAP Solution manager usage

• Scenario implemented

• Processes supported

• Benefits/Criticalities

– Recommendations

• QM Experience

STO operating – p. 4
 EWM project overview – target architecture

• The objective is to move to an architecture with EWM and ICAM.

AS IS May 2008

SAP R/3 ERP LEO SAP ERP 2005 LEO

SAP EWM
LVS/KMS - Funktionalität
LVS KMS
ICAM
LVS (Teils) - Funktionalität

MFR A MFR B MFR A MFR B

STO operating – p. 5
 EWM project overview - timeline

2006 2007 2008

7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6

•BBP Review 29th Sept.

•Simulation Tool

•Entw. EWM
•Entw. ICAM

•Bug Fixing
•Functional test & Simulation
•Prozessketten Test & Sim.
•Functional Test MFR
•Integration test
•Go-Live
•Go-Live Support

Heute

STO operating – p. 6
 Agenda

• Solution Manager processes

• EWM Experience
– EWM Project overview

– SAP Solution manager usage

• Scenario implemented

• Processes supported

• Benefits/Criticalities

– Recommendations

• QM Experience

STO operating – p. 7
 Implementation Scenario

• SAP solution manager was introduced in the

EWM project since August 2006

STO operating – p. 8
 Processes supported

Project Definition
• RoadMap (R/3 roadmap)
• No standard SAP RoadMap ready for EWM projects
• The project was already in place so there was not a
real need of a roadmap

• The step was mandatory so a dummy

roadmap (R/3 roadmap) was created
• The roadmap has not been used during
the project

Positive Negative
• N/A • No standard content in the SolMan for EWM
implementation projects

STO operating – p. 9
 Processes supported

Project Definition
• Scope (Not used)
• Blueprint already in place
• No standard SAP content ready for EWM
Projects

• Project standards (used)

• Documentation

• System Landscape (used)

• Useful to generate IMG for each system
• From SolMan, in different phases of the
project, it is possible to access the correct
system:
• Customizing  DEV system
• Testing  QA system

Positive Negative
• Once the System Landscape is settled-up it is • No standard content in the SolMan for EWM
possible to access the correct system in the implementation projects
right moment just using the solution manager

STO operating – p. 10
 Processes supported

Business Blue Print

• Objective
• With the BBP it is possible to map all the processes and
process steps down to the transaction level.
• It is possible to add documents at each level of the defined
tree structure.
• In case of SolMan content available there is also stndard
content (BBP, Best Practices, …)

• Our approach
• No standard BBPs were ready in the content of SolMan for
EWM projects
• The structure of the processes and process steps was
defined manually.
• This step is very time consuming. If the standard content
would be available, this step would be really shorter.

Positive
• Once that the structure is finalized this is very
useful to structure project
• Documentation can be added to the structure
• Graphical view of the processes
STO operating – p. 11
Negative
• No standard content in the SolMan for EWM
implementation projects.
• Time consuming to build the structure from the
scratch
• Some Menu were only in German.
 Processes supported

Configuration
• Objective
• All the configuration steps can be mapped in the
SolMan including access to different systems.
• With the standard content the steps are already
available in the SolMan

• Our approach
• No standard configuration was associated to the
structure for EWM projects
• The customizing steps were assigned manually to
the structure.
• Configuration team and process team were working
on the solution manager on daily basis.

Positive Negative
• SolMan is providing a clear view of the project • No standard content in the SolMan for EWM
and the step to build the system. implementation projects.
• Coming back to the system after the • Time consuming if the standard content is not
implementation there is a kind of “Cookbook” available
on how you implemented the project
STO operating – p. 12
 Processes supported

Testing
• Objective • Our approach
• Starting from the defined structure it is • We are actually creating the test plan and
possible to generate the test plan and test packages for the user acceptance test
packages • Next week we will start the user
• It is possible to assign tests to the users acceptance test
and track the results
• It is possible to manage the collaboration
between users and development team
during the test (create internal messages,
log tests, review the testing status)

Positive Negative
• The interaction between users and • The reporting on the results could be improved
development team is very useful • No automatic log of steps within the transaction
• Direct access to the QA system from SolMan during the testing
• In case of errors it is possible to describe the
error in detail (screenshot, attachments, …)
• Testing status available
STO operating – p. 13
 Processes supported

Testing

STO operating – p. 14
 Benefits/Criticalities

Benefits
• The overall project is really structured
• If the project resources are not really skilled they have a starting
point (roadmap, documentation, best practices, processes,
configuration steps, …)
• All the landscape of the project is accessible within the SolMan

Criticalities
• With latest products there is the risk that Solution Manager is not
providing standard content (if the standard content is not available it
is still suggested to work with SolMan)
• If the standard content is not available some activities are really
time consuming

STO operating – p. 15
 Benefits/Criticalities

• Not all the project steps are supported by the Solution Manager

STO operating – p. 16
 Agenda

• Solution Manager processes

• EWM Experience
– EWM Project overview

– SAP Solution manager usage

• Scenario implemented

• Processes supported

• Benefits/Criticalities

– Recommendations

• QM Experience

STO operating – p. 17
 Recommendations

• The use of SolMan, also if the standard content is not available, is

still useful to structure the project.

• Start from the standard processes and tree structures and tailor
them accordingly to your processes

• The use of SolMan in testing activities is really useful

STO operating – p. 18
 Agenda

• Solution Manager processes

• EWM Experience

• QM Experience
– Project overview

– Project administration

– Business Blue Print

STO operating – p. 19
 Project scope: Processes in Quality Control

Supply Chain

Events Inspection Lot Inspection Decision

Quality Messages
Inspection
stock

 Goods movements  Usage decision

 Orders  Samples What happens with
What are the Statistical
 Production  Skip lot the product ?
inspection Data
processing  Shop papers
results ?

Master Data
Complaint Reporting
Management & Statistic
Vendor BW
evaluation

STO operating – p. 20
 Project Timeline

2007 2008
Jan - Mrz Apr - Jun Jul - Sep Okt - Dez Jan - Mrz

Business Process Analysis

Business Blueprint (English)

24.01. Kick-Off
Review phases by SAP
Solution Manager training Realization

Unit Tests
13.06. Steering Committee
Integration Test
Rapid Prototype
Development
Training
today
Cut Over
SAP
Going Live Support

18.06. Blueprint acceptance deadline

STO operating – p. 21
 Agenda

• Solution Manager processes

• EWM Experience

• QM Experience
– Project overview

– Project administration

– Business Blue Print

STO operating – p. 22
 QM2007 – SolMan Project Administration

• The Project QM 2007 is defined as an “Implementation project”

• It includes:
• Design of global Ferrero QM business blue print
• Roll out Specification data base DQO (used on German SAP system)
• Roll out QM Process Ferrero Germany

• Note: QM2007 will be used as template to manage future roll

outs in other countries

STO operating – p. 23
 QM2007 – SolMan Project Administration

• Project Team Members

– List all IT related members which are assigned to specific
work items

STO operating – p. 24
 QM2007 – SolMan Project Administration

• Project Landscape
• The German SAP system
logical component ZSAP
ECC FIP is allocated to the
project

• All relevant customizing

object are grouped in the
Project QM 2007

STO operating – p. 25
 Agenda

• Solution Manager processes

• EWM Experience

• QM Experience
– Project overview

– Project administration

– Business Blue Print

STO operating – p. 26
 QM2007 – SolMan SOLAR01 BBP

• The Business Blue Print is structured according the business

scenarios of the solution manager and covers all relevant QM
processes of Ferrero

STO operating – p. 27
 QM2007 – SolMan SOLAR01 BBP

• Each business scenario is spit in several business processes and those are split
in business steps.
• Each of the steps contains a business blue print documentation in word format

STO operating – p. 28
 QM2007 – SolMan Outlook

Current activities:

• Set up of project schedule for the developing phase

• Assigning of all relevant SAP transaction to the business steps

Future activities

• Documentation of al relevant configuration

• Creation of test scenarios
• Preparation of user documentations

STO operating – p. 29
 Backup

STO operating – p. 30