SAP Activate Methodology 100

Workstreams: (Application) Design & Configuration

Design & Configuration: There are a set of Application workstreams that deal with different aspects of the application itself. These include design, configuration, testing, and integration. These workstreams cover the core of the work done on the solution to adjust it to fit customer needs. This includes the design and configuration activities, such as running the fit-to-standard workshops or configuring the system. It also covers the development of extensions, testing including integration, performance, system tests, regression testing, as well as User Acceptance Testing (UAT). ***responsible for ensuring that business processes are aligned with the SAP best practices ***activities include Conducting Scope Validation & Performing Fit/Gap Analysis

SAP Activate Community

Enter the SAP Activate Community by clicking the link: https://community.sap.com/topics/activate Follow the SAP Activate Community by clicking 'Follow' to stay on top of the latest content and SAP Activate topics. The site is structured to allow us to collaborate, by providing an easy to access place to ask questions, share experiences, and get the latest information about SAP Activate. You can interact with, and provide insights to the SAP Activate Community by clicking 'Ask a Question', 'Write a Blog Post' (make sure to tag 'SAP Activate' prior to publishing your blog), reviewing the latest content and resources that are available, review the 'Featured Content', and consume the additional SAP Activate content that is available within the community. Purpose: Access the latest SAP delivery methodologies that support SAP Project Teams in delivery of solution implementation, upgrade or migration projects, and customer engagements. Benefits: Direct connection to SAP Activate experts Questions and answers in the context of SAP Activate Content Structure Submit your feedback and ideas on SAP Activate Framework to SAP Activate content owners Create and search blogs related to SAP Activate topics Register and listen to SAP Activate experts in community calls Subscribe to forums, feeds, and content updates

Best Practices Explorer - Accelerators

Ex. Test Cases (This is an example of a test case for a business process available on the Best Practices Explorer. There are individual business process test cases available to download for related processes. This is a significant accelerator as consultants don't need to create test cases, and only need to adjust those found on the Best Practices Explorer to suit business processes which have been updated with Delta requirements.) Ex. Process Diagrams (There are individual business process diagrams available to download per business process. This is a significant accelerator as consultants don't need to design processes from scratch, and only need to adjust those found on the Best Practices Explorer to suit business processes which have been updated with Delta requirements.) Ex. Task Tutorials (There are multiple tutorials for individual business processes available. This supports project teams with training or demonstration activities within the project.)

Workstreams: Extensibility

Extensibility: addresses all custom modifications to the solution from specification to custom development. Developers / Programmers fall within, and deliver custom programming activities in this workstream.

Selective Data Transition Options

Shell Conversion: - A shell copy of the production system is made without master and transaction data, and converted to SAP S/4HANA. - The system conversion scenario is then used to convert the system to SAP S/4HANA. After the completion of the conversion - Then by using applying the Selective Data Transition scenario, specific scope can be carved out of the source system and copied to the target system (data is migrated into newly converted system) - This option is best if most of the original processes are being reused. Mix and Match: - A new SAP S/4HANA install is created (new implementation scenario) and elements of existing configuration and ABAP repository are transferred (selective data transition from existing SAP ECC) - This option is best if the majority of the solution is being redesigned but still retain some of their existing enhancements

Enablement Areas for All Customer Teams

***Enablement areas relevant for all customer team members coming from the business: 1- Solution Expertise 2- Technical Expertise 3- Project Management

SAP Model Company

***Ready to RUN S/4HANA system with pre-built Solution Documentation, which supports End to End Processes for a specific industry so the Project Team can focus on differentiation and Innovation (compared to SAP Cloud Appliance Library with ready to USE) ***Components of SAP Model Company - Business Process Content for SAP Solution Manager - Preconfigured Solution - Accelerators ***customer may use SAP Model company...resulting in NO Sandbox system for new implementation transition path

Simplification Item Checks

***Simplification Item Check (SI-Check) provides guidance on replacing custom code developed for SAP ERP with SAP S/4HANA for system conversion transition path...Relevance check: Determine which simplification items are relevant for the specific system in which you are running the simplification item check. This shall help you to assess the functional and technical impact of the system conversion on your system. Consistency check: During the conversion process, your system will be migrated to the new data structures and new processes. The conversion routines rely on consistent data in the system in order for this to happen automatically. If the simplification item check identifies data inconsistencies or missing mandatory preparation activities which could cause the system conversion to fail, it will make you aware of these issues so you can correct or exempt them before the actual system conversion starts. Simplification items check can be done and compared using the simplification database, which can be found in any SAP NetWeaver 7.5 system and above.

SAP Best Practices Solution Package Structure

***levels in the structure of SAP Best Practices Solution Package: a- Scope Item Groups b- Business Area c- Scope Items d- Building Blocks

Understanding System Conversion

***most critical factor is DATA INTEGRITY (not cost) Convert their existing SAP ERP solution to SAP S/4HANA. Includes retaining their business data, custom development, and configuration. Customers choosing this scenario may want to minimize change initially and then innovate selectively going forward. Highly likely that the customer will invest in new hardware to run the SAP S/4HANA application. This is due to factors like the database running in memory. Customers perform an initial sizing, and procure the new hardware based on the sizing results at the beginning of the project.

Workstreams: Application

***responsible for ensuring that business processes are aligned with the SAP best practices

SAP Activate Methodology Jam Site

***tool used to collaborate with other SAP Activate methodology practitioners ***gain access by submitting e-mail address via online form ***tool to access the SAP Activate Methodology content including the accelerators

SAP S/4HANA Migration Cockpit

***where you can find Data Migration Templates (NOT roadmap viewer, best practices explorer, or cloud appliance library)

SAP Roadmap Viewer

- The purpose of Roadmap Viewer is to provide access to SAP Activate methodology implementation roadmaps which represent a structured approach to the software implementation process. - Implementation roadmaps offer a comprehensive view of your project teams' associated (1) activities, (2) deliverables, and tasks, with accompanying (3) accelerator assets in document and hyperlink format (templates, examples, guides, web links) Ex. Transition to SAP S/4HANA - Implementation Roadmap View ****tool to access the SAP Activate Methodology content including the accelerators Roadmap viewer structure includes: 1 - Phases: Stages of the project. At the end of each phase, a quality gate exists to verify the completion of the deliverables. 2 - Deliverables: Outcomes that are delivered during the course of the project. Several deliverables are included within a phase. 3 - Task: Work to be performed. One or several tasks comprise a deliverable. 4 - Workstream: A collection of related deliverables that show time relationships within a project and among other streams. - - Streams can span phases, and are not necessarily dependent on phase starts and ends. 6 - Accelerators: Provide assistance in the form of How-to guides, Best Practice recommendations, prescribed templates, and links to learning materials. Accelerators can be linked to Phases, Deliverables, or Tasks. Ex. Accelerator on how to run your fit-to-standard workshops Ex. Cutover accelerator templates Ex. This Stakeholder Identification Guide Ex. This Business Driven Configuration Questionnaire Ex. This Business Process Master List *Navigate through Roadmap viewer by Workstream or Phase (not task or deliverable) *Display and navigate detailed SAP Activate methodology roadmaps == WBS (work breakdown structures made up of phase, deliverable, task, accelerators)

Three Pillars of SAP Activate

1 - Best Practices 2 - Guided Configuration 3 - Methodology

Custom Code Adoption

1- As-Is analysis: Gain full transparency on your custom code situation in the productive SAP ECC. 2- Decommission unused custom code: Decommission custom code which is not in use. This activity may start a long time before a system conversion, during conversion, and should continue afterwards. 3- Back-to-Standard where possible: Try to replace custom code with SAP or partner code. This holds true for modifications, clones and so on, and for custom code areas which are impacted by simplifications. 4- Adjust custom code for SAP S/4HANA (re-design/re-platform): Many existing custom code objects will run on SAP S/4HANA without any need for adjustment. However, some code objects must be adjusted. (for example, by using 'Quick Fixes'), and some should be adjusted according to the extensibility concept for SAP S/4HANA (in-app, side-by-side).

***Key Deliverables across project phases for System Conversion

1- Detailed system assessment 2- Code adjustment 3- Validation of migration 4- Production readiness check

RISE with SAP Delivered with Partner

1- Hyperscaler Partner 2- Service Partner Community 3- Reseller Community 4- Software Partners

SAP S/4HANA Upgrade Scenarios

1- Purely technical approach - you want to keep the system running as much as possible as before, you just cope with the SAP release strategy. 2- Leverage innovations - most of the existing functionality and processes will remain the same, but you will adopt new functions and sometimes, you might replace a previous one. Some examples include decommissioning an extension since the new release covers a requirement previously identified as a gap. 3- Embed Lob Products - integrate with the new release of SAP S/4HANA complementary products. Can be seen as a more ambitious variant of Leverage Innovations.

Understanding SAP S/4HANA Cloud Landscape (public)

1- SAP Business Technology Platform 1a- SAP Cloud Identity Services (under SAP BTP) 2- SAP Central Business Configuration (under SAP BTP) 3- SAP Cloud Starter System 4- SAP Cloud Quality System 5- SAP Cloud Production System

The Central Business Configuration system

Central Configuration system is used to configure S/4HANA Cloud The CBC is where all configuration activities are performed for the SAP S/4HANA Cloud deployment model. Part of the activities performed within the CBC is provisioning of the systems. This task is performed under the systems tab, from where the starter, quality, and production systems can be requested. SAP Central Business Configuration is designed to provide guidance for your implementation project by controlling the sequence of activities that are completed. In the Project Experience, you can manage your team members, complete activities to set up and configure your systems, and view the project status. Activities are grouped into phases, and each phase ends with a milestone. The configuration activities in SAP Central Business Configuration are designed to support customers in adapting the preconfigured SAP Best Practices content to their requirements. The available configuration activities are based on the active scope and country selections. Configuration activities may vary by country because not all business scenarios (scope items) are available in all countries. Configuration activities can be mandatory, recommended, or optional. 1- Project Management Task Timeline 2- Org Management 3- Scoping 4- Configuration

Transition Paths to SAP S/4HANA Cloud (Private)

There are several options when transitioning to an SAP S/4HANA solution. The following points details options available when transitioning to an SAP S/4HANA Cloud, private edition: 1- (recommended) One-step conversion from SAP ERP system to SAP S/4HANA Cloud, private edition 2- New Implementation from SAP ERP 3- System Conversion from SAP ERP 4- Selective Data Transition from SAP ERP 5- Lift & Shift from SAP S/4HANA on Prem to S/4HANA Cloud (Private) 6- Lift & Shift from SAP ERP on HANA followed by System Conversion 7- Selective Data Transition from SAP ERP on HANA

Technical Architecture and Infrastructure

This workstream can play quite different roles, some will be common across different roadmaps. In any project during the Realize phase, you will be performing changes to the existing security objects, for example, business roles based on the requirements collected in the Explore phase. When you adopt a new solution or convert from an earlier version, changing security definitions that translate into what a user is authorized to do or not are always to be expected. As systems have become more integrated and hybrid scenarios more common, SAP has developed new solutions that can handle the needs of cloud and on-premise implementations. Examples of those solutions are: SAP Cloud ALM SAP Identity Services

SAP Fiori Library

To facilitate the work of configuration, development, and security implementation, SAP provides several tools and resources. One of the most important examples is the SAP Fiori Library. When using SAP Best Practices, you will find a relation between the app and the scope item codes. In the SAP Fiori Library, you will find information about which Fiori apps are available for each product, which are the prerequisites (addons, patch level), how to install and configure the app, which security roles are provided, if it's possible to extend the app, features, and look preview. If you have the right access to the SAP support platform, you can access SAP Maintenance Planner to identify the upgrade or update the path that you will allow to bring your current solution to the required software levels. SAP Fiori apps library also allows the identification of related apps that can be relevant for end users. relevant to Application & Configuration workstreams

Understanding SAP S/4HANA Cloud Landscape (private)

1- Sandbox (SBX) NEW - In new implementations, the SBX is used by implementation consultants to deliver fit-to-standard workshops to customer experts with the purpose of gathering configuration and customization requirement data. CONVERSION - In a system conversion, the focus is on existing processes, SAP S/4HANA simplification items (captured in the SAP Readiness Assessment), reviewing new functionality and whether their current Workflow, Report, Interface, Conversion, Enhancement, and Forms (WRICEF) can be eliminated by adoption SAP Best Practices. The customer's existing SBX is converted to RISE with SAP S/4HANA Cloud, private edition. 2- Development (DEV) NEW - In a new implementation scenario the development system is used for configuration and development of customizations and integrations. Once completed, these are transported to the quality system for testing. CONVERSION - In a system conversion scenario the customer's existing development system is converted to SAP S/4HANA Cloud, private edition. 3- Quality (QAS) NEW - In a New Implementation scenario the configuration from the Development system is transported to the quality system where testing is performed before anything is transported to production. CONVERSION - In a system conversion scenario the customer's existing QAS is converted to SAP S/4HANA Cloud, private edition, based on the migration approach validated in the SBX and DEV systems. 4- Production (PRD) - The PRD system is used day-to-day to run the customer's business activities. 5- System Conversion NEW - In a new implementation scenario, the configuration from the quality system is transported to production system. The production system is used day-to-day to run the customer's business activities. CONVERSION - In a system conversion scenario, the customer's existing PRD system is converted t

Understanding On-Premise Landscape (on prem systems)

1- Sandbox system (Implementation consultants use the sandbox system to demonstrate SAP Best Practice processes to customer experts in fit-to-standard workshops. During the workshops, the best practices process are validated against the customer business scope, configuration data is gathered, and customization decisions are made among other activities. The Sandbox system is further used as a 'play area' for consultants to familiarize themselves with new functionality when the solution is live.) 2- Development system (The development system used to perform configuration activities. Once configuration is performed, it is saved in transport requests and transported to the quality system for testing.) 3- Quality system (The quality system is used to performed testing activities. Different cycles of testing are planned and executed to verify configuration and development efforts work according to customer requirements. After testing cycles are successfully completed, configuration and development activities are transported on to the production system in preparation for go-live.) 4- Production system (The production system is a live system where business users execute their daily activities to run the organization's business processes.)

Testing Sequence

1- Unit testing 2- Business process testing, also called string testing 3- Integration testing 4- Data conversion testing 5- User acceptance testing

SAP S/4HANA Cloud (Private) Features & Benefits

1. Full Scope and Coverage Full functional SAP S/4HANA scope including LOB and industry processes, supporting 25 industries Wide range of partner add-ons 64 country/region versions in 39 languages Rise with SAP. Your SAP concierge service to move to the cloud 2. Investment Protection System conversions and brownfield migrations into the cloud Application and technical operations out of ONE hand Safeguarding prior investments into SAP systems 3. Flexibility and Extensibility Access to SAP S/4HANA Extensibility Framework Side-by-side and in-app extensions Code enhancement and code modifications Expert configuration (full IMG access) Scalable platform 4. Cloud Scalability and TCO Elasticity, resilience, and TCO of hyperscaler infrastructure Technical operations done by SAP These include application upgrades and many basic functions Upgrades and performed by SAP on customer request

Primary Conversion Steps

1. Prepare ERP System Clean up custom code and reduce data volumes 2. Database Migration Move to SAP HANA database (only if source is on a DB other than HANA) 3. System Update Provide new applications and tables 4. Data Conversion Convert table content to new data model 5. Software Configuration Implement SAP S/4HANA mandatory and simplification items and reuse majority of existing processes SAP readiness check: Responsible for identifying which components need to be adjusted on SAP ECC in order to work on SAP S/4HANA Maintenance planner: Responsible for calculating the upgrade path Software Update Manager (SUM) is the tool that facilitates the 2-database migration, 3-software update, and 4-data conversion steps. Database Migration Option (DMO) is an optional feature of the Software Update Manager (SUM) tool. It combines three system conversion processes into a single step procedure: database migration + system update + data conversion. - DMO responsible for the Database Migration and Data Structure Conversion from any database to the SAP HANA database. System Move is an additional step that facilitates migration from old to new data centers (servers) - The reduces complexity, downtime, transition time, and costs of the system conversion by packaging multiple steps together and adding the system move to facilitate switching from the old servers to new servers in the target hyperscaler.

Overview Steps for New Implementation (private cloud)

1. Software Installation - SAP provisions a new SAP S/4HANA instance in the cloud 2. Preconfiguration Content Activation - Customers can choose one of the following preconfigured templates as a base for deployment: a- SAP Best Practices for SAP S/4HANA b- Enterprise Management Layer (EML) for SAP S/4HANA c- SAP Qualified Partner Packaged Solutions 3. Software Configuration - Configure and design the new SAP S/4HANA instance based on SAP best practices. 4. Initial Data Load - Transfer the business data needed to run the new system by loading master and open transactional data from the legacy system. The SAP S/4HANA Migration Cockpit facilitates migration of legacy data to the target SAP S/4HANA system. - - Two types of data are migrated: a- Master Data: Core business objects such as activity, cost center, bank master, customer, and supplier. b- Open Items: Open transactional data such as financial balances, sales orders, and purchase orders.

SAP Hyperscaler Partners

A cloud software a service (SaaS) solution requires infrastructure to host the solution. Infrastructure refers to the physical servers where your software is installed. A building with many rooms full of these servers is called a data center. SAP has its own data centers, and we partner with other companies that provide infrastructure services, who are referred to as hyperscaler partners. Our hyperscaler providers include Microsoft Azure, Amazon Web Services, Google Cloud, and Alibaba Cloud. When customers use an Infrastructure as a Service (IaaS) provider, they do not have to buy the physical hardware or employ in-house experts to maintain it. The classic 'on-premise' concept refers to a customer purchasing and owning their own servers on company property, and installing and maintaining their software in these servers. For the public cloud deployment, SAP is the default infrastructure provider. This enables us to offer customers the lowest TCO with a complete, packaged SaaS offering. For the private cloud deployment, customers can choose their preferred infrastructure provider from our hyperscaler providers, SAP, or in special cases, the customer's own data center. These special cases are reserved for customers in regulated industries, public sector, or in countries with data residency requirements.

Accelerator - Sizing Approaches for Hardware (on prem)

An additional consideration when implementing on-premise solutions, is sizing of the hardware. The size of the hardware and database is influenced by both business aspects and technological aspects. This means that the number of users using the various application components, and the data load they put on the network, must be taken into account. User-based sizing We defined three types of active users who work with the system to a different degree. Merely counting the users can be done quite easily. The estimation is quite rough as it says very little about the actual throughput these users produce. Throughput-based sizing This model is quite thorough as it calculates sizing on expected throughput. Assumptions in business terms (for example, number of order line items per year) need to be cross-checked against the individual installation. Customer Performance Test The according tests are done in a customer system with customer data. The disadvantage is that conducting these tests requires considerable time and money. For further information please refer to the white paper Carrying Out Customer Performance Tests.

Workstreams: Analytics

Analytics: covers the analytics aspects of an SAP implementation project.

CLOUD (PRIVATE)

Cloud Value, Traditional Flexibility & Full Scope - Single-Tenant (house) - designed to provide innovation and cloud value while allowing customers to retain their investments by converting their existing systems - private cloud deployment can be a new implementation, but also supports system conversion from an existing SAP ERP on-premise system. - enables customers to maintain many of their existing business processes and customizations while gaining the value of cloud architecture and services. The private cloud also supports the same functional scope as SAP S/4HANA on-premise, including all 25 industries, whereas the public cloud has a more focused finance-led core ERP scope with a few selected industries, such as Professional Services. *Upgrade schedule is defined by Service Level Agreement With private cloud, customers that require a high degree of control and customization get the best of both worlds. You still get full visibility and control with access to the backend of the system through the SAP GUI, but you also get to outsource the infrastructure and technical software maintenance to cloud providers (similar to public cloud) under one contract. In an SAP Private Cloud scenario, the service provider (SAP) is responsible the technical infrastructure and primary SAP Basis related activities, including upgrades, application and performance monitoring related troubleshooting, and all other IT infrastructure related services. In this scenario, the customer is responsible for all application and business process management activities, including application configuration and related support. A private cloud deployment is recommended if a customer has plans for a long-term evolutionary journey to the cloud with high landscape complexity including mostly fragmented, highly customized systems. The implementation

CLOUD (PUBLIC)

Complete, Modern, SaaS ERP (software as a service) - Multi-tenant (apartment building) - for companies ready to embrace the future of ERP with a new implementation and predefined processes - public cloud deployment is a new implementation with a fresh system, and offers the lowest total cost of ownership (TCO) with an easy to set up, and easy to use system based on standard SAP Best Practice business processes. - does NOT include traditional flexibility and full scope compared to Private Cloud -> can't adjust directly in cloud system, faster implementation, lower TCO *provides regular updates (quarterly basis) with new features and capabilities ***primary concern is DATA SECURITY (not speed of deployment) With the public cloud solution, customizations are made through SAP Fiori apps designed to facilitate those changes (for example, Custom Fields and Logic and Custom Business Objects). This means extensions are guaranteed to be lifecycle-stable through future releases and therefore require less maintenance and attention. For complex customizations that cannot be done through the existing Fiori apps, the SAP Business Technology Platform extension suites are readily available and easily integrated to SAP S/4HANA Cloud. These public cloud characteristics - multi-tenancy, standardization, outsourcing maintenance of the system to your cloud provider, and lifecycle- stable extensions, result in the lowest TCO and highest return on your investment. A public cloud deployment is recommended if a customer has the ability and mindset for a transformational project, low landscape complexity (less customization/control), and can implement a greenfield approach. The implementation will include: a- A complete, modern, SaaS ERP solution with full public cloud benefits the fastest path to innovation and lowest TCO. b- A clean Clo

ON PREMISE

Customer already running SAP ERP: (a) new implementation (b) system conversion - In a new implementation scenario customers implement a new instance of SAP S/4HANA or other SAP solutions by moving either from a non-SAP legacy system or from an older SAP solution. In this scenario, customers have the opportunity to maximize innovation, overhaul and redesign their business processes, and adopt new cloud-based solutions. Customers may only want essential master data and transactional data from their existing solution. In an on-premise environment, the customer IT is responsible for the entire solution. bAll IT roles, responsibilities, and activities rest with the customer team. ***key consideration with data migration on-prem is Data Volume! (not user access levels) *Maximum flexibility in terms of customization and integration! ***key consideration is accessing hardware and infrastructure requirements!!! *Requires additional deliverables for system setup (difference btwn new implementation of SAP cloud vs on-prem) --> specific on-prem deliverable that is NOT for cloud = Knowledge Transfer *use SAP System Landscape Management tool to assist in monitoring and managing system landscape *project jump-start for new implementation of on-prem includes SAP Best Practices

Data Volume Management (DVM)

DVM is used for (1) decreasing volumes of migrated data (by implementing DVM measures in source SAP ERP system before System Conversion) and (2) for avoiding explosive data growth in the S/4HANA system 1- Data avoidance and when and how to use this for *YOUR* system. 2- Data summarization - What data can be summarized on *YOUR* system. 3- Data deletion - What data can be deleted or truncated, and is unnecessary for *YOUR* system. 4- Data archiving - What archiving objects exist today, what will exist in SAP S/4HANA, and where archiving will exist.

Concepts of Data Management

Data Management Workstream consists of three substreams: 1- Data Migration - deals with migrating legacy data (master data as well as very limited transactional data) into target SAP S/4HANA system 2- Data Volume Management - aims at keeping required system performance level and optimizing TCO by storing the right (mostly transactional) data in the right place 3- Master Data Management - target is high data quality and data unification and its efficient management within business solutions landscape

Workstreams: Data Management

Data Mgmt: all Data Management activities within a project are covered under the Data Management workstream.

Selective Data Transition

Definition -> data migration from one or more existing SAP ERP solutions to SAP S/4HANA The Selective Data Transition path works with both the new implementation and system conversion transition scenarios. You select which data to transfer to target system which can include: - ABAP repository of objects and developments - Configuration (customizing) data - Master data - Transaction data (open items and a time-slice of historical closed items, for example, 2 years) Using the SAP LT (Landscape Transformation) tool, customers can tailor their scope relative to their unique scenarios and move these elements across. *Ensure data integrity by conducting thorough testing post-transition

Implementation Tool 1. SAP Solution Manager - Focused Build

Focused Build for Solution Manager enables the management of requirements and software development in large, agile innovation or waterfall and hybrid projects -> ready-to-run and integrated, tool-supported methodology Focused Build supports customers with a seamless, tool-based, requirements-to-deploy process. For this purpose, Focused Build provides pre-configured standard *SAP Solution Manager features* and processes, as well as additional build functions. Focused Build is a ready-to-run and integrated, tool-supported methodology to manage requirements and software development for all SAP projects. Key attributes of Focused Build: - Focused Build is delivered as a standard solution with no additional coding required. - SAP delivers all knowledge required with the focused solution, significantly reducing training costs. - Your license includes standard upgrade, reducing upgrade risk. - Focused Solutions are based on the proven SAP Solution - Manager standard, and are fully integrated in SAP Solution manager 7.2. SAP Solution Manager includes: - Solution Readiness Dashboard (track status of all project activities) - Project Planning (manage project plan, tasks, resources) - Process Modeling area (update process flow diagrams) - Requirement Backlog List - Test Step Designer (write manual test cases) - Test Suite Dashboard (track test activities) To support agile development, you can leverage SAP Focused Build, which is a ready-to-run tool integrated with SAP Solution Manager for managing agile projects. SAP Focused Build has no additional cost, and supports building the solution in short, time-boxed sprints, with frequent inspection points by the customer. Focused Build for SAP Solution Manager in the SAP Help Portal.

***Five Golden Rules (private cloud)

Foster a cloud mindset by adhering to fit-to-standard and Agile deployment detailed in SAP Activate. Use preconfigured solutions with defined processes. Use modern integration technologies. Use modern extensibility technologies. Ensure transparency on deviations.

3 - Activate Methodology

In SAP Activate methodology, we are leveraging the SAP Best Practices as a default way to build the baseline system for fit-to-standard There are four core project phases in SAP Activate that we do not have separate phases for the final preparation and go-live support, but instead execute them in one phase called 'DEPLOY'. The blueprint activities that were represented in ASAP, have been replaced with fit-to-standard analysis workshops. The project team uses the SAP Best Practices based system to validate the customer's requirement against a working baseline solution. Then, the team captures the delta requirements and/or user stories in the backlog. This information is then used for implementation of requirements during the Realize phase. SAP Activate Methodology supports not only the on-premise deployment, but also cloud deployment, with one consistent approach. SAP Activate brings together the approach for on-premise and cloud. It harmonizes the approach across these different deployment models which also helps to support hybrid deployment projects. - ONE simple, modular, and agile methodology, supporting all S/4HANA transition scenarios - Successor of ASAP and SAP Launch methodologies - Full support for initial deployment and continuous business innovation - Harmonized implementation approach for cloud, on-premise, and hybrid deployments - Broad coverage of SAP solutions starting with SAP S/4HANA; - SAP Activate methodology is designed to support all SAP solutions. - Enables co-innovation with customers, and is accessible for partners

Governance Bodies - Level 1 - 4

Level 1 - Executive Board (company-wide) - Sets business vision and goals - Approves project vision - Delegates authority to Steering Committee - Allocates funding for the project Level 2 - Steering Committee (project specific) - Approves project goals - Approves project results - Approves project changes according to delegated authorities - Delegates authorities to the Operating Committee - Escalates unresolved issues to the Executive Board Level 3 - Operating Committee (project specific) - Monitors and coordinates activities in all workstreams of the project - Delegates authority to Ongoing Meetings - Escalates unresolved issues to Steering Committee Level 3 - Integrating Committee (inter-project) - Makes decisions on integration and master data management across projects - Defines integration and controls integration points register - Defines release strategy across projects - Ensures integration and consistency between deliverables of several projects Level 4 - Ongoing Meetings (project specific) - Clarifies ongoing open issues - Escalates unresolved issues to Level 3 - Makes decisions as delegated by Level 3

Lift and Shift

Lift and Shift moves an entire system without change to a new landscape. Primary Steps: 1. Check Prerequisites Source system must be on a supported release. 2. Provision Target System Provision new hardware in the new landscape. 3. Backup and Restore Use Software Provisioning Manager to back up the current system and restore it on the target system.

SAP Activate (high level)

Major changes and the way customers approach implementation: 1 - Shorten time to value and reduction in costs 2 - Reduce risks while moving forward (move from big bang to incremental approach) 3 - Higher flexibility and choice for deployment (on cloud, on-prem, hybrid, mobile options) The purpose of the SAP Activate framework is to expedite and/or fast track any and/or all deployment options for all SAP products. This is achieved using automated testing tools, ready-to-run systems, and ready-to use content (available in the Roadmap Viewer) Leads to lower Total Cost of Implementation: 1 - As documentation effort is significantly reduced using accelerators. 2 - Configuration time significantly reduced using Ready-to-Run Systems. The SAP Activate Solution Adoption framework provides all content and tools required to support any SAP product deployment. This includes accelerators in the form of project plans and documentation templates available to be used in each project phase, as well as pre-configured 'in-system' business processes, making the systems virtually ready-to-run after activation.

Workstreams: Operations & Support

Operations & Support: all deliverables relating to the support of the solution, upgrade, incident, and change management when the solution is live, are covered within this workstream.

Cloud Appliance Library

Platform to deploy preconfigured system templates Customers can use the SAP Cloud Appliance Library (CAL) to deploy a trial system to explore various preconfigured and ready-to-run (ready to USE) SAP solutions. An appliance is a compressed system image that can be rapidly extracted into a regular system instance by preserving everything that has been configured in the appliance when it was developed.

Fit to Standard

Primary role of Fit to Standard Analysis is to Identify gaps between standard SAP solutions and business requirements sequence of steps: 1- Review Best practices process low 2- Demonstrate business scenarios and concepts 3- Discuss how the process fit with customer requirements 4- Identify gaps 5- Identify required configuration 6- Enable customer on execution of scenarios ***sequence of activities performed in Explore phase: a- set reference value b- conduct Solution Validation workshops c- Prioritize initial backlog d- Conduct Delta Design workshops ***minimizes need for rework during realization ***prioritizes delta requirements and gaps

Workstreams: Project Mgmt

Project Mgmt: covers all the aspects of setting up the project, running it, and delivering on the project objectives. The Project Management workstream is structured around the fundamentals of agile project delivery, and is aligned with Project Management Institute standard, the PM Body of Knowledge (PMBOK).

SAP Central Business Configuration

SAP Central Business Configuration (CBC) is a separate tenant that lives in SAP Business Technology Platform, where you provision your SAP S/4HANA Cloud systems (Starter, Quality, and Production), activate the business scope, and complete configuration-related activities. Configurations are moved from CBC to SAP S/4HANA Cloud through transports. SAP CBC is used by customers after go-live to continue to maintain their SAP S/4HANA Cloud solution by activating new scope, countries, and making configurations.

Implementation Tool 2. SAP Cloud ALM

SAP Cloud ALM is an Cloud Application Lifecycle Management (ALM) offering for customers with a cloud first or cloud only strategy. In this case, customers do not need to deploy SAP Solution Manager to manage the Implementation, as SAP Solution Manager is deployed on-premise only SAP Cloud ALM provides an in-system project management application to manage the project plan, tasks, and resources. The project management tool is suited to manage agile, waterfall, or hybrid projects. Project management is further integrated into the requirements management and release management areas. Similar to Focused Build. Key attributes of SAP Cloud ALM: - SAP Cloud ALM is deployed in the cloud only. - SAP Cloud ALM manages the application lifecycle for the Intelligent Suite. - SAP Cloud ALM is for cloud-centric customers. - SAP Cloud ALM manages cloud and hybrid (combination of on-premise and cloud) solutions. - SAP Cloud ALM manages the application lifecycle in the public cloud. - SAP Cloud ALM is an application running on SAP Business Technology Platform and is optimized for SAP HANA. - SAP Cloud ALM is an ALM solution optimized for cost efficiency. ***NO additional cost of product, ***pre-loaded SAP Activate tasks, ***Accelerated time to market* SAP Cloud ALM provides ability to: - Project Overview (manage project plan, tasks, resources) - Capture Requirements - Design Processes modeling area - Manage Transports - Prepare Testing *Key difference btwn Notes and Requirements in Change and Deploy capability of SAP Cloud ALM = users can create a follow-up task that is actionable for Requirements

Implementation Tools

SAP has a vast product portfolio including several options for implementation management tools depending on your business strategy, deployment option, and product landscape. Part of your SAP Activate journey is the selection of your implementation management tool. These tools are designed, developed, and available to manage all activities within your implementation project from one central application. The two primary options for implementation management are: SAP Solution Manager Focused Build SAP Cloud ALM

SAP Readiness Check

SAP readiness check: Responsible for identifying which components need to be adjusted on SAP ECC in order to work on SAP S/4HANA The following area is covered by the SAP Readiness Check for SAP S/4HANA: - Add-Ons and Business Functions - Custom Code and Development - Data Volume Management - Recommended SAP Fiori Apps - SAP S/4HANA Sizing

SAP Cloud Security Strategy

SAP's security strategy has three cornerstones: 1- secure products 2- secure operations 3- secure company

SAP LT (Landscape Transformation) tool

Selective Data Transition is enabled through the SAP LT (Landscape Transformation) tool. The following are the key capabilities and scenarios this tool is used for: 1- Consolidation of multiple system into one 2- Migration of Business Units (extraction) 3- Migration of selected applications ***system consolidation, extraction of business units, consolidation through online data replication SAP landscape transformation is made up of analysis and transformation tools to use as part of your migration, conversion, or reorganization projects. It works very similarly to a data migration tool which connects to source systems, transforms data, and loads to the target. SAP LT ensures full data consistency and data integrity within transformation projects such as data migrations and data conversions. *Two Landscape Transformation specific tasks in Explore phase: 1- Setup Landscape Transformation software 2- Run Landscape Transformation Assessment ***Tasks associated with the LT area are in which workstream? - Technical Architecture & Infrastructure

Side by Side Extensibility - New Implementation (on prem)

Side-by-side extensibility refers to developing an app or extension on a different platform, then integrating the custom development with the target SAP S/4HANA Cloud system. SAP's development platform is the SAP Business Technology Platform (BTP), and we have both low/no-code and code-based development solutions.*** Extensibility in SAP Business Technology Platform is divided into three suites: 1- Extension Suite - Development Efficiency - Extend and optimize business processes in your existing applications, and simplify development with low-code tools to create innovative applications faster. 2- Extension Suite - Digital Experience - Deliver consistent, personalized, and unified user experiences across business applications and multiple channels at scale. 3- Extension Suite - Digital Process Automation - Automate repetitive and manual tasks with digitalized workflows and robotic process automation bots. - Predefined process content packages designed for specific lines of business and industries enable you to implement customizations quickly and easily. Side by Side extensibility enables loosely coupled development (?)

Concepts of Solution Adoption

Solution Adoption Substreams 1- End User Training (ensure end users are ready to use new solution) 2- Value Management (ensure all decision are made based on business value) 3- Organization Change Management (ensure all stakeholders are identified and involved in the project and accept changes caused by the project)

Workstreams: Solution Adoption (Change Mgmt)

Solution Adoption: deals with what was previously covered in the OCM stream and training stream in ASAP. The adoption activities enable the organization and end users to use the solution in their daily work. The deliverables and tasks guide the project team in ensuring a smooth transition to operations, post go-live support, and change management. *Activities part of Solution Adoption workstream for new implementation*: - *Value Determination* - *Value Audits* - *Change Management Plan* - *Project Business Case* - *System Go Live Announcement (order)* - *Business Transformation Review (Point of View)* - NOT (scope validation, production support plan,detailed design-business process)

Definition of Done

Solution must be built and configured in the development system (DEV)

System Conversion New Implementation Selective Data Transition

System Conversion enables you to make a convert the existing system and data, then add innovation over time through LoB processes, the SAP Fiori launchpad, machine learning, and automation. New Implementation enables you to start with a clean system and deploy SAP Best Practices. Customers can start with new innovations and see the resulting benefits from day one. *Selective Data Transition meets the business need to harmonize data across multiple SAP ERP and other legacy system data. Customers can retain historic data in the productive system, while implementing partial redesign of their processes.

Workstreams: Tech Architecture & Infrastructure

Tech Architecture & Infrastructure: address all activities required for the technical end of the application. From operating systems, databases, installation, upgrades, and maintenance, all these activities fall within and are covered by the technical team 'Basis' under this workstream. ***takes lead in validation system performance under data load in final stages of SAP project

SAP Business Technology Platform

The BTP is a platform as a service and is included as part of the a RISE with SAP contract subscription. This subscription provides customers with access to all BTP software and services. It's important to note that while some services are not charged, others do included a service fee. Key capabilities include: a- Database and data management solutions provide the ability to handle the growing amounts of data stored in multiple locations by providing controlled access for your entire organization to analyze and act on a single source of the truth. b- Analytics solutions enable users to provide real-time insights through machine learning, AI, business intelligence, and augmented analytics to analyze past and present situations, while simulating future scenarios. c- Application development and Integration capabilities simplify development and accelerate integration on an open cloud platform. d- Intelligent technologies optimize processes, maximize resources, and kick-s

SAP Cloud Connector (on prem)

The Cloud Connector facilitates secure communication between SAP cloud solutions and protected on-premise networks that cannot be accessed directly from the internet and acts as a reverse invoke proxy component that is installed and runs on an on-premise network. The administrator has complete control over the on-premise systems and resources that can be accessed by the cloud applications and the cloud applications using the cloud connector. Broken connections are recovered automatically, and the tool provides audit logging of inbound traffic and configuration changes. Cloud connector is used in hybrid scenarios where cloud applications must access or extend on-premise software.

SAP Cloud Identity Services

The SAP Cloud Identity Services tenants are the first systems provisioned for a customer. SAP Cloud Identity Services runs on the SAP Business Technology Platform and consists of two separate tenants, Identity Authentication and Identity Provisioning. SAP Cloud Identity is the default identity provider for SAP S/4HANA Cloud and provides secure authentication and single sign-on for users in the cloud.

SAP Solution Manager Test Suite (on prem)

The SAP Solution Manager Test Suite is used to manage and execute testing for SAP solutions on-premise. You can plan the scope of testing required for cross-system business processes, manage the tests centrally, and execute those tests. SAP and Tricentis have expanded their existing partnership where all customers with an SAP Enterprise Support agreement will be entitled to use Tricentis Test Automation for SAP as a term license. This will benefit customers in facilitating an easier transition to SAP S/4HANA and the intelligent enterprise.

1 - Best Practices

The documented format of the SAP Best Practices can be found on the Best Practices Explorer. From this platform, all business processes' Best Practices documentation content for each product is available for review, download, and use with your projects. Documentation Best Practices allow the reader to read the Best Practices for each business process. The Configuration format of the Best Practices is found directly inside of the system. These Best Practices are preconfigured business processes which lay dormant inside of the system. Once activated, these Best Practice processes are now 'ready to run'. Configuration Best Practices allow the user to execute the process inside the system.

Best Practices Explorer

The following information can be found in SAP Best Practices Explorer: - Scope item fact sheets: A description of the business process including business benefits and key process steps covered. - Process flow: A representation of the standard business process to show how the software works by default. - Process flow (BPMN2): A downloadable version of the business process flow that can be edited in process modeling applications if the standard process flow is customized. It's important to document any process that no longer follows the standard process. - Test scripts: A procedure for testing the standard Best Practice processes in the system. - Set-up instructions: A guide with instructions to set up the prerequisite requirements (usually an integration) before the test script can be completed. - SAP Best Practices Solution Package: Contains descriptions and corresponding content (Solution Manager Content, Data Source definition for Data Services, and so on) in SAP Software Downloads Center. -- Each Solution package consists of solution specific content including: a- Customer Scope Presentations b- SAP Notes c- Processes Steps, Business Roles, and related SAP Fiori apps d- A list of all prerequisites e- Forms f- What's New g- Task Tutorials

SAP Cloud Production System

The production system is provisioned via the CBC and kept in sync with the quality system via weekly or bi-weekly transports. After configurations have been made in CBC, transported to quality, and tested thoroughly, the configurations can be released to the production system via the CBC. Certain configurations cannot be made in the CBC and must be done directly in the production system. The guided workflow tasks in the CBC instruct the implementation team members when to make these configurations in the production system. After go-live, the production system is used by end users to run the organization's business processes.

Project Governance

The project governance describes the flow of information between the project and all the stakeholders. It specifies the decision making and escalation steps to resolve issues. The governance framework has a couple of characteristics that need to be established. It focuses on realizing the business value, managing the risk and issues, and enforcing the standards and accountability for the project. Tools - In an on-premise scenario, a project manager most likely will be using *SAP Solution Manager* to perform is documentation and tracking activities. - In a cloud scenario, *SAP Cloud ALM* will be more common. The trend in SAP is to evolve from SAP Solution Manager to SAP Cloud ALM. - Both tools, SAP Solution Manager and SAP Cloud ALM can provide the single source of truth for the project documentation, for all workstreams. Solution Documentation has now been used for more than 20 years in SAP projects. - This tool's functionality can cooperate with other products, SAP and non SAP, for different purposes, from documentation, testing, process modeling, and so on. One example that is taking a major role in SAP implementations is SAP Signavio.

SAP Cloud Quality System

The quality system is provisioned and configured via CBC based on the data and requirements gathered during the fit-to-standard workshops. The implementation team should transport configurations to the quality system in weekly or bi-weekly sprints, followed by thorough testing of configured processes. Extensions, such as creating custom fields, are done with the relevant extensibility SAP Fiori apps in the SAP S/4HANA Cloud quality system. After thorough testing, extensions can be transported from quality to production using the Software Collection transport SAP Fiori apps in SAP S/4HANA Cloud. Other activities, such as setting up business roles and assigning permissions, setting up integrations, and migrating data, are done directly in the SAP S/4HANA Cloud quality system, but cannot be transported and must be done again in the relevant SAP Fiori apps in the production system.

SAP Cloud Starter System

The starter System includes the enterprise management scope and comes with preconfigured business processes and master data. The data and configuration in the starter system directly aligns with the scope item test scripts in SAP Best Practices Explorer. Implementation consultants use the starter system to demonstrate SAP Best Practice processes to customer experts in fit-to-standard workshops. During the workshops, the business scope that was identified in the Digital Discovery Assessment is confirmed, configuration data is gathered, and customization decisions are made. After consultants move onto configuring the quality and production systems, the starter system can be decommissioned.

Test Automation Tool for SAP S/4HANA Cloud

The test automation tool is integral part of SAP S/4HANA Cloud. With preconfigured test scripts you can automate your business process tests. You can further change existing or create new test cases via the recording functionality. In addition, improved regression testing is supported by SAP delivered test automates on app level. 1- Acceleration 2- Analysis 3- Regression 4- Documentation 5- Personalization

*Best Practices for New Implementation (on prem)

The tool for deploying SAP Best Practices in an SAP S/4HANA private cloud or on-premise system is the ***SAP Solution Builder. The focus of the Solution Builder is on solutions. A solution contains a set of SAP Best Practices scenarios which are predefined process flows for a particular line of business or business area. Scenarios consist of one or more building blocks, which are self-contained, and reusable entities that include customizing settings and/or master data steps. - Best Practices are only activated once in the development system. Transports are used to provide the quality and production systems with the business configuration defined in the development system. - All of a customer's business processes documentation live in the central library in Solution Manager called Solution Documentation. When customizing SAP Best Practices to a customer's requirements, do not edit the SAP Best Practices directly. Make a copy and edit the copy. Additional customer-specific content and supporting documentation is also created and maintained in Solution Documentation.

SAP Analytics and Reporting Portfolio

There are several SAP options for creating data insights and providing summaries in a structured (reporting) format for SAP customers. There are cloud, hybrid and on premise options The following are part of the SAP Analytics and Reporting Portfolio: - SAP Analytics Cloud - SAP S/4HANA Embedded Analytics - SAP Hybrid Solutions (BI/Planning/Predictive) - SAP Analytics Hub (BI,Planning,Predictive Analytics in one solution) - SAP BW/4HANA Data Warehousing - Advanced Compliance Reporting (ACR)

Testing Types

Unit Test: Confirm that individual transactions and RICEFW developments have been correctly configured - Within the project sprints, the consultant conducts unit testing. - This testing is informal, and doesn't need to be documented. - The objective of this test is functionality testing. String Test: Validate and verify the system components against Solution Documentation. - String testing is generally composed of two overlapping modules that are 'stringed' together to verify that modules / business units exchanging data work as expected. String testing can be viewed as a 'mini integration test'. Integration Test: To validate that all software module dependencies are functionally correct and that data integrity is maintained between separate modules for the entire solution. - System integration testing covers end to end business process, and all other business process scopes designed and built as part of the project. There can be several cycles of integration tests performed to cover the full scope of the solution. - This testing is formal, and must be documented. - The objective of this test is the entire scope of the project. - ***integration test scope outline includes (A - Solution Baseline, B - Delta/gap solutions, C - Data Flows with non-SAP application) User Acceptance Test: To check if the system can support day-to-day business/user scenarios and ensure the system is sufficient and correct for business usage. - the Realize phase ends with user acceptance testing. This should is conducted by business users, using the quality system and data migrated in earlier stages to carry out business process tests. UAT is performed by the business to validate the completed scope as agreed in fit-to-standard workshops. - This is meant to not only provide a final confirmation of system functionality and performance, but al

Retrofit

When performing a system conversion, new hardware is generally provisioned to support the SAP S/4HANA solution. This results in a temporary dual landscape (maintenance and project). The project landscape is an exact system copy of production (with data desensitized). As the project team start their conversion activities, the maintenance team continue their business as usual changes through the maintenance environment. This means that every time a maintenance change goes through the maintenance landscape, the project landscape is now out of sync. We use Retrofit to keep the project environment in sync with the maintenance landscape. Retrofit copies the change into the project landscape to keep the environments in sync.

2 - Guided Configuration

With Guided Configuration, you can perform the following tasks: 1 - Initial configuration of your solution and recording of updates for continuous innovation, 2- test your configured business processes, 3- data migration, and 4- evaluate activated business processes and country versions. ***Configuration in the public cloud solution is performed via Self-Service Configuration Ui's (SSCUI) and The Central Business Configuration system. ***Configuration for on-premise solutions as well as private cloud is perform via the traditional Implementation Guide (IMG) in Transaction SPRO. *Guided configuration helps with the following activities: - Train new users - View solution scope - Test configured processes

***Realize phase activities for System Conversion

a- custom code adjustment b- delta configuration c- development system migration d- non-production systems migration e- data aging configuration NOT operations impact analysis NOT sandbox system migration NOT value determination NOT custom code adjustment planning