Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

System Landscape

Former Member
0 Kudos

Hi all,

Pls let me know about System Landscape in detail.

Thanks and regards

Nandha

3 REPLIES 3

former_member181962
Active Contributor
0 Kudos

In plain jane terms, System landscape is the the collection of all the business systems within your firewall boundary.

For example, if your company has Peoplesoft to manage HR appilications, SAP R/3 to maintain SD and MM and Oracle system to maintain the FI data and a Seibel system to mainatin CRM related data, then your landscape is said to contain all these business systems.

Regards,

Ravi Kanth Talagana

Former Member
0 Kudos

Hi Nandha,

A landscape represents a logical, complex system, which consists of multiple, distributed components. Some of these components may be systems; others may be services, installed products, or other managed elements.

The following types of landscapes are defined in the SLD:

· Administration

A system landscape, which is created for administration purposes, for example, for common monitoring.

· General

A system landscape, which can contain all types of application systems.

· NWDI Systems

A system landscape that contains servers of the NWDI. The NWDI consists of a local client – the Integrated Development Environment (IDE) and some logical servers for processes like source management, build tasks, transport, and name reservation. All servers work together and require a common user base together with the IDE.

· Scenario

A system landscape that is created for a specific business scenario. Scenario landscapes are used in the Software Lifecycle Manager of SAP NetWeaver.

· Transport

A system landscape that is created for transport purposes. For example, all SAP Web AS systems that are connected by an ABAP transport path distributing the ABAP development.

· Web Service

A system landscape that is created to collect systems offering Web services and their clients. The hierarchy of these landscapes defines the Web service that is most appropriate for a given client.

Check this link for further information:

http://help.sap.com/saphelp_nw04s/helpdata/en/42/c099d518cf1d66e10000000a1553f6/frameset.htm

Hope it helps u.

Regards,

KK

Former Member
0 Kudos

Hi

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.

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

http://help.sap.com/saphelp_nw04/helpdata/en/31/f0ff69551e4f259fdad799a229363e/content.htm

http://blogs.ittoolbox.com/sap/kehinde/archives/understanding-the-sap-system-landscape-14030

<b>Reward if usefull</b>