You must have an SAP license to work with an SAP system. After installing a primary application server, a temporary license is active for only three months. During this period, you must install a permanent license. If the temporary license expires, only the user SAP* can log on to the SAP system.
You can install several licenses. If you change the installation number, all dependent information, such as SAP Software Change Registration (SAP SSCR) keys, is lost.
Conditions Requiring the Installation of a New License
You must install a new license after executing one of the following activities:
- Installed a new SAP system
- Changed the SAP system ID
- Changed the message server host
- Changed the hardware key by changing an existing hardware configuration
- Migrated to a different database
Note this list is not exhaustive.
For more information on how to apply SAP license key, see

Call transaction SLICENSE. The hardware key of the local host is shown on the screen. Use this hardware key to request a license from SAP.
In the AS ABAP-based SAP system, you can use the transaction SLICENSE to determine the hardware key on all SAP system hosts.
You can install a new SAP license on your SAP system using transaction SLICENSE. Select the Install button and upload the license file you received from SAP by mail. Immediately after the license is installed, the license key becomes active.
There are two types of keys that can be installed with transaction SLICENSE. They are delivered together in one license file.
the license key itself – used to prove, that there is a valid license contract for this SAP system – needed for customizing and development in this SAP system
the maintenance certificate – used to prove, that there is a valid maintenance contract for this SAP system – needed for patching and upgrading this SAP system
Note
The maintenance certificate is valid for three months only. To avoid installing a new maintenance certificate every three months in all SAP systems, there is a function in SAP Solution Manager to automize this procedure. This causes a batch job running in SAP Solution Manager, that automatically checks and – if necessary – updates the maintenance certificate.