Preparation of migration to SAP HANA
OTHER SERVICES
The marketing mix model is suitable for creating a marketing concept. This is usually divided into four pillars - the four Ps. These are Product, Price, Place and Promotion. In the case of services, this is often accompanied by the aspect of personnel policy. Although the marketing mix model is aimed at the external distribution of products and services, aspects of it can also be applied to an internal marketing of the SAP basis. For the design of the respective areas of the marketing mix, it is recommended to use a guide to develop a marketing concept. STEP 1: DEFINITION OF PERFORMANCE This step deals with the description of the services to be offered. Similarly, this step provides a categorisation of the type of service. These include, for example, the levels of secondary or primary service. With respect to the SAP basis, this step is concerned with product portfolio analysis and the creation of IT products and a product catalogue. STEP 2: OWN RESOURCES Subsequently, a determination of one's resources takes place. That is, it identifies the resources that are available and that can be used and the resources that need to be developed. Resources are people, objects, systems, knowledge, and funds. For the SAP basis, this step is an inventory. STEP 3: DETERMINATION OF THE OBJECTIVES The mission and vision of service providers will be determined in the framework of the setting of the objectives. It also sets measurable targets for the next three years.
SAP Basis is responsible for the smooth operation of programs in the SAP system. It acts like an operating system for R/3 and subsequent releases including S/4HANA. Each operating system provides an environment in which programs can run, such as MS Office on Microsoft Windows.
Definition of general system parameters
The logging of data changes in tables using transports should also be active. For this, the "RECCLIENT" parameter in your transport management system (Transakation STMS) must be set to "ALL" at all system levels.
Automatic error handling when a job is aborted is desirable and useful in most cases. The conscious processing and consideration of error situations in job chains - also at step level - can help to reduce manual effort. Error situations should be catchable: If they are non-critical elements, the following job can perhaps be started anyway. In the case of critical errors, a new attempt should be made or an alert issued so that an administrator can intervene manually. Simple batch jobs are usually not capable of this. The goal of an automated environment is not to have to react manually to every faulty job.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
Then actions such as distribution, implementation, activation and generation take place.
The latter two override ztta/roll_extension if used and offer the possibility to set different quotas for dialogue and non-dialogue work processes.