SAP Basis SM51 Application server instances

Direkt zum Seiteninhalt
SM51 Application server instances
Creation and implementation of the milieu according to the best SAP practices
Do you want to allow an employee access to exactly one view maintenance dialogue, but he should not be able to search for other care views in the SM30? This can be done easily with a parameter transaction. Learn how to create such a transaction step by step here. To create a parameter transaction, navigate to the SE93 first. Here you can create all types of transactions. The following dialogue will open: After pressing the "Create" button, a popup will open, on which you select the radio button "Transaction with parameters (parameter transaction)". In addition, type a short description as usual and confirm. The following dialogue will open: The transaction code must be specified here first. If you want to skip the entry dialogue when invoking the parameter transaction, and there is no way to open tables other than the one you want, make sure to select "Skip Entry Image". Furthermore, the GUI properties of the SM30 should be inherited so that the parameter transaction can be started with the same software. Configuration of the parameters In the lower part of the dialogue you will find a table ready for input. Here you can use the search help (F4).

If table logging is active in your system, you can specify which tables are to be logged in transaction SE13. For an active logging it is necessary to set the flag "Log data changes".
Consulting regarding the use of hardware, database as well as operating systems and their installation type (physical or virtual)
Examples of names are: SAP Cross-Application, SAP Innovation & Technology, SAP Services & Innovation, SAP Operations & Innovation or SAP Service Provider & Business Innovator. DESCRIPTION OF OWN PERFORMANCE AND SERVICE PORTFOLIO In order to be consulted by upstream or downstream entities, it is necessary to provide a detailed and understandable description of your service portfolio. This means that it can be explicitly stated in which cases the SAP basis needs to be contacted and involved in order to make the necessary decisions and not jeopardise a project or company success. In addition to the range of tasks covered by the SAP basis, it is also necessary to specify for which tasks and topics the SAP basis is not responsible. This recommendation is to be considered as universal and applies to all IT departments in order to clearly distinguish them and document the performance of their own IT organisation. INTERNAL MARKETING DESIGN AND ESTABLISH Building on the recommendation [A3], it is recommended to design and establish an internal marketing. The aim is to provide a transparent picture of the activities carried out in terms of the company's success and which are not visible to everyone.

Project successes should also be documented and circulated as success stories of the SAP basis or made available to the SAP basis stakeholders to highlight the importance of the SAP basis. These success stories can be shared from the grassroots or from the outside, for example. Examples include CIO communications or project reports. BENEFITS & CONSEQUENCES The added value of the implementation of the recommendations described above lies in the guaranteed operational stability and operational safety. In addition, a company and in particular an IT organisation with a strong SAP basis receives a competent and sustainable partner for SAP topics and technologies, who is always looking at the SAP picture in general. Furthermore, all business and IT departments are aware of the role and the scope of the SAP basis. This means that you can contact them as the right person in good time. There is a lower risk that certain areas may develop shadow IT related to SAP topics and technologies due to lack of transparency.

With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.

For his daily work he uses suitable tools (e.g. monitoring tools), in which he is trained and trained.

You can read more about assigning permissions to individual tables here.
SAP Corner
Zurück zum Seiteninhalt