SAP Landscape

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

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 development is done is development client and the request is
transported to production.

These three are landscape of any Company. They organized 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.

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
SAP Tickets
Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to
the support team are prioritized under three severity High, Medium and Low. Each and every
severity as got its time limits before that we have to fix the error.
The main job of the supporting consultant is to provide assistance on line to the customer or the
organisation where SAP is already implemented for which the person should be very strong in the
subject and the process which are implemented in SAP at the client side to understand,to
analyse,to actuate and to give the right solution in right time.This is the job of the support
consultant.
The issues or the tickets(problems) which are arised is taken care of on priority basis by the
support team consultants.
The work process in support projects are given below for your reference.
1. The customer or the end user logs a call through any tool or by mail (RADIX).
2. Each one of the support team is a part of support group.
3. Whenever a customer logs a call he /she has to mention to which work group (by name).
4. Once the calls came to the work group the support consultant or the team need to send an IR
(Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None)
5. Then the error is fixed, debugged by the support consultant or the team. Then after testing
properly by generating TR(Transport Request through the basis admin)
6. Then it is informed to the end user/customer/super user about the changes which have moved
to the production server by CTS process.
These are the process. In summary, what I understand is that if any configuration or
customization is required to solve the issue, then the consultant have to work on DEV Client, then
the end user will test it in the QA client and after approval the BASIS consultant has to transport
it to the PRODUCTION client.
An example:

Tickets in SD can be considered as the problems which the end user or the employee in the
company face while working on R/3. Tickets usually occur during the implementation or after
the implementation of the project. There can be numerous problem which can occur in the
production support and a person who is working in the support has to resolve those tickets in the
limited duration, every ticket has the particular deadline alert so your responsibility is to finish it
before that deadline.
To begin with , we should give "TICKET" to you for not knowing it.
Here is an eg of a ticket raise:
End user is not able to
1. Create sales order for a customer from a New plant , since shipping point determination is not
happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be
able to proceed further like DELIVERY, BILLING).
He raises a ticket and the priority is set in one of the below:
1. Low 2. Medium 3. High.
Now you need to solve this ticket. You would analyze the problem and identify that the SP
configuration has to be done for the new plant.
You would request a transport for DEV CLIENT to BASIS. You do the change and Request one
more Transport to BASIS for QA client. The End user will test the same by creating a sales order
for the new plant and approve it.
Finally, you request a transport to move the changes to PRODUCTION. Once the change is
deployed in production the TICKET is closed.
The Same Procedure is followed for SAP MM Tickets.

What is roll out of SAP Project?

As per SAP specific definition, rollout is the strategy for international SAP implementation.
Rollout strategy normally include the following

- Whether to implement SAP simultaneously (also known as big-bang) in all the countries, or
- Go live in sequence of phased manner
- Or to go for the combination of both (phased manner implementation for some of the countries
and big-bang for others).

Rollout strategy is the most important decision that a client can make during SAP
implementation. Normally, steering committee decides the rollout strategy.