SAP Basis SWI1 Work item selection - SAP Basis

Direkt zum Seiteninhalt
SWI1 Work item selection
Training - Administration SAP HANA
In order to ensure the stability of the systems and to reduce the risk through proprietary developments, release and patch management must be implemented. Standardised procedures can help to introduce proprietary developments, such as test strategies or service level agreements (SLAs). It is also important to align the productivity setting of customer applications with the maintenance windows and RTO (Recovery-Time-Objective).

With simple job programming, you can start in clear environments with few dependencies. If the number of jobs and the complexity increases, an automatic job control is a good choice. Honico Batchman is such a solution, a 100% SAP integrated AddOn, which is quickly and easily installed via normal transports. The advantage here is that no additional infrastructure is required; instead, the existing SAP system landscape is used for the entire control and execution without incurring a loss in performance. This also ensures full audit and operational security (compliance). Since pure SAP systems are rather the exception, non-SAP systems can also be controlled and monitored. As a third option, high-end solutions are available that additionally monitor the infrastructure and legacy. Widely used products in this segment are UC4 and Arvato Streamworks. These three solution options differ significantly in terms of price and scope of services. IT departments in companies must therefore evaluate which solution is best suited to their own requirements.
Synonym(s): SAP Basis Consulting, Consulting
The Open Innovation Model approach comes into play in the idea creation, evaluation and selection phase, which can also be divided into the three eponymous sub-steps. In a closed innovation model, innovation is created only from the company itself. The Open Innovation Model allows for different sources of idea generation. So it is about opening up the innovation process, as shown in Figure 2, which was presented earlier. The figure shows the company boundaries through the dotted lines and the ideas that can be generated both within and outside the company. The Open Innovation approach can be divided into the three core processes of the Outside-In process, Inside-Out process and Coupled process. The Outside-In process involves knowledge from external sources in idea generation. This happens, for example, through cooperation with companies, suppliers or even customers. The inside-out process supports development, commercialisation, and deployment to markets outside of the organisation itself if there is little chance of success in implementing the idea internally. The Coupled process links the two strategies mentioned above. This is an attempt to generate cooperation successes through joint development and subsequent commercialisation in networks. In terms of the SAP basis, the Outside-In process plays an essential role in generating ideas within the framework of the Open Innovation approach.

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 administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.

There are the following reasons that may lead to the termination of this step: TP_INTERFACE_FAILURE: Unable to call tp interface.

They are then re-created with a continuous numbering in order to distinguish them later.
Zurück zum Seiteninhalt