S4H100

S4H100 SAP S/4HANA Implementation Scenarios

D i s c o v e r y E d i t i o n .

. n o i t i d E y r e v o c s i D

.

. PARTICIPANT HANDBOOK INSTRUCTOR-LED TRAINING

. Course Version: 04 Course Duration: 2 Day(s) e-book Duration: 5 Hours Material Number: 50135509

Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used.

This information is displayed in the instructor’s instructor’s presentation

Demonstration

Procedure

Warning or Caution

Hint

Related or Additional Information

. n o i Facilitated Discussion t i d E y User interface control r e v o c Window title s i D

Example text

Example text

© Copyright. All rights reserved. reserved.


Contents vii

Course Overview

1

Unit 1:

Overview SAP S/4HANA

2

Lesson: Why do we Need a New Business Suite

5

Lesson: Introducing SAP S/4HANA

21

Unit 2: 2:

Overview of the Implementation to SAP S/4HANA

22

Lesson: The Three Ways to SAP S/4HANA

28

Lesson: Basics about Migration and Tools for Migration to SAP S/ 4HANA

32

Lesson: Migration to SAP S/4HANA

35

Lesson: Migration to SAP S/4HANA cloud

39

Lesson: SAP Activate Unit 3:

New Implementation Lesson: New Implementation Overview Lesson: New Implementation to SAP S/4HANA Exercise Exercise 1: Upload File with Data Services Lesson: New Implementation to SAP S/4HANA Cloud


Exercise 2: Upload File with SLT Unit 4:

System Conversion Lesson: Introduction Lesson: Aspects for Planning a System Conversion Lesson: Different Migration Options Lesson: Choosing the Right Option Lesson: Migration Services Lesson: Best Practices Exercise 3: Migration of Cost Elements Lesson: Lesson: Example: Custom Code Analysis Exercise 4: Custom Code Review

Unit nit 5:

Lan Landsc dscape ape Trans ansforma ormati tion on Lesson: The Content of Landscape Transformation Lesson: Lesson: Central Finance - a deployment option Exercise 5: FI Posting to Central Finance

Unit Unit 6:

SAP SAP Inf Info o Sou Sourrces ces and and Furth urther er Cour Course ses s Lesson: Further Courses and Useful Links





© Copyright. Copyright. All rights reserved.

Course Overview

TARGET AUDIENCE

This course is intended for the following audiences: ●

Program/Project Manager

●

Solution Architect

●

System Architect

●

Technology Consultant







UNIT 1

Overview SAP S/4HANA

Lesson 1

Why do we Need a New Business Suite

2

Lesson 2

Introducing SAP S/4HANA

5

UNIT OBJECTIVES ●

Describe the need for a new Business Suite

●

Describe SAP S/4HANA and its key features




Unit 1 Lesson 1 Why do we Need a New Business Suite

LESSON OBJECTIVES OBJECTIVES

After completing this lesson, you will be able to: ●


Why do we need a new Business Suite?


Figure 1: The World Is Now Digital

If you look at the numbers shown in the figure, it becomes obvious that the world around us is not getting simpler; it is getting more complex, for the following reasons: ●

Exponential growth of digital information - social, mobile, big data

●

Globalization and spread of business networks

●

Internet of Things (you could also say, the Internet of everything)

The response so far was to add more complex business processes, processes, more complex organizations, and more complex software solutions. At the end of 2009, 5% of the world's population owned smartphones. Four years later, later, that figure jumped to 22%. Cur rently, 1.7 1.7 billion people are on social networks. Over the next three years, that audience will surpass 2.55 billion. By 2020, 5 billion people will enter the middle class and come online, while 50 billion devices will be connected to the "Internet of Things," creating a digital network of virtually everything. Cloud computing - a $41 billion business in 2011 - will grow to a $241 billion business in that same time frame. The exponential proliferation of mobile devices, social media, cloud technologies, and the staggering amounts of data that they generate have transformed the way we live and work. In fact, 61% of companies report that the majority of their people use smart devices, for everything from email to project management to content creation.

© Copyright. All rights reserved.


Lesson: Why do we Need a New Business Suite

While all of these advancements have improved improved our lives and provided us with greater opportunities for innovation than ever before, they have also accelerated the rise of an entirely new problem to contend with, unprecedented and crippling complexity. The world may be getting smarter, but it has not become easier. Massive consumerization of IT means online purchasing, banking, completing online applications become commonplace. Think about how much digital data you created today. Maybe some of it was of interest to some organizations? Data is the new oil.


Figure 2: Advances in Technology

In the last few years, there have been significant advances in technology that application developers can take advantage of to build smarter and more powerful applications. For example, multi-core processors processors enable parallelism of tasks, which means more throughput of data and faster processing to give us real-time responses. Big memory enables us to fit an entire organization's database in memory; this means that we lose the mechanical spinning disk and the latency that it brings. Advances in the design of on-board caches means that data can pass between memory and CPU cores rapidly. In the past, even with large memory, this was a bottleneck as the CPUs were demanding more data and the journey from memory to CPU was not optimal. We can now easily add more servers to our la ndscape to add more processing power or memory, to scale to any size. SAP re-wrote their business application software to exploit the new h ardware fully. SAP worked closely with leading hardware partners, who shared their designs of their new CPU architectures, so that SAP could write the best software. software. Cloud computing technology has matured in the last few years, and is now a compelling deployment option for our customers who do not want to take on the complexity and cost of the installation and maintenance of IT landscapes. Virtualizing machines means lower costs of running enterprise-wide applications where public cloud service based on subscription models reduce the costs and simplify for all.

© Copyright. All rights reserved.


Unit 1: Overview SAP S/4HANA

Figure 3: Time to Rebuild the Business Suite for the Digital World

Since the beginning of enterprise computing, SAP has been rebuilding the business applications whenever major technology shifts have occurred. The following are some key moments in the application development history of SAP: ●

●


●

●

1979 - SAP invents ERP. SAP builds standard business software based on mainframe technology. technology. The name, SAP R/2, supports and integrates major business functions in realtime and handles multi-country and multi- currency implementations. 1992 - With the r ise of the PC, the introduction of client server architecture means another re-write of the applications so that we exploit the power of a 3-tier architecture approach, where processing is split across 3 layers of processing. A new graphical interface encourages end-user productivity. productivity. This is the birth of SAP R/3. 2004 - Now the web is firmly established as the common business network and customers demand better integration with business applications and the Web. SAP develops a new integration application platform, called SAP NetWeaver NetWeaver,, to enable this. Now, all SAP applications run on a common platform, and customers and partners can build and integrate existing application easily, using widely adopted Web standards, standards, such as SOA. The R/3 name was changed to SAP ERP. 2015 - A new wave of advances in hardware architecture brings massive computing power at reduced cost. Huge memory and multi-core processors arrive. The underlying design of the existing SAP applications is not optimal for the new hardware. A re-write of the complete suite is required. This is called SAP S/4HANA. S/4HANA.

LESSON SUMMARY You should now be able to: ●




Unit 1 Lesson 2 Introducing Introducin g SAP S/4HANA S/4HANA

LESSON OBJECTIVES OBJECTIVES After completing this lesson, you will be able to: ●


Introducing SAP S/4 HANA


Figure 4: SAP S/4HANA Next Generation Core and Lines of Business Solutions for the Digital World

SAP S/4HANA S/4HANA is not a single product. Customers can start with the basic components and add to them later. later. SAP S/4HANA Enterprise Management is a great place to start. This is known as the "simplified core". Perhaps it might help to think of SAP S/4HANA S/4HANA Enterprise Management as the replacement for SAP ERP. ERP. Here, we find support for all core business processes, such as order to cash, p rocure to pay, and so on. For many customers, this is where their SAP S/4HANA S/4HANA adoption begins. Seamlessly integrated with the core, we find SAP S/4HANA Lines of Business (LoB) solutions. These are options that can be added at any time, and provide best-in-class lines of business solutions and connections to SAP Business Networks. In the past, we had multiple add-on applications surrounding a core (for example SAP ERP, ERP, SAP CRM, and SAP SRM), but with overlapping models and much redundancy. Now, overlaps overlaps and redundancy have been completely removed from SAP S/4HANA.

Note: SAP S/4HANA S/4HANA is built natively and optimally to run only o n the SAP HANA platform.




Figure 5: Key Aspects of SAP S/4HANA

SAP S/4HANA S/4HANA is built on SAP HANA, so we inherit all of the capabilities of this powerful data management and application platform. This includes advanced text mining, predictive analysis, simulations, and powerful real-time decision support. A brand new user experience is delivered to improve the productivity and satisfaction of business users, and brings the interface up to a consumer-grade experience on any device. SAP S/4HANA S/4HANA can be deployed on premise, in the cloud, or by a combination of both, to provide flexible options to customers.


The data model has been massively simplified. This means that we lost unnecessary tables and, of course, the data in those tables, to shrink the footprint dramatically and to simplify the application design and extensibility.

Figure 6: SAP HANA - The Great Simplifier

The key enabler of SAP S/4HANA from the software software side is called SAP HANA, and it is the platform on which SAP S/4HANA is natively built. In 2005, SAP started researching the possibility of developing their applications built on an inmemory database. When SAP realized that no traditional database vendor had what was needed, SAP began its own in-memory database development. SAP worked with leading chip manufacturers to identify the optimal design of a database that could exploit the full power of the new generation of powerful processors.




The first release of SAP HANA was in 2011. It was positioned as a standalone datamart solution, where customers could capture data from any sources in real-time, load the data to the in memory database, and build BI reports and a pplications on top. Then, SAP began offering SAP HANA based Accelerators, which were deployed as sidecar engines to run alongside traditional SAP ERP functions that were critical to businesses, yet were performing slowly. Around the same time, SAP developed new applications that were completely powered by SAP HANA (for example, Smart Meter Analytics). Around 2012 SAP successfully successfully ported the first already-existing major application, SAP BW, BW, to run completely on SAP HANA. This was quickly followed by the porting of SAP Business Suite. We call this Suite on HANA (SoH), and it should not be confused with SAP S/4HANA. In 2015, SAP started from scratch and rewrote the complete business suite natively to run only on SAP HANA. Unlike Suite on HANA, SAP S/4HANA is a brand new code-line, which works only on SAP HANA. Unlike Suite on HANA, the ap plications do not have to work on any other vendors' database. This means that we were not restricted by the limitation of those databases and could code freely to exploit the full power of SAP HANA.


Figure 7: SAP HANA - The Platform for S/4HANA

SAP S/4HANA S/4HANA inherits the built in capabilities of SAP HANA. This is evident throughout the new SAP S/4HANA S/4HANA a pplications. The following are some of the key capabilities of SAP S/4HANA. ●

Application Services: As well as a database, SAP HANA can provide many application services. This means that many applications can be built in a 2-tier model, rather than a 3-tier model. For example, imagine an application that allows a project manager to check quickly that all team members have competed their timesheets. This could easily be developed as a Web application, where only a Web browser and SAP HANA are required. No application server is needed. This is because SAP HANA can handle the business logic as well as the database services. SAP HANA provides a full development environment with productivity tools supplied in the box. Everything that the developer needs at design time, as well as what is needed at run time, is there.




●

Processing Services: SAP HANA can handle many new types of data. This data includes text, spatial, graphs, and more. However, However, it is not enough to simply store these new data types, we need to be able to build applications that can process and integrate this data with traditional data types, such as business transactions. SAP HANA provides native in-memory engines that process any type of data in real time.

●

Integration Services: SAP HANA has multiple data consumption options built in. We can analyze continual streaming data, read data remotely in any data source, read Big Data stores, such as Hadoop, and synchronize in both directions with remote databases, and devices that collect data (IoT). SAP HANA has built in Extraction, Transformation, Transformation, and Loading (ETL) capabilities, so separate software software is no longer needed to clean, enrich, and profile data from any source.

●

Database Services: SAP HANA is a full in-memory column and row store database that can support both OLTP and OLAP requirements, and is built to run on high-end hardware. It stores data optimally, using automatic compression and, can manage data on different storage tiers, to support data ageing strategies. It has built-in high availability functions that keep the database running and ensure that mission critical applications are never down.



Figure 8: Traditional Approach to Data Model and Application Code

Traditional applications were built on a hierarchical data model. Detailed data was summarized into higher-level layers of aggregates to help system performance. On top of aggregates, more aggregates were built, as well as special versions of the database tables to support special applications. As well as storing the extra copies of data, application code had to be built to maintain extra tables and keep them up to date. These extra tables also needed to be backed up, so even the IT operations were impacted. In addition to aggregates, another inefficiency needed to be removed. Database indexes improve access speed because they are based on common access paths to data. However, However,



they need to be constantly dropped and rebuilt each time the tables are updated, and more code is needed to manage this process. The traditional data model is complex, and a complex data model causes the application code to be complex. It has been found that up to 70% of application code is built specifically for performance of an application and adds no value to the core business function. With a complex data model and complex code, integration with other applications and enhancements are difficult, and simply not agile enough for today's fast-moving environment.


Figure 9: Remove Complexity with SAP S/4HANA

Using the raw power of SAP HANA, we can aggregate on the fly in sub-seconds from any line item table. There is no need for prebuilt aggregates. SAP HANA can generate any view of the data at runtime, all from the same source tables. SAP HANA organizes data using column stores, which means indexes are usually not needed. They can still be created, but usually offer little improvement. Therefore, Therefore, as well as losing the aggregates and indexes from the database, we can also lose huge amounts of application code that deal with aggregates and indexes. We are left with a simplified core data model and simplified application code. It is now much easier to enhance the applications and integrate additional functions.




Figure 10: Massively Reduce Data Footprint

Tables in SAP HANA are compressed automatically, so that we can store huge amounts of data in little space. Further Further data footprint reductions are achieved because we removed huge numbers of tables that are not needed, along with unnecessary indexes.


We can also reduce the in-memory data footprint by implementing data ageing strategies, as follows: SAP HANA can split data across an in-memory tier (we call this HOT storage) and a diskbased tier (we call this WARM storage). storage). All processing and database services are common, which means that a developer does not need to know where the data is physically located; this is handled internally by SAP HANA. The benefit of this is that data that is used less frequently can be moved from HOT to WARM store automatically, automatically, so that we are not filling memory with data that is less useful. This d ata is still available whenever it is needed.




Figure 11: Simplified Applications

We have covered covered the simplification of applications from the technical side, so let us now look at how this simplification applies to the business side.


In traditional SAP ERP finance, financial postings were supported by two key documents, the Finance (FI) document, and the Controlling (CO) (CO) document. These documents provide the required views of the finance data from a legal perspective (FI) and an internal management accounting perspective (CO). There is a lot of overlap between these documents. Application code had to deal with these two types of postings whenever a business event occurred that triggered a financial outcome, for example, a material receipt. With SAP S/4HANA S/4HANA Finance, we now have only one document, called the Universal Journal Entry. A single financial posting is made to one table, which holds all of the information that is needed by both legal and management accounting. The application code is simplified, and any views of the data that are required are created quickly by SAP HANA. This means that we do not lose any business meaning, we just lose the underlying complexity of the application.




Figure 12: Next Generation User Experience with SAP Fiori

With SAP S/4HANA S/4HANA comes a brand new user experience. This is called SAP Fiori. SAP Fiori is not a software product; it is the name of a design approach that was created especially for SAP S/4HANA. S/4HANA. The key aspects of the design are as follows: ●


●

SAP Fiori applications must run comfortably on any device and should present a modern consumer-grade quality. quality. SAP Fiori applications should focus on specific job functions (as opposed to an overcomplicated overcomplicated screen filled with functions for different users).

●

They should offer only the essential information that a user needs to get their job done.

●

They should be intuitive enough to use with little or no training.

●

They should include embedded analytics to support in-process decision making.

●

The look and feel should be consistent across all applications.

●

SAPGUI is still supported, and can b e used alongside SAP Fiori applications to provide for an easy transition for existing SAP customers who are familiar with the classic interface.




Figure 13: Embedded Analytics and Decision Support

What do embedded analytics really look like to a business user? The figure, Embedded Analytics and Decision Support, shows an example of a material planner's new SAP S/4HANA S/4HANA application.


On the left, we see only the critical missing parts that need to be procured. The parts are presented because they need some action. As the planner clicks each part, the main screen presents the shortfall situation in an easy-to-interpret graph for their analysis. The planner can drill down to any part of the g raph to break down the aggregated demand or supply columns to find out why the parts are being consumed too quickly, or why the supply is falling short. The planner can choose an action and then simulate the effect before committing. This is an example of how online transactional processing (OLTP) (OLTP) and online analytical processing (OLAP) are now combined.




Figure 14: Special Case HANA Enterprise Cloud (HEC)

We have two SAP S/4HANA editions: on-premise and cloud. The on-premise edition provides many opportunities for customers to customize customize their system, and all aspects of the solution are maintained by the customer. By using SAP S/4HANA cloud edition in the public cloud, which is shared with other companies, you will have limited oppor tunities to customize the system and SAP will update the system when new releases appear.


If you are a HEC customer, customer, then your solution is hosted by a third party and you access your system via the internet. This might, mistakenly, be called a cloud solution, but, in fact, it is regarded as an on-premise solution. It is simply that your on-premise solution is managed by a third party. This is important to know, because, in this case, the System Conversion scenario, within SAP Activate methodology, applies. This means that the "cloud" in which the HEC on premise edition runs has nothing in common with the SAP S/4HANA S/4HANA cloud edition.




Figure 15: Cloud-Deployment-Models

SAP offers three different Cloud-Deployment-Models such as Private Cloud, Public Cloud, and Hybrid Cloud. Private Cloud is owned by customer, operations and management by customer, or 3rd party or both. The System is assigned to a dedicated customer, access through VPN (Virtual Private Network). It can be o perated on a customer site as well as remotely. remotely.


Public Cloud is one system used by different customers. It is operated by Service Provider, Provider, not by customer and has self-service access. Hybrid cloud is a mixture of two or more deployment models. It is integrated by standardized or custom interface technology, supporting the transfer of data and transaction.

Figure 16: SAP's Cloud-Deployment-Models




SAP Business Cloud contains: SAP Data Center, SAP Managed Operations, and SAP Support for both deployment models Private Managed Cloud, and Public Managed Cloud.

Figure 17: SAP the Cloud Company Powered by HANA


SAP as a Cloud Company has three different services: SAP HANA Enterprise Cloud (HEC), SAP HANA Cloud Platform (Platform as a Service, PaaS), and SAP Cloud Apps (Software as a Service, SaaS).

Figure 18: HEC AND HCP Side-by-Side

One of the most important innovations innovations in SAP HANA is that it allows the a pplications that users love to use. No longer do we have to have applications that let us take action, transactional applications, and other applications that let us do the analysis we need. This division was a function of the limitations of older databases and forced complex landscapes with multiple technologies and terrible user experiences. With SAP HANA, applications that




provide "in-context analytics" analytics" are easy to build. This not only brings efficiency to the business, but also simplifies IT landscape by requiring fewer technologies and servers. SAP HANA ENTERPRISE CLOUD

●

Run SAP applications in a private managed cloud environment

●

Fully Fully managed private and dedicated cloud

●

●

Designed for mission critical operations, with no tradeoffs on performance, integration, security, failover, and disaster recovery SAP manages the HANA cloud environment from infrastructure infrastructure to applications

SAP HANA CLOUD PLATFORM


●

Build new applications in an app lication development environment environment running in the cloud

●

Robust lifecycle management and application development services

●

Build extensions to core SAP applications and run in the cloud

●

Build extensions to SaaS applications and run in the cloud

Figure 19: SAP HEC - Nobody Knows SAP Better Than SAP

SAP HEC is flexible, secure, scalable, and offers Private Cloud.




Figure 20: SAP HANA Enterprise Cloud Gives You Flexibility

SAP HANA Enterprise Cloud Gives You Flexibility. It follows the idea of scalability of Cloud Computing. This means scale in or scale out of infrastructure resources if required.


Figure 21: SAP HANA Enterprise Cloud Core Services

SAP HANA Enterprise Cloud Core Services refers to assessment on technical aspects, Onboarding and Migration toward SAP HANA Enterprise Cloud, Cloud Infrastructure Infrastructure with enterprise-class Service Level Agreements, and Application Management providing application incident support and monitoring.




Figure 22: The Value of HEC in the Acceleration of Digital Transformation

●

Simplicity, Experience, Optimization, Peace of Mind, A Foundation for Innovation

●

Simplicity - allowing customers to deploy and realize the benefits of HANA quickly

●

Experience - supporting over 1,100 instances of SAP HANA, no one else comes close

●

●


●

Optimization - designed to support any SAP HANA landscape, no o ne knows SAP HANA better than SAP Peace of Mind - providing an integrated support model that feeds into HANA Development A Foundation for Innovation - combined with HCP and AMS for HEC provides customers a comprehensive comprehensive cloud portfolio and foundation for continuous innovation

LESSON SUMMARY

You should now be able to: ●








UNIT 2

Overview Overview of the Implementation to SAP S/4HANA

Lesson 1

The Three Ways to SAP S/4HANA

22

Lesson 2

Basics about Migration and Tools for Migration to SAP S/4HANA

28

Lesson 3

Migration to SAP S/4HANA

32

Lesson 4

Migration to SAP S/4HANA cloud

35

Lesson 5


SAP Activate

39

UNIT OBJECTIVES ●

Describe the three different scenarios to SAP S/4HANA

●

Explain Explain what migration is i s and describe the different tools of Migration

●

Describe the migration to the on premise edition SAP S/4HANA

●

Describe Describe the migration to SAP S/4HANA cloud

●

Describe how SAP Activate supports your implementation



Unit 2 Lesson 1 The Three Ways to SAP S/4HANA


Describe the three different scenarios to SAP S/4HANA

The Three Ways to SAP S/4 HANA


Figure 23: SAP S/4HANA: One Code Line, Different Products

In the figure, SAP S/4HANA: One Code Line, Different Products, the icons on the top righthand corner, SAP S/4HANA S/4HANA and SAP S/4HANA S/4HANA cloud, are very important. This is the first thing we have to distinguish because the on-premise system is basically what was released at the end of 2015 with release number 1511. We also have the SAP S/4HANA S/4HANA cloud, which is software as a service (SaaS). This is a real public cloud, basically. When we say cloud, we are normally not talking about the HANA Enterprise Cloud (HEC), which could be seen as the on premise edition in a hosted environment. The Business Suite, which sometimes comes into play when we talk about SAP S/4HANA Finance was previously known as Simple Finance. So these are the differentiators when we talk about SAP S/4HANA. S/4HANA.




Figure 24: Transition to SAP S/4HANA: The 3 Transition Scenarios (1)

SAP HANA Enterprise Cloud (HEC) is an on-premise system that can be reached in the cloud. It is an on-premise system system that can be converted as described in the "System Conversion" Conversion" scenario.


. n o i t i d E y r e v o c s i D Figure 25: Transition to SAP S/4HANA: Scenario: New implementation

The new implementation targets customers who want to move from their legacy system, whether an SAP ERP System or a non-SAP System, and implement SAP S/4HANA from scratch. This scenario is also known as a Greenfield approach. The benefits for you, as a customer, customer, are that you can re-engineer and simplify your business processes on SAP S/ 4HANA , taking advantage of the latest and best ready-to-run business processes. processes. You can use predefined data migration and best practices to start you off in a guided implementation. You can introduce SAP S/4HANA quickly and cost-effectively, and rapidly adopt additional innovations later. In a new implementation, you can also take full advantage of SAP Activate, the innovation innovation adoption framework for SAP S/4HANA.


Unit 2: Overview of the Implementation to SAP S/4HANA

The volume and complexity of your data migration, as well as the number of data migration objects affects the duration of the new implementation. The volume and scope of the business processes that you want to implement on SAP S/4HANA also affect the duration.

In on premise, you first install SAP S/4HANA with the software provisioning manager and then perform an initial data load from a source system, either through file upload from a legacy system, or, if the source is SAP, through direct system connection. The tools used are SAP data services for on premise or the SAP landscape transformation for the cloud.


Figure 26: Transition to SAP S/4HANA: Scenario: System Conversion

System conversion is for customers who want to convert their current system into an SAP S/ 4HANA system, bringing an ERP core system, whether it is already using SAP HANA as a database, or it is o n another database, to SAP S/4HANA. S/4HANA. The benefit is that you can move to SAP S/4HANA without a reimplementation; there is no disruption to your existing business processes and, once the conversion conversion is completed, you can reevaluate your existing existing process flows and adapt them as you want. The parameters that influence the duration of a system conversion conversion are technical as well as functional. You need to consider the number of systems that you have in your current ERP landscape and that you want to bring to SAP S/4HANA, and the actual size of your productive source database. In terms of the functional influencers, you need to consider, consider, for example, how many company codes you have, how many ledgers, and so on. The steps for a system conversion are as follows: Check your add-ons, business functions, and potential industry solutions using the maintenance planner. This is to ensure the SAP S/4HANA compatibility of those components.




If there are compatibility issues, a de-installation tool is available for enabled SAP and partner add-ons. Once you have completed the checks for add-ons and for industries, pre-check to identify further preparation steps, such a s, the activation of the customer-vendor-i customer-vendor-integration. ntegration. An optional check, which you can conduct at any time, is a custom code check to ensure code compatibility with SAP S/4HANA. Your custom code continues to run if the SAP S/ 4HANA simplifications and its new data model allow it. The custom code check tool identifies conflicts where, for example, custom programs programs access data structures that changed with SAP S/4HANA. The custom code checks are based on the simplification database content, which contains all incompatible changes of the data model, including business functions in SAP S/ 4HANA. Once you have completed all checks and adjusted your custom code, the third step is to run the actual conversion. You can run the actual conversion in one step, using the database migration option for software update manager. With that, you have performed a system conversion.


. n o i t i d E y r e v o c s i D Figure 27: Transition to SAP S/4HANA: Scenario: Landscape transformation

Landscape transformation targets targets customers who want to consolidate their landscape, or to bring data into an SAP S/4HANA system selectively. Examples of a selective transformation transformation are Central Finance, where the finance function is centralized, centralized, and you can take advantage of the universal journal and of statutory reporting using central finance. Another example is the selective carve out of a company code, which you want to bring to SAP S/4HANA as a front runner in your enterprise for SAP S/4HANA. The benefits are such that, with the landscape transformation, you can perform a selective transformation transformation to SAP S/4HANA, S/4HANA, and a llow a phased approach, focusing on areas with high return of investment, investment, a low total cost of implementation, and adapt to SAP S/4HANA S/4HANA in stages.



With the system consolidation, with harmonized and simplified processes, you will reduce the number of systems in your current landscape, lower your total cost of ownership, and improve the quality of your master da ta. Project parameters that influence the duration are, for example, the number of selected units that you want to consolidate, or the number of company codes that you want to carve out. What are the steps to consider? ●

●

The consolidation of clients from different source systems into one new or existing SAP S/ 4HANA system using the system landscape transformation. Next, consider the selective data transformation, where you carve out single entities and migrate selective applications, applications, such as central finan ce using the system landscape transformation.

Landscape transformation is a scenario that we will n ot cover in detail in this course. This course focuses on system conversion, as well as new implementation in the cloud and new implementation on premise. Later, in the tool section, we provide some links to more information on the landscape transformation, as well as the other two transition scenarios.


Figure 28: Transition to SAP S/4HANA: The 3 Transition Scenarios (2)

The figure, Transition to SAP S/4HANA: The 3 Transition Scenarios (2), compares the three transition scenarios on a high-level view and also on the data view. On the top left-hand side, you see a New Implementation, you see "deg ree of standardization" and "size of the repository to be kept" on the x-axis. New Implementation here means you only migrate master data and selected transactional data. From a transactional point of view, it is basically open sales orders, purchase orders, accounts payable receivable and so on. It is important to note that you can not migrate historical data, that means, closed purchase orders that are already done, billed, you cannot migrate. Why? Because we are using application interfaces. So, if you migrate such a record, the system would treat it as transactions that create a new order, order, for example. No historical data is possible.

Note: No historical data is possible in a new implementation scenario!

On the contrary, on the bottom right-hand side of the figure you see System Conversion. This is where you convert a complete existing system: The data never actually leaves the system.

© Copyright. All rights rights reserved.



In New Implementation, you have a legacy system, you pull the data ou t, and load it into the new system, so you have an old one you have to retire and you h ave a new system. With System Conversion, data never leaves the system, there is never a second system in place. Data gets converted into an SAP S/4HANA S/4HANA system, which also converts all the historical data to a new structure if needed. This is beneficial because you have your historical data, but again it depends on how big the system is because that might influence the runtime. If you have a 4 to 5-terabyte system system where 80% of it is historical data that you are not looking at, system conversion might be a thing you want to do. Discuss this up f ront, maybe do some Data Volume Volume Management (DVM), this will help you decide whether you want to go for a System Conversion Conversion or a New Implementation. Landscape Transformation Transformation is in between; for a system consolidation, it is worth a lot; for carve-out, it is of course a bit less but it is still moving data from one system to another. This figure gives you a good overview how the system differs from an implementation point of view, and what you have to consider when planning such a p roject. LESSON SUMMARY


Describe the three different scenarios to SAP S/4HANA S/4HANA




Unit 2 Lesson 2 Basics about Migration and Tools for Migration to SAP S/4HANA


Explain what migration is and describe the different tools of Migration

Migration


Figure 29: What Is Data Migration?

We often talk about Data migration without defining it. The important point to note is that simply moving data is insufficient; the goal of a data migration project is not simply to move and transform data from one system/ format to another; rather, it is to ensure that the moved data is of high q uality, uality, is fit-for-use, and supports the underlying bu siness processes processes and operational goals of the organization.

Figure 30: Data Migration Happens

Data migration happens in a lot of different ways, such as, merger and acquisition, divestitures, divestitures, data comes in, data goes out, application consolidations, business transformation projects, or of course new implementations. Data migration is not a one-time



Lesson: Basics about Migration and Tools for Migration to SAP S/4HANA

event. If you have, for example, a scenario of a central system or you start with a single company code first, you have a migration now, and you will have migrations in the future - for example, you start implementation with a certain country with SAP S/4HANA, and then you would like to load additional countries into the same system. Risks around data migration should be addressed very early so that you can manage that risk. The opportunity migration offers is the possibility to start with better data, specifically if you are coming from non-SAP as you have to do some sort of a data h armonization when you go to SAP S/4HANA. For data quality, quality, take the opportunity to ensure that all the data that you need in the system is in a good shape.

Figure 31: The Problem with Migration Projects


Analysts say that more than 80% of data migration projects run over time and over budget. Cost overruns by 30%, time overruns by an average of 40% percent, and 80% of organizations underestimate underestimate costs by at least by 50%. Over half of all ERP implementations are reported as challenged due to data integrity or data accuracy problems.

Figure 32: Transition to SAP S/4HANA: Migration Tools Overview

As you see in the figure, Transition to SAP S/4HANA: Migration Tools Overview, there is one tool for each scenario; the only exception is the New Implementation. On the top row, you see the New Implementation for on premise or the HEC ( the on-premise version in a hosted




environment). The migration tools we recommend are SAP Data Services. For the cloud we use the Embedded Migration Cockpit. The Legacy Migration Workbench (LSMW) (LSMW) tool can be used, too, but it is not recommended. LSMW does not support the new SAP S/4HANA data structures, such as business partner master data. Furthermore, LSMW does not support best practices, as SAP Data Services does.

Figure 33: SAP Data Services

SAP Data Services is a tool, not a service. It is a full blown ETL (extract, transform, transform, load) tool.


With Data Services, you can basically connect to all the sources, such as BW, an SAP system, Oracle apps, HANA, databases directly, directly, structured and unstructured files, data in Excel sheets or Access databases. You You can do all the transformation in SAP Data Services. It provides content with a lot of pre-transformed pre-transformed workflows and data flows. Everything is preconfigured and you have a lot of checks available, you do not have to start from scratch. When you install Data Services it is empty, but you can download content for free. You can use that content in your migration project. From a loading perspective, you have either batch or real-time processes, and you can load into various target structures. structures. In our scenario SAP S/4HANA S/4HANA would be the target environment.

Figure 34: SAP Information Steward Complements SAP Data Services



Lesson: Basics about Migration and Tools for Migration to SAP S/4HANA

The SAP Information Steward supports business users as well as I T users to ensure overall data quality. Business users can see how their information measures up against information governance rules and standards. IT can share data quality metrics with business users and involve them in owning the data problem.

Figure 35: SAP Landscape Transformation

SAP Landscape Transformation Transformation tool helps you to analyze, plan, and realize transformation projects within common business scenarios, such as corporate mergers and acquisitions, divestitures, divestitures, internal reorganizations, and projects to harmonize existing business processes. ●


Analysis Perform analysis for transformation Compare repository and Customizing of systems

●

Leverage Sell, Buy, and Restructure Sell or buy a company or parts of it Execute business unit reorganizations

●

Unify and Transform Data Gain transparency in financials and logistics Harmonize master data

●

Consolidate and Reduce IT Costs Consolidate systems with matching release or across releases

●

Migration Projects: Powerful tool for SAP  SAP migration Migrate all data, including history

LESSON SUMMARY


Explain what migration is and describe the different tools of Migration



Unit 2 Lesson 3 Migration to SAP S/4HANA


Describe the migration to the on premise edition SAP S/4HANA S/4HANA

Migration to S/4HANA S/4HANA


Figure 36: SAP S/4HANA New Implementation: Data Migration Functionality (On-Premise)

The figure, SAP S/4HANA New Implementation: Data Migration Functionality (On-Premise), outlines how the solution works, including all of the functionality provided with the migration content. In the figure, the steps shown are as follows: Legacy data environment The legacy data environment refers to the source systems for the migration. The legacy environment can be any third-party source system that is supported by SAP Data Services connectivity (almost all sources are supported as SAP Data Services supports ODBC protocol). SAP systems systems on a lower release that cannot be upgraded could also be the legacy system. The Rapid Data Migration package comes with pre-built content for SAP S/4HANA. Extract and profile Data is extracted from the source and placed in a staging area in SAP Data Services. At this point, you can conduct technical profiling with SAP Data Services. Additionally, Additionally, you can start profiling the source systems at an early stage, using SAP Information Steward. The Data Services environment is used as a staging area that extracts and profiles the



Lesson: Migration to SAP S/4HANA

data. The profiling can include looking at patterns in postal codes. For example, what percentage of postal codes has 5 digits? It could also be how many material numbers follow a specific pattern. You might be interested interested in how many unique IDs there are in a certain table. The extraction and profiling of data is an important first step in a data migration project in order to assess the quality of the source data and mitigate the overall risk for the data migration project to be successful. Cleanse, transform, and validate This includes updating the data so that it meets specific patterns, mapping and transforming the data according to rules, and validating data against the SAP S/4HANA business context. This can involve combining two fields into one, splitting fields, updating the data in a field to match certain rules (for example, telephone number formats), and validating data against required fields and lookup values from the SAP S/4HANA S/4HANA context and configuration. In addition, duplicate data records can be eliminated with this step. SAP configuration extraction Once the data is extracted, it is important to know how the data needs to be prepared for SAP. The solution reads business context and configuration settings in SAP S/4HANA to help map the data. As part of an SAP S/4HANA implementation, the system is configured with many values, such as cost centers, company codes, and country values. This step requires knowledge of the SAP business context to transform and then validate the data in Data Services against the SAP configuration and customisation settings. Mapping of the source data normally requires mapping fields that comply with the SAP configuration. Load


Once the data is transformed and validated, it is then loaded into the SAP S/4HANA system. This is normally loaded through IDocs and WebServices, WebServices, but can also be loaded using files and BAPIs. Reconciliation Reconciliation looks at what was actually loaded versus what was expected to be loaded. This ensures that all data was loaded and is ready for use. Dashboards and business reporting Throughout the process, dashboards are available for people involved to remain informed about the status of the migration. Additionally, Additionally, the migration project often sets data quality expectations and governance around data management. The entire process of assessing the data, validating it according to business rules and SAP context lays the groundwork for ongoing data governance. For example, if customer records were checked to ensure that every customer had a t least two associated contact persons, this process can continue to ensure that all new customer records have two contact persons.




Figure 37: Rapid Data Migration Solutions

●

●


Service Marketplace is the standard entry point for Rapid Data Migration. Here you find all additional solutions such as non-SAP S/4HANA, SAP ERP, SAP CRM, SAP Billing for Utilities, cloud solutions from SAP, SAP SuccessFactors, C4C, Workforce Analytics, BW, or SAP Hybris Marketing, even for retail. This gives you an overview on how much content is available. In addition we offer Rapid Data Migration to SAP S/4HANA on premise. There is an SCN community on the SCN community network/dm (data migration).



Describe the migration to the on premise edition SAP S/4HANA S/4HANA


Unit 2 Lesson 4 Migration to SAP S/4HANA cloud


Describe the migration to SAP S/4HANA S/4HANA cloud

Migration to SAP S/4HANA S/4HANA cloud


Figure 38: SAP S/4HANA New Implementation: Data Migration to SAP S/4HANA Cloud in Detail

The move to the SAP S/4HANA cloud can be considered as a New Implementation project with classical data migration activities. Data transfer is supported by a data migration server toolset included in the S/4HANA stack (SAP Landscape Transformation (SLT)). In cooperation with SAP Service Center, the virtual private network (VPN) connection connects your source system with the cloud target system. You can migrate master data such as the following: ●

Customer & Vendor (source system = classic customer, vendor; target system = SAP S/ 4HANA Business Partner)

●

Material Master

●

Bank Master

●

Activity Types, Activity Type Groups

●

Cost Centers, Profit Centers, Profit Center Groups, Cost Center Group




●

Inventory Balances

The figure illustrates the following: ●

(a) SAP Landscape Transformation (SLT) Tool required on customers OP system

●

(b) Customer needs to establish VPN connection to OP System

●

(c) For For new customers (legacy migration) a template-based approach is used (XLS)

●

SAP Cloud Operations: provision of cloud instance

●

Customer: Implement configuration in target

●

Customer: Implement integration to SAP Business Suite System or use template-based approach

●

Service Center: Re-Implement customer e nhancements

●

Consulting Service:

●

-

Maintain data mapping (Business Objects to be transferred) in SLT SLT

-

Transfer of master data; Transfer of transactional data

Customer: Data Validation



Figure 39: SAP Landscape Transformation - Outlook: S/4HANA Data Migration / Landscape Transformation Platform

SAP legacy systems are connected to the SAP Landscape Transformation tool through LAN/ WAN. While non-SAP legacy systems are connected through file upload with excel templates pre-configured by SAP. Transformed data will be inserted into SAP S/4HANA Cloud with standard interfaces like BAPI.


Lesson: Migration to SAP S/4HANA cloud

Figure 40: SAP S/4HANA Embedded Migration Cockpit: Cloud (file upload)

If you set up a cloud system, there is an implementation cockpit. In this end-to-end migration cockpit you can select "migrate your data". If you click it, the migration tool starts and asks you to identify relevant migration objects. The migration tool automatically checks what kind of business processes you activated. Based on your selection it only shows you the relevant migration objects. The migration tool generates the file templates, so there is no central storage location. With this, we can ensure that you always have the most up-to-date templates for your migration project. Finally, Finally, you start and monitor the data migration process. This phase handles value mapping, the error handling, and the productive load into the system. This is a guided procedure.

. n o i t i d E y r e v o c s i D Figure 41: Key Takeaways for Implementation Scenarios

There are three different implementation scenarios with different starting points and different prerequisites. prerequisites. What might seem as the best scenario at first might not really be the best for the specific customer; therefore, it is necessary to know all the details around the three different implementation scenarios. The Best Practices for data migration can jump-start migration. Data Services with its capabilities is specifically for complex data migration. It can reduce migration costs, especially using Information Steward.




Figure 42: Where to Find More Information About S/4HANA and SAP Activate

The figure, Where to Find More Information About S/4HANA and SAP Activate, lists more information sources. On the top left-hand side is the central SAP S/4HANA page. It's a highlevel entry. Then you have the SAP Activate page. This is the central Activate page: sap.com/activate. There is a community page on S/4HANA with a lot of discussions and a lot of additional material that you can use. The bottom right―hand side of the figure shows the SAP Best Practices Practices page where you can find the Data Services content. All SAP Best Practices are stored there. Even for non-SAP S/ 4HANA purposes, you can take a look there as well.


LESSON SUMMARY


Describe the migration to SAP S/4HANA cloud



Unit 2 Lesson 5 SAP Activate

LESSON OBJECTIVES

After completing this lesson, you will be able to: ●


SAP Activate



Figure 43: SAP Activate

SAP Activate is the combination of SAP Best Practices, tools, and Methodology to help customers simplify and accelerate the adoption of SAP S/4HANA. S/4HANA. There are three main components to SAP Activate, as follows: ●

●

SAP Best Practices - Ready configured business processes optimized and following industry best practices Methodology - SAP guidance to ensure a well-managed and accelerated implementation and continuous optimization



●

Guided Configuration - tools to help activate best practices content and make customized customized adjustments -

New implementations

-

System conversion

-

Landscape Transformation

Figure 44: SAP Activate - Methodology


SAP Activate methodology is the successor of the ASAP and SAP Launch methodologies and offers the following advantages: ●

●

●

Provides one simple, modular, and agile methodology that supports all SAP S/4HANA transition scenarios Provides Provides full support for initial deployments, and provides support after go-live for continuous business innovation Enables co-innovation co-innovation with customers and is accessible for partners who can add their own content, perhaps to support specific industry or country requirements requirements

●

Figure 45: SAP Activate - The Innovation Adoption Framework (I): Introducing SAP Activate



Lesson: SAP Activate

The goal and the business value of SAP Activate is to provide customers with a faster and less service-intensive service-intensive initial implementation, whether it is in the c loud or on premise. In addition, the goal of SAP Activate Activate is to provide the customer with the ability to innovate and adopt innovations rapidly throughout the entire product lifecycle. Once you have completed an initial implementation of SAP S/4HANA, you can go back later and apply additional innovations from the wealth of SAP S/4HANA S/4HANA new business scenarios or improved improved business scenarios and implement them. By applying SAP Activate, you put yourself in a position where you can go back and adapt more and more business scenarios and enjoy the benefits of a faster and less service intensive implementation. This leads to a reduced time to value, whether it is for the initial implementation or subsequent implementations, and a reduced total cost of ownership. ownership.


Figure 46: SAP Activate Methodology on SAP JAM

SAP Activate methodology is available to end users through the Methodology Jam community that is open to customers and partners, as well as SAP internal users. The landing page contains overview information, latest updates, and key links. From From the landing page, users can navigate to a specific methodology phase and explore the key project management deliverables in the phase. If users want more information, they can access the deliverable details that provide a description of the deliverable and appropriate accelerators that help complete the process. In addition to this structure, the Jam space contains collaboration areas. areas. Users can comment and provide feedback on each item in this group, and can start discussions and engage with SAP experts, or share examples with community. To request access a ccess to SAP Activate Acti vate methodology, metho dology, use this t his link: http:/ ht tp:// /scn.sap.com/ community/asap-methodology/blog/2015/07/09/sap-activate-methodology-jam-space-we-are-open-come-in




Figure 47: Process Modeling & SAP Activate with Solution Manager

SAP Activate is available with Solution Manager 7.2 or higher.

Note: Customers have to do an update if they are not already in the 7.2 version.

●

Customers ask for process models and p re-configuration

●

SAP delivers SAP Activate -

-

-


-

-

●

●

SAP delivers content for all S/4HANA S/4HANA editions; all processes are graphically modeled and extendable; SAP delivers new best practice content for each S/4HANA release Customers view process models in the 1content cloud Customers then go into a private cloud (CAL) and adapt SAP processes with SAP Solution Manager 7.2 to customer requirements. New SAP Solution Manager 7.2 process modeling environment optimal for this job Customers then take delta scoping into their live SAP Solution Manager 7.2 and start build phase SAP Solution Manager 7.2 offers the same trial capabilities as SAP S/4HANA

New customers use the SAP Activate pre-configuration to accelerate the build phase All SAP Activate content is available with and fully integrated into SAP Solution Manager 7.2




Figure 48: Best Practices for SAP S4HANA, on Premise Edition


SAP Best Practices for SAP S/4HANA provide ready-to-run digitized analytical and operational business processes that cover the fundamental business processes of an enterprise, often referred to as the baseline. Whether you want to streamline your procure-toprocure-topay processes, optimize your order to cash flow, or take ad vantage of simple finance, we provide a pre-configuration for many of your business priorities. Let us look at an example of a new financial implementation. You can use parallel accounting to address multi-national reporting requirements. requirements. You You do not need to create a standard chart of accounts, it already exists. Best practice for closing books, remaining IFRS compliant, tracking debits and credits, and calculating taxes are all pre-configured in your solution. These business processes are easily integrated with other cloud solutions, such as SuccessFactors SuccessFactors Employee Central, or the Ariba Network. SAP Best Practices also guide customers through the migration process to SAP S/4HANA, whether they migrate existing SAP ERP solutions from a non-SAP database or from legacy systems. systems. SAP Best Practices covers integration and migration fundamentals. In summary, whether it is a new implementation, a conversion, or a landscape transformation, you do not start from a blank slate. Instead, SAP Activate gives you sample data, clear guidelines, and step-by-step step-by-step directions on how to move from your current landscape to your goal. With the next releases of SAP S/4HANA in 2016, we also plan to deliver first SAP Best Practices for Line-of-Business Line-of-Business and Industry extensions on top of the baseline, plus additional knowledge and information on integration and extensibility for User Experience, Business Analytics, and for enhancing SAP processes to fit your needs.




Figure 49: Best Practices for SAP S4HANA, on Cloud Edition

SAP Best Practices for SAP S/4HANA provides the system and is responsible for all maintenance and upgrade operations. You benefit from the latest innovations by receiving quarterly updates provisioned in your solution automatically. This option may appeal to you if you prefer standardized standardized business processes and if you want to take advantage of fully deployed business scenarios scenarios in the c loud for a quick time to value. Currently, SAP offers best practices for all deployment options of SAP S/4HANA, cloud edition, Enterprise edition, Project Services edition, and Marketing edition.


Imagine that you are looking for better insight into your customers. With customer analytics in SAP S/4HANA cloud marketing edition, you can identify interests and create a 360° view of people in your ecosystem. Segmentation of contact data and the preparation and execution of campaigns then support you to transform the gained insight to action. You can transform anonymous contacts into high-value customers and brand advocates. If you are a service provider and you want to manage customer projects, SAP Best Practices for SAP S/4HANA S/4HANA cloud project services edition provides an end-to-end process of selling services, managing staffing, recording recording working times, and creating customer invoices invoices with a ll necessary details. Note that the available scope of pre-configured processes for SAP S/4HANA, enterprise edition equals the scope of the on-premise baseline. In addition, the solution scope of SAP S/ 4HANA, marketing edition, and project services edition is fully determined by the available SAP Best Practices. As with the on-premise version of SAP S/4HANA, the SAP Best Practices included with the SAP Activate guide you through the migration, integration, and fine-tuning of SAP S/4HANA.




Figure 50: Discover and Download SAP Best Practices Content


The figure, Discover and Download SAP Best Practices Content, shows the different ways to discover SAP Best practises.

Figure 51: Base Scope for Best Practices

The ready-to-run business processes delivered with SAP Activate support core industry requirements requirements and cross-enterprise priorities, priorities, for on premise as well as for the cloud. This table provides an overview of the business priorities for which we provide coverage with preconfigured processes.




SAP Best Practices baseline supports the requirements requirements of 11 core industries, not including industry extensions. These industries are Consumer Products, Wholesale Distribution, Life Sciences, Chemicals, Mill Products & Mining, Automotive, Automotive, High Tech, Industrial Machinery & Components, Aerospace & Defense, (Engineering, Construction & Operations), and Professional Services. The detailed breakdown of available pre-configured processes by line-of-business line-of-business or by endto-end solutions is available through the SAP Activate JAM community or in the business scenario recommendation tool. SAP Best Practices for SAP S/4HANA are tailored specifically to accelerate and simplify the adoption of SAP S/4HANA. Processes Processes delivered with SAP Best Practices support core industry requirements requirements and cross enterprise priorities . The following are the key capabilities: manage multiple geographies, divisions, subsidiaries, and ledgers; global and country-specific content; and analytical content included. Why Now, What Is New In the digital economy every company needs to think about d igitizing its business to simplify and innovate its business from operations to business models. SAP Activate gives you the freedom to get started quickly with SAP S/4HANA. S/4HANA. Using SAP Activate with SAP S/4HANA offers the following benefits:


●

Provides Provides you with the tools needed for an assisted implementation

●

Continuously supports you in the adoption of latest innovations innovations

●

Runs faster, faster, less service intensive initial deployments, deployments, in the cloud or on-premise

●

Allows you to use one methodology for any deployment mode and project size

●

Delivers sample organizational organizational and master data as part of the product to start with model companies





Discovery Edition

Would you like to learn more? Get access to the rest of this training title and to the rest of the SAP Learning Hub catalog by subscribing to a paid edition. http://go http://go.sap.com/tra .sap.com/training-cer ining-certification tification/learnin /learningghub.html#compare

Note: You are currently exploring the SAP Learning Hub discovery edition the free of charge  trial environment for our on-demand learning solution.




S4H100

Recommend Documents