Would you like to learn more about the different SAP modules?
For simple system environments, simple batch jobs are often sufficient
An understandable and comprehensible strategy enables the SAP basis to derive it as easily as possible to practice and to the resulting requirements and activities. The main task of the SAP basis is to support new business models by implementing the strategy and to show how much technical and financial effort and benefit is generated. It is also the task of the SAP basis to identify the skills and resources necessary for them and to ensure their existence at an early stage.
The default permissions to open and use a launchpad are the SAP_UI2_USER_700. The role for the administration is SAP_UI2_ADMIN_700. In the administration interface, the launchpad can be customised, so this permission should only be released to a few users for administration.
Preparation of full access to SAP systems and solutions in case of disasters (High Availability/Disaster Recovery)
The tasks of a company's own SAP Basis department are currently undergoing enormous change, as SAP is also increasingly relying 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.
Costs: 75% savings on subsequent corrections. Significant reduction in development and maintenance costs. ABAP code: 84% faster and more fail-safe programs. Improved performance reduces runtime and hardware utilization. Targeted corrections minimize system errors and downtime.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
There are several points to consider.
So Johannes logs in with the known password of the RFC user in the production system.