SAP Basis High flexibility for ad hoc growth

Direkt zum Seiteninhalt
High flexibility for ad hoc growth
The Basis system comprises a total of three layers (Figure 1):
Every SAP system evolves 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.

Project successes should also be documented and circulated as success stories of the SAP basis or made available to the SAP basis stakeholders to highlight the importance of the SAP basis. These success stories can be shared from the grassroots or from the outside, for example. Examples include CIO communications or project reports. BENEFITS & CONSEQUENCES The added value of the implementation of the recommendations described above lies in the guaranteed operational stability and operational safety. In addition, a company and in particular an IT organisation with a strong SAP basis receives a competent and sustainable partner for SAP topics and technologies, who is always looking at the SAP picture in general. Furthermore, all business and IT departments are aware of the role and the scope of the SAP basis. This means that you can contact them as the right person in good time. There is a lower risk that certain areas may develop shadow IT related to SAP topics and technologies due to lack of transparency.

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.
Definition of general system parameters
SAP Basis is the foundation of every SAP system. On this page you can find out what is behind the term and what SAP Basis is responsible for in detail.

If you need to reinstall a Support Package because of errors or because a SPAM update is required, reset its status. Resetting does not mean that the system is at an old state. Note that your system is inconsistent when you reset the status after items have already been imported (for example, after the DDIC_IMPORT step and following). Resetting the status should only be used to troubleshoot the issue and you should repeat the playback as soon as possible. Procedure To reset the status of a Support Package or Queue, select Add Status Reset. Result After updating the status, the corresponding entries in the cofile and in the log file are deleted. The support package must then be fully reloaded. The transaction SPAM starts the insertion with the step CHECK_REQUIREMENTS [page 26].

With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.

Further contents are the basic communication technologies: IDoc, RFC, http and SOAP.

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.


Now the role only has to be assigned to the corresponding users in the system.
Zurück zum Seiteninhalt