SAP Basis

Unit 7: Working with the Transport System ADM100
Lesson:
184
Data Structure of SAP Systems and System
Landscapes
Lesson Duration: 45 minutes
Lesson Overview
The data structure of an SAP system will be discussed. Terms such as
client, object repository, and cross-client Customizing will be introduced.
Threewaystochangeandcreaterepositoryobjectswillbedescribed.
The advantages and requirement for a three-system landscape will also
be presented.
Lesson Objectives
After completing this lesson, you will be able to:
• Describe the data Structure of an SAP system
• List the advantages of and requirement for a three-system landscape
You should emphasize that the repository and cross-client Customizing
only exist once for each SAP system. You can illustrate this with a fictional
example of two different companies mapped in different clients, and
served by one computer center. You should also emphasize that modifying
SAP objects should be an absolute exception, since time-consuming
tasks have to be performed during the modification adjustment. The
instructor should also introduce the SAP and customer namespace; for
more information, see the online help, section BC-CTS.
Business Example
SAP software is to be adjusted to company-specific requirements in your
company. How are programs exchanged between SAP systems? As little
postprocessing as possible should be required in the case of a subsequent
system upgrade.
Data Structure of the SAP System
Knowing the data structure of an SAP system is equally important for
users, developers, and administrators to understand the way in which
an SAP system functions.
218 © 2003 SAP AG. All rights reserved. 2003/Q3