A Customer Use Case: Transport of Copies (ToC’s) in the Defect Correction
Today I will share some other type of blog, not directly from me but hopefully worth sharing…
Some weeks ago I got an email from an internal consultant having a specific problem. He was asked to implement the Transport of Copies functionality for a customer at the Defect Correction (in SAP standard it is only available in the normal change).
He encountered an issue because for the ‘Transport of Copies’ button on the ‘Transport Management’ assignment block this was hard-coded blocked for the Defect Correction.
As I was very busy (and still are) with SAP Solution Manager 7.2 development and we are out of SAP Solution Manager 7.1 maintenance in our group, we made some win-win deal.
I would discuss it with my colleagues if we can open the Defect Correction up in general for ToC and would create a note for it.
Before the consultant would ask the customer for permission to share the documentation of the customizing and the use case, so I can publish it here and everyone can benefit from it :-). And the customer and consultant would test my note as I did not have time to set up the use case internally
So, please be aware that this is not double-checked by me ;-). No guarantees from my side. But as we know our customers they are the final instance in testing, so hopefully everything works fine :-).
But let’s start….
The Use case:
The customer has a 4 System, 5 Client landscape, in which the Development System contains two Clients, namely ‘Development’
and ‘Unit Test’.
The customer’s Implementation Project has moved into the Test phase to allow Integration, User Acceptance and Performance tests
to be performed in their QA and Pre-Production Systems.
Customer wishes to deploy the Transport of Copies as part of the Defect Correction process to allow configuration changes to be tested within the
Unit Test client before the associated transports are released and committed to the landscape.
The Customer wishes to create the ToC’s automatically based on a change in the Defect Correction’s Status (‘In
Correction’ -> ‘To be Unit Tested’), with the ToC’s then being imported into the Unit Test Client via an import that is scheduled to run every 15 minutes.
Solar Project setup in transaction SOLAR_PROJECT_ADMIN and QGM Project Landscape setup
Here is a screenshot of the project setup in SOLAR_PROJECT_ADMIN. Note the Unit Test System as Target System as a separate client 512 of the development system RK2.
Note: all of the screenshots are taken from a Development SolMan system against a dummy backend landscape that is represented by multiple Clients within the same Sandbox System.
Here is the set-up for a QGM project. As well the UNit test client is visible.
1.) Implementing the note
Implement note 2065211.
2.) Additional Status and PPF action adaption
Then we have defined a new user status ‘To be Unit Tested’.
How to enter a new status and adept the PPF actions is described here:
3.) Customizing the ChaRM actions of the new user status
Copy the Actions that perform the ToC as part of the Normal Change process (most notably ‘COPY_ALL’) to that of the Defect Correction via the IMG Activity ‘Make Settings for Change Transaction Types’.
Customize as well the execution time of the ChaRM actions
4.) Customizing the ChaRM consistency checks of the new user status
5.) Adapting the Phase Controller Model
Last but not least the Phase Controller Model has to be adapted. For your background, the Phase Controller Model controls which actions are allowed in which phase of the cycle. For example, it checks that a Defect Correction can only be assigned to a Change Cycle in phase ‘Test’. It defines in which phases of a cycle specific actions like reassign change document, assign transports, ToC or create transport or tasks are allowed. Or other transport functions.
Call Transaction ‘SM34’ (view cluster access), edit view cluster ‘/TMWFLOW/VC_PHMD’
Select the Phase Model ‘DEVRL’, Phase ‘Test’ with area ‘Assign Actions’:
Enter the action ‘TM_TR_RELEASE’, so release of transports for the Defect Correction is allowed during the Phase ‘Test’.
Note: the Action IDs listed in this View aren’t the Actions (e.g. ‘COPY_ALL’) from the IMG Activity above. Instead, they are a ‘grouping’ of similar/related
Actions, which we will review and refine in the next step.
Call Transaction ‘SM34’ (view cluster access), edit view cluster ‘/TMWFLOW/VC_CPVR’.
Choose the Participant ‘CRMW’, variant ‘SMDV’ (Implementation Project).
Note that entries for the Action ‘COPY_ALL’ only exist for the general Transaction Types for ‘Normal Change’. Consequently, the ‘COPY_ALL’ Action is disallowed for all other Transaction Types.
Create a new entry for ‘COPY_ALL_SMTM’ (not specifically ‘ZMTM’ as the generic Transaction Type should be referenced) and map it to Action ID ‘TM_TR_RELEASE’.
That’s all customizing to be done.
What you get:
A ToC is now automatically created whenever a Defect Correction moves from ‘In Correction’ to ‘Unit Test in Process’, which is then imported automatically into the Unit Test Client via a background job by report ‘/TMWFLOW/SCHEDULE_IMPORT’ which ahs to be scheduled.
Note: the eagle-eyed may have spotted that we have also configured the automatic release of transports when the Defect Correction’s Status changes to ‘To be Retested’ (from ‘To be Unit Tested’). This is enabled via the same technique as above, albeit by mapping Action ‘RELEASE_ALL_SMTM’ to Action ID
‘TM_TR_RELEASE’. What this means for the Customer is that their Functional/Development Consultants and Unit Testers now execute an identical process regardless of whether they’re asked to work on Normal Changes or Defect Corrections.
So, enjoy, if you find any errors in it, please don’t hesitate t
o get in contact,