ACT100

Unit 1 Lesson 1: SAP Activate Overview

Configuration Tools

- Content Lifecycle Management Tools

- Use IMG (Implementation Guide) or SPRO

Unit 1 Lesson 2: 3 Pillars

Methodology

- Prepare, Explore, Realize, Deploy Phase

Guided Configuration

- Configure your solution – allows customers to personalize solution

- View solution scope
- User training & on-boarding
- Test your processes
- Migrate your Data
- Manage your Test Processes

Activate Methodology

- Simple, modular and agile methodology

- Full support for initial deployment and continuous business innovation
- Cloud, onpremise, hybrid deployments

Activate –from SAP Launch and ASAP Methodology( not deleted but not updated)

Differences from old Methods

- Final preparation and go live support is now in one phase called DEPLOY
- 4 Core processes from 5
- No more than 10 key deliverable per phase
- Blueprinting  Fit/Gap Analysis Workshops

Implemntation Steps

1. Prepare
a. Project Setup
b. Roadmap and Approach
c. Initial System incl Best Practices
2. Explore
a. Delta Backlog
b. Delta Design
 c. Solution Fit/Gap
d. Activate Solution & Rapid Prototyping
3. Realize
a. sPrint Exectuion
b. Walkthough
c. E2E Test
d. Operations Setup
4. Deploy
a. GO Live
b. Cut Over
c. Rediness Check

Steps in Sequence

1. Project Setup
2. Roadmap and Approach
3. Initial System inc; Best Practices
4. Active Solution & Rapid Prototyping
5. Solution Fit/Gap
6. Delta Design
7. Delta Backlog
8. Sprint Execution
9. Walkthough
10. E2E Test
11. Operations Setup
12. Readiness Check
13. Cutover
14. Go-Live

Prepare Phase

- PM – setup Project Governance

o Clarifying project team roles and responsibilities
- Provide team with Project Standard
- End of the Phase, Sandbox System based on Best Practices

Explore Phase

- Verify solution which is based on Best practices support the customer needs
- Identify gaps and delta requirements
- List of all requirements captured in backlog is listed at the end of this phase
- List is used to prepare the release and sprint plan before Realize Phase

Realize Phase

- Start building functionality based on backlog list of gaps and delta requirements
- Build Cycles called Sprints
o Build and test Functionality
 - Each sprint, provide frequent checkpoints that the build is meeting the requirements
- Team will go multiple iterations to develop functionality to be ready for production
- Team conducts full end-to-end testing and prepares operations

Deploy Phase

- Business is ready to perform the cutover activities

- Complexity of activities depend on
o Number of users impacted by solution
o Need to conduct multiple cutover simulations as part of preparation for golive
- Project team provides a period of post go-live support (HyperCare Period)
- Then formally closed and solution is now in separate Productive Operations or RUN Phase

Prescriptive and COmprenehsive – provides guided work procedures for project team members,
deliverables for PM and accelerators like how-to documents or templates for all users

Unit 1 Lesson3: Integrate SAP Solutions Manager and SAP Activate

Portfolio to Project

- Drive portfolio of projects and balance business initiatives and Business value
- Strategy to balance and broker to portfolio
- Unified viewpoint across PMO
- Improves data quality
- Provide KPI and roadmaps

Portfolio Management  Project Management

Requirement to Deploy: bnuild business needs and when it need to measured business outcome

- Framework for creating, modifying, or sourcing a service

- Supports agine and traditional
- Enables visibility of quality, utility, schedule and cost of services
- Defines continuous integration and deployment

Demand  Design  Development  Test  Deploy

Request to Fulfill

- Catalog, request and fulfill services

- Helps IT organization transition to service broker model
- Present single catalog with items from multiple supplier catalog
- Efficiency manages subscriptions and total cost of service
- Manages and measures fulfillments across multiple suppliers

Monitor  Incident  Problem  Optimize

Detect to Correct
 - Bring IT service Operation to enhance results
- Visibility end to end
- Shared configuration model

Service Catalogue  Service Request  Service Fulfillment

SAP Activate COnfig Tools

- Configuration library in SAP Solution Manager 7.2

- Configuration object used to define configuration activities such as using classic IMG Object
- Do not use SAP Solution Manager but use Guided Configuration tools available as Manage
Solutions

Unit 2 Lesson 1: Methodology Key Characteristics

Fit/Gap Analysis

- Validate customer requirements against the working system and best practices documentation
- Team captures
o Delta requirements
o Configuration values
o Perceived gaps out of the fit/gap workshops in backlog list

Modular, Scalable, and Agile

- Combination of several principles

- Modules can be scaled up or down
- Agile: many iterations in design, incremental build and frequesnt validation with business to
improve quality of solution being build

Solution Validation Workshop

- Plan project team enablement and walkthough prior to keep these worksops focus on fit and
gaps
- Consultants start with the overall solution before drilling down to process and function detail
- Objective of workship is to challenge changes to standard functionality and determine if there is
aneed for these changes, any changes need to for value or benefit

Delta Solution Design Workshop

- Team creates design for addressing delta requirements and resolving gaps
- Customer business user have key role to design and acceptance of delta solution design

Purpose of Fit/Gap Analysis

- Primary Objective: have updated and approved Scope Baseline to move into Realization Phase
- Validate Pre-activated and preassembled solution in Sandbox
 - SAP Implementation meets customer business needs
- Discover, clarify, negotiate solution design
- Prioritize delta requirements and gaps
- Minimize need for rework during realization

Burndown Chart and Sprint Backlog

Sprint Backlog

- Backlog of all user stories that are in the scope in the sprint backlog
- Helps monitor the progress of work in the sprint
- Reflect even later that some task may have been initially under or overestimated

Burndown Chart

- Reflects estimated outstanding work

Sprint Review

- Demo of all functionality that has been created in the sprint

- Product owner must participate in demo,

Retrospective

- Scrum master looks back at the sprint and identifies what has workled well and activities need
to be improved

Solution Design and SAP Solution Manager

- Each process document will be associated with Business Process Hierarchy just like any SAP
Solution Manager Supported

Unit 2 Lesson 2: Methodology Structure

Quality Gate – stages of project to verify completion of deliverables

Workstream

- Collection of deliverables that show time replationships within a project

- Can span phases and not dependent on phase start and end

Prepare

- Define project governance

- Identify and define the resources, define the roles and responsibilities for project team and
detail the management plans

Explore

- Fit/Gap Analysis on working system with BEST practices content up and running
 - Objective: identify the fit of best practices based solution, caputure delta config and identify
gaps and config values
- All of these are captured by project team backlog
- Backlog items are implemented in system
- Best practices are used as a jump-start for a project

Realize Phase

- Adopts agile approach to iteratively and incrementally build the functionality from backlog
- Covers all build and test activities to prepare a release of functionality into production
- Full integration test and user acceptance

Deploy Phase

- Production environment and confirm readiness to switch into business operrations with new
solution
- Team performs sustainment and hyper-care activities
- Once customer switched over, Project team helps IT and business adopt and use functionality

Additional Phase: Discovery and RUN

Discovery Phase

- Deliverables can be leveraged to build a business case for SAP Based solution
- Incl:
o Overall Innovation Strategy and Roadmap Creation
o Value and Impact Analysis
o Implementation Strategy
o Technical Architecture and Infrastructure

Run

- Represents deliverables and tasks to run and operate on solution

- Reflect supporting system operations and improvements
- Incl
o Application Operations
o Business Processs Minotirng
o ALM Processes
o Optimization
- Methodology Accelerator
o Delivery Suppliment – info on changes to solution, important delivery-relevant aspects
o Solutions Scope – define the package, predefined scope, basis for statement of work
o Software and Delivery Requirements – list of all prerequisites that are needed for
deployment can start, content, tools and project
o WBS, Schedule and Effort Est. – decomposition of the work to be done, project team to
complete project objectives
o Project Governance and Management Plans – plans for managing risks, quality, scope

Explore Phase
 - More product specific content that team leverages in Fit/Gap Analysis
- Includes
o Customer Presentation – covers scope of the solution and service
o Master Data overview – table to understand sample master data shipped in package
o Organizational Data Overview – understand organization model data
o Process Diagram- graphical representation of steps
o SOlman template – container for implementation content for one or more solutions
o Project Backlog template – repository of all delta requirements and gaps to plan
iterative

Realize Phase

- Configuration guides and test scripts

- Team will use agile approach
- Guides for cutover planning
o Performed at last part of realize phase
- Methodology Accelerators
o Configuration Guides- detailed description for configuration
o Test Scripts – procedure for testing the activated system
o Agile Approach Guides – project team guides how to structure project into iterative
sprints
o Cutover plan – template for cutover, provide framework for transition to production

Deploy Phase

- Methodology Accelerators
o Project Schedule – basic project schedule that includes aggregated durations and list of
required skill/roles
o Cutover Plan – sample cutover schedule that provides list of critical cutover steps
o Operations Setup Guide – guide for setup of operational support for solution after
cutover to production
o schedule – aggregated

Unit 2 Lesson 3: SAP Best Practices Content

Solution Package

- cover scope of pre-configured ready to run business processes for S4HANA

Scope Items

- pre-defined business process

- represent best practice implementation choice for customer
- Each scope Item has Accelerators delivering detailed documentation
- Require specific building blocks to be implemented

Building Blocks
 - Set of customizing and master data steps for piece of business content
- Accelerators include configuration content to implement the scope items and project
documentation

Download SAP BEST PRACTICES DOCUMENTATION in SAP Service Marketplace

- Service.sap.com/rds

Unit 2 Lesson 4: Governance, Roles and Responsibilitie

Governance

- Framework for PM and Sponsors can make decisions that satify both stakeholder needs and
expectetions
- Address circumstances when these are not be in alignment
- Ensure communication and messaging fits organization and stakeholder
- PM needs to identify key player who will be a part of the governance and then build
- Key players are specified within project contract or Statement of Work

Level 1: Executive Sponsorship

Level 2: Steering Committee – provide Project team with vision and guidance, also cover the setting of
business priorities and overall strategy for project

Level 3: PMO

- PM and PMO Staff

- Link between stakeholders of project and PMO
- PM plays key role with steering committee

Level 4: Project Team

- Day to day execution of project activities

- Responsible for identification, resolution and communication of issues and risk to PMO
- PMO reports key issues and key risk to Steering committee and Executive Sponsor

Governance – establishes clear roles and responsibilities for each governance level

Product Owner

- Define features of product, decide release date and content

- Accepts or rejects work results
- Features are prioritized based on business needs

Scrum Master is shared among Scrum teams

- One scrum master can support up to 3 teams

- Ensure cooperation within the team
 - Remove barriers and trigger escalation of issues before they become critical

Team

- Cross-functional, seven members est

- Composed of experts across various industries
- Team size is from 5 to 10
- Experts
o Business Process
o Tester
o Authorization
o Technical

Unit 2 Lesson 5: Differences and Similarities between ASAP, SAP Launch and SAP Activate

Main changes

- 4 phases project lifecycle

- Agile project delivery
- Use of SAP Best Practices
- Fit/Gap workshops (Replaces Blueprinting)
- 10 or less key deliverables per phase, easier key guides and accelerators

System Conversion and Landscape Transformation

- Detailed roadmap for transition to SAP S4HANA

- Methodology content can be seen in Roadmap Viewer
o New, not covered in Launch and ASAP

Unit 3 Lesson 1: Access SAP Activate via SAP Jam

SAP JAM

- Co-operation environment for people to work and talk about the methodology
- Understanding and application to their project

Unit 3 Lesson 2: SAP Roadmap Viewer

RoadmapViewer

- Allows customer and partners to view Solution Manager Roadmaps Online

- Runs on SAP HANA Cloud Platform
- Shows S4HANA roadmaps and Activate Methodology roadmaps
- Roadmaps 3 Level
o Phases
o Deliverables
o Tasks
- Tool that gives access to full work breakdown structure of particular project
Unit 3 Lesson 3: SAP Activate via. SAP Solution Manager

Unit 4 Lesson 1: Journey Overview

Project Management – across all phases

Customer Team Enablement – Prepare Phase and early stages of Realize Phase

Design and Configuration – start of explore, thru Fit To Standard where we determine configuration
values

Integration – integrating solutions outside cloud solution with cloud solution.

Testing – in Realize Phase, for User unit testing, check functionality

System and Data Migration – start to prepare data in Explore phase during analysis of Data Quality and
handling activities

Transition to Operation – continue at end of project, toward end Explore Phase

Unit 4 Lesson 2: Prepare Phase

- Initial planning and preparation activities to get project started

- Includes
o Project goals, high-level scope
o Quantify business value objectives
o Secure executive sponsorship
o Est. Project standards and organization and governance
o Define roles and responsibilities
o Est. project management, tracking and reporting mechanisms for value delivery
o Customer team self-enablement
o Prepare the project environment
o Project team orientation

Sales to Delivery Handover

- Ensure smooth transition from sales process to delivery process

- Includes review of services contract and meeting with sales team to discuss project
- Deliverable: Sales to Delivery Management
- Procedure ( Summary of Tasks)
o Customer requirements and solution demonstrated
o Project Business Drivers, goals, objectives and successes metrics
o Clarify all concerns that customer had during sales system

Project Initiation
 - Prepare project management aspect of project
- Project Charter
- Stakeholder Identification
- Assigning resources
- Creating Project schedule
- Central Document respository is setup and access SAP Marketplace
- Deliverables:
o Project Charter
o Project Management Plan, Inc. Governance
o Project Schedule
o Project Budget
- Procedure ( Summary of task)
o Contact made with customer in order to explain implementation methodology
o Verify recipient of cloud system
o Idenfity Stakeholder and create Project Charter
o Create Project Schedule with activities, tasks
o Setup Document Repository
 SAP SOL MAN, JAM, Customer Sys
o Verify all parties are agreement with project plan
- Acceletators:
o WBS
o WBS Stream View
o Project Management Plan
o Risk Management
o Project Logistics Template
o Project Setup Checklist
o Issues Tracking Template
o Change Request Tracking Template

Customer Team Self-Enablement

- Provide customer project team with enablement materials prior to start of Project
- Deliverable: Customer Team Self-Enablement
- Procedure:
o Team provides training content and interactive learning
o Provides team members a self-paced path for acquiring skills and knowledge needed to
complete project successfully
- Accelerators:
o Training and Certification Ship
o S4HANA Learning Room
o SAP Activate Learning Room

Cloud System Provisioning

- Confirm infrastructure,
- Receive the initial system and provided project team with access
 - Deliverable: Starter System Provisioning
- Procedure:
o Assess if SAP cloud can meet requirements
o Verify if customer has access to cloud sys with URL, Login , password
o Enable customer on user creation
- Accelerators:
o Solution Specific Accelerators in JAM Site

Project Kickoff

- Kickoff project
- Ensure all needed information is shared
- Resources for successful project execution
- Deliverable: Kickoff Workshop
- Procedure:
o Prepare consolidating relevant project information into kick-off presentation template
- Accelerators:
o Project Kickoff Template
o Solution Specific Acceletors

Phase Closure

- Closure of phase and sign-off deliverable

- Ensure all deliverables from this phase are complete and accurate
- Idenfiy lessons learned during phase
- Caputure customer feedback and potential customer references
- Deliverable: Phase Closure
- Procedure:
o Q-Gate Review and check completion of phase deliverables
o Obtain customer Signoff
- Accelerators:
o Q-Gate Scorecarrd template
o Phase Signoff Template

Unit 4 Lesson 3: Explore Phase

- Team reviews solution scenarios to verify business requirements

- Configuration values are identified and added to sprint backlog list for Realize Phase
- Sprint Backlog List
o Preconfigured solutions with customer specific scope
- Activities:
o Solution validation workshops
o Confirm solution fit to required business processes
o Continue customer team enablement
o Indentify master data and organizational setup requirements
o Indentify and define configuration values
o Review data requirements and begin data cleansing
 o Prepare for integration to legacy system
- Flow:
o Fit to Standard Analysis  Configuration Values  Data Preparation  Release and
Sprint Plan

Project Execution, Monitoring, and Controlling

- Execute, monitor, and control project work as defined in Project Management Plan
- Deliverables:
o Project Management Plan
o Risk & Issue Logs
o Q-Gate Scorecard
- Procedure:
o Monitor and control project activities
o Assure scheduled project tasks are progressing as planned
o Assure resources are assigned to all scheduled project task
o Manage issues, action items and risks
o Manage changes to project scope, timeline, cost
o Communicate status and progress to takeholders
o Conduct quality Gate review
- For Agile procedure:
o Schedule and Conduct SCRUM Meeting
o Schedule Sprint Demonstration
o Organize Sprint Retrospective
- Accelerators
o Agile Scrum Meeting Guidelines
o Agile Change Request Templates
o Project Quality Gate Scorecard
o Status Template
o Open Issues Template

Customer Team Enablement

- Supplement the user self-enablement with discussion and process review specific to areas that
customer requires additional expertise
- Deliverable: Level 2 Enablement
- Procedure:
o Schedule functional topic workshops with customer on topics require additional
expertise
o Schedule workshop based on feedback from customer
o Lead the customer through business processes best practices, configuration variables
and interdependencies
o Follow-up customer to assure customer understands the functionality
- Accelerators:
o SAP HELP Ducmentation
o Learning Room
 o Solution Specific Accelerators in JAM Site

Fit to Standard Analysis

- Purpose is for deliverable to review predefined scenarios and processes for fit to the customers
business process
- Review uses iterative approach to assure that integrated dependencies are addressed
- Configuration taks are determined and entered into SPRINT BACKLOG
- Deliverable: Fit to Standard Analysis
- Procedure:
o Consultants demo to customer business scenarios highlighting areas that are
configurable or require customer input
o Customer runs business scenario outside workshop and check it at own speed for
additional understanding
o Customer evaluates the fit of suctomer;s business process and provides feedback on
both fit and configuration tasks
o Consultants resolves issues, solutions to issues are limited to scope, solutions outside
solution are managed using change orders
o Consultants add configuration tasks and gaps to the sprint backlog
- Accelerators:
o Solution Validation Overview
o Solution Validation Workshop
o Sprint Backlog Template
o Solution Validation Workshop
o Solution Specific Accelerators n JAM site
- Fit to Standard: Workshop Approach
o Explain Process using Best Practices
o Config system and delivered data to DEMO best practices, Highlight areas likely require
configuration decisions
o Explain how system meets or can meet specific customer requirements, basic processes
are discussed first as to gain understanding, complex processes are built from basic
o Idenfity gaps and catalog it on product backlog and further analysis and closure
o Determines and documents configuration values required. Customer is responsible for
providing value lists
o Consultant provides process flows, test scripts and users so that customer can execute
scenarios on their own, create sample customer data to enhance learning
- Pre-Configured w/ Best Practices  Identify Gaps  Catalog  Assign Importance &
Complexity
o Prioritization, Detailed analysis and Delta design for closing gaps
o May require modification of scope and timeline of implementation

Configuration Definition

- Define solution configuration values based on standard business scenario reviews and add them
to product backlog
 - Deliverable:
o Configuration Definition
o User Access & Security
- Procedure:
o Formal blueprint is not required unless stated,
o Caputure Design and Requirements of organizational structure, chart of accounts, all
Pre-activation configurations must be defined in order to activate Q-System
o Provide technical and integration design of solution to be implemented
o Accounting for all decisions made during Solution Validation
- Accelerators:
o Product/Sprint Backlog Template
o Solution Specific Accelerators in JAM Site

Solution Extension Preparation

- Identify and define required solution extension within extension framework of solution within
service contract
- Deliverable: Extension Specifications
- Procedure:
o Customer specific field extensions are captured and catalogued
o Complete field definitions are created to facilitate configuration and future support
- Accelerators:
o Extension field Specification
o Solution Specific Accelerators in JAM Site

Integration Prerequisites Confirmation

- Assurance that systems being integrated are compativle with cloud system, setup network
security, and develop specifications for extension fields
- Deliverables:
o Network Connectivity Checks
o Security Checks
o Adaptation Specifications
- Procedure:
o Apply integration system prerequisites in test environment so that it is compatible with
cloud system
 Include notes, support, patches, network security, and add-ins
o Confirm integration requirements in test environment
o Setup network connectivity
o Confirm fields to be integrated
 Customer needs to provide data mapping and value lists along specification for
adaptations
- Accelerators:
o Solution Specific Accelerators in JAM Site

Data Load Preparation

 - Develop plans and procedure to support loading of data into new system
- Data is analyzed for obsolence and cleansing is performed
- Deliveables:
o Data Migration Scope and Plan
o Specification for migrationprograms
- Procedures:
o Determine:
 Data requirements based on scenarios
 Data sources, extraction methods and loading methods
o Review data load templates and data mapping
o Analyze data to be migrated and perform data cleansing
o Design the programs or reports required to extract the data
o Develop the overall plan including sequence, expected data volumes and expected load
times
- Accelerators
o Data Load Planning Template
o Data Definition, Design, and Migration Plan

Phase Closure

- Signoff deliverable
- All required deliverables are complete and accureate and close any outstanding issues
- Idenfiy lessons learned during phase
- Deliverable:
o Q-Gate Scorecard
o Sign-Off Documentation
- Procedure
o Conduct Project Quality Gate to assure that phase deliverables
o Obtain Customer Sign-off for phase Completion
- Accelerators:
o Quality Gate Concept
o Solution Specific Accelerators in JAM Site

Unit 4 Lesson 4: Realize Phase

- Team uses series of iterations to incrementally build and test a complete business and system
environment
- Based on business scenarios and process requirements
- Activities:
o Configure system incrementally build in time-boxed iterations and sprint backlog list
o Enablement on key concepts and system administration
o Walk though solution processes with stakeholders
o Execute data migration
o Integrate to legacy systems as required
o Overall end to end testing of the solution
o Create cutover plan
 o Prepare change management and end user training

Design and Configuration

- Majority of solution build work will be

o COnfigruation of values
o Adjusting and expanding forms
o Extending standard reports
o Delivering solution walkthrough
o Integration setup
o End to end testing
- At the end we have provisioning system
- Plan and schedule data load and load validation activities
- Solution are being established and training materials prepared and initial end-user training
delivered.

Project Execution, Monitoring and Controlling

- Execute, monitor and control project work defined in PMP

- Procedure:
o Monitor and control project activities to assure that all scheduled project tasks and
deliverables are progressing as planned
o Assure resources are alighed
o Manage issues, action items, and risks
o Manage changes to project scope, timeline costs
o Communicate status and progress to project stakeholders
o Conduct Quality Gate Review
- Agiile Implementations
o Schedule and conduct SCRUM meetings
o Schedule Sprint Demonstrations
o Organize the Sprint Retrospective
- Deliverable:
o Project Management Plan
o Risk and Issue Logs
o Q-Gate Scorecard (Update)
- Accelerators:
o Agile Scrum Meeting Guidelines
o Agile and Change Request Templates
o Project Quality Gate Scorecard
o Status Template
o Open Issues Template

Customer Team Enablement (Level 2 )

- Complete knowledge transfer thru support of configuration and testing purposes

 - Deliverable: Knowledge Transfer
- Procedure:
o support configuration process with instruction and explanation of configuration process
o testing with knowledge transfer on resolutions to defects
- Accelerators:
o SAP HELP Documentation
o Solutoon Specific Documentation in JAM Sites

System Configuration and Solution Walkthough

- Configure the solution

- Process is iterative process to assure business needs are met
- When configured, solution is demonstrated to stakeholder for feedback
- Procedure:
o Configure system using values determined during explore phase
o Modify forms as required
o Setup reports
o Setup sample data to validate and demonistrate process
o Data should be coordinated with outher team members to allow for reuse in other
scenarios
o Demonstrate to customer key users the scenarios and receive confirmation that
processes meet business needs
o Adjust processes as necessary to close gaps
- Deliverable
o Solution Configuration
o Solution Documentation
o Forms Enablement
o Reports
o Access/ Authorization
o Solution Walkthrough
- Accelerators:
o Guided Configuration
o Solution Specific Acclerators in SAP JAM

Solution Extension Development and Deploymnt

- Develop solutoons extension identified in explore phase and included in scope of the project
- Deliverable:
o Solution Extension Development
o Solution Extension Deployment on Production
- Procedure:
o Adapt the user screen per specification
o Demo enhanced screen during walk-though of standard business processes and receive
feedback
- Accelerator:
o Soluton Specific Accelerators
Key Users to easiely adjust business configuration

- View and adapt configuration settings of solution

- Guided configuration along deployment phase of the project
- Includes only those configuration activities required for preselected scope
- Suitable for adjustments of basic settings such as organizational structure and master data
settings
- Does typically not change the business process flow

Need for the team to undertake solution walkthroughs in realize Phase, important to project team to
engage the business users and show them solution so we can iterate the build and validation of the
solution

Integration Setup in the Test System

- Setup the integration in quality assurance system so that production like data can be loaded for
testing
- Upon completion of testing, integration will be setup in production environment
- Deliverables:
o Integration Setup in Test / QSystem
o Integration Setup in Production System
- Procedure:
o Setup network security and connectivity
o Configure integration setup on
 Cloud system
 System to be integrated
o Create Integration mapping and transformation
o Execute initial integrated data load into the production system
o Repeat setup process in production environment
- Accelerators:
o Solution Specific Addcelerators in JAM Site

Solution Test Preparation & Execution

- Simulate business activity in order to validate the configured solution and related business
processes will satify customers
- Deliverables:
o Solution Test Preparation
o Test Plans
o Solution Test Execution Report
- Procedure
o Update delivery test plans
o Create additionaltest plans for new modules not covered before
o Assign resources and schedule test plans
o Execute test scenarios as defined in test plan and document the results
 o Log all issues
o Resolve identified issue and retest end to end scenario
- Accelerators:
o Testing Scenario Template
o Agile Testing Approach
o Solution Specific Accelerators

Data Preperation and Load

- Create data load files to load the data into cloud solution
- Customer is responsible for these tasks unless data migration service is implemented
- Deliverable:
o Data Load Test Results
o Defect Resolution
o Data Quality Assessment
- Procedure
o Develop and test data extraction programs and reports to assure proper information is
extracted, transformed and formatted to load templates
o Extract data into load templates, data validated for adherence to requirements
o Run both authomated and manual load process
 Data load plan and resolve defects
o Load times are recorded in load plan
o Verify data quality and consistency
- Accelerator
o Data load planning template
o Soluton Specific Accelerators in JAM Site

End User Training Plan and Execution

- Develop high level training plan that provides recommended approach and corresponding
activities to prepare enduser for new system
- Deliverables:
o EU Training Plan
o EU Training
o Change Management Plan
o Value Audits
- Procedure:
o Conduct Learning Needs Analysis
o Complete EU training plans
o Develop training scenario and material
o Start EU Training
o Prepare and work to Change Management Plan
o \Idenfiy Value Points, baseline and potential
- Accelertators
o SAP HELP Documentation
o Learning Room
Establish Support Plan

- Setup the processes and resources that will be involved with supporting users once system is
live
- Deliverables:
o Tehcnical Operations and Handover Plan
- Procedure:
o Assign resource leads that will be responsible for answering questions and
troubleshooting problems
o Assign technical lead responsible for communicating with SAP
 Responsible for gathering details on technical isusues
o Expand current help desk to include new solutions
- Accekerators
o Soluton Specific Accelerators

Cutover and Transition Plan

- Define document strategy, scope, times for moving from as-is solution to the to-be solution
- Deliverables:
o Cut-over plan
o Prod System Setup
- Procedure:
o Team assesses level the organization is prepared for transition, this includes proper
governance of master data quality is defined
o Once preparation is done, team will deliver preliminary cutover plan task to document
strategy, scope, and timelines
o Document activities such as transfer of data from legacy system to SAP software, setting
up and verifying interface connections, importing transports and all manual
configuration
o Preliminary plan will be reviewed with customer to validate plan for completeness,
dependecneis, timing, and other contraints at the end of the review, the project team
will have understanding of necessary adjustments to preliminary cutover plan

Unit 4 Lesson 5: Deploy Phase

- Team prepares system for production release

- Switches to production environment and conducts sustainment activities post go-live
- Activities:
o Execute cutover plan
o Transition business operations to new system
o Transfer from implementation support to production support
o Close the project

Project Execution, Monitoring, and Controlling

- Check old notes

Production Setup – Switch to Production

 - execute tasks as per the cutover schedule to prepare production system for operational use
- includes loading all data and verifying its accuracy and completeness
- begin entering live transactions to cloud production tenant
- Deliverables:
o Customer Solution Live in the Cloud
o Data Migration Load Validated
o Solution Accepted (SignOff)
- Procedure:
o Request production system
o Execute loading of configuration into production environment per cutover plan
o Load data into production environment
o Setup access production system to end users
o Verify data load complete and verify quality
o Final approval from stakeholders to beigin productive use of system
o Activate users in system
- Accelerators
o Cutover Plan Documents
o Solution Specific Accelerators

Handover to Support

- Transfer fro project support environment to a production support environment

- Procedure:
o Conduct support services meeting to introduce customer to support manager
 Support takes ownership of support and monitoring productive cloud system
o Set live system indicator in production system, allows support idenfigy the system as
productive system
- Deliverable:
o Solution handed over to Operations
- Accelerators:
o Solution Specific Accelerator

Project Close and Sign-off Project Deliverables

- Closure and signoff deliverables

- Ensure all deliverables are complete and accurate, and close outstanding issues
- Identify lessons learned to prepare formal phase closure
- Procedure:
o Conduct product quality gate to assure deliverables
o Review issues and risk to determine additional focus
- Deliverables:
o Q_Gate scorecard
o Sign-off Documentation
 - Accelerators:
o Quality Gate Concept
o Q-Gate scorecard template
o Quality Gate Checklist
o Phase Signoff Template
o Solution Specific Accelerators in JAM site

Unit 4 Lesson 6: Unit Summary and Additional Information

Flow:

Experience Trial  Fit to Standard Analysis  Scope and Configure  Migrate, Integate, Extent, Test 
On-board and Deplloy  Operate, Monitor, Support

Fig 201 p177

NOTE: UNIT 4 is for Cloud

Unit 5 Lesson 1: Journey Overview

Explore Phase, we have Rapid Prototyping

- Set of activities performed to create Baseline System

- Ready for use in Fit/Gap Analysis
o Solution Demo and Leads on delta design
o Delta requirements are identified
- Backlog list at the end of Explore Phase with release and sprint plan

Sandbox

- Have best practices as jumpstart

- We can use Cloud Applicance Library where fully activated SAP S4 HANA can be stood up and
recommended to use this to jumpstart instead of having time and effort to setup Sandbox
environment from scratch

Fit/Gap Analysis in Explore Phase,

- Idenfity scope items

- Capabilities
- Best practices to be activated in sandbox system

Transport Management System Capabilities

- Move to QA and PRD environment

Sandbox is used in Prepare and Explore Phase, which needs to be ready as baseline system for Fit/Gap
Analysis

Realize Development Environment to build solution in Sprint Executions and QA Environemnt is used in
testing activites
Unit 5 Lesson 2: Prepare Phase

Transition Planning Workshop for New Implementation

- Planning workshop reveal preparation activity

Project Start

- All activities to enable project team to successfully and efficiently execute project
- ProcedureL
o Team prepare standard and control monitor
o Rules and standards for project are defined
- Deliverable:
o Init
o Planning
o Team Enablement
o Organizational Change Management
o Q1: Prepare to Explore

Transition Planning

- Plan and prepare all transition in all major areas

- Deliverable:
o Transition Planning
- Procedure:
o Define Scope
o Define cutover approach
o Operational Readiness
o Define Technical Architecture
o Define Data Migration Architecture
o Define Analytics Architecture

Transition Preparation

- All follow up activities on plans for transition

- Deliverable:
o Transition Preparation
- Procedure:
o Analyze preparation
o Plan in detail
o Execute items on plan

Best Practices are already loaded into system compared to SAP Business Suite

Unit 5 Lesson 3: Explore Phase

- Validate the solution delivered to customer based on standard processes documentation

- Fit/Gap Analysis configuration for each business priority is determined and designs are reviewed
Sandbox based on best practices

- Fully activated and ready to go

- The best practices content may not always fit in
- Create customer-specific Baseline Build
o Adjust sandbox system and building character features we want to show in Fit/Gap
Analysis
- Instead of investing in prototyping a functional solution, prefer to use workshop presentation
materials with hot standard screen build for customers with their data

Solution Validation (Workshop A)

- Walkthough
- Show process flow and explain to customer how system works out of the box
- Walkthrough any additional functionality or visualization of baseline build in sandbox
- Capture requirements and form user stories in a call backlog

Backlog Prioritization

Design for Gaps and Deltas (Workshop B)

Documentation

- We should document based on decision rationale

- Why certain things are configured in a certain way and explain that level of detail
- Not a series of screenshots of content as it can be seen using a link to the configuration content
- If Solution Documentation is used and maintained, then it can be regarded as asset.

Activate Solution

- Ensure functional system is available to be used for demonistration and visualization in fit gap
session
- Overall implementation stratefy is foundation to start with pre-configed solution
- Deliverable:
o Activate Solution/ Sandbox
- Procedure:
o Reconfirm scope for activation
o Activation of best practices and test-activated processes

Design for Gaps and Deltas

- How business processes are evaluated for their fit against SAP Best Practices and how potential
gaps are managed
 - Deliverable:
o Fit-Gap Delta Design
 Introduction
 Finalize System Setup
 Solution Validation
 Gap Idenfication
 Delta Scope
 Gap Validation
 Delta Design
 Verify and Accept

Analytics Design

- Discussions and analysis with the cusotomer

- Procedure:
o Assess Analyics Infrastructure
o Understand customers long term and short term
o Analyze Customers most important business cases, data management
o Build decision tree/matrix to support roadmap
o Define target analytics solution
o Create project plan for implementation of target landscape

Legacy Data Migration Design and Plan-

- Describe outcomes of data migration workshop and preparation of data to be used in realize
Phase
- Procedure:
o Prepare and conduct data migration workshop
o Data Audit
o Prepare and Present data Migration scope and requirements Document
o Data Migration Apprach and strategy
o Test Data Management
o Define Specification for Data Migration
- Deliverable:
o Data Migration Design

Unit 5 Lesson 4: Realize Phase

- Build up solution
- Individual releases and sprint plans and requirements captured in backlog
- Steps:
o Sprint Execution  Walktough  E2E Test  Operations Setup
- Building Sprints: Iterative Approach

Agile Project Day to Day

 - Product Owner User Stories  Product Backlog  Sprint Planning Meeting  Scrumboard 
Daily Scrum  Sprint Backlog & Burndown  Review  Retrospective

Configuration of On-Premise Solution will be using traditional Configuration Tasks of Implementation

Guide (IMG)

- Done in IMG or via SAP Solution Manager (SolMan)

- Similar to SAP Business Suite
o Enter the configuration activity thru SAP SolMan
- Document for Solution Configuration
o Capture why changes are made
o Simply capture the configuration links in SAP Solution Manager
o Capture what has changed and why

Configurations and Product Enhancements

- Define and document strategy, scope, timelines for moving from as-is solution to the to-be
solution
- Hypercare period after go live
- Deliverables:
o Configuration:
 Introduction
 Core Finance
 Enhanced Request to Service
 Streamlined Procure to Pay
 Optimized Order to Cash
 Core human Resources
 Central Finance Imp
o Product enhancements

Data Aging Configurations

- New way of managing large amounts of data

- Deliverable is continuously to manage and enable data aging process
- Procedure
o Cleanup of Archive Data
o Configuration is different for Design Time and Runtime data
 Configure Data Aging (Design Time)
 Test Execution of Data Aging ( Runtime)
- Deliverable:
o Cleanup/Archive
o Data Aging Configuration

Analytics Configuration

- Prupose is to configure HANA Based Analytics Solution

- Procedure:
o Basis configuration BOBJ Cloud
 o Source system connect to one HANA DB
o Import models from S4HANA to HANADB or BW on HANA
- Deliverable:
o Analytic Configuration

Cutover Preparations

- How final cutover is prepared and tested

- Procedure:
o Production System Setup
o Create Cutover
- Deliverable:
o Cutover Preparation

Unit 5 Lesson 5: Deploy Phase

- Similar activities with implementation in cloud

End-User Training Delivery

- Ensure end-user training is successfully delivered to support readiness for adoption of the
solution
- Deliverables:
o End-User Training Delivery
- Procedure:
o Refine Training Execution Plan
o Validate and Adapt End User training material developed
o Deliver End- User Training with Training schedule
o Collect training evaluation
o Perform people readiness assessment to check how prepared people in organization
with regard to identified changes

Technical And System Testing

- Present the findings and recommendation from the results of technical tests such as
o Disaster Recovry Tests
o Backup and Restore Tests
- Procedure:
o Review and update System Test Plan created in realize Phase
o Prepare and execute technical and system tests
o Present findings and recommendation from the results of technical tests such as
 Disaster recovery test
 Backup and restore
 Other technical or basis related tests
o Signoff in otder to exit system testing
- Deliverable:
o Approved Technical System Tests
 - By finalizing technical System Tests, the tests can be done with customer as part of Operation
Acceptance Testing
- Testing includes

Tests should be executed in productionenvironment will be in Test Stratefy

- Responsibilities for testing is Test Manager

- Capture test requirements and ensure ownership of activities accepted

System Performance Testing

- Done in Deploy Phase

- Combined with User Acceptance Testing

Call to Arms Meeting

- Run day plan and actions to clear Blockers

- Celebrate Success in project
- Success related quoted for Positive thinking

Dress Rehersal

- Preparation for Go-Live of Transition project, execute a end-to-end dress rehersal of cutover
procedures
- Rehersals should be executed about two to four weeks prior to Go-Live
- All changes intented to be included in cutover should be available to dress rehersal
- Include changes from results of testing cycles
- Procedure:
o Review system test plan
o Prepare and Execute Technical and system tests
o Present findings and recommendations from results of technical tests
- Deliverables
o Dress Rehersal

Production Cutover

- Goal is to cut over production to SAP S4HANA

- Procedure:
o Execute cutover following the tasks defined in cutover plan
o Document the actual duration of each step to support future projects
o Capture any variances to the plan along with decision maker who approved change
o Cutover manager should proactively notify task owners of upcoming tasks
o Regularly communicate status to stakeholders
o After data is loaded, testing and data reconciliation must be completed
o Obtain System Sign-off
- Deliverables:
o Production Cutover
Handover to Support Organization

- Prupose is ensure that all open tasks are handed over to support Organization
- Procedure:
o Workload Analysis
o Health Check and Scalability Analysis
o Sizing Verification
o Resolve and Close Open Issues
o Handover Operations Responsibility
- Deliverable:
o Hypercare Support – support post go-live
o Handover to Support Organization

Project Closing

- Deliverable is ensure that all open tasks are handed over to support Organization
- Procedure:
o Finalize Project Closeout Report
o Obtain Sign-off for Project Closure
- Deliverable:
o Closing

Unit 5 Lesson 6: Unit Summary & Additional Information

SAP Activate and ASAP 8 Implementation Methodologies

Difference:

- One less core phase

- Fewer and different work streams
- JAM site hold Activate methodology
- Variants for SAP Activate for On-Premise and Public Cloud
- SAP provides S4HANA Solution configuration methodology content in WBS
- Activate defaults in Agile approach with BACKLOG of user stories
- References to Assemble to Order (A2O) and Rapid Deployment Solution is replaced with SAP
Best Practies

Same:

- Agile or Waterfall Project Approach

- Testing Activities not changed,
o UAT
o Performance Test

Objectives

- Agile option in ASAP but in Activate it is made default to use Agile

- Not every project may use Scrum
- Mindset emphasize the need for shorter cycles applying their mindset in building
In Waterfall Approach

- Prepare: projects do not have a sandbox or demo environment

- Explore: No fit/Gap Workshop and delta’s and gap’s to the baseline solution are captured, no
user stories and no backlog of requirements
- Realize: Configuation starts with general setting  Incrememntal buiold of the processes in
solution
o No planning and delivery of iterative and agile sprints
- Deploy: No Differences
- Waterfall projects are start from scratch compared to Agile where traditional process
decomposition and detailed design

Recommendation:

- Use best practices to jumpstart projects

- Use RDS and Defined Consulting Solutions

Implementation of S4HANA

- No requirement to assemble and load SAP Best Practices since it already contains the best
practice

Unit 6 SYSTEM CONERSION FOR S4HANA

Unit 6 Lesson 1: Journey Overview

From OLD SAP ECC to S4HANA

- We are not only transitioning but utilizing the capabilities of S4HANA

- There will be adjustments in tables and configuration adjustments
- Big area to address is custom code
- Assessment and clean up on existing custom code and some adjustments
- Data Volume Strategy
o Data Clean Up
o Data Archiving
o Data aging Configuration
o Good strategy in managing data volumes between in-memory and storage
o Invludes data analysis and volume
 Transactional data
 Master data

Conversion uses SAP Update Manager ( SUM) with Database Migration Option (DMO)

Customers who want to Move to S4HANA has the benefit of

- Migrations without reimplementation

- No Disruptions for existing business process
 - Re-evaluation of customization and existing process flow

Unit 6 Lesson 2: Prepare Phase

Moving existing environment into new environment with minimum interruption

- Analysis for custom code

- Operational readiness and technical architecture
- All are considered in transition planning workshops and transition planning activities

Project Start

- Enable project team to successfully and efficiently execute project

- Deliverables:
o Init
o Planning
o Team Enablement
o Organizational Change Management
o Q1: Prepare to Explore
- Procedure:
o Preparing standards, controls, monitors t execute project
o Team members are enabled in roles
o Rule and standards in project defined
o Phase completed with Q-Gate

Transition Preparation

- Follow up on the plans for the transition

- Deliverables:
o Transition Preparation
- Procedure:
o Analyze preparation items
o Plan in detail all items
o Execute according to plan

Unit 6 Lesson 3: Explore Phase

Activities in Explore Phase are

- Custom code assessment and clean up activities

- Data Volume Strategy and Planning
- Design and Condiguration

Test Strategy and Plan

 - Create project test framework
- Guidelines and methodology for user acceptance
- Agile Approach is planned which includes Sprint Validation Apprach
- Deliverable:
o Testing Strategy
- Procedure:
o Users act as Train the Trainer
o Methodical training and key users to perform end user training
o Enable key users to develop training material for end users
o Plan and develop end user training plan according project plan
o Finalization what training material is required for end users

Custom Code Analysis

- Customer need to idenfity code, that has to be adjusted

o Must do’s and those should do’s
- Deliverable:
o Custom Code Cleanup and Imporve
o Custom code Impact Analysis
- Procedure:
o Empowering Custom Code Management Tools
o Create Custom Code work list

Unit 6 Lesson 4: Realize Phase

- Execution of necessary steps to migrate to HANA

- Custom code will be adjusted and data aging configured
- Non production systems will be migrated to new environment
- Trainings are prepared
- Configuration activities adjustment based on initial analysis in sandbox

Custom Code Management Execution

- List of mandatory changes is completed within Realize Phase

- Custom code adjustment take place in the already converted DEV system and transported to
QAS for testing and later to PRD
- Transport adjusted custom mocde objects to PRD as part of GO-Live Transition
- Deliverable:
o Custom Code Management
o Data Aging Configuration
- Procedure:
o Adjust affected Custom Code
o Test and Optimize your Custom Code

Cutover Preparation

- How final cutover is prepared and tested

- Deliverable:
 o Data Migratio and Verification
o Data Aging Configuration
- Procedure:
o Production System Setup
o Create Cutover Plan

Unit 6 Lesson 5: Deploy Phase

- Finalize the readiness and supporting tools for production go-live

- Final testing and end-user training and cut-over rehersals
- Hand over all activities to customer team and close the project
- Before Production Conversion, Users are trainined, cutover “dress rehersals” or mock cutover
- Ready the team to provide functional and technical support
- Transition into operations after Hyper Care pr Post Go-live Support, incident analysis and
handover to Support Organization

Handover to Support Organization

- Ensure all open tasks are handed over to support organization

- Deliverable:
o Hyper Care Support
o Handover to Support Organization
- Procedure:
o Workload Analysis
o Health check and Scalability Analysis
o Sizing Verification
o Resolve and Close Open Issues
o Handover Operations Responsibility

Project Closing

- Ensure all open tasks are given to organization

- Deliverable:
o Closing
- Procedure:
o Finalize Project Closeout Report
o Obtain Sign-Off for Project Closure

Unit 6 Lesson 6: Unit Summary and Additional Information

Unit 7 Landscape Transformation for S4HANA

Unit 7 Lesson 1: Journey Overview

- Data migration based on SLT, or SAP Lanscape Transformation Capabilities

-