Client Copy / Export
Typical tools in the SAP Basis environment include:
All topics are relevant, which may also be of interest to a customer. Ideally, you get a balanced communication structure in the communication triangle between marketing, the target group and your own employees. Internal communication is an important aspect for the SAP basis. It is primarily a matter of passing on or communicating your own services, IT products and positioning to your employees. STEP 10: PLANNING The planning provides a translation of the previously agreed definitions into concrete measures. A description of the measure shall be provided. The measures can now be scheduled and included in a cost overview. Above all, it is important to plan realistically and to consider dependencies. This step, too, is of great interest to the SAP basis and is necessary to translate the previously agreed specifications into a concrete marketing concept of the SAP basis.
Ten years ago, there wasn't much more for SAP Basis experts than SAP Solution Manager. And most Basis administrators only used it at all because SAP virtually forced them to use SolMan to download updates.
Hiring Requirements
A well-cared-for emergency user concept enables the audit-proof allocation of extended permissions in combination with the assurance of daily operations in your company. This article first addresses the fundamental issues that require an emergency user approach. It then briefly explains how such a concept works in general and how we implement it. An Emergency User is normally used when tasks are temporarily taken over outside the initial field of activity. I described the different scenarios of when such a user can be used and how to deal with them in this blog post for you. Why is an emergency user approach important? There are several scenarios in which the use of an emergency user with extended rights is useful: In urgent cases, it is often necessary to be able to quickly make changes to the system that are outside the user's actual field of activity. A key user who has the necessary permissions is on vacation and needs a representation. The same user suffers short-term illness and his/her representative must take over his/her duties to ensure the operation. We recommend developing a concept for the short-term allocation of the additional permissions. This will ensure the implementation of the above scenarios. How does an emergency user approach work? An emergency user concept in SAP works fundamentally via a temporary assignment of additional rights to a specific user. After the tasks have been completed, the user is deprived of the rights. The tasks performed with the extended permissions are logged and can then be evaluated by an auditor. However, there are a few things to keep in mind: A process for granting special rights should be defined. It must be specified which users can get special rights. The time period for which users can request an emergency user should be limited.
Due to the technology diversity, including in the SAP product portfolio, the support by a single silo unit SAP basis is almost impossible. Likewise, there are many activities that are located for historical reasons in the SAP basis and in parallel in the non-SAP area. In this respect, the separation between SAP and Non-SAP must be examined and, if possible, eliminated by standardisation, integration and centralisation. For example, the issue of output management can be set up in a team that has knowledge in the SAP printing area as well as in the non-SAP printing area and has contact points in the SAP basis. From the SAP basis, tools must be made available to the non-SAP areas to support them in their work in the SAP environment.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
EPILOGUE In this step the insertion is completed.
As of SAP Basis Plug-In 2005.1, the release levels of the two plug-ins no longer need to correspond.