ChaRM: transport layer/routes used by ChaRM

Hi!
We have very complex trasport system settings and would like to implement ChaRM with parallel usage of transports in non-ChaRM environment.
We have a lot of transport routes (between DEV:100 and QAS:100) (e.g. SAP, ZDEV, ZFAD, ZGFA, YDAS).
How can we split the transport routes for ChaRM and transport routes for transports without ChaRM?
Which transport routes will be used with ChaRM?
Thank you very much!

Hi
as already mentioned in one of my replies to your last thread, ChaRM always (and only) uses the standard transport layer (route) per client.
This one and all other ones can be used for non-ChaRM transports. This is standard TMS functionality.
But you have to check if the "ChaRM check" in your project configuration accepts your TMS settings. Maybe the other transport layers/routes make waves. Then you have to change them...
regards
Andreas

Similar Messages

ChaRM: usage of ChaRM and none-Charm transport strategy

Hi ChaRM-TMS Gurus!
We have the following [SAP system landscape |http://www.file-upload.net/view-1086963/SDN_TMS_Ist_Soll.jpg.html] and would like to use ChaRM approach simultaneously.
What are the minimal requirements concerning transport layers/routes, which settings should be changed?
How much and which transport layer/routes does ChaRM need?
a) 1 any new transport layer/route
b) standard transport layer, transport layer "SAP" and others
Should all the standard transport layer/routes from virtual systems to real QAS and PRD systems or can I start as follows:
1) Leave the current TMS settings unchanged
2) Activate the extended transport control
Result: the current setting will be client specific and all the old transport requests will be moved to client specific transport routes
3) change the transport strategy (from mass transport to single transport)
3) Define new transport layer
4) Define new transport route for SAP objects from DEV to QAS
and assign the transport layer from 3) (client specific)
5) Define new transport route ZXXX from DEV to QAS
and assign the transport layer from 3) (client specific)
6) Define the delivery transport route from QAS to PRD (client specific)
7) activate and distribute the settings
Thank you very much indeed!
Thom

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

ChaRM: transport route migration

Hi!
we have a lot of different transport routes with different transport layer and would like to implement ChaRM.
We have a lot of different transport routes with different transport layer where we assign the developer classes/packages.
Now we would like use ChaRM.
As we know ChaRM uses standard transport layer and transport route.
Therefore we plan to consolidate all the developer classes/packages assigning to none-standard transport layer and route and migrate them to standard transport layer and transport route
Questions:
1) Can some one confirm whether or not ChaRM uses the standard transport layer with standard transport routes?
2) Or is it possible to create own transport layer u201CZCRMu201D, assign them all the development class/package relevant for ChaRM and leave the other none-transport layer unchanged?
3) Can one development class/package be assigned to several transport layers?
4) Has some one experience dealing with the approach of migration?
(tcode SE16 --> T_DEVC)
It will be great get some information regarding these questionsu2026
Thank you very much!

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

ChaRM: Support of more than one transport layer

Hi!
We would like to implement ChaRM for the 3 tier landscape (DEV:100 --> QAS:200 --> PRD:100) with several transport layers and transport routes:
a) u201CZDEVu201D u2013 Standard transport layer
b) u201CSAPu201D u2013 SAP transport layer
c) u201CYCSTu201D u2013 transport layer for internal customizing
d) u201CZEXTu201D u2013 transport layer for external vendor
All the transport layers should be used for the transports from DEV:100 to QAS:200 within ChaRM.
Our question:
Does ChaRM support several transport layers (SAP and none-SAP)?
Or does it accept only standard transport layer
(u201CSAPu201D and u201CZDEVu201D, but it doesnu2019t support u201CYCSTu201D and u201CZEXTu201D)?
Thank you very much!
regards

Hi
ChaRM only supports one (the standard) transport layer per client. I've already told you that some days ago... You can trust me I've configured those landscapes several times for many customers.
Enclosed please find a statement from SAP:
Transports are supported in the standard transport layer of each client. When you configure transport routes, note that only consolidation routes that are assigned to the standard transport layer of the relevant exporting client are taken into consideration. For each exporting client, exactly one target client and one target group are permitted.
We recommend that you assign exactly one development system to a production system, and that these two systems are connected by exactly one unique transport track.
If a development system and a production system are connected by more than one transport track, this may lead to inconsistencies within the transport distribution. This type of transport configuration cannot be supported by Change Request Management, and may cause inconsistencies within the tools involved.
So you have to change your TMS configuration and the assignment of transport layers to development packages. e.g. use transport layer SAP and ZDEV
Then it is possible to use ChaRM and standard TMS together
regards
Andy

ChaRM: Transport routes?

Hi!
We have the following [SAP system landscape |http://www.file-upload.net/view-1086963/SDN_TMS_Ist_Soll.jpg.html] and would like to use ChaRM-approach in parallel with non-ChaRM.
Can some one tell me how ChaRM recognizes the transport routes, if we have several transport routes in same client? (e.g. SAP, ZDEV, ZADF1...ZADFN)
Will only standard transport layer with appropriate transport routes (e.g. "SAP" and "Z<SID>") by supported by ChaRM?
Thank you very much!
regards

Hi Venu,
Transport routes should be created as per your client requirement for example you can set up the tms as below You can proceed as follow
Dev (100)->QAS (100)->PRD (100)
Dev (XXX)->QAS (XXX)
Now if the transport is created in 100 client and you want to move the same transport to other clients of dev and quality system via Charm you can schedule auto import job for other client specific to charm project it will solve the purpose.
Now for charm the main route could be Dev (100)->QAS (100)->PRD (100), create a logical component assign the corresponding 100 client's development system as Dev, Quality system as QAS and production as PRD,
Include that logical component in your charm project and then run the consistency check,
Regards
Rishav

ChaRM: Standard transport layer

Hi!
I have one question regarding transport layers for usage of ChaRM.
Which standard transport layer does the ChaRM need?
a) "SAP" transport layer
2) standard transport layer "ZDEV"
What will happen when one of this (SAP or ZDEV) will be mised or used outside of ChaRM?
Thank you very much!
regards
Thom

Thom Heinemann wrote:>
>
> Which standard transport layer does the ChaRM need?
> a) "SAP" transport layer
> b) standard transport layer "ZDEV"
Anand: ZDEV should be the standard transport layer......
All SAP standard objects will only follow SAP transport layer......irrespective of whatever standard layer is mentioned.....
> What will happen when one of this (SAP or ZDEV) will be mised or used outside of ChaRM?
Anand: Little more clarity is desired on this query....can you please be more specfic about what you meant..
Inspire ppl by rewwarding !!
Regards,
Anand....

ChaRM with several transport layers/routes

Hi!
We have a very comprehensive transport landscape where more than one transport layer is necessary.
The reasons therefore:
we implement none-SAP software and need an extra transport layer therefore
the developers still need an extra transport layer because of they assigned them their packages
Currently we have one and the same client in DEV system where all the transport layers reside.
Now we are thinking to implement ChaRM for all the transport layers.
1) Approach of splitting transport layers and working with different DEV clients
We split the transport layer and assign them the different standard layer
transport layer ZDV1: client 100
transport layer ZDV2: client 200
transport layer ZDV3: client 300
Question:
Is that possible to have here one maintenance project with more that one DEV system
(DEV:100, DEV:200 and DEV:300)?
Any helpful information will be very appreciated.
Thom

Hi Thom..
transport layer ZDV1: client 100
transport layer ZDV2: client 200
transport layer ZDV3: client 300
Why you have 3 Transports Layer???...
if you have
DEV100                QAS100    PRD100
DEV200
DEV300
Usually you have only 1 Layer from DEV100 to QAS100 (Consolidation Type)
To move from DEV100 to DEV200/300 use SCC1
IF you have
DEV100     -
> QAS100   -
>   PRD100
DEV200                QAS200
DEV300
You create 1 transport group
DEV100 -
> QAS100 ---> PRD100
                 |-->QAS200
Thanks
Wen

ChaRM taking standard SAP transport layer for a project

Hi
After creating transport request via ChaRM, we notice that the request is assigned to the transport group where standard SAP transport layer is assigned, and not to the respective project transport group.
I activated ChaRM for a project, by assigning logical component DEV-100 -
QAS-200 -
PRD-300
When creating transport request via CR, the request is created in D10-100 and assigned to /GLOBAL/ transport group instead of /PROJ01/ group. After debugging I notice that ChaRM is sending SAP transport layer and since SAP layer is assigned to /GLOBAL/, all requests are assigned to /GLOBAL/ group.
Is there any report or missing step which I should execute?
Thanks & Regards
Madhu Bommala

Hello Madhu,
To define what should be the transport layer used by Charm you should execute the report /tmwflow/set_track_generation ,
if you want to use your transport layer instead SAP layer, you should set the option NO_SAP in this report.
I hope that this information can help you.
Best Regards,
Diego Fischer

How to configure TMS for ChaRM with Customizing routes?

Hi Experts,
We have succesfully configured three system landscape TMS for ChaRM for several pipelines already. Now we are facing a situation where TMS is as follows:
DEV to QAS contains routes:
Customizing: ZEBP => 100
Transport: ZDEV => 100
Customizing: ZSUS => 200
Transport: SAP => 100
The question with these is how to add ZEBP and ZSUS to ChaRM configuration?
QAS to PRD:
Delivery: 200 => 200
Delivery: 100 => 100
Here the question is how to enable transports between 200s alongside 100?
When looking at SMSY in SolMan, SUS is a logical system only.
Has anyone of you come across a situation like this? I'm glad for any hints you may give me!
Our SolMan is 4.0 SP13.
Best Regards,
Auli

Hi
in my opinion you can configure it the following way:
Customizing: ZEBP => 100
Transport: ZEBP => 100 (not ZDEV)
Customizing: ZSUS => 200
Transport: SAP => 100
Then assign ZEBP as default transport layer for client 100 and ZSUS for client 200.
It is not possible to configure ZEBP and ZDEV for client 100 if you want to use charm
regards, Andy

What's the difference between transport route and transport layer

what's the difference between transport route and transport layer,Can somebody give me some explaination? thks in advance!

Hi,
Transport Layer in ABAP Workbench
    The Change and Transport System supports the distribution of development
    work on large projects across multiple SAP Systems.
    The packages in each development system are grouped into one transport
    layer.
    The transport layer determines whether objects are assigned to a local
    or transportable change request.
Use
    Each of your SAP development systems is assigned a transport layer as
    its standard transport layer. If you use Extended Transport Control, you
    can assign different standard transport layers to certain clients.
    You can define at the most one consolidation target for each SAP System
and transport layer.
When you create a package, it is assigned the standard transport layer
of the SAP System.
If you want to assign a different transport layer to a package, you
require the administration authorization for the Change and Transport
System.
The objects in a package automatically have the transport attributes
defined for the corresponding transport layer.
o   If a consolidation route originating in their SAP System is defined,
     then the objects are assigned to a transportable request, and
     transported into the consolidation target when it is released.
o   If a consolidation route is not defined, the objects are assigned to
     a local request, and are not transported.
Customizing settings are not assigned to a package. They have the
transport attributes of the standard transport layer of the system or
client.
It is best to assign a package a standard transport layer for which a
consolidation route originating in the development system is defined.
To display and maintain the transport layers and routes, use the
Transport Management System (transaction STMS).
Only the system adminstrator can make changes.
Caution:
     The tables TSYST, DEVL, TWSYS, TASYS are no longer productive as of
     Release 4.0A and cannot be maintained.
Regards
Ben

Using SolMAn / ChaRm for upgrade to ECC6

Good Day;
We are planning on using SolMan / ChaRm for our upgrade from 4.6C to ECC6 and I am wondering if it would be possible to do the following
Upgrade a development system to ECC6.
Define 2 virtual ECC6 Systems, 1 for the QA system and 1 for the production system
Create a project that contains all the business processes and has the above landscape assigned. This project does not have ChaRM active.
Create a maintenance cycle with the above landscape attached and ChaRM active.
As we upgrade the real QA and production systems to ECC6, we want to u201Cflip outu201D the virtual systems for the u201Crealu201D ECC6 systems.
Does anyone have any input in this type of plan?
Regards
Don

Good Day;
We are planning on using SolMan / ChaRm for our upgrade from 4.6C to ECC6 and I am wondering if it would be possible to do the following
Upgrade a development system to ECC6.
Define 2 virtual ECC6 Systems, 1 for the QA system and 1 for the production system
Create a project that contains all the business processes and has the above landscape assigned. This project does not have ChaRM active.
Create a maintenance cycle with the above landscape attached and ChaRM active.
As we upgrade the real QA and production systems to ECC6, we want to u201Cflip outu201D the virtual systems for the u201Crealu201D ECC6 systems.
Does anyone have any input in this type of plan?
Regards
Don

Is transport layer ONLY for consolidate router?

I have reviewed some STMS configurations and come up with this conclusion:
Transport layers other than "SAP" are for consolidation routers ONLY.
In other wods, if there is no consolidation router, no transport layers other than "SAP" needed.
Could you confirm my conclusion is right? And if so, why?
Thanks!

The definition of a consolidation route according to the course ADM325:
A consolidation route defines the path (the successive system and/or client) that is followed by a change request immediately after the release from the development system. Typically, the consolidation route proceeds from the development system to the quality assurance system in the standard three-system landscape.
A consolidation route is created from the development system to the quality assurance system through the transport layer Z.<SID>.
A consolidation route is created from the development system to the quality assurance system through the transport layer SAP for the transport of SAP standard objects.
Hope this helps.
Kind regards,
Mark Dijsselbloem

ChaRM: Transport of Copies

Hi Team,
I have configured ChaRM for normal correction (SDMJ). The standard SDMJ process is, when i execute the action "Complete Development", it sets the status of the normal correction as "To be Tested" as well the transport of copies also will be created. But in my case, the status of the normal correction is set to "To be Tested" but the "transport of copies" is not getting created parallelly. If i go to task list and execute the task "Create transport of copies", the "transport of copies" is getting created.
How to automate this task in the task list, so that when ever, i execute the action "Complete development", it set the status of the normal correction as "To be Tested" as well the "Transport of copies" also getting created in background?
Your guidance will be very much appreciated.
Thanks
Kumar

Dear Kumar
I think it's related to how the transport request was made, if it was made in se01 for example and not by ChaRM I think you don't have the automatic creation of transport of copies. Is that the case that your transport request was created outside ChaRM ?
Please check following SAP notes:
Note 1150426 - Registering transport requests in ChaRM
Note 1134993 - Checking transport requests outside ChaRM
Kind regards
Tom

2 consolidation routes, one transport layer - not possible

Hello everyone,
I have one DEV system and two QAS systems. Some of my development need to go to both of two systems, however some of them need to go to only one of my QAS.
So I have set up two transport groups: one link to both of two QAS and another one link to one of them. Because it is not possible for 2 consolidation routes with one transport layer, so there would be much of trouble when I need to transport my own development into that one QAS------I need to manually change the object directory entry/package for it first.
So I would like to know is there any way easier to set up the landscape so that the developer can easily choose the correct transport target in our situation?
Thank you very much in advance for your help!
Best regards,
Keith

Hi Keith,
please do not mix up transport groups (systems sharing one transport directory) with transport target groups.
If you have one development system DEV and two QA-Systems QA1 / QA2 then there are 3 options: Transport from DEV to QA1 only, transport from DEV to QA2 only and transport from DEV to both QA1 and QA2. To realize this, you need three consolidation routes starting in DEV. One with transport layer (say) ZQA1 pointing to QA1, one with transport layer (say) ZQA2 pointing to QA2 and on with transport layer (say) ZALL pointing to the transport target group which in turn points to QA1 and QA2. Then you need to create 3 packages (formerly: development classes) poining to one of these three transport layers. For example ZPACKZQA1, ZPACKZQA2, ZPACKZALL. Then when you create a programm you need to specify a package. Depending on the package you choose, the program will be transported to either QA1 only, QA2 only or both QA1 and QA2.
Best regards
Thomas

Diff. between transport route and transport layer

hi gurus,
What is the Diff. between transport route and transport layer.
Regds:
BBR.

No interview questions
Read the "Rules of Engagement"
regards
Juan

ChaRM: transport layer/routes used by ChaRM

Similar Messages

Maybe you are looking for