Moving a transport into a maintenance cycle

Hello All
I am doing some testing moving transports out of a maintenance cycle.
It appears that I can move a transport out of a maintenance cycle if it modifiable or released. What I am not able to do is move a transport into a maintenance cycle. It appears this might be a security (Role) thingy
The message I get is:
You cannot assign any requests to project
Message no. CTSPRJ043
Diagnosis
You want to create a request in project SB1_P00013, or assign an existing request to this project. However, you are not currently allowed to use this function for this project.
Anyone have any ideas
Regards
Don Newton

Good Day Srinivasa.
I am really trying to do 2 things.
1) In the current maintenance cycle there is work that was started (transport created through Change Request Management). It was requested that the work be completed in a future Maintenance cycle.
I want to (1) remove the transport from the current maintenance cycle and then (2) add the transport to a future (open) maintenance cycle.
2) There are transports that have been created outside Change Request Management and I want to move these into the current maintenance cycle.
Currently I am able to remove the transport from a maintenance cycle by using SE10, utilities, reorganize, u201Cdelete project assignmentu201D. What does not work is u201CAssign to a Projectu201D. When I try this I get the message u201Cyou can not assign any request to project SB1_P00015u201D.
I hope this gives you a better understanding of what I am trying to do.
As far as the SAP Tutor file, you could try to send it to me via the e-mail address that is on my profile.
Thanks again Srinivasa.
Regards
Don Newton

Similar Messages

Adding transports to a maintenance cycle

Good Day;
I am looking for a way to add transports to a maintenance cycle that were not created through Solution Manager / Charm
Regards
Don

Thank you very much... Me thinks we will have a look at Support stack 17,,,,,,, not the manual way...
Thanks again
Regards
Don

Moving Change requests to new Maintenance cycle after approval

Good Day
I was wondering, is there an easy way to move any give change request from one maintenance cycle to another one. An example would be.
I have a change request that currently has 1 ABAP, 1 Config and 1 Security transport assigned to our current maintenance cycle. I have been requested to move the change request (along with all the transports) to a future maintenance cycle.
Is it just a case of re-assigning the change request to the future cycle, ?
Regards
Don Newton

Hi Don,
It's a very interesting question... I think that a lot of people here need this functionality and SAP finally hear that from us.
This new functionality came with SP15. You should have a look to SAP notes 1071412, 1134993 and 1141086, it may help you to solve your problem.
regards,
Stéphane.

How do you move changes from your project developments into the maintenance development system?

Good day colleagues.
We are in the process of introducing retrofit, and the picture is clear for us, generally speaking, to retrofit the project landscape with the changes done in the maintenance landscape.
What about the other way around? We mean, when the project is set to Go Live, we understand the transports will be all added, e.g. to the Production System buffer to be moved there via Maintenance Cycle, based on the way we defined the project and the logical component being used.
However, how do you feed those project transports to your Maintenance Development System using ChaRM? or do you do that Manually? We doubt. Copying Production back into Development? no way !!!
How do you establish that? We have a sort of idea but the documents about retrofit only seem to talk about moving transports one way, as far as we have found.
Many thanks for any feedback.
Juan Carlos

Hi Piyush.
I apologize for a late close on this questioning about moving projects back into the maintenance stream.
Basically there are 2 solutions as far as we know:
1. What Vivek mentions, which is performing a cutover and repacking the project transports into 2 transports in the maintenance stream: A workbench and a customizing.   In that sense, at the end of the day you end up moving just 2 transports to the maintenance stream up to Production.   They contain all your project objects. Thanks to Vivek, again.
This is a very practical and interesting approach. The only reason we did not adopt it, is based on the fact that if by any chance we encounter an issue with a project transport object in the maintenance stream (Dev or QA), now that all is bundled together, we may be stuck right at the time weare getting ready to GoLive. How tough is going to be that issue? how easy and quick to fix?how much would that affect the whole project time frame?   Those questions made us decide to option 2.
2. What we are doing is that at cutover we move at the same time all project transports to the transport buffer of each of the maintenance stream systems (Dev, QA, and Prod).   We first open the gate to move the transports to Dev and we test, then to QA and we test, as well. If there may be an issue, and the issue can not be quickly resolved by the project team, we can go up to the extreme of using a new feature introduced in ChaRM in SP10, if we are not wrong, but definitely available in SP12. That feature provides a way to selectively decide which transports of the release are to Go Live and which ones do not, although we have no had to use that feature, yet, but it is there.
We do not see any risk on adding the transports to the maintenance buffers at the same time. There are ways to control the systems that are open for receiving transports, and the project phases, which guarantees no room for error. There have to be deliberate actions taken (more than one in our case), to wrongly move a project to GoLive before its time comes.
That is more or less the scenario Piyush.
Hope that explains the scenario. So far no decision on really publishing as a blog. It seems not to be written on stone, as consulting with different companies, each adds its own flavor to the recipe and shuffle ideas to get to what they are looking for and makes them happy.
Juan

Removing a corection from a maintenance cycle

Good Day;
I am trying to figure out how to remove a "correction" from a maintenance cycle. There is a transport assigned to the correction.
We are currently on support stack 17
Thanks all
Regards
Don Newton

Thanks Sanjai;
This part works well except that that any transports have remained in the maintenance cycle.
Not a big problem as I can use SE10 to remove the transport from the maintenance cycle as long as it is in u201Cmodifiableu201D status.
Thanks again Sanjai
Regards
Don Newton

Import of maintenance cycle with deleted transport requests in queue

We use Solution manager 7.0 with one maintenance cycle per satelite system landscape.
In this maintenance cycle Regular corrections and Urg. corrections are used.
When a transport request (connected to a correction) is re-imported into the quality assurance system.
The transport request triggers a deletion and "add to buffer" of the same request into the import queue of the production system.
The sequence of the transport in the production queue is correct before the "import all" into production is triggered via the tasklist of the maintenance cycle.
During the "import all" of the maintenance cycle into production the re-imported requests are pushed to the end of the importqueue.
The re-imported transports are imported last in the sequence and left in the importqueue.
The deletion of the request in the import queue causes this problem.
Re-importing a request is sometimes unavoidable (E.g. after a client copy to QAS).
All our satelite systems have a 3-tier landscape with a simple transport routes configuration.
We are looking for a solution to problem, this can be either technical or adjusting procedures.
Kind regards
Gert-jan Meijer

Hi Gert-Jan,
We do the same and we don't face this issue. There is thus a solution.
I never had this case, this might be a parameter in your QAS refresh procedure.
1/ If you empty your production import buffer (meaning you import it all to production) before tacking the production copy you will never have this issue.
2/ If you have some transportd left in the import buffer of production , you have this issue ? I guess this is our case
I will try to reformulate the case.
The refresh of QAS is causing the lost of some customizing that were not yet imported in production but was imported in QAS prior to the refresh of QAS.
When you reimport the "overwritten" transports in QAS after the refresh, this transport is removed from the QAS import buffer and going too the import buffer of production.
A/The same transport is now twice in the import buffer of production ? we don't have this in our landscape (I even think this was not possible)
B/Or in between this transport has been imported in production and thus you are right it falls in the import buffer of production again with another sequence.
Thank you to confirm your case A or B ?.

Transporting into a new BW system from a shared dev system

We are currently in the process of setting up a new BW system in the same landscape as our existing one where both boxes will share the same dev system. Our existing one is used by many different applications and has tonnes of shared objects on it. Our new box will only be used for SEM-BCS and thus does not need everything else that the other box contains. Since many objects are dependant on others (attributes and such) I am finding it hard to get transports into the new system. There always seems to be something missing even when I try to just move a single object. I also seem to be having troubles with InfoObject Catalogs where they cannot be moved if the InfoObjects are not there and the InfoObjects a cannot be moved with the Catalogs not there. This is all starting to give me a serious headache.
Has anyone delt with transporting to separate systems from a common development system? What is the best approach to this to ensure we only move what we need to the new system?

The transporting is the same, however there are a lot of dependant objects that also need to be brought into our system. I'm looking for a way to minimize what I need to transport into our new system.
Collecting automatically doesn;t seem to be working for me since it does not collect everything I need and when I add that missing object I then seem to be missing another list of objects. It seems to be a never ending cycle.

Maintenance Cycle creation not possible

Hello Developers,
(Solman 4.0 ChaRM)
I'm running into an issue concerning our maintenance project. I created a maintenance project, assigned systems and users to it, created an IMG, saved everything, but if I try to create a maintenance cycle via "/n/tmwflow/cmsconf", there is no project shown to choose. No project to choose = no maintenance cycle to assign.
As the system administrator insisted to create the RFCs and users manually, there might be a cause in that area, but I'm not sure.
Also if I run the consistency check in project configuration it says that the logical component "solution manager" is not used in my maintenance project, but if I run the same check in TA SMSY, it shows its usage.
I'm stuck and asking kindly for advise.
Any help appreciated.
Yours,
Rudolf Weis

Hello,
I assume you use solman 4. Let your system administrator perform ALL the steps in SAP Solman IMG --> SAP Solman --> Scenario-Specific Settings --> Change Request Management --> Standard Configuration --> Transport Management System; in the IMG otherwise it won't work.
Check the logical component (which I assume to be correct since you created a IMG project in the target system).
use the /TMWFLOW/Maintinst to check some settings as well
good luck

Question on normal maintenance cycle in 4.0

Hi
We have a maintenance cycle for normal corrections. Due to missed authorizations, when our testers changed the status of the change request after successful testing, the status is changed to 'consolidated', but the transport requests were not released. When we manually released the transports from SCMA task list, system released all the open transport requests, whose tasks are released. This has caused the issue of these transports being added to the production buffer. So now we have the released transport requests for requests that are at the consolidated status and for requests whose status in less than the consolidated status, i,e. to be tested, in development. If the status of the MC is changed to 'Go-Live' and when the production import job is scheduled, is it going to move all the transports in the production buffer or only those transports that have the corresponding change request status is 'Consolidated'? Thanks in advance.

I believe that in later Service Packs of SolMan 4.0 the "Export transport request" and "Return to development" actions described in note 910506 are not part of the standard workflows so some of these problems should not exist. SolMan uses Transport of Copies functionality when the developer performs the Complete Development action. These "copy" transports only get imported into the QA system and not into production. When the tester performs "Confirm Successful Test", the transport is actually released.
Now if for some reason the tester made a mistake when "Confirming", the correct action would likely be to do an Urgent correction to repair the problem or undo the change.

Error "no link to maintenance cycle" happens after reset to previous phase

Experts:
I have a CHaRM project which has successfully transported a few changes into production.
Then I use action "set to previous phase" several times to set this project to "development without release".
Then I create another change request by selecting the maintenance cycle of above project.
After authorizing and saving above change request, a normal correction is created. However this normal correction
has an error "no link to maintenance cycle" even its document flow shows the maintenance cycle mentioned above.
The IBase is the same as previous selected and is verified to be right.
Could you help decide what else is wrong?
Thanks!

Hi
Please go to your project and PRESS REFRESH button in System landscape-Change Requests Tab
this update the entries in database then now
goto this table /TMWFLOW/PROJMAP
Check if the Project is still locked in table /TMWFLOW/PROJMAP: If an error is detected during the processing, then the project might be locked in this table.
The refresh button will help you to get out of this problem and check also if there any other errors.
Regards
Prakhar

Maintenance cycle - Charm

Dear All,
I am in process of implementing CHARM and i am facing issue in the process flow for maintenance cycle.
In normal changes - we create change request and a maintenance cycle (MC) is attached to it. Once we change the status to Dev with release then changes are moved to Test system (transport of copies) and after successful testing (actual transport request is released) we change MC status to Test then changes moves to Test system. Then MC moves to Go live and then changes are imported to production. Now when status of MC is go live then we need to change the status back to dev with release which is not working instead it gets insync with the project phase. Kindly let me know if anyone has faced the similar situation.
Can you someone please clarify how mc status should work in case of normal changes.
Regards
Sushant

Hi Sushant,
1. try to change the phase of the project cycle without assigning any Change Document to it .
2. Number Ranges
"Before you can begin using Change Request Management transaction types, you must ensure that a number range is defined for these transaction types. The number range interval determines the sequential numbers assigned to newly created transactions. "
To do so you can use transaction SNUM and enter CRM_SERVIC as the number range object.
The number range interval which the system uses is defined in the transaction customizing in the Transaction Numbering section.
Please check the below link for more details in 3.2.7
https://websmp208.sap-ag.de/~sapidb/011000358700001056012011E.PDF (3.2.7)
Rg,
Karthik

ChaRM Action 'Transport into Sandbox System'

Hi,
How the action 'Transport into Sandbox System' works.
Wanted to know how this action works & in TMS do we need to map sandbox client.
From sand

Hi PK,
answer is Yes for the STMS and also you need to have a system defined as single type within maintenance cycle you re working in. Solman will be using your tasklist structure to understand which system is supposed to receive the import
Since a couple of stacks it became possible to actually define the role type of system that is supposed to receive the import of TR. I mean by role type the kind of system like you define in STMS when declaring a logical component
Regards
Khalil

ChaRM: Several maintenance cycles in one maintenance project?

Hi!
We are working with urgent correction within ChaRM and thinking about to implement the normal corrections as well.
Our ChaRM workflow for normal corrections is characterized by:
a)corrections with different Life cycle (those who will be processed within 1 week, other with 2 week, etc.)
Questions:
1) Is it possible to have several maintenance cycles for one maintenance project to handle condition u201Ca)u201D?
2) What will happen with all the normal corrections and urgent corrections that have a long life cycle (status: in development, test, etc.) when the charm manager set the status of maintenance cycle in u201CGo liveu201D?
Thank you very much!
H. Thomasson

Hi Holger,
Maintenance cycle and SMI project is a 1:1 relationship.
In status GoLive you will be able to continue developement/work on normal corrections but you will not be able to release any transport requests/create transport of copies so your testings in QA will be limited.
In phase GoLive you are able to import requests into production.
Normal Corrections which have not been released yet are not lost. Depending on your scenario you may switch phases back to "in dev with rel." after you imported into production. It is not necessary to close and recreate maintenance cycles if you use one project for daily/weekly maintenance.
/cheers

ChaRM - Multiple Maintenance Cycles

We now have a Quarterly release cycle; however, we'd also like to have a Weekly release cycle for the smaller break / fix changes that are not true Urgents. We don't want to use UCs for these since we'd like to move them together on Saturday morning. How can we prevent leapfrog issues? For example, if an object is on the Quarterly and Successful Testing is recorded, the object is released. If the the same object is now changed and included on the Weekly Maint Cycle and moved to production, it will be overlaid when the Quarterly Maint Cycle is moved to production. I don't think this is possible, but I was asked to confirm..... Is it possible to re-import all of the Transports from previous weeks at the time the Quarterly ones are moved to ensure all Transports are moved in the order they were actually released? Is there a way to detect / prevent leapfrog issues? What do other companies do?

If you use normal correction for your quarterly release and SDHF corrections for your weekly releases, the normal correction will move ALL transports for the maintenance project including those which are for the SDHF corrections and even those for which the SDHF correction has not been approved for production import.
If you are only using SDHF variants for your process - then there is a possibility to handle this manually through the maintenance cycle directly. There are mass transport move tasks in the task list of the maintenance projects. However, this will require a manual element to your process for the production import.
But as you may already be aware, either of these options are tricky to implement and you need to have someone with a good understanding of development and transports.
Hope this helps...
Cheers
Pranav

ChaRM Maintenance Cycle

Can anyone tell me how to close a maintenance cycle in status of withdrawn that looks like there are still unprocessed transports even though the transport objects have been moved to a different transport, and transported to production? Thanks

Hello Linda,
Can you pleae reviw these Notes, as I am pretty sure they talk about what you are trying/wanting to do
933705 Closing inconsistent project cycles
1134993 Checking transport requests outside ChaRM
Hope this helps you resolve.
Regards,
Paul

Moving a transport into a maintenance cycle

Similar Messages

Maybe you are looking for