Migration from a change of operating system, homogeneous/heterogeneous database
SWE2 Event type linkage
I recommend that you schedule the background job PFCG_TIME_DEPENDENCY with the report RHAUTUPD_NEW. Scheduling the RHAUTUPD_NEW report with two variants has proven to be a best practice: Once a day before users log on for the first time (e.g. midnight or very early in the morning). This way the users are synchronized once a day. Once a month (or even once a week) with the option "Perform cleanup", so that obsolete profiles and user mappings are regularly cleaned up. Also handy: If the naming conventions of your roles allow it, you can also align the report according to different time zones. For example, I have a customer who runs the user synchronization for his users in the USA and Asia at different times, so that the daily business of the respective users is not disturbed.
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.
Determination of specific transactions with user assignment using SE16N
In earlier product generations, databases from various third-party providers were used - primarily Oracle and Microsoft SQL. However, this has changed with the introduction of the new database generation SAP HANA.
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.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
The first call should automatically open a dialogue to maintain the organisational levels, as they are still empty.
The new roles of SAP Basis employees tend to be "enablers" and coordinators between the cloud provider and internal IT and the business departments.