Aborting a system measurement (rollback) in USMM

[Former Member]

Good evening

It appears a partial system measurement under transaction USMM was performed (the status reads Data Not Sent To SAP) last February, likely as an accident when the last user classification was being performed.

We are now in May and would like to "roll back" (erase) that data and redo the measurement (the data is invalid anyways since it is in February). Is there a way to reset the status so a new measurement process can be started from the beginning? I found an OSS Note called "Note 1150840 - System measurement: Unlocking the USMM" that could help if you want to perform a new measurement but I would prefer any other solution to erase the last system measurement.

Kind Regards

Moggie

[former_member199816]

Thanks a lot patrick unlock command worked for me

[Former Member]

Just a quick note for everybody who's facing the same issue:

Using command "%UNLOCK" in the command field (as mentioned in note 1150840) works even though you cannot implement note 1150840 itself (e.g. if your SAP_BASIS release is greater than 700).

[Former Member]

Thanks a lot Patrick !

It worked perfect to me...

[JPReyes]

What's stopping you from running an new measurement?... if the date for February was not complete or its obsolete then simply run a new measurement and submit.... Or the problem that you had is preventing you from running a new measurement?...

Regards

Juan

[Former Member]

Good morning Juan. Thank you for your prompt reply.

When clicking either the statistics or log button, I get a message "1 measurement job(s) is/are not yet started or still running" (message code BV133)

I suspect the measurement job it is referring to is the transmission job invoked when the "Send to SAP" button is clicked. That would likely solve my problem but I don't want to transmit just yet

Regards

Moggie

[JPReyes]

I see, unfortunately I don't have an answer for you... why don't you send that anyway? As the info will be obsolete.

Regards

Juan

[Former Member]

Good morning Juan

I am going to try the OSS Note first to see if it solves the problem. If that does not work, I will click the Send to SAP button but I will try to warn SAP first that the information is invalid and to expect more up-to-date information

Regards

Moggie

[former_member185031]

You are right. I have also faced the same problem last year and applied some note.Unfourtunately right now i dont remeber the note name.You should check in OSS What is your Basis Patch level.

Regards,

Subhash

[Former Member]

My 7.00 BASIS patch level is 14.

I will be installing the OSS Note that I mentioned (1150840) tomorrow morning. I will let all know how it turns out.

Regards

David

[Former Member]

Had a change of heart and used OSS Note 441940 instead of the original note1150840.

That solved my problem in the end, The message went away.

Moggie

[Former Member]

In case someone has a similar problem:

I had the same in my SAP system. One measurement job was planned but not executed and I couldnot start a new measurement because of the error message "1 measurement job(s) is/are not yet started or still running" (message code BV133). Instead of applying the note 441940, I selected the planned jobs (RSUVM007 and RSUVM008) via sm37 and released them. When the jobs were finished, USMM could be started again.