Determination of specific transactions with user assignment using SE16N
Recording customer infrastructure and consulting SAP® systems and operations
This is key to leveraging SAP's simplification plan. Since the release of SAP HANA, SAP has worked to simplify the system.
A BW system often plays a very central role in larger companies. Here the data from the various connected source systems are analysed and reported centrally. A previous customer of mine had a BW system, to which a total of over 20 other SAPP production systems were connected. With such a large and mostly living system landscape, it is normal that individual systems are dismantled from time to time. However, especially with large SAP landscapes, there are strict regulations regarding the permissions of technical RFC users. For this reason, the simple "right-click —> delete" of a source system in RSA1 will often not lead to the target, but rather to a failed permission check. With this blog post, I'll show you a workaround on how to clean a source system from a BW system using the RSAR_LOGICAL_SYSTEM_DELETE and RSAP_BIW_DISCONNECT function blocks.
SICK SAP Installation Check
In order for Fiori applications to be displayed according to the calling users, appropriate Fiori permissions must be maintained in the PFCG. There are several points to consider. This article discusses the permissions required to launch a Fiori application. In addition, a short explanation is given, how the displayed tiles can be configured in the Fiori launchpad via reels. To run Fiori applications from the launchpad and the permission queries defined in the OData services, the corresponding Fiori permission objects must also be maintained in the PFCG. Here the start permissions for the application's OData service in the backend system as well as permission objects are relevant for the business logic of the OData services used in the application. In general, it is important to know that if Fiori is implemented correctly, permissions must be maintained in the front-end server (call Launchpad, start the tile, etc.) as well as permissions in the back-end server (call the OData services from the backend). This article explains this in more detail.
For more information about the lowest support package level for SAP ABA and SAP Basis to install an SAP Basis plug-in, see basis-plug-in → SAP Plug-In → SAP Basis Plug-In → Releases on the SAP Service Marketplace. For more information about the lowest support package level for the corresponding SAP R/3 Plug-In, see basis-plug- in → SAP Plug-In → SAP R/3 Plug-In → SAP R/3 Plug-In Releases on the SAP Service Marketplace. This level depends on the release of SAP R/3 or SAP R/3 Enterprise.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
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.
The role of the SME thus corresponds to an expert role in the technology environment.