SAP Basis Concept, planning and execution transports

Direkt zum Seiteninhalt
Concept, planning and execution transports
SAP Basis Service
Why should we even have an individual SAP Security Check performed? Your SAP authorisation concept is designed to ensure the security and protection of data against unauthorised access and abuse. The technical complexity of SAP systems and the ongoing adaptations of business processes often lead to unknown security vulnerabilities. In addition, the increasing digital networking with business partners offers further attack points on your SAP system. SAP Security Check gives you an overview of the security situation of your SAP systems. This will identify potential risks that could jeopardise the safe operation of your IT landscape. Your starting situation The ongoing changes in your IT systems lead to unrecognised security vulnerabilities and your auditors will regularly report to you in the final report on abuses in the authorisation concept. The legal requirements (e.g. EU guidelines) to secure your business processes and IT systems have not yet been implemented and the increasing networking with business partners presents new challenges to your security system. The security-related system settings and permissions settings applied to your SAPS systems are poorly documented, which in many cases causes the system settings to allow extensive critical access unchecked. Critical SAP permissions, profiles, and roles identify permissions that allow critical operations to be performed in terms of security or from a legal or business perspective are called "critical permissions" by SAP. The granting of critical allowances must therefore generally be carried out with particular care and should therefore be planned in advance. Technical and organisational measures and processes must then ensure that the desired level of safety is implemented.

In the SAP NetWeaver BI Authorization Concept lesson, the training participant is familiarized with the authorization functions of the SAP Business Information Warehouse. The differences between the authorization concept for ERP systems and the authorization concept for NetWeaver BI are taught.
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
How are blockchain and digital currencies related? Blockchain technology provides the basis for the existence of a decentralised digital currency. Such a currency is an application that can be executed on the basis of an underlying blockchain. However, the blockchain offers many more applications, such as ownership, identification, communication, etc. , all of which want to get rid of a central controlling party. Blockchain: is the immutable transaction history of a decentralised community. Cryptocurrency: An application of blockchain technology to use a blockchain to secure information about the currency via cryptography. What is Mining? Mining is one of the most misunderstood things about cryptocurrencies. Most people believe that mining is a process in which a cryptocurrency is created. But that is wrong. Mining is a process in a decentralised system to build consensus. Consensus means consent and agreement on what happened and what didn't. In a central system, the central institution does that. For example, a bank with all its advantages and disadvantages. In a decentralised system, the Community decides. To avoid any disagreements, "Mining" is used as one of the possibilities.

You would like to know more about what is happening on your SAP systems - then I recommend that you take a closer look at the Solution Manager Usage Procedure Logging (UPL) functionality. What code is often executed? Which database tables are accessed regularly? What unused developments exist? - The UPL provides answers to these questions. You can implement the functionality into your existing SAP landscape without additional licence costs and with moderate effort. What information does the UPL provide? Usage Procedure Logging is used to log and record user behaviour data roughly comparable to the ST03N workload statistics. UPL is able to record the call and execution of the following ABAP objects: Reports Functional Blocks Classes Methods Subroutines SQL Calls In addition, UPL is able to detect dynamic programme calls and generate transparency about the modifications used. All usage data is recorded in detail and automated and, if desired, made available centrally in the SAP Solution Manager. Benefits 1) Hardly measurable Performance Impact 2) Central collection of data of all systems in the SAP Solution Manager's BW 3) No complex setup 4) Once activated, the collector and extractor jobs run regularly and without further manual activities Possible usage scenario If you have Solution Manager 7.2 in use, you can use UPL within the framework of "Custom Code Lifecycle Management" (in German: management of customer developments). After one activation of the BW content and some standard jobs, you select one or more systems for which you want to activate UPL. If you already have the SP05 installed, there is a separate "Guided Procedure" for configuring the UPL in SOLMAN_SETUP.

"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.

A clearly structured and secure authorization management is very important to avoid errors and prevent access by unauthorized persons.

I hope that with this I can give you some guidance so that you can avoid these mistakes.
SAP Corner
Zurück zum Seiteninhalt