SWU2 Transactional RFC
SAP NetWeaver - maintenance and support
In the SAP Business Objects environment, you can extend the control of permissions using the CMC tab configuration. The tab configuration allows you to easily show or hide specific tabs for users or groups. Enable CMC Tab Configuration By default, the CMC Tab Configuration feature is set to "Don't Limit" and is disabled. For you to be able to use the tab configuration at all, you will need to enable it for now. Note: If you enable the tab configuration, all users that are not under the default Administrators group will not see tabs for the time being. This is because access is denied by default through the CMC tab configuration. Therefore, once enabled, you must maintain tabs for all existing groups. Therefore, make sure you have an account associated with the Administrators Group! To do this, go to Applications, right-click Central Management Console, and select Configure Access to the CMC tab: The CMC can be found under Applications. Now enable the configuration by selecting the Restrict option. Use Restrictions to enable the option. Hide/show tabs If you are now logging in with a user that is not in the default Administrators group, you will not see applications/tabs on the CMC home page. Initially no applications/tabs are visible To display the desired tabs for the groups again, switch to users and groups with your administrator account, right-click on the desired group, and select CMC tab configuration. Enter the tab configuration. In the dialogue that appears, you see that all tabs are denied access by default.
In the beginning, in our company the installation and management of the systems were dealt with by the functional consultants/consultants of the respective systems. The CRM consultant was responsible for the SAP CRM system, the SRM consultant for the SAP SRM, etc.
SAP HANA® DB
Regular maintenance tasks or the standard procedures must be described and defined to build checklists based on them and to control compliance with this standard. The SAPSolution-Manager can also support this as a tool of SAP e.g. through the Guided Procedures. In this context, it is also necessary to document the functionality of an underlying application and thereby determine what testing and monitoring activities are necessary. This is a reconciliation process between the SAP basis, other IT departments and, if necessary, the business areas concerned. The defined standard and the system's IST situation must be fully documented and regularly checked for compliance. This can be done through automated monitoring, validation using tools such as SAP-LVM (Landscape Virtualisation Management) or SAP Solution Manager, as well as manual checklists. Only the regular review of the standards guarantees their compliance. It can also support the regular use of SAP services such as Go-live Checks or Early Watch. Examples of how to standardise procedures are listed here: ・ Naming of system instances and logical hosts, or at least one central registry in a directory service, or LVM or SAP customer portal ・ Centrally starting and stopping systems, such as via the LVM ・ Categorising SAP instances by T-shirt size to define profile standards and cost them.
If you now want to change the permission data, you will be asked for values for the appropriate organisation levels. First enter a tilde (~) and define the value later in the derived roles. Maintain the permissions you want and then generate the master role. Adding the organisational level to the master role Step 2: Define derived roles Create derived roles Assign the master role After you have created the master role, it is the derived roles that are in the process. To do this, re-enter a suitable role name via the PFCG. In our example, it is called "findepartment_d01". For a better overview, it is usually useful to name and number the derivatives after the master roles. You can also define the roles according to a different scheme. After you have created the role, you must then enter the master role in the Derive from Role field in the Description tab. Confirm the Auto Enquiries. Customise the Organisation Levels Now go to the "Menu" tab. There you can see that the data from the master role was automatically copied. Since the role has not yet been generated, the Permissions tab is currently highlighted in red. Therefore, call "Change Permissions Data". The first call should automatically open a dialogue to maintain the organisational levels, as they are still empty. If this is not the case, or if you would like to adjust the organisational levels again in a later case, you can also access them via the button Ordende (see screenshot). If everything worked well, you can now see that the permissions were also automatically taken from the master role. If you generate the role, the permission tab will also appear green. Congratulations, you have successfully created a derived role! Repeat step 2 with the additional derivatives to adjust the organisation levels accordingly.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
See also: Generation Error [Page 30].
In this regard, SAP Basis refers to all transactions, programs and objects that control the functions of the overall system.