Skip to Content
avatar image
Former Member

system landscape

hai to all,

coul any one explain me what is system landscape , where and what situattion is is used while doing implimentation.

please reply, points are rewarded.

thanks

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

8 Answers

  • avatar image
    Former Member
    Feb 14, 2007 at 07:31 AM

    Hi Vijay

    Go thr below links for better understanding on Landscape:

    http://www.ryerson.ca/~ppille/sap/Resources/EnterpriseResourcePlanningSAP2.htm

    http://sap-img.com/general/what-is-sap--landscape.htm

    REWARD IF IT HELPS

    Regards

    Srini

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 14, 2007 at 08:19 AM

    hi

    In generally 3 system landscape.

    1.Devlopment client

    2.Quality client

    3.Production client - it used enduser.

    Rewards point it helps.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 14, 2007 at 09:58 AM

    Hi,

    The system landscape contains all systems that were installed. The customer can choose any landscape

    according to the requirements.

    If the customer is very big, one can implement four system landscapes. Mid size customers can go for two

    system landscape.

    Now we will see different system landscapes:

    Four System Landscape:

    In this landscape, we will find four systems,

    1) development system

    2) test system

    3) pre-production system

    4) production system

    In development system, we find three clients

    100

    140

    180

    100 can be used as configuration client. 140 can be used for development. 180 can be used for testing

    purpose in development system.

    The Test system contains two clients

    010

    040

    010 can be used for testing, where as 040can be used for training purposes.

    The pre-production system is the one which behaves exactly as production system. It contains data similar to

    production system. We can test with similar production data.

    Production system contains one client where the end users will be working with real time data supporting day

    to day business.

    -


    The R/3 architecture consists of 3 layers.

    The three layers are:

    Presentation layer

    The PC-based GUI interface that is used by the end-user community.

    <b>Application layer</b>

    The SAP application servers that service requests for data and manage the interface to the presentation layer.

    <b>Database layer</b>

    The actual DBMS that communicates with the application servers to fulfill their requests for data.

    A piece of "middleware" called BASIS links the application to the database and the operating system. BASIS is most commonly associated with the GUI interface to SAP (called SAPGUI), and the BASIS Administrator is an SAP professional who is responsible for configuring the SAP environment, including the GUI screens and the SAP application servers.

    SAP end users log into their PCs using SAPGUI, and are connected to a specific application server. This application server has pre-established connections with the Oracle database, and it services all requests for data. As I mentioned earlier, the access language for Oracle data is SAP ABAP. ABAP generates Oracle SQL (Structured Query Language), which is then used to service the end user's request for data. The communication between the application servers and the database, and between the client and the application servers, is TCP/IP.

    Also go through the link

    http://en.wikipedia.org/wiki/SAP_R/3>

    Mohan

    Award points if it helps.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 14, 2007 at 01:42 PM

    Hi,

    Just add some more info, Landscape is something which tells where and how our consultants work is carried out that it helps the enduser run their business on SAP.

    We have basically 3 servers, starting with a <b>Development server</b> where the abapers and consultants do the required customizations and configurations. Threre might be different clients in a Dev Server. Functional guys might work on one client where as developers might be working on one more. Also one more client is maintained which is a nearby replica of the production system, sometimes called as a Golden client.

    A <b>Test server</b> or a <b>Quality Server</b> where all the customizations ( development ) and configurations are tested for ok. The configurations and customizations done in develpment are moved to quality and tested. If found ok we have those developments moved to Production server where the enduser would be working.

    A <b>Production Server</b> where the actual enduser will be working. On this the developers and consultants are not allowed to make any kind of changes. Whatever is required with proper approvals they are developed in Development server, tested in Quality and have them moved to Production.

    To facilitate this kind of secured working environment a system landscape is setup with various servers.

    Hope it helps. Please reward if useful.

    Thanks & Regards

    Sadhu Kishore

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 14, 2007 at 01:59 PM

    Dear Vijay,

    System landscape is a concept and used to protect the mishaps on production server during the entire life cycle of the SAP projects.

    Depending upon the budget allocated and the need of the following the systems landscape is decided:

    1) In-house development of Forms, reports and enhancements (Development Server)

    2) Improve quality of the development activity (Add a Quality Server)

    3) Business Intelligence to be Implemented (Add a Server for BI)

    4) What to track pre and post project tasks through solution manager (Add another Server for SM)

    System landscape includes hardware, software, stragegy of operating hardware and software.

    The above a important during implementation.

    Hope this helps you.

    Best regards.

    Rajneesh Vaishnav

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 14, 2007 at 02:18 PM

    Hi,

    The system landscape contains all the SAP Systems that you have installed. It can consist of several system groups, whose SAP Systems are linked by transport routes.

    After you decide which clients you need and which roles you want them to have, you need to decide how to distribute them amongst the different SAP Systems. You can set up multiple clients independently of one another in a single SAP System. However, when you configure the data, you must remember that cross-client Customizing settings and Repository objects are identical for all clients in a single SAP System. Changes made in one client apply immediately to all clients in the system.

    SAP recommends 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.

    Make all changes to Customizing data and Repository objects in the Customizing client. When you release the corresponding change requests, they are transported into the quality assurance client. This means that changes to cross-client data only appear in the quality assurance client after the transport. In the quality assurance client you can test whether the transports are complete, or whether any linked changes are missing and are still in unreleased change requests. If the test is successful, the change requests are transported into the production client. The production client is completely separate from the other clients as regards cross-client data.

    If you need other clients with additional roles you can set them up in one of the three systems. Set up the development test client (TEST) and the prototype client (SAND) in the development system. Set up the training client (TRNG) in the quality assurance system.

    I hope this information will help you.

    regards

    kiran.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 14, 2007 at 03:19 PM

    Hi, Check this out.

    SAP R/3 Landscape

    for <customer>

    INTRODUCTION 3

    TERMINOLOGY 3

    R/3 SYSTEM LANDSCAPE FOR <CUSTOMER> 4

    R/3 Systems 4

    SAP Standard Clients 5

    SAP Clients for <customer> 6

    Client Copies - SCCL 7

    Client Copies of Change Requests - SCC1 7

    Transport of Change Requests - SE01 and STMS 7

    Description of how DEV clients are to be used 8

    Introduction

    The purpose of this document is to describe the SAP R/3 Landscape and Client Strategy for <customer>. The document outlines the R/3 systems and SAP clients that are defined, and describes their purpose.

    Terminology

    System Landscape - The System Landscape consists of all R/3 systems that share a

    common transport directory.

    R/3 System - An R/3 System consists of a central database server and the application servers attached to this central server.

    SAP System Identification (SAPSID) - The SAPSID is a unique three character code that

    identifies the R/3 System.

    Client - A Client is a legal and organisational entity in an R/3 System whose business

    management is protected against unlawful access. In addition a Client:

    • Has its own set of user data.

    • Is a logical system with separate master records.

    • Has its own set of table entries keyed by client.

    Customising - Methods in the R/3 System with which SAP's functionality is configured and

    tailored to fit an organisations needs.

    Development - Utilising the SAP development tool set to create SAP reports, interfaces,

    conversion programs and enhancements.

    R/3 System Landscape for <customer>

    R/3 Systems

    R/3 System System Role

    SAPSID Development Quality Assurance Production

    DEV X

    QAS X

    PRD X

    Development System: An environment where customising and development can be performed. Once all the customising and development changes have been unit tested, these changes can be transported to the Quality Assurance system for further system testing.

    Quality Assurance System: An isolated environment for testing the customising and development changes. When configuration has been thoroughly tested in this system it can be transported to the production system.

    Production System: A standalone production environment houses the organisation’s live data and where real business processes are performed.

    SAP Standard Clients

    The following tables describe the standard clients that are delivered with SAP R/3.

    R/3 System Client - Reference Description

    ALL 000 - SAPR SAP Reference

    001 - SAPS SAP Sample

    066 - SAPE SAP EarlyWatch Service

    999 - SAPG SAP Government Template

    Client Name Options

    000 SAP AG SAP Reference

    No changes allowed

    No changes to repository and client-independent customising objects

    Protection Level 1: No Overwritting

    001 Auslieferungsmandant R11 SAP Reference

    No changes allowed

    No changes to repository and client-independent customising objects

    Protection Level 1: No Overwritting

    066 EarlyWatch SAP Reference (Protected against SAP Upgrade)

    No changes allowed

    No changes to repository and client-independent customising objects

    Protection Level 1: No Overwritting

    999 Government Template SAP Reference

    No changes allowed

    No changes to repository and client-independent customising objects

    Protection Level 1: No Overwritting

    SAP Clients for <customer>

    R/3 System Client - Reference Description

    DEV 100 - CUST Customising

    200 - SAND Sand Box

    300 - TEST Unit Testing

    QAS 100 – INTG Integration Testing

    200 – TRNG Training

    PRD 100 – PROD Production

    DEV

    Client Name Options

    100 Customising Customizing

    Automatic recording of changes

    Changes to repository and client-independent customising allowed

    Protection Level 1: No Overwritting

    200 Sand Box Demo

    Changes without automatic recording

    No changes client-independent customising objects

    Protection Level 0: No Restriction

    300 Unit Testing Test (If Set to Productive it is not possible to use Client Copy Tools)

    No changes allowed

    No changes to repository and client-independent customising objects

    Protection Level 0: No Restriction

    Client Copies - SCCL

    Initial Client Setup During System Installation

    R/3 System Target Client Source Client

    DEV 100 – CUST 010 - SAPS

    200 – SAND 100 - CUST

    300 – TEST 100 - CUST

    QAS 100 – INTG 010 - SAPS

    200 – TRNG 100 - INTG

    PRD 100 – PROD 010 - SAPS

    Post System Installation

    R/3 System Target Client Source Client Frequency

    DEV 200 – SAND 300 - TEST Weekly

    300 – TEST 100 - CUST As Required

    QAS 200 – TRNG 100 - INGT As Required

    100 – INTG 100 - PROD As Required

    Client Copies of Change Requests - SCC1

    R/3 System Target Client Source Client Reason Frequency

    DEV 300 – TEST 100 - CUST Customising Changes Ad Hoc

    QAS 200 – TRNG 100 - INTG Customising Changes After QA Approval

    Transport of Change Requests - SE01 and STMS

    R/3 System Client Operation Frequency

    DEV 100 - CUST Export Transport Request After Unit Testing

    QAS 100 - INTG Import Transport Request As Required

    200 - TRNG Import Transport Request As Required

    PRD 100 - PROD Import Transport Request Production Ready

    Description of how DEV clients are to be used

    DEV/100: Customising settings are made in the CUST client to create a prototype system. All application customising occurs in this client. Only approved master data for customising purposes can be entered into this client. No transaction data should be entered in this client. System developments are transported from this client by assigning them to an appropriate development class.

    DEV/200: The entire implementation team has access to the SAND client for experimentation and education. System developments can be created in this client so long as they are assigned to $TMP.

    DEV/300: Copies of customising changes are moved to the TEST client from the CUST client for unit testing. Here unit testing can be performed before the customising changes are exported from the CUST client to the central transport host. This client will contain master and transaction data used to test the customising settings. Note that this data is not always reliable as it may have been created and the customising settings subsequently altered.

    Hope it helps.

    Raj

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 14, 2007 at 05:57 PM

    System Landscape is the methodlogy how the configuration will move from one client to another. Client here refers to different servers which can be in one box or multiple box.

    System landscape is as under:

    <b>Development Server</b> (also called as Golden Client, where configuration takes place. This is the place where consultants work primarily)

    <b>Test Server</b> (This is the place where the configuration is moved from development server for testing activity, so as to assure that the configuration is meeting the requirement or not. Here the consultant & core team checks & validates the working of scenario / requirement)

    <b>Production Server</b> (Once the testing is confirmed by core team, then the customization is transported from development server to production server, where the end user work with live data)

    Regards,

    Rajesh Banka

    Reward points if helpful.

    Add comment
    10|10000 characters needed characters exceeded