cancel
Showing results for 
Search instead for 
Did you mean: 

New Request is NOT created. User locked the load of master data.

Former Member
0 Kudos

Dear friends,

While loading masterdata to a characteristic (direct master data update), it failed once due to some problem with user authorisation (of lets say user1). The failed request is lets say Req1.

While trying to load again with another user with proper authorisations (lets say user2), the data load fails with the following errors:

1. User1 locked the load of master datas for characteristic. (Message no. RSDMD174)

2. Lock NOT set for: Loading master data attributes (Message no. RSENQ002)

Strangely, No new request gets created during these subsequent attempts, but Req1 (in error state) is appended with new records every time.

A check on SM12 reveals that there are no locks for either user1 or user2.

Any help would be highly appreciated.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Roberto

Thanks for your quick reply.

But, unfortunately there is no open process to kill in SM50

regards.

atlaj

Former Member
0 Kudos

Look in RS12 to delete your lock.

And, FYI, look at OSS Note 316329 for more details...

Hope it helps!

Bye,

Roberto

Former Member
0 Kudos

Hi Atlaj,

Did you try SM37 with your users. Is there a job active?

Former Member
0 Kudos

Hi atlaj,

Just check your attribute change run is running or not. The attribute change run and masterdata load cannot run in parellel.

Regards

Sriram

Former Member
0 Kudos

Hi dear,

I think you have to kill the process (the first one) in SM50...

Hope it helps!

Bye,

Roberto

...please don't forget to close your old post and to assign some points to the useful answers...it's THE way to say thank here...