Database Reference
In-Depth Information
the testing is complete, the Basis team will move the changes to the production system for
deployment.
Software Logistics in ABAP Systems
As mentioned, software logistics in an ABAP system includes a discussion of concepts such
as SAP System Landscapes, SAP client concept, SAP client instance strategy, SAP version
management, SAP client-dependent and client-independent data, SAP configuration
changes using the Implementation Guide, and SAP change requests and transport manage-
ment. Some of the examples of SAP ABAP systems are SAP ERP, SAP BW, and SAP
SCM.
System Landscapes
The System Landscape is defined as a SAP server environment usually comprising of devel-
opment, quality assurance, and production systems. Additional systems in a typical land-
scape may include servers for training and data conversion purposes as well. Recommenda-
tions for a System Landscape are based on the purpose, organization size, and scope of the
implementation effort of the project.
In a one-System-Landscape, development, quality control, and production needs are met
by a single system. This kind of landscape is usually used for demo and training environ-
ments only. It is not recommended for productive operation. In a two-System-Landscape,
development and test are performed in one system and changes are then moved to a second
production system. This landscape does not allow for an isolated test environment, and any
changes to the development objects can have an immediate impact on the testing environ-
ment. This landscape is not recommended for productive operations. It is usually used in
demo, training, and very small organizations where the scope is limited. SAP recommends a
minimum of three System Landscapes consisting of development, quality control, and pro-
duction systems. This is the most common SAP System Landscape, and it meets the needs
of most mid-size to large organizations. The illustration shows a minimal three-System-
Landscape environment consisting of development, quality assurance, and production sys-
tem environments. Moving the code changes and configuration changes from the develop-
ment system to quality assurance systems and then to production systems in an orderly man-
ner, with proper testing and an approval process, is usually referred to as a “promote to pro-
duction strategy.” For some SAP implementation projects, the needs are more demanding
than the typical three-System-Landscape, and in these cases the landscape is further exten-
ded into four or five System Landscapes. This is further discussed in detail in
Chapter 13
.
