What is SAP Landscape?

Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different lanscape DEV, QAS and PROD. - DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test. - QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training. - PROD may have something like a 200 Production. These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario. Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving everytime. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example). You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients. But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory. The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation. In summary: Landscape : is the arrangement for the servers IDES : is purely for education purpose and is NOT INCLUDED in the landscape. DEVELOPMENT ---> QUALITY ----> PRODUCTION DEVELOPMENT : is where the the consultants do the customization as per the company's

requirement. QUALITY : is where the core team members and other members test the customization. PRODUCTION : is where the live data of the company is recorded. A request will flow from Dev->Qual->Prod and not backwards. 1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you do all the configuration/customization as per the companies business process. 2. Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server. 3. Production Server: This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new develpoment is done is development client and the request is transported to production. These three are landscape of any Company. They organised their office in these three way. Developer develop their program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server. Presentaion Server- Where SAP GUI have. Application Server - Where SAP Installed. Database Server - Where Database installed. What is the meaning of "R" in R/3 systems? R/3 stands for realtime three tier architecture. This is the kind of architrecture SAP R/3 system has. R/3 means three layers are installed in Different system/server and they are connected with each other. 1) Presentation 2) Application 3) Database Why do we call client 000 as golden client? Golden client contains all the configuration data and master data so some extent. All the configuration settings are done in golden clients and then moved to other clients. Hence this client acts as a master record for all transaction settings, hence the name "Golden Client". The Development Client is also the Golden Client because it has all the correct configuration settings which have been tested and are error free. The Golden Client is taken a reference while performing some other configuration

settings.You cannot change any settings in the golden client.

What exactly is SAP System Landscape? How does this phenomenon differ from SAP System Architecture? In this posting, I intend to answer the above mentioned, closely related questions in a very concise manner, with particular emphasis on the system landscape of SAP. Often times, SAP users, especially new comers misunderstands the two concepts. The SAP architecture is typically the technology framework of the SAP system. SAP's architecture unlike the system landscape has changed over time (and more recently) with the advent of SAP ECC. In a prior posting, I "x-rayed" they system architecture of SAP R/3. They system landscape basically is the set-up or arrangement of your SAP servers. Ideally, in an SAP environment, a three-system landscape exists. A three-system landscape consists of the Development Server-DEV, Quality Assurance Server-QAS and the Production ServerPROD. This kind of set-up is not primarily designed to serve as server clusters in case of system failure, the objective to enhance "configuration pipeline management".

A Typical SAP Three-System Landscape. At this juncture, it is important to state that a test system - Sandbox can also exit separately. The essence of the sandbox is to test the configuration of the business processes of a company, especially at the inception of the project (before the Business Blue Print is signed). It can also serve as a practice environment, even after go-live. Pipeline is the environment where the configuration in the development system is moved to the quality assurance system and finally to the production system. The whole idea is to ensure that the configuration of these systems is in sync at any point in time. Suffice to say that, configuration/changes are first made in the Development system, thoroughly tested in the Quality Assurance system before been loaded into the production (Live) system.

This approach throws up the transport management system concept. Transport management system is the coordination of the movement of objects and configuration changes from the development system to the Quality Assurance system and then to the Production system. At times, this sequence of movement is not possible, especially in cases where an SAP note mandates that changes be made directly on the production system. In such rare cases, objectively confirm that the change transport cannot be performed. Very likely, your system must have been configured to "not modifiable" (a system locking strategy that enforces the three-system landscape change transport rule); unlock the system by changing the global setting option to "modifiable" using transaction SE03. After you have done that, effect the change(s) on the system. Immediately lock the system back by changing the global setting option to "not modifiable" using transactionSE03. Replicate the changes on the other system. Note that transaction SCC4 can also be used to lock the system so that client dependent and independent configuration changes are not carried out directly on the production system. By and large, the SAP system landscape ensures that the integrity of data is enhanced via enforcing a controlled configuration changes effect on the target system - production.