Transport procedure

1 Change request release procedure

• The development and the customizing work are performed in the client 100.
• Transport requests are moved to 110 and 120 for the testing purpose.
• All the development and customizing changes are recorded in SAP system generated change request numbers.
• Requests need to release to move the request into QAS or PRD systems.
• These change requests are transported into the QAS clients 200,210,220 first and verified.
• After verification the transport requests are released and transported to Quality client 200.
• After Confirmation from the respective Consultant the transport request is moved to Production Client 300 when required.
• The Functional consultant performs releasing of a change request. User authorization prevents others from releasing change requests for which they are not responsible.

 2 Quality Assurance Testing Procedures:

            The following standards are followed to ensure stable development and quality assurance   testing environments.

• After releasing a change request in the development system, further development on the related objects should be stopped. In other words, the actual versions of these objects are frozen.
• After import into Quality Assurance the logs are checked.
• Testing of the objects in the quality assurance environment either ends with a sign off, or requires a correction. If corrections are necessary, they are done on the actual version of the object in the development client.
• After successful testing and verification by a responsible person (respective module consultant and core user), further development can begin on the identified objects.

3 Procedure for imports into Production

• All the customization and development work will be performed only in the DEV client.
• All the change requests created by application consultants will be recorded and documented.
• After confirmation all the change requests will be transported into the QA client. Only after successful verification in the testing client the requests are further imported into the production client.
• All the change requests that are approved to be transported are released and transported first to QAS client and after verification and testing ok; are then transported to Production client.