Showing results for 
Search instead for 
Did you mean: 


Former Member
0 Kudos

hi....SD masters,

Can any body tell what exact difference between System Land Cape,

R/3 Achitechture and also Client Architechture.....if possible with Examples also..

I faced this question in interview....



Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos


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 : 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.

R/3 Achitechture

Client - Application Layer - Database Layer

Client Achitechture

Client1 -


Client2 -


<b>Reward If Useful</b>

Thnx & Regards


Former Member
0 Kudos

system landscape:

SAP recommend a three-system landscape in which each of the central clients has its own SAP System.

This consists of a development system DEV, a quality assurance system QAS and a production system PRD. The development system contains the Customizing client CUST, the quality assurance system contains the quality assurance client QTST and the production system contains the production client PROD.

r/3 architecture :

it refers to

1.application layer

2.database layer

3.presentation layer.

reward points


Former Member
0 Kudos

see in System Land Cape u have servers like Development server,Q & S server,and

prodiction serner.

under Development server u have clients like 020 - golden,045-regular,050-sandbox.

see Golden client is clean and neat client u should not do any thing here,

u can do what all the development in 050-sand box and after testing u can transport to 020-golden once transported that data canot be change.

in 045- regular u can do development...

in Q&A testing is dont both unit and integration tests.

before Go-live the data has to transport to production client..

if u come accross R/3 Achitechture here u have 3 - layers base layer - (for processing SAP applications if any data needed that can be retrived from data base)

2.application layer - (SAP applications are processed)

3.presentation layer - (SAPGUI-interface)

Client Architechture - it is nothing but R/2 or R/3(client intended Architechture)

example of R/2 - Database layer and application layer will in one PC

and presentation layer will in one PC

for R/3 -the all three layers will in 3 diffrent PC's

that what i know