ChaRM transport route, one development, 2 QA, 2 PRD system landscape

[Former Member]

Hello,

We have a customer who has an ERP system with a transport route which is the following:

One single Development system which feeds, 2 QA systems and then 2 PRD systems.

We are to implement ChaRM and we want to customize the tickets so that every time you execute the import action of a transport request into QA (and later into PRD) both systems QA1 and QA2 are updated and later on with PR1 and PR2.

We would like to know how to support this scenario in Solution Manager using ChaRM. How do we set up the logical component at SAP, how we define the transport route and layers, and how we define the actions in the SDHF ticket.

I appreciate your help.

Regards

Esteban

[khalil_serrhini · Accepted solution]

Hi Esteban,

this is normal behavior for ChaRM.

Please check link 1 to understand why this is normal behavior and then check link 2 to see how to resolve situation (import job)

http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm

http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm

Hope this helps

Regards

Khalil

[Former Member · Accepted solution]

Hello Gurus,

We have done additional customizing incluiding in a new action in the SDHF0001 action profile so that customizing is distributed in the other system. That creates a new SDHF transaction which points to the other route QA2 and PR2. Then we can moved the new created SDHF transaction into production.

Also we program 4 jobs using programs

/TMWFLOW/SCMA_BTCH_SYNC_TEST

/TMWFLOW/SCMA_BTCH_SYNC_UC

These jobs runs every 2 hours so that if someone forget to move the ticket into the following system, it will take care of them.

It seems that it works fine.

Thanks a lot for your help

Regards

ESteban

[Former Member]

A new test shows some questions

[khalil_serrhini]

Hello Esteban,

yeap as said above you can hav charm handling your kind of landscape. But you need to know the functionality of importing in 2 systems simutaneously that it does nt depend on how you customize ChaRM.

That is a task that is available in Header Tasks of Maintenance Cycle Tasklist (tr SCMA or /n/tmwflow/proj) called Transport Simultaneous Operations if i remember well. By executing this task you ll be able to for example import into boith QUAL at the same time or launchig multiple release in different DEV systems (not your case)...

Regards

Khalil

Edited by: Khalil SERRHINI on Jun 11, 2010 11:28 AM

[Former Member]

Many thanks for both of your answers. I will tested at my customer

Regards

ESteban

[Former Member]

Hello,

We set up a testing environment for change request management. In a solution manager we created five clients. One single development which feeds two quality systems, and final two production system. As it was said in the thread we used transport groups in the transport route. The development system feeds this transport group which feed to import queus in quality systems. We tested this transport route and transports worked well and arrives into both production 1 and production 2 systems.

Then created a logical component for that landscape, with five sytems. Then we created a maintenance project using that logical component. We created a maintenance cycle and then a task list was created which shows two delivery system, and the two productive systems. All the groups have the right actions.

However when we created a SDHF correction the system creates the task list only for 3 systems, not for the five of them.

we see that only action groups are created for development, quality 1, and production 1. No entries for quality 2 and production 2

We try to run the action which is in the general part of the task list to execute the import in multiple systems, it cames out with the correct selection of importing in quality 2 system because it is the transport group. However an error is raised saying that the actions for quality 2 are not there in the task list which is true. Finally, as short term solution, we were able to import into quality 2 and later on pr1 but done manually in the stms transactions which is not what we want to do.

Regards

Esteban Hartzstein

Edited by: Esteban Hartzstein on Aug 24, 2010 2:06 AM

Edited by: Esteban Hartzstein on Aug 24, 2010 2:07 AM

[fernando_rocha1]

Hi Esteban,

This landscape is supported in ChaRM, however you will need to use target groups.

Please check the following links to see how to set up:

First steps to work with Change Request Management scenario

/people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario

Change Request Management scenario: Usual questions and known errors

/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors

Best Regards

Fernando