SAP Basis How relevant is SAP Basis? - SAP Basis

Direkt zum Seiteninhalt
How relevant is SAP Basis?
SE80 ABAP Workbench
It should be mentioned here that it only makes sense to access the tables by reading the SELECT statement to get a quick view of the results. Using the DBACOCKPIT, it is not possible to create entire table structures using Create Table. For such applications, SAP provides other, better options. Another important point is that once a user has the necessary permissions to use the transaction DBACOCKPIT, it can potentially (with appropriate permissions on the tables) access the entire SAP system. For example, a query can be used to read the entire user table. Therefore, the transaction should always be treated with caution and only awarded to administrators. DBACOCKPIT handles the call control permissions similar to the SE16 / SE16N transaction. When the table is called, the S_TABU_DIS or S_TABU_NAM permission object is checked with a specific activity. This means that only the tables or table permission groups for which the corresponding values in the aforementioned permission objects are assigned can be accessed. You can read more about assigning permissions to individual tables here. In addition, you can save SQL statements that you run once, and run them again at any time to recognise changes in the result set without having to reformulate the SQL statement each time. The editor also allows you to start the query for SQL statements in the background. The result is obtained by calling the transaction SM37, in which the result is output in a spool file.

SAP Basis is also known as module BC or application Basis. In this regard, SAP Basis refers to all transactions, programs and objects that control the functions of the overall system. This includes, among other things, user and authorization management as well as the configuration of interfaces via RFC.
Post Installation Services
SAP Basis is structured as a classic three-tier model. It contains the following components:

In the following dialogue, select a TADIR service and the programme ID "R3TR" and the object type "IWSG". Now you can select the OData service stored on the front-end gateway. Then switch to the Permissions tab to generate the current profile of the permission objects with the new Fiori permission. Once you have performed these steps, the treated role has the necessary permissions on the front-end side. Fiori Permission to call the OData service on the backend server Now go to the role maintenance in the PFCG on the backend server. Open the appropriate role in Change Mode. Now you can repeat the steps for the frontend as explained above. However, when selecting the TADIR service as the permission proposal, you now select the object type "IWSV". Here you can select the OData service of the specific Fiori application stored in the backend.

Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".

The application programs on the application servers request the required data from the database layer, process it, prepare it for the user and pass it on to the presentation layer.

Instead of data and application development, the focus here is on providing the software environment on which the company's tools are created.
SAP BASIS
Zurück zum Seiteninhalt