VV501 error in Posting Goods Issue (VL02N)

[Former Member]

Hi,

in VL02N when we try to "Post Goods Issue" sap gives the error "vv501 - Blocking error"

The error is like below:

Diagnosis

A system error occured during the attempt to block the material you are processing.

System Response

It can be assumed that problems exist in the system at the moment, which prevent proper processing. The whole transaction is therefore stopped.

Procedure

Please inform your system administrator as soon as possible.

Any suggestions ??

Edited by: Oguzhan Subasi on Oct 5, 2011 10:38 AM

[Lakshmipathi · Accepted solution]

Check whether this helps you

[Re: posting good issue problem|;

G. Lakshmipathi

[Former Member]

Hi,

we solved the problem. It is about overflow of the lock table. But the interesting thing is there are different profiles that you should determine the lock table size. We have had enlarged the size of one of the profiles, but since the other one stays low the problem survived.

Then we enlarged the other profile (standalone instance profile) too, and the problem was solved.

Thanks everyone.

[Former Member]

Any ideas ??

[Former Member]

Hi,

I checked the threads, but the solutions arent what am i looking for.

In my deliveries there will be planty of items that have same material and batch number. But i can post good issue if the delivery has less item than ~200 even when it has items with same material number and batch. The problem occurs when the delivery has more items than ~200.

we can solve the problem by splitting the delivery with VLSP, but that is not acceptable for our costumer.

i found that not:

Note 1104630 - Failed Inbound Queues due to Locking Problems

But it didn't helped or maybe i couldnt apply it properly.

Any more suggesitons ??

[jpfriends079]

Hello

Try refering following SAP notes:

- 1317108 - No Automatic Queue Restart After Error Message VV 501

- 78252 - Posting inventory difference: Blocking error

- 1126733 - co06: item can be changed while being updated in parallel

- 1257803 - Incorrect locking behavior in backorder processing

I hope these can assist you.

Regards

JP

[Former Member]

When i checked for SAP Note 78252 - Posting inventory difference: Blocking error, here is what writen in the note:

&----

---

*& Title: MM07MFB9 *

&----

---

...

FORM BUCHEN_INITIALISIEREN.

...

READ TABLE PREFETCH04 INDEX 1.

IF SY-SUBRC IS INITIAL. " delete

IF SY-SUBRC IS INITIAL AND INVENTUR IS INITIAL. " insert

CALL FUNCTION 'MB_PREREAD_MATERIAL_VALUES'

EXPORTING MBEQU = TCURM-MBEQU

TABLES PRE04 = PREFETCH04.

ENDIF.

...

ENDFORM.

...

when i look to the code, i cant see the codes that should be deleted according to that note. I see that another SAP note (316622) had been apllied. It is ilke below:

IF MBVAL IS INITIAL.

DATA: XLOCK. "note 316622

IF NOT XMBWL IS INITIAL AND XLOCK_ALLP IS INITIAL. "note 316622

"No lock on EM07W because lock already exists "note 316622

XLOCK = X. "note 316622

ELSE. "note 316622

"Lock EM07MW in exclusive mode "note 316622

CLEAR XLOCK. "note 316622

ENDIF. "note 316622

CALL FUNCTION 'MB_PREREAD_MATERIAL_VALUES'

EXPORTING

MBEQU = TCURM-MBEQU

XONLY = XLOCK "note 316622

TABLES

PRE04 = PREFETCH04

PRE21 = PREFETCH21

* pre22 = prefetch22. "kaz

PRE22 = PREFETCH22 "kaz

PRE29 = PREFETCH29 "kaz

IT_ENQUEUE_EXCEPTION = LT_ENQUEUE_EXCEPTIONS. "396879

Should i insert the line ?

[Shiva_Ram]

Not sure why you are particular about inserting? This note 78252 applies to SAP versions 3.0D and 3.1G, which are older versions. I assume the SAP version you are working with is latest one. I recommend elevating the issue to SAP through support portal.

Regards,

[Former Member]

Hi,

You may be facing problem with lock table size, which has occured before in shipping context.

For this, you may want to consider applying the following notes:

13907 System error in the block handler, overflow lock ta

70865 Material block during goods movements

Also, speak to your basis regarding the Note 316622 that was applied.

Hope the above helps.

Thanks.

[kalyan_mokirala]

Hi Subasi,

Check the below link. It is not having enough information but go through the thread. It may help you at least to analyse the issue further.

Please let us know if the problem is resolved also don't forget to mention the way you resolved the issue.