CLIENT LANDSCAPE

Clients in SAP provides environment for developing, testing and customizing of the programs. Requirement of separate systems and client landscape design stems from the fact that the SAP implementation involves various activities e.g. development, trying out business process modeling on the sand box, testing the designed process scenarios, testing by end users, end user training and finally going live on the productive system. These activities cannot be carried out on one single hardware box. Therefore, it is important that a well-designed approach is followed to keep the logically distinct environments on separate hardware boxes and have a predefined client landscape strategy in place to be able to track and control the implementation. Following are the various environments in different phases of the project: Development environment Quality Assurance environment Training environment Production environment

Development environment The Development environment would enable team members to configure the SAP system for the different business processes . All configurations required for the business processes and custom developments (i.e. reports, forms, interfaces etc.) are done and unit tested first on this environment. Any changes to SAP software in terms of configuration or ABAP repository is done here. After all the changes have been unit tested and found to be working as expected, these changes can be transferred to the quality assurance system for further system testing. The configuration and development changes are transported using transport requests. Quality Assurance environment The Quality Assurance environment is used for system integration and user acceptance tests. Once the business processes are found to be working as expected, configuration or custom-developed programs are transported to the production system.

It is intended to perform a thorough testing in the Development and the Quality Assurance environment for the business processes before the customization or custom developed programs are transported to the productive environment. Training environment The Training environment would facilitate training to the end-users. The training server has the same business process configuration and custom developed programs, which would otherwise exist on the production system. This enables the users to learn and practice to transact the business activities within SAP environment so that they are able to perform their job responsibilities on the actual production system with ease. Production environment The Production environment would be the place where actual business transactions would be carried out. The transport route for transport request would be unidirectional.

Terminology
System Landscape The landscape consists of all SAP Systems (Instances) involved in the implementation project and client architectures that access (or share) a common transport directory. R/3 System A R/3 System consists of a central database server and the application servers.

SAP System Identification

The SAP System Identification often referred to as the SAPSID, or SID, is a unique three-character code that identifies the R/3 System. In this document the SAP System Identification codes used are DVR for the development and QAR quality assurance or test system, and PDR for the production system.

Client
A client is a legal and organizational entity in the SAP System whose business management data is protected against unlawful access. In addition, a client: Has its own set of user data Is a logical system with separate master records

Customizing
Customizing is the process of configuring the SAP System such that the SAP functionality fits the companys needs.

Development
Utilize the SAP development tool set (such as the ABAP/4 Development Workbench, RFC SDK, ADK, etc.) to create SAP reports, interfaces, conversion programs, and enhancements.

Client Landscape for SAP R/3 Enterprise

The SAP R/3 Landscape will consist of the Development System, Quality Assurance System, Training system and Production system. The end-user training will be conducted on the Training system. The Standard Pre-configured clients 000 (SAP Reference Client), 001 (SAP Sample client) & 066 (SAP Early Watch Service client) will be created by default when SAP R/3 Enterprise and IS Oil Downstream is installed. Client 065 has to be created by copying client 000 after completion of SAP installation. As per ISOil installation document, various CATT procedures are to be executed in client 065 and the results are to be sent to SAP (Waldorf) so that IS-Oil team can ratify the correctness of the IS-Oil installation. The different clients that will be created in various R/3 systems are as follows:

Development environment IS-OIL CATT Client (065) Golden Master Client (100) Role Master (125) Sandbox Client (110) ABAP/4 Development Client (120) Unit Testing Client (190)

Quality Assurance environment Quality Assurance Final Integration Client (200) Data Upload Test client/ Production Back-flush Client (210) HR Payroll Client (250)

Production Environment Pre Production client (500) Production client (300)

Training Environment

Development Server Client Landscape

System Identifier (SID): DVR The development instance will have SAP R/3 Enterprise / IS-Oil Downstream installed following the SAP standard installation procedure. Thus client 000 will have all the IS-Oil Downstream related functionalities & changes. This client 000 would then be copied over to 065, 100 and 110. Client 065 is used for running ISOIL CATT procedures to test the correctness of IS-OIL installation. Client 100 is used as a Golden Master Client and client 110 as a sandbox environment. The client 100 will then be copied over to 120 for ABAP development. The client 190 will be created from client 000. All client dependent configurations done in client 100 and SAPscript objects developed in client 120 would be transported to client 190 and suitable testing would then be done in this client to check business processes.

Customising Client / Golden Master (Client 100) Source The SAP standard client 000 would be copied to client 100 with IS-Oil Downstream functionality. Usage Golden Master/ Customizing client for functional team. All work of configuration will be done in this client. This is the client where the core team will configure the client according to GAIL business practices. This client is available to functional team members who have the access of configuring the SAP system. Only configuration work should be done here. No transaction will be done in this client Refresh - This client will not be refreshed during the duration of the project. Role Master (Client 125) Source The Client 100 would be copied to client 125 with SAP_ALL profile. Usage - Golden Master client for roles and authorizations. Only roles creation would be done in client 125. These roles would be transported to client 190 of the development server for testing and then would be transported to the quality and production servers.

Sandbox Client (Client 110) Source The SAP standard client 000 would be copied to client 100 with IS-Oil Downstream functionality. Usage The entire Project Team will have full transaction and configuration access to this client. The users on this client can carry out different experiments and trials on this client to check out different functionalities. Only client dependent customizing changes would be allowed in this client. Changes in this client will not be stored in change requests. Nothing will be transported out of this client. Refresh If required, this client can be periodically refreshed from the Golden Master Client (100) or Unit Testing Client (190) with necessary approval from project management team..

ABAP Development Client (Client 120) Source The SAP client 100 would be copied to client 120 after basic configuration is over in client 100 and before ABAP development work can start. Usage - Any changes to the standard SAP programs and development of custom reports will be performed in this client. Only ABAP/4 modifications are allowed in this client; therefore, the access is limited ONLY to ABAP/4 team. All modifications will be stored as Change Requests. Refresh This client will not be refreshed during the duration of the project. Unit Testing Client (Client 190) Source The SAP standard client 000 would be copied to client 190 with IS-Oil Downstream functionality. Usage The Project Team members involved in Unit Testing as well as the entire Development Team will have access to this client. No modifications to configuration will be allowed here. Configuration changes will be transported to this client from the Golden Master Client (100). After successful testing in this client, the changes would be taken to the Quality Assurance System. Refresh This client will not be refreshed during the duration of the project.

R/3 Quality Server Client Landscape

System Identifier (SID): QAR The purpose of the Quality Assurance Environment is to ensure that proper data and configuration is available in the production server and the System is properly tested before go live. It also serves as the environment where proper integration testing can be done. The quality assurance environment will have the SAP instance QAR, which will be made up of number of clients. Quality Assurance Final Integration Client (Client 200) Source 000 and 100 (DVR Customizing Transport request) plus 120 (ABAP Development Transport Requests). Usage Quality Assurance Final Integration client is the place where all the configurations from every module are tested together for their functionality robustness. The configurations made in the development environment will be tested and confirmed for their integrity in this client. The testing team will test inter-dependent functionality of the configurations. In order to maintain the integrity of the configurations, direct modifications are not allowed in this client. All modification must be performed in the development environment prior to moving them into this client. Change Request tested in this client would be transported and applied to the client in PDR environment. In other words, in this client the complete cycle of the business processes will be tested. Refresh This client will not be refreshed during the duration of the project. Data Upload Client / Production back-flush client (Client 210) Source This client will be copied from client 200 / 300 as per the requirement. Usage A provision of a client 210 can be kept on the QAR server. If the volumes of data upload on production server is large or the data migration programs are complicated or the data received from locations needs to be subjected to extended sanity checks, then client 210 can be created by copying 200. Alternatively, core team members might try to test some transactions after creation of production client, 300. In another post-go-live scenario, team members might request a copy of production data to try out some activities

before doing it directly on production like financial period closing etc. To cater to all these requirements, a client copy from 300 to 210 is to be done. Refresh Client will be refreshed from client 200 / 300 as and when required with necessary approval from project management team. To refresh the client, Protection level need to be changed to Protection Level 0. HR Payroll Client ( Client 250) Source This client is copied from client 200 (Quality Assurance Final Integration) with profile SAP_CUST and SAP_ USER. Usage HR client for the testing of payroll. All the customizing requests will be taken to this client from client 200.

R/3 Production Server Client Landscape System Identifier (SID): PDR Once the user acceptance test is completed and has been signed off, the preparation for the production environment begins. In production environment, only one productive client is available for use. It is also recommended just to have only the production client excluding the SAP standard clients, such as client 000 (reference client), client 001(reference client), and client 066 (early watch client) be on the system. Pre Production Client (Client 500) Source This client is a copy of client 300(PDR) Usage This client is a pre production client and will be used for data upload and testing. The client will be deleted post Go-Live.

Production Client (Client 300) Source 000 and 100 (DVR Customizing Transport request) plus 120 (ABAP Development Transport Requests). Usage Production client is the client where the real productive transaction data will be entered into the system. Access to the production client is restricted by using the roles. No modifications are allowed in this environment. In case any modifications are required, they must be made in the development environment, transported to integration environment for formal testing, and finally transported to the production environment. Refresh This client will not be refreshed ever.

R/3 Training Server Client Landscape

System Identifier (SID): TRR

Training Client (Client 400) Source This client will be copied from client 200 (QAR). Usage The training environment is typical for any SAP R/3 implementation. All the end user trainings for preparing the users to work in the SAP environment is accomplished here. This client will be refreshed from client 200 (QAR) on demand. Refresh This client need not be refreshed during the duration of the project. But on demand from core team members, the client may be refreshed from client 200 (QAR) with necessary approval from project management team. To refresh the client, Protection level need to be changed to Protection Level 0.

10