RZ01 Job Scheduling Monitor
Patching
An important area of SAP Security is the analysis of the customer's own SAP programs, which are classically written in the proprietary SAP language ABAP. Here, too, as in all programming languages, security vulnerabilities can be programmed - whether consciously or unconsciously. However, the patterns of security vulnerabilities in ABAP code differ from those in Java stacks or Windows programs. The goal of these conventional programs is usually to either crash the program (buffer overflow) or to artificially execute the program's own code (code injection). Both is not possible in ABAP, since a crash of a process causes nothing else than the creation of an entry in the log database (Dump ST22) and a subsequent termination of the report with return to the menu starting point. So a direct manipulation as in other high level languages or servers is not possible. However, there are other manipulation possibilities.
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.
Archiving and DART
Daily monitoring and maintenance of your systems. Together with you, we create a catalog of measures to ensure the optimal operation of your SAP landscape.
In addition to acute project support, our SAP Basis team can also serve as co-managers. With co-management, your SAP administrator and an abilis employee share the day-to-day tasks.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
Static configuration in the SM19 Under the Dynamic Configuration you can also see if SAL is currently active for the system.
If it was not created, make sure that the [Page 10] Recreate Data File settings in SPAM settings are enabled.