SAP Business Team
SAP Change Request Management
SAP Change Request Management How-to’s
During the course of a normal correction, these users (as example, the developer) can set the correction to In Development and then generate transport requests in the DEV system, to which the change will be added later. After the development activity has been completed, the normal correction can be transferred to testing. The change is automatically released in the DEV system and imported into QAS system and then evaluate if testing as successful or unsuccessful. If testing is unsuccessful, the status of the change document is reset to In Development, whereas the successful testing changes to status Consolidated. This status indicates that testing has been successful and enables the import of the change into PRD or Pre-PRD, according to the specific SAP landscape strategy. When all changes have been successfully imported into PRD system, the individual change documents can be completed by setting the user status from Consolidated to Production. The various user statuses that represent the individual steps involved in a normal correction are as follows: 41. Created 42. In Development 43. To be Tested 44. Consolidated 45. Production 46. Withdrawn These status values map the various steps in a normal correction, provide a general overview for users and facilitate navigation. The following table shows the activities that are possible in a normal correction during the various phases of an Implementation, Template or Upgrade project.
Version 0.2 Page 19 of 72