ChaRM: Creation of workbench and customizing requests in different clients

[Former Member]

Hi Experts,

we have to following issues to solve: currently when we create transport requests out of SolMan/ChaRM on the attached DEV system, the worbench- and the customizing transport requests are both created in the same client, e.g. 010, on the DEV system.

Now we have the requirement from one of our projects, that - according best-practice procedures and also recommendation from SAP - the workbench transport request is being created in client 010 of DEV while the customizing transport request is being created in another client (e.g. 300) on DEV.

Any ideas if and how this is possible in ChaRM ?

Thanks,

Martin

[khalil_serrhini]

Hi Martin,

Solmaniacs' assumptions are correct. You can have as many source clients as you want.

As long as

- STMS configuration (transport routes, and domain links) are consistent

- SMSY configuration (logical components are declared properly with assigning the right role types to systems/clients)

- Project declaration are done correctly (so that from Solman solar_project_admin you can read the STMS as confiured in the distant STMS domain)

- IMPORTANT: those configuration GO ALONG with each other !! (SMSY should nt contradict STMS for example...)

The tasklist that is generated for each Solman project will be as follow

- Node 1: Header Tasks (commun to all systems)

- Node x: Corresponding to track x declared in Project (each Source System will have his own node with the corresponding track under)

- Node x+1

- Node ...

- Last Node : Tasks for Tasklist closure - checks on scma consistancy and CTS projects closure

So you'll always have n+2 nodes in your tasklist; n beeing the number of declared source (=dev) systems in project

For each action launched from change docuemnts like creation of TR, release of TR or Retrofit (as Solmaniac said) you'll have an additional pop-up that will appears letting you choose the system you want to use for the action

Hope its helpful

Regards

Khalil

[Former Member]

Martin-

This would be my assumption: If you maintain both DEV clients as source clients in your TMS, when you generate your Task List they should both appear in your Maintenance Cycle the same way.

Then when you select "Create Transport Request" you should have the option to create it on system A and system B. In your case you would have to pull this action twice, if you needed to create both request types at the same time.

When I set up Retrofit (2 DEV systems), the system would prompt me with a choice of DEV systems to create requests on.

Test in your sandbox first to confirm.