SAP HANA Cloud Platform (SAP HCP)
The Client Control
If you want to skip the backgrounds and prefer a direct step-by-step guide, you can jump directly into the last section. Preparation For this workaround, you need access to both the source system and the BW system. In addition, they shall have the possibility to access the SE37 and execute functional modules there. Especially in production systems this is a very critical justification. So assume that you may need a Firefighter user for this action. Working in the BW system Now that the preparations have been completed, you have to call a FuBa on the BW system and on the source system, which solves the connection on the respective page. Beginning on the BW system, go into the transaction SE37 and call the function block "RSAR_LOGICAL_SYSTEM_DELETE": RSAR_LOGICAL_SYSTEM_DELETE Enter the required values here. The following table helps you fill in: Field Description I_LOGSYS The logical name of the source system. The name of the source system, as found in RSA1, will be entered here. In addition, this name can also be found in the DB table TBDLT. I_FORCE_DELETE Boolean, X = Delete despite error messages I_NO_TRANSPORT Boolean, X = This change should not be transported to subsequent systems I_NO_AUTHORITY Boolean, X = Ignore Permission Checks Work in the source system In the source system, go to transaction SE37 and call the function block "RSAP_BIW_DISCONNECT" : The descriptions of the fields are as follows. These can be found in the RSBASIDOC source system connection table Field Description I_BIW_LOGSYS The logical name of the BW system. In the RSBASIDOC table, find the correct value in the column "RLOGSYS". I_OLTP_LOGSYS The logical name of the source system. The column ‘SLOGSYS’ in the table RSBASIDOC. I_FORCE_DELETE The logical name of the BW system. In the RSBASIDOC table, find the correct value in the column "RLOGSYS". Completion In the end, you have to call the respective function block in the BW and source system, fill in the parameters and execute the function block.
There is no way around containers, and even SAP will soon have to reorient itself here and allow the NetWeaver stack to be run in containers. There are many indications that Kubernetes will win the battle for supremacy among container management tools. SAP has also already invested in Gardener and is also intensifying its partnerships with IBM and Red Hat Openshift.
Import external transport orders to an SAP system
New risks in SAP HANA: In addition to the known risks, there are also new risks from the use of SAP HANA. A very good example are frequently used web applications that represent something new in the SAP area. In contrast to an SAP ERP system, HANA systems consist mainly of web applications, which were considered optional in the previous versions. These web applications can be found by various search engines on the Internet. This also applies to SAP Portal or Netweaver. There are URL schemes that help locate the system. This also applies to other SAP systems that use Web applications. This makes the new technology vulnerable to typical web attacks. SQL Injection, ABAP Code Injection, or XSS are all included. All risks known for a normal SAP system also apply to a SAP-HANA system. The data is stored unencrypted in RAM. Only then does the system gain this speed advantage. This results in risks such as a read-out by memory scraping malware. These pick up data in memory. Encryption costs performance, so it is not used by default. Especially during a migration HANA runs in a parallel system, therefore at least one new system comes to your landscape. Also note: HANA has its own tools and settings that need to be known and configured. The bottom line is that the system simply needs more attention when operating. Many settings often result in more errors. Three - points - HANA Security Plan 1) Roles and permissions In a previous SAP system, roles and permissions are certainly one of the main pillars of a secure system. Roles and permissions work differently in a HANA system. There are two types of users: 1) Default (limited): With this type of user, there are different access methods to the database. For example, the JDBC or HTTP technologies are used to give two examples.
If we look at the question of standardisation, this concerns not only the administrative side of IT products, but also the standardisation and simplification of IT products offered by the SAP basis. For this purpose, tools such as ITIL for standardised tasks and the development of IT product and IT service catalogues have already established themselves to the greatest extent possible. These clearly describe the IT services provided. In addition to the definition of the service to be provided, the clear description shall include the identification of disclaimers and conditions that must exist. Also part of the service description is a price that can be composed of fixed and variable parts. This simplification and bundling of the product portfolios should also reduce the administrative burden when ordering, activating, changing, terminating and, of course, invoicing. The description of the IT services and the associated development of an IT product catalogue is the basis for standardisation, whether the recipient is an external or internal customer (e.g. a business unit). One difficulty is the definition of IT products, i.e. the pooling of IT services and resources. An orientation towards the idea of cloud computing can help. The characteristics of cloud computing are the provision of standardised services in terms of performance and type of performance, results-orientated services, provision of performance to a wide range of service customers, scalability, transaction-based billing and high risk of IT service failure.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
Step-by-step Summary Copy Cofiles/data file to transport directory Normally /usr/sap/trans, if not —> AL11 -> DIR_TRANS Customise file owners and permissions chown adm chmod 664 In SAP system: STMS -> Import Overview -> Select Import Queue -> Additions -> Additional Jobs -> Attach Enter Transport Jobs ().
Therefore, make sure you have an account associated with the Administrators Group! To do this, go to Applications, right-click Central Management Console, and select Configure Access to the CMC tab: The CMC can be found under Applications.