How to create a parameter transaction for the SM30
Is that all there is to know about SAP Basis?
Have you ever wondered what there is actually a tab personalisation for role maintenance in the PFCG or for user data maintenance in the SU01? I will answer this question for you in this blog post. What do we need the Personalisation tab for? This tab gives you access to the central repository for personalisation data. The purpose of this repository is to create a storage facility for user- and role-specific data without the need to create additional database tables. This data should then be taken into account in all manipulations of users and roles. The functionality initially includes a generic repository for user- and role-specific data and centralised access to that data by user and role maintenance. It also provides the ability to connect existing tables with user-specific data to the central access via a defined interface. To store personalisation data in the central repository, a key must be assigned to the data: This is done via the registration transaction PERSREG. The personalisation data that you create is stored in the generic drop table. Access to it is provided by the class methods of the CL_PERS_ADMIN class. Different levels of personalisation The data can be stored either to the user, to roles or to the system. A user can then read all data assigned to him (via role or his own settings) at once.
How does a blockchain build consensus? Once you decide to send a payment to someone, you must use the Private Key to "sign" it (in German: signature). This means nothing other than that you specify another public address to which you want to send the money and confirm this transaction with your own private key. You don't have a central authority to send the information to, you're going to spread the information to all the other Miners around you. The miners then forward this information to other miners, who in turn do the same. This exponential wave of information reaches the entire network of the distributed community within a few milliseconds. Every time a miner receives a transaction, it checks that the transaction is actually correct. It checks which private key has signed, which public address the transaction should go to and whether the sender has enough "coins" for this transaction. What are consensus mechanisms? Any miner that solves a transaction through complex mathematical calculations is rewarded by the sender with a "fee" (transaction fee). How will it be decided which miner will receive the transaction fee? Because only one can get this reward. Also, what happens when you try a double spending by sending one transaction to one miner and then another transaction with the same money to another one millisecond later? These two could not yet exchange and thus information would be different in the network.
This step prompts you to customise your modifications to Repository objects by calling the transaction SPAU. EPILOGUE In this step the insertion is completed. Among other things, it is checked that the queue has been fully processed. SPAM: Troubleshooting The SAP Patch Manager performs several steps during the recording. If errors occur, SPAM will interrupt the playback to ensure consistency of the recording. After fixing the error, you can resume playback. When you cancel, a dialogue box appears with the information on which step and why the editing failed. This dialogue box is also available when you select Jump Status and then Queue, Support Package or SPAM Update (View Support Package Status (page 29)). Depending on the processing step in which the error occurred, the dialogue box will provide you with additional specific assistance to correct the error. You may also need to reset the status of a Support Package [page 36]. If you are having problems downloading Support Packages from the SAPNet - R/3 frontend, please see Note 34376. If you are having problems working with SPAM, read the note 17381This note gives you an overview of known problems and their solutions. For a list of the most important information about Online Correction Support (OCS), see Note 97620, which is updated regularly. If you are unable to resolve your issue with the information provided or with the following information, then record a problem message in the SAPNet - R/3 frontend with the information from the error dialogue box and send it to the BC-UPG-OCS topic group. Note 97660 when capturing the problem message. See also: Generation Error [Page 30].
Instead of letting the power consumer determine each parameter individually, the SAP basis can now create meaningful bundles, such as the power server with a lot of processor power, memory and disk space, and the light server in a simpler setup. Each bundle has its own price, which requires preparation and consideration. The principle of consistently aligning IT services with repeatable standards is thus directly linked to the standardisation of processes and technical specifications. Standardised products can only be offered if process processes are standardised. Likewise, these can only be offered as simple and comprehensible product bundles if technical standards are established.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
In practice, it means taking responsibility for the maintenance environment of the systems, their cooperation, updating, solving user problems and efficiency issues (concerning the network, databases or operating systems), backup copies and architecture.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
A standardisation strategy can then be developed, defined and implemented.