SAP Basis How to create a parameter transaction for the SM30 - SAP Basis

Direkt zum Seiteninhalt
How to create a parameter transaction for the SM30
MaxDB
The entry screen gives a brief overview of the status of the last queued. In case of incomplete support packages, the last (aborted) step of the SPAM will be displayed. System: Check the correct function of the transport tools using Tool Transport Tool. Make sure there is enough space (the size of the OCS files multiplied by 2) in the transport directory (see the R/3 profile parameter DIR_TRANS with the AL11 transaction or the SE38 transaction and the report RSPARAM). Make sure that there is enough space, especially in the subdirectories trans/EPS/in and trans/data. Use the latest SPAM update. Verify that the SPAM update offered in the SAPNet - R/3 frontend or the SAPNet - Web Frontend is newer than the one available in your system. You can see the version of the SPAM update available in your system in the title bar of the SPAM image. We recommend that you always run the latest SPAM update first [page 14] to avoid problems when playing. The insertion of a SPAM update is analogous to the insertion of support packages. There must be no incomplete support packages in your system. To do this, under Folder in the SPAM, select Aborted Support. Packages and select View. Support packages should not be displayed. The status light should be green. If not, view the detailed status and log information for all support packages in the system. Select Jump Status or Jump Log. Load Activities Support Package [page 15] Define Queue [page 17] Insert Queue [page 20] If necessary: Sync Modifications [Page 22] Verify Protocols [Page 23] Confirm Queue [Page 24].

As a member of the SAP Basis specialist team, your responsibilities will include the design, operation, administration, support and installation of an extensive SAP system landscape with over 50 systems for 17 universities and 2 institutions in Lower Saxony. Furthermore, you will monitor the SAP system landscape as well as its interfaces to external systems and carry out measures within the scope of software lifecycle management (e.g. note maintenance, support stacks, release upgrades) and change management (e.g. hardware migration, transport system and documentation). As part of the SAP Basis team, you will be the contact person for organizational and technical questions of the universities and in 3rd-level support for user inquiries.
Good communication skills (foreign language skills)
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).

You can view them using the RSPUTPRT report or the AL11 transaction. AUTO_MOD_SPAU This step checks whether modifications can be adjusted automatically. RUN_SPAU_? This step prompts you to customise your modifications to Repository objects by calling the transaction SPAU. EPILOGUE In this step the insertion is completed. Checks whether the queue is fully processed. In this case, transport buffer entries should no longer exist for the Queue. There are the following reasons that may lead to the termination of this step: TP_INTERFACE_FAILURE: Unable to call tp interface. TP_FAILURE: The tp programme could not be run. For more information, see the SLOG or ALOG log file.

"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.

CANNOT_RESET_FCS_FLAG: If there is an FCS Support Package (FFD) in the queue, the system will be marked as being at the generally available release level after this support package is inserted.

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.
SAP BASIS
Zurück zum Seiteninhalt