RFC Security, Science-Fiction and Theatre
SWUD Workflow Diagnosis
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).
You can reduce the Queue selection. To do this, select the Support Package that should be the last in the queue. After that, the queue is recalculated. You can also start the recalculation explicitly with Queue. Note that you can only select Support Packages that are part of the software component you have selected (the mouse cursor will change its appearance accordingly). The support packages associated with the calculated queue are green. The highest support package of the previously selected software component is additionally marked with a green tick. The support packages that are no longer part of the queue are still visible in the list and can be selected again. If you want to set the queue for another software component, select New Component. Result You have defined a queue. Now insert the support packages in the queue [page 20]. Rules for the Queue The following rules apply to creating a Queue: If it is an FCS system, the first step is an FCS Support Package. If it is missing from the queue, it cannot be defined. Instead, you will receive an error message telling you the name of the missing FCS Support Package. You cannot insert an FCS support package in a non-FCS system (official state of delivery). Support packages for a selected component are queued in order. If support packages in the queue have connections to support packages of another component (further predecessor relationship, required CRT), the queue will be extended by additional support packages until all predecessor relationships are fulfilled. Note that the SAP Patch Manager takes into account the configuration of your SAP system and only adds support packages to the queue that can be inserted into your system.
SAP Basis - operation, structure and definition
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.
Here, too, the requirements profile for SAP Basis experts has shifted: Database administration is simply part of the job today. The majority of SAP customers place the SAP HANA database in the hands of the Basis team for build and run operations.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
Basis includes a client/server architecture and configuration, a relational database management system (DBMS), and a graphical user interface (GUI).
Resources must be made available for this.