Advantages of SAP Basis Support
Roles
On the one hand, staff clerks (or other personnel officials) should be able to carry out their important work. On the other hand, the protection of personal data of one's own employees is one of the most important tasks of the authorisation system. Any mistake in this area can cause the company's data protection officers to wring their hands over their heads. For this reason, tools are currently being developed to provide security and visibility in the HR permissions area. The basic idea is a clear overview that shows which data certain users in the SAP system can access. Based on this, automatic checks can be developed, which run in the background and regularly check whether critical gaps have been created by changes to the permissions in the HR area. The use of such a tool can create more security, especially in the HR authorisation environment. In addition, the possibility of the overview function is very pleasant and relieving for all involved. Read more This blog post is intended to show what is already possible in the field of Security Automation. The topic will accompany us more and more in the SAP area in the next few years. Therefore, it is recommended to start thinking about how your company is prepared for security automation. If you are interested in setting up and preparing a company outside the security area, I can recommend the book 'Consulting Y' by Ferdinando Piumelli (Managing Director of mindsquare GmbH). In this book, Mr. Piumelli describes his observations and experiences of digital transformation as a strategy consultant for leading DAX30 companies. In doing so, he is focusing on the near future, which, in the spirit of the digital revolution, will have a major impact on the world's large companies and economy.
The identification of critical SAP permissions for the use of an SAP system must therefore be carried out in any case. In addition to permissions, you can also identify critical profiles and roles that are already in the delivery state.
Definition
In the default scenario, the support packages in the queue are fully loaded. In the event of an error, you will not be able to resume and complete the playback successfully unless the error(s) are resolved. Prerequisites The queue is already defined. Procedure To set the scenario you want, select Additions Settings. Select the desired scenario. Select Insert Support Package Queue. You can also use this function to restore an aborted commit procedure. The status bar provides information on the progress of the commit and the latest steps of the SAP Patch Manager. During the recording, you may get into the modification comparison (SPDD, SPAU). If you are playing with the default scenario, you must immediately perform the comparison of Dictionary objects (transaction SPDD), whereas when you compare Repository objects (transaction SPAU), you have the choice to skip it first and perform it later (modification comparison [page 22]). The mode is blocked while a Support Package is being introduced. To avoid repeated login, open a second mode before inserting the queue.
You would like to know more about what is happening on your SAP systems - then I recommend that you take a closer look at the Solution Manager Usage Procedure Logging (UPL) functionality. What code is often executed? Which database tables are accessed regularly? What unused developments exist? - The UPL provides answers to these questions. You can implement the functionality into your existing SAP landscape without additional licence costs and with moderate effort. What information does the UPL provide? Usage Procedure Logging is used to log and record user behaviour data roughly comparable to the ST03N workload statistics. UPL is able to record the call and execution of the following ABAP objects: Reports Functional Blocks Classes Methods Subroutines SQL Calls In addition, UPL is able to detect dynamic programme calls and generate transparency about the modifications used. All usage data is recorded in detail and automated and, if desired, made available centrally in the SAP Solution Manager. Benefits 1) Hardly measurable Performance Impact 2) Central collection of data of all systems in the SAP Solution Manager's BW 3) No complex setup 4) Once activated, the collector and extractor jobs run regularly and without further manual activities Possible usage scenario If you have Solution Manager 7.2 in use, you can use UPL within the framework of "Custom Code Lifecycle Management" (in German: management of customer developments). After one activation of the BW content and some standard jobs, you select one or more systems for which you want to activate UPL. If you already have the SP05 installed, there is a separate "Guided Procedure" for configuring the UPL in SOLMAN_SETUP.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
In the pop-up you have to name the exact transport order.
What experience have you had with EDI? I look forward to your feedback.