SPAU SPAU selection and start
Introduction/training of the in-memory database
The master's thesis identified and examined in detail influencing factors such as technological trends and the SAP product strategy as well as the company-specific conditions. Several empirical studies were also carried out in the course of the work. If you are interested in the entire Master's thesis and are a DSAG member, you can read the document at info@dsag.de, headword: Master thesis SAP-Basis of Tomorrow, request.
This step is of fundamental importance for the SAP basis. It concerns both the inward-looking perception described in the marketing & self-understanding recommendation and the outward-looking perception in the form of a mission and vision.
High sense of responsibility
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.
Once the UPL is activated, you can access the usage data as follows: Solution Manager: BW Query 0SM_CCL_UPL_MONTH (other predefined Querys available) Managed System: Report /SDF/SHOW_UPL Based on the UPL's data collection, you can now use additional functionalities of the CCLM to depick, for example, proprietary developments that are unused for a long time. Do you know the UPL of SAP and already use it to gain more information about its existing system landscape?
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
The desired speed advantages result.
The data here is not only data tables, but also applications, system control tables and user data.