Topic 2: Landscape of SAP HR (Systems info)

[freesaphr]

Before we go to Screen shots of SAP, Lets learn Landscape of SAP HR & other info

Landscape means basically SAP Systems information, like where the Developers will config the SAP HR MODULES and where the Quality will check and finally where the client will use the output.


SAP HR Have total 3 Servers

(We can say systems, like one system will have 3 servers)

[freesaphr]

SAP HR Servers


Development Server
Quality Server
Production Server

Process:

First Configures will config the SAP HR sub-modules (Payroll, Time management, PA, OM...) in Development system.

They will save what ever they done in a TRANSPORT REQUEST (TR)

Then they will move the saved info to QUALITY System with help of BASIS (Basis is other SAP Module like ABAP, HR, FICO...)

Once the quality people check and conform the saved info (TRANSPORT REQUEST) will move PRODUCTION system (Where Client can assess and they can use for there operations once GO-LIVE done)

[freesaphr]

Every company have there own naming conversation for servers.


1. Development Server - *D1

Where.,

D denoted Development server

* is denotes the country server, like
Asia Pac - A, North America - N, Europe - E

Example: If you are doing implementation for Europe client - ED1, if for North America - ND1 same for Asia Pac- AD1



2. Quality Server - *Q1

Where.,

Q denoted Development server

* is denotes the country server, like
Asia Pac - A, North America - N, Europe - E

Example: If you are doing implementation for Europe client - EQ1, if for North America - NQ1 same for Asia Pac- AQ1



3. Production Server - *P1

Where.,

P denoted Production server

* is denotes the country server, like
Asia Pac - A, North America - N, Europe - E

Example: If you are doing implementation for Europe client - EP1, if for North America - NP1 same for Asia Pac- AP1

[freesaphr]

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 lanscape 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 practised 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.

1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you do all the configuration/customization as per the companies business process.

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


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

Application Server - Where SAP Installed.

Database Server - Where Database installed.

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

Why do we call client 000 as golden client?
Golden client contains all the configuration data and master data so some extent. All the configuration settings are done in golden clients and then moved to other clients. Hence this client acts as a master record for all transaction settings, hence the name "Golden Client".

One of the most basic concepts in SAP is that of "Client". A client is defined as a legally and organizationally independent unit within SAP R/3. For purposes of SAP R/3, a client can be company, corporation or even a business unit. One of the first things SAP asks for at the time of login is the client number. SAP R/3 comes inbuilt with three standard clients viz. 000, 001 and 066. Let us see all the three different client's in SAP R/3 in detail.


Clients in SAP R3 - Concept of Client in SAP R/3



Client 000 - Client 000 is a special client in SAP since it has client independent settings. Client 000 in SAP R/3 comes with a simple organizational structure. It is a sort of test company. Client 000 contains all standard configurations, parameters, standard transactions, etc that are normally used in the SAP R/3 business environment.

Client 001 - Client 001 is a copy of client 000. Client 001 also includes a test company. Client 001 can be customized to prepare it to move it into the production environment. However, once client 001 is customized, it does not behave like client 000.

Client 066 - Client 066 is used to perform "Early Watch" service for customer systems.

One important thing to remember is that during SAP R/3 implementation, once SAP is installed, the first thing to be done is copy a standard client included in SAP R/3 package. With the help of this, SAP users can start using SAP for creating tests, training, or even start using it for customization.

[hasan869]

In *D1, what does 1 mean?

Is it also a variable or a constant?

Originally Posted by freesaphr

Every company have there own naming conversation for servers.


1. Development Server - *D1

Where.,

D denoted Development server

* is denotes the country server, like
Asia Pac - A, North America - N, Europe - E


Example: If you are doing implementation for Europe client - ED1, if for North America - ND1 same for Asia Pac- AD1




2. Quality Server - *Q1

Where.,

Q denoted Development server

* is denotes the country server, like
Asia Pac - A, North America - N, Europe - E


Example: If you are doing implementation for Europe client - EQ1, if for North America - NQ1 same for Asia Pac- AQ1



3. Production Server - *P1

Where.,

P denoted Production server

* is denotes the country server, like
Asia Pac - A, North America - N, Europe - E


Example: If you are doing implementation for Europe client - EP1, if for North America - NP1 same for Asia Pac- AP1