REDUCTION AND AVOIDANCE OF ORGANISATIONAL INCENTIVES
Unicode Conversion
SAP will provide all SAP Notes in the SAP ONE Support Launchpad digitally signed. This is to increase the security when the updates are loaded. If you have unsigned SAP hints, there is a risk that the notice has been changed unnoticed and malicious code will be added to your SAP system when you install the notice. This poses a significant threat to the SAP system, which is why the digitally signed provision of the clues is an important improvement. However, to use digitally signed notes in your system, you will need to take a few steps to prepare them. If you install SAPCAR version 7.2 or later and have a user with the necessary permissions, all you have to do is insert the Note 2408073 into your system and do the manual pre- and post-processing. A digital signature technically ensures that any change can be detected at the notice and can be checked by the system to see if the present note, which is to be inserted into the system, is unchanged. Prerequisites to use digitally signed SAP hints To prepare your SAP system for digitally signed clues, you first have to meet some requirements: Digital signed SAP hints are provided as SAR files. The SAR files are unpacked with SAPCAR and checked for their digital signature. SAPCAR must be available on the Application Server in version 7.20 or higher. Therefore, it is strongly advised to update SAPCAR. If SAPCAR is not at least in version 7.20, the digital signature verification fails and the message cannot be unzipped. Installation of the digitally signed clue is then not possible. The implementing user also needs some permissions to perform the necessary manual pre- and post-processing of the note on the system: Authentication for the transaction SLG1 Read permission for the S_APPL_LOG permission to write and delete data from the application directory Upgrade the SAPCAR version on your system to version 7.20 or higher SAP basis version 700 or higher, for older versions the notice must be inserted manually If you have met these requirements, you can use the implementation of note 24080 Start 73. Implementation SAP Note number 2408073.
If you look at everything I've described up front in its entirety, it quickly becomes clear which direction things are headed: the SAP basis will increasingly move toward an SRE-centric environment over the next decade. This is what the future of SAP looks like, and I look forward to an exciting journey.
SYSTEM
Instead of data maintenance and application development, SAP Basis is more about providing and maintaining the software environment on which the data resides and is processed. Therefore, SAP Basis is an important core of any SAP infrastructure and is required in both predecessor versions such as R/3 and current versions such as S/4HANA 2021.
If your system is already above SAP NetWeaver Release 7.0, then you must either import SAP Note 1731549 or a corresponding Support Package. Afterwards, when creating new users, it is no longer possible to assign user names that are only composed of variants of spaces or other invisible special characters. Important: Changes to already existing users with these names or their deletion option are not affected by this! The SAP Note also adds the customizing switch BNAME_RESTRICT, whereupon you can control yourself whether alternative spaces are allowed to appear in certain places in the user name. For this, the following values must be set in the customizing table PRGN_CUST: NO = The alternative spaces are still allowed in the user name. ALL = The character set is reduced to a defined range, excluding certain special characters because they have specific meanings in certain operating systems or databases. This predefined character set is: ABCDEFGHIJKLNMOPQRSTUVWXYZ_0123456789,;-§&()={[]}+#. FME = The letters F, M and E stand for Front, Middle and End. With an 'X' in this three-digit switch value you can now explicitly specify at which position in the user name no wide spaces and control characters may occur. All combinations are possible, e.g.: XME = None of these special characters may occur at the BEGINNING of the user name. XMX = In the user name none of these special characters may occur at the BEGINNING and at the END. FME = One of these special characters may occur at any position in the user name (this corresponds to the default setting, i.e. as if no entry was maintained in PRGN_CUST for the switch). SAP recommends the use of the value ALL.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
The goal is to understand the authorization concept and the ability to define individual authorization profiles.
As an interface to the user, the presentation layer contains software components (the SAP GUI) by means of which the user is presented with the application.