the transition to sap...

© 2

015

SAP

SE o

r an

SAP

affilia

te c

ompa

ny. A

ll rig

hts

rese

rved

.

Enterprise Management

The Transition to SAP® S/4HANA

Table of Contents3 Introduction

3 SAP S/4HANA – At a Glance

4 SAP S/4HANA, On-Premise Edition and SAP S/4HANA, Cloud Edition

8 The Road to SAP S/4HANA

15 The Transition to the On-Premise Edition of SAP S/4HANA

16 SAP S/4HANA Finance, On-Premise Edition

19 SAP S/4HANA, On-Premise Edition 1511

22 New SAP Customer

25 The Transition to the Cloud Edition of SAP S/4HANA

2 / 27

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

DISCLAIMERThis document outlines our general product direction and should not be relied upon in making a purchase decision. This document is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this document or to develop or release any functionality mentioned in this document. This document and SAP’s strategy and possible future devel-opments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or noninfringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.

Safe Harbor Statement This document is intended to outline future product direction and is not a commitment by SAP to deliver any given code or functionality. Any statements contained in this document that are not historical facts are forward-looking statements. SAP undertakes no obligation to publicly update or revise any forward-looking statements. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. The timing or release of any product described in this document remains at the sole discretion of SAP. This document is for informational purposes and may not be incorporated into a contract. Readers are cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

3 / 27


SAP S/4HANA – AT A GLANCEOver the years, growth in transactional databases and other data sources as well as their associated systems have complicated enterprise applications and infrastructure. This, in turn, has complicated and stymied many organizations’ ability to meet the needs of their business, whether that is timely access to analytics, the ability to absorb new business models, or being able to create new, streamlined business processes. In response, SAP is rewriting and simplifying our applications to take advantage of our in-memory business platform. This new and unique enterprise application is called the SAP® S/4HANA suite. It removes previous technological barriers and helps our

companies manage complexity and Run Simple across their digital value chains.

What is SAP S/4HANA? SAP S/4HANA is a new business suite of applications designed to Run Simple in a digital and connected world. It is built on the advanced in-memory computing platform SAP HANA® and designed on the modern SAP Fiori® user experience (UX) (see Figure 1). SAP S/4HANA offers:

• Complete choice of deployment – cloud and on premise

• Instant value across lines of business and industries

• The ultimate sophistication: simplicity

Introduction

Figure 1: SAP S/4HANA – At a Glance

Internet of Things

Business networks

Social networks

SAP Fiori® user experience (UX) Role-based user experience for all devices

Applications and extensions for SAP S/4HANA Instant insight-driven applications for

all lines of business and industries

SAP HANA® platform In-memory platform for all data

On-premise edition

Cloud edition

SAP® S/4HANA

Native integration for hybrid scenarios from SAP companiesAriba | Concur | Fieldglass | hybris | SuccessFactors

People

Devices

Big Data

4 / 27


Customers Have the Choice SAP S/4HANA can be deployed on premise, in the cloud, or as a hybrid to give real choices to customers. Successful customers traditionally define their “core business” or “core processes” as the way that they can differentiate from competitors and realize a competitive advantage. Those areas are often kept in an on-premise environment in which customers require the maximum amount of flexibility, have all configuration possibilities, and modify the business logic in SAP software according to their needs. Here, the on-premise edition of SAP S/4HANA would be the go-to solution. In other business areas in which differentiation is not essential but high standardization is required, it would be ideal for customers to adopt industry best practices. The cloud edition of SAP S/4HANA is the ideal choice in this case because it provides best practices right from the start and reduces the total cost of ownership.

SAP S/4HANA, ON-PREMISE EDITION AND SAP S/4HANA, CLOUD EDITION The business scope for each edition was designed to offer maximum choice to customers in align-ment with their business requirements:

• The on-premise edition of SAP S/4HANA offers a business scope similar to current SAP Business Suite software in terms of coverage, functionality, industry, and languages. Within this scope, SAP S/4HANA also includes the transformational simplifications delivered with the SAP S/4HANA Finance solution (SAP Accounting powered by SAP HANA) as well as a planned integration with the SAP SuccessFactors® Employee Central solution and the Ariba® Network. We intend to offer a yearly innovation cycle through innovation

packages for the on-premise edition. The next innovation package is planned for the end of 2015.

• The cloud edition of SAP S/4HANA covers specific business scenarios for the marketing line of business and for the professional services industry. It also covers the most essential scenarios to run an entire enterprise in the cloud with a digital core, which includes finance, accounting, controlling, procurement, sales, manufacturing, plant main-tenance, project system, and product lifecycle management, plus integration with SAP Success-Factors Employee Central, the Ariba Network, the SAP hybris® Marketing solution, SAP Fieldglass software, and the SAP Jam™ social software platform. Three offerings are currently available as part of the cloud edition of SAP S/4HANA:

– SAP S/4HANA, cloud marketing edition – for the marketing line of business

– SAP S/4HANA, cloud project services edition – for the professional services industry

– SAP S/4HANA, cloud enterprise edition – for a full enterprise resource planning (ERP) scope

We intend to offer a quarterly innovation cycle for the cloud edition.

All SAP Business Suite customers have an option to move to SAP S/4HANA. The details are dependent on the source system of SAP Business Suite and the target edition of SAP S/4HANA. For a move to the on-premise edition of SAP S/4HANA, we offer a one-step procedure for the majority of current SAP Business Suite customers. This one-step procedure includes the database migration (for those customer companies not yet on the SAP HANA database) plus the installation of the SAP S/4HANA core with the appropriate innovation packages.

5 / 27


The cloud edition of SAP S/4HANA requires an initial setup using guided configuration utilities. In this edition – in which SAP is responsible for the operations, including the software change procedures (remember: quarterly innovation cycles) – the degree of flexibility is limited compared to the on-premise edition. For example, customer modifications to SAP software objects are not allowed in these editions.

Accordingly, we consider the transition to the cloud edition as a new implementation for our customers. On a long-term road map into the cloud, a customer might choose a path where the initial move is to the on-premise edition and then eventually migrate to one of the cloud editions.

For those customers, the intermediate step to the on-premise edition provides the opportunity to consume the values of SAP S/4HANA (SAP Fiori, data footprint reduction, and application simplification) but gives more time to adapt current custom code to the cloud requirements, for example. There may be customers that have older SAP Business Suite software releases that want to move immediately to one of the SAP S/4HANA cloud editions without the intermediate steps of upgrading SAP Business Suite to the newest enhancement package (EHP) and then migrating their database to SAP HANA.

Comparing the Editions – At a GlanceThe differences between the two editions of SAP S/4HANA are displayed at a glance in Figure 2.

Figure 2: SAP S/4HANA – Comparing the Editions

SAP® S/4HANA, on-premise edition

SAP S/4HANA, cloud edition

Licensing model Traditional licensing Subscription licensing

Infrastructure and maintenance model

Customers are in control of deployment and maintenance with their own dedicated IT staff

SAP provides the system and is responsible for maintenance

Speed of innovationCustomers have full control over speed of innovation, planned downtimes, changes within the system, and changes of the system

Cloud customers participate automatically on quarterly innovation upgrades

Implementation approach

Highly individual requirements regarding business processes and customization

Predefined best-practice configuration with limited specialization

Functional scope

Full enterprise resource planning scope (including SAP S/4HANA Finance and logistics function-ality); integrates with SAP SuccessFactors® Employee Central, SAP Fieldglass software, SAP hybris® Marketing, SAP Jam™, and the Ariba® Network

Key scenarios; embedded ERP scenarios; integrates with SAP SuccessFactors Employee Central, SAP Fieldglass software, SAP hybris Marketing, SAP Jam, and the Ariba Network

Custom code Full traditional ABAP® extensibility up to core modification (which is not recommended for total cost of ownership reasons)

In-app extensibility with limited ABAP, SAP HANA Cloud Platform as extension platform for larger extensions

6 / 27


Licensing ModelFor the on-premise edition of SAP S/4HANA, our traditional pricing model is in place. SAP Business Suite customers need to purchase the foundation-promotion license to run the new SAP S/4HANA code line. For the cloud edition, the pricing model is subscription based.

Infrastructure and Maintenance ModelFor the on-premise edition of SAP S/4HANA, customers are in full control of deployment and maintenance with their own dedicated IT staff. For the cloud edition, SAP provides the system and is responsible for system maintenance. This includes the execution of patches and release upgrades.

Speed of InnovationFor the on-premise edition of SAP S/4HANA, customers are responsible for deployment and maintenance and have full control over the speed of innovation, planned downtimes, and changes within the system. For the cloud edition, customers participate automatically in quarterly innovation upgrades based on service-level agreements.

Implementation ApproachCustomers (usually in collaboration with consulting partners) can implement highly individual requirements regarding business processes and customization. This requires detailed technical know-how. Customers coming from SAP Business Suite can move to the on-premise edition of SAP S/4HANA in a one-step technical procedure using the Software Update Manager tool with a data migration option.

In the cloud edition, the customer is following best practices with standardized fine-tuning requirements to participate more quickly in future innovative business processes. A could-edition customer can implement the solution with key-user business know-how. During this process, limited technical know-how is required. Customers coming from SAP Business Suite can move to the cloud by implementing the cloud edition of SAP S/4HANA using guided configuration functionalities, plus (if required) data migration functionality (technically based on SAP Landscape Transformation software).

7 / 27


Functional Scope In the on-premise edition of SAP S/4HANA, customers can use the full SAP ERP scope from SAP Business Suite. (This includes application innovation from SAP S/4HANA Finance and logistics functionality.) The on-premise edition can integrate with other cloud solutions from SAP, such as SAP SuccessFactors Employee Central, SAP Fieldglass software, SAP hybris Marketing, SAP Jam, and the Ariba Network. The cloud edition covers specific business scenarios for the marketing line of business and the professional services in-dustry. It also covers the most essential scenarios to run an entire enterprise in the cloud with a digital core that includes finance, accounting, controlling, procurement, sales, manufacturing, plant main-tenance, project system, and product lifecycle management. This comprehensive offering also provides native integration between SAP S/4HANA and other cloud solutions from SAP, including human resources solutions from SAP companies

SuccessFactors and Ariba, as well as the SAP hybris Marketing solution.

Custom Code A customer would select the on-premise edition of SAP S/4HANA if maximal flexibility in business-critical processes is required that goes far beyond standardization. However, adding business logic is not enough, because modification to SAP software objects is required. In the cloud edition, customers limit their flexibility by using cloud extensibility functionalities to transform and introduce new innovations to patched and upgraded operating systems.

Availability of SAP S/4HANAThere are quarterly innovation cycles for the cloud edition of SAP S/4HANA. Innovations for the on-premise edition are delivered in a yearly cycle. Figure 3 displays the deliveries planned next.

Figure 3: SAP S/4HANA – Availability

Yearly innovation cycle

SAP® S/4HANA, on-premise edition

Quarterly innovation cycle


SAP Simple Finance (1503)

Available today Planned innovation Future solution


SAP S/4HANA, on-premise edition


Next update (1506) Next update (1602)

SAP S/4HANA (1602) (with SAP S/4HANA Finance and logistics functionality)

8 / 27


THE ROAD TO SAP S/4HANA The road map for getting from where you are today to where you want to be in the future to maximize benefits will vary according to various business and IT drivers. For example, you may already be using SAP Business Suite powered by SAP HANA or have a hybrid scenario. You may be a new SAP customer, or you may already have a mature SAP software landscape. You may want to roll out SAP S/4HANA as quickly as possible, try it in a specific geography or business unit, or im-plement the central finance foundation provided by SAP S/4HANA Finance as a shared service center. You may want to implement SAP S/4HANA on premise or in the cloud. There are many options, and we can help you identify the business benefits and plan your road map.

The SAP S/4HANA Finance solution marked the first step in our SAP S/4HANA road map for customers. Today, a customer can join the SAP S/4HANA family by installing SAP S/4HANA Finance. SAP S/4HANA Finance replaces the traditional SAP ERP Financials solution. With the Q4/2015 delivery of the on-premise edition of SAP S/4HANA, we will also deliver additional application innovation in the logistics area (see Figure 4). However, the innovation delivered with Q4/2015 is not considered an “add-on” (or “exchange innovation add-on”) similar to what we call it in combination with SAP S/4HANA Finance. Instead, we speak of the installation of the SAP S/4HANA core. This core consists of several innovation packages. With the Q4/2015 delivery, innovation packages for simplified financials and logistics will be included. Additional innovation packages will enhance the core in the future.

Figure 4: SAP S/4HANA, On-Premise Edition (Q4/2015 Delivery) – Technical Stack (Basic)

SAP Fiori® UX

Core applications in SAP S/4HANA(SAP S/4HANA Finance, logistics functionality, and so on)

SAP HANA®

SAP® S/4HANA

9 / 27


There are three different implementation scenarios for customers to move to SAP S/4HANA (see Figure 5): • System conversion – Existing SAP Business Suite customers that want to move to SAP S/4HANA

• Landscape transformation – Existing SAP Business Suite customers that want to opti-mize their system landscape and move to SAP S/4HANA

• New implementation – New SAP customers that want to move from a legacy system to SAP S/4HANA

Figure 5: Implementation Scenarios

System conversion

Enterprise resource planning (ERP) system

On-premise edition

EXAMPLE: Complete conversion of an existing SAP Business Suite software system to SAP S/4HANA

Landscape transformation

ERP system Region A On-premise

edition EXAMPLE: Consolidation of a current regional SAP Business Suite software landscape into one global SAP S/4HANA software system

ERP system Region B

Cloud edition

ERP system Region C

New implementation

ERP system On-premise edition

EXAMPLE: New or existing SAP customer implementing a new SAP S/4HANA software systemNon-SAP

systemCloud edition

SAP® S/4HANA

10 / 27


System Conversion – Existing SAP Business Suite Customers That Want to Move to SAP S/4HANA This scenario focuses on existing SAP Business Suite customers that want to migrate from their current system to the on-premise edition 1511 of SAP S/4HANA (see Figure 6). This includes the following technical steps (main steps – not the complete technical piece list):

• Update to SAP NetWeaver® Application Server 7.5 (SAP NetWeaver AS) component for ABAP®

• Migrate the database to SAP HANA (in cases where SAP Business Suite is not yet running on SAP HANA)

• Install SAP S/4HANA, on-premise edition • Install SAP Fiori for SAP S/4HANA, on-premise edition

• Migrate data from the old data structures to the new simplified data structures

The scenario is technically based on Software Update Manager with the database migration option in cases in which the customer is not yet on the SAP HANA database.

Basically, the customer can move to the on-premise edition (Q4/2015 delivery) in a one-step procedure:

• The following are supported start releases for a one-step procedure – SAP ERP 6.0 and SAP Business Suite powered by SAP HANA; enhance-ment packages 0–7 (enhancement package 8 once available) for SAP ERP 6.0; SAP Business Suite powered by SAP HANA (including SAP Simple Finance, on-premise editions 1503 and 1602).

• Customers running older releases of SAP Business Suite can move to SAP S/4HANA in a two-step approach (for example, with Unicode migration and business partner conversion as a first step and then move to the on-premise edition as the second step).

Our best practices for this scenario are an accel-erated project methodology using a step-by-step HTML guide, project tools and enhancements to use Software Update Manager with the database migration option to its fullest potential, and a guided process to migrate your database using new project accelerators.

Figure 6: SAP S/4HANA, On-Premise Edition – System Conversion

SAP Fiori® UX

Core applications in SAP S/4HANA(SAP S/4HANA Finance, logistics

functionality, and so on)

SAP HANA

SAP S/4HANA

Start release

Core components in SAP ERP(financials, controlling, sales and

distribution, materials management, service parts planning, and so on)

Any database or SAP HANA®

SAP® Business SuiteBased on the Software Update Manager tool with database migration option

11 / 27


Landscape Transformation – Existing SAP Business Suite Customers That Want to Optimize Their System Landscape and Move to SAP S/4HANA This scenario focuses on existing SAP Business Suite customers that want to migrate from their current system or system landscape to the on-premise edition 1511 of SAP S/4HANA (or system landscape). This scenario covers more complex migration scenarios. It includes the following technical steps (main steps – not the complete list of technical elements):

• (Possible) new installation of SAP S/4HANA, on-premise edition 1511

• (Possible) conversion of a system to SAP S/4HANA, on-premise edition 1511

• Additional migration steps based on SAP Land-scape Transformation combined with system landscape optimization services

Usually a migration project is more than a technical task to move to the newest software architecture. The migration project has to deal with requirements such as merging multiple systems into one global suite system or migrating selective parts of a system (for example, line of business or organizational units). These migration requirements can be addressed using SAP Landscape Transformation.

Figure 7 displays the system consolidation use case.

Figure 7: SAP S/4HANA, On-Premise Edition – Merging Multiple Systems into One Global Suite System

SAP Fiori® UX

Core applications in SAP S/4HANA

SAP HANA

SAP S/4HANA

Start release

Core components in SAP ERP


SAP® Business Suite

Start release

SAP ERP

Any database or SAP HANA

SAP Business Suite

Legacy

Any customer legacy system

12 / 27


Figure 8 displays the move to SAP S/4HANA based on company codes.

Use cases like data volume reduction (data cleanup and archiving) during a migration to SAP S/4HANA would also fit in this category.

Our best practices available for this scenario are predefined extraction, transformation, and loading capabilities (coded assets) created in SAP Land-scape Transformation. They support the analysis and extraction of data from SAP source systems. The data is then validated and transformed to meet SAP S/4HANA requirements and loaded using pre-defined interfaces.

Figure 8: SAP S/4HANA, On-Premise Edition – Migrating Selected Parts

SAP Fiori® UX

Core applications in SAP S/4HANA(company code 1)

SAP HANA

SAP S/4HANA

Start release

SAP ERP(company code 1, company code 2,

company code 3, and so on)



Based on SAP Landscape Transformation

13 / 27


New Implementation – New SAP Customers That Want to Move from a Legacy System to SAP S/4HANAThis scenario focuses on net-new customers (coming from any legacy system) or SAP Business Suite customers that start with a new installation for a variety of reasons. This includes the following technical installation steps (main steps – not the complete list of technical elements):

• Install SAP NetWeaver AS 7.5 for ABAP, based on SAP HANA

• Install SAP S/4HANA, on-premise edition • Install SAP Fiori for SAP S/4HANA, on-premise edition

In this scenario, SAP S/4HANA is implemented and master and transactional data are migrated from the legacy system. Depending on the edition of SAP S/4HANA and customer detailed require-

ments, SAP Landscape Transformation or SAP Data Services software is used for the required data migration.

Figure 9 displays this scenario.

Our best practices available for this scenario are a predefined, guided configuration provided to set up the future target system much more quickly than traditional implementation processes. The best practices for data migration match the preconfiguration and automate most of the conversions needed. For SAP source systems, system landscape transformation is used, as in the previous scenario. For content from third-party source systems (not from SAP), SAP Data Services provides extraction of data from virtually any source system. Additionally, SAP Data Services will cleanse and transform data to meet the target data format for SAP software.

Figure 9: SAP S/4HANA, On-Premise Edition – New Implementation

Legacy


SAP Fiori® UX

Core applications in SAP S/4HANA

SAP HANA®

SAP® S/4HANA

Option: data migration from legacy system

14 / 27


Continuous Innovation with SAP Activate The SAP Activate innovation adoption framework expedites SAP S/4HANA implementations throughout the customer lifecycle with ready-to-run digitized business and technical processes, implementation tools, and next-generation methodology. SAP Activate supports customers at multiple starting points, including new imple-mentation, system conversion, and landscape transformation. • SAP Best Practices packages provide ready-to-run, digitized business and technology processes optimized for SAP S/4HANA. Leveraging SAP’s expertise and experience for standard processes saves time, helps deliver predictable results, and focuses efforts on innovation. Our best practices provide clear guidance on integration and migration fundamentals and include business processes such as finance and logistics. They are designed to guide you through an optimal migration scenario, whether you’re moving from a legacy SAP software system or a third-party database. It includes a reference solution for running in the cloud in addition to details on enhancing processes to fit your needs and integrate with other cloud solutions.

• Guided configuration is the content lifecycle management tool that helps you configure and test chosen SAP Best Practices packages. Now you can configure, test, and receive support in

data migration processes that are needed for the selected best practices. You have the option to add or update your choices at a later time. Automated updates and intuitive configuration changes assist in initial implementation and help you adopt ongoing innovation more quickly with minimal disruption. The result? You can customize preconfigured business processes – from charts of accounts to organizational structures – without IT involvement.

• SAP Activate methodology is SAP’s new software implementation methodology that builds on proven approaches and SAP’s experience to offer a consistent, agile-based track for any deployment type – cloud, on premise, hybrid, or mobile. It offers support for initial implementation and continuous innovation with SAP S/4HANA. The implementation best practices walk project teams through the planning, build, and deployment of the SAP solution. SAP Activate methodology caters to customer-specific configuration and extensions requirements to reflect your own business practices while remaining extremely scalable – nimble enough for smaller engagements or more robust for larger projects.

SAP Activate gives you the freedom to get started quickly and achieve faster outcomes with SAP S/4HANA, whatever your current configuration.

SAP® ACTIVATE • SAP Best Practices • Implementation methodology • Guided configuration

15 / 27


The following sections contain the technical prereq-uisites and the path to move from SAP Business Suite to the on-premise edition of SAP S/4HANA.

In the section “SAP S/4HANA Finance, On-Premise Edition,” you can find the technical details related to SAP S/4HANA Finance. In the section “SAP S/4HANA, On-Premise Edition 1511,” you can find the technical details related to the on-premise edition 1511 of SAP S/4HANA. In the section “New SAP Customer,” you can find details for new SAP customers implementing SAP S/4HANA.

For existing SAP Business Suite customers, the move to SAP S/4HANA is a technology exercise,

based on Software Update Manager with a data-base migration option. For new SAP customers or customers combining the move to SAP S/4HANA with use cases described in the section “Landscape Transformation – Existing SAP Business Suite Customers That Want to Optimize Their System Landscape and Move to SAP S/4HANA,” the technology used is based on SAP Landscape Transformation or SAP Data Services or both. The understanding of these technologies is the basis for the transition to SAP S/4HANA.

Links to the technical information are listed in the following table.

The Transition to the On-Premise Edition of SAP S/4HANA

Link Document

SAP S/4HANA, On-Premise Edition – Transition-Related Technology

Software Update Manager – SAP Help Portal

Software Update Manager – SAP Community Network blog

Database Migration Option – SAP Community Network blog

Introduction to Database Migration Option of Software Update Manager

Introduction to Database Migration Option of Software Update Manager – User Interface Demo

Migration Technology and Services

SAP Landscape Transformation – SAP Help Portal

SAP Landscape Transformation – SAP Community Network

SAP Landscape Transformation – Functions in Detail

SAP Landscape Transformation – Online course (LT100)

SAP Data Services – SAP Help Portal

SAP Data Services – SAP Community Network wiki

http://help.sap.com/saphelp_nwidmic_72/helpdata/en/f1/aa89158a6d4617878a4827dad07b4b/content.htm

http://scn.sap.com/community/it-management/alm/software-logistics/blog/2012/11/07/software-update-manager-sum-introducing-the-tool-for-software-maintenance

http://scn.sap.com/docs/DOC-49580

https://vimeo.com/user21884330/review/78267156/e0caac1dde

https://vimeo.com/user21884330/review/78267155/c9ac11432c

https://support.sap.com/saplt

http://scn.sap.com/community/saplt

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0b8aa9c-f937-3010-108f-e5d5195aa322?QuickLink=index&overridelayout=true&57909044098013

https://performancemanager5.successfactors.eu/sf/learning?bplte_company=SAP&_s.crb=kixvMHNzhL2UqTUiiOg/mjvDtcc%3d

http://help.sap.de/bods

http://wiki.scn.sap.com/wiki/display/EIM/Data+Services

http://scn.sap.com/docs/DOC-49580

https://vimeo.com/user21884330/review/78267155/c9ac11432c

https://vimeo.com/user21884330/review/78267156/e0caac1dde

http://scn.sap.com/community/it-management/alm/software-logistics/blog/2012/11/07/software-update-manager-sum-introducing-the-tool-for-software-maintenance

http://help.sap.com/saphelp_nwidmic_72/helpdata/en/f1/aa89158a6d4617878a4827dad07b4b/content.htm







16 / 27


SAP S/4HANA FINANCE, ON-PREMISE EDITIONAs of June 2015, customers can join the SAP S/4HANA family by installing SAP S/4HANA Finance. In various documents, you find the term “exchange innovation add-on” used to describe this scenario, with SAP S/4HANA Finance replacing the traditional SAP ERP Financials solution with application innovation in the finance area.

More information about the on-premise edition of SAP S/4HANA Finance can be found here:

• Finance line of business – http://go.sap.com /solution/lob/finance.html

• SAP Help Portal – http://help.sap.com/sfin200

The following SAP Notes are related to SAP S/4HANA Finance:

• Information on product name – SAP Note 2171868

• Latest updates – SAP Note 2117481 (release information note)

• Release restrictions – SAP Note 2127080 • Compatibility of enterprise extensions, industry solutions, and add-ons – SAP Note 2119188

Technical Prerequisites and Software ProductsTechnically, the on-premise edition 1503 of SAP Simple Finance is based on (see Figure 10):• EHP 7 for SAP ERP 6.0• SAP NetWeaver technology platform 7.40• SAP HANA

Figure 10: SAP Simple Finance, On-Premise Edition 1503

With the installation, several software units are installed:

• SAP S/4HANA Finance, on-premise edition • SAP HANA Live for SAP S/4HANA Finance, on-premise edition

• SAP Fiori for SAP S/4HANA Finance, on-premise edition

• SAP Smart Business cockpit for SAP S/4HANA Finance, on-premise edition

For more information, see the Administrator’s Guide for the on-premise edition 1503 of SAP Simple Finance.

SAP Simple Finance, on-premise edition 1503

SAP ERP 6.0 (enhancement package 7

for SAP NetWeaver® 7.40)

SAP HANA®

SAP® S/4HANA

http://go.sap.com/solution/lob/finance.html

http://go.sap.com/solution/lob/finance.html

http://help.sap.com/sfin200

https://css.wdf.sap.corp/sap/support/notes/2171868



http://service.sap.com/sap/support/notes/2119188

http://help.sap.com/sfin200

17 / 27


The Transition Path to the On-Premise Edition of SAP S/4HANA FinanceIn the following constellations, we support a one-step transition path from SAP Business Suite to the on-premise edition 1503 of SAP Simple Finance:

• Customers on any database; SAP NetWeaver AS 7.0x for ABAP; EHP x for SAP ERP 6.0 (see Figure 11)

• Customers on SAP HANA; SAP NetWeaver AS 7.40 for ABAP; EHP 7 for SAP ERP 6.0 (see Figure 12)

• Customers on SAP Simple Finance on-premise edition 1503 (see Figure 13)

We plan to deliver further innovations and appro-priate migration paths for SAP S/4HANA Finance in 2016.

Figure 11: One-Step Procedure for Customers on Any Database; SAP NetWeaver AS 7.0x for ABAP; EHP x for SAP ERP 6.0

SAP S/4HANA Finance

SAP ERP 6.0 (enhancement package 7 for

SAP NetWeaver 7.40)

SAP HANA

SAP S/4HANA

Start release SAP ERP 6.0

(enhancement packages 0–7)

SAP NetWeaver 7.0x

Any database

SAP Business Suite

Based on Software Update Manager with database migration option

One-step procedure for SAP® S/4HANA Finance – constellation 1: • SAP HANA® database migration • Update to enhancement package 7 for SAP ERP 6.0; SAP NetWeaver® 7.4 • Installation of the on-premise edition of SAP S/4HANA Finance

18 / 27


Figure 12: One-Step Procedure for Customers on SAP HANA; SAP NetWeaver Application Server 7.40 for ABAP; Enhancement Package 7 for SAP ERP 6.0

SAP S/4HANA Finance


SAP NetWeaver 7.40)

SAP HANA®

SAP S/4HANA



SAP NetWeaver 7.0x

Any database

SAP Business Suite

Based on Software Update Manager

One-step procedure for SAP® S/4HANA Finance – constellation 2: • Update to enhancement package 7 for SAP ERP 6.0; SAP NetWeaver® 7.4 • Installation of the on-premise edition of SAP S/4HANA Finance

Figure 13: One-Step Procedure for Customers on SAP S/4HANA Finance

SAP S/4HANA Finance, on-premise edition


SAP NetWeaver 7.40)

SAP HANA

SAP S/4HANA

SAP Simple Finance add-on 1.0


SAP NetWeaver 7.40)

SAP HANA® database

SAP Simple Finance


One-step procedure for SAP® S/4HANA Finance – constellation 3: • Installation of the on-premise edition of SAP S/4HANA Finance

19 / 27


SAP S/4HANA, ON-PREMISE EDITION 1511With the on-premise edition 1511 of SAP S/4HANA (Q4/2015 delivery), we plan to enhance the functional scope with application innovation and simplification in the logistics area (see Figure 14). Now, with the application innovation in the financials and logistics area, we can discuss SAP S/4HANA. We plan on enhancing the core with more application innovations in the future. In addition to the appli-cation simplification in the finance and logistics areas, the core consists of the innovations in the SAP Fiori UX and SAP HANA essential for success in the digital economy.

To help ensure a smooth transition to the on-premise edition of SAP S/4HANA, traditional features will remain available. In addition to application-specific functionality, only SAP GUI technology is still available after the move to SAP S/4HANA.

Technical Prerequisites and Software ProductsTechnically, the on-premise edition 1511 of SAP S/4HANA is based on:

• SAP S/4HANA core applications (including SAP S/4HANA Finance and logistics functionality)

• SAP NetWeaver 7.50 • SAP HANA

Figure 14: SAP S/4HANA, On-Premise Edition 1511 – Technical Stack (Basic)

SAP Fiori® UX

Core applications in SAP S/4HANA (SAP S/4HANA Finance, logistics


SAP HANA®

SAP® S/4HANA

20 / 27


The Transition Path to the On-Premise Edition 1511 of SAP S/4HANA In the following constellations, we support a one-step transition path from SAP Business Suite to the on-premise edition of SAP S/4HANA:

• Customers on any database; SAP NetWeaver AS 7.0x for ABAP; EHP x for SAP ERP 6.0

• Customers on SAP HANA; SAP NetWeaver AS 7.0x for ABAP; EHP x for SAP ERP 6.0

• Customers on SAP HANA; SAP NetWeaver AS for ABAP 7.40; EHP 7 for SAP ERP 6.0; SAP Simple Finance add-on 1.0 for SAP Business Suite powered by SAP HANA; or SAP Simple Finance, on-premise edition 1503

These constellations are displayed in Figures 15, 16, and 17.

Figure 15: One-Step Procedure for Customers on Any Database; Enhancement Package x for SAP ERP

SAP Fiori® UX



SAP HANA

SAP S/4HANA



SAP ERP core components(financials, controlling, sales and


Any database

SAP Business Suite

Based on Software Update Manager with database migration option

One-step procedure for SAP® S/4HANA, on-premise edition – constellation 1: • SAP HANA® database migration • Installation of the SAP S/4HANA core applications (based on SAP NetWeaver® 7.5)

21 / 27


Figure 16: One-Step Procedure for Customers on SAP HANA; Enhancement Package 7 for SAP ERP 6.0

SAP Fiori® UX



SAP HANA

SAP S/4HANA

Start release (enhancement package 7

for SAP ERP 6.0)

SAP ERP core components(financials, controlling, sales and


SAP HANA® database

SAP Business Suite


One-step procedure for SAP® S/4HANA, on-premise edition – constellation 2: • Installation of the SAP S/4HANA core applications (based on SAP NetWeaver® 7.5)

Figure 17: One-Step Procedure for Customers on SAP S/4HANA Finance

SAP Fiori® UX



SAP HANA

SAP S/4HANA

Start release (enhancement package 7 for

SAP ERP 6.0); SAP Simple Finance

SAP ERP core components (financials, controlling, sales and


SAP HANA® database

SAP Business Suite


One-step procedure for SAP® S/4HANA, on-premise edition – constellation 3: • Installation of the SAP S/4HANA core applications (based on SAP NetWeaver® 7.5)

22 / 27


In addition, please note the following: • An explicit upgrade to EHP 7 is not required for the move to the on-premise edition 1511 of SAP S/4HANA (see Figure 15).

• Customers using older releases of SAP Busi-ness Suite (for example, still on non-Unicode) can move to the on-premise edition, version 1511, in a two-step transition approach.

• The installation of the SAP Fiori UX software components are a separate installation step and typically installed on a separate, central gateway server. For purposes of simplification, the figures do not show this aspect.

NEW SAP CUSTOMER We will support new customers for the on-premise edition of SAP S/4HANA in their implementation project with preconfiguration based on SAP Rapid Deployment solutions and rapid data migration with SAP Data Services. Additionally, there will be content packages for the implementation and integration with SAP S/4HANA and other cloud solutions from SAP, such as SAP SuccessFactors Employee Central. Figure 18 shows at a glance the data migration based on SAP Data Services.1

Figure 18: SAP S/4HANA, On-Premise Edition: Data Migration Based on SAP Data Services – At a Glance

1. More information is available on SAP Help Portal.

Legacy data environment Data staging and test environment Loading Target

environment

Legacy applications and cloud applications

Legacy databases – Open Database Connectivity

Flat files, XML, HTML, CSV, mainframe, Microsoft Excel

1

SAP

Extr

act a

nd p

rofil

e

CleanseName parsing, address parsing and correction, material/product parsing, matching

TransformTransform data into SAP software structure

Validate and loadBusiness validation rules, automatic configuration validation

Reconciliation

Staging area 3

2

Web service

IDocs

SAPConfiguration and extraction for SAP software

SAP® S/4HANA

SAP

5

4

6

7Dashboards and

business reportingPerformance

analysis

Transparency, governance, and communication


23 / 27


Legacy Data Environment (1) The legacy data environment refers to the source systems for the migration. It can be any third-party source system that is supported by SAP Data Services connectivity (almost everything, as SAP Data Services supports Open Database Connec-tivity protocol). SAP software systems on a lower release that cannot be upgraded can be a legacy system as well. The rapid data migration package comes with prebuilt content for SAP S/4HANA.

Extract and Profile (2)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, you can start profiling the source systems very early on using SAP Information Steward software. SAP Data Services is used as a staging area that extracts and profiles the data. The profiling can include looking at patterns in postal codes. For example, what percentage of postal codes has five digits? It could also be how

many material numbers follow a specific pattern. For example, you might be 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. The quality of the source data is assessed, and the overall risk of data migration is mitigated to help ensure the overall success of the data migration project.

Cleanse, Transform, and Validate and Load (3)This includes updating the data so that it meets specific patterns, mapping and transforming the data according to rules, and validating data against the business context in SAP S/4HANA. 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 context and configu-ration settings in SAP S/4HANA. Also, duplicate data records can be eliminated with this step.

24 / 27


Configuration Extraction for the SAP Software (4)Once the data is extracted, it is important to know how it needs to be prepared for the SAP software. The solution reads business context and configu-ration 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 enables you to know the business context in the SAP software, to transform and then validate the data in SAP Data Services against the SAP software configuration and customization settings. Mapping of the source data normally requires mapping fields that comply with the configuration.

Load (5)Once the data is transformed and validated, it is then loaded into SAP S/4HANA. This is normally done via intermediate documents (IDocs) and Web services but can also be done with files and the BAPI® programming interface.

Reconciliation (6)Reconciliation looks at what was actually loaded versus what was expected to be loaded. This helps ensure that all data was loaded and is ready for use.

Dashboards and Business Reporting (7)Throughout the process, dashboards are available for the people involved to stay informed about the status of the migration. Additionally, the migration project often sets data-quality expectations and governance around data management. The entire process of assessing and validating the data according to business rules and the SAP software context lays the groundwork for ongoing data gov-ernance. For example, if customer records were checked to ensure that every customer had at least two contact persons associated with it, then this process can continue to ensure all new customer records have two contact persons.

25 / 27


The cloud edition of SAP S/4HANA covers specific business scenarios for the marketing line of business and for the professional services industry. It also covers the most essential scenarios to run an entire enterprise in the cloud with a digital core, including finance, accounting, controlling, procurement, sales, manufacturing, plant maintenance, project system, and product lifecycle management, plus integration with SAP SuccessFactors Employee Central, the Ariba Network, SAP hybris Marketing, SAP Fieldglass software, and SAP Jam.

SAP S/4HANA, CLOUD EDITION – THREE OFFERINGSThree offerings are currently available as part of the cloud edition of SAP S/4HANA:2

• SAP S/4HANA, cloud marketing edition – for the marketing line of business

• SAP S/4HANA, cloud project services edition – for the professional services industry

• SAP S/4HANA, cloud enterprise edition – for a full ERP scope

For more details regarding the scope of the different cloud offerings, see SAP Community Network.

IMPLEMENTATIONThe initial step in moving to the cloud edition of SAP S/4HANA is the implementation of the customer’s cloud system. Based on the built-in functionalities of the guided configuration, the customer (optionally supported by consulting and implementation partners) implements business scenarios and business processes. The required master and transactional data can be migrated from SAP Business Suite (or any legacy system).

The Transition to the Cloud Edition of SAP S/4HANA

2. A free 14-day cloud edition trial system is available to help you experience the value of simplicity across key business scenarios: project manager, cash manager, general ledger accountant, accounts receivable accountant, and accounts payable accountant. You can access the trial at www.sap.com/s4hana-trial.

http://scn.sap.com/community/s4hana/blog/2015/06/25/sap-s4hana-cloud-edition-1506-what-is-the-scope

http://www.sap.com/s4hana-trial

26 / 27


DATA MIGRATION Technically, the migration to the cloud edition of SAP S/4HANA is based on SAP Landscape Transformation and SAP Test Data Migration Server software as data migration tools. Data is migrated from a customer’s source system (SAP Business Suite or any legacy system) to a new

cloud target system for SAP S/4HANA. From an implementation point of view, the data migration is integrated into the implementation cockpit in SAP S/4HANA (end-to-end implementation experience).

Figure 19 gives a visual overview of moving to the cloud edition of SAP S/4HANA.

Figure 19: Move to SAP S/4HANA, Cloud Edition – At a Glance

Innovation packagesSimplified financials I logistics

Scope* Key scenarios I Dedicated ERP scenarios

SAP HANA

SAP S/4HANA

SAP ERP Full ERP scope

Database Any database I SAP HANA® database


Data migration (based on SAP Landscape Transformation)

Legacy


*Scope dependent on chosen offering (SAP S/4HANA, cloud marketing edition; SAP S/4HANA, cloud project services edition; SAP S/4HANA, cloud enterprise edition)

27 / 27

Studio SAP | 39926enUS (15/10) © 2015 SAP SE or an SAP affiliate company. All rights reserved.

You can find links to the technical information in the following table.

Link Document

SAP Landscape Transformation – SAP Help Portal

SAP Landscape Transformation – SAP Community Network

SAP Landscape Transformation – Functions in Detail

SAP Landscape Transformation – Online course (LT100)

SAP Data Services – SAP Help Portal

SAP Data Services – SAP Community Network wiki














No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

the transition to sap...

Documents