SAP Basis Online, offline, delta backups - SAP Corner

Direkt zum Seiteninhalt
Online, offline, delta backups
SAP Basis range of services
SAP Basis usually takes care of the administration of the SAP system. The most important SAP Basis transactions are listed in this article.

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.
Solution Manager
Especially in larger companies, which also have multiple locations in different countries, it is often necessary to grant different employees the same permissions for different levels of organisation, such as accounting circles. In order to make maintenance and maintenance of the system easy in such a situation, it is useful to set the inheritance principle for SAP permissions. How does SAP Permissions Inheritance work? An inheritance is always about a master object passing certain properties to a derived (sub) object. Therefore, these properties do not need to be maintained several times. Also, changes to the master object are passed directly to the derived objects. This allows easier maintenance and drastically minimises the error rate. In the case of SAP Permission Inheritance, the required permissions are bundled in a Upper or Master role. Only the organisational levels have to be maintained in the roles derived from them. The permissions are automatically pulled from the master role. Create Inheritance for SAP Permissions The following shows how to create and use inheritances for SAP permissions. This requires only two steps: Creating a master role and defining derived roles. Step 1: Create a master role Inheritance always requires a parent role, because all properties are inherited from it. If this role, in which all shared permissions are bundled, is missing, the first step is to create this master role. To do this, open the PFCG transaction and enter the desired name of the master role in the Name field. It is possible to identify master and derived roles by using naming conventions. The "Single Role" button will then be used to create the desired role. In the following example I create the master role "findepartment_r".

Since jobs and backups should run at set times for organizational or technical reasons, automating them is a good idea. In simple, clear system environments, many SAP Basis administrators help themselves with SAP CPS (Central Process Scheduling) and simple ABAP batch jobs that start operations or other jobs. Since the desires and the system environments usually grow continuously, this approach becomes complex and confusing over time and troubleshooting often becomes difficult. As a result, maintainability often falls by the wayside and error-proneness can increase. If different jobs are strung together to form chains, further problems arise.

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

Note: Logging user activity must be aware of the users concerned! Configure the SAL only for technical users or in consultation with users / works council / etc.

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 you will find useful information on this topic.

Encryption costs performance, so it is not used by default.
SAP Corner
Zurück zum Seiteninhalt