STMS Transport Management System
Continuous improvement of system availability and performance
The decision to outsource a task or service should be taken not only in terms of cost, but also by assessing the competitive differentiation and strategic importance. Characteristics for describing the costs are the specificity of the task and the embossing by unit cost degression, i.e. decreasing costs with increasing number of tasks or performance. Of strategic importance are, in particular, those tasks and services which are difficult to imitate by competing companies. Figure 4 compares the strategic importance and cost advantages in order to arrive at fundamentally valid statements regarding the usefulness of outsourcing for certain IT tasks and services. In addition to this, as already discussed by Recommendation [A2], it is then worthwhile to establish a catalogue of criteria for evaluating and looking in detail at certain characteristics of the application or services. An exemplary catalogue of criteria can be found in chapter 9.6 of the Master thesis. Figure 4: IT Outsourcing Decision Matrix THE DECISION TO OUTSOURCE A TASK OR PERFORMANCE SHOULD BE MADE NOT ONLY IN TERMS OF COSTS BUT ALSO BY ASSESSING COMPETITION DIFFERENTIATION AND STRATEGIC IMPORTANCE.
You trust in the availability of your SAP systems. Our specialists are happy to support your team in all phases of your SAP projects. We support your SAP HANA systems. And stand by your side during a platform or release upgrade.
GUIDE TO THE DEVELOPMENT OF A MARKETING CONCEPT
To influence the ABAP/Dynro generation, select Additions in the entry screen of the SPAM. Function Menu Path Turn Generation on or off Settings Ignore generation errors during the commit. Ignore error in SPAM steps If an error is detected in one step, the transaction SPAM stops processing until the error is resolved. You can always check with Status to see in which step and for what reason the abortion took place. Types of errors There are the following types of error messages: Security checks of the transaction SPAM A typical example is the OBJECTS_LOCKED_? step. The SPAM transaction interrupts processing when objects are still locked in jobs to be overwritten by the queue. Error messages of the programmes tp and R3trans The cause of error can always be found in the corresponding transport log. A typical example is the TEST_IMPORT step. This checks to see if there are unconfirmed repairs to objects overwritten by the queue. The affected objects are listed in the Testimport log. Incorrect setup of the Change and Transport System Common errors are the lack of appropriate rights to the files of the Change and Transport System or the use of old programme versions of tp or R3trans. Verify that the transport tools are working correctly with Transp Tool. Check Tool. A typical example is the DISASSEMBLE step. If adm does not have write permissions for the /usr/sap/trans/data (UNIX) directory, SPAM will cancel DISASSEMBLE with CANNOT_DISASSEMBLE_R_DATA_FILE. The transaction SPAM requires that the Change and Transport System [External] is set up correctly. For more information on known problems, see Notes 97630 and 97620.
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.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
This suite consists of various modules for creating role concepts, managing permissions including a permission concept, and also enables the implementation of an emergency user concept.
However, quite a few companies also offer to train employees to make them fit to work as SAP Basis Administrators.