In good tradition we will extend the FAQ series for SAP S/4HANA, thanks again to many feedback received. Let´s dive right into the Q2/2016 update.
What is the right reporting option in SAP S/4HANA: SAP BW powered by HANA, or SAP S/4HANA Core Data Services?
Here there is not right or wrong. SAP BW powered by HANA will continue to represent the preferred solution for strategic enterprise data warehousing to help customers consolidate data from different sources (including SAP and non-SAP data sources) and get a consistent view across the enterprise.
SAP S/4HANA Core Data Services built in SAP S/4HANA, delivers real-time operational reporting capabilities covering all typical analytics use-cases in the context of the suite. You can do all your operational reporting and process analytics covering all typical business suite analytics use-cases with the CDS views. This is the new “HR IS”, for embedded reporting.
SAP BW powered by HANA will continue to act as SAP’s central enterprise data warehouse solution. SAPS/4 HANA and SAP BW on HANA complement each other. This document will give you more details on this topic.
What is the authorization concept in SAP S/4HANA? It is the same as ECC 6.0?
SAP S/4HANA, on-premise edition 1511 generally relies on the user management and authentication mechanisms provided with the SAP NetWeaver platform, in particular the SAP NetWeaver ABAP Application Server and the SAP HANA Platform. Therefore, the security recommendations and guidelines for user administration and authentication as described in the SAP NetWeaver Application Server ABAP Security Guide and SAP HANA Platform also apply to SAP S/4HANA.
In addition to these guidelines, we include information about user administration and authentication that specifically applies to SAP S/4HANA in the following topics:
- User Management This topic lists the tools to use for user management, the types of users required, and the standard users that are delivered with SAP S/4HANA.
- User Data Synchronization SAP S/4HANAcan share user data with other components. This topic describes how the user data is synchronized with these other sources.
- Integration into Single Sign-On Environments
See the Security Guide for SAP S/4HANA, on-premise edition 1511
Concerning the migration from SAP ECC to S/4HANA, what are the options and services offered by SAP for the migrations?
To move from an SAP ECC System to SAP S/4HANA, we have to consider different implementation scenarios supporting the move to SAP S/4HANA
- Scenario 1 – System Conversion: Existing SAP Business Suite Customer who wants to move to SAP S/4HANA
- Scenario 2 – Landscape Transformation: Existing SAP Business Suite Customer who want to optimize their system landscape and move to SAP S/4HANA
- Scenario 3 – New Implementation: New SAP customer who want to move from legacy systems to SAP:
- See more details in the cookbook“The road to SAP S/4HANA”
Considering the Data Migration, SAP offers with SAP Activate for SAP S/4HANA a innovation adoption framework that expedites SAP S/4HANA implementations throughout the customer lifecycle. It offers ready-to-run digitized business and technology processes, guided configuration, and next-generation methodology.
The data migration content from SAP Activate to SAP S/4HANA, on-premise edition allows the customer to extract and analyze selected data from virtually any source system. See also for more details the SAP service market place for SAP Best-Practice for data-Migration
Scenario 1: Procedure of System Conversion
Is there to possibility to have Custom Code also in SAP S/4HANA Cloud?
We want to answer this question in two ways. On the one hand side, this question might refer to a customer who runs SAP ECC and considers moving into SAP S/4HANA Cloud.
On the other hand side, the question is of pure technical nature.
There are two transformation scenarios for moving into SAP S/4HANA Cloud which are “New Implementation” and “Landscape Transformation. Both scenarios imply a new system installation in SAP Data Centers. Customers can initially migrate business data into the system and further on are able to integrate their SAP S/4HANA Cloud instance with other SAP Cloud solutions and with on-premise solutions. Having said this, the consequence is that there is no option to move any ABAP-code from any SAP ECC system to SAP S/4HANA Cloud.
Instead the way forward has much to do with the technical options and concepts of extending SAP S/4HANA Cloud, which is now referred to in the second part of the answer.
SAP offers two flavors of extensibility in the cloud, which are complementary and can be combined:
- In-app extensibility is the capability of extending the existing S/4 HANA applications. The target group is the business expert in the company or from a consulting partner (aka key user). The tool set consists of web-based apps for end-to-end creation of extensions, for example custom fields, custom logic, etc.
More information can be found here: http://scn.sap.com/community/s4hana/blog/2015/07/15/s4hana-extensibility-the-new-white-paper
Is there any changes in the Simplification list coming with the feature pack stacks FSP01, FSP02 … ?
SAP has published a simplification list for SAP S/4HANA on premise 1511. The Simplification List consists of simplification items with the focus on what has to be considered by customers in an implementation / system conversion project from SAP ERP 6.0 to SAP S/4HANA, on-premise edition.
New innovations that also can result in changes of the Simplification list are shipped on a yearly basis for each mayor release of SAP S/4HANA. The next major release is planned for end of 2016. For more information about the release strategy check this blog that will give you more information.
Note that the simplification list is not a replacement for the product documentation but a complement. The document – Feature Scope Description – is accessible here. SAP will provide a new version for all Feature Pack Stack.
Keep the feedback and your questions coming, we will prioritize accordingly and update our FAQ for you. Keep the feedback coming.
Also check frequently sap.com/s4hana.
Stay tuned for the next update in Q3 and let´s stay connected @SDenecken