To inherit SAP permissions with different organisational levels
OAC5 Barcode Capture Settings
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).
The results of the tests can be documented so that the development can be considered over a period of time. This way, you will be aware of the revision and of the relevant issues before the examination.
SAP Emergency User Concept - How it works and how it works
Often one is obliged to perform a migration. There are various reasons such as legal requirements or preparatory measures for an S/HANA conversion. We are happy to support you in your decisions.
The website www.sap-corner.de offers many useful information about SAP basis.
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.
Tasks such as the update of components, the insertion of security updates or monitoring should be further automated. It is recommended to use only one automation tool (SAP Solution Manager or SAP LVM). Custom solutions and scripts should not be used or replaced with standard tools if possible, because otherwise different script languages and script versions will have to be managed, resulting in a lot of maintenance. Standardised SAP scripts are welcome here. A useful definition of thresholds, for example on the basis of historical system behaviour, must also be defined for monitoring.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
The necessary skills and roles for the SAP basis are explained in detail in the recommendation Skills & Roles.
I described the different scenarios of when such a user can be used and how to deal with them in this blog post for you.