Support in setting up connectors and interfaces
SP01 Output control: spool requests
More security with less effort Internal employees often do not have the comprehensive know-how to know all relevant security risks. However, our security experts specialise in this. We use a standardised approach to determine your current security situation. Based on the analysis results, we show you where the security of your SAP systems can be improved and show you possible solutions. Focus your internal resources on your core business, while our experts will perform a customised audit on your SAP system to determine your security status. SAP Security Check - Our standardised approach (4-step model) Briefing: You register an interest in SAP Security Check. A consultant will contact you and discuss the details of the exam. They have the opportunity to clarify individual issues and to determine the focus of the security check. Data extraction: To ensure that your system is not affected by our audit, we export the relevant data manually or with the help of a data export tool. Analysis: Our security experts analyse the data, evaluate the results and prepare your report. Results: We will discuss the results of SAP Security Check with you. If safety deficiencies have been discovered, we will give recommendations for action on how to correct them. Optionally, you can ask our experts to solve your security risks in the short term. Your security risks become transparent Rapid assessment of your current SAP security status Detailed analysis and documentation Simple traffic light system enables overview of the results You can assess and prioritise the potential for danger for your company for every risk Know-how Transfer and recommendations for action You can easily communicate internally with the transparent and easily understandable final report You can close the relevant security gaps with our measures Optional: Eliminating security deficiencies Experts Our standardised approach enables us to assess the security of your SAP systems systematically and quickly. You do not need to build up authorisation expertise.
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.
Clear authorization concept
Instead of data maintenance and application development, SAP Basis is more about providing and maintaining the software environment on which the data resides and is processed. Therefore, SAP Basis is an important core of any SAP infrastructure and is required in both predecessor versions such as R/3 and current versions such as S/4HANA 2021.
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
A BW system often plays a very central role in larger companies. Here the data from the various connected source systems are analysed and reported centrally. A previous customer of mine had a BW system, to which a total of over 20 other SAPP production systems were connected. With such a large and mostly living system landscape, it is normal that individual systems are dismantled from time to time. However, especially with large SAP landscapes, there are strict regulations regarding the permissions of technical RFC users. For this reason, the simple "right-click —> delete" of a source system in RSA1 will often not lead to the target, but rather to a failed permission check. With this blog post, I'll show you a workaround on how to clean a source system from a BW system using the RSAR_LOGICAL_SYSTEM_DELETE and RSAP_BIW_DISCONNECT function blocks.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
Only with professional care and maintenance of its components can SAP NetWeaver bring its advantages as an integrative platform to bear.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
Following the recommendation of dividing the SAP basis into an application-orientated and infrastructure-related SAP basis [A4], Figure 3 shows a possible presentation form.