Technology Blog Posts by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
julieplummer20
Product and Topic Expert
Product and Topic Expert
83,438

 

Update, re ASE license for AS ABAP 7.5x

Just a heads-up, since so many people subscribe to this blog post. I am sorry about the delay. However, the ASE license for SAP AS ABAP 7.5x, Developer Editions is now updated and available in the usual place. SCROLL DOWN to ABAP 7.50:

https://developers.sap.com/trials-downloads.html?search=ABAP

In future, all updates about the ASE license will be posted here, so please subscribe here if you are still using any 7.5x version:

AS ABAP 752 SP04, developer edition: NOW AVAILABLE - SAP Community

(The version under 7.52 SP04 is obsolete.)

ABAP Cloud Developer Trial 2022 SP01 now available on Docker!

Hi All, Please find the latest version of ABAP Cloud Developer Trial - 2022, SP01 - on Docker here:

https://hub.docker.com/r/sapse/abap-cloud-developer-trial/tags 

Again, please go straight to the Tags tab, since the Overview Pull command does not work (this is a Docker feature outside our control).

If you want to get stuck in immediately, the Pull command is as follows:

docker pull sapse/abap-cloud-developer-trial:ABAPTRIAL_2022_SP01

Enjoy!

ABAP Cloud Developer Trial is a free, downloadable ABAP Platform on SAP HANA 2.0 for trying out the ABAP language and toolset. It is extensively pre-configured with SAP Fiori launchpad, SAP Cloud Connector, pre-configured backend /frontend connections, roles, and sample applications.

This solution is intended for two groups of developers:

  • Non-ABAP developers, who are interested in learning more about the ABAP language and development tools
  • ABAP developers, who are interested in learning about new features (see below for some examples)

Note: This is the new name for ABAP Platform Trial. The name change is to highlight that you can now develop in the new ABAP Language Version, ABAP for Cloud Development. For more information, see the Highlights below. By the way, if you are interested in our overall release strategy for the Trial, see Karl Kessler’s announcement blog post from 2023: Now available: ABAP Platform Trial

julieplummer20_0-1707312743960.png

IMPORTANT:

All: Before you pull the image

Make sure that you:

  • understand the principles of docker container technology
  • know the entities docker image / docker container and their relationship
  • know the basic commands to work with images and containers

All: Troubleshooting/ Support

Since ABAP Cloud Developer Trial is a free offering for education and demo purposes only, we offer it with SAP Community support. That means that no primary support is available for this product. 

To get Community Support, please create a new question in the SAP Community - ABAP Development forum and add the user tag "#abap_trial". I will try to monitor these questions, but other experienced ABAP users / mentors also see them and often provide support.

(NOTE: Now that comments are no longer threaded, it is almost impossible to keep track of / answer your troubleshooting / error questions, so posting a question is more efficient than posting a comment.)

Mac Users: 

Previously, ABAP Platform Trial ran on both Intel and M-series processors. Since then, Apple has upgraded its iOS. Thus, on the newest MacOS version, you can no longer run ABAP Cloud Developer Trial on Docker Desktop for MacBooks with an M-seríes processor. This is not a SAP-specific issue. So for now, you have two options:

  • Run Docker Desktop with a MacBook that has an Intel processor.
  • Use the UTM app to emulate an AMD64 Linux distro via Apple QEMU.

Many many thanks to Community member @dylan-drummond for researching this. Dylan has written an exhaustive guide to this: 

M-series Apple Chip MacBooks and Abap Platform Trial containers using Docker and Podman 

This is Community content, so consume at your own risk; however, this could be very helpful to many Mac users.

ABAP License

The ABAP license supplied with the Docker image lasts only three months. Therefore, you should download and import the demo license as follows:

  1. Logon to your ABAP system with the user SAP*, client 000, same password as for DEVELOPER (DEVELOPER , client 001, is locked).
  2. Start transaction SLICENSE; copy the hardware key.
  3. Get the license from minisap , choosing the system A4H.
  4. Back in your ABAP System, start SLICENSE again, then choose Install.
  5. Log off, then log on with the user DEVELOPER, client 001.
  6. The old ("INITIAL") license(s) should be deleted automatically. If not, start SLICENSE again; remove the old invalid licenses. (sap* is not allowed to delete licenses).

Updates:

25th October, 2024: ABAP Cloud Developer Trial 2022, initial shipment to be withdrawn

ABAP Cloud Developer Trial 2022, initial shipment will be withdrawn on Thursday, 31st October, 2024, since 2022 SP01 is now available.

1st October, 2024: SAP ABAP Platform 2022 SP01, Developer Edition on Cloud Appliance Library (CAL)

Just a heads-up: Appliance template "SAP ABAP Platform 2022, Platform Edition" has been published externally and can be accessed here:

ABAP Platform 2022 SP01 dev edition on CAL 

 

16th May, 2024: File upload vulnerability - Workaround

Symptom

An unauthenticated attacker can upload a malicious file to the server which when accessed by a victim can allow the attacker to access, modify or make unavailable user's information and system.

Reason

The Content Repository "FILESYSTEM" and "SOMU_DB" are configured with "No Signature" checked.

Workaround

To ensure that a secure default configuration is implemented, correct your system as follows

If you have the relevant access, you can refer to SAP Note 3448171 for more details.

Note that this workaround is a temporary fix and is not a permanent solution. SAP strongly recommends you apply the corrections outlined in the security note, which can be done in lieu of the workaround or after the workaround is implemented:

  1. Execute Transaction 'OAC0'
  2. Open the content repository 'FILESYSTEM' for all releases. 
  3. Change the Version Number to '0047' (Content Server Version 4.7)
  4. Uncheck the checkbox "No Signature" 
  5. Save the settings.
  6. Execute Transaction 'OAC0'
  7. Open the content repository 'SOMU_DB' in case of release 7.50 or higher.
  8. Change the Version Number to '0047' (Content Server Version 4.7)
  9. Uncheck the checkbox "No Signature"
  10. Save the settings.

Highlights of the 2022 Edition

ABAP Cloud Development: Developer Extensibility Scenario

julieplummer20_0-1713188198928.png  

ABAP Cloud map

ABAP Cloud is the ABAP development model you need to build cloud-ready business apps, services, and extensions. Including it in the ABAP Cloud Developer Trial means that you can get a feel for the concepts pertaining to ABAP Cloud Development and to a clean core when extending SAP S/4HANA. This scenario lets you build extensions directly on the SAP S/4HANA stack - tightly coupled, cloud-ready, and upgrade-stable. Of course, we don't offer the strictly business content from SAP S/4HANA. However, we do offer all the language elements - RAP cloud-optimized language, and released APIs and extension points. 

Important: You are thereby restricted to  cloud-optimized ABAP language. That is, if you are used to developing in Classic ABAP on-premise, and want to try out Cloud development, you must comply with ABAP Cloud Development rules, such as:

  • Use public SAP APIs (local or remote) released by SAP to access SAP functionality and SAP data
  • Use public SAP extension points released by SAP to extend SAP objects. Modifications to SAP objects are not supported. (This includes SFLIGHT, for example.)
  • Use ADT (ABAP Development Tools) as your ABAP IDE
  • Use RAP (ABAP RESTful Application Programming Model) to build Fiori apps and services. SAP technologies like Dynpro or Web Dynpro are not released for ABAP cloud development
  • The software components ZLOCAL and ZCUSTOM_DEVELOPMENT can only be used for ABAP Cloud development - that is, compliant with these rules

More information:

ABAP RESTful Application Programming Model (RAP) - 2022

julieplummer20_2-1707312818813.png

Offers you an efficient way to build enterprise-ready, SAP HANA-optimized, OData-based Fiori UI services and Web APIs in the cloud as well as on-premise.

New features in 2022 include:

  • Custom business objects
  • Event Consumption and Exposure
  • RAP Generator
  • RAP business object Test Double Framework (TDF)

To make it easier for you to get started, we have also added:

More information: 

 

Git-Enabled Change and Transport System (gCTS)

Snag_c56468.png

gCTS = CTS + git

A new way of transporting objects, gCTS enables you to use Git to store your ABAP development objects. gCTS makes use of special Git features, such as working on local copies of a central remote Git repository. Software development takes place in the usual editors like ABAP Development Tools (ADT). Changes to objects are still recorded in transport requests. Current states of objects can be pushed to remote Git repositories, either by releasing a transport request or while you’re working.
For the official documentation overview, see: 

Git-Enabled Change and Transport System (BC-CTS-GIT) | SAP Help Portal

The official documentation for configuration is in two parts:

  1. Configuring Git-Enabled Change and Transport System
    Here, we have preconfigured the first two parts, so you only have to complete parts 3-5:  
     julieplummer20_0-1714132333934.png
  2. Configuring Git Repositories

Some certificates are already available. If you would like to connect to your own GitHub server or to a provider other than github.com, you have to add the appropriate certificates to the ABAP system in transaction STRUST. The configuration has been done for the default user ‘DEVELOPER’.

To get started with gCTS, simply open the gCTS app in the SAP Fiori Launchpad (FLP).

If you are a SAP customer, partner, or employee, the following SAP Note provides additional information: SAP Note: 2821718 . However, the essential configuration has already been done for everyone.

abapGit

julieplummer20_1-1711536855908.png

Yes, abapGit is available out of the box.
Documentation is here: abapGit Documentation
If you are not yet familiar with abapGit, this post by graham.robinson is a great introduction, with how-to videos:
abapGit So Easy

Custom Code Migration with the ABAP Test Cockpit (ATC)

We've pre-configured ABAP Platform Trial to run as a central check system for checking your custom code prior to migration - particularly useful for:

  • SAP S/4HANA Readiness Checks
  • SAP Cloud Readiness Check

You can test this out of the box locally in SAP ADT, then configure the rest of your landscape to work with it.
For more general information on ATC, see these two excellent blogs, by Olga Dolinskaja:

SAP Cloud Connector

julieplummer20_0-1707312915858.png

SAP Cloud Connector provides a link between SAP Business Technology Platform (BTP) applications and on-premise systems. It runs as on-premise agent in a secured network; acts as a reverse invoke proxy between the on-premise network and SAP BTP; and lets you use existing on-premise assets without exposing the entire internal landscape.


If you are interested in connecting your ABAP Platform Trial with a licensed version of SAP BTP, ABAP Environment (i.e.“Steampunk”), I have written a tutorial mission on this: Connect Your On-Premise System with SAP BTP, ABAP Environment

For more information, see:

 

Other Highlights of ABAP Platform 2022: Overview

Blog post: ABAP Platform for SAP S/4HANA 2022, from November 2022, by Olga Dolinskaja, including the Overview Presentation

Guides, Tutorials, FAQ, Troubleshooting

If you’re not sure where to start with your new system, we have written several tutorials:

SAP Tutorial Navigator: ABAP On-Premise Tutorials.

I have started putting together FAQs specifically for ABAP Platform Trial / ABAP Cloud Developer Trial on Docker. If you would like to contribute to this, please let me know:

ABAP Trial Platform on Docker: Tips and Tricks

The old FAQs  also contains some non-release-specific info on Cookbook-style projects, by SAP Community members: I will 

FAQ and Troubleshooting for SAP AS ABAP 7.5x

Issue: Docker container works only for a few hours: "

Since I cannot currently edit the FAQ, I am repeating the following from Attila

"I disabled the Resource Saver in Docker Desktop, and it fixed the connection issue happening after few ours of my Win11 computer is idle / locked.

julieplummer20_0-1716967341205.png

 

According to the Docker documentation the Resource Saver setting should not suspend tcp connections or similar. Do not understand why, but looks like it works."

 

174 Comments
Kushal_Banerjee
Explorer

Hi Julie,

Greatest Thanks for your advice and support. Just wanted to know one quick question mentioned below: -

After installing Docker instance "sapse/abap-cloud-developer-trial:ABAPTRIAL_2022_SP01" into my Laptop (Intel 7i and 32Gb RAM) on the same instance can install SAP Add-on SAP Content Server of OpenText Content Server, OpenText Archive Center Services  and Upgrade SAP OpenText Application into same "sapse/abap-cloud-developer-trial:ABAPTRIAL_2022_SP01" ...?

Please kindly help me by replying me exactly.

Thanks & Regards

Kushal_Sambhunath_Banerjee

julieplummer20
Product and Topic Expert
Product and Topic Expert

Hi @Kushal_Banerjee , 

I am sorry but this is beyond the scope of my product specialism. I would suggest that you post this question on a forum with more reach - namely,  SAP Community - ABAP Development forum .

Also, please read the license agreement carefully.

I am sorry I can't help any further.

Best wishes,
Julie Plummer.

Hi All,

Can you tell me with YES/No answer whether in this SAP Docker Container instance (sapse/abap-cloud-developer-trial:ABAPTRIAL_2022_SP01) will it be possible to install Add-on OpenText DS,CS or/and AC instances ?

Thanks

Kushal_Sambhunath_Banerjee

yury_sichov
Active Contributor

In ABAP Cloud Developer Trial 2022 every time I start docker ( docker start -ai a4h )  I always got different Hardware Key . . : U1856651609 (of this computer (for example) next run - it will change again. And licence file updation doesn't work. Probably because of that issue with altering Hardware key. I have been using 7.52 and Trial 1909 there was not such problem. Laptop was Dell but older model. No idea how to solve licence problem. 

Fl0r1n
Participant

Hi @yury_sichov 

Had the same problem two weeks ago when installing the new license file. 

My workaround was to manually replace the hardware key from the generated file with the hardware key that the system is expecting (from the error message i.e.)

After this the system accepted the newly generated license.

Florin

stephan_daub
Product and Topic Expert
Product and Topic Expert

Dear @Fl0r1n and @yury_sichov 

thanks for using SAP Cloud Developer Trail 🙂
Regarding the "issue" with the changing HW keys: there is no issue at all.
Every time you restart your container it MAY get indeed a new HW key.
But: the licensing mechanism inside the SAP stack will determine if there is a valid license and will update the relationship "HW key <> valid license" inside SLICENSE.

See this example I had performed some days ago:

1.) There was a license before with this maschine data:
----- Begin SAP License -----
SAPSYSTEM=A4H
HARDWARE-KEY=I1028913049
INSTNO=DEMOSYSTEM
BEGIN=20250330
EXPIRATION=20250630

2.) After this step, I stopped the container, did an update of docker desktop software and re-started the container.

3.) During the container start, the HW key changed to S0898059505

stephan_daub_0-1743661117858.png

4.) Finally, if you check with SLICENSE....

stephan_daub_1-1743661169316.png

... you will find the "overall" license still valid even the license was issued for another HW key 😊

Conclusion:
If you have a valid license, changing the HW key will not invalidate the license.
But be careful: this rule only valid in this scenario;)

Please check your SLICENSE information and post it here for further investigation. The image is nearly 6 month on the market and had been downloaded many times.

Small hint for free: Please kindly check:
https://community.sap.com/t5/technology-blogs-by-sap/abap-cloud-developer-trial-2022-available-now/b...
(this is THIS document) -> Section "ABAP License" how to extend the license.


Best,
Stephan
SAP - ABAP Cloud Developer Trial Team

yury_sichov
Active Contributor
0 Kudos

Thanks a lot, Fl0r1n and stephan_daub.

Probably Hardware key is not an issue. But I have trouble with passwords. Maybe I lost this valuable info.

I can not run Slicence and check because I don't have SAP* password. I have only DEVELOPER psw - Ldtf5432 (from trial 1909 - it may be wrong psw)

In instruction said - 

  1. Logon to your ABAP system with the user SAP*, client 000, same password as for DEVELOPER (DEVELOPER , client 001, is locked)."

Probably I missed somewhere correct password. I guess  someone can tell me a correct passwords.

With running Slience I just can upload correct licence As I did always earlier. And no need to run  

docker cp A4H.txt a4h:/opt/sap/ASABAP_license​

Thanks in advance.

stephan_daub
Product and Topic Expert
Product and Topic Expert

Dear @yury_sichov 

all passwords are listed in section "User and Passwords" in the docker README.md located here: https://hub.docker.com/r/sapse/abap-cloud-developer-trial 

Have a nice day!

Best,
Stephan
SAP - ABAP Cloud Developer Trial Team

 

 

yury_sichov
Active Contributor
0 Kudos

Thanks,  stephan_daub

Solved.

kyo_choi2
Participant
0 Kudos

Has anyone tried to use the HANA DB using HANA Studio or HANA modeling perspective in ADT?  If so which user ID/PW should I use?

j_l_l
Newcomer
0 Kudos

Hi,

I have installed ABAP cloud developer trial 2022 SP1 on my Windows 11 Home laptop with 32GB of RAM, I am running Docker on WSL2. Problem I have is whenever I log into the system, I get runtime error "DBIF_REPO_SQL_ERROR occurred. P1=ABAP-generat" and I am logged out of the system, with SAP logon message "SQL Error 4 while accessing program SAPMS380 part (location vhcala4hci_A4H_00-W6)". Could anynone please help with this?

Thank you very much in advance for your help!

vodela
Active Participant
0 Kudos

hello

In the developer edition, when I create a package in the settings for Default Language Version there is only one option ABAP for Cloud Development - as this is a test system for developers is there any way I can get other options such as ABAP developers etc so that my development is not restricted by the limitations imposed by the cloud settings.

Best regards

RameshScreenshot 2025-04-06 192246.jpg

Hi Ramesh,

Related to your question. Following may be the approx answer: -

In the SAP Cloud Platform ABAP Environment (also known as ABAP in Cloud or SAP BTP ABAP Environment), the ABAP language version is restricted to "ABAP for Cloud Development" to ensure compatibility and security.

Limitations of ABAP for Cloud Development
The ABAP for Cloud Development language version has certain restrictions compared to the standard ABAP language version used in on-premise SAP systems. These restrictions are in place to ensure the stability and security of the cloud environment.

Options to Access Other ABAP Language Versions
If you need to develop with other ABAP language versions, such as ABAP Developer Edition, you may consider:

1. SAP ABAP Developer Edition: You can install the SAP ABAP Developer Edition on your local machine, which provides a more traditional ABAP development environment.
2. SAP Cloud Platform Trial: You can also use the SAP Cloud Platform trial version, but keep in mind that it will still be restricted to the ABAP for Cloud Development language version.

Considerations
Before choosing an option, consider the following:

1. Cloud vs. On-Premise: Determine whether you need the specific features and restrictions of the cloud environment or if an on-premise solution is more suitable for your development needs.
2. Licensing and Costs: Familiarize yourself with the licensing and cost implications of each option.

NOTE: Correct me if I am wrong.

Thanks & Regards

Kushal_Sambhunath_Banerjee

julieplummer20
Product and Topic Expert
Product and Topic Expert
grafitosLeg
Explorer
0 Kudos

hello - if somebody could help with this topic as below 

I've installed  ABAP Platform 1909 SAP GUI for Windows and with Docker image I've tried to run the SAP GUI

- the problem with the licence immidiately occurred and I tried to logon to SAP* to fix this problem  - unfortunatelly I locked the SAP GUI with the message "Password logon no longer possible - to many failed attempts" - I've tried to reinstall SAP logon several times, clean the registry and the only attempt will stay like to reinstall Docker installation because , I suppose...because the failed attempts are stored in the application server...

the only Login ID that is consider is IDADMIN on 000 Client but... instead "Password logon no longer possible - to many failed attempts" messsage I got "Logon not possible  - error in license check" -  but can't to get it ... 

regards

 

grafitosLeg_0-1744140197328.png

 

Sigurdur
Participant

You should also be able to use logon DDIC on client 000, just take care to find the correct password in docker instructions, and the go to transaction SU01 to unlock SAP*

grafitosLeg
Explorer
0 Kudos

That's fantastic advise Sigurdur !

From reading to understanding there's a long way, especially we don't ..read... 🤣🤣

Thanks Bro  - it works now 

 

GauravGaurav
Discoverer
0 Kudos

@stephan_daubI have newly installed ABAP developer trial, but I'm not able to login as DEMO license is expired now and License from minisap is not working as the Hardware Key is changing on every restart.

Any workaround?

Hi Gaurav, Expected solution for your problem is mentioned below:-

Possible Solutions

1. Fix the Hardware Key Stability

You can stabilize the hardware key by:

  • Setting a fixed hostname and container ID.

  • Mapping /etc/hostid from the host to the container (Linux only). 

  • Alternatively, patching the system to always generate the same hardware key (hacky but effective).

    Steps to try:

    In your Docker run command (or compose file), use:

    --------------------------------------------------------------------
    bash
     
    docker run --name a4h \
    --hostname=a4h.local \
    --add-host=a4h.local:127.0.0.1 \
    -v /your/local/path:/sybase \
    -e SAP_SYSTEM_SID=A4H \
    -e SAP_SYSTEM_PASSWORD=YourPassword \
    -p 3200:3200 -p 3300:3300 -p 8443:8443 \
    sapse/abap-cloud-developer-trial:ABAPTRIAL_2022_SP01
    --------------------------------------------------------------------------------
    This alone may not fix the Hardware Key issue unless the underlying OS/container logic generates it consistently. If not:
    • Try exporting the HOSTNAME environment variable inside the container, and editing /etc/hostid if your host allows that (some distros restrict it).


      🔄2. Apply a New License on Each Restart (semi-automated)

      If you can’t stabilize the hardware key:

      • Just request a new license every time the hardware key changes.

      • Automate it as part of the container startup:

        1. Parse the hardware key from transaction SLICENSE.

        2. Submit it manually to SAP Minisap.

        3. Upload the new license via SLICENSE or with saplicense tool.

          Temporary Fix: View Hardware Key

          You can get the current hardware key from inside the container like this:

           

          bash
          docker exec -it a4h bash saplicense -get
           
          OR from SAPGui in tcode SLICENSE.

          Thanks

          Kushal_Sambhunath_Banerjee

           

GauravGaurav
Discoverer

I fixed the issue by applying license after the installation. Below are the steps

  1. Install and run the docker image. Cannot login in GUI as default license is expired.
  2. Get the Hardware key from the terminal.
  3. Get the license from minisap using hardware key.
  4. Copy the license into the running container by command 
docker cp <local path the key file> a4h:/opt/sap/ASABAP_license
  •  Trigger license update. 
docker exec -it a4h /usr/local/bin/asabap_license_update​
  • Now login into GUI and check in SLICENSE t-code.
  • Now on every restart whenever the Hardware key changes. License should be valid.
Th0mas
Discoverer
0 Kudos

Hi,

Docker.Desktop Windows Version 4.40.0
ABAPTRIAL_2022_SP01

i have a Problem with the license update in a existing container.

My Steps:

Get the Hardware key from the terminal.
Get the license from minisap using hardware key.
Copy the license into the running container by command

 

Th0mas_1-1745224721293.png

Trigger license update. 

Th0mas_2-1745224793750.png

Login  Client 000 or 001 as sap*(normal user cannot login)

Th0mas_3-1745224975841.pngTh0mas_4-1745225014375.png

What can i do to fix the Problem?

Best Regards
Thomas

 

 

custandcode
Explorer
0 Kudos

Hi Th0mas,

interesting, never had the issue with the changing HW Key. I change my licences always with TA SLICENSE in SAP GUI. I have checked my A4H System now and I see a list of HW Keys, one active, the other inactive. 

regards
CC

DenisGaland
Participant
0 Kudos

fixed

Kushal_Banerjee
Explorer
0 Kudos

Hi Th0mas,

Expected solution for your problem is mentioned below:-

Possible Solutions

1. Fix the Hardware Key Stability

You can stabilize the hardware key by:

  • Setting a fixed hostname and container ID.

  • Mapping /etc/hostid from the host to the container (Linux only). 

  • Alternatively, patching the system to always generate the same hardware key (hacky but effective).

    Steps to try:

    In your Docker run command (or compose file), use:

    --------------------------------------------------------------------
    bash
     
    docker run --name a4h \
    --hostname=a4h.local \
    --add-host=a4h.local:127.0.0.1 \
    -v /your/local/path:/sybase \
    -e SAP_SYSTEM_SID=A4H \
    -e SAP_SYSTEM_PASSWORD=YourPassword \
    -p 3200:3200 -p 3300:3300 -p 8443:8443 \
    sapse/abap-cloud-developer-trial:ABAPTRIAL_2022_SP01
    --------------------------------------------------------------------------------
    This alone may not fix the Hardware Key issue unless the underlying OS/container logic generates it consistently. If not:
    • Try exporting the HOSTNAME environment variable inside the container, and editing /etc/hostid if your host allows that (some distros restrict it).


      Kushal_Banerjee_0-1746174256411.png

       

      2. Apply a New License on Each Restart (semi-automated)

      If you can’t stabilize the hardware key:

      • Just request a new license every time the hardware key changes.

      • Automate it as part of the container startup:

        1. Parse the hardware key from transaction SLICENSE.

        2. Submit it manually to SAP Minisap.

        3. Upload the new license via SLICENSE or with saplicense tool.

          Temporary Fix: View Hardware Key

          You can get the current hardware key from inside the container like this:

           

          bash
          docker exec -it a4h bash saplicense -get
           
          OR from SAPGui in tcode SLICENSE.

          Thanks

          Kushal_Sambhunath_Banerjee