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.