Flexible response to peak loads
Transaction Code Description
However, it is not correct to refer to the SAP NetWeaver and SAP HANA platforms as SAP Basis. Both components are only parts of an SAP Basis architecture (see Structure of SAP Basis).
He has already gathered a lot of helpful information from the day-to-day business in his department: Johannes knows the RFC interfaces and the corresponding technical RFC users from his work with the applications. He also quickly got the password for various RFC users via the radio ("As long as passwords are only communicated by phone and never exchanged in writing, we are clean!"). And that the RFC users are generously entitled even in productive systems is no longer a secret ("Better to have more permissions than too little; the RFC connections have to run, otherwise there is trouble from the specialist areas!"). Since Johannes has access to the SE37 as a developer, it is not a problem to get the necessary access using the function block BAPI_USER_CHANGE - disguised as RFC User. In short, it changes the user type of a technical RFC user in a production system from
to by calling the function block.
Products and services at a glance
Let me show you how EasyReCert can simplify this process. Automatic representation of employees & role assignment Each user of the application automatically receives the employees assigned to him. In the first step, the user verifies the assignment of the employees assigned to him. In the second step, the user is shown the roles of his employees. It is now possible to mark the assignment of the role as correct or incorrect. Understandable explanation of the roles Often roles have no talking names and for the decider it is not clear which specific permissions are behind a role. The tool offers the possibility to provide a description for each role, which is available by pop-in. Looking up which role has which permissions and which is meant for which is completely omitted. Flags & Criticality The tool offers in its options the possibility to set flags for critical roles and highlight them in particular. At a glance, the decision-makers see that one of their employees has a critical role and can examine it carefully. Since roles are classified differently in each company, you are completely free to decide which roles you want to consider critical. Roll Whitelist Do you want to exclude certain roles from the audit? Or do you want to test only critical roles? The tool offers you a whitelist function for this. This whitelist allows you to include roles that you do not want to check in the recertification process. So you completely decide which roles the tool should take into account. Logging of the results The results of the tests are logged via the application log and can be viewed both by SAP standard means and directly by the tool. It is also possible to export the audit logs or add optional comments to the logs later.
However, the system modifiability has no influence on customising changes that are customised by the client. If you want to set the customising changes to customise, you must go to the client control. You can achieve this either by pressing the button "Client Control" when changing the system or by calling the table T000 via the transaction SM30. If you are now in the list of clients, you can double-click on the respective row to jump into the settings of the respective client. Here you can also make the desired settings and save them. Step-by-Step Tutorials System Modifiability (Customising Settings and Repository Objects that are independent of the client) Call the SE06 and click on "System Modifiability". Adjust the desired objects and global setting, depending on your request. Save the changes. Client control (custom customising settings) Call the T000 table in the SM30. Double click on the desired client. Change the settings here depending on your request. Save your changes.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
Then define a description and the destination system of the transport.
The security-related system settings and permissions settings applied to your SAPS systems are poorly documented, which in many cases causes the system settings to allow extensive critical access unchecked.