Change Request Management scenario: Working examples "Being Completed” and "Completed"phase
This blog covers the Being Completed and Completed phase as part of the working case initiated in SDN blog: Change Request Management scenario: Working examples.
Here you will find also the possible actions and statuses of normal and urgent corrections, when you are in this MC phase.
In this phase:
If there are no open TRs, the MC can be closed by setting the status to "To be closed". Subsequently a new MC can be create.
No further changes are possible in this MC are possible.
When completing the MC all open request and transactions will be decoupled from the task list. When generating a new task list for the same project, all open request and transactions will be linked to this new task list and can be processed further, see note 1071412 for details.
This is the suggested test for the set of corrections in this phase:
Correction | User Status | Action | Final User Status | Details |
SDMJ 8000001049 | Created | | | |
SDMJ 8000001046 | In Development | | | |
SDMJ 8000001051 | In Development | | | Created SMMK900664 but left empty |
SDMJ 8000001053 | In Development | | | SMMK900666, task released |
SDMJ 8000001055 | Production | | | |
SDMJ 8000001057 | Withdrawn | | | |
SDMJ 8000001059 | Production | | | |
SDMJ 8000001061 | Production | | | |
SDMJ 8000001065 | Created | | | |
SDHF 8000001067 | Created | | | |
SDHF 8000001069 | Withdrawn | | | |
SDHF 8000001071 | In Development | | | created SMMK900670 but left empty, H000000398 |
SDHF 8000001073 | In Development | | | SMMK900672, task released H000000399 |
SDHF 8000001077* | Completed | | | |
SDHF 8000001075* | Completed | | | |
SDHF 8000001079 | Completed
| | |
SDHF 8000001091* | Completed | | | |
I am going to go to Completed phase and see how to handle these open corrections.
Always close the task list working with the SDMN document of the MC.
A task list can be closed even with modifiable transport orders according to note 1071412 "Completing a task plan with changeable transport requests", also apply note 1344191.
Then when you create a new cycle, the system automatically assigns these processes and objects to the new cycle. This is also logged in application log. To display the log entries, you can use transaction /TMWFLOW/MAINTINST. Navigate to the tab with your project type (usually the maintenance project) and choose 'Create...' and 'Execute'. Then select the required project and choose 'Messages at Time of Creation'.
There are 8 open corrections, 4 of them with TR created and not released:
8000001067 Change 11- SDHF SDHF Urgent Correction Created
8000001071 Change 13- SDHF SDHF Urgent Correction In Development
8000001073 Change 14- SDHF SDHF Urgent Correction In Development
8000001046 Change 1- SDMJ SDMJ Normal Correction In Development
8000001049 Change 2- SDMJ SDMJ Normal Correction Created
8000001051 Change 3- SDMJ SDMJ Normal Correction In Development
8000001053 Change 4- SDMJ SDMJ Normal Correction In Development
8000001065 Change 10- SDMJ SDMJ Normal Correction Created
SDMJ 8000001051 | In Development | Created SMMK900664 but left empty |
SDMJ 8000001053 | In Development | SMMK900666, task released |
SDHF 8000001071 | In Development | created SMMK900670 but left empty, H000000398 |
SDHF 8000001073 | In Development | SMMK900672, task released H000000399 |
If you go now to see TR in the satellite SMM: 100 you will see that the project is called now "ALL_FLOW_1_DECOUPLED_0000000001":
For an already imported TR you can see SAP_CTS_PROJECT filled.
For the TR SMMK900666 you can see that now it is not assigned to any CTS project:
I create a new MC cycle for the project in solar_project_admin:
Create Task List:
Checking again the open TRs:
All 8 open corrections are assigned now to the new MC and you can continue working on it.
Please see the last SDN Blog of this working example: Change Request Management scenario: Working examples Final Points and Appendix