Articles

Everything you need to know about SAP S/4HANA Assessment using KTern

Kirthan Ramesh - 12 Minute read

24-Mar-2020


Executive Summary

SAP presented SAP S/4HANA to the world in 2015. In an interview at the 2018 SAP TechEd conference, Rudolf Hois, SAP VP and chief product owner for SAP S/4HANA stated that 50- 60% of the S/4HANA installed base have already chosen system conversion as their route. In fact, to accommodate this route’s growing popularity, the versions of SAP S/4HANA beyond 1809 simplify and reduce the downtime for system conversion. SAP ECC to SAP S/4HANA System Conversion, also called a ”brownfield” approach, enables migration to SAP S/4HANA without re-implementation and without disruption to existing business processes. At the same time, it enables the re-evaluation of customization and existing process flow.

However, migrating to S/4HANA is not as simple as it sounds. It is unlike any other SAP ECC upgrade. It requires a deep understanding of the business structures and technical impacts as well as updated skillsets and business strategies. Therefore, as the first step, you must assess and evaluate the effort required and the business impact before moving to S/4HANA.

What is SAP S/4HANA assessment?

One of the primary reasons for the complexity of any SAP S/4HANA transition project is the vast legacy data and the customizations that you must migrate. An SAP S/4HANA assessment enables you to understand the implications of the transition from an existing SAP ERP system to SAP S/4HANA. The check helps to identify the necessary preparations and pre-projects in the current system landscape, long before an SAP S/4HANA system conversion project starts.

There are several factors which you must consider before deciding to move to S/4HANA. You should have the answers for some relevant questions like:

  • How disruptive will the transition be for your organization?
  • What is the amount of effort required to transition to S/4HANA?
  • How many custom codes will be impacted?
  • What is the impact on the existing landscape?
  • How much testing effort and business involvement is required?
  • How to start preparing for your journey to S/4HANA?

But, how do you get the answers to the above questions? You get the answer by completing a comprehensive SAP S/4HANA assessment/study of your SAP ECC system, preferably with KTern.

SAP S/4HANA Assessment using KTern

KTern is a disruptive all-in-one product built on the SAP Activate framework, the “S/4HANAPEDIA” automation rule engine, a next-gen collaboration platform, and future-ready machine learning algorithms. All these features work in coalition to help ECC customers before their transition, during their transition, and after the transition.

Before the transition, KTern provides an auto-generated blueprint for your ECC to S/4HANA system conversion by completing a comprehensive automated assessment. This blueprint will help you define the right plan, the right effort estimate, the right system sizing, the right execution, the right project management, and the right quality for your ECC to S/4HANA transition - Ensuring up to 53% faster, 37% cheaper, and 99.9% safer S/4HANA migrations.

You can also download the complete E-Book of SAP S/4HANA Assessments using KTern here.

KTern’s SAP S/4HANA Assessment provides the following:

  1. Simplification Item Check
  2. Enterprise Structure Mining – Sales (ESM)
  3. Enterprise Structure Mining – Purchase Documents
  4. ESM – Orders
  5. ESM – Billing
  6. Add-on analytics
  7. Business Function Analytics
  8. Custom Object Analytics
  9. Custom Code Impact Analysis
  10. Test Case Recommendations
  11. Fiori App Recommendations
  12. BW Extractor Check
  13. Transport Request Analytics
  14. Archiving Recommendations
  15. User License Recommendations
  16. Training Scenario Recommendations
  17. Roadmap Guide
  18. Effort Estimation

In this article, we’ll explain in detail about each of these features and how it provides a comprehensive analysis so that you can move to S/4HANA without any hiccups.

INTERESTING READ

Challenges in System conversion from SAP ECC to SAP S/4HANA

Read more


Simplification Item Check  

Simplification list items (in short, Simplification Items) illustrates the business adaptation requirements and effects to custom developments for each function described. Typically, each Simplification Item consists of an SAP OSS Note. The OSS Note has the description and details on how to run that Simplification Item. You have to install the OSS Note into the system and run the Simplification Items Check. However, with KTern, you can automate the process of Simplification Item Check and it provides a comprehensive overview of all the relevant simplifications for SAP S/4HANA – that is, all mandatory solution adjustments in a system conversion project.

Features of Simplification Item Check

KTern's Simplification Item check calculates the total number of Simplification Items in a system. It then classifies them into impacted and non-impacted Simplification Items. KTern also provides the status of each Simplification Item with SAP Note references. It also specifies why a particular Simplification Item is relevant or not relevant to your business.




Further, the impacted simplification items are classified based on the status as follows:

  1. Change of existing functionality: Simplification items in this category refer to functions that are generally available in some form in SAP S/4HANA but have been adapted in such a way that might affect existing processes and custom programs.
  2. Functionality unavailable (equivalent exists): Simplification items in this category refer to functions that are not available in SAP S/4HANA. However, the equivalent functionality is available in SAP S/4HANA.
  3. Functionality unavailable (no equivalent):  Simplification items in this category refer to functions that are not available in SAP S/4HANA. And, there is no equivalent functionality available. If you think that such impacted items are critical to your business, then it makes sense to wait until SAP releases that functionality and then make the move to S/4HANA.
  4. Non-Strategic Functions (equivalent exists):  SAP has identified many of the existing core ECC modules/sub-modules/functionalities as "non-strategic" in S/4HANA. If current ECC-users or new businesses require these functionalities which are part of a "non-strategic module/functions" then they have to adopt the "strategic solution" as per S/4HANA roadmap. These "strategic-solutions" may or may not have its equivalent in S/4HANA. Generally, the non-strategic functions with equivalents can be classified into: 1.New S/4HANA solutions part of extended S/4HANA product or 2.In some cases, existing SAP products which are being enhanced/built for S/4HANA.
  5. Non-Strategic Functions (no equivalent):  The Simplification Items where these "strategic-solutions" have no equivalent in S/4HANA are classified into this category

You can read more on KTern’s simplification item check here.

Enterprise Structure Mining - Sales  

In most SAP S/4HANA assessments, as the first step, organizations aim to find out the enterprise structure in SAP and drill down the hierarchy of each functional module. They find out answers to questions like - What is the type of the system? What is the orientation of the SAP system? How and who uses the system? What is the most effectively used process? How many company codes are there in the system? What are the most effectively used sales organizations? And much more.

Finding out answers to these questions is a very manual task. Many functional consultants are deployed for this purpose. The functional consultants then go through each T-Code, Table and Report to map the hierarchy of the enterprise structure in SAP and find out the complexity of the system. Sounds tiring, right? But this step is mandatory and cannot be skipped. Only after this step, you can proceed with the next step in the system conversion process.

With KTern, you can automate and find out the entire enterprise structure in SAP with just the click of a button. You can find the answers to the above crucial questions easily.

Features

KTern’s Enterprise Structure Mining – Sales documents feature drills down the various organizational units. It drills down from company codes, sales organizations, distribution channels, plants and all the way up to the sales documents generated. In this way, KTern provides a clear hierarchy and evidently maps the organizational structure. The hierarchy of a sales organization is as follows:
Company Code -> Sales Organization -> Distribution Channel -> Division -> Plant -> Number of Sales Documents Generated




The functional consultants manually doing this task will definitely not be able to provide such clarity and accuracy in mapping the org structure. They have to go through each table, record and T-code to get this information. An even then, they will not be able to get the total picture. And, let’s not talk about the time required to complete the task. It may take several weeks or even months to complete it. KTern automates the task and provides the results in a span of a few minutes.

You can read more on KTern’s Enterprise Structure Mining – Sales here.

Enterprise Structure Mining – Purchase  

KTern’s Enterprise Structure Mining – Purchase Documents feature drills down the various organizational units. It drills down from company codes, purchasing organizations, purchasing groups, plant, storage location and all the way up to the number of purchase documents created. In this way, KTern provides a clear hierarchy and evidently maps the organizational structure. The hierarchy of a purchase organization is as follows:
Company Code -> Purchasing Organization -> Purchasing Groups -> Plant -> Storage Location -> No. of Purchase Documents Created


Another important feature of KTern’s Enterprise Structure Mining is that you can sort and search the company codes, purchasing organizations, purchasing groups, plant, storage location, and the number of purchase documents. This enables you to determine the most active company codes, purchasing organizations and so on. For example, if only two purchase documents are generated for the past 5 years in one of the plants, then it can be inferred that that particular plant is not active. After taking a call with the business stakeholders, you need not move that particular plant to S/4HANA.

You can gain such insights only when you have such detailed hierarchy and organizational mapping as provided by KTern. Such observations from KTern helps the MM functional consultants, business stakeholders from both the System Integrator side and the customer side, and the Solution Architects to have a clear picture of the landscape and take better data-driven decisions.

You can read more on KTern’s Enterprise Structure Mining – Purchase here.

Enterprise Structure Mining – Orders  

An SAP system contains several types of orders associated with various modules. They would have been generated over the past several years of using SAP. KTern’s Enterprise Structure Mining feature – Orders drills down the various company codes present in an SAP Landscape. It drills down from company codes, plants, controlling area and the types & number of orders generated. In this way, KTern provides a clear hierarchy and evidently maps the orders generated with its functional module. The hierarchy is as follows:
Company Code -> Plant -> Controlling Area -> Number and types of orders


KTern also provides the option of downloading this report. In addition, you can also post it in the forum, assign stakeholders and collaborate. You can upload the files in KTern and subsequently use it any other stage of the system conversion process. Thus, KTern provides a platform to join forces and work together in determining the relevant enterprise structures in SAP and plan the path to S/4HANA.

You can read more on KTern’s Enterprise Structure Mining – Orders here.

Enterprise Structure Mining – Billing  

Enterprise Structure Mining - Billing feature drills down the various company codes present in an SAP Landscape. It drills down the company codes, currency, the user who created the document and the type & number of billing documents generated. In this way, KTern provides a clear hierarchy and evidently maps the orders generated with its functional module. The hierarchy is as follows:
Company Code -> Currency -> Created by user -> Type and number of billing documents
KTern can automate this task and provide the hierarchy in just a span of a few minutes.



KTern also provides the option of downloading this report. In addition, you can also post it in the forum, assign stakeholders and collaborate. You can upload the files in KTern and subsequently use it any other stage of the system conversion process. Thus, KTern provides a platform to join forces and work together in determining the relevant enterprise structures in SAP and plan the path to S/4HANA.

You can read more on KTern’s Enterprise Structure Mining – Billing here.

Add-on Analytics  

Your transition from ECC to S/4HANA can stop in its tracks if there is an incompatible add-on. All add-ons must be certified in order to run on S/4HANA. For SAP’s own add-ons or the ones sold through SAP’s pricelist, you can directly request the status of add-ons and additional packages from SAP themselves. However, SAP is not responsible for the independent third-party add-ons.

Add-on compatibility check is one of the most important and decisive features in KTern’s Impact Analysis module. The main objective of this feature is to determine the add-ons incompatible with S/4HANA, and how it impacts the transition process.

Features of Add-on analytics

KTern automates the process of add-on compatibility check during the SAP S/4HANA assessment and does not require the installation of any SAP Notes in the system. After connecting the system, KTern runs the check and automatically classifies the installed add-ons into compatible and incompatible add-ons.

KTern also goes a step further and classifies the add-ons into three broad categories. They are:

  • Software components
  • Installed products
  • Correction packages

If one of your critical add-ons is not compatible with S/4HANA, then your entire business could be at risk. In such cases, you will have to wait for SAP’s roadmap to make that particular add-on compatible with S/4HANA. Only then, you can plan your transition from ECC to S/4HANA.




KTern also provides the option of downloading this report. In addition, you can also post it in the forum, assign stakeholders and collaborate. You can upload the files in KTern and subsequently use it any other stage of the system conversion process. Thus, KTern provides a platform to join forces and work together in determining the relevant enterprise structures in SAP and plan the path to S/4HANA.

You can read more on KTern’s Add-on analytics here.

Business Function Analytics  

KTern’s Business Function Analytics feature analyzes all the business functions installed in an ECC system in the Discover phase itself. It then classifies them into active and inactive business functions. The main objective of this feature is to analyze the impact of migrating these active business functions to S/4HANA. If any critical active business function is not compatible with S/4HANA, then you cannot migrate to S/4HANA.

Features of Business Function Analytics

KTern automates the process of analyzing business functions. After connecting the system, KTern runs the business functions analytics check and automatically classifies the installed business functions into active and inactive business functions. KTern also classifies the business functions into the following types:

  • Enterprise Extensions: These are the type of business functions which activate industry-independent and industry-specific applications and business processes.
  • Enterprise Business Functions: They can activate special features in SAP S/4HANA. They contain both industry-specific and industry-independent enterprise business functions.
  • Industry Business Functions: They contain functions specific to a particular industry and are part of the industry business function sets.
  • If one of your critical add-ons is not compatible with S/4HANA, then your entire business could be at risk. In such cases, you will have to wait for SAP’s roadmap to make that particular add-on compatible with S/4HANA. Only then, you can plan your transition from ECC to S/4HANA.




    You can read more on KTern’s Business Function Analytics here..

    Business Function Analytics  

    KTern’s Business Function Analytics feature analyzes all the business functions installed in an ECC system in the Discover phase itself. It then classifies them into active and inactive business functions. The main objective of this feature is to analyze the impact of migrating these active business functions to S/4HANA. If any critical active business function is not compatible with S/4HANA, then you cannot migrate to S/4HANA.

    Features of Business Function Analytics

    KTern automates the process of analyzing business functions. After connecting the system, KTern runs the business functions analytics check and automatically classifies the installed business functions into active and inactive business functions. KTern also classifies the business functions into the following types:

  • Enterprise Extensions: These are the type of business functions which activate industry-independent and industry-specific applications and business processes.
  • Enterprise Business Functions: They can activate special features in SAP S/4HANA. They contain both industry-specific and industry-independent enterprise business functions.
  • Industry Business Functions: They contain functions specific to a particular industry and are part of the industry business function sets.
  • If one of your critical add-ons is not compatible with S/4HANA, then your entire business could be at risk. In such cases, you will have to wait for SAP’s roadmap to make that particular add-on compatible with S/4HANA. Only then, you can plan your transition from ECC to S/4HANA.




    You can read more on KTern’s Business Function Analytics here..

    Custom Object Analytics  

    You can create several custom transactions, tables, reports and objects in your SAP system. However, before moving to S/4HANA, it is necessary to analyze all the custom objects in order to determine the most used objects and to retire some custom objects. Without a single unified view of all the custom objects, it is very difficult to figure this out. However, KTern is here to save the day.

    Features of Custom Object Analytics

    KTern automates the process of SAP custom object analytics. As a result, this section gives you an analytical view of the custom objects present in the system. After connecting an ECC system, KTern runs the custom object analytics check and determines the custom objects present in a system. The custom objects are then grouped based on the custom packages, the stakeholder who created it, the type of custom object and the frequency of usage.




    In addition, you can also sort and search the custom objects according to the object types, custom packages, object owner, and the frequency of custom object usage. Hence, this enables you to determine the most used and least used custom objects.

    With this feature of KTern, you can gain analytical insights on the following:

    • Custom packages with respect to the number of objects
    • Frequently used custom transactions/reports
    • Top x custom object stakeholders
    • Top x custom object types
    • Custom objects summary, and much more

    Typically, one of the first questions a stakeholder asks to determine the weight and complexity of the ECC system is: What is the total number of custom objects in the system? KTern provides the answer to the above question and much more additional insights in just a click of the button. You can also use this feature to indirectly determine the timeline and effort of an SAP S/4HANA system conversion project.

    Custom Code Impact Analysis  

    Using the custom code impact analysis feature of KTern in SAP S/4HANA assessment, you can assess and analyze the syntactical change impact of all the custom Z tables, Z programs, and Z objects. It is a pre-requisite to check the impact on the standard SAP code and the custom code before moving to S/4HANA. Without completing this step, you cannot proceed further in the system conversion process.

    Features of Custom Code Impact Analysis

    KTern automates the process of SAP custom code impact analysis. As a result, this section gives you an analytical view of the custom code present in an SAP ECC system. After connecting an ECC system, KTern runs the custom code impact analytics check and analyzes the custom programs and objects present in a system.

    The key activities that can be performed using KTern with respect to the custom code are:

    1. Identification of affected custom objects
    2. Scope definition of custom code migration
    3. Define which custom code needs to be taken to S/4HANA
    4. Define usage frequency
    5. Custom code analysis parameters
    6. Syntactically incompatible change of existing functionality
    7. Functionality not available but functional equivalent available
    8. Functionality not available
    9. Change of existing functionality with a performance impact

    You can also upload the custom objects by exporting from SCMON

    The Custom Code Dashboard also provides a chart depicting a usage vs impact score of the custom objects. This helps in prioritizing the high impact code with a high frequency of usage. You can eliminate the low usage custom programs and objects after taking a call with the business stakeholders. 




    Based on the information provided by KTern, you can plan your SAP S/4HANA system conversion with confidence.

    KTern’s AI-powered rule engine automatically calculates the impact score of a custom program based on its analysis parameters and the number of impact cases. For example, if the custom program has many impact cases and its equivalent functionality is not available in S/4HANA, then it is given a high impact score.

    KTern also provides the roadmap and effort for the S/4HANA system conversion based on the results from the custom code impact analysis.

    Test Case Recommendations  

    KTern recommends the test scenarios and test cases which can be tested during the Realize phase. And the best part is, all these recommendations are available after the SAP S/4HANA assessment itself. Hence, it can be used to calculate the effort and timeline for a S/4HANA conversion.

    Features

    Test Suite Catalog

    KTern automates most of the testing process in SAP S/4HANA conversion. As a result, KTern generates the recommendations for test cases and calculates the effort for various scenarios. KTern enables test scripts to be loaded by connecting KTern with an ECC system and running “Check Test Case Recommendations”. The Test Suite Catalog contains the results in a hierarchical manner as Plan, Scenario, and Test case.




    Test Suite Wizard

    KTern provides the basic information on each test case in the test case wizard. It consists of the following basic information:

    1. The test plan and scenario to which the test case belongs
    2. The related functional module of the test case
    3. The Business Process of the test case
    4. Description of the test case
    5. Priority and test type
    6. The stakeholders assigned to each test case
    7. Files and Reference Notes
    8. Discussion Forum

    Test Suite Dashboard
    VVV Scoring

    The VVV Scoring Dashboard covers the Volume, Value, and Velocity Analysis of the business per transaction usage and helps decide the critical business processes which must be tested. KTern analyzes each transaction for its value, volume (frequency of usage) and velocity and assigns a score between 1 and 50 with 1 being the lowest and 50 being the highest. This can be used to determine the critical business cases and assign priority for each test case.




    Fiori App Recommendations  

    KTern’s Fiori App Recommendations feature automatically analyses the connected system and recommends the necessary Fiori applications. KTern also determines the relevancy score of each recommended Fiori app along with its respective module and transaction. In addition, KTern also provides the list of stakeholders and the impacted roles for each Fiori App. The Solution Architects and the Project Managers can use this feature to prioritize the implementation of Fiori Apps.

    Features

    KTern automatically analyses the connected ECC system and recommends a list of SAP Fiori Apps which can be implemented. As a result, this section gives you an analytical view of the Fiori Apps as per their functional modules after analyzing the various transactions.

    In addition, KTern also provides the associated stakeholders of each Fiori App along with their relevancy score and impacted roles. For each recommended Fiori App, KTern provides the following information in an easy-to-consume tabular format:

    1. Module to which the SAP Fiori App belongs
    2. Analyzed transaction
    3. Fiori App type
    4. Relevancy Score
    5. Stakeholders
    6. Line of Business
    7. Impacted Roles
    8. Reference SAP Note
    9. Reference link




    There are over 1000 Fiori applications today. Implementing all the thousand Fiori apps does not make sense. Hence, you will have to decide which Fiori apps are relevant to your business. With KTern’s Fiori App recommendations, you can easily get answers to the below questions and determine the most important Fiori applications and implement them first.

    • The business process and roles which will be improved and to which functional module they belong
    • The applications that should be available for immediate use
    • The business users who will access those apps
    • In which use cases will the business users use those apps
    • And, on which devices will they use them

    Based on answers to the above questions, the Solution Architects and Functional Consultants can activate the required Fiori Apps during the system conversion.

    BW Extractor Check  

    With the SAP BW Extractor check feature, KTern automatically identifies and analyses all the data sources. It also classifies them based on the impact while moving to SAP S/4HANA. It is a pre-requisite to check the compatibility and impact of the SAP BW Extractors before moving to S/4HANA. Without completing this step, you cannot proceed further in the system conversion process.

    Features

    KTern finds out the total number of BW data sources in a system and the number of impacted and non-impacted data sources in a system. As a result, this section gives you an analytical view of the BW data sources present in the connected system.

    It then classifies the data sources into Whitelisted and Not Whitelisted data sources. Whitelisted data sources are SAP-Authorized data sources. The data from these authorized data sources are migrated safely to S/4HANA because the data structures in these data sources abide by the standard best practices. Not Whitelisted data sources are not authorized by SAP and it may cause some trouble during the system conversion process.




    This feature is essentially used by the SAP Analytics, BI/BW consultants. They use it to determine the amount of effort required from their end to convert to S/4HANA. For example, if a data source is not working or not whitelisted in S/4HANA, then they have to create a custom data source, migrate all the data to this new data source and then integrate it to the new system. Same is the case for non-relevant data sources. Some data sources may be deprecated in S/4HANA, but the data they contain might be crucial. In such cases also, an analytics consultant will have to a custom data source.

    Also, if you are planning a parallel BW4HANA implementation, then the data from the SAP S/4HANA assessment becomes crucial.

    Transport Request Analytics  

    KTern’s TR Analytics feature automatically identifies and analyses all the transport requests in a system. KTern automatically finds out the total number of Transport Requests in a system in (n) and (n-1) years. It also gives an analysis of the stakeholders who create these transport requests. As a result, this section gives you an analytical view of the Transport Requests present in the connected system.

    There are three types of Transport Requests. They are:   

    1. Workbench Request: Workbench requests are cross-client. It essentially means that the changes done in one client are automatically reflected in all other clients. 
    2.   
    3. Customizing Request: Customizing requests are client specific. The changes will not be reflected in other clients. 
    4.   
    5. Transport of Copies: Transport of copies allows you to transport objects to any specified SAP System. It allows you to move the original location of objects to a target system. 




    KTern also categorizes the Transport Requests into seven categories: 

    1. Open Transport Requests
    2. Top 100 Large TR Types
    3. Transport Requests over the years 
    4. Top TR Stakeholders 
    5. Number of Transport Requests per month 
    6. Top 10 large Transport Requests till date 
    7. Top 5 stakeholders of large TR 

    Archiving Recommendations  

    With the Archiving Recommendations feature, KTern automatically analyses the system and identifies the documents, tables and custom programs which can be archived. You can then archive these data to any other third-party storage database.

    Features

    SAP Data Archiving Process essentially involves three major steps:

    1. Creating archive files
    2. Running delete programs
    3. Storing the archive file

    KTern provides a detailed report on archiving recommendations. The results are as follows: 

    1. Documents archiving potential
    2. Tables archiving potential
    3. Custom programs archiving potential




    User License Recommendations  

    With the Archiving Recommendations feature, KTern automatically analyses the system and identifies the documents, tables and custom programs which can be archived. You can then archive these data to any other third-party storage databaseIn the case of S/4HANA system conversion, you must analyse the existing SAP ERP users and their license types. KTern automates this process. It finds out the total number of SAP ERP users and also classifies them into active and inactive users based on their activity. As a result, this section gives you an analytical view of all the users present in the system and helps you make the right decision with respect license purchase before moving to S/4HANA.




    KTern also provides the below information about each and every particular user in the ECC system: 

    1. Name of the user
    2. User type (Communication user, Dialog User or System User)
    3. License type (Professional, Limited Professional, Test or ESS user)
    4. Type of Admin user
    5. System to which the User belongs
    6. Last Login date of the User
    7. User status (Active or Inactive

    This feature of KTern is essentially used by the Project Managers and key stakeholders of the customer side. It enables them to have a thorough understanding of their ECC landscape and their licensing model. The main purpose of this feature is to determine the number and type of licenses you need to purchase before moving to S/4HANA. Doing this analysis before moving provides a significant advantage in planning your system conversion. That’s why this feature is included in the Discover phase itself.

    You can read more about KTern’s user license recommendations here.

    Training Scenario Recommendations  

    KTern’s Training Scenario Recommendations feature identifies the business processes which have undergone changes in S/4HANA. You must train the end-users to adopt these changes. KTern also identifies the relevant training scenarios along with the stakeholders who must be trained. This will enable the Project Managers to keep an eye on the training of the end-users and effectively govern the change management process.

    Features

    KTern analyzes and documents the training requirements for the key users and end-users. KTern automatically provides the training scenarios for each module based on the impact of change in S/4HANA. It provides a clear description, status of each training scenario in S/4HANA, and the reference SAP Notes (which has all the changes with respect to that business process).




    One of the most important features of KTern’s training scenario recommendation is that it identifies the key stakeholders of each business process. They are ranked based on their usage of each scenario. For example, all MM consultants use Goods Withdrawal process of Material Management module. This functionality is unavailable in S/4HANA, but an equivalent exists. Hence, you must train the end-users to adopt the new process. KTern provides a list of all the users who use this process and ranks them hierarchically according to their usage. The consultant who uses this process/scenario the most receives Rank 1. Hence, based on this analysis, you can design and execute a training plan in the subsequent phases of the project.

    The stakeholders can then create a training event and assign it to the relevant functional and technical consultants.

    Roadmap Guide  

    KTern’s Impact Analysis module assesses the complete SAP landscape and provides an assessment report. The SAP S/4HANA assessment report enables you to understand the implications of the transition from an existing SAP ERP system to S/4HANA. The Roadmap Guide module of KTern provides an automated high-level roadmap of the SAP S/4HANA system conversion process. The Solution Architects and the Project Managers can then validate the roadmap and proceed with the system conversion project.

    Features

    After assessing an SAP ECC landscape completely, KTern  auto-generates a roadmap and timeline for your S/4HANA conversion. This roadmap/timeline is custom-made for your system only. It takes system complexity, customizations, add-ons, integrations and enhancements into account and then comes up with the timeline.

    KTern also provides a detailed timeline of each of the sub-phases of the project with their start and end date. The Solution Architects and Project Managers can use this rough project roadmap and chart out a detailed plan for the conversion. 




    Effort Estimation  

    The SAP S/4HANA assessment will enable the customer and implementation partner to better understand the implications of system conversion. It identifies the necessary preparation and pre-checks to be done in the current system landscape, long before the real conversion begins. In addition to resource and duration estimation, HANA database sizing and hardware sizing is estimated for an SAP S/4HANA conversion project.

    Based on this SAP S/4HANA assessment report, KTern will use its inbuilt effort estimation engine to accurately predict the efforts and resources for a conversion project.

    KTern accurately estimates costs and resources to optimize the total cost of conversion and to identify and deploy the right resources for an effortless SAP S/4HANA realization. This module helps the customer and the SAP partner to estimate the required man-hours based on user name, module name, transaction name and type as it quantifies the IT effort required to move to SAP S/4HANA. KTern’s AI-powered Effort Estimator also makes you understand the business support required to complete the project. As part of Effort Estimation, KTern provides: 

    1. Recommended Project Timeline
    2. Recommended Duration Estimate
    3. Recommended Resource Utilization Estimate




    KTern accurately calculates the number of technical consultants, functional consultants, solution architects and project managers from both the system integrator side and the customer side. This feature, combined with the roadmap generator, is used to plan a smooth and risk-free transition to S/4HANA.

    Conclusion

    Therefore, in this way KTern performs a complete scan of the connected ECC system and provides a comprehensive SAP S/4HANA assessment report with which you can plan your SAP S/4HANA migration with ease.

    In addition, you can also get started by exploring the features of KTern at https://ktern.com/get-started. Alternatively, if you would like a guided demo of the product from one of our product engineers, kindly get in touch with us by submitting a message at https://ktern.com/company/contact

    If you would like to know more about the SAP S/4HANA Readiness Assessment program, kindly get in touch with us

    Connect with Product Manager

    As an existing SAP ECC customer, if you want to know more about the project or about KTern and the SAP S/4HANA Readiness Assessment program, please get in touch with us through our contact form or connect with our product manager on or through .


    Experience the features in action

    Get started for free. No credit card required!


    Start now