Training - Administration SAP HANA
OUR SOLUTIONS
Due to the technology diversity, including in the SAP product portfolio, the support by a single silo unit SAP basis is almost impossible. Likewise, there are many activities that are located for historical reasons in the SAP basis and in parallel in the non-SAP area. In this respect, the separation between SAP and Non-SAP must be examined and, if possible, eliminated by standardisation, integration and centralisation. For example, the issue of output management can be set up in a team that has knowledge in the SAP printing area as well as in the non-SAP printing area and has contact points in the SAP basis. From the SAP basis, tools must be made available to the non-SAP areas to support them in their work in the SAP environment.
SAP Basis, which means system administration and platform basis of SAP systems - quasi the operating level behind the SAP applications in the company. NEXUS / ENTERPRISE SOLUTIONS is now focusing more strongly on this business area and is strengthening its service portfolio in the basic operation of SAP Basis services (Application Management Services / ongoing support) with optional extensions and project services of SAP Basis operation, for example, in the course of migrations.
High Availability ( HA/DR ) concepts
Inheritance Hierarchy with Master Roles and Associated Roles If you have created multiple derived roles, a simple overview of all "related" roles can be convenient. To do this, call any derived role, or the master role, and then click the "Inheritance Hierarchy" button. You will now get a detailed overview of which roles are assigned to which master role.
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.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
Furthermore, the know-how, which aspects should be dealt with in an authorisation concept and how the corresponding processes can look practical and at the same time audit-proof is often lacking.
If you are using this Emergency User Concept and following these steps, you can ensure: Each user on the production system retains his or her original necessary rights.