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

Similar Messages

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

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

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: 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: 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

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 strategy

Hi!
We have the following system landscape:
EO1 --> QO2 --> VO2
EO1 --> VO3
VO2 and VO3 are both the virtual systems.
Between EO1 and VO3 and Q02 and VO2 we have a lot of transport routes (SAP, YABK, ZEO1, .., ZIAN).
Now we would like to use ChaRM approach with new client specific transport routes (EO1 --> QO2 --> PO1) as well as leave the old TMS settings unchanged.
The questions we have:
1) Do we need standard transport route u201CSAPu201D for the ChaRM approach?
2) Can we leave the old TMS configuration for old requests, but use ChaRM with new configuration?
Thank you very much!
regards
Thom

Thom,
1) The suggestions I see:
    a. create a Transport Group which contains your VO3 and QAS system and create the necessary transport routes to this group. If you now setup your project for ChaRM and only specify the real systems, SolMan will recognize the correct systems (even though it will give you a full overview of STMS when clicking the button 'Shipment Routes' in the System Landscape of the project - once the Task List is created, you'll see ChaRM only mentiones the systems you've added in the System Landscape). The disadvantage of this is that all Transport Requests you release in your DEV system will be added to the import queue of QAS and VO3. This is of course only a disadvantage if both systems don't need to receive the same changes.
   b. Not 100% sure if this is technically possible. Create separate consolidation routes for VO3 and QAS from DEV. Again when you specify the correct systems in the project, SolMan will use only those.
As far as I know, ChaRM doesn't make a choice based on type of transport route, such as 'SAP'.
2) a. I know 'single transport' is recommended by SAP, but this is not a showstopper for the configuration of ChaRM. ChaRM also works with 'mass transport'.
    b. ChaRM needs to be client-specific, can be that here there is some interference between ChaRM and non-ChaRM.
    c. As ChaRM corrections are all assigned to a Maintenance Cycle and a Maintenance Cycle is based on a CTS project in your DEV satellite system; SolMan is in complete control of your Transport Request. What I mean with this is that if you do automatic import on your systems, only your non-ChaRM changes will be imported. Because by default ChaRM changes all status switches of the CTS project to 'inactive'. From the moment you trigger the import from a Transport Request out of ChaRM in Solution Manager; only then the necessary status switch will be activated and it will be possible to import a change into your satellite system. Periodic import of ChaRM changes is also possible, but has to be scheduled using the correct Task List out of SolMan.
You can look and change these status switches manually in your satellite system with TA SPRO_ADMIN, select the correct project and navigate to tab Transport Request. Here is a button 'CTS Status Switches'.
Hope this helps you a little further!
Good luck and let me know if you have any more questions...
Roel

STMS Transport Route Administration - Import Targets not modifiable.

Hello. I'm trying to configure cCTS for use with CHARM. I have created my system clusters and defined a consolidation and delivery route for the clusters. Now when I double click on my clusters in edit mode and navigate to the Import Targets tab, I am not able to modify this tab. I have been following the cCTS for CHARM and QGM Configuration guide.

Thanks Jessica
I'm also working with OSS SAP Support now to try and resolve my issue.
In short I can some up the problem and testing completed so far.
To Start:
The Server group removed old QA server from our SAP Landscape, therefore STMS Transport Route required rebuilding.
Systems:
We have a very complex system setup with SAP R3, CRM and BW systems. Each system has it's own server (Dev = R3D, CRD & BWD, QA Testing is now = R3T, CRT & BWT, Production = R3P, CRP & BWP) The Original QA servers are now being removed (R3Q, CRQ & BWQ)
CRD is the Transport Domain Controller, with transport bins located on CRD for R3D & BWD, CRT for R3T & BWT and CRP for R3P & BWP. (Firewalls and Server locations are the root cause for the different Trans Directories)
Transport route:
Transport route for SAP R3 was: R3D -> R3Q -> R3T & R3P (in a delivery group). The new Transport Route needs to be R3D -> R3T -> R3P.
Main Problem now: With the Transport Route configured like R3D -> R3T -> R3P, any new transport requests created in R3D moves to the R3T Import Queue automatically when the transport is released. Once the transport is successfully imported into R3T, it should automatically be added to the R3P Import Queue, but does not.
Present work around: I've reconfigured the Transport route to R3D -> R3T & R3P. Any tranport request once released, is successfully added to both the R3T & R3P Import Queues.
I have checked all SAPService<sid> OS users and passwords, ensured that the TMSADM user was recreated and working on each of the systems, used telnet to log onto each of the servers from each of the other servers at the OS level (to ensure it's not a landscape firewall security issue), I've also checked all RFC connections in the same manner (to ensure each system can reach the others), recreated the route from R3T to R3P as both a Consolidation and a Delivery type of route,
I will post any resolution found later.
Thanks for the help anyway

Transport routes issue

Hi,
I have two solman systems in my landscape.
Dev Solman has following clients : 100, 801, 802, 803, 804
Prod Solman has : 100, 200
I have created the transport routes as below :
Transport layer 1:
prod solman 100---> 200
Transport layer 2:
dev solman 100 to prod solman 100
Transport layer 3:
dev solman 100>802>803-->804.
For this
Here I need a route actually from dev solman 801>802>803-->804.
How can I get the development systems to start from client 801 and also client 100 for the same system ?
Regards,
Kaustubh.

Hi
it is posible by just defining the system roles means client roles and the proper landscape definition in smsy.
might be this give [ChaRM - Mainenance Cycle in two system landscape - possible?|ChaRM - Mainenance Cycle in two system landscape - possible?]
Jansi

Unable to add transport route in HANA Application Lifecycle Management (XS)

Hi There,
When we are using HANA LM to create transport routes then routes are created but straight away it comes with following error message:
Internal Error: Transport Route(s) could not be retrieved.
We have checked that required roles are assigned to user. Roles are
sap.hana.xs.lm.roles::ExecuteTransport
or
sap.hana.xs.lm.roles::Administrator
Same works in DEV and PROD environment. I ran debug in Chrome and found that it is throwing an error when trying to run following:
http://XXXX:portnumber/sap/hana/xs/lm/core/transport.xsjs?enrich=true&_=XXXXXXX
After looking in HANA studio I have found that transport.xsjs has got following function which will throw above error on exception:
function retrieveTransport(req, res) {
if(!utils.checkForPrivileges(res, [ "sap.hana.xs.lm::Display"])){
    return;
var item = utils.getItem(req.path);
var enrich = req.parameters.get("enrich");
var deleted = req.parameters.get("removed");
try {
    if (typeof item === 'undefined') {
      var transportRoutes = trans.readAllTransports(deleted);
      if (enrich) {
        enrichTransportRoutes(transportRoutes,deleted);
      utils.setNoCacheHeaders(res);
      res.contentType = 'application/json';
      res.setBody(JSON.stringify(transportRoutes));
      res.status = $.net.http.OK;
    } else {
      // retrieve transport path id
      var tpath = trans.readTransport(item);
      if (!tpath) {
        utils.reportError(res, null, utils.getText("TRANSPORT_ID_INVALID", item));
      } else {
        res.contentType = 'application/json';
        res.setBody(JSON.stringify(tpath));
        res.status = $.net.http.OK;
} catch (ex2) {
    utils.reportError(res, null, utils.getText("ROUTES_NOT_RETRIEVED"), ex2.toSource());
Please see attached chrome console log for more info:
I am able to retrieve information about this but I am not sure what is causing this. Your help will be really appreciated.
Regards
Angad

I've also tried the following wlst:
createJCRFileSystemConnection(server='SERVER-MS1', appName='application', name='Repository', path='/APP/ContentRepository/')
But then i'm getting:
java.lang.UnsupportedOperationException: Could not find MBean operation "createConfig(java.lang.String)" for MBean registered under "oracle.adf.share.config:ApplicationName=application,name=ADFConfig,type=ADFConfig,Application=application" and implementd by "class oracle.adf.mbean.share.config.RuntimeMXBeanImpl"
Error in creating configuration with name "oracle.adf.mbean.share.config.runtime.webcenter.doclib.AdfDoclibConfig"
java.lang.UnsupportedOperationException: Could not find MBean operation "refresh()" for MBean registered under "oracle.adf.share.config:ApplicationName=application,name=ADFConfig,type=ADFConfig,Application=application" and implementd by "class oracle.adf.mbean.share.config.RuntimeMXBeanImpl"
An error occurred while performing "setAttribute" on "PrimaryConnectionName"
javax.management.RuntimeMBeanException: These mbeans encountered exceptions and may not have been saved
Repository- JCR -- Could not do this operation, the backing store for this context is read only.Edited by: Harry van Oosten on May 10, 2010 10:33 PM

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

COMPUTE_BCD_OVERFLOW error while saving transport routes

Hi,
When we are creating new transport routes with domain controller ABC. It is giving the above dump.
Dont know what to do. FYI we deleted previous TMS config and created new one.
Thanks,
Rohan

Check the values which you are passing to the BDC.. the data type should be changed for a field.
You can execute the BDC with mode 'A' & check.
Best regards,
Prashant

How can I add a system to the transport route?

Hi,
 I have a DBP --> PBQ --> PBP systems and now I have a new environment TRN (Training system) and I want to include this system in the transport route.
Right now the transport route is configured like I said 'DBP --> PBQ --> PBP' and I want to include this environment (TRN) to the transport route because I want that the system pass automatically the orders that going to PBP system to TRN too in the same time that pass it to PBP. For example, like this:
 PBP
DBP --> PBQ ==>
 TRN
How can I do that?
<removed_by_moderator>
Read the "Rules of Engagement"
Thanks people!!
Edited by: Juan Reyes on Apr 16, 2009 8:57 AM

Hi Carlos,
whatever be the environment, whether it is DEV, QA or PRD, when you login into an ABAP SAP system and run transaction STMS,
In the initial screen, it always shows two fields, System and Transport domain.
System field contains the SID in which you are currently logged in.
Transpor Domain shows value like this: DOMAIN_SID
here this SID is the domain controller for the system in which you are logged in
However, if you are logged in the domain controller system itself and then run STMS, then it will show in the lower half of the screen, that, you are logged in as a Domain Controller.
To be more clear, run STMS in any system and Menu->Overview->Systems->Second column 'TMS system type' must contain a 'domain controller symbol' against one sytem SID. this SID is the domain controller.
thanks
Bhudev

Function module/BAPI or standerd program to define Transport route

Hi All,
I am configuring the TMS configuration through ABAP program .
I am able to configure Domain controller, and able add system to it.
Now I am not able to define Transport route, Can anybody tell me how can I achive this?
Is there any function module/BAPI or standerd program for it?
Thanks,
Swarup

Hello
To check the BAPIS to related module go to swo1 tcode.
Thank u,
santhosh

Multiple CTS+ non-abap transport routes

Gurus:
We find a document about CTS+ as follows:
https://websmp104.sap-ag.de/~sapidb/011000358700000517932007E
On above picture, OTO is the shared DEV system.
1) Is this correct?
2) if we have different DEV systems for different landscapes, what should we do?
All are non-abap ststems in this discussion.
Thanks!.

Hi,
the transport route's definition that you described (OTO as start system of all transport routes for CTS) is only valid if your CTS-System is on NW 7.0 SPS 12. Starting with NW 7.0 SPS 13, the 'real' development system is also set as the starting point in the transport route.
Are you using SPS 12?
You can find a detailed description on CTS+ on help.sap.com: http://help.sap.com/saphelp_nw70/helpdata/EN/45/ec25370fdc3481e10000000a1553f6/frameset.htm
If you need information on CTS, please take a look at the CTS page here on SDN: Change and Transport System
hope this helps
Karin

Need Transport route for two systems(Urgent)

Hi All,
I have configured everthing like configuring domain controller and added to to domain controller.
Now i need to do below steps
I have Development (client) and Quality(client) in same system and Production as separate server.
I want to configure transport route from Development client to Quality client and from Quality client to Production Server.
Development Server SID is DEV ( Dev Client 100 and Quality Client 140) and Production Server SID is PRD
Transport route must be configured like below:
DEV( Dev client 100) -> DEV (QAS client 140) -> PRD
We are struck with this
Best Regards,
Pratyusha

Hi Pratyusha,
As far as configuring Development and Quality systems concern, in one system is not suggested. I think you are aware of this.
However, I need some more information on your question like the operating systems which you are using in DEV/QAS and in PRD.
First, configure the Domain Controller in either DEV/QAS or PRD.
Irrespective of the OS, you need to maintain IP address along with the host name and fully qualified domain in the etc/hosts file.
for example DEV/QAS system ip address is 172.16.23.14 and host name is abc007, then you need to make an entry in etc/hosts file at the OS level as follows.
172.16.23.14 abc007 abc007.yourcompany.com
where in abc007.yourcompany.com is the fully qualified domain name.
Once you done this in both, DEV/QAS and PRD, systems, then configure 3 system landscape from STMS tcode in the other system which is not a Domain controller.
I hope this is helpful. Getin touch if you have any more questions or doubts.
Regards,
Satish.
Edited by: Satish Arram on Jul 31, 2008 2:06 PM

ChaRM: transport route migration

Similar Messages

Maybe you are looking for