Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Random user delivery block

Former Member
0 Likes
1,627

Hi,

I am facing this problem when one of my client uses the VL02N transaction and when he successfully logged out, but if another user login and uses VL02N it shows document "XXXX" object is blocked by user "YYYY"

Help me out what needs to be done in that aspect.

Thanks in advance,

Arun

SD Consultant

Message was edited by: Thea Hillenbrand: I deselected the category ABAP Trials and Developer Editions. This category should be used for ABAP Systems in the Cloud Appliance Library related contributions. Kind regards, Thea

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,580

Hi Arun

It is most likely that user YYYY ended their SAP GUI Session without exiting the transaction.

This results in the lock being retained. The length of time the lock is retained is managed by your SAP Basis Team, so if it is required for this to be shortened, have a chat with them.

Alternatively ensure the relevant users understand how to log out of the SAP GUI Screens correctly.

Regards

Arden

7 REPLIES 7
Read only

Former Member
0 Likes
1,581

Hi Arun

It is most likely that user YYYY ended their SAP GUI Session without exiting the transaction.

This results in the lock being retained. The length of time the lock is retained is managed by your SAP Basis Team, so if it is required for this to be shortened, have a chat with them.

Alternatively ensure the relevant users understand how to log out of the SAP GUI Screens correctly.

Regards

Arden

Read only

0 Likes
1,580

Hi Arden,

Thanks for your reply

I understand your point that you have made, but how it is happen when new user try to access it everytime?

Read only

0 Likes
1,580

Hi Arun

If you're saying the lock is for the same object, and the lock should have been released by now.

Then there may have been an issue with the system releasing the lock.

You can use transaction SM12 to manually remove the lock.

"ONLY IF YOUR 100% SURE IT SHOULD NO LONGER BE LOCKED"

Regards

Arden

Read only

0 Likes
1,580

Hi Arden,

Thanks for your help...by using your advice this issue is solved now..:-)

Regards,

Arun

Read only

0 Likes
1,580

Hi Arden,

Today I have several problems with lock delivery.


I found out this happens when I want to delete a delivery in VL02N and another user (YYYY in this case) is doing batch determination in transaction VL02N.

This is NOT for the same customer and also NOT for the same article.

Could you please help me why this happen after removing a lock?

Regards,

Arun

Read only

0 Likes
1,580

Hi Arun

Not quite sure I'm understanding the issue fully, is it possible a user has gone into your transaction after you released the lock?

Regards

Arden

Read only

0 Likes
1,580

Hi Arden,

Thanks for your response :-), not an issue I am currently investigating on this issue, i'll let you know as soon as i get some conclusion.

Thanks & Regards,

Arun