Preparation of the migration to the SAP HANA database
SP02 Output controller: overview of spool requests
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.
Here, too, the requirements profile for SAP Basis experts has shifted: Database administration is simply part of the job today. The majority of SAP customers place the SAP HANA database in the hands of the Basis team for build and run operations.
SU25 Profile generator: upgrade and initial installation
To best adapt your SAP system to the internal and external requirements of your organization, further table-related customizing is required. Here, SAP offers the possibility of logging changes to critical tables through table logging.
In addition, the applications prepare the data in such a way that the user can visually capture it via the presentation layer. Conversely, the application server transfers all data that a user enters via the presentation layer to the underlying database.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
That is, depending on the target group, information must be created and communicated.
But with such a large number of parameters one quickly loses an overview of the influence of each parameter.