Skip to Content
SAP Solution Manager

How to Add a System "On-the-Fly" to a ChaRM Project Track (Part 2)

This is Part 2 of the Document 'How to Add a System "On-the-Fly" to a ChaRM Project Track'

For Part 1, see document How to Add a System "On-the-Fly" to a ChaRM Project Track (Part 1)

Add the Source System E2D, Client 601 to the Project Track "Z_LSC_TEST (Source System E2D-601)" again

Now, the entire Project Track "Z_LSC_TEST (Source System E2D-601)" has to be rebuild again from Scratch.

This means, that all referring systems, which formerly have been deleted from the Project Track, have to be re-assigned again.

Thereby the new QA-System E2D, Client 602 will be added to the System Landscape as well.

Please start by positioning the Cursor on the Project Track "Z_LSC_TEST (or on "Source Systems)", and add the Source System E2D, Client 601 (Development System) as first step.

In order to do so, you have to press the Button "Add System":

On the following Pop up you have to click on the F4-Help in order to display the systems, which are available for selection:

Mark the entry with the Source System E2D, Client 601 and press "Enter":

Quit the following Screen with "Enter" as well:

As result, the Source System E2D, Client 601 will be re-added to the Project Track "Z_LSC_TEST (Source System E2D-601)":

The Change of the Task List has to be saved to a transport request:

Add the referring Target Systems (including the new QA-System E2D, Client 602) to the Project Track "Z_LSC_TEST (Source System E2D-601)" again

Therefore please position the Cursor on the Project Track "Z_LSC_TEST (Source System E2D-601)" (or on "Target Systems"), and press the Button "Add System":


On the next Pop up, click on the F4-Help:

Now you can select the QA-System E2D, Client 602, which has to be newly added to the Project Track "Z_LSC_TEST (Source System E2D-601)":

Quit the next Screen with "Enter":

Repeat this procedure for the Target System E2D, Client 603 (System Role: Pre-production System) as well:

Add the Production System E2D, Client 604 to the Project Track "Z_LSC_TEST (Source System E2D-601)" again

As last step please position the cursor on the Project Track "Z_LSC_TEST (Source System E2D-601)" (or on 'Production Systems'), and press the Button 'Add System' in order to reassign System E2D, Client 604 to the Project Track "Z_LSC_TEST (Source System E2D-601)":

Select System E2D, Client 604 (System Role: Production System) from the following Pop up:

Quit the next Pop up with "Enter":

Finally the Project Track "Z_LSC_TEST (Source System E2D-601)" is completely rebuilt: The old Project Track Entry can now be deleted in order to tiny up the Task List:

Quit the Pop up with "Yes", which will save the changes to the Task List M0000000436:

As result the Project Track "Z_LSC_TEST (Source System E2D-601)" now consists of the

  • Maintenance System E2D, Client 601 (Source System),
  • Quality Assurance System E2D, Client 602 (Target System),
  • Pre-production System E2D, Client 603 (Target System), as well as
  • Production System E2D, Client 604 (Production System), and

can now be further used for Change Request Management activities.

In case that the Tasks within the Task List M000000436 are locked, after re-adding all referring Systems to the  existing Project Track (‘Z_LSC_TEST (Source System E2D-601’), please re-open all relevant Tasks again.

Perform a Refresh on the SAP Solution Manager Project Z_LSC_TEST

As last step a refresh on the SAP Solution Manager Project Z_LSC_TEST has to be performed.

Launch Tr. SOLAR_PROJECT_ADMIN, select the SAP Solution Manager Project Z_LSC_TEST and go to Tab "Change Management":

Press the Button "Display <> Change", and then the Button "Refresh".

The SAP Solution Manager Project Z_LSC_TEST is now completely refreshed:

Further Processing of existing Change Documents after Adding a System to a Project Track on-the-Fly

Further Processing of Normal Changes with User Status 'To be Tested'

A specific Change Document (Normal Change) is in the User Status ‘To be Tested’, the generated Transport (Transport of Copies) is in the Import Buffer of the QAS System or has already been imported to the QAS System. The original transport has not yet been released.

Now you add a new system to your Project Track, which replaces the former QAS System as Target System in the Target Group of the Consolidation Route.

After the system landscape change on-the-Fly has been performed, you want to process this Change Document further. However you cannot set the next User Status ‘Successfully tested’.

The system quits with the message ‘Not all generated transports have been imported’, and resets the User Status of this Change Document back to ‘To be Tested’.

This is due to the following reason: When further processing a Normal Change Document, SAP Change Request Management verifies, if a Transport of Copies has been successfully imported to the QAS System, which meantime has been replaced by a new System on-the-Fly. As this is not the case, the User Status is automatically reset to ‘To be Tested’.

You have alternative Options available in order to avoid or overcome this situation:

Option 0: ‘Avoid Normal Changes Documents with CRM User Status ‘To be Tested’ beforehand performing System
Landscape Changes on-the-Fly’

If possible avoid Normal Change Documents with CRM User Status “To be Tested” before removing or adding a System from(to) a Project Track on-the-Fly.

Option 1: ‘Reset the Normal Change to User Status ‘In Development’

Reset the User Status to ‘In Development’ again, and then process the Change Document again. When setting the User Status ‘To be Tested’, the system will automatically create a new Transport of Copies, which can be imported to the Pre-production System via the Task List. From there on, you should be able to process the Change Document as normally.

Option 2: ‘Make the UI Object ‘RELEASE_COPY’ editable/executable for the User Status ‘To be Tested’

Go to Tr.SPRO
Reference IMG
Solution Manager

Capabilities

Change Control Management

Change Request Management Framework

Adjust UI Objects by User Status.

Select the Transaction Type for Normal Change and make the UI Object ‘Release_COPY’ editable/executable for the User Status ‘To be Tested’.

In consequence it is possible to manually create a Transport of Copies from the Transport Assignment Block in the Web UI and import it to the new Test System.


Further Processing of Normal Changes in all other User Statuses

The further processing of Normal Changes in all other CRM User Statuses should work as usual.

It is also possible to close the current Change Cycle afterwards.

Uncompleted Change Documents are taken over and can be further processed within the new Change Cycle.

Processing of newly created Change Documents after Adding a System to a Project Track on-the-Fly

The processing of newly created Change Documents should run smoothly.


Evaluate the Impact on the configured ChaRM Workflows

Please be aware, that system landscape related changes, like described in this document, may have an impact on your currently configured ChaRM Workflows.

It has to be evaluated in detail, if the ChaRM Workflows have to be adjusted as well.

Back to Part 1<<< End of Part 2

Former Member

No comments