SLICENSE SAP License Management
SM65 Background Processing Analysis Tool
Do you want to allow an employee access to exactly one view maintenance dialogue, but he should not be able to search for other care views in the SM30? This can be done easily with a parameter transaction. Learn how to create such a transaction step by step here. To create a parameter transaction, navigate to the SE93 first. Here you can create all types of transactions. The following dialogue will open: After pressing the "Create" button, a popup will open, on which you select the radio button "Transaction with parameters (parameter transaction)". In addition, type a short description as usual and confirm. The following dialogue will open: The transaction code must be specified here first. If you want to skip the entry dialogue when invoking the parameter transaction, and there is no way to open tables other than the one you want, make sure to select "Skip Entry Image". Furthermore, the GUI properties of the SM30 should be inherited so that the parameter transaction can be started with the same software. Configuration of the parameters In the lower part of the dialogue you will find a table ready for input. Here you can use the search help (F4).
Have you ever wondered what there is actually a tab personalisation for role maintenance in the PFCG or for user data maintenance in the SU01? I will answer this question for you in this blog post. What do we need the Personalisation tab for? This tab gives you access to the central repository for personalisation data. The purpose of this repository is to create a storage facility for user- and role-specific data without the need to create additional database tables. This data should then be taken into account in all manipulations of users and roles. The functionality initially includes a generic repository for user- and role-specific data and centralised access to that data by user and role maintenance. It also provides the ability to connect existing tables with user-specific data to the central access via a defined interface. To store personalisation data in the central repository, a key must be assigned to the data: This is done via the registration transaction PERSREG. The personalisation data that you create is stored in the generic drop table. Access to it is provided by the class methods of the CL_PERS_ADMIN class. Different levels of personalisation The data can be stored either to the user, to roles or to the system. A user can then read all data assigned to him (via role or his own settings) at once.
Finally run SQL queries directly in the SAP system
SAP, as one of the world's leading software providers with over 100,000 employees, represents a central component of their system landscape for many companies. Thanks to the many different modules, such as "Finance" and "Human Capital Management", as well as the wide range of customization options, a broad field of professions and possible areas of focus has opened up here in almost 50 years.
As we know, BASIS is a set of tools. This tool has the following different functionalities.
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
SPAM ensures that support packages are only played in the order specified.
The freeware Scribble Papers is a "note box" in which all kinds of data can be stored. It takes in typed texts as well as graphics and entire documents. The data is then organised in folders and pages.
As usual, it must be assigned to a package and a workbench order to become available.