To build the quality assurance (QA) environment with changes unit tested and released from the development environment
· Ensure that the development and QA environments are synchronized, with an identical configuration. This allows the integration of customizing and development efforts for integration testing.
· Depending on your solution landscape, you may have to build additional environments, for example, for training or pre-production. To do so, proceed as described in this task.
· To ensure consistency between environments, record all the changes you make to your development environment and ensure that new environments are similar.
· Use the Customizing Cross-System Viewer to compare customizing objects in two different clients (clients can be in the same SAP system or different ones).
1. Establish the clients required for each environment.
It is better not to set up the QA system from the development system by means of a database copy or client transport, for the following reasons:
· You cannot maintain your system landscape with these methods since they overwrite the target system or client.
· The system copy takes everything, including incomplete customizing and development efforts. It is difficult and time consuming to remove the unwanted objects.
· A client transport does not transport Repository objects, such as table structures and ABAP reports. They must be transported beforehand with change requests.
2. Import the change requests that have been unit tested and released from the development environment into the QA environment.
- Imports can occur after the unit tested change request(s) have been released from the development system. This step signifies that the changes contained in the change requests are ready to be promoted to the QA system.
· The import queue for the QA system contains a list of released requests that are waiting to be imported. This list is in the order that the change requests were exported. The latest copy of a change is the final result in the target system.
· To import the current import queue, use the TMS Start Import.
· After successful import, a change request is moved from the quality assurance import queue to the production system import queue.
3. Review the transport logs for the change requests and check that no errors occur. To do so, you can use the following tools:
- Customizing Organizer
- Workbench Organizer
- Transport Management System (TMS)
4. Depending on your client strategy, establish additional clients.
Result
QA system can receive unit tested change requests (customizing and development from the development system) for integration testing.
· Using change requests to build the QA system enables you to become familiar with TMS and possible special transport cases. This can help you to build and maintain the production system.
· The production system must be built like the QA system, so proper administration of change requests is essential.