APDCL Instance Strategy Ver1.1

Project: - APDISCOM Page 1 of 20

APDISCOM Implementation Project “ASCEND”

Landscape & Change Transport Strategy Document

Deliverables against Milestone – Realization

1.1.1 APDCL Instance Strategy

A : Instance Strategy for ERP6.0 :

The SAP Landscape scenario comprises three distinct systems:-

An environment where customizing, development changes can be performed in Development Server.

Testing of the customizing and development changes can be performed in Quality Assurance Server.

A production environment where the users work on live system.

Development (DEV)

The Development environment would enable team members to configure the SAP system for the different business processes of APDISCOM. All configurations required for the business processes and custom developments (i.e. reports, forms, interfaces etc.) will be done and unit tested first on this environment. Any changes to SAP software in terms of configuration or ABAP repository will be 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.

There will be separate Development systems for each DISCOMs (CPDCL, EPDCL, NPDCL and SPDCL)

The Table contains the proposed SID, Instance Number and hostnames: -

Sr. No DISCOM SID Instance Number Hostname

1 CPDCL CRD 00 cpdeccdev

2 EPDCL ERD 00 epdeccdev

3 NPDCL NRD 00 npdeccdev

4 SPDCL SRD 00 spdeccdev

Quality (QAS)

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.

The Training client would facilitate training to the end-users. The training client 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. The training client would also be used for testing the Data Migration tools like LSMWs.


1 CPDCL CRQ 00 cpdeccqas

2 EPDCL ERQ 00 epdeccqas

3 NPDCL NRQ 00 npdeccqas

4 SPDCL SRQ 00 spdeccqas

Production (PRD)

The Production environment would be the place where actual business transactions would be carried out.

There is a individual Production instance of ERP 6.0 for CPDCL, NPDCL, SPDCL and EPDCL

The other systems in the landscape must guarantee that defective programs or incorrect customizing configurations do not adversely affect the production environment.

Each Production system will be having a pre-production client


1 CPDCL CRP 00 cpdeccprd

2 EPDCL ERP 00 epdeccprd

3 NPDCL NRP 00 npdeccprd

4 SPDCL SRP 00 spdeccprd


1. CPDCL landscape Strategy

1. The Development instance of ERP 6.0 contains separate client for performing the customizing and Development.

CPDCL Client -220 CPDCL Customizing ClientCPDCL Client -120 CPDCL Development ClientCPDCL Client -150 CPDCL Sandbox ClientCPDCL Client- 250 CPDCL Unit Testing Client

APPCC Client 010 APPCC Customizing client.APPCC Client 011 APPCC Unit testing client.

The Customizing client (220) will be used for ONLY customizing changes i.e. the client will not be open for performing any Cross client changes.

The Client 150 will be used as Sandbox client.

The Development client (120) is where all the ABAP developments and Cross client changes be carried out. No Customizing changes will be carried out in this client.

The Unit Testing Client (250) is where all the changes will be tested and found to be working. Only after this will the change request be transported to Quality Assurance system where further testing will be carried out.

The APPCC Client (010) will be used for performing all customizing activities related to APPCC.Separate company code 5000 will be created in this client.

The APPCC Client (011) will be used for testing all changes made in the APPCC customizing client. Once tested, these changes will be transported to APPCC specific quality client in QAS system.


2. The Quality instance for CPDCL will contain 2 clients for Quality testing and End-User training

CPDCL Quality Client - 200 Quality Client for CPDCLCPDCL Training Client - 210 Training Client for CPDCL.

APPCC Quality Client – 020 APPCC Quality client

CPDCL Integration testing will be performed in Quality client 200. End-user training will be performed in the training client 210.The training client 210 will also be used for testing all LSMWs and other Data Migration tools.Client 020 will be used as APPCC Quality client.

3. The CPDCL production client will contain 2 clients. The production clients of ERP system will connect to production instance of BI and EP located at CPDCL via RFC/HTTPS protocol

CPDCL Production client – 600 Production Client for CPDCLCPDCL Pre-Production Client – 500 Pre-Production Clients for CPDCLAPPCC Production Client – 060 APPCC Production client

1.1 CPDCL Transport Management strategy

There are 2 types of transport request created in development system

1. Customizing

2. Workbench

Customizing transport request will be created by Functional team and Workbench transport request created by Development team. Customizing transport request contain configuration for common business process and configuration of individual DISCOM

Transport path for Change requests in CPDCL:

1. All new requests will be created in new CPDCL Golden Master (220) and will be imported into Unit Test client (250) before releasing it to QAS system.

2. ONLY CPDCL specific customizing will be done in the Golden master 220 client. No other DISCOMs (NPDCL, EPDCL and SPDCL) customizations should be done in this client.

3. All the CPDCL Specific and common Request has to be transported to the Quality client first. The Org Structure deletion Request has to be moved at the end. The same will be followed in case of the Production system.


4. For setting up the Production system, the CPDCL specific and common requests will be moved first. Then the Deletion requests (deletion of NPDCL, EPDCL and SPDCL) will be moved followed by all the delta configuration requests.

5. The workbench transport request created in Development client (120) will be tested in client 180 before releasing it.

6. All workbench related transport request will move into 200 client QAS systems.

7. After Integration testing in QAS, all workbench request will move to company specific Production client

8. All workbench requests created in CPDCL Development client will be moved to individual DISCOM Development system first and then to each DISCOM QAS and Production systems.

9. Any Changes to ABAP programs, reports, screen changes etc. will only be done in CPDCL development client (120)

10. If in case there are any changes to be done to Developments which is DISCOM specific then this will be addressed in the respective DISCOM Development client (120) and will be moved in QAS and finally in Production system.

Transport path for Change requests for APPCC:

1. All Customizing activities related to APPCC will be done in APPCC Customizing client 010.

2. Developments for APPCC will be carried out in 120 ABAP Development client.

3. All changes made in APPCC Customizing client will be moved in 011 APPCC Unit test client using “SCC1”, tested thoroughly before releasing it to Quality system.

4. In Quality system a separate client 020 will be created for performing Integration testing.

5. After Integration testing in QAS, all Customizing and Workbench related to APPCC will be transported to APPCC Production client 060.

Naming Conventions for Transport Requests related to APPCC: -

1. APPCC Customizing request Each request description will begin with “APPCC:” followed by a proper description of the transport request.

E.g. If ERDK90063 is a common transport request then its description should be: -

ERDK900063 APPCC :< XX>_Request for Configuring Help on ERD system

Where “ERD” is the System ID

XX- will have value initials of the ModuleDeveloper (ABAP) – DEVFinance – FIControlling – COSales and distribution – SDMaterial Management – MMProduction Systems – PSHuman Resource – HRPlant Maintenance – PMBusiness warehouse – BW


Enterprise Portal – EPBasis – NW

** The same should be followed for Workbench requests related to APPCC.


2. EPDCL landscape Strategy


Development Client -220 EPDCL Customizing ClientDevelopment Client -120 EPDCL Development ClientDevelopment Client -150 EPDCL Sandbox ClientDevelopment Client- 250 EPDCL Unit Testing Client

The Customizing client (220) will be used for ONLY customizing changes i.e. the client will not be open for performing any Cross client changes.

The Development client (120) is where all the ABAP developments and Cross client changes be carried out. No Customizing changes will be carried out in this client.


2. The Quality instance for EPDCL will contain 2 clients for Quality testing and End-User training

EPDCL Quality Client - 200 Quality Client for EPDCLEPDCL Training Client - 210 Training Client for EPDCL.

Integration testing will be performed in Quality client 200. End-user training will be performed in the training client 210.The training client 210 will also be used for testing all LSMWs and other Data Migration tools.

3. The EPDCL production client will contain 2 clients. The production clients of ERP system will connect to production instance of BI and EP located at EPDCL via RFC/HTTPS protocol


EPDCL Production client – 600 Production Client for EPDCLEPDCL Pre-Production Client – 500 Pre-Production Client for EPDCL

Development System Quality System Production systemClients Golden

MasterABAP Development

Sandbox Unit Testing

Test Client

Training Client

Production Client

Pre-Production Client

EPDCL 220 120 150 250 200 210 600 500

2.1 EPDCL Transport Management strategy


1. Customizing

2. Workbench


Transport path for Change request in EPDCL

1. The EPDCL development system was created using all CPDCL specific and common transport request created as on 21st Oct. EPDCL Org. structure was created by copying the CPDCL Org. structure. In the process 3 EPDCL specific deletion requests (deletion of CPDCL Org. Structure) were created.

2. After 21st Oct no configuration changes were done in EPDCL development system. In order to make EPDCL Development system in sync with CPDCL development system, all trans[port requests created post 21st Oct (customizing as well as workbench requests) were moved into EPDCL development system. Again the CPDCL specific Org. Structure was deleted. In the process another set of 3 deletion requests (deletion of CPDCL specific Org. Structure) were created.

3. For creation of EPDCL QAS and PRD systems,

a. The CPDCL specific requests created as on 21st Oct will be imported first.

b. Next the EPDCL specific configuration requests created in 100 client will be moved.

c. Next the EPDCL specific deletion requests (deletion of CPDCL specific Org. Structure) created in EPDCL Dev. system will be imported.

d. Transport requests created post 21st Oct in CPDCL development system will be imported.

e. The second set of deletion requests created in EPDCL 220 client will be imported.

f. The delta configuration requests created in EPDCL Golden master client 220 will be imported.

4. All new requests will be created in new EPDCL Golden Master (220) and will be imported into Unit Test client (250) before releasing it to QAS system.

5. ONLY EPDCL specific customizing will be done in the Golden master 220 client. No other DISCOMs (CPDCL, NPDCL and SPDCL) customizations should be done in this client.


6. All workbench requests created in CPDCL Development client will be moved to EPDCL Development system first and then to EPDCL QAS and Production systems.



3. NPDCL landscape Strategy


Development Client -220 NPDCL Customizing ClientDevelopment Client -120 NPDCL Development ClientDevelopment Client -150 NPDCL Sandbox ClientDevelopment Client- 250 NPDCL Unit Testing Client

The Customizing client (220) will be used for ONLY customizing changes i.e. the client will not be open for performing any Cross client changes.The Development client (120) is where all the ABAP developments and Cross client changes be carried out. No Customizing changes will be carried out in this client.


2. The Quality instance for NPDCL will contain 2 clients for Quality testing and End-User training

NPDCL Quality Client - 200 Quality Client for NPDCLNPDCL Training Client - 210 Training Client for NPDCL.


3. The NPDCL production client will contain 2 clients. The production clients of ERP system will connect to production instance of BI and EP located at NPDCL via RFC/HTTPS protocol

NPDCL Production client – 600 Production Client for NPDCL


NPDCL Pre-Production Client – 500 Pre-Production Client for NPDCL




Test Client

Training Client

Production Client


NPDCL 220 120 150 250 200 210 600 500

3.1 NPDCL Transport Management strategy


1. Customizing

2. Workbench


Transport path for Change request in NPDCL

1. For creation of NPDCL development system, all CPDCL specific and common transport request created in CPDCL Development system will be moved into NPDCL Golden Master client (220) followed by the CPDCL specific deletion requests.

2. All the other CPDCL specific delta configuration requests will be moved into NPDCL Golden master client 220 along with all the Workbench requests (Developments, SAP Notes, other Client independent requests)

3. In case of HR Module, the NPDCL specific Org. structure request created in CPDCL 100 client will be moved into NPDCL Golden Master client 220. Other than this NO other request from CPDCL 100 client will be moved into NPDCL 220 client. The same request will also be moved into NPDCL QAS and PRD system.

4. NPDCL Org. Structure will be created by copying the CPDCL Org. structure and then deleting the CPDCL specific Org. Structure.

5. For creation of NPDCL QAS and PRD systems, the CPDCL specific requests will be moved first followed by the deletion requests (deletion of CPDCL specific Org. Structure) created in NPDCL Dev. system

6. All new requests will be created in new NPDCL Golden Master (220) and will be imported into Unit Test client (250) before releasing it to QAS system.

7. ONLY NPDCL specific customizing will be done in the Golden master 220 client. No other DISCOMs (CPDCL, EPDCL and SPDCL) customizations should be done in this client.






4. SPDCL landscape Strategy


Development Client -220 SPDCL Customizing ClientDevelopment Client -120 SPDCL Development ClientDevelopment Client -150 SPDCL Sandbox ClientDevelopment Client- 250 SPDCL Unit Testing Client

The Customizing client (220) will be used for ONLY customizing changes i.e. the client will not be open for performing any Cross client changes.The Development client (120) is where all the ABAP developments and Cross client changes be carried out. No Customizing changes will be carried out in this client.


2. The Quality instance for SPDCL will contain 2 clients for Quality testing and End-User training

SPDCL Quality Client - 200 Quality Client for SPDCLSPDCL Training Client - 210 Training Client for SPDCL.


3. The SPDCL production client will contain 2 clients. The production clients of ERP system will connect to production instance of BI and EP located at SPDCL via RFC/HTTPS protocol

SPDCL Production client – 600 Production Client for SPDCL


SPDCL Pre-Production Client – 500 Pre-Production Client for SPDCL




Test Client

Training Client

Production Client


SPDCL 220 120 150 250 200 210 600 500

4.1 SPDCL Transport Management strategy


1. Customizing

2. Workbench


Transport path for Change request in SPDCL

1. For creation of SPDCL development system, all CPDCL specific and common transport request created in CPDCL Development system will be moved into SPDCL Golden Master client (220) followed by the CPDCL specific deletion requests.

2. All the other CPDCL specific delta configuration requests will be moved into SPDCL Golden master client 220 along with all the Workbench requests (Developments, SAP Notes, other Client independent requests)

3. In case of HR Module, the SPDCL specific Org. structure request created in CPDCL 100 client will be moved into SPDCL Golden Master client 220. NO other request from CPDCL 100 client will be moved into SPDCL 220 client. The same request will also be moved into SPDCL QAS and PRD system.

4. SPDCL Org. Structure will be created by copying the CPDCL Org. structure and then deleting the CPDCL specific Org. Structure.

5. For creation of SPDCL QAS and PRD systems, the CPDCL specific requests will be moved first followed by the deletion requests (deletion of CPDCL specific Org. Structure) created in SPDCL Dev. system

6. All new requests will be created in new SPDCL Golden Master (220) and will be imported into Unit Test client (250) before releasing it to QAS system.

7. ONLY SPDCL specific customizing will be done in the Golden master 220 client. No other DISCOMs (CPDCL, EPDCL and NPDCL) customizations should be done in this client.





Guidelines

1. The transport file from Development Quality Production should be transfer via FTP, there should be a enough bandwidth available across the location to transfer the files (the size of the files depends on the transport request generated per day)

2. The frequency of transport in production system should be once or twice per week and for emergency case it has to be happened immediately after approval from business owner.

3. Each Module Lead should maintain a list of transport requests created.

4. Before releasing the transport request from Development system it has to be thoroughly tested and approve by respective team lead and process owners.

5. The transport to production system will be done only after approval from PMO


B : Instance Strategy for BI, EP, GRC and DMS:


Each DISCOM will have a separate landscape for BI, EP, GRC and DMS.

1.BI (Business Intelligence)

The configuration changes in Business Warehouse Implementation are cross-client in nature, therefore only a single client will be used for customization, ABAP development as well as unit testing. The BI Development client has to be configured for bi-directional communication with the SAP ERP Development server. The changes made in BW Development (100) environment would be carried forward to the BW Quality Assurance Client (200) and BW Production Client (300) for each DISCOM (CPDCL, NPDCL, SPDCL and EPDCL).

BI Development Instance will be connected to ERP development instance.

BI Quality instance will be connected to ERP Quality instance.

BI Production instance will be connected to ERP Production instance.

2.EP (Enterprise portal)

Enterprise portal will be used as a single point of entry to the users accessing ERP and BI. The JAVA application development will be carried out in Development instance of Enterprise portal using NWDI platform.

The enterprise landscape consists of Development, quality and Production instance for each DISCOM (CPDCL, NPDCL, SPDCL and EPDCL).

Development instance of Enterprise portal will connect to Development instance of ERP and BI System.

Quality instance of Enterprise portal will connect to Quality instance of ERP and BI system.

Production instance of Enterprise portal will connect to production instance of ERP and BI, the enterprise portal URL will be access using Secured layer (SSL). The Portal communication to Backend SAP systems ERP and BI is through HTTPS protocol

3.GRC (Governance, Risk & Compliance)

The system landscape for GRC will consist of Development and production instance only.

Development Instance will be connected to ERP development and Quality instance


Production instance will be connected to ERP Production instance

4.DMS (Document Management System)

The system landscape for DMS will consists of Development and Production Instance only.

The development system will be connected to the ERP development and Quality Instance.

The Production system will be connected to the ERP production system.

ANNEXURECurrent Status as on 02/03/2010

1. CPDCL

a. CPDCL Development system has been setup and client 220 (CPDCL Customizing client), 250 (CPDCL Unit testing client), 150 (Sandbox Client) and 120 (ABAP development client) have been created.

b. APPCC Customizing client 010 and Unit testing 011 have also been created.

c. CPDCL Quality system has been setup with 200 (CPDCL Quality client) and 210 (CPDCL Training Client)

d. CPDCL BI Development system has been setup with 100 (CPDCL BI Client).

e. CPDCL BI QAS has not been setup due to unavailability of servers.

f. CPDCL EP Development system has been setup. No QAS system has been setup because of unavailability of servers.

g. CPDCL BI and EP development systems have been connected using SSO (Single Sign-ON). Similarly CPDCL ECC Dev and QAS have been connected to CPDCL EP system using SSO.

h. CPDCL GRC development system has been setup and all the required settings have been done.

i. CPDCL DMS system has not been setup because of unavailability of servers.

2. EPDCL

a.EPDCL development system has been setup and client 220 (EPDCL Customizing client), 250 (EPDCL Unit testing client), 150 (Sandbox Client) and 120 (ABAP development client) have been created.

b.EPDCL Quality system has been setup with 200 (EPDCL Quality client) and 210 (EPDCL Training Client)

c.EPDCL BI, EP, GRC and DMS system have not been setup because of unavailability of servers.


3. SPDCL

a. SPDCL development system has been setup and client 220 (SPDCL Customizing client), 250 (SPDCL Unit testing client), 150 (Sandbox Client) and 120 (ABAP development client) have been created

b. SPDCL Quality system has been setup with 200 (SPDCL Quality client) and 210 (SPDCL Training Client)

c. SPDCL BI, EP, GRC and DMS system have not been setup because of unavailability of servers.

4. NPDCL

a. NPDCL development system has been setup and client 220 (NPDCL Customizing client), 250 (NPDCL Unit testing client), 150 (Sandbox Client) and 120 (ABAP development client) have been created

b. NPDCL ECC QAS, BI, EP, GRC and DMS systems have not been setup because of unavailability of servers.


Documents

APDCL Instance Strategy Ver1.1