P. 1
SAP Landscape

SAP Landscape

|Views: 99|Likes:
Published by rahulkajave

More info:

Published by: rahulkajave on Jul 16, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

03/18/2013

pdf

text

original

SAP R/3 Landscape

for <customer>

.......................................................8 SAP Landscape Page 2 ...............................................4 SAP Standard Clients...........3 R/3 SYSTEM LANDSCAPE FOR <CUSTOMER>..................................7 Description of how DEV clients are to be used....................................................................................................SCC1..................................................2 INTRODUCTION...................................................7 Transport of Change Requests .............................................................................................5 SAP Clients for <customer>.....................Table of Contents TABLE OF CONTENTS.......................................................................................................................................4 R/3 Systems................................................7 Client Copies of Change Requests ...............3 TERMINOLOGY.......................SCCL..............................................................................SE01 and STMS..............................6 Client Copies .................................................................................................................

Client .A Client is a legal and organisational entity in an R/3 System whose business management is protected against unlawful access. Is a logical system with separate master records.The SAPSID is a unique three character code that identifies the R/3 System.An R/3 System consists of a central database server and the application servers attached to this central server. conversion programs and enhancements. Has its own set of table entries keyed by client. Terminology System Landscape . In addition a Client: • • • Has its own set of user data. SAP System Identification (SAPSID) . The document outlines the R/3 systems and SAP clients that are defined. interfaces. Customising .Introduction The purpose of this document is to describe the SAP R/3 Landscape and Client Strategy for <customer>. R/3 System . Development .Utilising the SAP development tool set to create SAP reports.Methods in the R/3 System with which SAP's functionality is configured and tailored to fit an organisations needs. and describes their purpose.The System Landscape consists of all R/3 systems that share a common transport directory. SAP Landscape Page 3 .

SAP Landscape Page 4 . Once all the customising and development changes have been unit tested. Production System: A standalone production environment houses the organisation’s live data and where real business processes are performed. these changes can be transported to the Quality Assurance system for further system testing.R/3 System Landscape for <customer> R/3 Systems DEV QAS PRD R/3 System SAPSID DEV QAS PRD Development X System Role Quality Assurance X Production X Development System: An environment where customising and development can be performed. When configuration has been thoroughly tested in this system it can be transported to the production system. Quality Assurance System: An isolated environment for testing the customising and development changes.

SAPS 066 . R/3 System ALL Client Reference 000 .SAP Standard Clients The following tables describe the standard clients that are delivered with SAP R/3.SAPE 999 .SAPG Description SAP SAP SAP SAP Reference Sample EarlyWatch Service Government Template Client 000 Name SAP AG 001 Auslieferungsmandan t R11 Options SAP Reference No changes allowed No changes to repository and clientindependent customising objects Protection Level 1: No Overwritting SAP Reference No changes allowed No changes to repository and clientindependent customising objects Protection Level 1: No Overwritting SAP Reference (Protected against SAP Upgrade) No changes allowed No changes to repository and clientindependent customising objects Protection Level 1: No Overwritting SAP Reference No changes allowed No changes to repository and clientindependent customising objects Protection Level 1: No Overwritting 066 EarlyWatch 999 Government Template SAP Landscape Page 5 .SAPR 001 .

TEST 100 – INTG 200 – TRNG 100 – PROD Description Customising Sand Box Unit Testing Integration Testing Training Production 200 Sand Box 300 Unit Testing Options Customizing Automatic recording of changes Changes to repository and client-independent customising allowed Protection Level 1: No Overwritting Demo Changes without automatic recording No changes client-independent customising objects Protection Level 0: No Restriction 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 SAP Landscape Page 6 .SAP Clients for <customer> DEV 100 – CUST 200 – SAND 300 – TEST QAS 100 – INTG 200 – TRNG PRD 100 .PROD R/3 System DEV QAS PRD DEV Client 100 Name Customising Client Reference 100 .SAND 300 .CUST 200 .

SE01 and STMS R/3 System DEV QAS Client 100 .CUST 100 .INTG 010 .TEST 100 .SCC1 R/3 System DEV QAS Target Client 300 – TEST 200 – TRNG Source Client 100 .SCCL Initial Client Setup During System Installation R/3 System DEV QAS PRD Post System Installation Target Client 100 – CUST 200 – SAND 300 – TEST 100 – INTG 200 – TRNG 100 – PROD Source Client 010 .CUST 100 .PROD Frequency Weekly As Required As Required As Required Client Copies of Change Requests .INTG 200 .INGT 100 .Client Copies .TRNG PRD 100 .SAPS R/3 System DEV QAS Target Client 200 – SAND 300 – TEST 200 – TRNG 100 – INTG Source Client 300 .SAPS 100 .PROD Operation Export Transport Request Import Transport Request Import Transport Request Import Transport Request Frequency After Unit Testing As Required As Required Production Ready SAP Landscape Page 7 .INTG Reason Customising Changes Customising Changes Frequency Ad Hoc After QA Approval Transport of Change Requests .CUST 010 .CUST 100 .SAPS 100 .CUST 100 .

System developments are transported from this client by assigning them to an appropriate development class. SAP Landscape Page 8 . No transaction data should be entered in this client. All application customising occurs in this client. Only approved master data for customising purposes can be entered into this client. Note that this data is not always reliable as it may have been created and the customising settings subsequently altered.Description of how DEV clients are to be used DEV/100: Customising settings are made in the CUST client to create a prototype system. This client will contain master and transaction data used to test the customising settings. Here unit testing can be performed before the customising changes are exported from the CUST client to the central transport host. 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. DEV/200: The entire implementation team has access to the SAND client for experimentation and education.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->