SAP Basis SUM - the Software Update Manager, the relatively new tool for "remote control" of the known update transactions from outside the system, for ABAP and JAVA - SAP Basis

Direkt zum Seiteninhalt
SUM - the Software Update Manager, the relatively new tool for "remote control" of the known update transactions from outside the system, for ABAP and JAVA
Call Inheritance Hierarchy
There are the following types of Support Packages: SPAM/SAINT Update A SPAM/SAINT update (PAT) contains updates and improvements to the SAP Patch Manager and the SAP Add-On Installation Tool. FCS Support Package An FCS Support Package (FFD) brings an FCS system to the generally available release level (GA level) before other support packages can be inserted. Component Support Package One such support package (COP) applies to one software component (SAP_BASIS, SAP_HR, SAP_APPL, etc) and contains corrections for errors in the repository and in the dictionary in exactly this software component. Support Packages for the component SAP_HR include adjustments due to legal changes in addition to these corrections. A BW Support Package (BWP) is a support package for the SAP Business Information Warehouse (SAP_BW) software component and contains corrections only. Add-On Support Package An Add-On Support Package (AOP) always applies to an add-on with a specific release and includes corrections for that add-on.

This saves us a lot of time and ensures that no checks are overlooked when performing manually. Security Automation via HR Permissions HR permissions are a very risky topic in many companies and are often only touched with silk gloves.
Update & Upgrade
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.

The CodeProfiler prevents poor-quality code or programs with security vulnerabilities from entering a productive SAP system landscape in the first place. It is therefore important to use the CodeProfiler throughout the entire lifecycle of a software. Already during programming, the CodeProfiler helps the developer to identify and correct errors and vulnerabilities in the SAP landscape. The CodeProfiler automatically ensures that only "clean" code is transported to the next level (development system -> test system -> quality assurance system -> production system). The CodeProfiler can also be used for regular review cycles.

The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.

Then select the order type "Transport of copies".

The included text of the authorisation concept is completely customisable, so that the concept can be tailored to your situation without creating a permission concept from scratch.
SAP BASIS
Zurück zum Seiteninhalt