USING STANDARDISATION AS A BASIS FOR OUTSOURCING
Post Installation Services
In this case, the term stands for the basic administration of SAP systems. In this context, responsible employees perform a number of classic tasks.
SAP HANA has been one of the major topics in the SAP environment for the last few years. Many customers are currently faced with the question of whether or not to migrate your SAP system. In addition to the actual changeover itself, there are many other topics on which you should have already informed yourself in advance, as these influence the success of SAP HANA in your company. What do you already know about SAP HANA? I would like to encourage you to think about security in the following article. If you would like to learn about the architecture of HANA, I recommend a contribution from our colleagues at erlebe Software. SAP HANA Scenario But why are we even talking about HANA Security? Why is it so important to consider new security strategies with the new technology? With HANA it is possible to analyse data quickly. BW scenarios primarily benefit from the in-memory database (IMDB) used, as speed advantages in data access are particularly positive. Compared to a classic ERP / R3 scenario, the normal DB is replaced by HANA. The desired speed advantages result. However, migration is expected to be required for the changeover. This is caused by customer-specific developments in the system. HANA is not a further development of SAP ERP, HANA is the next stage of an ERP system. It is well known that an ERP system contains the capital of the companies. Therefore a new HANA system like all other ERP systems is also interesting for attackers. On the one hand, such a system contains the critical business data that are available for espionage. In addition, most business processes are mapped in such a system and offer an attack surface for sabotage. In addition, users do not initially know the new technology well. This also applies to administrators in the area of a new technology. Attackers quickly gain a dangerous leap of knowledge over these user groups. SAP HANA has a lot of new features, although many existing ones are used by SAP ERP, so there is a risk here.
Daily Check Solution
Introducing secinfo and reginfo files into an existing system landscape is associated with risk and effort. As already indicated in the two options, the workload increases greatly as the system landscape grows.
The SAP Patch Manager (SPAM) is the online correction support (OCS) customer site. The SPAM transaction gives you the ability to easily and efficiently import support packages provided by SAP into your system. Depending on the system used or the configuration of your system, you must insert different types of Support Packages [page 8]. You will receive support packages in SAPNet - Web Frontend, in SAPNet - R/3 Frontend or on Collection CDs. Since SPAM runs within the SAP system, you do not need to know the operating system to handle the transaction. In the language usage of SAP, the term patch has been replaced by the term support package. Note that you can only work with this transaction in SAP GUI for Java and SAP GUI for Windows.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
for the maintenance/installation of SAP systems.
secinfo and reginfo Request generator Option 1: Restrictive procedure In the case of the restrictive solution approach, only in-system programmes are allowed.