Objectives of the training SAP HANA - Installation and Administration:
Presentation layer (graphical user interface)
Meanwhile, there are other ways to build consensus. But, for the most part, the following three options have proven effective as a consensus mechanism: 1) Proof of Work 2) Proof of Stake 3) Proof of Importance The differences are presented in another blog post. How do blocks form in a blockchain? Each block will build irrevocably on an older block. If you were to remove the block, you would also have to remove all blocks above it, which would destroy the entire chain of blocks. Because each new block also contains information from its predecessor block. This is very important for understanding the immutability of a blockchain. If you were to manipulate a block afterwards, you would have to adjust all the blocks that follow. The effort would be so infinitely large and expensive that such a manipulation can practically not be implemented. You can think of it as this. A blockchain arises from the cryptographically linked blocks (puzzles) full of transactions (puzzle pieces) and therefore cannot be changed without destroying the entire blockchain. For this reason, a blockchain is seen as an immutable transaction history agreed upon by a decentralised community. A blockchain is programmed to work with each miner on the longest part of the blockchain, as this is obviously the chain in which most of the work has been invested.
Only one transaction code can be entered here, otherwise a single role would always be searched, which includes all transactions searched for and is assigned to the respective user. However, since the transactions can also be assigned to the user via different roles, this would not be useful. If you use the above Input variants are also only considered transactions that have been maintained in the role menu. If it is not certain whether the transaction was entered in the menu or in the S_TCODE privilege object of the role, up to four transactions can also be checked by searching through the S_TCODE permission object. Important is the attention and appropriate use of the AND/OR relationship. After the query is executed, the roles that contain the requested transaction and are associated with the user are now displayed. If you use the search through the S_TCODE permission object, the following result page appears. When looking at the result, in addition to limiting the number of transactions that can be entered, another drawback of this variant becomes apparent: Although both associated roles are displayed, at first glance it is not possible to see which transaction is contained in which role. To do this, the roles would have to be considered individually. If more transactions with user assignment are to be identified at the same time and the role assignment is to be seen directly, the use of the transaction SE16N is recommended.
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.
Hardware Sizing
A secure SAP system does not only include a good role concept. It is also necessary to check whether a user should (still) have a specific role. Regular verification of role assignment is called recertification. In this blog post, I'd like to introduce you to the need for recertifications and our own tool, EasyReCert. The need for recertification - scenarios: Example 1: The "apprentice problem" Imagine the following scenario: A new employee (e.g. apprenticeship or trainee) will go through various departments as part of his or her training and will work on various projects. Of course, an SAP User will be made available to your employee right at the beginning, which is equipped with appropriate roles. As each project and department passes, the employee repeatedly needs new permissions to meet the requirements. After the employee has successfully completed his or her induction and is now in a permanent position, he or she still has permissions that are not necessary to perform his or her duties. This violates the principle of "last privilede" and represents a potential security risk for your company. Example 2: The change of department The change of department is one scenario that probably occurs in every company. If a change of department does not automatically involve a complete reallocation of roles and the employee simply takes his old permissions with him, critical combinations of permissions can occur very quickly. For example, an employee who has permissions in accounts payable and accounts receivable violates the SoD ("Segregation of Duties") principle and poses a potential security risk to your company. Recertification as part of a revision: The two examples above show that a regular review of role allocation identifies potential security risks for your business and can be addressed.
SAP Basis refers to the IT underlying the SAP system. It includes various middleware programs and tools and is responsible for the smooth operation of the SAP system.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
If you look at everything I've described up front in its entirety, it quickly becomes clear which direction things are headed: the SAP basis will increasingly move toward an SRE-centric environment over the next decade.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
It is also possible to export the audit logs or add optional comments to the logs later.