Project is not released. hence cycle cannot be created error.

[former_member278348]

Dear All,

We are trying to setup change request management system in Solman 4 SP 9.

We have created a maintenance project and assigned system landscape to it.

In the change request tab in the SOLAR_PROJECT_ADMIN when we try to

create a maintenance cycle it is giving error message

"The project is not released. Hence cycle can not be created".

I am also getting following errors in the check in SPRO.

"No consolidation system found for DEV-222 (project ZOTEMAINT)"

"No track for project ZOTEMAINT with log. system DEV/222"

ZOTEMAINT is the project name.

What is the cause of these errors ?

regards

Magi

[Former Member · Accepted solution]

Hey Magi,

The cause of these error is " Incorrect TMS settings ".

So first of all ensure that you TMS is set up properly with DEV, test and prod landscape.

Reward for usefull answer.

Regards,

Anand.

[former_member278348 · Accepted solution]

Hi Anand,

What exactly to check for the incorrect TMS settings? We are actually

doing transports daily thru this route. ie DEV-QAS-PRD. If there was

any problem then transports wouldn't have worked.

Is there any specific settings to checked regarding TMS ?

regards

magi

[Former Member · Accepted solution]

Hi!

Don't know if this is of any help, but at least in our system, TMS is set client specific and mass transports are switched to single transports (settings described in SPRO). Check also RFCs and the corresponding authorizations.

I have also received "incorrect TMS settings" everytime a system has been down when I switch on ChaRM settings. We do use two systems until ChaRM is fully deployed. One is client specific (ChaRM) and the other is outside ChaRM (not client specific). Both settings work fine.

Closing Maintenance Cycle works better in SP12 than it did in SP09.

Try also instructions given to me some while ago ().

BR

Auli

Message was edited by:

Auli F

This is the link I meant to past here!

[former_member278348 · Accepted solution]

Hi Auli,

The problem is solved now. I am able to create a maintenance cycle. The

problem was with the TMS not having client specific transport route. I changed

the transport layer and in the extended transport control I added the client in

consolidation , delivery etc. After this the errors i was getting in CHARMCHK

has gone and the refresh in the change request tab is also not giving

synchronization error.

Thanks to Anand also for pointing me in the right direction.

Thanks & regards

magi