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 about SAP S/4HANA.

For comments regarding the cookbook itself, please use the accompanying blog.

Table of Contents

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

• Overview
• What is available now ?
• Further capabilities in context of SAP S/4HANA
• Transition Options
• Extensibility & Adaptation
• Best Practices & Enablement by SAP
  

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

• This first on-premise version of SAP S/4HANA was released in March 2015. Since this version currently has the highest implementation figures, there is a separate page on it in the cookbook.

3. Implementing SAP S/4HANA with SAP Activate

• This page gives an overview of the accelerators consolidated in SAP Activate that  help SAP partners and customers throughout the different phases of SAP S/4HANA implementation projects

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 ?

Further capabilities in context of SAP S/4HANA

SAP S/4HANA: Transition Options

SAP S/4HANA: Extensibility & Custom Code Adaptation

Best Practices & Enablement by SAP

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

The following check list is for SAP HANA On premise 1511 FS01. The activity check list covers Installation, Post installation and BASIC Check and Configuration, Project Requirement specific Configuration, Solution Manager Integration, BASIC SAP FIORI Configuration for S/4 HANA.

This document outline the step by step process of SAP S/4 HANA On premise edition 1511 post installation. For installation step please refer SAP S/4 HANA On premise edition 1511: Installation Step

Fresh SAP S/4 HANA On premise edition 1511: Post Installation Guide

1 Typographic Conventions

Type Style                                                        Represents                                                         Example

----------------------------------------------------------------------------------------------------------------------------------------------

<SAPSID>                                           SAP System name in uppercase          XXX

<SAP_release>                                   SAP release of the system                  608 (ERP 6.0 EHP 8)

<SYSNR>                                           SAP System number                           XX

<sapexe_dir>                                      Directory of the SAP Kernel                \usr\sap\XXX \sys\exe\run;

<hostname>                                        Host servername in lowercase             XXXXXXXXXX

<platform>                                          Os Version                                         suse linux x86_64

<mount Directory>                              SAP Mount Directory                         /sapmnt

1.1 References

S/4 Hana Help –

http://help.sap.com/s4hana_op_1511

Configure system to connect to the System Landscape Directory of SAP Net Weaver (SLD) - http://scn.sap.com/docs/DOC-8042

File system and directory structure please follow - http://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdf

Automated Initial Setup of ABAP-Based Systems Information published on SAP site - http://scn.sap.com/docs/DOC-41405(Do not run using DDIC User. Create a Separate user)

Perform Client Copy from '000' using suitable profile to client 100, based on if  'SAP Best Practice Content'  is to be used or not -

https://websmp210.sap-ag.de/~sapidp/012002523100012419282015E/

Importing solutions from SAP Best Practices content –

https://websmp206.sap-ag.de/~sapidp/012002523100012419282015E/frameset.htm?897f5c252e5d4d4494af6134d3c20a34.html

http://scn.sap.com/docs/DOC-72212  - Installation

http://scn.sap.com/docs/DOC-72952/ - Getting the most Recent Best Practices Content

2 Post installation activities

2.1   Initial Checks & Backup

2.2   TMS configuration

TMS can be configured separately or as part of Automated Initial Setup of Systems Based on SAP NetWeaver 7.4 & above ABAP.

2.3    Automated Initial Setup of Systems Based on SAP NetWeaver ABAP 7.4 & above

2.4 Activate Business Function Set

It is important to activate the Enterprise Business Functions after installing SAP S/4HANA ON-PREMISE, but before creating the client in which the content delivered with the SAP Best Practices for SAP S/4HANA, on-premise edition shall be activated.

2.5 Language Installation

2.6 Setting up a New best Practice client

The best-practice client setup is the prerequisite to successfully activate and deploy the SAP Best Practices content. Setting up a new best-practice client requires the configuration content from client 000 and the activation of the SAP Best Practices content depending on the selected business scope. The new client shall only contain the minimum required settings from client 000; all other settings shall be created by activating the SAP Best Practices content and match the business scope.

2.7 Carrying out setup for implementation

This section describes preparatory tasks which need to be carried out in order to use the implementation tools.

1. Provide users for content activation.
2. Prevent out of memory dumps

2.8 Preventing out of Memory Dumps

Some activities like the upload of installation data or defining the scope of customer solutions might cause a high memory consumption. Problems can be prevented by setting the memory to 6 GB.

The following options for creating the required clients should be discussed:

This concludes the post installation activities.

This document outline the most recent SAP Best Practices content before activating a solution. This steps needs to be performed after S/4 HANA On premise 1511 installation and post installation activities. Please refer the following document for Installation and Post Installation activities.

http://scn.sap.com/docs/DOC-72212  - Installation

http://scn.sap.com/docs/DOC-72798  - Post Installation

1 Getting the most recent SAP Best Practices Content

Before activating a solution, get the most recent SAP Best Practices content. This content is attached to SAP Notes, which are integrated into the central note 2246714 Information published on SAP site. Download the transport containing the data file with the content from the SAP Note and import it manually in client 000.

2 Importing solutions from SAP Best Practices Content

This document refers the steps to upgrade SAP HANA SPS using HLM with Screenshots.

From SPS 06 Rev 69 to SPS 08 Rev 85

Reference Notes :

2021789: SAP HANA Revision and Maintenance Strategy                      

1896320 - Error occurred while trying to start SAP HANA Life cycle Manager

***Take a backup of the HANA database and its configuration files***

The first step of HANA DB Upgrade is to upgrade the HLM – HANA Lifecycle Manager.

Open the SAP HANA Studio, right click on the system name  and select HANA Lifecycle Manager and select ‘Apply Single Support Packages’

In this case since the software were downloaded from SMP already select ‘Manually downloaded content’ option as shown below.

Browse through the software library path where the HLM software has been kept and select the file name.

HLM needs to be restarted after updation, select ‘Restart Now’ button.

HLM update is completed.

After the successful updation of HLM, new version is shown as 1.0.7.12.

We have to now update the HANA DB software and other software components.

Click on ‘Apply Single Support Packages’

In this case since HANA server is on a single instance but not on HA chose the option as ‘Normal’.

Chose option ‘Manually downloaded content‘, as the required software is already downloaded.

Browse through the software location directory at server level as below: Chose Next

Just before the upgrade preparation starts, shows the current and target versions

Click Next

SAP HANA Upgrade started

SAP HANA Upgrade completed

Once Execute Update phase completed we will find this screen as below

The Upgrade of SAP HANA System to SPS 08 Rev 85 is completed.

Check latest version in overview tab of SAP HANA system in SAP HANA Studio.

The Upgrade of SAP HANA System to SPS 08 Rev 85 is completed.

Check latest version in overview tab of SAP HANA system in SAP HANA Studio.

***Take a backup of the HANA database and its configuration files.

One of the great features brought by S/4HANA is HANA Live. With the help of ready to use hundreds of calculation and analitic views, real time multi dimensional operational reporting is available by using any presentation tool, like Lumira.

So with this document, I would like to share how to group related measures. In analytic views or calculation views, if you are using multiple measures and if you want to organize them, for example, to segregate the planned measures with the actual measures, then you can create a folder and group all related measures within this folder. 

First of all you need to connect to your HANA db with valid and authorized user, and Hana Live add-on should be installed. I have assumed that you have enough expertise about modelling in HANA Studio. Once you have managed to acces HANA Live with HANA Studio you will see this screen:

You can see the content under HBA->ecc->Calculation Views

After expanding Calculation Views, all available content will be visible and subject to modify, browse , etc... In my document I want to use AccountingDocumentJournalQuery which is the main query for real time transactional financial postings. Because of being main hub, there are many measures.

So organizing them into folders will help users.

Just double click on the query name and get the details, as it is shown on the screen shot above,click the folder icon and get the folders window with measures.

Simply create required folders and by drag and drop, organize your measures.

So simple and so useful.

Hope you like,

Cheers,

Sarhan.

Some SQL statement consolidated to execute the following details for DB running on HANA.

1. GENERAL INFORMATION  - eg DB name, OS User name, Instance name and number, Support Packages, Hosts etc.

2. PATCH HISTORY

3. SPACE INFORMATION

4. MEMORY INFORMATION

_________________________________________________________________________

Select 'GENERAL INFORMATION:' NAME,

  ' ' VALUE

FROM

  DUMMY

UNION ALL

( SELECT

    ' ',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    'Database type',

    'HANA'

  FROM

    DUMMY

)

UNION ALL

( SELECT

    'Evaluation time',

    TO_CHAR(CURRENT_TIMESTAMP, 'YYYY/MM/DD HH24:MI:SS')

  FROM

    DUMMY

)

UNION ALL

( SELECT

    'Evaluation user',

    CURRENT_USER

  FROM

    DUMMY

)

UNION ALL

( SELECT

    'OS user',

    VALUE || ' (' || COUNT(*) || ' host' || CASE WHEN COUNT(*) = 1 THEN '' ELSE 's' END || ')'

  FROM

    M_HOST_INFORMATION

  WHERE

    KEY = 'os_user'

  GROUP BY

    VALUE

  ORDER BY

    VALUE

)

UNION ALL

( SELECT

    'Startup time',

    TO_CHAR(START_TIME, 'YYYY/MM/DD HH24:MI:SS')

  FROM

    M_DATABASE

)

UNION ALL

( SELECT

    ' ',

    TO_CHAR(TO_TIMESTAMP(SUBSTR(VALUE, 1, 19), 'YYYY-MM-DD HH24:MI:SS'), 'YYYY/MM/DD

HH24:MI:SS') || ' (' || HOST || ')'

  FROM

    M_HOST_INFORMATION

  WHERE

    KEY = 'start_time'

  ORDER BY

    HOST

)

UNION ALL

( SELECT

    'Database name',

    DATABASE_NAME

  FROM

    M_DATABASE

)

UNION ALL

( SELECT

    'Instance name',

    VALUE

  FROM

    M_SYSTEM_OVERVIEW

  WHERE

    NAME = 'Instance ID'

)

UNION ALL

( SELECT

    'Instance number',

    VALUE

  FROM

    M_SYSTEM_OVERVIEW

  WHERE

    SECTION = 'System' AND

    NAME = 'Instance Number'

)

UNION ALL

( SELECT

    'OS Name',

    VALUE

  FROM

    M_HOST_Information

  WHERE

    Key='os_name'

)

UNION ALL

( SELECT

    'Support package stack',

    'SPS' || TO_CHAR(CASE

      WHEN REVISION >= 90             THEN 9

      WHEN REVISION BETWEEN 80 AND 89 THEN 8

      WHEN REVISION BETWEEN 70 AND 79 THEN 7

      WHEN REVISION BETWEEN 60 AND 69 THEN 6

      WHEN REVISION BETWEEN 45 AND 59 THEN 5

      WHEN REVISION BETWEEN 28 AND 44 THEN 4

      WHEN REVISION BETWEEN 20 AND 27 THEN 3

      WHEN REVISION BETWEEN 12 AND 19 THEN 2

      WHEN REVISION BETWEEN  1 AND 11 THEN 1

    END)

  FROM

  ( SELECT

      SUBSTR(VALUE, LOCATE(VALUE, '.', 1, 2) + 1, LOCATE(VALUE, '.', 1, 3) - LOCATE(VALUE, '.',

1, 2) - 1) REVISION

    FROM

      M_SYSTEM_OVERVIEW

    WHERE

      SECTION = 'System' AND

      NAME = 'Version'

   )

)

UNION ALL

( SELECT

    'Number of hosts',

    TO_CHAR(COUNT (DISTINCT HOST))

  FROM

    M_SERVICES

)

UNION ALL

( SELECT

    MAP(ROW_NUMBER () OVER (ORDER BY COORDINATOR_TYPE, HOST), 1, 'Host role', ' '),

    RPAD(COORDINATOR_TYPE, 8) || ' (' || HOST || ')'

  FROM

    M_SERVICES

  WHERE

    SERVICE_NAME = 'indexserver'

  ORDER BY

    COORDINATOR_TYPE,

    HOST

)

UNION ALL

( SELECT

    MAP(ROW_NUMBER () OVER (ORDER BY HOST), 1, 'Host directory', ' '),

    VALUE || ' (' || HOST || ')'

  FROM

    M_HOST_INFORMATION

  WHERE

    KEY = 'sap_retrieval_path'

  ORDER BY

    HOST

)

UNION ALL

( SELECT

    'Timezone',

    VALUE || ' (' || COUNT(*) || ' host' || CASE WHEN COUNT(*) = 1 THEN '' ELSE 's' END || ')'

  FROM

    M_HOST_INFORMATION

  WHERE

    KEY = 'timezone_name'

  GROUP BY

    VALUE

  ORDER BY

    VALUE

)

UNION ALL

( SELECT

    'Database log mode',

    VALUE || ' (default)'

  FROM

    M_INIFILE_CONTENTS

  WHERE

    SECTION = 'persistence' AND

    KEY = 'log_mode' AND

    LAYER_NAME = 'DEFAULT' AND

    NOT EXISTS ( SELECT * FROM M_INIFILE_CONTENTS WHERE SECTION = 'persistence' AND

      KEY = 'log_mode' AND LAYER_NAME = 'SYSTEM' )

)

UNION ALL

( SELECT

    ' ',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    'PATCH HISTORY:',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    ' ',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    TO_CHAR(INSTALL_TIME, 'YYYY/MM/DD HH24:MI:SS'),

    VERSION

  FROM

    M_DATABASE_HISTORY

  ORDER BY

    INSTALL_TIME DESC

)

UNION ALL

( SELECT

    ' ',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    'FEATURE INFORMATION:',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    ' ',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    'Database log mode',

    VALUE || ' (' || MAP(LAYER_NAME, 'HOST', HOST, 'SYSTEM', 'system wide') || ')'

  FROM

    M_INIFILE_CONTENTS

  WHERE

    SECTION = 'persistence' AND

    KEY = 'log_mode' AND

    LAYER_NAME IN ('HOST', 'SYSTEM')

)

UNION ALL

( SELECT

    'Automatic log backup',

    VALUE

  FROM

    M_INIFILE_CONTENTS

  WHERE

    SECTION = 'persistence' AND

    KEY = 'enable_auto_log_backup'

)

UNION ALL

( SELECT

    MAP(ROW_NUMBER () OVER (ORDER BY REPLICATION_PATH DESC), 1, 'Replication', ' '),

    IFNULL(REPLICATION_PATH, 'No')

  FROM

  ( SELECT DISTINCT

      REPLICATION_MODE || ' (' || SITE_NAME || ' -> ' || SECONDARY_SITE_NAME || ')'

REPLICATION_PATH

    FROM

      DUMMY LEFT OUTER JOIN

      M_SERVICE_REPLICATION ON

        1 = 1

    WHERE

      REPLICATION_MODE != ''

  )

  ORDER BY

    REPLICATION_PATH DESC

)

UNION ALL

( SELECT       /* SAP Note 2014148 */

    'Query result cache',

    MAX(VALUE)

  FROM

    M_INIFILE_CONTENTS

  WHERE

    FILE_NAME = 'indexserver.ini' AND

    SECTION = 'cache' AND

    KEY = 'resultcache_enabled'

)

UNION ALL

( SELECT

    ' ',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    'SPACE INFORMATION:',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    ' ',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    'Database size on disk (GB)',

    Value

  FROM

    M_SYSTEM_OVERVIEW

    Where

    Section = 'Disk' and Name = 'Data'

)

UNION ALL

( SELECT

    'Log size on disk (GB)',

    Value

  FROM

    M_SYSTEM_OVERVIEW

    Where

    Section = 'Disk' and Name = 'Log'

)

UNION ALL

( SELECT

    'Data backup size (GB)',

    LPAD(TO_DECIMAL(SUM(BACKUP_SIZE) / 1024 / 1024 / 1024, 12, 2), 13)

  FROM

  ( SELECT

      BACKUP_ID

    FROM

      M_BACKUP_CATALOG

    WHERE

      UTC_START_TIME =

      ( SELECT

          MAX(UTC_START_TIME) START_TIME

        FROM

          M_BACKUP_CATALOG

        WHERE

          ENTRY_TYPE_NAME = 'complete data backup' AND

          STATE_NAME = 'successful'

      )

  ) MB,

    M_BACKUP_CATALOG_FILES B

  WHERE

    B.BACKUP_ID = MB.BACKUP_ID

)

UNION ALL

( SELECT

    MAP(ROW_NUMBER () OVER (ORDER BY HOST), 1, 'Row store size total (GB)', ' '),

    LPAD(TO_DECIMAL(SUM(ALLOCATED_SIZE) / 1024 / 1024 / 1024, 12, 2), 13) || ' (' || HOST || ')'

  FROM

    M_RS_MEMORY

  GROUP BY

    HOST

  ORDER BY

    HOST

)

UNION ALL

( SELECT

    'Column store size total (GB)',

    LPAD(TO_DECIMAL(SUM(TABLE_SIZE) / 1024 / 1024 / 1024, 12, 2), 13)

  FROM

    M_TABLES

  WHERE

    TABLE_TYPE = 'COLUMN'

)

UNION ALL

( SELECT

    'Row store tables',

    LPAD(COUNT(*), 10) || '    (SAP schema: ' || LPAD(SUM(MAP(SUBSTR(SCHEMA_NAME, 1, 3), 'SAP',

1, 0)), 6) || ')'

  FROM

    TABLES

  WHERE

    TABLE_TYPE = 'ROW'

)

UNION ALL

( SELECT

    'Column store tables',

    LPAD(COUNT(*), 10) || '    (SAP schema: ' || LPAD(SUM(MAP(SUBSTR(SCHEMA_NAME, 1, 3), 'SAP',

1, 0)), 6) || ')'

  FROM

    TABLES

  WHERE

    TABLE_TYPE = 'COLUMN'

)

UNION ALL

( SELECT

    ' ',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    'MEMORY INFORMATION:',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

    ' ',

    ' '

  FROM

    DUMMY

)

UNION ALL

( SELECT

   'Memory',

   Value

   From

    M_SYSTEM_OVERVIEW

     WHERE

    SECTION = 'Memory' AND

    NAME = 'Memory'

   )

UNION ALL

( SELECT

   'Resident Memory used',

    LPAD(TO_DECIMAL(SUM(USED_PHYSICAL_MEMORY) / 1024 / 1024 / 1024), 5)

    FROM

    M_HOST_RESOURCE_UTILIZATION

)

UNION ALL

( SELECT

   'HANA instance memory (used)',

    LPAD(TO_DECIMAL(INSTANCE_TOTAL_MEMORY_USED_SIZE / 1024 / 1024 / 1024), 5)

    FROM

    M_HOST_RESOURCE_UTILIZATION

  ORDER BY

    HOST

)

A few months ago I wrote the blog Activating FIORI-Apps in S/4 HANA - not so hard after all!.

Now I'm moving its content to a document, as I intend to share new findings I have and think that updating an old blog over and over again is not the best thing to do.

I used to think that activating FIORI apps is a cumbersome task and I have to admit I had to give it a few attempts before I got some success.

But then I got four of them running in a short time, so I really got "in the flow". Now I think that it's not that hard, after all.

I'll share with you what I did / my general approach here:

[Please note: I'm working on an sandbox system, that is not even accessible from the "outside world" - if you're in a productive environment you probably have to pay a lot more attention to security-concerns.

(Like, thinking twice and checking back with others, before activation services in SICF; or fine-tuning the authorizations)]

Have your systems installed / up to date

We are running a backend with S/4 HANA 1511, SP1:

S4CORE          100       0001     SAPK-10001INS4CORE            S4CORE

Our frontend (gateway server) has SAP Fiori for SAP S/4HANA 1511 installed:

UIS4HOP1        100       0000     -           UI for S/4HANA On Premise

For configuring those systems, I use a document called "SAP Fiori Technical Foundation Configuration(EE0)" https://fioriapps-rds.dispatcher.hana.ondemand.com/docu/EE0_NWG20_BB_ConfigGuide_EN_XX.pdf

Other prerequisites:

• Have a equally named user in both the front- and the backend.
• For testing, I give them quit a lot of authorization in fron- and backend (like SAP_ALL).
• In the backend, let it have role SAP_SM_S_RFCACL .

After this is done, to activate an app what I do is this:

(if not mentioned otherwise, things are done on the front end = gateway server).

1. Find your App in the App-Libraray (https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/)

     I'll take "Manage Purchase Orders" (https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F0842')/S3OP) as an example.

2. Check that the needed front- and backend-components are installed.

3. Activate the UI5-application in SICF.

The path is allways: /default_host/sap/bc/ui5_ui5/sap/

The appslibrary will tell you the service name (MM_PO_CRES1)

-> just right-click and activate.

4. Activate OData services:

In /IWFND/MAIN_SERVICE, publish the OData servic(es) mentioned in the appslibrary (MM_PUR_PO_MAINTAIN).

Also make sure that it's activated in SICF as well:

Here the path is: /default_host/sap/opu/odata/sap/

5. Assign the role given in "PFCG role for Business Catalog" (SAP_BR_PURCHASER) to your user and start testing:

6. Log on to the Fiori-launchpad.

It's usually located at [server:port]/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html .

Tipp: use Chrome as your browser.

7. You now should see the Apps as provided by the PFCG-Role.

8. Find the one you wanted (Manage Purchase Orders) and klick on it.

9. It's quite possible that it will not work right away, but don't let that stop you:

The F12-Key is your friend!

-> switch to the Console.

Press F5 to reload the launchpad again.

Then click the App again.

-> Watch the error messages in the console!

There are usually 2 main error sources you can identify by those messages:

a)

A service is not running!

GET http://[hotsname]/sap/bc/ui5_ui5/sap/mm_purdoc_lsts1/~29C6FEC22735BB70BBE819198D78D~5/Component.js403 (Forbidden)

-> go to the SICF-Node given in the URL (here: /sap/bc/ui5_ui5/sap/mm_purdoc_lsts1) and activate it.

b)

An OData service is not available:

GET http://[hostname]/sap/opu/odata/sap/ME2STAR_OD_SRV/$metadata?sap-language=DE 403 (Forbidden)

-> go to /IWFND/MAINT_SERVICE and publish it!

(don't forget to to activate the respective SICF-Node as well!)

You probably have to repeat those steps (reload, Click, Look, activate something in b) a few times, but in the end you should have your running app:

Bonus-steps:

You already see the other apps (provided by the PFCG-Role) so why not make the usable, too!?

-> you can use the same "klick, look, activate"-cycle for it.

Conclusion:

As always you have to invest some time and get acquainted with the problem domain. As you gain experience, the solution hidden behind an error message will get more and more obvious to you.

F12 is key when trying to find out what's wrong!

To enable our customers to plan their journey to SAP S/4HANA in detail, we have created the “Simplification List for SAP S/4HANA, on-premise edition 1511.” This list provides detailed functional-level descriptions of the required changes to individual transactions and solution capabilities in SAP S/4HANA. It supports customers who are transitioning from SAP ERP 6.x or SAP Simple Finance, on-premise edition, to SAP S/4HANA, on-premise 1511 edition and includes guidance on the activities customers need to complete before, during, and after the conversion to SAP S/4HANA.

In addition to the Simplification List the Maintenance Planner, the conversion Pre-Checks and the Custom Code Migration Worklist are offered to give a tool-based support for the customer.

For more details regarding these tools see the following S/4HANA SCN Blog: http://scn.sap.com/docs/DOC-68976

Based on the experience gained from current projects, we expect that a typical customer system will be affected by on average 30 to 40 of the currently around 300 Simplification Items. Technical pre-checks, which assess the usage and configuration of a customer’s existing SAP Business Suite system, identify the relevant Simplification Items. Customers can run these pre-checks on their existing SAP Business Suite systems during the planning phase prior to the actual conversion to SAP S/4HANA. SAP plans to further improve the process of identifying Simplification Items by providing additional pre-checks and even more advanced tools that will reduce the list per system to a specific subset for that particular system.

The Simplification List, therefore, serves three purposes:

• Planning the actual system conversion from a traditional ERP solution to SAP S/4HANA
• Reducing efforts during the actual conversion by enabling individual Simplification Items to be dealt with in advance for those customers intending to migrate in a future project (if, for example, they are currently tied up in other projects)
• Implementing SAP S/4HANA-compliant strategic capabilities when rolling out new capabilities to avoid rework on SAP S/4HANA (relevant to, for example, customers who still need to finish major rollouts prior to converting to SAP S/4HANA)

With this S/4SCN Blog we want to start a series of blogs providing more information about dedicated simplification items. Simplification items where we assume that any customer project has to deal with. We are planning to provide for a list if dedicated simplification items per item a dedicated S/4HANA SCN blog with dedicated information. Based on the single S/4HANA SCN blogs feedback can be given and questions can be raised (which we try to answer as fast as possible). Follow the Link to access the dedicated S/4HANA SCN blogs per Simplification Item. Here you can find an attached Power Point with more information.

Can't wait ? Start your trial here

The trial is based on a software appliance for SAP S/4HANA, on-premise edition 1511 Feature Pack Stack (FPS) 01, and the corresponding SAP Best Practices. This blog is mainly focusing on the 30-day trial but the software appliance can also be used for longer engagement (both in a hosted environment or on-premise), see e.g. the read-more links in the appendix below.

Here’s the scorecard of the trial with the most important facts:

If you are already experienced with the previous SAP S/4HANA on-premise trial (1503 release, not available anymore as trial), you will easily be able to switch to the new trial release since the ‘mechanics’ are the same as before:

• Free SAP Cloud Appliance Library access for 30 days
• Built-in 30-day test & evaluation license for SAP S/4HANA (free of charge for the supported trial scenarios during that time)
• Amazon AWS fees (~ 4 USD per uptime hour) are charged to your AWS account
• Support via SAP CAL community in SCN
• Possibility to extend the 30-day trial phase by acquiring an SAP CAL subscription license (requires valid SAP S/4HANA license as well)

If you are new to trials in SAP Cloud Appliance Library, there’s a detailed ‘Quick Start Guide’ on the trial landing page to get started. Registration in AWS and SAP CAL takes a few minutes, start-up of your personal trial instance will take less than one hour.

The scope of the trial has been extended and now covers the below four ‘walkthrough’ scenarios that are explained in detail in an extensive demo script:

• Order-to-cash

• Plan-to-production

• Procure-to-pay

• Self-service-procurement

But of course you’re free to explore and adapt the system as needed (and covered by the terms&conditions of the trial) since you have full administrative rights and even access to the Linux operating system.

Technically, the trial consists of three Amazon appliances that are bundled into one solution instance:

1. SAP S/4HANA (the core ABAP backend)

2. SAP NW JAVA with Adobe Document Services (for forms, output management, and usage in Credit Management)

3. MS Windows remote desktop for easy access of the trial system

One more thing: Deploying the trial appliance on your own hardware

If you are interested in receiving the trial appliance for installation on your own on-premise hardware, this can be accomplished by ordering two Blu-Ray discs from SAP (the MS Windows remote desktop is not included in this shipment).

The shipment is free of charge, however, corresponding SAP S/4HANA licenses need to be in place depending on recipient and use case e.g. for partners a T&D license or for customers a SAP S/4HANA / SAP HANA license including SAP Cash Management and Integrated Business Planning for Finance (via BPC for SAP NetWeaver).

For SAP customers, an engagement with either SAP Consulting or an enabled SAP partner is required to receive and deploy the solution on customer premises. Ordering of the discs by a partner and deploying it on customer-site afterwards is not allowed.

The following SAP notes contain more information on the ordering process:

• Ordering process for SAP partners (2041140) - also containing information how SAP partners can enable themselves for Blu-Ray deployment.
• Ordering process for SAP customers (2202234)

And lastly to summarize:
This presentation gives an overview of the software appliance for SAP S/4HANA 1511 FPS01, covering the used SAP Best Practices, the trial and the Blu-Ray shipment aspects.

As usual, there is also a central SAP Note for details, known issues, etc. for the appliance:

2032086 SAP S/4HANA On Premise Edition 1511 FPS01 Fully Activated Appliance - Central Note.

Best,

Joerg

Appendix: Link collection for further information

Software appliance in general:

• Overview presentation for the appliance
• Central SAP note for the appliance
• SAP Best Practices for SAP S/4HANA 1511, on premise edition

30-day trial:

• On-premise trial landing page
• Quick Start Guide for the on-premise trial
• Demo Guide for Trial Business Scenarios

Blu-Ray shipment.

• Ordering process for SAP partners (2041140)
• Ordering process for SAP customers (2202234)

SAP CAL information:

• SAP CAL Console
• SCN Community for SAP CAL (also for support for CAL issues)
• How to acquire an SAP CAL subscription (and other CAL business questions)
• For SAP employees only: How to get an SAP internal CAL account and attach it to your cost center

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 about SAP S/4HANA.

For comments regarding the cookbook itself, please use the accompanying blog.

Table of Contents

1. What is SAP S/4HANA

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

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

• This first on-premise version of SAP S/4HANA was released in March 2015. Since this version currently has the highest implementation figures, there is a separate page on it in the cookbook.

3. Implementing SAP S/4HANA with SAP Activate (this page)

This page gives an overview of the accelerators consolidated in SAP Activate that  help SAP partners and customers throughout the different phases of SAP S/4HANA implementation projects:

• SAP Activate: Overview
• End-to-End Customer Experience
• Discover
• Prepare
• Explore
• Realize

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

SAP Activate: Overview

SAP Activate project phases:

Discover

Prepare

Explore

Realize

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 about SAP S/4HANA.

For comments regarding the cookbook itself, please use the accompanying blog.

Table of Contents

1. What is SAP S/4HANA

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

2. SAP Simple Finance, On-Premise 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. Implementing SAP S/4HANA with SAP Activate

• This page gives an overview of the accelerators consolidated in SAP Activate that  help SAP partners and customers throughout the different phases of SAP S/4HANA implementation projects
  

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

SAP Simple Finance, On-Premise 1503: Overview

SAP Simple Finance, On-Premise 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.

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 about SAP S/4HANA.

For comments regarding the cookbook itself, please use the accompanying blog.

Table of Contents

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

• Overview
• What is available now ?
• Further capabilities in context of SAP S/4HANA
• Transition Options
• Extensibility & Adaptation
• Best Practices & Enablement by SAP
  

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

• This first on-premise version of SAP S/4HANA was released in March 2015. Since this version currently has the highest implementation figures, there is a separate page on it in the cookbook.

3. Implementing SAP S/4HANA with SAP Activate

• This page gives an overview of the accelerators consolidated in SAP Activate that  help SAP partners and customers throughout the different phases of SAP S/4HANA implementation projects

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 ?

Further capabilities in context of SAP S/4HANA

SAP S/4HANA: Transition Options

SAP S/4HANA: Extensibility & Custom Code Adaptation

Best Practices & Enablement by SAP

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

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.
• Ensure that the latest version of the Software Update Manager is used:

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 available at:

• support.sap.com/sltoolset (LINK)
  • Section "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, and regarding SUM for System Conversion

• Database Migration Option (DMO) of SUM - Introduction
• System Conversion to SAP S/4HANA: SUM is the tool

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 (FPS1): 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 and the following SCN blog: SAP S/4HANA Custom Code Migration Worklist.

Related information – at a glance