PFCG Role maintenance
What does TREX have to do with SAP Solution Manager?
In the beginning, in our company, the installation and management of the systems were dealt with by the functional consultants/consultants of the respective systems. The CRM consultant was responsible for the SAP CRM system, the SRM consultant for the SAP SRM, etc.
Presentation layer: The presentation layer is the top layer of the R/3 SAP Basis system and includes communication with the user. Here, the data is graphically prepared for the user on the terminal device by means of software components from the application programs of the application layer. The presentation layer represents the interface to the user (SAP GUI).
AL11 SAP directories
If regulations for the standardisation of SAP systems or tasks and procedures are in place, they must also be consistently complied with and their compliance must also be verified. In case of non-compliance, for example due to project influences or technological problems, the exception must be returned to the standard in a timely manner. Resources must be made available for this.
On www.sap-corner.de you will also find useful information about SAP basis.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
This access method depends solely on the rights assigned to the user. System users: Users of this user group are comparable to SAP*. They act as administrator in the system. Therefore, they should be deactivated / set to inactive as soon as possible, as soon as the system operation is ensured. You should still be aware of the SAP ERP environment to address this security risk. In a HANA system, there are privileges instead of permissions. The difference is first of all in terms of terminology. Nevertheless, the permissions are assigned differently (directly / indirectly) via the assignment of roles. These are thus accumulations of privileges. As in older SAP systems, system users must be disabled and certain roles that already exist must be restricted. Compared to an SAP ERP system, small apps are allowed instead of large applications. In this case, attention should be paid to an individual authorisation. It should be a matter of course for users to have implemented secure password rules. Settings Securing the system also means securing the underlying infrastructure. Everything from the network to the host's operating system must be secured. When looking at the system landscape, it is striking that the new technology brings many connections that need to be secured. The SAP Gateway, which is responsible for the connection between backend and frontend, is also a security risk and must be considered. All security settings of existing and future components must be validated to HANA compatibility. Secure communication of connections is obtained when you restrict access where possible. Encryption of the data of a HANA system is disabled by default. Be sure to encrypt sensitive data anyway. Especially data that is archived. If an attack is made on your system, you should be able to run forensic analysis, so you should enable the audit log. Moreover, few users should have access to it.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
Select the vendor partner type LI and create a new partner agreement.
For this reason, tools are currently being developed to provide security and visibility in the HR permissions area.