Describing the Scope of DFPS with SAP S/4HANA

Objective

After completing this lesson, you will be able to explain the main differences between SAP ECC and SAP S4HANA as the new digital core

Main Differences Between SAP ECC and SAP S/4HANA

In the former DFPS solution, the force generation process started with creating the detailed organizational structure. However, in real life creating the organizational structure in the system comes after a more high-level design and analysis phase. During this phase, the planners start with the strategic intent and directives of the political and Army command, which are unstructured in nature, analyze them, break them down into concrete and formulated requirements. It is only then that they define the required structure and the resources.

In D&S, SAP enhanced the solution to support this planning phase.

SAP S/4HANA Enterprise Management is SAP’s next-generation digital core:

  • Innovative in-memory database
  • New architecture and new data models
  • Renewed applications
  • New UI technology (SAP Fiori)
  • Cloud and on-premise deployment models
  • Natively integrated

This figure highlights the SAP S/4HANA Architecture differences from the classical SAP Business Suite architecture, as well as the development approach of our new Digital Core.

SAP S/4HANA is a new product line. The classical Suite and SAP ERP are still available. The current planned end of mainstream maintenance for the Suite is 2027. Look at SAP Note 2881788 for more details.

Support Package Stack for SAP S/4HANA 2022*

After the general availability of SAP S/4HANA 2022, Feature Package Stacks (FPS) and Support Package Stacks (SPS) contain stabilizations bundled with corrections and legal changes. Customers benefit from this functionality as part of their maintenance fee. The first SPS of a new release can contain selected features and is labeled Feature Package Stack (FPS) accordingly. Support Package Stacks are compiled periodically and made available in the SAP Service Marketplace.

SAP S/4HANA 2023*

New release incl. new technology stack and following new release strategy.

Important Links

Note

* This is the current state of planning and can be changed by SAP at any time without notice.
  1. SAP S/4HANA 2022 with RTC on October 12th, 2022, stays with the current Release Strategy 1+4 (1 year innovation line, 4 years standard maintenance line)
  2. Starting with SAP S/4HANA 2023, the innovation line will be extended to 2 years with an additional maintenance line of 5 years (2+5)
  3. For the 3 releases 1709, 1809, 1909 the extended Maintenance will end in 2025
  4. During the innovations line, SAP will continue to deliver innovations in 3 Feature Package Stacks (FPS) in 2 years
  5. Release Naming convention: [YYYY] (for example., 2022) for SAP S/4HANA and SAP S/4HANA Cloud, private edition, [YYMM] (for example., 2208) for SAP S/4HANA Cloud, public edition
  6. SAP will continue to support SAP S/4HANA until 2040

    → all customers can adopt SAP S/4HANA Innovations at their own pace (no customer has a disadvantage compared to the previous [1+4] strategy)

SAP S/4HANA Evolution of Architecture

Acquisitions / new:

  • Ariba: 2012
  • SFSF: 2012
  • SCP: 2012
  • Hybris: 2013
  • Concur: 2014
  • Fieldglass: 2014
  • IBP: 07/2014
  • BW/4HANA: 2016
  • Leonardo: 2017– 2019
  • AIN: 2017
  • Qualtrics: 2019

Rebrandings

  • Hybris → C/4HANA: 2018
  • C/4HANA → Customer Experience: 2020
  • (ML, iRPA, Conversational AI, IoT, Situations)

This is the official product map of the SAP S/4HANA Suite, which is made up of different sections.

All Solution Areas reflect the official SAP GTM terminology, which is further documented in the SAP Solution Explorer, but also in the SAP Feature Scope description.

  • In the dark grey area, you can see all Solution Areas, included in the Shipment Scope and in the SAP S/4HANA Enterprise Management license.
  • In the light grey area, you will find Solution Areas included in the shipment (or available as Add-Ons), which will require separate licenses.
  • In the white area, you will see products or solutions outside the shipment scope that can be integrated but require individual projects. Many of them can be seamlessly integrated with available interfaces (API's) or Best Practices so that a relevant integration scope is supported "out of the box".

Log in to track your progress & complete quizzes