Professional Documents
Culture Documents
1.Quality Assurance (QA)server:- Quality server is where the team members and other members test the
new customization, programs etc. ... It is the server where the live data of the company is recorded after
project go live.
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.
In the Development system the SAP ERP is being configured: Customizations are done by the different
processes consultants, developments are done by the programmers, etc. The main system is the Production
system - this is the system where the end-users work.
QAS is Quality Server, while Implementing SAP there will be different servers... Development, Quality and
Production... Development will be done at the Development server and once tested and found acceptable will be
transported to Quality where testing is done again and then Transported to Production Server where the end user
will work.
Create RFC enabled FM. Create a RFC destination using SM59 which will be pointing to the Application
server on Quality system. You will need to provide the user name and password for the Quality system in
the destination having enough authorizations to fetch the data from tables.
Three-System Landscape
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.
Their first commercial product was launched in the year 1973 and was based on the tier system like the
one-tier system was called SAP R1 and the two-tier system was called SAP R2 and the three-tier
system was called SAP R3.
A system landscape consists of Development Server (Dev), Production Server (PROD), and
Quality Assurance server (QAS). SAP Architecture is defined as a technology framework of SAP
system and it changes with time unlike the system landscape.
The basic difference between a development server and a quality server are as
below:
1. Customisation and ABAP developments are done by consultants and tested
in development server whereas they are tested by the core team / business
users in the quality environment
2. In a 3 tier structure (Dev > Qlty > Production) a client refresh is usually
done from Prodcution to Quality only
Serverr
Difference between Quality Server and Development Serve
SAP has a methodology of running a project called as ASAP methodology. As per this methodology,
common practise is to create a 3 or 4 system landscape. SO normally there will be Sandbox system
(rough work system), Golden client (configuration stored here), Development system (Development
work done), Quality System (Most of testing goes here) and Production system (real-time server). Work
done will be moved from one system to other using Transport Requests (TRs) which will be generated
when you do any changes in any system.
Sandbox is like rough work system where you can do the configuration as per the clients requirements.
In Sandbox, most of times TRs will not be generated but BASIS consultant can make TRs compulsory
here too if needed. In some SAP customers, this system might not be there. Configuration will be done
in DEV system only but wrk will be segregated as different TRs.
Develoment system is where the complete configuration will be done. Mos of time Unit testing goes in
DEV system only unless Client is specific to test everything in QAS system. Once the configuration is
done, tested in QAS system by consultants and by client’s SAP consultants or end-users; then it will be
moved to PRD and Golden client.
Quality System is used to test the whole configuration; technically and functionally. Without proper
testing, there will be lot of errors in Production system. That is not acceptable by any client. SAP
consultants will have complete ‘Change’ access upto here. In the remaining Production client and
Golden Client, functional consultants will not have ‘Change’ access but only ‘Display’ acces just to see
what is going on. In some clients, technical consultants (ABAP, BW, etc.) will not have any access to
production. Only BASIS consultants will move the TRs generated by technical consultants to Production
system.
Production system is where real-time things happen. End-users in client will start posting accounting,
MM, SD, PP and other implemented modules as part of configuration done in DEevelopment system.
TRs will be moved from Develoment to Production once testing is complet in Quality system. If there is
any issue in the Production system, end-users wil raise that as a ticket with a priority label attached to
it. You as support SAP consultant must look into the issue by loggin into Production where you have
only ‘Display’ access. Looking at the issue, do the necessary changes in Develoment system, generate
the TRs, move it to quality system, do the testing, ask the end-user to do the same and once
confirmed, move the TR to production to mitigate the error.
System Landscape & Architecture
SAP system landscape is defined as an arrangement of SAP servers. Ideally, in a Sap environment,
a three-system landscape exists. A system landscape consists of Development Server (Dev),
Production Server (PROD), and Quality Assurance server (QAS).
SAP Architecture is defined as a technology framework of SAP system and it changes with time
unlike the system landscape. SAP Architecture changes with new software like SAP ECC 6.0, the
most recent one.
The following is a request in SAP System Landscape −
DEVELOPMENT >>>> Quality >>>> PRODUCTION
The following figure represents SAP three tier system landscape where work flows from Dev > QAS
> PROD and not in backward direction.
Sandbox Server
When a project is implemented, at the initial stages, a sandbox server is used where all the
customization, configuration is performed.
Development Server
Next is to save the configuration in development server and saved in workbench requests and this
has to be transported to Production server.
Production Server
You can consider it as the final or the most refined stage where the work is done when project is in
production/go live. All the changes that are required by the client are performed in the DEV
environment and later, the request is transported to production.
SAP System 3 – Tier Architecture
The image given below shows 3-tier architecture of the SAP system. The presentation layer is
the topmost one. This contains the device/application to control the SAP system. This can include
mobile devices, end user systems or SAP GUI or web browser based client.
The presentation layer communicates with the application server to perform all the processing and
which is known as brains of an SAP system.
An application server consists of multiple instances and communicates with the database layer of
the three-tier architecture.
The bottom layer is called the database layer. This is responsible to store all the data. The
database of SAP system is kept on a separate server for performance and security reasons.
The presentation layer consists of different components for ABAP and JAVA that enables the
communication and processing of data in SAP system.
The key components of the presentation layer include the following −
Message Server − This is used to manage communication between distributed dispatchers in the
ABAP system.
Message Server − This is used to manage server processes and JAVA dispatchers. It is used to
manage communication within JRE.
Dispatcher Queue − This is used to store multiple work process types.
Dispatcher − This is used to distribute the requests to the work processes.
Memory Pipes − This is used to manage communication between ICM and ABAP work processes.
Enqueue Server − This is used to handle logical locks set by the executed Java application
program.
Java Dispatcher − This is responsible to receive the client requests via presentation layer and
forward to the server process.
Gateway − This is used to manage communication between SAP system and external systems.
ABAP Work processes − This separately executes dialog steps in R/3 applications separately.
What are the roles of Sandbox, Golden client, development, unit test,
QA, and production in SAP’s server landscape?
You have three servers part of SAP landscape. DEVELOPMENT | QUALITY | PRODUCTION
Part of DEVELOPMENT you have SANDBOX client / GOLDEN client / UNIT TESTING client
Landscape can vary from client to client but above are the minimum set up.
What are the roles of Sandbox, Golden client, development, unit test,
QA, and production in SAP’s server landscape?
Generally in SAP system practices, 3 different landscapes/clients are used.
Landscape/clients : is the arrangement for the servers,are basically logically discrete or separate
subsystem within SAP system. These can be considered as logical sub-units within SAP system.
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 landscape DEV, QAS and PRD.
– DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180 – Unit Test.
– QAS may again have multiple clients for ex: 300- Integration Test, 700 to 710 Training.
– PRD may have something like a 200 Production.
These three are landscape of any Company. User is given access to specific client based on business
unit that user belongs to, geography or roles & responsibility assigned to user. They organize their
office in these three way. Developer develop their program in Development server and then transport
it to Quality Landscape via Transport request. In Quality server tester check/test the program and then
transport it to Production Server via the same Transport Request created in Development Client. Later
it will deploy to client from production server.
A request will flow from Dev -> Qual -> Prod and not backwards.
As per the above pictorial representation of the three landscapes in SAP, the below can be called as
different segments of Development landscape itself.
1. Sandbox is a server which can be said to be a playground for trying and testing
configuration and scenario. This server will have Master Data and Transaction Data.
2. Golden Client is a server which will only have configuration and a clean server with
only relevant configuration. Configurations are nothing but Customizing data. This
server will not have Master Data and Transaction Data.
3. Unit testing client has the data of both Sandbox and Golden client, where
configurations are imported from golden client and testing of the repository objects is
done here before moving the object to Quality landscape.
Types of servers
Types of servers and its working applications can understand by the System Landscape . System landscape
contains all systems( two System landscape or three System landscape or Four System landscape) 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.
1) Development system
2) Test system
3) Pre-Production system
4) Production system
1) Development system
2) Test system
3)Production system
2)Production system
100
150
200
100 can be used as configuration client. 150 can be used for development. 200 can be used for testing
reference of configuration.
The Test system contains two clients
250
300
250 can be used for testing, where as 300 can be used for training purposes to endusers.
400
450
400 is the pre-production client which behaves exactly as production client. It contains data similar to production
client. We can test with similar production data.
450is the production client where the end users will be working with real time data supporting day to day
business.
Once you finish the configuration in Development Server according to your business requirement, all TRu2019s
are transported to Quality Server and you can test here client business Process. If its working fine, then all
TRu2019s are transported to Production Server from Development Server
What are the roles of Sandbox, Golden client, development, unit test,
QA, and production in SAP’s server landscape?
You have three servers part of SAP landscape. DEVELOPMENT | QUALITY | PRODUCTION
Part of DEVELOPMENT you have SANDBOX client / GOLDEN client / UNIT TESTING client
Landscape can vary from client to client but above are the minimum set up.
SAP MM Project Landscape Servers & Clients Full Details
Ø SAP Landscape is the SAP SE System environment where the SAP project is
implemented. SAP BASIS Consultant prepares the landscape like Development Server,
Quality Server, and Production Server. SAP system clients are created for different
purposes.
Ø SAP Server- SAP Software Version (ECC 6.0 (EHP6)
Ø SAP Client- 310, 320, 330…210,220,230…100 (Particular SAP System)
Development Server
Quality Server
Production Server
SAP ECC 6.0 (EHP6) SAP ECC 6.0 SAP ECC 6.0
(EHP6) (EHP6)
320- Configuration
Client 220- Quality
Client
330- Development
Test Client 230- Training
Client
Overview of SAP MM Project Clients
310- Sandbox Client
Provided to SAP Consultants to test and practice business scenarios. This client is used for
self-practice by SAP Consultants.
320- Configuration Client
Configuration is done as per the business blueprint. The project is developed for this client.
Base configuration (Enterprise Structure) and the final configuration is done in this client.
This client is also called Golden Client.
330- Development Test Client
Testing is performed by SAP consultants who develop the project. Unit testing and
Integration testing are done as per the business process master list (BPML).
210- Testing Client
Testing Sheet is prepared and testing is conducted by the core team member/module lead
(employee of the company). Testing is the process of post-transaction and checks reports.
220- Quality Client
All business process is shown to company and User Accepting Test (UAT) is taken by SAP
Consultants from the company. UAT is the process of taking approval of the business
process from the company.
Sandbox : The word sand means draw something on it and rub it if do not match or meet the correct figure.This
is the place we can do anything and doesn't effect on other servers or clients.In the Initial stage of the
implementation project you have given a sandbox server to do all the configuration or customization based on
companies requirement.
Golden client :In this place the real configuration has done as per the requirement.If satisfied with
configuration,they transport it to the quality server for testing and if not they re-do the configuration to meet the
requirement.This is very clean and neat client we cannot use it for rough usage like the sandbox.Master data
cannot configured in golden server.
If you configure/customize the work and when u save the work the system generates the Alpha-numeric
number is called Transport Request (TR).
Unit test : Here we test the development and configuration changes before we transport them into the another
system or server.
Integration testing : If we done a transaction on one module (ex : MM) it will be affected on other function
modules of sap server.So to identify the affected modules based on the transaction we do Integration Testing.
Production Server (PROD)
This is the client where the business people will work after project Go-Live.It is a live system where business
processes are executed.
The below diagram can give the summary information about the 3 servers.
Functional/Technical consultants can have direct access to development sever .Some times they will have
chance to access Quality server.
Sap QA people can work on Quality server only.
Sap do not recommend one system landscape containing all clients (Development,Quality and Production) in a
single system.If the system is used productively,you can no longer develop in it and test in it unless you stop
productive operation.
2. Two System LandScape
In this land scape system Quality assurance clients also included in the development system DEV.The
disadvantage of two system landscape is cross-client data is used in both customizing and quality assurance
clients.This means that any changes in the cross-client data customizing client can affect the tests in the quality
assurance.
If we do change the data in Customizing (Golden) client ,the transport(Change) request will be generated
.When you release the transport request , then it is transported to Quality assurance client.In the QAS the testing
will be done by the QA people.If the test is successful then the TR will be transported to Production client.
What is SAP Landscape?
Just try to understand the system sap landscape, Every company follows their own landscape
as a standard you will have three servers like development, quality assurance and production
server.
What ever configurations u have to do u will do it in dev server and in the quality you make
some testing for the tasks and once you think the work is good you can move that to
production server you will find different clients in each server again as u find golden config
client, abap dev client, unit testing client in dev server, u will have master config client,
integration test client, training client in qa server and u will find only one client i.e. prod client
in prod server.
It is mandatory for you to know about the servers and clients before you claim any
experience.
Sap Landscape
Sap Landscape basically is the system setup of SAP.You should say that Development server,
then Quality server and then Production server, no. of users.
To be more specific you can list the clients also in a particular server:
It also comprises of your SAP landscape (systems) cape itself like Development system,
Quality system, Integration system and Production system. You can include the modules,
which are supporting
Production server
A production server is a server used to host website content and applications
for deployment to a live environment. It is the main server on which websites and Web
applications are accessed by end users and is also referred to as a live server.
DESCRIPTION
SAP Server is a 'Production Server'
APPLIES TO
Central/Foundation with Transaction, Query, Journal Entry, Runner
10.X
2. You are attempting to run a script/template on a production SAP server, the script/template is not in
production status.
Solution: The script/template will need to be approved and in production status before you will be able to
run in production SAP.
3. You are attempting to run a script/template on a production SAP server, the script/template is in
production status.
Solution: You may not have permission to run in this SAP system. Please reach out to your Central admin so
that you can be added to the allowed users or groups for this system.
You do not have permission to record/run in production for one or a combination of the 3 reasons above.