✒️El landscape de SAP
El landscape de SAP
SAP Landscape
The SAP landscape refers to the arrangement and configurations of SAP servers within a company implementing the system. It involves determining the architecture, the number of servers, and their specific purposes. BASIS professionals handle the configuration.
Within these landscapes, system administrators define Environments, also known as systems in SAP.
SAP Environments
An environment in SAP is a server where the SAP system is installed. Each environment is independent and relies on its own database or a partition of the database.
- Development: Involves programming and system configuration by functional consultants.
- Testing: Includes technical and integration testing.
- Production: Allows end-users to utilize standard and custom transactions.
Types of Landscapes
- Single-Environment SAP Landscape: Combines development, testing, and production operations in a single system.
- Two-Environment SAP Landscape: Separates production from testing and development.
- Three-Environment SAP Landscape: Independently divides development, testing, and production environments.
Clients / MANDT
Within each SAP environment, various clients or 'MANDT' exist, each showcasing distinct data. A client is an instance created within an environment for configuration, development, training, or testing. In SAP, it's also known as a 'Mandate' and can be viewed using transaction SCC4.
Development Environment Clients
- Client 101: For configuration and programming.
- Client 102: Sandbox for experimentation by consultants.
- Client 103: For unit testing of programming.
Testing Environment Clients
- Client 210: For integral testing by consultants and key users.
- Client 220: For human resources training.
Production Environment Clients
- Client 410: Accessed by end-users for daily company operations.
Client Definitions
- Logical Perspective: Client serves as an organizational unit, allowing users to work without interference, ensuring unique access to visualize and update application data.
- Physical Perspective: The Client is typically the key field in SAP database tables. Only one person can access a Client at a time, ensuring data integrity.
If you think you need to separate data between different clients in the same system, you need to have MANDT field in the table. Those kind of tables will be known as client dependant.
Standard Clients
Come pre-installed with SAP. Every SAP system includes three standard Clients:
- Client 000: Reference Client with no parameterization data. Custom Clients should be created with copies of 000 to ensure proper parameterization from scratch.
- Client 001: Example Client initially identical to 000 but can be modified without SAP updates affecting it.
- Client 066: Service Client for EarlyWatch, ensuring data security in productive environments. It connects with SAP for performance issue detection services and should never be modified or deleted.
Custom Clients
These are created by the user (SAP administrators of the client company). Each company can assign any number to custom clients. While many or few clients can be created, having too few may cause issues in configuration, program development, or testing. Conversely, having too many clients increases the database size, reducing performance. Hence, a balance is crucial.
Functions of Custom Clients:
- Client 200 Development and Configuration: This is where tailored developments are created as needed. Both technical and functional consultants work here. There are no master data or transactions. Therefore, if testing is required, it will be conducted in client 220.
- Client 210 Sandbox: Unusual tests are conducted here to avoid disrupting the routine work of client 200. Changes made here are not recorded.
- Client 220 Unit Testing: Those responsible for development and configuration perform unit tests on the programs. Master data and transactions are present here.
- Client 300 Integration Testing and Quality Control: Functions similarly to client 220. Tests involve interaction between different modules, performance checks, and user approval.
- Client 310 End User Training: After completing the tests related to client 300, the prototype is transferred to client 310. This allows users to train and practice.
- Client 320 Configuration Master: Used as a reference to check the configuration of production without accessing its system, eliminating the need to grant access to unauthorized personnel.
- Client 400 Production: This is where real exploration of the system takes place. It is the only custom client that should exist in the production environment. Before going live, initial loads of master data, movements, and historical data are performed here.
Development Classes or Packages
The development class, also known as a package, is a way of organizing all the new objects created in SAP by classifying them based on modules or functional areas.
There is a development class called TMP, used for temporary objects that won't be transported between environments, specifically for testing purposes.
Transaction SE80 is used to create development classes or packages.
Sobre el autor
Publicación académica de Jaime Eduardo Gomez Arango, en su ámbito de estudios para la Carrera Consultor ABAP.
SAP Master
Jaime Eduardo Gomez Arango
Profesión: Ingeniero de Sistemas y Computación - España - Legajo: SW34C
✒️Autor de: 99 Publicaciones Académicas
🎓Cursando Actualmente: Consultor ABAP Nivel Avanzado
🎓Egresado del módulo:
Disponibilidad Laboral: FullTime
Presentación:
Ingeniero de sistemas y computación con 8 años de experiencia el desarrollo frontend & backend (react/node) y en cloud (aws), actualmente desarrollando habilidades en sap btp, ui5, abap y fiori.
Certificación Académica de Jaime Gomez
