S4HANA – Saptechnicalguru.com

SIC: Online Simplification Item Check

SAP has an online simplification item check available. This can be used for both a conversion to S4HANA as well as an upgrade of S4HANA to a higher version.

The readiness check inside the system focuses on data used and on mandatory items.

The online check also gives information on changes and potential new features you can use.

Online simplification item check

The online simplification item check can be found here. On the screen select your target version:

Here we simply take the highest version: S4HANA 2023. A new screen comes where you can select the source version and details of the feature pack of the target:

Click on Go to get the result list:

This check does not replace the mandatory readiness check inside the system. It can help you to prepare in planning phase of an upgrade.

SAP Readiness Check for SAP ERP Usage and Data Profiling

To prepare for an S4HANA migration, you can use the SAP Readiness Check for SAP ERP Usage and Data Profiling. This analysis will provide data insights in your current ERP system usage.

Tool installation and run

The tool can be installed by applying OSS note 3112362 – SAP Readiness Check for SAP ERP Usage and Data Profiling. Transport this note to your productive system. The tool needs to have the actual production data. Start program RC_UDP_COLLECT_ANALYSIS_DATA:

Start with the Schedule Analysis. A batch job will collect the data. Once done, you can use the Display Analysis Data button to see the results. The Download Analysis Data allows you to download the data. The data needs to be uploaded to the SAP Readiness site.

Tool result

After uploading to the SAP readiness site, give SAP about one hour to process the data.

Then the analysis result is available:

From left to right:

Detailed data profiles
Module based data profiles
Top list of data volumes

Zoom in on the module based data profiles:

For each part, you can now drill down to table level:

This way you can see if a certain S4HANA change will have much impact or not (due to amount of records).

GTS Edition for Hana readiness check

If your company is running a GTS (global trade system) it might consider a conversion to GTS Edition for HANA. The GTS version for HANA has a different functional scope than a regular GTS system. It might be some functions are no longer supported on GTS Edition for HANA, some might be different, but also new functions might be available.

SAP GTS, edition for SAP HANA: Conversion readiness check

To get the right input for your business, you can run the conversion readiness check. Load OSS note 3033398 – SAP GTS, edition for SAP HANA: Conversion readiness check into your development system and transport it to your productive GTS system. The tool you can already run on development to get an impression, but must finally be run in production to make sure the data checks are done properly.

The note delivers program /SAPSLL/READINESS_CHK_V8000. This program you run in the system. The output is directly a list of items that might require your attention:

OSS note 2973223 – SAP Global Trade Services, edition for SAP HANA: Conversion readiness check – conflict clarification contains extra explanation on the checks.

Unlike most of the other readiness checks, no upload to SAP is required. You just run the check locally.

Bug fix and clarification OSS notes

S4HANA conversion DTV tool (data transition validation)

When you are running S4HANA conversion, this will include financial data conversion. For compliancy reasons the FICO business will demand you run reports before and after the conversion to show that the data is converted ok.

To structure these checks the DTV tool (data transition validation tool) was developed by SAP.

How to install the DTV tool

Master note for the DTV tool is 3117879 – DTV Tool – Central Note.

DTV tool can be used for S4HANA 2021 and higher as target system. There is no installation needed there.

For the source system you need to be on the right support package or install via TCI delivery note 3103342 – DTV Tool Initial Delivery.

Technical reference blog from SAP: link.

How to run the DTV tool

Start of the tool is transaction code DVF:

The detailed steps are described high level in this SAP blog.

All detailed steps (including how to setup connections to source system) are explained in the SAP help file for the DTV tool.

SAP Activate methodology for S4HANA implementations

In the past there was the RunSAP implementation methodology. This is now succeeded with the SAP Activate methodology. The most important one is the S4HANA implementation.

You can go to the methodology using this link.

The roadmap now opens:

The methodology is split into several phases:

Discover
Prepare
Explore
Realize
Deploy
Run

The method is focusing more on using out-of-the-box SAP software and focused on Agile/Scrum way of implementing S4HANA.

On the tab content you can find useful content per phase:

And accelerators per phase:

Keep in mind the method is focusing on green field implementation. Nevertheless you can still use the content and accelerators in your own projects.

SAP Process discovery

SAP offers new tool called Process discovery.

This tool can help you to prepare for an S4HANA conversion.

SAP pathfinder will most likely by succeeded by Signavio process insights. Read this blog for more information on Signavio process insights, discovery edition.

Preparation

Apply OSS notes 2758146 and 2745851 and move them to your productive system.

Then run program RC_VALUE_DISCOVERY_COLL_DATA in productive system with the business scenario recommendation option.

The first option is for the pathfinder tool. You can read more on this option in this blog.

Let the batch job collect the data. Run the program again and use button Download Analysis Data to download the data.

The analysis

Now you can upload this file to the SAP site. Wait about 5 working days for SAP the process the data.

You can look at a sample report on this link:

And you can see the demo results:

Background

Background on SAP process discovery can be read in this SAP blog.

In case of issues you can read the troubleshooting guide: 2977422 – Process Discovery (evolution of SAP Business Scenario Recommendations) & SAP Pathfinder report – troubleshooting guide.

SAP Readiness Check for SAP S/4HANA upgrades

The SAP readiness check is normally used to asses the impact of an ECC to an S4HANA system upgrade or conversion (read this blog).

It can also be used to asses the impact of an upgrade of a lower S4HANA version to a newer S4HANA version.

Preparation for the S4HANA readiness check

First apply the notes listed in master note 3059197 – SAP Readiness Check for SAP S/4HANA upgrades. If you have a short dump after start of program RC_COLLECT_ANALYSIS_DATA, follow the instructions in OSS note 3093810 – Executing report RC_VALUE_DISCOVERY_COLL_DATA immediately results in an ABAP Dump CX_SY_DYN_CALL_ILLEGAL_FUNC.

Also apply the notes mentioned in OSS note 3061414 – Enabling extended integration impact analysis for SAP Readiness Check, if you want to include ALE scenario’s in your analysis.

If you have to upgrade to a newer version, apply the latest version of the 305197 note and afterwards start program /SDF/RC_START_CHECK and use the “Update latest version form SAP catalog” button.

Running the check

Start program RC_COLLECT_ANALYSIS_DATA:

Start the batch job and wait until it is done.

Start program RC_COLLECT_ANALYSIS_DATA again and push button Download Analysis Data.

This file you need to upload on the SAP Readiness check site.

Result

After you have uploaded the results SAP needs about 1 hour to process the results. Then you can look at the items you need to consider for your S4HANA release upgrade:

Remark: the amount of items will be far less than the ECC to S4HANA conversion readiness check.

Bug fix notes

Bug fix notes:

Reducing S4HANA upgrade downtime: ZDO, zero downtime option

Next to nZDTM (near zero downtime) there is now a new option called ZDO (Zero Downtime Option). This new option even further reduces the downtime of an upgrade to a newer version.

The ZDO option is primarily available for S4HANA upgrades (for example upgrade from S4HANA 2020 to S4HANA 20201), but is also available for products based on the same ABAP version, like SAP Focused Run.

How does the ZDO work?

ZDO is the next evolution of the shadow system. Now not only the code is duplicated, but also the data and settings. This is done in a so called bridge system. Postings are duplicated in the main and in the bridge system.

In this way the business downtime is further reduced:

A ramp down, restart and ramp up is still required.

Technical background

All the technical background and restrictions are listed in OSS note 2707731 – Prerequisites and restrictions of Zero Downtime Option of SUM for SAP S/4HANA and training ADM330e.

The note states as well that the basis person must have followed the training ADM330e before the customer is allowed to perform the ZDO option. The option is released for customer, after training. Why is training required? The option is technically very nice, but also complex (updates are done in both the old and new release). The restrictions and execution must be done correctly and in high quality fashion. This cannot be done without proper training.

You should also do a full dress rehearsal of the ZDO upgrade including people posting data in the system during the bridge phase.

The most common use case is an S4HANA upgrade. But the ZDO upgrade can be used in other used cases as well. For example SAP Focused Run can also be upgraded with ZDO. There are special notes, instructions and restrictions: 3269755 – SAP Focused Run 4.0 Support Package 00 – Update Preparation and Postprocessing Documentation. Check the notes carefully for your specific use case.

Memory

ZDO will use more memory since it will have 2 database schemas. Check and monitor this carefully on your test upgrades and extrapolate to production. A ZDO upgrade does require a test run on full production copy size.

Execution of ZDO issues

During execution of ZDO, you will get far more issues and errors as compared to the downtime optimized scenarios. For this reason, the first ZDO upgrade you execute should be on a sandbox system. Preferably as a copy of your productive system. You will learn a lot of things on the sandbox upgrade, to make the real upgrade later on go smooth.

Addons

Some addons might block the upgrade. Some can still be allowed in the upgrade, but cannot be upgraded along with the upgrade and have to remain at the same version. At the bottom of note 2707731 there is an always up to date excel file containing the Allow List for addons.

OSS notes in ZDO checks phase

During the prechecks and later even in shadow system build up, SUM will come with list of OSS notes that need to be applied in main system or in shadow.

For the real upgrade: already apply all the notes on the development system before the upgrade and transport these to production.

Database inconsistencies

All database inconsistencies must be resolved. Repair via SE14, see blog.

BI system settings

ZDO is currently only supported for embedded BI scenario. This might mean you need to get help from your BI team on de-activating some BI content.

To find out what is blocking: go to transaction SE24 and enter class CL_RS_UTILITIES. Start the test tool and launch method GET_SYSTEM_SCOPE. If the answer is DATA_WAREHOUSE, this will block the upgrade. Use your debug skills (or ask ABAP developer) to see which items are throwing roadblocks. Then de-activate or delete that content (with help of your BI team).

Old HANA transport containers

Some old HANA content might block the ZDO upgrade. Read more on this in OSS note 2982320 – HTA for HDI: Error in execution of HDI call: insufficient privilege. Steps to solve: repair privileges on the ABAP HANA user. Run program SCTS_HTA_ADMIN in repair mode.

Background

Background blog from SAP: read here.

S4HANA security parameter baseline changes

If you convert your ECC system to S4HANA or upgrade a S4HANA system to a higher version, you should check the security parameters. A lot of parameters have a different recommendation in S4HANA.

Questions that are answered in this blog are:

Where can I find information on security parameter changes after S4HANA conversion or upgrade?
How can I check if the changed security parameter are properly implemented in my S4HANA system?

Security parameter changes S4HANA

OSS note 2926224 – Collection Note: New security settings for SAP S/4HANA and SAP BW/4HANA using SL Toolset and SUM is the master note. This note contains an important excel attachment that is listing all the changes and recommendations per S4HANA target version.

This note is also referring to OSS note 2926224 – Collection Note: New security settings for SAP S/4HANA and SAP BW/4HANA using SL Toolset and SUM, in which more details are explained on the background.

Checking implementation of security parameter changes in the system itself

After your upgrade to S4HANA, you can run program RSPFRECOMMENDED to check how well the security parameters are implemented:

Set up parallel landscape for upgrades and conversions

When doing a conversion from SAP ECC towards S4HANA you will face a long period where the system is frozen for changes. In most cases business changes still need to continue. For this situation setting up a parallel landscape is a good solution. A parallel landscape might be required for other major upgrades or large data conversions.

How does a parallel landscape work?

How does the parallel landscape work? Initially we have a DEV, UAT and PRD system landscape where transports move from DEV to UAT to PRD system.

With a parallel landscape we install a second development and UAT environment of the same version as the production system. Let’s call them DE2 and UA2.

Now we can start to convert and upgrade the DEV and UAT system to the new target version.

Now 3 development moves are happening:

From DE2 to UA2 to PRD the changes that business is needing (automated support via STMS).
From DE2 to DEV system there is manual synchronization required (dual or double maintenance): all code changes and settings need to be redone (or in some cases even redeveloped).
Transport from DEV to UAT (automated support via STMS): here is where you make your future fixes and developments and move these from DEV to UAT system for testing.

Conflicts between points 2 and 3 often need manual resolution.

At the go-live moment, all transports are imported into PRD from the UAT environment. After live the DE2 and UA2 system can be decommissioned.

Costs of a parallel landscape

Don’t underestimate the costs of a parallel landscape:

Your infrastructure for Development and UAT system will double.
If you are unlucky you also need parallel landscape for connected systems like BI and SCM.
You need basis resources to install, setup, monitor and update the extra systems.
More transports to monitor and to keep track of.
The double maintenance is a lot of work to be done manually. You need also extra person to keep track of administration that the double maintenance is done properly.

Tooling might exist to help, but in practice it cannot cover too many use cases. So don’t get your hopes too high on them.

Alternatives for parallel landscape

There are alternatives for a parallel landscape:

Accept the freeze period
Set up an emergency repair box: copy productive system to a special system for emergency repairs only

These alternatives can be an option for smaller landscapes and organizations.