Installation
SLICENSE SAP License Management
Every SAP Basis system must be controlled and managed by an administrator. The person responsible ensures smooth operation of the system. This can be an internal administrator, or can be handed over to external service providers.
When it comes to outsourcing or outtasking SAP Basis services, we see ourselves as an experienced partner for ensuring that your SAP systems run smoothly. In addition to planning your future SAP deployment, we perform upgrades and configuration changes. We support you on-site and/or remotely in all SAP system management tasks to ensure the continuous availability of SAP applications.
REDUCTION AND AVOIDANCE OF ORGANISATIONAL INCENTIVES
Within SAP R/3 Enterprise, the SAP Basis Plug-In is a prerequisite for you to use the SAP R/3 Plug-In. SAP Basis Plug-In and SAP R/3 Plug-In must always have the same release level, for example PI 2004.1 and PI Basis 2004.1. If you plan to upgrade SAP R/3 Plug-In within SAP R/3 Enterprise, you must also upgrade SAP Basis Plug-In. As of SAP Basis Plug-In 2005.1, the release levels of the two plug-ins no longer need to correspond. However, the SAP R/3 Plug-In Support Package for PI 2004.1, which contains new interfaces, still requires a specific SAP Basis Plug-In. For example, SAP R/3 Plug-In Support Package 10 for SAP Plug-In 2004.1 requires SAP Basis Plug-In 2005.1.
With the SPAM transaction, you can always find out about the record status of your system. The SPAM transaction is included in the SAP Upgrade process. SAP Patch Manager (SPAM) (BC-UPG-OCS) SAP AG SAP Patch Manager (SPAM) (BC-UPG-OCS).
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
The chain now has in principle two end pieces (2 parallel blocks).
This means that the values for abap/heap_area_dia, abap/heap_area_nondia, ztta/roll_extension_dia and ztta/roll_extension_nondia can be set dynamically here.