Hardware Sizing
All information in one place
A degree in computer science is usually a prerequisite and is now almost compulsory. Those who have been trained as IT specialists can take advantage of further training to become SAP Basis Administrators and thus position themselves particularly well on the job market. However, quite a few companies also offer to train employees to make them fit to work as SAP Basis Administrators.
SAP recommends a role design for Fiori permissions based on the defined catalogues and groups in the launchpad. In such a catalogue there is usually a set of apps and services which is relevant for a specific user group. If a role for one or more catalogues in the launchpad has been authorised, the corresponding catalogues and groups will be displayed in the app finder only for eligible users when the launchpad is launched. This ensures that every user only sees what they are working with. Important: These Fiori permissions are maintained on the frontend server! Maintain catalogue permissions in the PFCG To add a Fiori permission to open a catalogue for a role, reopen this role in the PFCG in Change mode and follow the next steps: 1) Select Menu tab 2) Click on the small arrow to add an item 3) Select "SAP Fiori Tile Catalogue" Then select the corresponding Catalogue ID for which the selected role should be eligible. Now the role only has to be assigned to the corresponding users in the system. Once you have completed these steps, you will have the Fiori permissions you need to view individual tile catalogues on the launchpad.
How are SAP modules and SAP Basis related?
In order to reduce the complexity of the SAP basis operation and to accelerate and simplify the tasks of the SAPBasis and to create free capacities, standardisation and automation of the existing activities is required. Details can be found in chapters 7.7 and 9.5 of the Master's thesis.
User authentication is usually performed by entering a user name and password. This information is called user credentials and should only be known to the user, so that no third party can gain access to the system under a false identity. This post explains how a user's password protection can be circumvented and how to prevent it. SAP system legacy data The login data of a user, including password, are saved in the USR02 database table. However, the password is not in plain text, but encrypted as a hash value. For each user there are not only one but up to three generated password hashes. Different algorithms are used to calculate these values, but only the Salted SHA1 can be considered sufficiently safe. Table deduction USR02 The secure password hash is located in the fifth column of the pictured table deduction with the heading Password hash value. The corresponding data field in the column is called PWDSALTEDHASH. Weak Password Hash Risks You have a good and working permission concept that ensures that no processes or data can be manipulated or stolen. A potential attacker now has the ability to read out your database with the password hashes. The hash values are calculated using password crackers, which are available on the Internet at home, and the attacker now has a long list of user credentials. To damage your system, the user will now search for the appropriate permissions and perform the attack under a false identity. Identifying the actual attacker is virtually impossible. Check if your system is vulnerable too Your system generates the weak hash values if the login/password_downwards_compatibility profile parameter has an unequal value of 0.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
Examples include CIO communications or project reports.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
To evaluate the log files, please use transaction RSAU_READ_LOG.