SU24 Maintenance of authorization default values
Troubleshooting and fault elimination
The SAP Basis Plug-In is backward compatible and follows the release and maintenance strategy of the SAP R/3 Plug-In. SAP delivers it together with the SAP R/3 Plug-In. For more information, see SAP Service Marketplace at basis-plug-in → SAP Plug-In → SAP Basis Plug-In → Releases.
In every company with an SAP system, there is someone who is responsible for the SAP Basis. This person ensures the trouble-free operation of the SAP system. He or she accompanies maintenance work and intervenes in special situations, such as poor performance. Even for companies that hand over the operation of the basis to an external service provider, there are often still tasks from the user and authorization management environment at this point.
Companies face a major challenge. The world is not going digital, but it is already. The age of digitisation and the related technological changes, as well as the demands of customers, bring new opportunities and new challenges for companies. In addition, the product strategy is changing, including that of SAP. In order to achieve the associated goals of the company and to implement them as effectively and efficiently as possible, the SAP basis must contribute to the design of an IT roadmap and to the design of the digitisation and also cloud strategy. A detailed review of the IT Roadmap recommendation is carried out within the master thesis in chapter 7.9.
Basis includes a client/server architecture and configuration, a relational database management system (DBMS), and a graphical user interface (GUI). In addition to interfaces between system elements, Basis includes a development environment for R/3 applications, a data directory, and user and system administration and monitoring tools.
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
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.
The protocol of the Commandfile import contains the cause of the error.