cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Maintain Number Ranges

Former Member
0 Kudos

(System is SAP Enterprise R/3 4.70 - Kernel 620)

I am receiving the following message when I attempt to maintain the number ranges for FI documents (transaction OMR4, second option vertically):

"The transaction is locked by user [My Username] for maintenance"

(Message no. NR023)

The issue possibly arose after being disconnected from the SAP server while I was maintaining the number ranges. When I logged on again and executed this transaction, the message appeared for the first time.

In order to solve this, I attempted to check (with SM01) whether OMR4 was locked, but this was not the case (the corresponding "lock" flag is not activated).

Next, I thought this was the result of function "NUMBER_RANGE_ENQUEUE" being executed on the number range object. However, I would have to request the help of someone with more knowledge in ABAP before attempting anything with the ".._DEQUEUE" function.

If someone knows where I can find this "maintenance lock", and how I can deactivate it, I will appreciate your help.

Thank you in advance.

Regards

Accepted Solutions (1)

Accepted Solutions (1)

former_member197269
Active Contributor
0 Kudos

Hi Peter,

Try T.code SM12 , and select ur username , delect all the entries in generated list.

this will unlock all tables which u have been using. (caution: take help of ur basis guys; as you might not have access to this t.code)

alternative, relogin; you will get a popup box asking to select one of the 3 radio button; select the first (login and disconnect other login) and then goto t.code OMR4 to maintain number ranges.

Hope this helps.

Please assign points as way to say thanks.

Answers (1)

Answers (1)

Former Member
0 Kudos

When you enter the SAP for the second time, did the system asked "multi access of user ID is not part of SAP agreement"...or something like that?

If yes, see if there are 3 checkbox, select "log in, and finished any session in the system".

It seems that the system "think" you're still accessing the screen while you were disconnected actually.

regards,