Is it possible to transport requests to 2 QA clients with ChaRM?

[Former Member]

Hi

If there are 2 QA clients and requests need to be tranported to both clients at the same time,

can SolMan ChaRM handle this?

Transport route is as follows.

DEV_______QA_______PRD

200___->__300___->_100

______--->__500

Anybody has experience?

My version is SolMan 7.0 SP16

Thank you

[Former Member]

Guys this tread has been very helpful. My problem is different. I have a target client in my dev machine of /ENT_ABAP/ for workbench request. We recently change our QAS system from C00 to C03. We created a new Logical Component and Project for this QA change. But when we create a transport in Charm it default to target group co3:100 instead of /ENt_ABAP/ which it did before. I am a Basis consultant so Charm configuration is not my expertise. Any help to get the default target groups to say /ENT_ABAP/ instead of c03:100...

donald.smith3 at pseg.com

561-967-2695

[Former Member]

Dear, I am with the situation a little different. Instead of having two clients in QA, I can two of DEV.

Today I have the charm implemented and working correctly, only a client of DEV. I need to create a request that I can tell which client I need. I am not able, someone has been there?

My landscape today is:

DEV-> QAS -> PRD

300 100 100

I need to configure to make

DEV -> QAS -> PRD

(300 OR 310) 100 100

Thanks,

Mag

[Former Member]

Hi Mag,

the standard solution is to have one customizing client and one development client (thus 2 client in DEV). (At KONE we use only client to do both one but the programmers manually change the target group of the workbench transports)

Depending on the object type the target group will be thus different

Now if you want to customize in 2 different clients you will face consistency issues like we had in the past in our company when we were managing every project in a different client. Consolidation was a nightmare.

We are not doing it anymore but I guess this is still possible even with solman

The first step is to customize TMS correctly and open 2 customizing client.

Because transport are client independent, you should be able to work in both but for the release I am not sure how SOLMAN is going to the right client. Maybe SOLMAN is smart enough to ask you in which development client you want to work....I hope some other have this experience, I don't have this one with solman

good luck

br Xavier

[Former Member]

hello,

we are using 3 different clients in QA and this is working fine.

But don"t forget that one of them will be the main QA.

If your TMS is set-up correctly, (meaning you can test your transport route without CHARM in a first place)

this is working fine. You must first check this at TMS level.

Don't forget to check your SMSY. (system component)

if you need this only for one project you only need to create a new project or update the correspind project

in SOLAR_PROJECT_ADMIN when you include your system component check that all target clients are defined there. If not you can still do it manually.

important note : If you have already projects running you need to update all your projects manually

feel free to ask

best regards

Xavier

[Former Member]

ulf

Thank you for the info. I knew the word, but did not know what it does.

Xavier

Thank you! Can I ask you 2 questions?

1) Do you use target group?

2) If not, I assume that you transport requests to indivisual clients manually. How can you do that with SolMan? What action definition/method make it possible? (standard method?)

Especially, how can you specify target clients?

Thanks again in advance.

[Former Member]

hello,

1. we use one target group for Workbench development and one for customizing (default one)

we have a particular set-up that is not classical (one signel development/customizing client, classically you split into 2 different development clients)

2. when the release is done all target buffers receive the transport and we import automatically every 30 min OR manually via solman (ur.gent correction)

best regards Xavier

[Former Member]

Hi,

If you have 2 QA clients,as Xavier mentioned you can create target group and do the import.As per the ChaRM reuirement you will set a default client for the QA system.So once a TP is moved to the mentioned QA,you can run a report that will import the TP to other QA clients/systems as well.

For auto import of TPs to parallel test systems use the report

/TMWFLOW/SCMA_BTCH_SYNC_TEST from se38.Schedule this report as a background job with the proper varian.

Hope this is helpful.

Regards,

Avinash.

[Former Member]

Thank you for the advice.

I created transport target group. With the setting, transport created in DEV 200 is added to que to QA 300 and 500. This is one great progess. But I noticed that still each tranport needs to be imported indivisually by STMS (not one import action).

I want a operator in Solman to perform tranport to several QA clients. In my example. QA 300. 500

DEV_______QA_______PRD

200___->__300___->_100

______--->__500

Does anybody know if action "HF_EXECUTE_ACTION IMPORT_TEST" can import transport to several QA clients? (First of all, I wonder how several QA clients are confuired in Logical components (SMSY)

Regards

P.S. How do people know special reports like /TMWFLOW/SCMA_BTCH_SYNC_TEST? Is there any technical documentation from SAP about "hidden" reports/techniques?

[Former Member]

Hi,

What you want to do is all supported by standard SSM, but requires ChaRM customized:

- TA: SCMA, there is a function "Perform transport tasks in several systems"

- Within that function you can easily activate to which system you want to transport.

- ChaRM is then taking care of your transports through the systemlandscape

Good luck,

Kind regards,

Rutger

[Former Member]

Thank you, everyone.

I added the second QA client (500) to logical component (T-cd: SMSY) and maintenance project (T-cd: solar_project_admin). Also extended transport is activated and target group is created (T-cd: STMS), which contains 2 QA clients (300, 500).

One problem arises. When I perform uergent correction (SDHF), the second QA client (500) does not appear in the maintenance cycle (HXXXXXXX). I can manually add the client to the maintenance cycle in SCMA. But, why doesn't the second QA client (500) appear in the maintenance cycle from the begining?

On the other hand, the second QA client (500) appears in regular maintenance cycle (MXXXXX) without manual addition.

Is there anyway that the 2nd client appear as a default system?

Thank you

[Former Member]

hello,

I have the same behaviour in my landscape. Only the systems in the main path is available in SDHF task list

I would say this is normal.

Why is this normal ?

Because the ur.gent correction is to be considered like an emergency process that doesn't superseed the normal maintenance but that complement it to have a faster change in place.

That means the ur.gent transport will follow the normal maintance process anyway

If you miss the ur.gent transport in the other QA client you may schedule the following task in your project tasklist

/TMWFLOW/SCMA_BTCH_SYNC_TEST or online

/TMWFLOW/SCMA_TRIMP_SYNC_TEST

This is not obvious how this is working and I am currently evaluating this solution in another thread

[|]

on your side you may also want to evaluate this tasks ?

br

Xavier

[Former Member]

Xavier

Thank you for the infor.

> /TMWFLOW/SCMA_BTCH_SYNC_TEST or online

> /TMWFLOW/SCMA_TRIMP_SYNC_TEST

I will try these.

(maybe next week. I am swamped in other issues....)

[Former Member]

xavier

Sorry for my late reply. I did the investigation of multiple QA client import and got the result.

My landscape is

DEV QA PRD

100 --> 200, 300 --> 100

---> QA 200, 300 are in same target group

--> QA 200 is the main QA route

I run TMWFLOW/SCMA_BTCH_SYNC_TEST and it works well.

But, online program /TMWFLOW/SCMA_TRIMP_SYNC_TEST does not work even though

it is excuted in the corresponding task list. It returns error.

I think I will go with TMWFLOW/SCMA_BTCH_SYNC_TEST, but you know how to execute /TMWFLOW/SCMA_TRIMP_SYNC_TEST? When and with what parameteres?

Regards

[Former Member]

I havn't work with charm yet, but you can do this by using target groups. For this, you have to activate the extended transport control (http://help.sap.com/saphelp_crm50/helpdata/en/1b/9dc2d6e59911d184810000e8a57770/content.htm) by setting the tp paramater 'CTC' to 1. Then you can define target groups and in this target group can be any system.client.

Hope it helps,

Regards,

ulf