SAP Solution Manager for Global Roll-Outs - RBE · PDF fileSAP Solution Manager for Global...
Transcript of SAP Solution Manager for Global Roll-Outs - RBE · PDF fileSAP Solution Manager for Global...
SAP Solution Managerfor Global Roll-Outs
Product Management SAP Solution Manager,SAP AG
Globalelements(no changes)
Local elements(full authorization
for changes)
Global Standardization and Harmonization
Harmonizedelements
(certain changes)
Global Roll-out – Challenges
Centralized standard definition• Harmonization of local
requirements• Roll-out to local units
Adapt local requirements• Knowledge transfer to local units• Controlled implementation of
local requirements• Check standard observance
Release management• Adapt standard to changed
requirements• Version management
Enterprise Requirements
Local Systems Requirements finalized in Local Implementation Projects
Local Unit 1 Local Unit 2 Local Unit 3
Global Roll-out – Process in Detail
T1V1Define globaltemplate
1
Global Template(s) becomeReference System
2 Roll out global template
T1V1 T1V1 T1V1
3 Implementtemplate
Local Systems Requirements adapted in Local Implementation Projects
Local Unit 1
T2
T3
Local Unit 2
T3
Local Unit 3
T2
Global Roll-out – Process in Detail (II)
Enterprise Requirements
T2 T3
Global Template(s) becomeReference System
6 Roll out newtemplate version
T1V2 T1V2 T1V2
7 Implement new templateversion via comparison and
adjustment
4 Roll intemplaterequirements
T1V2 5 Create newtemplateversion
Adapting Templates
Defining Global Templates
Implementation at Local Sites
Global Roll-Outs with SAP Solution Manager
Assign Preconfiguration to Template
Template ZBANKTemplate ZBANKS1Accounting
BC SetsTransactions
Test cases
Com
pone
nt s
yste
ms
Ref
eren
ce s
yste
ms
Global Templates – From Definition toShipment
© SAP 2007 / Page 8
Template Project
TemplateZBANK
TemplateZBANK
TemplateZHUMRESTemplate
ZHUMRES
S2MSS
S1Accounting
S3LSO
Create templatesand scenarios
1
Template ZHUMRESTemplate ZHUMRES
Template ZBANKTemplate ZBANK
Assign scenarios totemplate
2 Collecttemplates intotransport
4Release templatesfor:
current SAP SolutionManager system
another SAP SolutionManager system(transport)
3
S1Accounting
S3LSO
S2MSS
Using SAP Solution Manager in a TemplateProject
Project PreparationSetup global project framework
• Create a template project• Create required no of templates (in template project)• Select standard scenarios from the process library (BPR) as starting point for modeling
template-specific business scenarios
VisibilityControls template use
Open for public useClosed for public use, template „under construction“
Global Rollout FunctionalityControls the use of global attributes
Using SAP Solution Manager in a TemplateProject
Business BlueprintDefine global requirements
• Detail standard scenarios to customer-specific process structure• Assign template(s) to the customer-specific process structure• Set global attributes to determine scope of process changes in local roll-out projects• Describe global business and technical requirements
Global Attributes• Changes to scenarios, processes and process steps allowed?• If so, to what extend?
Working with Global Attributes
Documen-tation
IMG structuresand settings
Globalcustomerdevelopments
Organiza-tional structure
Master datadocuments
Countryversions
Localdevelop-ments
Global and inte-grated
processes
Localprocesses
Globalelements(no changes)
Localelements(full authorizationfor changes)
Standard complete elementsStandard partial elements
Harmonized elements(certain changes)
Global attributes:Define scope of changes allowed in local roll-outprojects
Note!• Re-use of existing configuration possible• Translation or process structure can be triggeredusing SAP standard translation tools.
Using SAP Solution Manager in a TemplateProject
Global RealizationPrepare reference templatewith preconfiguration
• Assign related IMG activities, create and assign BC Sets• Assign global customer-specific developments (programs, transactions etc.)• Record sample / master data as CATTs• Create standard test cases (manual test cases, CATTs, eCATTs )
•
Template Collection Process
TemplateCollector
Sets up transport(of copies) with
alltemplate-relevant
content
1 Determineshipment type
2 Selectproject
3 Checkmessage
logs4 Selectlanguages tobe collected
5 Definetransportrequest
6 Checkmessage
logs
Adapting Templates
Defining Global Templates
Implementation at Local Sites
Global Roll-Outs with SAP SolutionManager
Using Solution Manager in a Local Roll-outProject
Project PreparationSetup roll-out project framework
• Create a local roll-out project (type: implementation)• Select one or multiple templates and related scenarios
Business BlueprintScope & enhance global template
• Adapt harmonized and local processes to local-specific requirements• Document local specific requirements of harmonized/local processes
RealizationConfigure global & local requirements
• Apply template-specific customizing (related BC Sets) for global processes• Perform final configuration via IMG activities based on local-specific requirements• Re-use master data samples recorded in global template• Apply global customer developments (such as reports)• Re-use standard test cases to test standard processes and
use as template to create test cases for local-specific requirements
Template vs. Implementation Project
Template Project
Template ZBANKTemplate ZBANKS1Accounting
Template ZHUMRESTemplate ZHUMRESS1LSO
S1MSS
Implementation Project
Template ZBANK’Template ZBANK’S1’Accounting
Template is copiedinto implementationproject
Template content with pre-configuration is basisfor local configuration
Template original ZBANKand copy ZBANK’ aredecoupled
Copytemplate
Copytemplate
Implementation Project: Adding Processes
Template Project
Template ZBANKTemplate ZBANKS1Accounting
Template ZHUMRESTemplate ZHUMRESS3LSO
S2MSS
Implementation Project
Template ZBANK’Template ZBANK’S1’Accounting
P3’Budgeting
P1TPM
P3BudgetingP2
Planning
Business Process Repository:Library of SAP referenceprocesses
Adapting Templates
Defining Global Templates
Implementation at Local Sites
Global Roll-Outs with SAP SolutionManager
Global Roll-out in Different Stages
Versionizing concept to control/track changes in templates
Roll-out Stage 2: Mass roll-outRoll-out Stage 1: Pilots
Templ. ZBANK V1Templ. ZBANK V1S1Accounting
Pilot feedback
Enhancements
Templ. ZBANK V2Templ. ZBANK V2S1Accounting
Template Roll-in, Update, and Roll-Out of NewVersion
Roll in Template RequirementsFeedback from local sites for improving and enhancing templates
Local sites give feedback on:– Template improvements, e.g. customer-specific enhancements to be implemented– Template corrections
Create New Template VersionScope and enhance global template
Implement feedback from local sitesAdapt template to new or updated SAP solutions (new building blocks from BPR) ornew customer-specific processes
– Increment version before next version update.– All versions are automatically archived.
Roll out and adapt template changesCompare and adjust template version
Note!SAP Solution Manager does not offer explicit tool support fortemplate roll-in and update process.
Compare Differences Between TemplateVersions
How do I detectHow do I detectdiscrepanciesdiscrepancies
betweenbetweenthe old and thethe old and thenew template?new template?
Register in Web Shop
Select Product
Update Shopping Basket
Business-to-Consumer
Business Processes
Internet Sales: B2C
Selected Business Scenarios
New template Template in current project
Register in Web Shop
Select Product
Update Shopping Basket
Business-to-Consumer
Create Order
Process Order
Order Processing
Business Processes
Internet Sales: B2C
Selected Business Scenarios
Compare Differences Between TemplateVersions
CompareCompare
Adjust
New template Template in current project
Register in Web Shop
Select Product
Update Shopping Basket
Business-to-Consumer
Create Order
Process Order
Order Processing
Business Processes
Internet Sales: B2C
Selected Business Scenarios
Register in Web Shop
Select Product
Update Shopping Basket
Business-to-Consumer
Business Processes
Internet Sales: B2C
Selected Business Scenarios
Create Order
Process Order
Order ProcessingCompare andCompare andadjust functionalityadjust functionality
provides theprovides thesolution !!!solution !!!
Based on archived template versions
Comparison Against Source (1/2)
Comparison against source (2-way comparison)Starting point for comparison is always the source, such as:
New template content (version)New process library content (BPR)New content from other projects
New, changed or deleted items of the source are indicated in your process structure(yellow warning icon )Initiate comparison via transactionSA_PROJECT_UPGRADE
Note!Comparison does not include changes inside the object,such as changes to the contents of a BC Set or documentation!
Comparison Against Source (2/2)
Comparison against source (2-way comparison)
Comparison results:Changes in the newtemplate version
Specify parametersfor comparison
Comparison and Adjustment (1/3)
Comparison and adjustment (3-way comparison)Compares current process setup against
Source (requires SA_PROJECT_UPGRADE having been operated)Changes in project after take-over of source items, such as documentation ortransactions added in the project after template copy
Initiate compare and adjust via theAdjust to the Original button
Note!Comparison does not include changes inside the objest,such as changes to the contents of a BC Set or documentation!
Comparison and Adjustment (2/3)
Comparison and adjustment (3-way comparison)
New BC Set deliveredwith new template version
Items changed in current project(here: deleted)
Adjust to Original
Comparison and Adjustment (3/3)
Comparison and adjustment (3-way comparison)
Copy content into project andcomplete comparison
Yellow exclamationmark disappears
Summary
• Global standardization and harmonization of scenarios
• Large (multi-national) customers(various SAP R/3 (Enterprise) or mySAP Business Suite inplace)
• Support of process standardization projects• Eased implementation at local sites• Reduced effort for standard adaptation
Task
Target Group
Benefits
Global Roll-Outs – Benefits in Detail
Support of process standardization projects• Methodology• Efficient centralized definition and pre-configuration of global / harmonized elements• Setup of multiple templates in parallel
Eased implementation at local sites• Re-use of customizing on local components• Compliance check• Documentation of standards
Reduced effort for standard adaptation• Version management• Comparison and adjustment of template versions
Deutz AG, Germany
The main driver in choosing theSAP Solution Manager was the
convincing concept of an integratedplatform that manages implementationand operations of mySAP Business Suite,leveraging state-of-the-artimplementation technologies.
Wolfgang Trabant, Project Manager, Methodology
Deutz is an independentand world-wide leadingmanufacturer of dieseland gas engines forvarious machines.
Their project scope in-cludes R/3 4.6C, SAP forAutomotive, SAP CRMand SAP BW for about2,000 expected end-users.
Deutz migrated fromValueSAP to SAPSolution Manager afterthe Business Blueprintphase.
„
© SAP 2007 / Page 31
Copyright 2007 SAP AGAll rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changedwithout prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, orother items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Servicessowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.Alle Rechte vorbehalten.