Hi everyone,

SAP Simple Finance, on-premise edition marked the first step in our SAP Business Suite 4 SAP HANA roadmap for customers. With the installation of the SAP Simple Finance, on – premise edition the customer is joining the SAP S/4HANA family. However, with the SAP S/4HANA, on – premise edition 1511 (Q4/2015) the functional scope will be enhanced with additional application innovation in the logistics area. 

The following blog describes at a glance technical details and pre-requisites of the migration path from SAP Business Suite to SAP Simple Finance, on-premise edition 1503 and the migration path from SAP Business Suite to SAP S/4HANA, on-premise edition 1511. Regarding the SAP S/4HANA, on-premise edition 1511 the chapter below describes a future development and should be understood in the sense that they are "planned to be" like described.

Happy to read your feedback!.

Kind Regards,

Frank

_______________________________

Introduction

SAP Simple Finance, on-premise edition marked the first step in our SAP Business Suite 4 SAP HANA roadmap for customers. With the installation of the SAP Simple Finance, on – premise edition the customer is joining the SAP S/4HANA family.  However, with the SAP S/4HANA, on – premise edition 1511 (Q4/2015) the functional scope will be enhanced with additional application innovation in the logistics area.

Depending on customer’s requirements and roadmaps there are different transition paths to SAP S/4HANA. The following figure displays an (abstract) roadmap of a specific customer on his journey to SAP S/4HANA, on-premise edition. This customer is planning to move to SAP S/4HANA with a roadmap which goes over several years. First the customer moved to SAP Business Suite on HANA, now he plans to go to SAP Simple Finance, on-premise edition and then as a third step to SAP S/4HANA, on-premise edition which does include application innovations in logistics area.

Figure 1: Move to SAP S/4HANA, on-premise edition – a possible customer Roadmap in several steps

In addition to the technical move to SAP S/4HANA this specific customer is simplifying their overall system landscape. Currently, several SAP Business Suite Systems are used in the different regions; however, a central SAP S/4HANA system per region is planned as a target.

For a different customer, a different roadmap might be applicable. The following figure gives an outlook to the to SAP S/4HANA, on-premise edition 1511 (Q4/2015 delivery). Here, it is planned to offer a path where the customer can move to SAP S/4HANA, on-premise edition 1511 (Q4/2015 delivery) from a SAP Business Suite start release (for example SAP ERP 6.0) still on anyDB.

Figure 2: Move to SAP S/4HANA, on-premise edition 1511 (Q4/2015 delivery) – a possible future roadmap

Technical details and pre-requisites of the different transition paths

SAP Simple Finance, on-premise edition

Today (as of June 2015) a customer can join the SAP S/4HANA family by installing SAP Simple Finance. In different documents you can find the term “exchange innovation add-on”, because SAP Simple Finance replaces the classic ERP Financials with application innovation in the financial area.

More information about SAP Simple Finance, on-premise edition can be found here:

• Line of Business - Finance: http://go.sap.com/solution/lob/finance.html
• SAP Help:http://help.sap.com/sfin200

SAP Notes related to SAP Simple Finance:

• For Information on product name see SAP note:2171868
• For the latest updates refer to SAP note 2117481
• For release restrictions see SAP note 2127080
• Compatibility of enterprise extensions, industry solutions, and add-ons can be found in SAP Note 2119188.

Technical Prerequisites and Software Products

Technically the SAP Simple Finance, on-premise edition 1503 is based on:

• SAP enhancement package 7 for SAP ERP 6.0
• SAP NetWeaver 7.40
• SAP HANA database

Figure 3: SAP Simple Finance, on-premise edition 1503 (basically)

With the installation of SAP Simple Finance on-premise edition, several software units are installed.

• SAP Simple Finance, on-premise edition
• SAP HANA Live for SAP Simple Finance, on-premise edition
• SAP Fiori for SAP Simple Finance, on-premise edition
• SAP Smart Business for SAP Simple Finance, on-premise edition

More detailed information can be found in the Administrators Guidefor the SAP Simple Finance, on-premise edition 1503.

The transition path to SAP Simple Finance, on-premise edition

In the following constellations a one-step transition path from SAP Business Suite to SAP Simple Finance, on-premise edition 1503 is supported:

• One-Step Procedure for customers on anyDB, ABAP AS 7.0x, SAP ERP6.0 EHPx
• One-Step Procedure for customers on SAP HANA, ABAP AS 7.40, SAP ERP6.0 EHP7         
• One-Step Procedure for customers on SAP Simple Finance 1.0

These constellations are displayed in the following figures:

Figure 4: SAP Simple Finance, on-premise edition 1503 - One-Step Procedure for customers on anyDB, ABAP AS 7.0x, SAP ERP6.0 EHPx

Figure 5: SAP Simple Finance, on-premise edition 1503 - One-Step Procedure for customers on SAP HANA, ABAP AS 7.40, SAP ERP6.0 EHP7

Figure 6: SAP Simple Finance, on-premise edition 1503 - One-Step Procedure for customers on SAP Simple Finance add-on 1.0

Additional Remarks:

• It is planned to deliver further innovations for SAP Simple Finance in 2016. It is planned to provide appropriate migrated paths then. 

SAP S/4HANA, on-premise edition 1511

With the SAP S/4HANA, on-premise edition 1511 (Q4 / 2015 delivery) it is planned to enhance the functional scope with application innovation and simplification in the logistics area. Now with application innovation in financials and logistics area we could speak of the SAP S/4HANA Core. More application innovations are planned to enhance the SAP S/4HANA Core then in future.  In addition to the application simplification in financials and logistics area the SAP S/4 HANA Core consists of the SAP Fiori user experience (UX), and innovations for the digital economy based on SAP HANA.

Figure 7: SAP S/4HANA, on-premise edition 1511 - technical stack (basically)

To ensure a smooth transition to SAP S/4HANA, on-premise edition traditional features will stay available. Besides application specific functionality, just the SAP GUI based user interface technology should be listed as still available functionality after the move to SAP S/4HANA.

Technical Prerequisites and Software Products

Technically the SAP S/4HANA, on-premise edition 1511 is based on:

• SAP S/4HANA core components (including simplified financials and simplified logistics)
• SAP NetWeaver 7.50
• SAP HANA database

The transition path to SAP S/4HANA, on-premise edition 1511

In the following constellations a one-step transition path from SAP Business Suite to SAP S/4HANA, on-premise edition is supported:

• One-Step Procedure for customers on anyDB, ABAP AS 7.0x, SAP ERP6.0 EHPx
• One-Step Procedure for customers on SAP HANA, ABAP AS 7.0x, SAP ERP6.0 EHPx
• One-Step Procedure for customers on SAP HANA, ABAP AS 7.40, SAP ERP6.0 EHP7, SAP Simple Finance add-on 1.0 / SAP Simple Finance, on-premise edition 1503

These constellations are displayed in the following figures:

Figure 8: SAP S/4HANA, on-premise edition 1511 - One-Step Procedure for customers on anyDB, SAP ERPx

Figure 9: SAP S/4HANA, on-premise edition 1511 - One-Step Procedure for customers on SAP HANA, SAP ERP6.0 EHP7

Figure 10: SAP S/4HANA, on-premise edition 1511 - One-Step Procedure for customers on SAP Simple Finance

Additional Remarks:

• An explicit upgrade to Enhancement Package 7 is not required for the move to SAP S/4HANA, on-premise edition 1511. See figure 8 and figure 9 above.
• Customer using older SAP Business Suite Releases (for example still on Non-Unicode) can move to SAP S/4HANA, on-premise edition 1511 in a two-step transition approach.
• The installation of the SAP Fiori UI software components are a separate installation step and typically installed on a separate, central gateway server. Due to simplification reasons the figures above do not visualize this aspect.

SAP Activate Methodology is a unique implementation experience that combines SAP Best Practices, methodology, and guided configuration to help customers and partners deploy SAP S/4HANA. The SAP Activate library features a collection of blogs that provide a deeper dive into the methodology to help you get the support you need to Run Simple while continuously innovating and driving real results.

July 2015

SAP Activate methodology JAM space - we are open, come in | Jan Musil | July 9, 2015

SAP Activate: What's the story behind the SAP Best Practices optimized for S/4HANA? | Bob Caswell | July 2, 2015

June 2015

SAP Activate - what is the methodology story? | Jan Musil | June 24, 2015

May 2015

Introducing SAP Activate: Best Practices, Guided Configuration, & Methodology Optimized for S/4HANA | Bob Caswell | May 7, 2015

Run Simple with SAP Activate: Best Practices, Methodology, & Guided Configuration | Bob Caswell | May 21, 2015

** Keep a look out for the SAP Activate landing page on sap.com

S/4HANA Services library provides blogs and discussions focused on how S/4HANA can help your business run simple.  Whether you’re interested in finance, marketing, human resources, or IT the S/4HANA Services Library can be a resource for you to hear directly from SAP Services experts on leveraging this technology to innovate throughout your organization.

S/4HANA Cookbook | July 2015

SAP S/4HANA cookbook: Guiding you through your implementation | by Joerg Wolf

S/4HANA Servces Flipbook | 2015

Unlock The Power - Run Simple with SAP S/4HANA

1. Introduction

SAP S/4HANA is SAP’s next generation business suite designed to help you run simple in a digital and networked world. This new suite is built on advanced in-memory platform, SAP HANA, and offers a personalized user experience with SAP Fiori.

Deployable in the cloud or on-premise, SAP S/4HANA is built to drive instant value across lines of business and industries with the ultimate in sophistication: simplicity.

This document is divided into 2 parts it helps the user create a low cost S/4HANA demo system using SAP Cloud Appliance Library (CAL) on Amazon’s AWS Cloud. Methodology described in this document could be applied in creating demo systems of any type.

Part 1: Gives detailed steps on how to create a S/4HANA instance on AWS.

Part 2: Gives detailed steps on how to reduce the Operational costs of the S/4HANA instance.

2. SAP Cloud Appliance Library (CAL)

SAP’s Cloud Appliance Library (shot name CAL) can is used to quickly provision test and demo systems on standard cloud infrastructure providers like Microsoft’s Azure, Amazon Web Services. In this document we will concentrate only on Amazon Web Services (AWS).

User can access CAL from the URL http://cal.sap.com and login or register in it. When the user logs in for the first time he will need to agree to SAP’s terms and conditions.

3. Amazon Web Services (AWS)

Before we provision S/4HANA system on CAL we need to have an account in either Amazon Web Services or Microsoft’s Azure. As mentioned earlier we are going to be using AWS.

User can access AWS from the URL http://aws.amazon.com and login or register in it. Please note Amazon would charge the user based on the usage so we need to be careful to stop/delete instances and other components when they are no longer needed.

4. Provisioning S/4HANA on AWS

This section provides detailed steps on how to provision S/4HANA on AWS using CAL. Before proceeding to this section user needs to have a valid account in both CAL and AWS.

4.1. Extract Access Key and Secret Key from AWS

Logon to AWS account and click on user name at the top right which expands as a drop down menu. Select Security Credentials from the Menu.

Now you will get an information box where you need to click Continue to Security Credentials.

Now expand Access Keys (Access Key ID and Secret Access Key) and click on Create New Access Key to generate a new key pair. Download the Key pair for future use but please keep it safe.

4.2. Create AWS Account in CAL

Now Logon to CAL (http://cal.sap.com) and click on Accounts Tab you will be able to see the list of cloud accounts already created.

On the top right click on Create Account to open Create Account wizard enter the name and description.

Now click next and select Amazon Web Services from the Cloud Provider drop down and provide the Access Key and Secret Key

Now click next and next again and click finish. You should see the entry in the Accounts table.

4.3. Activate S/4HANA solution in CAL

Now click on Solutions tab and in the search text at the extreme right type Fiori and click on try now for the entry “SAP S/4HANA, on-premise edition – Fully Activated”.

You will be presented with the Terms and Conditions dialog scroll down and click on Accept.

After clicking on accept it will apply the agreement

Try Now link will change to Activate. Click on Activate link now. Screen will grey out for some time.

Now Activate link will change to Create Instance link. Click on this link to display Create Instance wizard.

Leave the values to defaults and click on Next. (Make a note of the region)

Leave the values to default again and click next. Here set the master password as per the password requirements as described in the wizard and click next.

In the next screen select Manually activate and suspend in the Scheduling Options drop down and click Next.

In the Summary screen review all the settings and click on Finish.

You will get a Private Key dialog where you need to Click on Store followed by download. Do not forget this step as you will need this private key to logon at the OS level.

Another dialog comes up informing it will take around 50 minutes to activate the instances.

4.4. Check and verify the activation process.

Logon to AWS and select the appropriate region as specified on the previous sub section will creating the instance and click on EC2

Now click on Instances.

You will see the instances will gradually get created and the Instance State will become green.

Once the instance named “SAP_S4HANA(SAP ERP 607 on SAP HANA SP09)” is green you can access the system at the OS level of the S/4HANA system.

To access the OS level from windows you need Putty and Puttygen executables which can be downloaded from URL http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

Before accessing the OS from putty we need to set the ip address as public IP of the instance (as shown above)  for the host vhcalhdbdb in the hosts file located in the directory C:\Windows\System32\drivers\etc

Now open Putty and create and entry for SAP_S4HANA with the host name vhcalhdbdb as shown below

Now open Puttygen to convert the private key file from pem to ppk format.

Select Conversions-> Import Key

Now select the pem file you downloaded earlier

Now click on Save private key a warning dialog appears just click Yes.

Now click on Save private key a warning dialog appears just click Yes.

Now specify the file name and click Save.

Now expand SSH->Auth and specify the ppk file

Now go back to Sessions and click Save.

Now click on Open you will be presented with a Alert dialog as show below. Just click Yes.

And specify the user id as root and you will be logged on to the OS without asking for password as you have provided a valid private key file.

After roughly 50 mins you will see the system is up and running. Both the HANA DB and SAP ERP are up and running and also the XS Engine url http://vhcalhdbdb:8002 is available.

Also you can configure the HANA studio to connect to the new HANA database (as SYSTEM/<master password>) and you will notice all the processes are running fine without any issue.

Also create a new SAP GUI connection to ECC and you can logon to SAP with the below connection parameters.

You will also notice in CAL the instance status in green now

Finally invoke stopsap in erpadm and HDB stop as hdbdm.

Now stop all the 3 instances by selecting all the 3 instances and select Instance State->stop from Actions button.

Now if you notice the size on the S/4HANA box is r3.8xlarge which is pretty powerful system with 32 CPUs and 244 GB RAM!!!. And the hourly costs for running such a system is pretty high its 2.8$ / hr which makes it unaffordable for many of us even to run it for 3 hrs a day would cost 250$ a month!!.

Next section would give you a workaround in greatly reducing the operating costs by almost 7 to 10 times.  Please note that this technique is valid only for AWS.

1. Reduce the Operational Costs for S/4HANA on AWS

This section will provide the detailed steps you need to follow to reduce the operational costs for S/4HANA system. We will be following the Spot Request feature provided by AWS to reduce the operational costs.  Using this feature we create a AMI (Amazon Machine Image) and run this image as spot instance where in you can set the max price beyond which the system would stop immediately. Based on the trend for a Month/Week/Day we can specify the upper limit.

You can access this trend from Spot Requests->Pricing History

1.1. Create AMI (Amazon Machine Image)

Now select the instance and from actions select Image->Create Image.

Now give a name and description to the image and make sure all the drives are selected and click create Image.

A request confirmation dialog appears

Now go to the AMIs section and you will see the image creation is in progress and after a while gets completed

1.2. Create a Spot Request with the AMI

Now select the completed AMI and from actions select Spot request.

In the first screen of this wizard select the machine size as r3.8xlarge and click next.

In the next section specify the Maximum price as double and lowest price of the subnet (which is us-east-e in this case) and also select the same subnet.

Next step leave it as it is and click next.

And the next step as well, just click next.

In the next step specify a security group which has access to all ports for simplicity as this is a demo system.

Now click Review and Launch and level the Boot from SSD dialog with default option.

And finally in the Review screen click on Launch button

And specify the same key pair which was generated in the CAL.

And finally click on Request Spot Instances. A request confirmation dialog appears.

Click on View Spot Reqests to see the status of the Spot request.

Now go to instance and you will see the instance would have started after a while.

You will see the instance is running currently at 0.35 $ with max price of 0.75 $ so you have saved 4 times to 8 times the actual cost.

1.3. Logon to Spot Instance to check the startup

Now go to the hosts file located in C:\Windows\System32\drivers\etc and change the ip to the new public IP as shown in the figure above.

And do not logon as root from Putty now instead login as ec2-user

Now sudo as root and check the private IP using ifconfig command which in this case is 172.31.60.35

Now go it /etc/hosts and change the IP for vhcalhdbdb to private IP

Now reboot the system using the menu choice below

After a while the system will reboot.

After the reboot you will notice all the services will start up within 30 mins.

Check dpmon as well from OS level

And also SAP ABAP and HANA you will notice the licenses are valid.

2. Final Steps

Now we have two options:

• We can either create an image out of running Spot instance or terminate the Stop instance in which case you will have a new AMI with all the changes retained in it.
• Just terminate the spot instance and you would lose all the changes made on the spot instance.

You will notice there is no option to stop the Spot instance you can only reboot or terminate a spot instance.

SAP S/4HANA Cookbook

The SAP S/4HANA Cookbook covers the most important aspects of implementing SAP Business Suite 4 SAP HANA (SAP S/4HANA).

It consists of a small set of HTML landing pages that provide abstracts for specific topics, along with links to further deep-dive information.

The content on these pages follows an iterative approach and will be updated regularly.

Comments are disabled on this page to keep it lean. Please use the SAP S/4HANA forum to raise questions, comments, or ideas.

Table of Contents

1. What is SAP S/4HANA (this page)

• Overview
• What is available now ?
• Functional Capabilities
• Transition Options
• Extensibility & Adaptations
• Education & Service Offerings by SAP
  

2. SAP Simple Finance, On-Premise Edition 1503: Implementation Information

• This is the current on-premise version of SAP S/4HANA, therefore there's a separate page to dive into details

3. Transition to SAP S/4HANA: Know your options in detail

• Planned for Q4/2015 (see 'What is SAP S/4HANA > Transition Options' for currently available overview)
  
  

Note: For access to SAP Notes and roadmap information, an 'S-user' is required (see here).

SAP S/4HANA: Overview

SAP S/4HANA: What is available now ?

SAP S/4HANA: Functional capabilities in detail

Note wrt. naming: Final product names for both Simple Finance (sometimes abbreviated as sFIN) and Simple Logistics (sLOG) to be determined.

SAP S/4HANA: Transition Options

SAP S/4HANA: Extensibility, Adaptation, Integration

Education & Service Offerings by SAP

Comments are disabled on this page. Please use the forum to raise questions, comments, or ideas.

The SAP S/4HANA Cookbook covers the most important aspects of implementing SAP Business Suite 4 SAP HANA (SAP S/4HANA).

It consists of a small set of HTML landing pages that provide abstracts for specific topics, along with links to further deep-dive information.

The content on these pages follows an iterative approach and will be updated regularly.

Comments are disabled on this page to keep it lean. Please use the SAP S/4HANA forum to raise questions, comments, or ideas.

Table of Contents

What is SAP S/4HANA

• Read this page to get an overview of SAP S/4HANA, current releases and capabilities, transition paths, ...
  

SAP Simple Finance, On-Premise Edition 1503 (this page)

• Overview
• Technical implementation
• Functional implementation
  • Accounting
  • Cash management
  • Integrated business planning
  • SAP Fiori and Analytics
  • Central finance
• Learning resources for SAP Simple Finance
  

3. Transition to SAP S/4HANA: Know your options in detail

• Planned for Q4/2015 (see 'What is SAP S/4HANA > Transition Options' for currently available overview)
  

Note: For access to SAP Notes and roadmap information, an 'S-user' is required (see here).

SAP Simple Finance, On-Premise Edition 1503: Overview

SAP Simple Finance, On-Premise Edition 1503: Technical implementation

The following sections describe the functional areas of SAP Simple Finance, On-Premise edition 1503 in detail.

SAP Accounting powered by SAP HANA

SAP Cash Management powered by SAP HANA

SAP Integrated Business Planning for Finance

SAP Fiori and Analytics for Simple Finance

SAP Central Finance

Learning Resources for SAP Simple Finance

Comments are disabled on this page. Please use the forum to raise questions, comments, or ideas.

As Announced in SAPPHIRE NOW 2015, SAP has launched SAPACTIVATE, an online information hub that offers SAP S/4HANA implementation methodology to help customers to move smoothly into the innovative future of SAP S/4HANA, the next-generation business suite. This implementation methodology is a unique combination of SAP best practices, methodology, and guided configuration documents to simplify the adoption of SAP S/4HANA for all the different implementation scenarios.

Fig.:SAP S/4HANA Implementation Scenarios

So, what is SAP ACTIVATE?

SAPACTIVATE provides SAP Best Practices packages for any S/4HANA implementation, including migration, integration and configuration, and uses one methodology for any deployment mode — cloud, on premise or hybrid.

SAPACTIVATE delivers ready-to-run business processes optimized for SAP S/4HANA.

SAPACTIVATE is geared for a speedy initial implementation of S/4HANA and is designed for continuous innovation.

SAPACTIVATE supports different starting points for customers to adopt SAP S/4HANA – new implementation, system conversion and landscape transformation

SAPACTIVATE also enables partners to extend the ready-to-run business processes shipped by SAP, which builds the basis on which partners could update their custom best practices and co-innovate with SAP.

1) SAP Best Practices for a quick and easy SAP S/4HANA Migration

SAP Activate offers pre-configured best practice scenarios and functionalities for S/4HANA implementation, covering all different aspects like Migration, Integration and Configuration. Those best practices will be a live content that will be continuously updated as new enhancements are activated.

SAP Best Practices for SAP S/4HANA provides ready-to-run financial and logistics business processes integrated with other cloud solutions, such as SuccessFactors Employee Central or Ariba Network.

SAP used its deep business process expertise, based on real-life scenarios, to create those Best Practices, that could be used by customers to determine the optimal path forward given their industry, existing systems and strategic business imperatives.  Customers can make optimal implementation decisions using SAP Best Practices, and easily adjust them as needed over time. Included are specific migration recommendations for companies that typically have multi-faceted systems across numerous databases.

Fig.: SAPACTIVATE Best Practices On-Premise Edition

Fig.: SAPACTIVATE Best Practices Cloud Edition

SAP Activate gives a clear answer to the question: How can I get there with a guarantee of success and with a quick time-to-value approach?

SAP Activate will also offer Opportunity for Partners

SAP Activate provides SAP partners with a simple path to co-innovate with SAP by tapping their domain expertise by process and industry, and build on top of the SAP Best Practices and add functionalities on the SAP HANA Cloud Platform as new scenarios become available, effectively becoming both a services company and recognized thought leader.

2) Guided Configuration

SAP Activate contains a comprehensive set of tools designed to guide customers and partners step-by-step through the process of software implementation. Simple, easy-to-follow, on-screen instructions provide technical guidance with visually engaging displays. The guided approach also allows business and IT to collaborate for a successful outcome. The entire process of collaboration will be recorded, thus supplying a configuration history that can be tapped into for future use.

The SAP S/4HANA Guided Configuration covers the following sections:

• Configure your solution: Guides to help on the S/4HANA configurations for both, initial implementation & continuous innovation adoption
• Test your processes: Business process driven, pre-defined automated test
• View Solution Scope: Evaluate activated business processes and country versions
• Migrate Your Data: Business process driven, pre-defined automated test
• User Training & Onboarding: Guided Product tours

Example Scenario of Guided Configuration:

Process: Decrease approval value for purchase orders (through self service configuration)

1st Step: Access Guided Configuration

2nd Step: Open Self-Service Configuration UI

3rd Step: Review Configuration Values:

4th Step: Adjust Reference Settings:

Automated Test Plans

• Delivers pre-scripted, process oriented test cases for delivered best practice scenarios
• Test scripts adapt to current configuration
• Tests are independent from underlying data
• Documents success of test runs

Supported scenarios

• Create or change test plans
• Run test plans
• Documentation of test success
• In case of errors, adapt test data

3) Methodology

SAP Activate Methodology help customers achieve fast and cost efficient deployment of SAP innovations with ONE simple, modular and agile methodology, covering all phases of SAP S/4HANA Implementation: Prepare, Explore, Realize, Deploy.

Fig.: SAPACTIVATE Methodology Phases

The SAPACTIVATE Methodology will help companies develop a comprehensive project plan encompassing all of the tasks required for migration and implementation. Regardless the deployment scenario: cloud-based, on-premise or hybrid, the methodology behind SAP Activate helps chart the simplest path to innovate for greater business value. The methodology begins with SAP Best Practices and includes a fit-gap analysis to determine individual company needs. The methodology is also designed for partners to incorporate into their own best practices.

Fig.: SAPACTIVATE S/4HANA Adoption Roadmap

SAP Activate methodology is the overall starting point for initiating any implementation of SAP S/4HANA. It is the successor of the ASAP methodology and SAP Launch methodologies, and caters to the usage of SAP’s premium engagements, SAP MaxAttention and SAP Active Embedded.

SAPACTIVATE Methodology Principles:

How it compares to ASAP and SAP Launch

SAPACTIVATE It is the successor of the ASAP methodology and SAP Launch methodologies,

Differences for different deployment options are reflected in specific versions of the methodology for each deployment type:

• For On-Premise deployments, ASAP 8 Methodology is replaced by SAPACTIVATE methodology for On-Premise Edition, which supports SAP S/4 HANA and SAP Business Suite (ERP, CRM, SRM,…) implementations.
• For Public Cloud deployments, SAP Launch Methodology is replaced by SAPACTIVATE methodology for cloud enterprise edition, SAPACTIVATE methodology for cloud project services edition and SAPACTIVATE methodology for cloud marketing edition (coming soon), covering each of the different Public Cloud offerings. SFSF, C4C and Ariba will transition to SAP Activate later in H2 2015.

Methodology Accelerators

SAP Activate offeres Accelerators for each of the different phases of the implementation:

PREPARE:

Available Accelerators:

• Delivery supplement
• Solution scope
• Software and delivery requirements
• WBS, schedule and effort estimation
• Project Governance and Management Plans

EXPLORE:

Available Accelerators:

• Master data overview
• Organizational data overview
• Process flow diagrams
• SAP Solution Manager template
• Project backlog template

REALIZE:

Available Accelerators:

• Configuration guides
• Test scripts
• Agile approach guides
• Cutover plan

DEPLOY:

Available Accelerators:

• Project schedule
• Cutover plan
• Operations Setup Guide

Social Collaboration

One of the biggest benefits of sharing the methodology content in the SAP JAM is that the space provides opportunity for collaboration between users. You can leave comments on any element in the site. Let us know how the document or guidance worked for you. You can expect response from the SAP subject matter experts, moderators and potentially from other users. We encourage you to use this platform to let us know what you think. Share how the SAP Activate methodology works for you. We will use this feedback to fine tune the methodology content over time.

How to access SAPACTIVATE

SAPACTIVATE is embedded in SAP S/4HANA. No additional licenses are required.It can be accessed

1. via SAP JAM (for customers, partners and SAP Employees)
2. via SAP Solution Manager (for Project Teams)

Fig.:SAPACTIVATE Entry Screen

SAPACTIVATE Illustrative video

Summary

• SAPACTIVATE is a game changing consumption experience introduced with SAP S/4HANA
• SAPACTIVATE is a unique combination of SAP Best Practices, Methodology, and SAP Guided Configuration delivered with a reference solution
• SAPACTIVATE enables customers to start fast, build smart, and run simple while continuously innovating in the cloud and anywhere

Find similar posts on Blog on SAP S/4HANA

Follow me on Twitter: Salva Gimeno SAP (@SalvaGimenoSAP) | Twitter

Follow me on LinkedIn: https://br.linkedin.com/in/salvadorgimeno

In this document I am demonstrating how to setup Fiori apps on a two system landscape setup,

Fiori (Netweaver System) as FrontEnd and Simple Finance (ERP System) as Backend.

We can also make use of one frontend to connect with multiple backend systems, though there are few modifications required(Its an easy way than to setup whole new frontend every time)   

FrontEnd

• Install NW 740 (any DB)-  with latest SAP_UI
• SAP Gateway
• Standard configFiori
• Setup CUA (User mapping to BS)
• Install sapwebdispacher
• Defining System alias for BS & consume services /IWFND/MAINT_SERVICE

BackEnd

• Install S4 Application -BackEnd
• HDB with HANA XS
• Smart Business Cockpits will have components to install on FS & BS, In this case..

           (SAP SMART BUSINESS FOR SFIN 2.0)

            FS : UIAPFI70

            BS : HANA_CONETNT

                                                      -- The End --

Dear Friends,

I would like to share my experience of SAP S4HANA sFIN On Premise Edition 1503 Upgrade from 1505 to 1508 (aka sFIN 2.0 SP01 to SP02) SP Upgrade.

Source : SAP ECC 6 EHP7 SP8 (NW SP10) sFIN 2.0 1505

Target  : SAP ECC 6 EHP7 SP9 (NW SP11) sFIN 2.0 1508

We had total 5 productive clients in the system.

Pre-requisites:

1. Make sure all conditions should meet as per SAP note  2117481 - Release Information Note: SAP Simple Finance, on-premise edition 1503

2. HANA should be on Revision 97 is a part of the above note.

Execution phase runtime.

Execution took approximate 6 hours.

Below 2 phases took maximum time during the Execution phase.

• TABIM_UPG can be optimized during the execution phase as well.
• RUTDDLSCREATE need to optimized before starting the upgrade.This phase took 2 hours. We can only implement the below notes before starting the upgrade to optimize its run time. I was not aware about these notes during the Upgrade.

# 2150018 - CDS views missing from database

# 2160038 - Error message during activation: View cannot be deleted from the database

sFIN Issue: 

We faced one issue related to sFIN in Pre Processing phase   MAIN_SHDIMP/SUBMOD_SHD_RUN/START_SHDI_SHD2!

• 2196474 - Syntax error in program SAPLSEWORKINGAREA during installation of SAPKB74011

Solution: Applied attached note to fix it.

Please apply this note before starting sFIN SP Upgrade to avoid this issue.

Without this issue, sFIN upgrade was smoother and similar to any other Support Pack Upgrade.

DB Size :

Regards

Sahil

In my documentation I’ll explain how to migrate a current on-premise ERP system running on ASE database to S4Hana by using DMO for SUM 1.0 SP13.

For my setup the migration will encore on Hana rev100 with SAP Simple Finance, On-Premise Edition 1503 (SAP HANA ANALY. FOR SFIN 2.0)

Disclaimer: For my deployment I did not consider the sizing exercise, always do it in order to avoid issue. Also no custom code reside on my system, so if it's your case run the custom code management for Hana migration.

In order execution

• Generate the upgrade queue for Ehp7
• Install the new Hana database
• Download DMO for SUM 1.0 SP13
• Run the DMO process
• Install and configure SFIN 2.0

Guide used

SAP Business Suite powered by SAP HANA Cookbook

SAP Simple Finance, On-Premise Edition 1503 SPS 1508

SAP HANA Master Guide

Note used

1813548 - Database Migration Option (DMO) of SUM 1.0 up to SP13

2144096 - Installation Note for SAP HANA Live for SAP Simple Finance, On-Premise Edition 1503

2171868 - SAP Simple Finance: Information on Product Name and Versioning Changes as of May 2015

2117481 - Release Information Note: SAP Simple Finance, on-premise edition 1503

2157996 - SAP Simple Finance, on-premise edition: Checklist for Technical Installation / Upgrade

1737650 - EHP7 for SAP ERP 6.0 SP Stacks - Release & Information Note

1974650 - SAP Simple Finance, on-premise edition: ICF Service Information

1971111 - SAP Simple Finance, on-premise edition: Browser Requirements

1946054 - SAP Simple Finance, on-premise edition: Transaction codes and programs - Comparison to EHP7 for SAP ERP 6.0

2127080 - Release restrictions for SAP Simple Finance on-premise edition 1503

1972819 - Setup Integrated Business Planning for Finance

Link used

Help SAP Hana for SFIN 2.0

Overview Architecture

The following architecture is based on physical server for Hana and virtual server for the ERP system. I’ll use our Hana CoE to perform this migration to S4Hana.

For this configuration I’ll intentionally split the DMO process for SFin 2.0 installation, in other word I’ll first upgrade and migrate with DMO and then do the SFin 2.0 installation.

Generate the upgrade queue for Ehp7

My system is already register In Solman, I need to generate my queue to target Netweaver 7.40 and ERP 6.0 Ehp7

Download your stack xml and the package.

Install the new Hana Database

The rep-requisite before doing the migration is to have the new database available, so I’ll create the new database on the revision 100.

Since the installation is straight forward I’ll just show the summary for the install

Download DMO for SUM 1.0 SP13

From the SL Toolset web page download the last SUM version

Run the DMO process

My system has been backed up, the stack has been downloaded and the DMO for SUM is decompressed in my /usr/sap/<SID>, I can now start my migration.

Before you start the upgrade process take in consideration that some works needs to be perform before and after. Refer to the upgrade guide ERP 6.0 Ehp7

Not like the regular SUM process the DMO run by using the hostagent option

The upgrade/migration done make the check on the system to see which DB is operate and of course I do a backup of my system

Install and configure SFIN 2.0

S4HANA (currently release SFIN 2.0) deployment consist of 2 main component

•    SAP SFINANCIALS 2.0 ADD-ON installation/Upgrade (ERP side)

•    SAP HANA Live 2.0 VDM for SFIN On-Premise Edition (Hana side)

Important consideration before to start:

•    Prepare the application data migration before the add-on is installed or upgraded. This requires knowledge in application FI, CO and Asset Accounting.

•    Potentially existing data inconsistencies need to be resolved before the add-on installation / upgrade. Afterwards this may no longer be possible

•    Check whether the add-on installation will be possible, verify the currently installed software components in regards to their compatibility with SAP Simple Finance 2.0 (SAP Note 2103558)

•    Check customer-owned code for any adaptations needed to comply with the new SAP Simple Finance data model, otherwise the SAP Simple Finance installation may be blocked with ABAP dictionary activation errors.

SAP SFINANCIALS 2.0 ADD-ON installation/Upgrade (ERP side)

For my document I use the add-on: SAP Simple Finance, on-premise edition 1503 support package stack 1508

Based on:

•    SAP enhancement package 7 for SAP ERP 6.0 SP Stack 09

•    SAP NetWeaver 7.40 SP Stack 11

•    Kernel used kernel 7.42 SP 32 or higher

This specific add-on doesn’t support the regular installation over SAINT, run the SUM to install and update it. Before to run the process implement the relevant note according the note 2117481

Once the note are implemented, from solution manager (MOPZ) download the add-on

Once the package completely downloaded run the DMO process to install it

Once process done check out the new installed component

The Abap add-on installed now, the SAP Simple Finance, On-Premise Edition 1503 component needs to install on Hana.

Check the second part of the document - S/4Hana Setup on-premise (part 2)

In the second section of this document, i'll explain how to deploy the SFIN 2.0 Hana component and make the configuration on the abap side.

The first part of the configuration can be check here - S/4Hana Setup on-premise (part 1)

SAP HANA Live 2.0 VDM for SFIN On-Premise Edition (Hana side)

In order to deploy the SFIN 2.0 specific views on Hana, 2 Hana Live component will need to be install on Hana

•    SAP HANA Live 1.0 for SAP ERP (SAP HANA ANALYTICS FOR ERP 1.0)

•    SAP HANA Live 2.0 for SAP Simple Finance, on-premise edition (SAP HANA ANALY. FOR SFIN 2.0)

Select the following package on the market place and deploy it over HALM in this order :

To load this add-on into I’ll use hdbalm command

“./hdbalm –u <user> -h <hostname> -p <port> install <zip package>”

And install the second add-on for SFIN 2.0

Always check the deployment log once done and make some check from product deployed in HALM web

SAP HANA SFIN 2.0 abap installation post work

In order to be able to use SFIN 2.0 on the abap side, post activities needs to be perform:

•    Activate Financial Extension

•    Activate ICF services

I will first turn Fin. Extension switch to “on” in SFW5 transaction

Several ICF services needs to be activated in order to use SFIN 2.0, since many of it needs to activate I won’t list them all so refer to the following note:

•    1974650 - SAP Simple Finance, on-premise edition: ICF Service Information

From an installation perspective for the mandatory component, it’s all done, the next phase is now the configuration and i will explain it below.

SAP HANA SFIN 2.0 configuration

SAP Simple Finance, on-premise edition leverages the latest features of BI Content and integrated business planning applications. The following configuration steps need to be performed in the SAP Simple Finance system:

•    Activate Embedded BW

•    Switch on business function

•    Activate Content Bundle for New Financial Planning

•    Activate Planning and Consolidation Unified

For my case I did setup a client 200 for BW and also create the logical system name

In SE03 make the namespace with prefix /BI0/ and /BIC/as modifiable

With DDIC run RSA1 (set the parameter RSWAD_SKIP_JAVA and value 'X' before to avoid java error)

Once completed check in RSD1 if ORSPL* InfoObject exist in active version

Project planning requires the activation of business function FIN_CO_CCMGMT as a technical prerequisite. Cost center planning requires the activation of business function FIN_CO_CCPLAN, so i will turn them on in SFW5

The BF activated, now I can activate Content Bundle for New Financial Planning, in order to do it:

1.    Activate DataSource 0PROFIT_CTR_0106_HIER

2.    Activate Content Bundle

3.    Activate Analysis Office Workbooks

4.    Copy default customizing settings to your planning clients

In RSA5 expend the complete list of data source and activate “0PROFIT_CTR_0106_HIER”

Warning

Run the transaction “BSANLY_BI_ACTIVATION”

Make sure you select the following entries and activate

During the activation the “select source system” windows appear, do not select any system, and click cancel to pass it.

Once completed with no error

Run now the transaction RSOR to activate Analysis Office Workbooks

Select all workbook starting with /ERP/SFIN_A*, in addition /ERP/SFIN_M01_Q1000_WB01, ERP/SFIN_V10_Q0001_WB01, and /ERP/SFIN_V11_Q0001_WB01 and transfer the selection

/ERP/SFIN_M01_Q1000_WB01 (Income Statement by Market Segment)

ERP/SFIN_V10_Q0001_WB01 (Work Analysis)

/ERP/SFIN_V11_Q0001_WB01 (WIP Analysis)

Check all object and click install

Once completed I copy the ACT01 category from client 000 to my Planning client (100)

Note: you have to open the client 000 for client specific object

The transport created it needs to imported in client 100

Once the transport imported activate Planning and Consolidation Unified in SM30

Add the following

The configuration is completed, now the functional consultant can interfere with the system to make their necessary configuration according their needs.

In my next documentation i'll continue with the client side configuration based on "SAP Fiori for SAP Simple Finance, On-Premise Edition" and  "Business for SAP Simple Finance, On-Premise Edition"

Williams

SAP APO stands for Advanced Planner and Optimizer. SAP APO is a supply chain planning tool; that helps organizations manage their supply chain. SAP APO had primarily four modules DP (Demand Planning), SNP (Supply Network Planning),PPDS (Production Planning and Detail Scheduling), GATP (Global Available to Promise). Learning SAP APO ideally needs some domain background but not mandatory. In-case one is planning to learn SAP APO but is new to supply chain and SAP its suggested to spend time to learning basic supply chain concepts. As a tool SAP APO is very interesting and fun to learn compared to other modules offer by SAP.

Over the past few years, SAP has extended its planning footprint beyond SAP APO with the introduction of SAP Sales and Operations Planning, SAP Demand Signal Management, and SAP Enterprise Inventory and Service-Level Optimization. Based on the business drivers discussed at the beginning of this article, SAP envisions a state-of-the-art demand network that puts the customer at the centres of all processes and connects all the business partners required to fulfil the demand with the speed customers are expecting, while meeting all efficiency and profitability goals. With this new approach, SAP decided to simplify the overall planning platform with speed, customer-centricity, and responsiveness in mind. The SAP approach leverages SAP HANA technology and enables a common data model, allowing for real-time data across supply chain planning solutions Moving from an on- premise technology to a purpose-built, cloud-based technology gives customers multiple deployment options moving  forward.

The new solutions enable companies to transform their supply chains into demand networks by:

>Simplifying and coordinating the planning experience for users across functions through a new user interface with embedded collaboration technology and the option for planners to work within Microsoft Excel

>Reacting more quickly to changes in demand to capture more sales by leveraging SAP HANA to provide demand networks with real-time monitoring and a focus on short-term planning

>Enabling more frequent planning cycles by avoiding any latency due to data transfer between different planning systems

>Ensuring plans are executed in operational systems by incorporating predictive  analytics (for example, demand sensing) algorithms in combination with optimization (for example, multi-echelon inventory optimization) to translate plans into operational systems

>  Reducing complexity and time to achieve business value through deployment in SAP Cloud

Agenda:

> SAP APO/SCM overview

> Demand Planning

> Supply Network Planning

> Global ATP

> Production Planning & Detail Scheduling

1.>SAP APO/SCM Overview& Architecture:

SAP Fiori for SAP HANA Live for SAP APO

SAP Business Objects business intelligence solutions

If you want to use SAP APO data in these analytic applications, you must make it available in SAP HANA. To transfer SAP APO data to SAP HANA, you use the replication functions of the APO Analytics (SCM-APO-ANA) component.

2.>Demand Planning (DP):

The Demand Planning (DP) component of SAP Advanced Planner and Optimizer (SAP APO) is a complex, high-performance, and flexible instrument that supports the sales/requirements planning process in your company. User-specific planning layouts and interactive planning books allow not only the inclusion of various departments, but also of other companies, in the forecast creation process. The configuration of demand planning is an important factor for a successful implementation of the system. This is performed, as it is also done for the Supply Network Planning component

> Info Cube and Transfer Structures BW concepts

> Transfer data from ECC

> Create CVC

> MPOS and Planning Area

> Create Planning Book

> Forecast Calculation

> Promotion Planning

> Life cycle Planning

> Error Technique

> Release /Transfer Profile

> Mass Processing

> Back ground jobs in demand planning

> Process Chains

> Macro

3.>Supply Network Planning (SNP):

SNP ensures the optimal uses of Manufacturing, Distribution and Transportation of Resources to meet forecasts and actual demand while considering all constraints in the supply chain. SNP plans production, procurement and transportation through the entire supply Supply network by using optimizing and heuristic approaches

A number of constraints are taken into account during the SNP Optimization run, including capacity constraints that have been defined for resources. You usually use the SNP Optimizer profile to specify which constraints you want the optimizer to consider during the optimization run. However, in certain circumstances, it might be necessary to define constraints that are time-based;

> An upper bound for external procurement (at product-location level)

> An upper bound for stock on hand (at product-location level)

> An upper bound for production (at product-PPM/PDS level)

> An upper bound for transportation (at product-transportation lane level)

> An upper bound and a lower bound for total receipts (at product-location level)

4. GATP:

GATP stands for Global Available to Promise. It is part of SAP SCM-APO tool.

GATP is like promising to customer demands based on some predefined availability checks on your existing stocks. It uses ATP rules to decide whether the customer demands can be confirmed against the available stocks.

It is a tool by which you try to maximize your servicing capacity to the customer by using different methods of GATP.

1. E.g. you define if a customer asks for product A if A is not available you can give him B or C or D or ALL (Functionality product substitution); if these products are not available in asked location, system will look for other locations (Functionality product substitution).

If nothing is available, system triggers production (using Available to Promise).

In short how it helps is, by reducing customer demand loss by increasing the serviceability.

ATP versus GATP

ATP functionality is already there in R/3 but with limitations:-

1. ATP-Availability check in ERP is limited to single location.

2. Product Substitution is manual and it is limited to single material substitution.

3. Production cannot be called from ATP check for a MTS product.

4. No simulation.

Global ATP checks the entire network (other plants), product / material substitutions defined in the condition and also production from alternative location based on the advanced functionality called Rule based ATP.

> Alternative Product

> Alternative Location

> Production (Alternation PPM).

5.>Production Planning & Detail Scheduling (PP/DS):

It Determines the Production Planning and Detailed Scheduling (PP/DS) reactions to planning-relevant events

Determines the pegging-relevant quantity of customer requirements across all applications:

Determining the reactions to planning-relevant events:

This usage is specific to PP/DS. In the PP planning procedure, for each planning-relevant event that can occur for a location product, you specify which action Production Planning and Detailed Scheduling (PP/DS) should automatically execute when this event occurs. A planning-relevant event. SAP delivers standard planning procedures that it recommends you to use in certain scenarios. However, you can also define your own planning procedures. You should reconcile these carefully with your planning processes, because only certain event-action combinations can be used effectively within a planning procedure.

To be able to plan a product using PP/DS, you must have entered a planning procedure in the location product master. You define planning procedures in Customizing for Production Planning and Detailed Scheduling (PP/DS).

Determining the pegging-relevant quantity for customer requirements

You define in the planning procedure whether the desired quantity or the confirmed quantity of customer requirements is relevant for pegging. This setting is relevant for all planning applications in SAP APO.

The PP planning procedure contains the following elements:

Planning-relevant event

SAP provides a selection of events that are typical in production planning. The events can be divided into the following groups:

Changing master data in the SAP APO system (such as product, plan, or transportation lane)

Changing stock in the  OLTP system

Creating or changing requirements elements of orders (customer requirements, planned independent requirements, dependent requirements, and stock transport requirements) in PP/DS or in the  OLTP system

Creating or changing receipt elements for in-house production orders or external procurement orders in PP/DS or in the OLTP system.

Test drive S/4 Hana – cloud edition.

The test drive is available for Project management, Finance and Marketing

You can create procurement orders as well. Available in Fiori style tiles. Looks good, also apprehensive if this style can match the utility value of the SAP GUI. This document covers the Procurement process only.

Procurement process:

• Basic difference is the Ux. The layouts are simplified and user friendly.
• Prompts on typing is not available. You need to go into search mode to pull up a vendor. Which is same as in SAP Gui
• While creating a PO, I wanted to add a few pricing conditions. Clicked on the item value link –but could not add new pricing elements
• WBS element is now called Work package name
• When you display a vendor you can get all information related to the vendor in one screen:
  • Master data
  • Info record
  • Purchase orders, status and values
  • Invoices
  • Vendor balances, line items
  • Payment blocks etc
• Similarly when you display a material –you get every information related to the material
• Collaboration is easy as there is an email link at each object
• But no other means of collaboration or social media seemed to be available
• The best way of retrieving my purchase order seemed to be via the purchase group. My PO would have been nice. Prompts and intelligent suggestions are missing. This is definitely a must in today’s world. Currently a significant area for improvement for S/4
• Goods Receipt: I had missed selecting a Storage location in the PO. During GR it just stopped me without allowing any way to enter the GR. Grrr…
• Back to PO create with storage location selected
• In the midst of GR creation, I thought lets check the PO and it had problems..
• So can I not operate on multiple screens? Right clicked on the PO link and no “new tab” option available.
• Could not post the GRN as the combination of Material, Plant with Storage location was not maintained. Looks like auto create of storage location has not been set.
• Invoice processing: Again searching a PO is not friendly enough. Posting is very unfriendly if some information like tax code is missed out in the PO.

Overall my sense is:

Pros:

1. Nice screen layout, friendly to the eyes
2. Functionality not compromised, I assume the configuration flexibility is still the same
3. Reporting for objects are easy to find

Cons:

1. Number of teething issues especially related to search
2. If the initial document is not complete then subsequent transactions cannot be performed
3. I see similar rigidity as core ECC

Questions:

1. Given that all aspects need to be configured what is the timeline expected for cloud ERP deployment? Competitors claim 90 days. What is SAP’s take?
2. Most of the changes I see are in the Ux, I am aware that the columnar data storage against each record is the other change with reduction in number of tables. This will drastically alter the performance. Is there anything else I am missing?

Hi everyone,

SAP Simple Finance, on-premise edition marked the first step in our SAP Business Suite 4 SAP HANA roadmap for customers. With the installation of the SAP Simple Finance, on – premise edition the customer is joining the SAP S/4HANA family. However, with the SAP S/4HANA, on – premise edition 1511 (Q4/2015) the functional scope will be enhanced with additional application innovation in the logistics area. 

The following blog describes at a glance technical details and pre-requisites of the migration path from SAP Business Suite to SAP Simple Finance, on-premise edition 1503 and the migration path from SAP Business Suite to SAP S/4HANA, on-premise edition 1511. Regarding the SAP S/4HANA, on-premise edition 1511 the chapter below describes a future development and should be understood in the sense that they are "planned to be" like described.

Happy to read your feedback!.

Kind Regards,

Frank

_______________________________

Introduction

SAP Simple Finance, on-premise edition marked the first step in our SAP Business Suite 4 SAP HANA roadmap for customers. With the installation of the SAP Simple Finance, on – premise edition the customer is joining the SAP S/4HANA family.  However, with the SAP S/4HANA, on – premise edition 1511 (Q4/2015) the functional scope will be enhanced with additional application innovation in the logistics area.

Depending on customer’s requirements and roadmaps there are different transition paths to SAP S/4HANA. The following figure displays an (abstract) roadmap of a specific customer on his journey to SAP S/4HANA, on-premise edition. This customer is planning to move to SAP S/4HANA with a roadmap which goes over several years. First the customer moved to SAP Business Suite on HANA, now he plans to go to SAP Simple Finance, on-premise edition and then as a third step to SAP S/4HANA, on-premise edition which does include application innovations in logistics area.

Figure 1: Move to SAP S/4HANA, on-premise edition – a possible customer Roadmap in several steps

In addition to the technical move to SAP S/4HANA this specific customer is simplifying their overall system landscape. Currently, several SAP Business Suite Systems are used in the different regions; however, a central SAP S/4HANA system per region is planned as a target.

For a different customer, a different roadmap might be applicable. The following figure gives an outlook to the to SAP S/4HANA, on-premise edition 1511 (Q4/2015 delivery). Here, it is planned to offer a path where the customer can move to SAP S/4HANA, on-premise edition 1511 (Q4/2015 delivery) from a SAP Business Suite start release (for example SAP ERP 6.0) still on anyDB.

Figure 2: Move to SAP S/4HANA, on-premise edition 1511 (Q4/2015 delivery) – a possible future roadmap

Technical details and pre-requisites of the different transition paths

SAP Simple Finance, on-premise edition

Today (as of June 2015) a customer can join the SAP S/4HANA family by installing SAP Simple Finance. In different documents you can find the term “exchange innovation add-on”, because SAP Simple Finance replaces the classic ERP Financials with application innovation in the financial area.

More information about SAP Simple Finance, on-premise edition can be found here:

• Line of Business - Finance: http://go.sap.com/solution/lob/finance.html
• SAP Help:http://help.sap.com/sfin200

SAP Notes related to SAP Simple Finance:

• For Information on product name see SAP note:2171868
• For the latest updates refer to SAP note 2117481
• For release restrictions see SAP note 2127080
• Compatibility of enterprise extensions, industry solutions, and add-ons can be found in SAP Note 2119188.

Technical Prerequisites and Software Products

Technically the SAP Simple Finance, on-premise edition 1503 is based on:

• SAP enhancement package 7 for SAP ERP 6.0
• SAP NetWeaver 7.40
• SAP HANA database

Figure 3: SAP Simple Finance, on-premise edition 1503 (basically)

With the installation of SAP Simple Finance on-premise edition, several software units are installed.

• SAP Simple Finance, on-premise edition
• SAP HANA Live for SAP Simple Finance, on-premise edition
• SAP Fiori for SAP Simple Finance, on-premise edition
• SAP Smart Business for SAP Simple Finance, on-premise edition

More detailed information can be found in the Administrators Guidefor the SAP Simple Finance, on-premise edition 1503.

The transition path to SAP Simple Finance, on-premise edition

In the following constellations a one-step transition path from SAP Business Suite to SAP Simple Finance, on-premise edition 1503 is supported:

• One-Step Procedure for customers on anyDB, ABAP AS 7.0x, SAP ERP6.0 EHPx
• One-Step Procedure for customers on SAP HANA, ABAP AS 7.40, SAP ERP6.0 EHP7         
• One-Step Procedure for customers on SAP Simple Finance 1.0

These constellations are displayed in the following figures:

Figure 4: SAP Simple Finance, on-premise edition 1503 - One-Step Procedure for customers on anyDB, ABAP AS 7.0x, SAP ERP6.0 EHPx

Figure 5: SAP Simple Finance, on-premise edition 1503 - One-Step Procedure for customers on SAP HANA, ABAP AS 7.40, SAP ERP6.0 EHP7

Figure 6: SAP Simple Finance, on-premise edition 1503 - One-Step Procedure for customers on SAP Simple Finance add-on 1.0

Additional Remarks:

• It is planned to deliver further innovations for SAP Simple Finance in 2016. It is planned to provide appropriate migrated paths then. 

SAP S/4HANA, on-premise edition 1511

With the SAP S/4HANA, on-premise edition 1511 (Q4 / 2015 delivery) it is planned to enhance the functional scope with application innovation and simplification in the logistics area. Now with application innovation in financials and logistics area we could speak of the SAP S/4HANA Core. More application innovations are planned to enhance the SAP S/4HANA Core then in future.  In addition to the application simplification in financials and logistics area the SAP S/4 HANA Core consists of the SAP Fiori user experience (UX), and innovations for the digital economy based on SAP HANA.

Figure 7: SAP S/4HANA, on-premise edition 1511 - technical stack (basically)

To ensure a smooth transition to SAP S/4HANA, on-premise edition traditional features will stay available. Besides application specific functionality, just the SAP GUI based user interface technology should be listed as still available functionality after the move to SAP S/4HANA.

Technical Prerequisites and Software Products

Technically the SAP S/4HANA, on-premise edition 1511 is based on:

• SAP S/4HANA core components (including simplified financials and simplified logistics)
• SAP NetWeaver 7.50
• SAP HANA database

The transition path to SAP S/4HANA, on-premise edition 1511

In the following constellations a one-step transition path from SAP Business Suite to SAP S/4HANA, on-premise edition is supported:

• One-Step Procedure for customers on anyDB, ABAP AS 7.0x, SAP ERP6.0 EHPx
• One-Step Procedure for customers on SAP HANA, ABAP AS 7.0x, SAP ERP6.0 EHPx
• One-Step Procedure for customers on SAP HANA, ABAP AS 7.40, SAP ERP6.0 EHP7, SAP Simple Finance add-on 1.0 / SAP Simple Finance, on-premise edition 1503

These constellations are displayed in the following figures:

Figure 8: SAP S/4HANA, on-premise edition 1511 - One-Step Procedure for customers on anyDB, SAP ERPx

Figure 9: SAP S/4HANA, on-premise edition 1511 - One-Step Procedure for customers on SAP HANA, SAP ERP6.0 EHP7

Figure 10: SAP S/4HANA, on-premise edition 1511 - One-Step Procedure for customers on SAP Simple Finance

Additional Remarks:

• An explicit upgrade to Enhancement Package 7 is not required for the move to SAP S/4HANA, on-premise edition 1511. See figure 8 and figure 9 above.
• Customer using older SAP Business Suite Releases (for example still on Non-Unicode) can move to SAP S/4HANA, on-premise edition 1511 in a two-step transition approach.
• The installation of the SAP Fiori UI software components are a separate installation step and typically installed on a separate, central gateway server. Due to simplification reasons the figures above do not visualize this aspect.

SAP S/4HANA 1511 - Initial Version (SPS 00) -

This document is an effort to captures a summarized view of "Simplification-Listing" & the restrictions of KEY Functionalities.

Base information has been referred from SAP Notes, Release Information, S/4HANA 1511 sap help.

2189824 - SAP S/4HANA, on-premise edition 1511: Release Information Note

2214213 - SAP S/4HANA, on-premise edition 1511: Restriction Note

2214409 - The release information for Add-Ons.

http://help.sap.com/s4hana_op_1511

Release of SAP S/4HANA, on-premise edition 1511

In November 2015 (1511) updates have been released for both, SAP S/4HANA, on-premise and cloud edition. In November 2015, SAP delivered a massive wave of simplification and innovation in the core of SAP S/4HANA. With this delivery, enterprises can drive unprecedented business value with innovative use-cases - in core financial and operational areas such as in logistics – taking full advantage of a simplified data model and a responsive user experience.

Key simplifications and innovations include:

• Optimized working capital with new accounts payables and receivables cockpits
• Decreased stock buffers with simplified data model in inventory management for real-time, high-volume processing
• Increased visibility with real-time stock and material flow insight
• Reduced manufacturing cycle time with streamlined material flow for internal requirements (MRP)
• Augmented reactivity with real-time monitoring of production orders regarding flow and critical issues
• Improved operational decisions with easy simulation of supply alternatives
• Lower procurement costs with standard integration to the Ariba Business Network
• Better customer service with new sales order fulfillment cockpit for instantly identifying bottlenecks and issues

For more information see as well the SCN blog from Sven Denecken: Link

The System Conversion to SAP S/4HANA, on-premise edition 1511

Different transition paths are supported with SAP S/4HANA, on-premise edition 1511:

• New Implementation
  New installation of SAP S/4HANA e.g. for customers migrating a legacy system.
• System Conversion
  Customers who want to change their current system into a SAP S/4HANA system.
• Landscape Transformation
  Customers who want to consolidate their landscape or to selectively transform data into a SAP S/4HANA system.

The SAP S/4HANA, on-premise edition 1511 system conversion supports one-step procedure (Database, SAP NetWeaver and application transition in one step) for SAP ERP 6.0 EHP x…7 systems. System Conversion requires a Unicode (UC) source system. Non-Unicode source systems will require a two-step approach (first move to Unicode then to SAP S/4HANA, on-premise edition 1511).

Basically it can be distinguished between technical and semantic tasks during the system conversion. The technical installation procedure is based on established lifecycle management tools (Maintenance Planner, Software Update Manager [SUM] and Database Migration Option [DMO]). Due to the fact that SAP S/4HANA is a new product line (and not the successor of SAP Business Suite) things are done differently in SAP S/4HANA.

• Many of the changes are technical in nature and have no or only limited impact on peoples work and thus do not trigger business change management. Such changes will be mandatory when converting a system to SAP S/4HANA.
• Other decisions are more of a strategic nature determining which version of functional support will evolve into the digital era and provide the capabilities demanded from the unstoppable business process innovation. Where those strategic directions demand change management through adoption, SAP at large keeps the traditional capabilities available as compatibility scope enabling a rather technical migration of these processes and leaving the time of change management at customer decision that may well happen when initially converting or at a later point in time.

To allow our customers a better planning and estimation of their way to SAP S/4HANA, we have created the “Simplification List for SAP S/4HANA, on-premise edition 1511”. In this list we are describing in detail on a functional level what happens in S/4HANA to individual transactions and solution capabilities. In some cases, we have merged certain functionality with other elements or reflected it within a new solution / architecture compared to the SAP Business Suite products.

The technical procedure – well established tooling

Maintenance Planner

The Maintenance Planner checks the system with regards to business functions, industry solutions, and add-ons. If there is no valid path for the conversion (for example, the add-on is not released yet), the Maintenance Planner prevents the conversion.

The Maintenance Planner is a pre-requisite for the system conversion to SAP S/4HANA, on-premise edition 1511. The Maintenance Optimizer (MOPZ) is not used

For more information regarding Maintenance Planner see SAP Help: http://help.sap.com/maintenanceplanner

Software Update Manager (SUM)

Software Update Manager (SUM) is the technical tool for system conversion to SAP S/4HANA, on-premise edition 1511.

Note: You must run the Maintenance Planner before the SUM.

For all information about using the SUM, please see the document Conversion of SAP Systems to SAP S/4HANA, on-premise edition Using Software Update Manager 1.0 SP15 available at:

• service.sap.com/sltoolset (LINK)
  • Software Logistics Toolset 1.0
  • Section "Documentation"
  • System Maintenance

Database Migration Option (DMO)

DMO - the one-step-migration to SAP HANA database for SAP systems. It is called "database migration option (DMO) of Software Update Manager (SUM)". For SAP S/4HANA it combines the installation of the SAP S/4HANA, on-premise software and database migration to SAP HANA in one tool

See the following SCN Blog with helpful information regarding DMO - SCN LINK

Adoption Tasks – how SAP support the customer

Simplification List for SAP S/4HANA, on-premise edition 1511

To allow our customers a better planning and estimation of their way to SAP S/4HANA, we have created the “Simplification List for SAP S/4HANA, on-premise edition 1511”. In this list we are describing in detail on a functional level what happens in S/4HANA to individual transactions and solution capabilities. In some cases, we have merged certain functionality with other elements or reflected it within a new solution / architecture compared to the SAP Business Suite products.

For more information see Simplification List for SAP S/4HANA, on-premise edition 1511: PDF

Conversion Pre-Checks

Pre-checks are shipped as SAP Notes to customers that want to convert to SAP S/4HANA. Customers can use these pre-checks to find out what mandatory steps they have to carry out before converting to S/4HANA. The results list the instances that need addressing before attempting the conversion process. The checks are run twice again during the conversion process: both times in the Software Update Manager (SUM). The conversion is stopped if errors persist.

Implement SAP Note 2182725, and all the related notes attached to it. Make sure to use latest version of this note and regularly check for updates of all attached notes. Implement and run these reports on every system (Sandbox, DEV, QA, PROD) you want to convert to SAP S/4HANA, on-premise edition 1511. Report R_S4_PRE_TRANSITION_CHECKS.

Custom Code Checks

These checks are based on the Simplification list concept. Before converting to SAP S/4HANA, on-premise edition 1511 you need to check your custom code against the SAP S/4HANA simplifications. These simplifications are loaded into the Custom Code Check Tool. After you run the tool, you obtain a list of instances where your custom code does not comply with the scope and data structure of SAP S/4HANA 1511, on-premise edition

For more information about the Custom Code Check tool, see SAP Help Portal: Link

Related information – at a glance

Guides/Documentation

Related SAP Notes

With the release of SAP S/4 HANA On-premise Edition 1511 now released and available, there has not been any significant changes from ATP (Available-to-Promise) perspective which has direct business benefits. However, there will be future releases which will come up with such innovations. Below is the ECC ATP logic change which is part of this release.

Database table VBBS which contained aggregated sales requirements for the calculation of ATP will no longer be used. Instead, table VBBE will be used to refer to open quantity (OMENG) and confirmed quantity (VMENG) where each ATP-relevant requirement is explicitly stored. The old ERP ATP check coding will also refer to VBBE.

Reference Release Note: 2209696

Best regards

Parth Soneji