Scribd
Upload
6 views5 pages

System Land Scape-241022

The document outlines the system landscape for SAP, detailing the roles of Development (DEV), Quality Assurance (QAS), and Production (PRD) systems, along with their respective clients and transport request (TR) processes. It explains how configuration steps are copied between clients using TR numbers, the types of transport requests, and the importance of a Golden Client for maintaining perfect configurations. Additionally, it describes the Sandbox environment for practice and the sequence of TRs for moving configurations across systems.

Uploaded by

Sasi Preetham
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
6 views5 pages

System Land Scape-241022

The document outlines the system landscape for SAP, detailing the roles of Development (DEV), Quality Assurance (QAS), and Production (PRD) systems, along with their respective clients and transport request (TR) processes. It explains how configuration steps are copied between clients using TR numbers, the types of transport requests, and the importance of a Golden Client for maintaining perfect configurations. Additionally, it describes the Sandbox environment for practice and the sequence of TRs for moving configurations across systems.

Uploaded by

Sasi Preetham
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

System Land Scape

TR – Transport Request no – is a reference no for the


configuration steps done in a certain client. By using this no
– You can copy the configuration steps done in one Client to
any other client.
System Land Scape – is the arrangement of Servers or
Systems.
1. Development System (DEV)
2. Quality Assurance System (QAS)
3. Production System(PRD)

DEV QAS PRD


600 100
400
300 200

In Dev System we have TWO Clients as given below


Development Server
1. Development Client (600)– All the Functional
Consultants will log to this client with separate UN and
PW and do their respective configurations.
2. Unit Testing Client(300)- All the Functional Consultants
will log to this client with separate UN and PW and do
their respective Unit Testing.Unit Testing is Individual
module wise testing
The configuration steps developed in Dev Client will be
copied into this client by using TR no.
TC – SCC1 . This will be done by Individual FN
Consultant.we need to log on to Unit Testing Client and
use this TC
Quality Assurance System
This consists of the below clients
1.Integration testing Client (100)– All the Functional
Consultants will log to this client with separate UN and PW
and to do Testing of the all Business Processes related to all
the modules. This is testing among the Modules.
2.User Acceptance Testing Client(200) - All the Business User
will log to this client with separate UN and PW and do their
respective Testing of the Business Process.
The configuration steps developed in Dev Client will be
copied into this client by using TR no.
TC – STMS_IMPORT .This will be done by BASIS Consultant
The TRs are to be released in Dev Client , then only the TRs
will be transported to QAS and Production.
Production Server-
Production Client(400)-One fine day , All the configuration
steps developed in development client will be copied into
Production Client by using the Transport Request numbers.
From that onwards all the business user will log to this Client
to do their day to day activities in SAP Environment.
The configuration steps developed in Dev Client will be
copied into this client by using TR nos.
TC – STMS_IMPORT .This will be done by Individual BASIS
Consultant

Golden Client –
All the perfect configuration steps developed are maintained
in a separate server. In the event of failure of the servers, the
configuration steps can be copied into any of the client.

Sandbox – This is a separate system for Practicing purpose

Transport Requests-
Two Types –
1. Customizing Request –The TRs belonging to Functional
Consultants -
2. Workbench Request- The TRs belonging to Technical
Consultants –ABAP
TC – SE09/SE10
Modifiable- This TR can be used to save the further
configuration steps when the status is Modifiable
Released – once the TR is released in Dev System – This TR
cannot be used to save further configuration steps
BASIS -Sequence of TRs to be moved- ABAP –FI-MM-
SD-PP-QM-PM
Before a moving the TR from Dev Client to QAS / PRD – we
have to release the TR in Dev Client
TC-SE09
Select the TR Task

You might also like