LAND SCAPE ASAP TESTING
IMPLEMENTATION “E2E” (END TO END) FULL LIFE CYCLE
SUPPORT
UP GRADE
ROLL OUT
I). SAND BOX ENVIRONMENT:
-This environment is intended to be areas where the team can safely prove the concepts are resolve the issue with out having to be concerned with the impact to the main system.
This system can be refresh periodically are when ever it is required.
SAND BOX CLIENT: -
This is the only client in this environment that is to be used for those tasks that do not fall under any tropical run.
For example the proofs of concepts that the development team does not have the experience of performing in the post are not comfortable enough in performing can be done in this client. The production data issues can also be pulled down to this client to prove the solution.
II). DEVELOPMNT ENVIRONMENT:
-This environment is intended to be an area where the main activities accurse and or tested before being mood through the quality environment on their way to
production.
A). GOLDEN CONFIGARATION: -
SAND BOX
This is the client where all the configuration setting will be done and transported the team members will have restricted access to this client. This client is the reference client for production configuration where testing will not be allowed.
B). ABAP DEVELOPMENT CLIENT: -
This client is used by the programmer to develop new ABAP programs. Those programs created here can be tested independent of the configuration development changes that might be according in the other clients no configuration is allowed in this client. The configuration changes for this client are done by refreshing them using the golden configuration client.
C). UNIT TESTING CLIENT: -
This client is used specifically for the unit testing of the find configuration. This client will be created from the golden configuration client and the sample text data will be up loading here for carrying out unit testing.
III). QUALITY ASSURENCE ENVIRONMENT:
-This environment is to be has close to the same has the production environment as possible this gives the developers a static version of how the production
environment will be all the completed unit tests from the development environment strung together in to longer test that constitute the entire business process and tested hers. There changes to the cross client objects are not allowed in this environment where they must be done in the development environment. In rare circumstances where a change has to be done directly in this environment, a prier approval will be needed.
A). MASTER CONFIGURATION CLIENT: -
After unit testing is completed all those changes are transported to this client so this is a client who contains all these transports.
There should not be any transactional data (testing) in this client so this client acts has golden client.
B). INTEGRATION TESTING CLIENT:
-This client is used for integration and user acceptance testing consist of those unit test strength together to compromise the complete business process the integration testing is performed in this client after the functional configuration is completed.
This client is create a from the master configuration client.
C). TRAINING CLIENT:
-This is the client where the actual “SAP” training is done for users this client is refreshed from master configuration client has for the requirements any
configuration changes which go to the production client would also go to this client.
IV). PRODUCTION ENVIREMENT: -
This envirement is used for the production live operations of the client.
PRODUCTION CLIENT:
-This client issued for the live transactions. The custom rising and repository
changes are only allowed to the transported to this envirement after they have been fully tested in the “QA” envirement and have a formed chase control approved. No customizing or repository changes are allowed in this client under any
subcumstences this client is unique in the land scrape which cannot be refresh, can only be restored from a back up.
ASAP – METHODOLOGY (Is also called has road map)
SDLC
(SOFT WARE DEVELOPMENT LIFE CYCLE)
Accelerated “SAP” is a implementation solution provided by “SAP” for the rapid and efficient implementation of the “SAP” system the “ASAP” methodology integrates several components that work in conjunction.
PHASE IN “ASAP” METHODOLOGY: -1). PROJECT PREPARATION.
2). BUSINESS BLUE PRINT. (B.B.P) 3). REALIZATION.
4). FINAL PREPARATION.
5). GO – LIVES SUPPORT.
1). PROJECT PREPARATION:
-This phase provides initial planning and preparation for the implementation of
“SAP” system.
Deciding the scope of the project
Deciding the system land scope
Team formation
SAP
Consulting team client team
Project manager project manager
` Functional technical basis end power code business User’s users team process Owner (BPO’s)
PREPARING BUSINESS PROCESS DOCUMENT (or) BRS: -It is the documentation of business requirement of the client
(AS IS ETUDY) “BRS” (BUSINESS REQUIREMENT SPECIFICATION)
CICK OF MEETING:
-This mile stone activity is a critical point that officially launches the “R3”
implementation for the client. It also explains the implementation strategy. Time
(very important) (Deciding go-live date) and project goods and objectives 2). BUSINESS BLUE PRINT (B.B.P):
-In this phase we create business blue print which is a detailed documentation of the results gathered during requirements work shops. For then more the business blue print serves to document the business process requirements of the company. On this basis we will achieve a common under standing of how the company intense to run they business process in the SAP system.
A). Deciding the organization at structures
B). Preparing the data collection sheets for data migration (flat file) C). Deciding the data conversion strategy for data migration.
D). Preparing (B.B.P) documentation. (AS – IS vs. TO BE) AS –IS TO BE
1).R1 Y/N 2).R2 Y/N 3).R3 Y/N 4).R4 Y/N
E). Identifying the varies when customization has to be done.
F). GAP analysis.
G). Deciding user roles and authorization.
3). REALIZATION: - (This phase talk about configuration)
A). In this phase we implement all the business process requirements based on the business blue print. We configure the entire system step by step in two work
packages called “BASE LINE” configuration and final configuration organization change management.
B). BASIC LINE CONFIGARATION AND CONFIRMATION: -During base line configuration we work on those processes which can be configured with out any programming on enhancement.
C). UNIT TESTING OF BASE LINE CONFIGARATION: D). FINAL CONFIGURATION AND CONFERMATION:
-The final configuration is an iterative (repeated) process in which we set up all the business requirements.
It is a transformation process that expands the base line solution defined during the business blue print and base line configuration through multiple cycles until a solution is found to deliver that satisfies the entire stated business requirement.
PREPARING FUNCTIONAL SPECIFICATION TO PASS ON THE REQUIREMENTS TO ABAPER
TESTING THE CUSTOMIZATION
Preparing user manuals and configuration documents 4). FINAL PREPARATION:
-In this phase we complete the testing, system managements and the other related activities to finalize our readiness to go live. For there more this phase also server to resolve all the critical open issues.
A). UNLOADING THE SIMULATED DATA FROM THE LEGACY SYSTEM.
B). CARRYING OUT INTEGRATION TESTING.
C). DECIDING CUT OVER ACTIVITIES AS CUT OVER STRATEGY:
In the cut over strategy we decide which activities can be stopped for time being so that the other issues can be resolve which are essential for the project to go live.
PRE GO – LIVE END USER TRAINING.
5). GO – LIVE AND SUPPORT.
LIVE TRANSACTIONS WILL BE TACKING PLACE IN THE PRODUCTION SERVER.
PRODUCTION SERVER
POST GO – LIVE TRAINING
S.L.A: - (SERVICE LEVEL AGREEMENT)
TOOLS: - (KINTANA) (AVINTIE) (EXPRESS.O.) (CLARIFY) issue tracking tools.
SAME TIME THIS IS THE “IBM” TOOL.
REMOTE ACCESS.
V.P.N: - (VERTUAL PRIVATE NETWORK FOR REMOTE ACCESS).
NOTE: - We need to transfer the data from the development to quality server by transporting the custom rising request and work bench, request by using the transaction code “SE09”.
Go to “SE09”.
Select the request type (CUSTOMIZING REQUEST) Select the button display.
Select the required request and select the icon release directly.
NOTE: - To transport the request the basis guy has to set up transport management system “TMS”.