SAP Basis Development guidelines - SAP Stuff

Direkt zum Seiteninhalt
Development guidelines
STMS_IMPORT Import queue
The results of the tests can be documented so that the development can be considered over a period of time. This way, you will be aware of the revision and of the relevant issues before the examination.

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.
SM12 Select lock entries
Every SAP system develops over many years. It grows and changes with the company. The more functions are mapped in it and the more data is stored, the greater the importance of and dependence on this central ERP system. There is no such thing as a standard SAP Basis solution. It is developed individually with reference to the company.

Capacity must be built to provide the necessary space for pilot and research projects and to meet the increased demands. This can be done, among other things, by increasing the previous resources or/ and by measures of standardisation & automation as well as "cloudability", outsourcing & outtasking.

The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.

The Message Control tab defines which application should generate a message.

On www.sap-corner.de you will also find useful information about SAP basis.

For the control, measurement and monitoring of external partners, Service Level Agreements and meaningful key figures are also available.
SAP Stuff
Zurück zum Seiteninhalt