Target Audience
Practitioners for practitioners
The presentation layer is based on the software components, collectively called "SAP GUI". This includes several possible implementation variants: for example, SAP GUI for HTML (Web GUI) and Web Dynpro for ABAP (WDA). Since the respective GUI depends entirely on the concrete application, the presentation layer looks very different in practice.
However, the tasks also include strategic and planning aspects. For example, administrators define requirements and standards, select and control upgrades or extensions, implement monitoring processes, and take care of necessary backups and emergency management.
Related terms
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.
On www.sap-corner.de you will also find useful information about SAP basis.
SAP's client concept enables a SAP system to be split into several logical sub-systems - clients. These subsystems can be used independently and in isolation as separate systems. But how should non-client transactions be treated? How can you prevent one client from accessing the other and why should you want to prevent that? In this blog post, I will answer these questions and discuss some negative examples. Why is it important to consider independent transactions separately? Imagine that every one of your employees is allowed to create or change a client in the production system, or worse, both. Creating and modifying a client in the production system is authorised and documented - you wonder what could possibly go wrong? The risk in this case is a loss of integrity of system and data, loss of confidentiality: With each new client, Superuser SAP* lives up to its comprehensive, cross-client rights and the assigned standard password.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
itSMF Deutschland eV has further developed and improved these standards, and at the same time operates a portal for exchanging knowledge and experience.
secinfo and reginfo Request generator Option 1: Restrictive procedure In the case of the restrictive solution approach, only in-system programmes are allowed.
The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.