SAP Basis Collaboration and management of (sub-)projects in the SAP Basis environment, if necessary also cross-departmentally - SAP Corner

Direkt zum Seiteninhalt
Collaboration and management of (sub-)projects in the SAP Basis environment, if necessary also cross-departmentally
SWELS Switch event trace on/off
SAP Basis consists of three layers: a database layer, an application layer and a presentation layer. The database layer manages all the data of the SAP system in a database located on the database server and administered by a database management system (DBMS). The database supplies the connected SAP applications with the required data, data tables or system control tables. It also receives and stores new information generated by the user.

A degree in computer science is usually a prerequisite and is now almost compulsory. Those who have been trained as IT specialists can take advantage of further training to become SAP Basis Administrators and thus position themselves particularly well on the job market. However, quite a few companies also offer to train employees to make them fit to work as SAP Basis Administrators.
Configuration as well as maintenance, upgrades and backup & recovery
The Technical Lead functions as the work package leader or sub-project manager within the SAP basis when the project is the focus of the SAP basis. The Technical Lead will become more important in the future as the SAP basis acts as a technology consultant and more projects and project activities are expected in the future. This role must be filled more and more often. Due to the increased demands, this role and the associated activities must be professionalised through training and further training.

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.

The transaction SPAM starts the insertion with the step CHECK_REQUIREMENTS [page 26].

Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page www.sap-corner.de you will find useful information on this topic.


I_FORCE_DELETE Boolean, X = Delete despite error messages I_NO_TRANSPORT Boolean, X = This change should not be transported to subsequent systems I_NO_AUTHORITY Boolean, X = Ignore Permission Checks Work in the source system In the source system, go to transaction SE37 and call the function block "RSAP_BIW_DISCONNECT" : The descriptions of the fields are as follows.
SAP Corner
Zurück zum Seiteninhalt