SAP Basis Ensuring operational readiness - SAP Admin

Direkt zum Seiteninhalt
Ensuring operational readiness
The Client Control
Database layer: The database layer contains a database server on which all the data of the SAP ERP system is managed. This includes the database management system (DBMS for short) and the actual dataset. The dataset includes user data and data tables as well as applications and system control tables.

There are the following reasons that may lead to the termination of this step: CANNOT_GET_OBJECT_LIST: The Object List for a Support Package could not be found because the Support Package does not exist. CANNOT_CHECK_LOCKS: An error occurred while detecting the locks of an object in the queue. OBJECTS_LOCKED_IN_REQUESTS: Objects found in unreleased jobs. Release these jobs before you resume playing. SCHEDULE_RDDIMPDP In this step the transport daemon (programme RDDIMPDP) is planned. There are the following reasons that may lead to the termination of this step: CANNOT_SCHEDULE_RDDIMPDP: The RDDIMPDP job could not be scheduled. Enter the transaction SM37 (job selection), enter the following parameters, and select Next: Job Name RDDIMPDP Username Start by Event SAP_TRIGGER_RDDIMPDP Select the job that was cancelled and view the job log.

On www.sap-corner.de you will also find useful information about SAP basis.
Process transports between systems
In order to have some advantage in terms of new SAP technologies, suitable PoCs (Proof of Concepts), research and pilot projects must be initiated to build know-how and evaluate boundary conditions or feasibility. Furthermore, this serves the evaluation of new business models by the underlying technology in collaboration with the respective business unit.

Parameters in the SAP create a high degree of flexibility. Profiles can be used to configure the system for almost any purpose. But with such a large number of parameters one quickly loses an overview of the influence of each parameter. For storage management alone, there are 20 different parameters that can be changed at different points in the SAP system. This article brings order to the mess and explains the most important parameters. There are three types of memory in the SAP system for a work process: ・ Roll Area - Local Memory Area for a Work Process ・ Extended Memory - Global Memory Area for All Work Processes ・ Private Storage /Dynamic Memory (Private Memory/Heap Memory) - Private Memory Overview of SAP System Memory Regions Parameters for the Rolling Range When a user starts a programme, a role area is created for that programme instance through a workprocess. The user context is stored in this memory area. The size of the roll area for a work process is determined by the ztta/roll_first parameter. If the storage area is not sufficient, a portion of the Advanced Memory will be allocated for the user context, the size of which will be determined by ztta/roll_extension, ztta/roll_extension_dia, and ztta/roll_extension_nondia. The latter two override ztta/roll_extension if used and offer the possibility to set different quotas for dialogue and non-dialogue work processes.

Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.

In all these areas, they take care of the smooth functioning and development, thus helping the company to make internal processes more efficient and consequently save costs and resources.

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.


EARLY INVOLVEMENT IN THE PROJECT IS ESSENTIAL.
Zurück zum Seiteninhalt