SAP Basis SWU2 Transactional RFC

Direkt zum Seiteninhalt
SWU2 Transactional RFC
Missing result documentation
To best adapt your SAP system to the internal and external requirements of your organization, further table-related customizing is required. Here, SAP offers the possibility of logging changes to critical tables through table logging.

Using various user, administration and monitoring tools, the SAP Basis system is controlled and managed by an administrator, who is thus responsible for its trouble-free operation. Many companies hand over these tasks to an external service provider.
Why does a company need an SAP Basis department? [Using our company as an example]
The SAP Basis Plug-In is backward compatible and follows the release and maintenance strategy of the SAP R/3 Plug-In. SAP delivers it together with the SAP R/3 Plug-In. For more information, see SAP Service Marketplace at basis-plug-in → SAP Plug-In → SAP Basis Plug-In → Releases.

Since innovations through IoT (Internet of Things) or big data scenarios not only affect the SAP basis, but also highlight products and services for customers of their own company, the role of the SAP basis in relation to these scenarios and services must be clearly defined. In general, the SAP basis sees its responsibility here in the connectivity to the corporate network or the enterprise systems, which lie in the responsibility of the SAP basis. The support of the applications, based on the technologies as well as the associated services, is the responsibility of the respective department that offers this service. A SAP-based support service must be agreed and regulated during the conception.

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

This is the repository data used by applications.

In the administration interface, the launchpad can be customised, so this permission should only be released to a few users for administration.
SAP Corner
Zurück zum Seiteninhalt