Once the UPL is activated, you can access the usage data as follows: Solution Manager: BW Query 0SM_CCL_UPL_MONTH (other predefined Querys available) Managed System: Report /SDF/SHOW_UPL Based on the UPL's data collection, you can now use additional functionalities of the CCLM to depick, for example, proprietary developments that are unused for a long time. Do you know the UPL of SAP and already use it to gain more information about its existing system landscape?
In the age of digitisation, the wheel need not be reinvented. Certain functions are consumed or used by platforms only, without fully retaining the necessary infrastructure. In order to participate in this compared to competitors, it is necessary to introduce these technologies, to use them and to learn about their possibilities. Examples include the use of cloud services or applications in the IoT and big data environment.
SCC7 Client import - postprocessing
To best adapt your SAP system to the internal and external requirements of your organization, further table-related customizing is required. Here, SAP offers the possibility of logging changes to critical tables through table logging.
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.
In the area of SAP Basis Operations, we handle all technical tasks for our customers that arise during the installation, operation and maintenance of SAP systems.
The differences between the authorization concept for ERP systems and the authorization concept for NetWeaver BI are taught.