SAP Basis SQ01 Maintain SAP Query

Direkt zum Seiteninhalt
SQ01 Maintain SAP Query
Analyses Proactive measures for optimization
Remove weak password hashes from the system: Only updating the profile parameter does not provide you with the necessary security. There are still many weak hash values in your database that can be used to attack your system. These must be completely removed from the database. To do this, use the report CLEANUP_PASSWORD_HASH_VALUES. To do this, call the transaction SA38 and enter the name of the report in the input field. Run or F8 executes the programme and cleans your database Report CLEANUP_PASSWORD_HASH_VALUES This programme removes the outdated hash values across all clients. Have you already experienced this attack method or any other comments on this topic? Share your experiences with us in the form of a comment under this article.

Since innovations through IoT (Internet of Things) or big data scenarios not only affect the SAP basis, but also highlight products and services for customers of their own company, the role of the SAP basis in relation to these scenarios and services must be clearly defined. In general, the SAP basis sees its responsibility here in the connectivity to the corporate network or the enterprise systems, which lie in the responsibility of the SAP basis. The support of the applications, based on the technologies as well as the associated services, is the responsibility of the respective department that offers this service. A SAP-based support service must be agreed and regulated during the conception.
Practitioners for practitioners
Basis includes a client/server architecture and configuration, a relational database management system (DBMS), and a graphical user interface (GUI). In addition to interfaces between system elements, Basis includes a development environment for R/3 applications, a data directory, and user and system administration and monitoring tools.

If you have modified SAP objects, you have to match these objects during playback. The transaction SPDD matches Dictionary objects, and the transaction SPAU Repository objects. Prerequisites SPAM prompts you for modification matching. How to Stop Inserting the Support Package (F12). SPAM will resume processing at RUN_SPDD or RUN_SPAU steps. To enable your developers to perform the modification synchronisation, create an order in the Transport Organiser [Extern] and under this task for the developers. Ask developers to perform the modification matching for their objects. Synchronisation of Dictionary Objects (SPDD): The developers can view the list of affected objects with the addition of Synchronise Modifications in the input image of the transaction SPAM. Synchronisation of Repository Objects (SPAU): Developers must call the transaction SPAU and then match it. Once the match is complete, developers must share the tasks and inform you. The comparison can be done in any client. Call SPAM. Select Insert Support Package Queue. You will be prompted again to perform the modification sync. Since it has already been completed, ignore the hint and select Next. SPAM completes the processing and returns the status.

For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.

Furthermore, the output should be limited to the roles only.

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.

Each Support Package is valid for one release level (but for all databases and operating systems) and requires a precisely defined number of predecessors.
Zurück zum Seiteninhalt