Change Request Management scenario: Working examples “Go-Live” phase
This blog covers the Go-Live 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:
Importing the entire project buffer into the production system, all transport orders are imported into the production system at the same time in the same sequence as they were exported, also the urgent corrections that has been already imported into the production system to ensure consolidated system status.
No type of correction can be released during this phase.
If there are still any open TRs, you have to return to the Development with Release phase and repeat the process including the test phase to ensure that any open requests can be released and transported.
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 | Consolidated | Set Production Status | Production | IT operator run task "Import Transport Request" in SMM:300, production system TR imported in SMM:300 ALL |
SDMJ 8000001057 | Withdrawn |
|
|
|
SDMJ 8000001059 | Consolidated | Set Production Status | Production | IT operator run task "Import Transport Request" in SMM:300, production system TR imported in SMM:300 ALL |
SDMJ 8000001061 | Consolidated | Set Production Status | Production | IT operator run task "Import Transport Request" in SMM:300, production system TR imported in SMM:300 ALL |
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* | Successfully Tested | Released for Production | Authorized for Import | SMMK900676, imported in SMM:200 I run firstly "Import Transport Request" in SMM:300 |
| Authorized for Import | Import Correction to Production System | Production | Error: Action cannot be performed during this maintenance phase Action: Recheck correctionàstatus remains in Production, now without errors |
| Production | Confirm Correction | Confirmed |
|
| Confirmed | Complete Correction | Completed | I close the H* because as you can see below the TR was already imported by the "Import Transport Request" |
SDHF 8000001075* | To be tested | Confirm Successful Test Released for Production Import Correction to Production System Confirm Correction Complete Correction | Completed | SMMK900674, imported in SMM:200 I run firstly "Import Transport Request" in SMM:300 Error: Action cannot be performed during this maintenance phase I close the H* because as you can see below the TR was already imported by the "Import Transport Request" |
SDHF 8000001079 | Completed |
|
| SMMK900678, imported in SMM:300 |
SDHF 8000001091* | Authorized for Import | Import Correction to Production System Confirm Correction Complete Correction | Completed | SMMK900688, Import into system SMM :200 Error: Action cannot be performed during this maintenance phase |
These orders were imported in SMM: 300 when I run task "Import Transport Request" in SMM: 300, production system:
SDMJ 8000001055 Consolidated SMMK900668 Imported in SMM: 200
SDMJ 8000001059 Consolidated SMMK900681 Imported in SMM: 200
SDMJ 8000001061 Consolidated SMMK900684 Imported in SMM: 200
SDHF 8000001079 Completed SMMK900678 Imported again in SMM: 300
SDHF 8000001091 Authorized for Import SMMK900688 Imported in SMM :200
SDMJ 8000001063 SMMK900692 Document Deleted via Business Transactions->Delete
SDTM 8000001092 Completed SMMK900690
SDHF 8000001077 Successfully Tested SMMK900676
SDHF 8000001075 To be tested SMMK900674
You will say why system is importing TR of corrections like SDHF 8000001075 that has status "to be tested"????
All TRs that were in the production import buffer are imported.
When you import a TR in quality system this order is added to the next import system buffer, usually production system buffer.
How to handle the situation and why can't it be solved.
The IMPORT into PRD is a pour call of TMS functionality, so we can not manipulate the import queue.
Recommendation: Always switch the phase/status in the SDMN transaction and not in the task list, in the SDMN transaction you will get the info that there are already SDMJ and SDHF correction in the import buffer switch are in status to be tested.
Which this information you should contact the colleague who owns the correction, mainly the SDHF correction and solve this, means forcing the colleague to test his SDHF.
So this means, it is not recommended to switch to status going-live and import immediately, because you always have to check the import buffer before import, by checking the status of the SDMN transaction.
This describes the process how it should work.
*In the case of these two SDHF corrections 8000001075, 8000001077 and 8000001091, in "To be tested" and "Successful Test" and "Authorized for Import", after running the Import in SMM:300 I can go with these corrections until Completed status because these TR are already in production. No new import into production system is done because with the tp import ALL these TR are deleted from the production import buffer.
With these correction statuses I change the phase to from "Go-Live" to "Being Completed" phase:
9 warnings:
Normal Correction 8000001046 still has status 'In Development'
Normal Correction 8000001049 still has status 'Created'
Normal Correction 8000001051 still has status 'In Development'
Normal Correction 8000001053 still has status 'In Development'
Normal Correction 8000001065 still has status 'Created'
Urgent Correction 8000001067 still has status 'Created'
Urgent Correction 8000001071 still has status 'In Development'
Urgent Correction 8000001073 still has status 'In Development'
Next phase in SDN Blog: Change Request Management scenario: Working examples "Being Completed" and "Completed" phase
1 Comment
