Presentation layer (graphical user interface)
For the authorisation requirement of a user, the transactions with user assignment already awarded should be determined accordingly, in order to be able to exclude them when selecting a suitable role. How does this work? There are various ways to identify specific user-assigned transactions, with varying degrees of result. The following article presents two variants. The first section first describes how to use SUIM to address the problem and what problems are encountered. It then explains how the task can be solved by using the transaction SE16N. As in the previous blog post Identifying all transactions of multiple roles, the roles Test_Schmidt1 and Test_Schmidt2 are used for this. Two of the transactions MM01, MM02, MM03 and MM04 were assigned to these roles in different ways. In the Test_Schmidt1 role, the transactions MM01 and MM02 were entered in the Role menu. In the Test_Schmidt2 role, the transaction MM03 was maintained in the menu of the role, but the transaction MM04 was maintained only in the S_TCODE permission object of the role. Both roles have been assigned to the user SCHMIDT_TEST. Identification of certain transactions with user assignment using SUIM This option is useful if only one transaction is to be checked for its existing assignment to a particular user. The audit is carried out here by means of the transaction SUIM. For this purpose, the variant "Roles according to complex selection criteria" has to be executed in the SUIM. After activating the option "With valid assignment of", the corresponding user and the transaction to be checked will be entered here. It is also recommended to hide the display of the collection roles in the search results.
Our SAP Basis trainings and courses originate from our practical work in companies. All SAP Basis trainings for system administration and administrators are conducted by SAP certified experts, who know what they are talking about, because they mainly realize SAP projects at our customers.
With the growth of the company also came extensions and the need for a whole SAP Basis team. Basically, it is a condition that occurs sooner or later in any organization that maintains SAP systems.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
The past ten years have primarily revolutionized the infrastructure and database layer. The fascinating thing is that there have been hardly any changes to the SAP installation program SAPinst during this time.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
If the Support Package implementation stops, you can resume processing at a later time.
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.
The alias of BASIS is SAP Application Server Technology and the alias of NetWeaver is SAP Web Application Server.