SAP Basis STMS_IMPORT Import queue

Direkt zum Seiteninhalt
STMS_IMPORT Import queue
SAP NetWeaver - maintenance and support
Basis administrators often have basic ABAP knowledge, for example, and ABAP developers know the basics of SAP Basis. Nevertheless, the two fields of activity are usually organizationally separated in the company.

Site Reliability Engineering(SRE) is the equivalent of SAP Basis in the Google world. Ben Treynor, who has been with Google since 2003 and is considered the godfather of SRE, describes SRE as "what happens when you give operations tasks to a software engineer".
What is SAP-BASIS?
The SAP Basis Plug-In is backward compatible and follows the release and maintenance strategy of the SAP R/3 Plug-In. SAP ships it together with the SAP R/3 Plug-In.

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.

"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.

Some useful tips about SAP basis can be found on www.sap-corner.de.

Since SPAM runs within the SAP system, you do not need to know the operating system to handle the transaction.

After that, these roles should be exported from the system (for example, to an Excel file) and then submitted to the supervisor so that he can decide whether the role assignment is appropriate or not.
SAP Corner
Zurück zum Seiteninhalt