Currently Being Moderated

Change Request Management scenario: Working examples "Development with Release" phase

This blog covers the Development with release 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:

TRs can be released from within a regular correction.

For regular corrections, the administrator has to use the task list to import all released corrections into the test system or he has to schedule regular import batch jobs.

If any regular corrections exist whose status has not yet been set to Tested successfully when the maintenance cycle phase is changed from Development w Release to Test, the system issues a warning in the SDMN document. These corrections are then excluded from the integration test and cannot be released.

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

To be Tested

 

 

 SMMK900668, TOC SMMK900680, created and exported AUTOMATICALLY (also imported as you can see in SDMJ *1059)

SDMJ 8000001057

Withdrawn

 

 

 

SDMJ 8000001059

Created

Set to "In development"

In Development

 

In Development

Created Transport Request

In Development

SMMK900681

In Development

Logon to System

In Development

Release task

In Development

Complete Development

To be Tested

TOC SMMK900683 created and exported

To be Tested

Go to the Task List

To be Tested

IT OPERATOR should go to task list to import the TOC to SMM:200

From SMM:200 tas list "Import Transport Request"--> IMPORT ALL, all released transport orders of this project will be imported!! Also from SDHF correction already imported to SMM:200

- TOC SMMK900680 is imported, because this request is already in the qua import buffer

Also:

- SMMK900674 ( SDHF 8000001075)

- SMMK900676 (SDHF 8000001077)

- SMMK900676 (SDHF 8000001079)

are imported again in SMM:200, this happens only with the first import ALL in QUA, not with the others.

Job /TMWFLOW/SCMA_TRORDER_IMPORT

To be Tested

Logon to System

To be Tested

 

To be Tested

Confirm Successful Test

Consolidated

Task "Release Transport Request" appears AUTOMATICALLY in the task list, TR SMMK900681 is released!

AGAIN IT Operation should go to task list to import this released TR into SMM:300

SDMJ 8000001061

Created

Set to "In development"

In Development

 

In Development

Created Transport Request

In Development

SMMK900684

In Development

Logon to System

In Development

Release task

In Development

Test Transport

In Development

"Select Transport Request to be copied" popup--> selected SMMK900684

TOC SMMK900686 created and exported

IT OPERATOR go to task list to import the TOC to SMM:200

In Development

Complete Development

To be Tested

Another TOC is created automatically  SMMK900687

IT OPERATOR go to task list to import the TOC to SMM:200

To be Tested

Confirm Successful Test

Consolidated

Task "Release Transport Request" appears AUTOMATICALLY in the task list, TR SMMK900684 is released!

AGAIN IT Operator should go to task list to import this released TR into SMM:300 but not until Go-Live phase

Consolidated

Set Production Status

Consolidated

Error: Unable to successfully complete import into production system

This error appears because transport order is not imported in  SMM:300, this can not be done in this phase, only in Go-Live phase after the Import ALL in SMM:300

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 8000001075

To be tested

 

 

SMMK900674, H000000400, imported in SMM:200, and in SMM:300 import buffer

SDHF 8000001077

Successfully Tested

 

 

SMMK900676, H000000401, imported in SMM:200

SDHF 8000001079

Completed

 

 

SMMK900678, H000000402, imported in SMM:300

SDHF 8000001091

Created

Set to "In Development"

In Development

The "Create transport request" popup appears automatically, created SMMK900688, H000000411

 

In Development

Logon to System

In Development

SMMK900688, task released

 

In Development

Pass Correction to Test

To be tested

"Select Transport Request to be Released" popup for  SMMK900688 appears, select it.

Import into system SMM       200 started

 

To be tested

Logon to System

To be tested

Check if the change is correct

 

To be tested

Confirm Successful Test

Successfully Tested

 

 

Successfully Tested

Released for Production

Authorized for Import

 

 

With these correction statuses I change the phase to from "Development with release" to "Test":

image

TR and TOC situation:

image

image

image

image

There are 8 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 8000001055 still has status 'To Be Tested'

Normal Correction 8000001063 still has status 'Created'

Normal Correction 8000001065 still has status 'Created'

In Test phase the code is freeze, I mean, you can not release any request, so if you want to be able to work with these corrections you should go back to Development with release phase.

If not, only these corrections will be included in the actual test and go-live:

  • Normal Correction 8000001059 Consolidated
  • Normal Correction 8000001061 Consolidated
  • All urgent corrections

During this Test phase you can work with SDMJ in Status "Consolidated" and with SDHF corrections.

The other will be included in the next test phase, SDN Blog: Change Request Management scenario: Working examples “Test” phase

Note: 

  • When one normal correction is at status "Consolidated", then the transport requests should have already been released, so you are not allowed to withdraw the normal correction at this status.
  • However if you do not want to transport the changes to follow up systems, you should create a new normal correction, edit the same object and cancel the changes made in the first normal correction, set the new normal correction to status "Consolidated". In this way when you trigger the import from project task list, everything will be transported all together, which means the requests in two normal corrections will be able to cancel each other, hence no change will be made.

Comments

Actions

Filter Blog

By date:
By tag: