ChaRM - Transport copies

Hi,
We are implementing ChaRM and have the following situation.
In our landscape we have two system CRM, ERP, but we have QAS only for ERP.
Then form CRM we have CRdev --> CRprd and when I create normal correction in ChaRM the both kind of request (original request and test transport) go to CRP.
The question is How do I do for only request about customizing/workbenchnot transport of copies go to CRP?
Can anyone help me?
Thanks
Daniely

Hi Christian,
Thanks for your answer but, I had tested the SDMI before.
I have the following situation:
1.Using SDMI, all transport release go to CRPRD doesn't matter if the correction was "tested successfully", because of this I needed to use SDMJ for only correction "tested successfully" to be imported to CRPRD.
2.In our landscape we have another system like R/3 and this system has QAS. Then if I change the u201Cnormal correctionu201D Iu2019ll have problem in this system.
Do you know if is there a way to configure transport of copies for each system?
Thanks
Daniely

Similar Messages

Anybody use Transport Copies using CHaRM

Hi
Did anybody use transport copies options in CHaRM? When I use it's displaying only the transport created using CHaRM. But I need the transport created outside CHaRM?
By the time configured CHaRM, developer already working on the development system and created quite bit of Transport requests. Now wants to include all those transport request into CHaRM created transport request.
Looking for 2 options.
1) Register Transport Requests
2) Transport Copies
Tried both are not working. If any otherway please suggest.
Thanks
Ava

Hi,
The option 'Register Transport Requests' will only link the outside transports to the maintenance cycle. You can't work on these transports through a Correction Document (such as Normal Correction ).
In case you have already created transports outside of chaRM and these transports are not yet released you can do the following:
1. Create a Change Request and Correction Document
2. Create a transport request from this correction document
3. In the development system to go to se09 and use the option 'Merge Requests' (and not include objects). This will delete the previous request and move all your objects to the request created through chaRM (and you will not run into any lock issues).
4. For the transports which are released you can use the 'Include Objects' option.
The transport of Copies functionality when used from within ChaRM will create a copy of your original transport and move it to the QAS system. It will not load the production buffer. In case you find any issues while testing in QAS, you can still go back in DEV and add changes to te original transport request. This way all your work gets added to the same TR and you can keep doing transport of copies for testing in QAS. Once your are ready you can release your original TR.
Thanks,
Kriti Bhalla.

Don´t create the transport copies when the change goes to test

Hi all,
I am using Solman 7.1 SP8. I am in step of the test og the ChaRM.
The scenario is:
- maintenance project;
- normal change;
ERROR : when I put the change to "pass Normal Change to Test", showed a follow messages:
And the didn´t change of the status of the Normal Change.
And the didn´t create of the transport copies.
Best regards,
Adriana

Hi Vivek,
I didn´t understand your sugestion.
What is not clear for me :
- "release the tasks inside the transport Request Manually (SE03 in target system)"
>> My request exists in source system only. If I search my transport request using the transactio SE03 in Source sysrem, I don´t found.
- Do I need to release the task of the transport request to this functionality works ?
Thank you very much for your attention!
Adriana

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

ChaRM:Release of system GRS not be determin during Create Transport copies

Hi ,
I am facing following error during Create Transport of copies in ChaRM Maintances Cycie.So we couldn't able release the TR.
Error : Release of system GRS could not be determined
We already checked some threads, but we couldn't get solution.
Kindly help to fix issue.
Regards,
Karthik

Hello,
My suggestion is execute a charm check in your project to verify if there is some consistency error.
Please, check if there is a IMG project assigned.
This will require an IMG project to be assigned and the correct logical component added which will reflect the TMS configuration.
Best Regards,
Diego Fischer,

Transport COPA new value field

Hello SAP Experts,
I have created a new COPA value field. Now i would like to transport the same to Test (Acceptance or Quality) server, can you kindly let me know how can i proceed with this.
Your inputs are highly appreciable in this regard.
Many thanks in advance.
Regards,
Pavan Kumar P

Hi,
Please read note 131664 regarding the use transaction KE3I to transport operating concern structures.
In principle you can transport a new value field with a transport of an operating concern - part 'Structures: ABAP Repository objects' in transaction KE3I.
You need to perform the following steps:
1. Value field added in source system thro tcode KEA6
2. Regenerate the environment of operating concern in source system (tcode KEA0)
3. Transport using KE3I (select: ABAP repository objects)
4. Regenerate the environment of operating concern in target system.
Via transaction code KE3I you have the option to transport specific object classes. If you select 'Structures: ABAP Repository objects' the following settings are transported:
Cross-client objects in the SAP Repositiory
- Tables and structures of the operating concern (CE1xxxx - CE8xxxx)
- Domains and data elements for CO-PA characteristics
- Master data tables for CO-PA characteristics (without data)
Cross-client control tables
- CO-PA field catalog
- View directory
Normally we advise customer to add a new value field/characteristic to
DEV then transport to QAS and then transport to PRD. This ensures that
the operating concerns in the 3 systems are in sync.
regards
Waman

Transport COPA Value fields

Hello Experts,
I have the scenario wherein we need to change the description of certain value fields & transport it to test & production system. I know this can be done via KE3I in which we can transport the entire operating concern but my interest lies in whether there are any potential impacts on production system in which there is already transaction data? Does this function transport the entire customization tables of COPA ? If transported to live environment, any impacts?
These questions are only to those COPA experts who have transported operating concerns for live systems containg transaction data.
Regards,
Amol

Hi
I am interested to know why you are looking for this change if want to change for reporting purpose you can change in BW from where we are getting the reports .
when you regenerate Operating concern, the old data needs to be dropped and reloaded again
which is a mamoth task and not advisable by SAP as well ,as dropping data and reloading the same their is no validation cycle for the same
Thanks
Deepak

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

ChaRM: Transport reuqest status inconsistency

Hi Gurus,
I am having a problem when passing a correction to test in ChaRM. The error shows as "Not all transport yet released".
When checked from SE01, all transports concerns are indeed released.
I then ran a report from /tmwflow/reporting to see transports included in the ChaRM in question. There the statuses of two (out of all four) requests were shown as "D" = Modifiable. The other two were shown as "R" = Released.
I am wondering if this has anything to do with my not being able to proceed to the next status?
BR Li

Hi
I escalated the issue to SAP, it was found that three out of all four requests of the ChaRM (SDHF) seem not to have a CTS project assigned. All four requests are connected to the urgent correction task list but not to the maintenance cycle (CTS project). The analysis was that the CTS project assignments to the requests may had been removed in SE09. The requests/ChaRM were created by a developer and I couldn't not check/confirm if this was indeed the case. They cannot be added to project from the maintenance cycle's task list either as they had been released.
Nevertheless I am still puzzled by the status inconsistency information. From report /tmwflow/reportingn, and from table /tmwflow/trordhc all shown that the three troubled transports were not released. I am not sure if this missing CTS project connection is the reason the information cannot be read correctly. I don't know when ChaRM is doing the consistency (condition) check regarding release and import when "Pass Correction to Test", where the information is checked/read.
SAP suggestion is to import the requests manually with STMS. This of course is not the best solution, however there seems not another other trick to proceed with the ChaRM. I cannot set the status to the next with CRM program either. The "not all transports yet released" error persists.
Siddharth, thanks. Yes, the report i used was the one ended with "n".
Jansi, for some reason the note you suggested cannot to downloaded from snote tranaction in SolMan, so I haven't implemented it yet.
BR Li

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 Consistency

Dear Experts,
I have a questions that is related to the transport consistency with ChaRM. Scenario:
1. I create a change at an object X using a normal correction and transport it to the QAS system via the maintenance cycle functionality
2. Now I make another change to the same object X using an urgent correction and transport it to QAS and PROD quickly
3. After the maintenance cycle is updated again, the normal correction is imported to PROD and overwrites the urgent correction again (?) ! This would revert the urgent correction!
Is there a functionality that controls these inconsistencies?
Thanks for all answers!
Regards,
Marc

Hi Marc,
This will depend on how you have customized your maintenance cycle. When you've customized your own variant for the tasklist associated to your cyle or use the correct standard one (SAP0 not SAP1), make sur that you've selected the option Transport Request remains in import buffer after import.
By choosing this, your transport requests associated to urgent correction will stay in import queue after being imported in QA. This means that when you will import the project the import sequence will be preserved and no regression will occur.
Hope this explaination will help you.
Best regards,
Stéphane.

ChaRM - Transport copies

Similar Messages

Maybe you are looking for