Migration and management of cloud-based solutions
Remove weak password hashes from the system: Only updating the profile parameter does not provide you with the necessary security. There are still many weak hash values in your database that can be used to attack your system. These must be completely removed from the database. To do this, use the report CLEANUP_PASSWORD_HASH_VALUES. To do this, call the transaction SA38 and enter the name of the report in the input field. Run or F8 executes the programme and cleans your database Report CLEANUP_PASSWORD_HASH_VALUES This programme removes the outdated hash values across all clients. Have you already experienced this attack method or any other comments on this topic? Share your experiences with us in the form of a comment under this article.
With all these tasks we can support you to compensate e.g. bottlenecks or failures as well as fast growth in your teams. We have resources that have been active in this environment for many years and have gained extensive experience. We are happy to assist you with these challenges.
Restore systems + DB
In order for Fiori applications to be displayed according to the calling users, appropriate Fiori permissions must be maintained in the PFCG. There are several points to consider. This article discusses the permissions required to launch a Fiori application. In addition, a short explanation is given, how the displayed tiles can be configured in the Fiori launchpad via reels. To run Fiori applications from the launchpad and the permission queries defined in the OData services, the corresponding Fiori permission objects must also be maintained in the PFCG. Here the start permissions for the application's OData service in the backend system as well as permission objects are relevant for the business logic of the OData services used in the application. In general, it is important to know that if Fiori is implemented correctly, permissions must be maintained in the front-end server (call Launchpad, start the tile, etc.) as well as permissions in the back-end server (call the OData services from the backend). This article explains this in more detail.
In addition to purely administrative tasks, SAP administrators are also responsible for communication tasks. They work with the company's internal support services to find ways to help users solve and avoid problems and pitfalls they may encounter when using SAP solutions. For internal purposes, the SAP administrator also prepares documentation to look for errors and try to address the root causes. If necessary, he communicates with the company's decision makers so that improvements, adjustments and optimizations can be made to the SAP software.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
Since the desires and the system environments usually grow continuously, this approach becomes complex and confusing over time and troubleshooting often becomes difficult.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
The next step is to define the output parameters.