ADMIN TOOLS
OData Services
The presentation layer is the top layer of the R/3 SAP Basis system and includes the communication with the user. Here, the data is graphically prepared for the user on the end device by means of software components from the application programs of the application layer. The presentation layer is the interface to the user (SAP GUI).
SAP Basis Administration Batch Control Job Control A large proportion of batch jobs run at night, while IT systems are available for dialog and online applications during the day. Meanwhile, web applications demand computer capacity around the clock. Even dialog systems are no longer in operation only from 8 a.m. to 6 p.m., but between 7 a.m. and 10 p.m. or longer. The time window for administration tasks is increasingly shifting toward transaction processing. This leaves less and less time for mission-critical batches, which can lead to disruptions and terminations. Whereas batch processing used to be a mainframe domain, companies today usually have to control background processing in heterogeneous operating system environments and client-server applications. For this reason, cross-platform, integration-capable job schedulers that can respond to unplanned events are in demand.
ST02 Operating system overview
The coverage of old core tasks (such as security or compliance) and new core tasks (such as cloud or mobility) must be increased in the sense of a holistic consideration. This means that certain tasks must be considered not only in the context of the SAP basis, but also in the overall context.
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.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
In earlier product generations, databases from various third-party providers were used - primarily Oracle and Microsoft SQL.
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 www.sap-corner.de you will find useful information on this topic.
The following table shows the typical structure of a three-tier R/3 Basis system.