Incident: 1000000xxx - Identity Authorisation Run aborted due to locked documents

[wjmatamoros1]

Hello Friends, 
Someone knows what this error refers to:
Diagnostic Information
Health Check Component: ABAP Engine 
Health Check Name: Cancelled Job Check 
Description
The job described in the Error Information section and Context Information section was canceled. As consequence, the results of the job are not available.Reason for the cancelation is a locked document. The user locking the document is mentioned in the Error Information section. As soon as the user closes the related document, the job can be restarted.Error Information
Run Type: Identity Authorisation Run 
Run ID: 00000000000000000000000000000000014 
Run Description: Asesor Maquinaria 
Alias: WILLIAM.MATAMOROS 
Document is locked by: alias 
Date and Time for executed Job: 21.03.2018,21:49:34 UTC  

I have been working with some access restrictions to a commercial role and Ihave received these incident notifications.

Could you please guide me?
Thanks in advance,

[PrasanthArya · Accepted solution]

This Health Check incident gets created when a key user does changes on one of the existing Business Roles but the screen was not closed after this step. Due to this the run to update the changes got aborted.

Once the user has closed the screen the run will be triggered again and will update the changes done on the Business Role.

[wjmatamoros1 · Accepted solution]

Thanks for your response Prasanth.

I've been trying to generate access restrictions, but these do not work! Every time I update the commercial role I keep the changes, update the users, and even close the session with the user but after a moment I am presented with this error.

I have closed all sessions with the Alias that mentions the error, even block the user but still present inconsistencies.

I went back to update another commercial role with another user and keeps presenting the same error with the new Alias.

What should I review in the access restriction, to identify why the restrictions do not apply.

I have already raised an incident but I have no response from SAP Support.

Thanks for the reply.