SAM4U: Software Asset Manager

SAP has released the SAM4U tool to manager your software licenses for SAP. This tool is especially useful in large SAP landscapes.

The SAM4U tool helps you to optimize the licenses. It does not replace the formal license submission tool SLAW2.

Benefits of SAM4U

  1. Improved SAP license cost control
    SAM4U continuously analyzes actual SAP usage and compares it with purchased license entitlements. It helps identify: over-licensed users, under-licensed users, users automatically classified into expensive license categories.
    Opportunities to reduce license costs through reclassification.
  2. Proactive audit readiness
    Instead of waiting for an SAP audit: License consumption is continuously monitored. Compliance gaps become visible early. Entitlements and usage are maintained in one place. This reduces surprises during SAP license audits.
  3. Consolidated View Across Multiple SAP Systems

Usage data from ECC, S/4HANA and other ABAP systems is consolidated. License consumption is tracked centrally. Landscape-wide reporting becomes possible.

  1. User classification optimization

SAM4U analyzes: actual usage, authorizations, assigned roles.

It highlights users who may be consuming more expensive license types than necessary and suggests optimization opportunities.

  1. Authorization analysis

The tool provides: current vs. target user classifications, detailed authorization object analysis, role and profile impact assessments.

This is useful for Basis, Security, and GRC teams performing role redesign or license optimization exercises.

  1. Transaction usage analysis

SAM4U tracks: active user behavior, transaction code usage, historical activity.

Transaction analysis can be leveraged for authorization role redesign.

  1. SAP HANA consumption insights

SAM4U includes: historical HANA memory consumption, database growth trends, HANA enterprise edition analytics. This gives visibility into HANA utilization over time.

  1. Simulation capability

According to the SAM4U user guide, the tool can simulate: changes to roles
changes to authorizations, impact on required license quantities.

This allows “what-if” analysis before implementing role changes.

  1. No data leaves the customer network

License data remains inside the customer’s environment. SAP does not receive operational usage data through SAM4U. This addresses common security and confidentiality concerns.

  1. No additional license cost. SAM4U tool is free of charge.

Time to implement the tool is not for free.

Set up of SAM4U

The setup of the SAM4U tool is clearly described on the SAP help file for SAM4U. SAP also offers help with a service to implement the tool on their SAM4U site.

Central installation

The first part is the installation of the central tool on the central system.

Choose a system with a high S4HANA version. Do not use SAP solution manager.

First make sure on the central system the bug fix notes listed in 3646933 – SAM4U Solution | Fiori Application | V2 are applied. And apply the notes for 3292019 – SAM4U Data Extractor.

Once done goto the installation and upgrade part of the SAP help file for SAM4U:

F0llow all the steps:

Hints: the first 2 steps are confusing. It tells you to start transaction /n/SAM4U/START, but that only works when step 2 is done, where you create the actual start variant.

After completing all the steps when starting transaction /n/SAM4U/START the FIORI page should launch:

Connecting the SAP systems

Per SAP system you want to connect, first apply the notes for 3292019 – SAM4U Data Extractor. The per connected system follow the steps in the SAP help file for SAM4U for the Data Extractor Guide:

Choose between RFC based or file based data extraction. Important in both cases to give the user ID’s the appropriate authorizations as described in both Required Authorizations section as in the Data Gathering section. Make sure the data extractor job runs regularly.

The data of the extractors is stored in table /SAM4U/BEXDUSE. Looking at the content of this table as basis person can also help you to get insights into how end users are using the system. You can find transaction start, but also Remote Function calls.

Administration of systems

Before usage you must administer all your systems in the solution. This part is explained in the SAP help file for SAM4U:

After setting up the proper authorizations go to the Administration section:

In the SAM4U tool add the system by clicking the + sign:

In the popup that comes select the RFC you created from the central system to the backend system. Make sure the user in your RFC has the rights to run and read the SAM4U tables, and has the rights to run the SAM4U RFC modules. If the rights are not ok, the tool will make the connection Red (without further detail). To get the details of what is missing in the target system role, run an ST01 or STAUTHTRACE in the target system for the user ID used in the RFC.

First do one system to test the entire function. When you are happy, repeat for all backend systems.

Next step is to download the ruleset xls which is attached to OSS note 3113382 – Authorization-based SAP S/4HANA User Simulation / FUE Projection. Upload the downloaded xls with the Upload button:

Next step is to download License Entitlement file from me.sap.com. Instructions are given on top. Use the upload button to upload the file:

Running the tool

On the landscape tab run the tool per landscape to gather the data, by pressing the Go button:

Wait until the results are done.

Go to the Consolidation tab and create a consolidation and execute it:

Now the data sections in the Analytics and License entitlement are visible with the data:

For all the functions here, the SAP help file for SAM4U links is excellent to explain the details:

OSS notes and SAP references

If you need bug fix notes search on me.sap.com with the term SAM4U.

Link to the official SAM4U marketing. Small and simple blog on SAM4U.

Link to the YouTube explanation of SAM4U.

SAP GUI 8.10

SAP GUI 8.10 is released now and is supported until 30.06.2029. The first patch level is also release. Future patch levels are published in OSS note 1053737 – Expected release dates for SAP GUI for Windows. PL2 for SAP GUI 8.10 is scheduled for October 2026.

The old SAP GUI 8.00 is supported until 31.07.2027.

General SAP GUI 8.10 help file reference; link. SAP blog page: link.

SAP GUI 8.10 changes

All formal changes are list in OSS note 3549180 – New and changed features in SAP GUI for Windows 8.10.

Caching: 3579956 – Download and caching of multiple types of remote configuration files as of SAP GUI for Windows 8.10.

Custom theming

SAP GUI 8.10 allows custom theming. If you want to use it read the corresponding SAP help file.

32 vs 64 bit

Both are still supported, but only 1 per pc / laptop. See this blog.

Bex components

Bex components are removed from the default SAP GUI 8.10 build. If still needed, read OSS note 3691456 – SAP BW Business Explorer 7.x is no longer included with SAP GUI for Windows 8.10 DVD compilation and must be installed separately.

SAP script components

Some older systems and users might still require SAP script legacy editor: 2221815 – SAPscript Legacy Text Editor controls are not packed in SAP Windows GUI Installation.

Detecting unencrypted GUI and RFC traffic

When protecting SAP landscape with SCN encryption on GUI and RFC, there are 2 parameters that can block all not-encrypted traffic: snc/only_encrypted_rfc and snc/only_encrypted_gui.

Before setting these parameters, you first want to know which interfaces and GUI connections.

Logging settings

To enable the logging, setup in SAP audit log transaction SM20 (or RSAU_CONFIG) the BUJ event for non-encrypted communication:

Next to this set RZ10 parameter snc/log_unencrypted_rfc to value 2 to also log the unencrypted RFC’s.

Warning: if you have many RFC's and start to encrypt them, this event can generate massive amounts of logging. Consider to switch on temporarily to log limited amount of time to get the first work list.

Audit log results for unencrypted RFC and GUI

Use transaction SM20 or RSAU_READ_LOG and select event BUJ.

Unencrypted RFC looks like this for ABAP to ABAP:

And for external RFC to ABAP:

In the details you can find the source IP address.

Unencrypted GUI usage looks like this:

In the Terminal Name column you can find the desktop/laptop of the user still using unencrypted GUI.

SAP Router tips and tricks

This blog will give tips and tricks on SAP Router.

SAP router versions and maintenance can be found in this OSS note: 1897597 – SAProuter: Release rollout.

OSS note 1895350 – Secure configuration of SAProuter covers the security aspects of SAP router. To store encrypted passwords in SAP Router, follow the instructions of OSS note 2046942 – Support encrypted passwords in saprouttab.

SAP router documentation is listed in OSS note 30289 – SAProuter documentation. Public documentation of SAProuter. Help link on help.sap.com on SAP router.

For trouble shooting network issues, follow the instructions in OSS note 1227116 – Creating network traces.

In case you need reverse invoke of the SAP router follow the instructions from this help.sap.com link.

Support backbone configuration

The support backbone configuration is explained in OSS note 2827658 – Automated Configuration of new Support Backbone Communication – Update 02. STC01 task list SAP_BASIS_CONFIG_OSS_COMM can be used to speed up the setup:

OSS notes:

Performance monitoring for http(s) and ODATA

You can setup detailed performance monitoring for HTTPs and ODATA calls to show this information in ST03 workload monitoring.

Setup

Run program SWNC_CONFIG_URL and change the settings:

Background OSS note: 2093522 – ST03 Profiles do not show full information (compressed data). This note also warns that for very large volume there might be issues with the data collection. Solution for that issue is explained in OSS note 2059569 – Runtime error EXPORT_TOO_MUCH_DATA when saving statistic data aggregates.

With report SWNC_CONFIG_PATH you can reduce the path in the recording. See also OSS notes 2285159 – ST03n: Normalization of background job names and URLs in VC/WM profiles and 3070839 – MON-TUN: Extension of length and starting Position for the Normalization of URLs. By doing this, you get more aggregation and also less issues: 3297874 – How to improve the performance of transaction ST03/ST03N on systems with high http(s) workload.

Result in ST03

In ST03 you can now see the results in the part for transaction profile standard overview:

Good background SAP blog: reference.

Funny ABAP code blocks

Just for fun: funny ABAP code block comments….

When we cannot call our own function modules properly, we do deserve a short dump (program LSZA0F34):

Spaceship BERID, MRP area, has adventures (program LATPCFA6):

Program LSHI0F02 has road construction (Baustelle):

Trigger an error or end up in FI hell (program LWOST_CR_IMG01FNG):

A nice golden rule: do not touch coding if you don’t know what you are doing, and if you do it is night work for you in the office to repair it (program SAPMSSYD):

It will be painful (program RPCMSAG0PBS_FORMS):

Program RSORAF01 show life is sometimes terrible:

Complaints in function module ADDR_GET_NEXT_COMM_TYPE about junior programmers:

Some commented out Scheisse (shit in German) in program RV14B000:

Program RSDBPREV calls out to Helga:

ADT-VS: ABAP development tools for visual studio

SAP ABAP on Eclipse will be replaced with ABAP on visual studio (background is explained in this blog). Developments in the RAP framework and AI Joule will be done in ADT-VS. If you are looking for Eclipse ADT installation, read this blog. Both Eclipse ADT and ADT-VS require the ABAP backend installation of the ADT tools, which is the same for both and described in this blog.

Installation and connection to backend

Frequently asked questions blog refers to the formal help.sap.com page on ADT for visual studio code.

Simple steps:

  1. Install Visual Studio Code on your laptop from this URL Download Visual Studio Code – Free AI Code Editor for Mac, Linux, Windows.
  2. Launch the newly installed tool
  3. Go to the Extension on the left hand side:

Search for the ABAP Development tools and install them:

4. Wait for the installation to finish and restart the Visual Studio

5. To add an ABAP destination, click in the menu View and select Command Pallette, and key here ABAP: New Destination

6. In the popup select on the right hand side the + button:

7. Select RFC to backend or HTTP to cloud system:

If you take RFC, the popup will show entries from your SAP GUI.

8. Enter User ID, password, client (be careful here: default it will give you 000, this is NOT what you want), language and password if SSO is not setup

Using the studio

On the left hand side the connections are visible. Right click on any and select the option Logon to Destination:

Rest is same as ADT. Do realize that not all editors are yet working in Visual Studio.

Background references

ABAP AI Joule: read this blog, and this blog. Do realize AI ABAP Joule is licensed and not free of use.

All about ABAP for VS code: blog.

Transport RC-8 errors, reasons and solutions

This blog will list several RC-8 transport errors, explanation of the reason, and solution to solve the RC-8.

Import options

The transport import has a tab for options:

In the below solutions there is reference to the use of these options.

Adding transport again to the import queue

To re-import transport again, go to transaction STMS, go to the import queue, select the menu Extra, Other Requests, Add. Enter the transport request and tick the box Import Again:

Local repair

For some reason the ABAP code was changed locally in the target system.

The text looks like “was repaired in this system”:

Solution: re-import with the overwrite originals flag, and set the flag overwrite objects in unconfirmed repairs.

Component version mismatch

A very frequent cause of transport errors can be component version mismatch. This means that the system detects a difference in components between the source and target (more on components in this blog). That can be a component (like add on) that is already installed on the source , but not yet on target. Or that in the source the ST-PI or ST-A/PI is already patched, but not on the target.

In most cases this version mismatch can be ignored and you can set the “Ignore Invalid Component Version” flag.

When not to set this flag:

  1. Transports related to newly installed addon like customizing/workbench needing the new component
  2. Transports with OSS notes related to this component (for example OSS notes on top of ST-PI)

Missing ABAP object references

A very common cause of RC-8 is that an ABAP program needs an object, which the developer stored in a different transport. To fix the RC-8: import first the transport with the object, then the ABAP program transport. Or import them both at the same time.

To avoid such RC-8’s always run the transport sequence check tool, as explained in this blog.

SAP AI Core

The whole world and also SAP are investing a lot in AI.

This blog explains technical references for the SAP AI Core. We stick to technical facts, not opinions, nor future predictions, nor business cases. There are already more than sufficient blogs on these topics.

SAP AI Core main description

The main information of SAP AI Core can be found in this document published by SAP. Current version at time of writing this blog was from May 2026.

It contains background information about:

  • Architecture
  • License and consumption measurement
  • Setup
  • Security
  • And many more topics

Online cost calculator

Check this link for the online SAP AI Core Cost Calculator.

Starter training

Training for starters:

SAP Help

General SAP help is available on this link.

Useful OSS notes

Available LLM GenAI models on BTP are listed in this OSS note: 3437766 – Availability of Generative AI Models.

Available machine types for Machine Learning: 3660109 – Availability of Hardware Instance Types.

Other OSS notes:

SAP AI architecture

SAP AI golden path for architecture can be read on this official SAP page. This page also refers to a Forbes article on reasons why 95% of AI pilots fail.

The API issue

The problem with AI is the use it needs of the SAP API’s. SAP has created barrier for usage in its API policy: API_Policy_latest.pdf and the FAQ Frequently Asked Questions On SAP API Policy.

This policy goes back to the classic indirect access discussion. SAP cannot sell end user licenses if a single agent is doing the work.

Table analysis tool

In some cases transaction SE16 might not be allowed to be used in a productive system. But as basis you need to analysis a table (for example to count amount of entries).

As alternative you can use the table analysis tool.

Start transaction ST13, and choose tool TABLE_ANALYSIS:

The output:

As alternative, you can also use SA38 to run program /SSA/CAG.

Bug fix OSS notes: