Reimporting of Request while doing normal correction

[Former Member]

Hi all,

We are using SOLMAN 4.0 and SCM functionality.We use a same maintenance cycle and after doing all the imports to production system at Go-Live phase,we agian change the phase to "Developement w/o Release" and do the maintenance cycle activity again.But while doing the normal correction again using the same maintenance cycle we have found that all the request that has been moved in the previous run has also been imported again.What can we do to stop this reimports?

Pls help on the above issue.

Thanks in advance,

Avinash.

[Former Member]

Hi Avinash - looks like someone other than me is bothered by this feature...!

You're quite right that by using the standard maintenance cycle process and 'recycling' like this, you're gonna end up importing the same stuff, including any urgent corrections, again and again. It'll get to the point where you can't process things within anything approaching a reasonable time frame.

SAP's alternative ? Multiple maintenance cycles... OK, but then how do you decide which of the several open maintenance cycles to drop your new change into ? How to handle the fact that very soon you've got incomplete changes linked to a dozen (or two dozen... or a hundred) open maintenance cycles ? You've got 10 landscapes under SolMan control ? Make that a thousand open maintenance cycles... OK, sorry, getting carried away there, but you see where I'm going !

The reasoning behind it is that this is the only way you're able to ensure that your transports are always imported in the correct sequence. Fair point... terrible solution though.

We got around this by treating every change we make as an urgent correction (and SAP have subsequently 'released' this as a model that can be used, though it's not recommended). We have everything in a single maintenance cycle in which the status is never changed and push the CDs through individually. We have of course lost all control of import sequence, though that said, it's certainly no worse than it was under STMS.

This way at least our developers can keep developing, our testers can keep testing all the time, and we do of course have the benefits of a more tightly controlled (in terms of approving and migrating changes). We have lost some functionality too, but overall there's a net gain...

Guess this doesn't help much, but good to share the experience !

Cheers -ILL

[Former Member]

Hi ILL,

Thanks for sharing your experience.We are also using only urgent corrections now.Hope SAP comes with a proper solution sooner are later.

Regards,

Avinash