Migration from a change of operating system, homogeneous/heterogeneous database
What has changed in the past decade and what can we expect in the coming decade? How will they affect the requirements profile of SAP Basis experts and how can they adapt to them?
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".
In order to reduce the variety of different system variations and the related variety of routine tasks, it is necessary to reduce the number of customer specifications. In particular, the implementation, set-up and configuration of the systems and security concepts must be harmonised or returned to the SAP standard. To this end, it is necessary to establish, in cooperation with the relevant IT departments, a standard for, for example, operating systems and databases within the limits set by the product.
Tasks
SAP Basis consultants are experts in consulting. The job of an SAP Basis consultant has many areas of responsibility such as:
There is an RFC error. CANNOT_ADD_PATCH_TO_BUFFER: A support package could not be included in the transport buffer. For more information, see the log file in the /usr/sap/trans/log (UNIX) directory. CANNOT_MODIFY_BUFFER: An attempt was made to modify the transport buffer without success. TEST_IMPORT This step checks whether there are still objects in unshared tasks that are overwritten during the commit. The log of the test import shows the cause of the error. For more information, see Note 42379. IMPORT_OBJECT_LIST In this step, the object lists for the support packages in the queue are fed into the system.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
As an alternative, one can directly use the workload monitor in the transaction code ST03N.
As a result, the know-how is often lacking and it is quickly taken to the next search engine, where long and partially incomplete forum entries make finding the right approach even more difficult.