Permissions for an app's business logic
Application layer
When I began my career administering SAP ERP on Oracle in the early 1990s, running a database required far more knowledge. An Oracle administration expert with a decade of experience understood perhaps only about 5% of what the database required.
Each SAP Basis system must be controlled and managed by an administrator. This person is responsible for the smooth operation of the system. This can be an internal administrator or it can be handed over to external service providers.
REGULAR FLOW OF INFORMATION
In the past, when we deployed SAP environments, we first had to work out detailed sizing and architecture and pass this on to the procurement team, who then ordered the systems and installed them in the data center. From there, it went on to the network team, the storage team, the operating system team, and the database team. So it was not uncommon for three to six months to pass between the architecture design and the installation of a new SAP system.
Different customers have different support requirements and concepts. We support them on-site as an extension of their internal team as well as through remote connections. Be it on an ad hoc basis (e.g. release upgrade, DB upgrade, optimization of Solution Manager) or on a permanent basis (e.g. monitoring of operations in SLR, fast reactions in defined exceptional cases, planned maintenance), we have the right team, the appropriate procedures (ITIL) and the modern tools to implement your requirements.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
Some useful tips about SAP basis can be found on www.sap-corner.de.
Hide/show tabs If you are now logging in with a user that is not in the default Administrators group, you will not see applications/tabs on the CMC home page.
However, these sums can vary depending on the company and location.