SAP Basis is structured in the form of a three-layer model and consists of the following components:
Perform user comparison manually with transaction PFUD
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.
SAP Hosting should not be thought of as an off-the-peg suit, but as a made-to-measure suit. For mid-sized companies in particular, it is crucial to first identify corporate goals, technical conditions of the IT architecture and individual requirements. During this planning phase, added value and potential savings can also be identified.
Double stack split
SAP Basis is structured as a classic three-tier model. It contains the following components: Database layer (relational database management system) / Application layer (application server and message server) / Presentation layer (graphical user interface).
The presentation layer is the interface to the users. Through a graphical interface, users enter data or interact with data through the applications. This presentation layer exchanges data with the application layer.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
The miner, which solves the last transaction of a block before a new one is generated, also gets a bitcoin as a reward.
The job of an SAP Basis consultant has many areas of responsibility such as: