Skip to Content

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.

/wp-content/uploads/2014/09/project_548626.png

Here is the set-up for a QGM project. As well the UNit test client is visible.

Landscape.png

The Customizing:

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’.

Status of DC.png

How to enter a new status and adept the PPF actions is described here:

http://scn.sap.com/community/it-management/alm/solution-manager/blog/2012/06/06/how-to-insert-a-new-user-status-in-charm-in-71

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’.

CHaRM Actions.png

Customize as well the execution time of the ChaRM actions

ChaRM actions -execution time.png

4.) Customizing the ChaRM consistency checks of the new user status

Customize these ChaRM consistency checks, mainly as in the Normal Change.
Charm Consistency checks.png

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.

Phase controller model.png

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’.

phase controller 2.png

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.

UI 1.png

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,

best regards,

Michael

To report this post you need to login first.

10 Comments

You must be Logged on to comment or reply to a post.

  1. Vivek Hegde

    This is very interesting Michael, I shall give it a try sometime soon. As of now my customer does not have any idea of ToC in Defect Correction, and I hope they do not come across this blog since we are already overloaded πŸ˜† πŸ˜† πŸ˜† (*pun intended)

    Thanks again, your blogs are always very well constructed.

    Cheers,

    Vivek

    (0) 
  2. Louis Nicolas Arson

    Nice blog!

    Thanks for sharing this howto … but I still confused : What is the interest of Defect Correction instead of using Normal Change ?

    Normal Change is powerful and very convenient. I use it even during our testing phase…

    (0) 
    1. Michael Vollmer Post author

      Hi Louis, the defect correction is the SAP template for the test message. The normal change is for project-based development. In SAP Standard, the defect correction is only allowed to be created during phase ‘Test’. And it doesn’t need to be approved via RfC, you create it in SAP standard always stand-alone. And the status flow is different but normally customers change this nevertheless.

      Hope that clarifies it somewhat.

      best regards,

      Michael

      (0) 
    1. Raquel Pereira da Cunha

      Hi Michael Vollmer,

      I tested it in two different scenarios (landscapes with 4 and 5 clients, but it doesn’t really matter) and with and without tasks in the transports (I tested the scenario where objects are included directly in the transport) and it worked properly.

      The only thing that I had to do that is not described in your blog was to add an entry for the new status in table AIC_PROC_EDIT for RELEASE_REQU. But I only needed it because I didn’t configure the automatic release while setting status “to be Retested” as you did, so I needed the Release Transport Request button to be visible. Otherwise Everything would be ok.

      Just a comment: in your picture showing the creation of entry “COPY_ALL_SMTM”  we see “RC_TR_RELEASE” instead of “TM_TR_RELEASE”,  but as you explained it correctly in your text, I don’t think people will do it wrong.

      Thank you again,

      Raquel

      (0) 
  3. Annie Tran

    Hi Micheal,

    Thanks for sharing. I’ve followed your post Β and have it work perfectly. However, my client asked me if it is possible having the button Transport of Copies on the Transport Management Block ?

    I have done my search but it seems like it not standard SAP. Do you have an idea?

    Thanks again.

    (0) 
  4. Michael Vollmer Post author

    Hi Annie, for the button Control check the user Status dependent Ui Control in the charm Framework area. It should be made editable for the defect correction with customizing.Β I am not quite sure if the Code itself allows it. Might depend on your stack…Cheers Michael

    (0) 

Leave a Reply