Project Preparation
Business Blue Print
Realization:
LANDSCAPE:
DEVELOPMENT ---> QUALITY ----> PRODUCTION
Client-100 - Golden Client-200 -Testing
Client- 300
Client -110 - Testing Client- 210 - Training
Client-120 - ABAP Development
or OR
Client-100- Golden, Testing, ABAP Client -200- Testing, Training
Golden: Only Configuration will be done here - SPRO
Testing: Master Data and Transaction Data - SAP Easy Access
ABAP : All ABAP development changes are done here
Transport Request:
Almost all the configuration changes will be prompted a screen to save the changes
in a Transport Request.
Two types of Transport Request are available
1. Customized Transport Request: The changes which wont effect other clients in the
same landscape.
Almost all the configuration changes which are done by Functional Consultants are
saved in Customized TR.
Ex: Creation of Organization Structure, Creation of Material Types, Creation of
Purchasing Document types
2. Workbench Transport Request: The changes which effects cross clients/other
clients in the same landscape are saved in Workbench TR.
Almost all the changes which are done by Technical Consultants are saved in
Workbench TR. Very few functional changes are saved in Workbench request.
Ex: Define Access Sequences, Creation of new texts of Purchasing
Note: Although those settings are in SPRO, few changes won't ask you transport
request. These changes have to be maintained in each Client. We can say client
specific settings which we have to be repeated in each client.
Ex: Number Ranges, few Release strategies configuration settings, Few split
valuation changes
Realization:
Server installment
Clients creation- Basis
User IDs for Consultants and Core team members- Basis
Authorizations- Security
1. Configuration in GOLDEN CLIENT- 100:
ORGANIZATION STRUCTURE-TR1
Respective module configurations
TR- Master Data
TR- Procurement
TR- Pricing Procedure
TR- Release strategies
TR- Automatic Account Assignment
TR- Inventory Management
TR- Logistics Invoice Verification
TR- Changes after Unit testing
TR- Changes in Master Data
2. Moving TRs to Testing Client 110:
Activities:
* Client to Client copy or movemet withing same landscape- T Code - SCC1. All
configuration changes are moved to Testing Client 110
* Define Number ranges and release strategy related settings which are not
transportable
* Unit Testing by Consultants
* Any configuration changes have to be done in Golden Client 100 and move
immediately to 110 through SCC1
* Training to Core team members - Level 2 training
* Unit Testing by Core team members. Same UT script is used
* Any configuration changes have to be done in Golden Client 100 and move
immediately to 110 through SCC1
* Once UT is done, release TRs and share the TRs to Basis team to move to QUALITY
* Check all the configurations are moved from Golden to Quality or not. Define
Number ranges and release strategy related settings which are not transportable
* Perform System Integration Testing- SIT
* Any configuration changes have to be done in Golden 100 and release TR. Then move
to Quality - 200
* User Acceptance Testing or Business Acceptance Testing or Final Acceptance
Testing. This testing is done by Core team members(business). Three different names
but single testing and the same
SIT script is used for UAT.
* Any configuration changes have to be done in Golden 100 and release TR. Then move
to Quality - 200
* Preparing Functional Specification and working with ABAP for development testing
are done simultaneously along with above activities from starting of Realization
phase
* Master Data and transaction data conversion templates/Upload templates
