SAP Basis SWUD Workflow Diagnosis

Direkt zum Seiteninhalt
SWUD Workflow Diagnosis
INCENTIVES TO CREATE NEW ROLES
SAP Basis administrators still spend much of their time reviewing their systems or doing project work such as new installations. With the transition to more automated, container-based environments that span multiple clouds, the role of the administrator will also need to be redefined and root cause analysis will take on a much higher profile.

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.
SWEQADM Administration of the event queue
The implementation of a cross-sectional function will promote and safeguard the operation of the SAP systems that form the backbone of the company. By coordinating the SAP basis with other IT departments, the optimisation is always done in the overall context of the company or the IT organisation. Eliminating the separation of SAP and non-SAP topics in areas where it is considered useful will lead to expert groups and synergy effects through centralisation.

SAP HANA has been one of the major topics in the SAP environment for the last few years. Many customers are currently faced with the question of whether or not to migrate your SAP system. In addition to the actual changeover itself, there are many other topics on which you should have already informed yourself in advance, as these influence the success of SAP HANA in your company. What do you already know about SAP HANA? I would like to encourage you to think about security in the following article. If you would like to learn about the architecture of HANA, I recommend a contribution from our colleagues at erlebe Software. SAP HANA Scenario But why are we even talking about HANA Security? Why is it so important to consider new security strategies with the new technology? With HANA it is possible to analyse data quickly. BW scenarios primarily benefit from the in-memory database (IMDB) used, as speed advantages in data access are particularly positive. Compared to a classic ERP / R3 scenario, the normal DB is replaced by HANA. The desired speed advantages result. However, migration is expected to be required for the changeover. This is caused by customer-specific developments in the system. HANA is not a further development of SAP ERP, HANA is the next stage of an ERP system. It is well known that an ERP system contains the capital of the companies. Therefore a new HANA system like all other ERP systems is also interesting for attackers. On the one hand, such a system contains the critical business data that are available for espionage. In addition, most business processes are mapped in such a system and offer an attack surface for sabotage. In addition, users do not initially know the new technology well. This also applies to administrators in the area of a new technology. Attackers quickly gain a dangerous leap of knowledge over these user groups. SAP HANA has a lot of new features, although many existing ones are used by SAP ERP, so there is a risk here.

"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.

This requires close collaboration between the department and IT, as later adaptations or additional systems will extend the implementation and exceed the budget.

This ensures that additional support packages can be used in the future.
SAP Corner
Zurück zum Seiteninhalt