Landscape means basically SAP Systems information, it is where the Developers will configure the SAP HR MODULES and where the Quality Analyst will check and finally where the client will use the output.
SAP HR Have total 3 Servers
- Development Server
- Quality Server
- Production Server
Process:
First the functional analyst configures the SAP HR sub-modules (Payroll, Time management, PA,
Functional Analyst saves the work done in development server in a TRANSPORT REQUEST (TR) (Transport request is a process to transport objects from one system to another using objects.)
The saved information is then moved to the QUALITY Server with help of BASIS (Basis is other SAP Module like ABAP, HR, FICO...)
Once the Quality Analyst has checked and conformed the saved information (TRANSPORT REQUEST) it is moved to PRODUCTION system (Where Client can assess and they can use it for operations once they GO-LIVE ).
Every company has there own naming convention for servers.
1. Development Server - *D1
Where D denotes Development server
* is denotes the country server, like Asia Pac - A, North America - N,
Example: If you are doing implementation for Europe client - ED1, if for
2. Quality Server - *Q1
Where Q denotes Development server
* is denotes the country server, like Asia Pac - A, North America - N,
Example: If you are doing implementation for Europe client - EQ1, if for
3. Production Server - *P1
Where P denotes Production server
* is denotes the country server, like Asia Pac - A, North America - N,
Example: If you are doing implementation for Europe client - EP1, if for
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 would have multiple clients for ex: 190- Sandbox, 100- Golden, and 180- Unit Test.
- QAS may again have multiple clients for ex: 300- Integration Test, 700 to 710 Training.
- PROD may have something like a 200 Production.
These names and numbers are at the implementer's discretion on how they want to use it or they have been using in their previous implementations or how is the client's business scenario./needs.
Any change to 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 every time. 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) clients. This is a configuration only client. Now upon a successful transport by the SAP BASIS consultant, 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.
In the Testing client you can not 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 Client) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular configuration is satisfactory.
The Golden client remains the 'database' 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 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->Quality->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 company’s 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 development is done in development client and the request is transported to production.
The above three are landscape of any Company.
A developer develops the program in Development server and then transports it to test server. In testing server testers check/test the program and then transport it to Production Server. Later it will deployed to the client from production server.
- Presentation 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 real-time three tier architecture. This is the kind of architecture 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 to 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, thus the name "Golden Client".
Creating Transport Requests
Use
You want to create a transport request in the development system where your software changes have to be recorded.
Prerequisites
A maintenance cycle or an urgent correction exists whose status is Active.
Your user profile contains at least the authorization of SAP_CM_SMAN_DEVELOPER role in change request management system.
If you execute this task from within a change request, you need at least the authorizations of t he SAP_SOCM_DEVELOPER role in the Change Request Management system. If you execute this task from within the Schedule Manager, you need at least the authorizations of the SAP_CHANGEMAN_OPERATOR role in the satellite system.
Procedure
The steps in this procedure refer explicitly to maintenance cycles; however, you can also use this procedure for urgent corrections. If you want to do so, select an urgent correction instead of a maintenance cycle. You can also execute this task from within a change request. In this case, a transport request that contains default values is created.
To create a transport request from within a maintenance cycle, proceed as follows:
1. Call transaction /TMWFLOW/CMSCONF.
2. Choose Scheduling.
3. On the Maintain. Cycles tab page, select Display Existing Maintenance Cycles. The system displays a list of the maintenance cycles whose status is Active (default setting). To select or activate cycles with other statuses, see Changing the Status of Task Lists.
4. Click the maintenance cycle for which you need to create a new transport request.
5. Under the task node of the development system, select Create Transport Request, and then start the act ion by clicking with the quick info text Execute task.
6. On the screen t hat appears, enter the owner of the request you want to create and a short text for the request. You can also add developers to whom you want to assign transport tasks within this request. If you do not enter these parameters, a request is created that contains your user as the owner, a single task for your user, and a generated short description. After the transport request has been created, the task list for the maintenance cycle is displayed again.
7. Check the status of your task. If you need more information about the task, check the application log in the Daily overview of the task list.
In the selected development system two transport requests (a workbench and a Customizing request) are created for the specified owner and developers. In the case of urgent corrections, only one open workbench and one open Customizing request are permitted at any time. The created transport requests are connected to the maintenance task list. The transport requests are provided with the transport request attributes SAP_CTS_PROJECT (which contains the CTS project ID) and SAP_TMWFLOW (which contains the task list ID of your task list).
3 comments:
Awesome Man!
Nice post thank you for sharing- anyone who was p*ssed off because you cant right click and copy the data just select and ctrl C and paste it.
Dont know why someone who would give information freely would try to restrict it as well.
ورنيش شفاف
Post a Comment