Cooperation with internal support
Migration to SAP HANA
In the past, when we deployed SAP environments, we first had to work out detailed sizing and architecture and pass this on to the procurement team, who then ordered the systems and installed them in the data center. From there, it went on to the network team, the storage team, the operating system team, and the database team. So it was not uncommon for three to six months to pass between the architecture design and the installation of a new SAP system.
Another important example is the reading permission for TemSe objects. The temporary files are often forgotten, because it is often not considered that cached (strictly) sensitive data, which is intended for only one user (owner), can be viewed by another user without permission - and across clients. The examples mentioned show us how important it is to carefully assign permissions for client-independent transactions. Download Transaction tables The transactions that enable the examples above, including certain expressions of the associated permission objects and our recommendations for them, can be found in the file "Critical cross-client permissions" for download. Other client-independent transactions are located in the Cross Clients TCODES file. The criticality of these transactions should be assessed according to the context. I recommend always being careful and keeping these transactions in mind.
SM66 Work processes of all instances
The Advanced Memory thus contains mainly user contexts of different work processes, if these cannot be loaded completely into the roll area. Since the storage area is accessible for all work processes, the work processes can also access external user contexts that lie here. In addition, the Advanced Memory contains a global area where data can be stored independently of user contexts. The extended memory size is determined by the values of em/initial_size_MB and em/global_area_MB. The first parameter determines the size of the storage area in which user contexts can be stored, and the second determines the size of the global area. Parameters for Private Storage Last but not least, there is the private storage, which is only used when the user context of a work process has used up all the other storage areas available to it, i.e. its share of the extended memory and its rolling area. In this case, the workprocess goes into PRIV mode. A workprocess in private mode is bound to its current user context and will not become free for other tasks until the current request is completed. If it has used up all the private memory allocated to it, the workprocess will then be restarted and the memory released. This behaviour is controlled with the abap/heaplimit parameter. At times, the user context may exceed the value of abap/heaplimit. The parameters abap/heap_area_total, abap/heap_area_dia and abap/heap_area_nondia define an upper limit for private storage. The abap/heap_area_total parameter defines how much private storage all workprocesses can use in total. The parameters abap/heap_area_dia and abap/heap_area_nondia, on the other hand, determine how much private storage a single (non-)dialogue workprocess can use.
As a user of the group, you cannot see tabs either. Now select the applications / tabs to which the group should be accessed (with CTRL you can select several) and select the Grant button. Note: Select the Grant drop-down menu using the button and not the drop-down menu! Use the drop-down menu to determine if and how far users of the group you are currently editing can make CMC tab configurations to other groups / users! Select Grant for the desired tabs. If you still do not see any applications/tabs, it is because the group/user lacks the generic display right at the top level of the respective tab. To do this, go to the desired tab (in the example is the universe), select Manage —> Top-Level Security —> All Universes (the last point differs depending on the tab). Confirm the hint that appears and assign at least the following right for the groups you want: General —> General —> Objects View. Once this right is granted, the tab will also appear on the CMC home page. You can then see the tabs on the CMC home page.
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
This can be an internal administrator, or can be handed over to external service providers.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
Internal communication is an important aspect for the SAP basis.