Sap Rollout Template by jfi71777

VIEWS: 345 PAGES: 5

Sap Rollout Template document sample

More Info
									Managing Global Template Rollout




What Is an SAP Global Template?


  - It contains globally defined system structures, data standards, and common processes
based on key integrated scenarios supporting your company’s business
  - Global Template should cover most of the configuration settings
  - Target 80%/20% global vs. local


    -   Local elements will be added during each subsequent implementation rollout
    -   Local language/currency
    -   Legal/regulatory requirements
    -   Local names and descriptions




Whats the SAP methodolgy for Global Implementation?




SAP has its own methodology for Global Template Development and Roll-out.Overview and
details of New Global ASAP Roll-out Roadmap can be downloaded here>>




Also its not a good idea to talk about support on GO-LIVE celebration parties.SAP has recently
come out with support and operations roadmap with "RUN SAP". Details of it can be
downloaded here>>




What goes in global template? 




Criteria for Assessment of Global/Regional/Local Activities




1                         Activity/Work-step is   common                                     all regio
                                                                        , deemed a BEST PRACTICE a
2                                                 BEST PRACTICE
                          Activity/Work-step is deemed as a              and is available to all regio


                                                                                          1/5
Managing Global Template Rollout




3                                               BEST PRACTICE
                        Activity/Work-step is deemed as             , but applies only to a particu
4                       Activity/Work-step is   unique                                         THEN i
                                                                     to a specific facility,country, orfl
(implementation specific)
5                                               THEN flag           LOCAL
                        Answers to 1 through 3 are NO  this sub-process as
(implementation specific)




Usually project team leads decide to the global vs regional configuration.If desicion or
concensus could be reached withing the project team level the issue can vbe escalated to
steering commitee. 




Optimizing Your Environment




Due to sheer complexity of global implementation's landscape its very critical the environment is
optimize and meticulously designed with planning for future.
• Architect the end-state solution and build a detailed plan to get from the starting system to the
end system
• If your landscape has a considerable number of SAP solutions, then one system (box or
LPAR) isn’t realistic for every SAP component. Consider putting several components on a
single box (LPAR).
• Invest in server virtualization technology if you haven’t
• Environment management is a full-time job that requires very skilled architects who
understand SAP NetWeaver® architecture in addition to your company’s legacy systems and
business




This example illustrates the complexity of the environment since each instance has all of the
SAP software components (SAP CRM, ECC, SAP SCM, BI … etc.)
11 environments x 8 components = 88 SAP systems 


 88 systems don’t include application servers, high availability servers, and third-party tool
servers (batch scheduler, tax systems, backup, EDI, etc.)




                                                                                                 2/5
Managing Global Template Rollout




• Be diligent in following processes and procedures for maintaining and building the system
• Building a team consisting of technical, functional, and business representatives dedicated to
change control and environment management is crucial
• Create service-level agreements between the process and technical teams from the start of
the project

Software Development


  - There is no magic ratio for onshore/offshore development —it depends on several factors
  - Type of development objects
  - Interfaces, for example, need more onshore involvement
  - Maturity of offshore team and experience of onshore teams dealing with offshore teams
  - Quality of functional specifications
  - Business knowledge of offshore team
  - Availability of business and process experts offshore
  - Maturity of the SAP product
  - The more mature the SAP product, the more experience the offshore team should have
and vice versa




Typical development cycle with onsite/offsite setup.




Testing Strategy


   - Treat the Global Template as if it’s the most important pilot you have
   - Follow the standard methodology to perform unit, string,integration, and performance
testing as you would on any project
   - Perform as many cycles as you need to perform the integration test on the global template



                                                                                            3/5
Managing Global Template Rollout




   - It will save you a great deal of time when it comes to the pilot rollouts
   - During the pilot rollouts, remember that all defects found that are global need to be fixed in
the global template


    - Apply common standards and reporting metrics to the Global Template and the pilot
rollouts




Scope of Testing




System Testing




System Testing ensures that all of the components within a system are functioning and
interacting properly. It also confirms that all of the components comprise a system which
functions according to the design and are capable of handling rules, transactions, and queries
of the type and volume expected in a production environment.




Integration Testing 




Integration testing verifies proper functioning of each system in relation to one anther (end to
end testing). The focus of integration testing is on finding defects, and therefore, in addition to
testing for proper function under normal circumstances, it will also emphasize responses to bad
data, out-of-bounds input, and other abnormal conditions.




Regression Testing




Regression testing ensures that when the code has changed, previously running functions have
not been affected and problem fixes have actually occurred. These regression tests should be
executed just prior to the deployment of new code to ensure that the release will not create new
or unforeseen problems in the production environment.



                                                                                              4/5
Managing Global Template Rollout




Performance Testing 




Performance testing ensures that the system, as built, can maintain adequate throughput,
satisfactory response, and timely completion of operation under different conditions of stress
and volume. It is also to determine whether, or at what point, extreme conditions are likely to
cause a system failure.




Typical testing cycles mapped to project implementation phases is depicted below.




                                                                                             5/5

								
To top