SM59 Configuration of RFC connections
Activation of the email function for all events in the Security Audit Log
Whenever you find a red traffic light on the Roles tab in the user master in SU01 - or a yellow traffic light on the Users tab in PFCG, you can usually solve the problem with a simple user synchronization. The fact that such a user adjustment is necessary can have several reasons. Among others: after a role transport to / when assigning users to roles via PFCG after restricting the validity of roles to users when roles are assigned indirectly via organizational management. Users usually notice the problem of a user comparison that has not been carried out quite quickly: Authorizations are missing, although at first glance they are available in the assigned authorization roles. This is because a user is assigned the correct authorization role - but the profile associated with the role is not up to date.
To add additional permissions for defined groups in the launchpad to PFCG roles, follow the steps described above. This time, you only select a "SAP Fiori tile group" instead of a "SAP Fiori tile catalogue". There are very few differences between permissions. Fiori Eligibility for OData Services The launch authorisation for the OData service stored in the backend from a Fiori app is queried on both the front-end and back-end servers when the application is launched. Therefore, this permission must be added to the appropriate role on both servers. The typical sequence of clicking on a Fiori app in the launchpad triggers the following steps: 1) When selecting the tile, the app Fiori implementation is called 2) The app retrieves dynamic data from the HTTP endpoint of the OData service on the frontend server from 3) An RFC call to the gateway activation of the backend system is followed, retrieving the relevant business logic 4) Now the Fiori permission for the corresponding OData service is queried on the backend 5) If this was successful the appropriate business logic permissions are queried in the OData service. To add the Fiori permission to run a OData service for an app to a role, please perform the following steps: In the PFCG, open the appropriate role in Change mode, perform steps on the following screenshot: 1) Select Menu tab 2) Arrow next to the "Transaction" button click 3) Select Permissions proposal.
As a user of the group, you cannot see tabs either. Now select the applications / tabs to which the group should be accessed (with CTRL you can select several) and select the Grant button. Note: Select the Grant drop-down menu using the button and not the drop-down menu! Use the drop-down menu to determine if and how far users of the group you are currently editing can make CMC tab configurations to other groups / users! Select Grant for the desired tabs. If you still do not see any applications/tabs, it is because the group/user lacks the generic display right at the top level of the respective tab. To do this, go to the desired tab (in the example is the universe), select Manage —> Top-Level Security —> All Universes (the last point differs depending on the tab). Confirm the hint that appears and assign at least the following right for the groups you want: General —> General —> Objects View. Once this right is granted, the tab will also appear on the CMC home page. You can then see the tabs on the CMC home page.
The presentation layer is the top layer of the R/3 SAP Basis system and includes the communication with the user. Here, the data is graphically prepared for the user on the end device by means of software components from the application programs of the application layer. The presentation layer is the interface to the user (SAP GUI).
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
The print jobs are multi-tenant, which means that the authorisation award should also be well thought through at the point.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
These can be found in the RSBASIDOC source system connection table Field Description I_BIW_LOGSYS The logical name of the BW system.