SAP Basis Development guidelines - SAP Corner

Direkt zum Seiteninhalt
Development guidelines
/IWFND/MAINT_SERVICE Activate and manage services
The tasks of a company's own SAP Basis department are undergoing enormous change at many companies, as SAP is also relying more and more on cloud services. Strategically, completely self-hosted SAP systems are becoming rarer and the proportion of customers using an SAP system from the cloud is increasing. The new roles of SAP Basis employees tend to be "enablers" and coordinators between the cloud provider and internal IT and the business departments. Until that time comes, companies can also rely on external service providers to offer expert know-how as well as operational support for the transition period.

In principle, exceptionally good knowledge of computer science is essential. In addition, SAP administrators must of course be particularly well versed in this specialist area and be able to deal confidently with all issues relating to SAP solutions. Since they often also work in international companies, it is an advantage if they have a very good command of written and spoken English.
RESOLUTION OF SILO EDUCATION AND/OR SEPARATION OF SAP AND NON-SAP SPLITS
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.

Site Reliability Engineering(SRE) is the equivalent of SAP Basis in the Google world. Ben Treynor, who has been with Google since 2003 and is considered the godfather of SRE, describes SRE as "what happens when you give operations tasks to a software engineer".

Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.

With HANA, replication works instantly and provides richer functionality and better control than previous databases.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.


IMPORT_OBJECT_LIST In this step, the object lists for the support packages that are in the queue are fed into the system.
SAP Corner
Zurück zum Seiteninhalt