What do the next ten years hold in store?
For existing solutions, it is necessary to assess to what extent the solution is customised. A modification is the more serious the more time-consuming the maintenance is, including testing, e.g. in the case of upgrades. The fewer customer specifications are available, the more suitable a system or application is for external operation by a service form to be chosen.
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".
Planning ahead: Ideally, your SAP system administrator should make the necessary adjustments to your system landscape before end users are affected. This requires careful planning and anticipation of long-term trends.
You can call the SPAM transaction in one of the following ways: Select SAP menu Tools Maintenance Patches. Enter the transaction code SPAM. Features The SAP Patch Manager provides the following features: Loading Support Packages: Requested support packages can be loaded into your system from SAPNet - Web Frontend, SAPNet - R/3 Frontend, or Collection CDs. Inserting Support Packages: Resetting When SPAM inserts a support package into your system, a fixed sequence of steps is followed. If the Support Package implementation stops, you can resume processing at a later time. The operation will resume where it was cancelled.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
Both ABAP and Java stack can be monitored from one platform.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
For more information about the lowest support package level for the corresponding SAP R/3 plug-in, see the SAP Service Marketplace.