Академический Документы
Профессиональный Документы
Культура Документы
Project “ASCEND”
Landscape & Change Transport Strategy
Document
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.
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
Sr. No DISCOM SID Instance Number Hostname
1 CPDCL CRP 00 cpdeccprd
2 EPDCL ERP 00 epdeccprd
3 NPDCL NRP 00 npdeccprd
4 SPDCL SRP 00 spdeccprd
1. The Development instance of ERP 6.0 contains separate client for performing the customizing and
Development.
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.
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
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
1. The Development instance of ERP 6.0 contains separate client for performing the customizing and
Development.
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.
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.
2. The Quality instance for EPDCL will contain 2 clients for Quality testing and End-User training
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
1. The Development instance of ERP 6.0 contains separate client for performing the customizing and
Development.
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.
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.
2. The Quality instance for NPDCL will contain 2 clients for Quality testing and End-User training
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
1. The Development instance of ERP 6.0 contains separate client for performing the customizing and
Development.
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.
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.
2. The Quality instance for SPDCL will contain 2 clients for Quality testing and End-User training
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
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
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).
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
ANNEXURE
Current 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
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.