Technical structure
Determination of specific transactions with user assignment using SE16N
For these cases, you should take a closer look at the DBACOCKPIT transaction. This transaction provides you with many other database management features, an editor that allows you to easily execute your SQL queries against your SAP system. This method displays the result in the GUI shortly after the query is sent. How to execute a SQL query To call the editor for SQL queries in DBACOCKPIT, the user must: The user needs corresponding rights to execute the transactions SM49 and SM69. STOR and SMSS must be cultivated in the S_ADMI_FCD permission object. SQL queries must maintain the database connection. To get the current status of a database connection, see the DBCONT table. Rights for calling the table(s) to be retrieved must be assigned. For more details, see the section "Further information on DBACOCKPIT" in this blog post.
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.
Insert Queue
In order to cope with the digital transformation in general, but also to cope with the changing demands on the SAP basis and its scope of responsibility, it is necessary to revise existing roles and define and establish new roles. These include the roles of the technology architect, new features of the Subject Matter Expert (SME), and the role of the Expert Team Lead in leading a group of experts. Further information can be found in chapter 7.1 and 9.3 of the Master's thesis.
The website www.sap-corner.de offers many useful information about SAP basis.
Cross-client tables can be modified. The control system of another, productive client can thus be undermined and undermined. Quite a lot of power! Did you also know that the SAP system provides a feature that deletes table change protocols (DBTA BLOG table) and that it is effective across all clients? If the table change logs have not been additionally archived via the BC_DBLOGS archiving object, traceability is no longer available. That way, every criminal act within your company can be beautifully covered up. Similarly, full access to batch management allows you to manage all background jobs in all clients with the permission. This allows you to delete old background jobs that have gone unauthorised. There are also some points to consider when managing print jobs. Typically, the following two SAP access permissions are enabled to protect print jobs: S_SPO_DEV (spooler device permissions) S_SPO_ACT (spooler actions). Why? Confidential information in print jobs is not protected against unauthorised disclosure. (Strictly) sensitive print jobs can be read unauthorised or redirected to external printers and printed out. Print jobs are unprotected unless additional SAP access permissions are enabled to protect print output. The print jobs are multi-tenant, which means that the authorisation award should also be well thought through at the point.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
This is installed by an SAP Basis administrator and can consist of one of the following databases: HANA, Sybase, DB2, Oracle, MSSQL and MaxDB.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
In the Test_Schmidt2 role, the transaction MM03 was maintained in the menu of the role, but the transaction MM04 was maintained only in the S_TCODE permission object of the role.