Hi,
SAP Architecture is basically how the SAP is structured. Basically it is a client Server Architechture. In this if you look at it, there are two views, one is Software-Oriented and the other one is Hardware Oriented.
In software Oriented view we have Presentation Layer, Application Layer, and the Database Layer. Presentation layer is the one we sit and work on the screens i.e., GUI (Graphical User Interface). At presentation layer we don't know what exactly happens inside. we just know whether we are getting proper output or not.
Application Layer is the one where all applications, i.e., programs etc. This is where the actual programs are written either by SAP (which are hardcoded or by ABAPer)
And finally, Database Layer. this is where all our actual data is stored. SAP uses Oracle for this.
The R/3 System architecture allows you to separate application from the presentation and the database. This is the prerequisite for distributing load onto several application servers in client/server configurations. Therefore, the system can be distributed, in hardware terms, at three different levels.
This architecture means that the installed host service can be adjusted without any problems(scalability), especially where load profiles have changed as a result of increasing user numbers, or because additional components have been used. R/3 System scalability provides you with flexibility when choosing hardware and software.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.