Transaction Code Description
Post Installation Services
There are the following reasons that may lead to the termination of this step: TP_INTERFACE_FAILURE: Unable to call tp interface. TP_FAILURE: The tp programme could not be run. For more information, see the SLOG or ALOG log file. COMMAND_FILE_IMPORT_FAILURE: Unable to import the Object List to one or more Support Packages. The protocol of the Commandfile import contains the cause of the error. OBJECTS_LOCKED_? This step checks to see if there are any objects left in unreleased jobs that will be overwritten during the commit.
SAP Basis represents the cornerstone of the SAP system, i.e. the foundation without which the system cannot function. Furthermore, it includes some administration tools and middleware programs. These programs can be used with the help of SAP Basis independently of the operating system and database used.
SM19 Security Audit
ITIL stands for The IT Infrastructure Library. ITIL is a summary of "best practices" rules for professional implementation of IT service management. ITIL has established itself as an international standard in the area of IT business processes. The ITIL set of rules describes the processes, the organizational structure and the tools required for IT infrastructure. ITIL is based on the economic added value that IT operations provide for the company. itSMF Deutschland eV has further developed and improved these standards, and at the same time operates a portal for exchanging knowledge and experience.
Especially in larger companies, which also have multiple locations in different countries, it is often necessary to grant different employees the same permissions for different levels of organisation, such as accounting circles. In order to make maintenance and maintenance of the system easy in such a situation, it is useful to set the inheritance principle for SAP permissions. How does SAP Permissions Inheritance work? An inheritance is always about a master object passing certain properties to a derived (sub) object. Therefore, these properties do not need to be maintained several times. Also, changes to the master object are passed directly to the derived objects. This allows easier maintenance and drastically minimises the error rate. In the case of SAP Permission Inheritance, the required permissions are bundled in a Upper or Master role. Only the organisational levels have to be maintained in the roles derived from them. The permissions are automatically pulled from the master role. Create Inheritance for SAP Permissions The following shows how to create and use inheritances for SAP permissions. This requires only two steps: Creating a master role and defining derived roles. Step 1: Create a master role Inheritance always requires a parent role, because all properties are inherited from it. If this role, in which all shared permissions are bundled, is missing, the first step is to create this master role. To do this, open the PFCG transaction and enter the desired name of the master role in the Name field. It is possible to identify master and derived roles by using naming conventions. The "Single Role" button will then be used to create the desired role. In the following example I create the master role "findepartment_r".
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
Encryption costs performance, so it is not used by default.
Some useful tips about SAP basis can be found on www.sap-corner.de.
These web applications can be found by various search engines on the Internet.