Maintenance Optimizer - Can't create new transaction

[Former Member]

Hi,

My SolMan system is at SP15 on the ABAP stack and due to project politics the Java stack is at 12

I use the maint Opt transaction quite often due to a upgrade project we are undergoing and it seems that when i create a new Maint Opt transaction and select a system it displays these messages:

Warning Status was reset by system

Warning There is already a transaction for the systems of this product version

I had a look and found this note 1030498 and went through it but it seems i still get the error message. Does anyone know if the problem is somewhere else?

Thanks,

Mani

[Former Member · Accepted solution]

Hi,

I have to say that this is actually not an error. It is not allowed to

process two maintenance transaction for the same system.

You may withdraw the previous maintenance transaction by clicking on

the "withdraw" button.

You may also deactivate the checks following the steps below then you

would be able to continue with the transactions in spite of the

message "There is already a transaction.....".

SPRO

-> Solution Manager Implementation Guide

-> SAP Solution Manager

-> Configuration

-> Scenario-Specific Settings

-> Change Management

-> Change Request Management

-> Extended Configuration

-> Change Transaction

-> Change Transaction Types

-> Consistency Checks in Change Request Management

-> Assign Conditions to Status Values

Please change the condition 'SYSTEM_ASSIGNMENT' for the

transaction type 'SLMO' in respect of the message type from 'Cancel'

to 'Warning'.

Best regards,

Felipe Pitta

[Former Member]

thanks all!

[Former Member]

Mani

If you received the message even though there are no other open maintenance transactions for the system in the solution, then you should implement Note 1165890 - MOPZ: Withdrawing maintenance transactions

and check Note 1296589 - MOPZ: Not able to continue to step "Select Files"

Bhudev