System Landscapes and client systems
SAP systems are client systems. A client (Client) is a closed organization and data link unit within an R / 3 system (with separate master records and a separate set of tables). Each R / 3 can several (more precisely, contain up to 1000) client. The client concept enables multiple legal (commercial law) and organizationally independent companies into a single SAP R / 3 to operate the system, e.g.
• The clients of the company in a group within an R / 3
Systems of this group or
• a variety of clients for the clients of an Application Service
Provider (ASP) within an R / 3 this provider.
The exceptions are the components of SAP Business Information Warehouse (SAP BW) and SAP Knowledge Warehouse (SAP KW) of mySAP business intelligence (mySAP BI). In them will be used only one client. When a user logs on to an R / 3 systems, it always reports in a particular client of this system. Normally, he can
with this application (because the rights associated with the R / 3) work only with application data of the client. However, there are tasks in R / 3, which across clients
are. This mainly customizing tasks (with-client settings, for example modeling the structure of a company using organization elements), and development tasks (eg
Development of program objects - such reports - in the ABAP Workbench) and test these settings and objects.
More generally, this is to introduce tasks (with the introduction an SAP system) and maintenance tasks. If you customizing, development and testing tasks in the same SAP R / 3 system, such as conducting productive, so, there may be too (sometimes significant) disruption of production operations to come. To this Encounter danger, it is recommended that these tasks (and possibly more Tasks, such as for example Training exercises) with a certain "distance" making of productive client. First, other clients should be chosen for these tasks. However, it should be noted, that any other client additional system resources (the main memory and the database) is required and the administrative burden is heavier is.
• Customizing Client
Customizing and development work (in the ABAP Workbench) should
in customizing and development client (in short: Customizing
Client) are implemented. For him, the abbreviation is usually CUST.
• Quality Assurance
Tests (eg, integration testing of several different application components)
should be conducted in a quality client
will. For these clients, the abbreviation is QTST usual.
• Productive client
The separate client for the productive use of the SAP system is
Productive client. For him, the acronym PROD is common.
For larger introduction or maintenance tasks recommended, SAP AG, perform these tasks in one or more other SAP systems and the results of the work (eg, attitudes and / or objects) to transport between the SAP systems. The tools available here
especially the client-Copy (client copy) and the Change and Transport System
(CTS) are available.
So it - depending on the variety of work tasks and the size of the group / company and possibly its partner companies - to more or less complex system landscapes. A system landscape consists from SAP systems, which by transport routes (for the initial and Maintenance process) are linked.
System landscape-1
It consists of three SAP systems each of these clients (CUST, QTST and PROD) in a separate SAP system is included. Changes customizing settings and objects of the ABAP workbench are carried out exclusively in the customizing client CUST and
after the release of the associated change orders in the quality assurance client
QTST transported. After successfully testing the Change requests from there to the productive client PROD transported.
System landscape-2
It consists of two SAP systems, with clients and CUST QTST in one SAP system are included and the client PROD in the other SAP system is included. The sequence of changes, revisions, and transportation is basically the same as in the 3-system landscape. The disadvantages of a 2-system landscape consists in the fact that Client independent Data are in CUST and QTST shared; changes CUST-client settings in the tests may in QTST influence. In addition, the completeness of the transportation of can CUST after QTST is not guaranteed in any case. For smaller SAP implementation and in particular only minor Workbench development is the 2-system landscape, however, a reasonable alternative be the 3-system landscape.
System landscape-3
It consists of a single SAP system, in which all three clients (CUST, QTST and PROD) are included. The 1-system landscape is characterized by SAP AG is not recommended. Especially after the real you no further developments and tests are made in the system, unless the production operation is set during this time (eg
during working holidays).
|
