SM30 Table maintenance
What does an SAP Basis administrator do?
The security of an SAP system requires protection against unauthorised access, e.g. through the secinfo and reginfo files. A cleanly implemented authorisation concept protects against attacks within the SAP system. However, it is also possible to attack your SAP system via the network. Through the RFC Gateway Server, your system communicates with external servers and programmes. One particularly effective way to protect against this are so-called Access Control Lists (ACL). Find out what this is and how you can use it to better protect your SAP system. The SAP Standard offers different approaches for gate protection. All methods combined can provide even greater safety. For example, it is possible to use Access Control Lists (ACL) to monitor exactly which external programmes and which hosts can communicate with the gateway. Another option is to configure the gateway to support Secure Network Communication (SNC). Finally, there are various security parameters for the gateway. This article focuses on the use of ACL files such as secinfo and reginfo files. What is an ACL? Access control lists are files in which permitted or prohibited communication partners can be recorded. For the gateway to use these ACL files, parameters must be set in the default profile of the SAP system and of course the files must be maintained accordingly. With the help of logs and traces, which can be configured for this purpose, a precise investigation can be made in advance of the activation, which connections currently run via the gateway. This allows them to prevent important applications with which your system communicates from being blocked by the ACL files. The rules in the ACL files are read from top to bottom of the gateway to decide whether to allow a communication request. If none of the rules matches the requesting programme, it will be blocked. Network-based ACL The network-based ACL file contains permitted and prohibited subnets or specific clients.
SAP Basis is also known as module BC or application Basis. 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.
Advice on hardware, database, operating system, type of installation (physical or virtual)
Will Blockchain's Economy and Administration Revolutionise? What is a blockchain? A blockchain is a complete and unchanging transaction history of all transactions of a decentralised community that everyone who is part of it agrees to. The word blockchain first fell in connection with Bitcoin as a decentralised network for payments in the digital currency of the same name. The blockchain describes an underlying technology in which all transactions are publicly and unchangeably recorded. This transaction history is updated periodically. Each participant in the decentralised community accepts it as a reality, stores it on their computer, and can thus ensure at any time that no one can duplicate expenditure, as this would lead to a conflict in the transaction history elsewhere. A peculiarity of blockchain technology is that it has solved the "Double Spending Problem". Double-spending means something that can be doubled, and by 2008, only one central institution was considered to be sustainable. Double Spending can best be understood using the example of an image on a mobile phone. When I upload it to Facebook, I made a copy of it and I can upload it to Instagram, for example. So I used my picture "double". This effect made it impossible to establish a trustworthy, decentralised digital currency by 2008.
Some useful tips about SAP basis can be found on www.sap-corner.de.
Have you ever wondered what there is actually a tab personalisation for role maintenance in the PFCG or for user data maintenance in the SU01? I will answer this question for you in this blog post. What do we need the Personalisation tab for? This tab gives you access to the central repository for personalisation data. The purpose of this repository is to create a storage facility for user- and role-specific data without the need to create additional database tables. This data should then be taken into account in all manipulations of users and roles. The functionality initially includes a generic repository for user- and role-specific data and centralised access to that data by user and role maintenance. It also provides the ability to connect existing tables with user-specific data to the central access via a defined interface. To store personalisation data in the central repository, a key must be assigned to the data: This is done via the registration transaction PERSREG. The personalisation data that you create is stored in the generic drop table. Access to it is provided by the class methods of the CL_PERS_ADMIN class. Different levels of personalisation The data can be stored either to the user, to roles or to the system. A user can then read all data assigned to him (via role or his own settings) at once.
"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP basis.
Your administrator must carefully schedule these tasks when user demand is low so they don't impact performance.
Both are required to use the solution documentation in conjunction with other components.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.