21.09.2013 Page 1 of 2 SAP Note 322989 - Late block: Number of blocking attempts Note Language: English Version: 3 Validity: Valid Since 19.10.2000 Summary Symptom During the parallel update of goods movements for the same materials, lock situations occur even if the late block (Transaction OMJI) is activated. The system generates error message M7023 (plant data blocked by other user) is issued. Additional key words OMJI, lock, late block, M3023. Cause and prerequisites "Late block" does not mean "No block". It is required for sending exclusive blocks. This is carried out online for a short time and then only when entering the hot phase of the update preparation so that several movements can be entered at the same time. This creates situations where a process requests this block, however the exclusive block is held by another process which is currently in update. In this case, the waiting process tries several times to request the block by itself. When a certain number of attempts have been made, it then abandons this and generates the error message. Solution You have the option of varying the number of attempts. As of Release 4.6, it is possible to do this directly in Transaction OMJI. In earlier releases, you have to modify the source code. Note 72440 can be used for identifying the source code points. The modification requires that you change the number '10' in the lines in each case DO 10 TIMES. This number specifies the number of blocking attempts which are carried out at intervals of one second. A small number of attempts causes the error message to be displayed earlier. A large number increases the number of blocking attempts, however, it causes the end user to have to watch the hourglass for a long time before the system nevertheless finally generates the error message again, as it has not succeeded in accessing the block, despite the long waiting period. Header Data Release Status: Released for Customer Released on: 18.10.2000 22:00:00 Master Language: German Priority: Recommendations/additional info Category: Consulting Primary Component: MM-IM-GF-LOCK Material Block

Sapnote 0000322989 block nmaterial

Download PDF Report

Upload
hergamia
View
57
Download
1

Embed Size (px)

Citation preview

Page 1: Sapnote 0000322989 block nmaterial

21.09.2013 Page 1 of 2

SAP Note 322989 - Late block: Number of blocking attempts

Note Language: English Version: 3 Validity: Valid Since 19.10.2000

Summary

SymptomDuring the parallel update of goods movements for the same materials, locksituations occur even if the late block (Transaction OMJI) is activated.The system generates error message M7023 (plant data blocked by other user)is issued.

Additional key wordsOMJI, lock, late block, M3023.

Cause and prerequisites"Late block" does not mean "No block". It is required for sending exclusiveblocks. This is carried out online for a short time and then only whenentering the hot phase of the update preparation so that several movementscan be entered at the same time.This creates situations where a process requests this block, however theexclusive block is held by another process which is currently in update.In this case, the waiting process tries several times to request the blockby itself. When a certain number of attempts have been made, it thenabandons this and generates the error message.

SolutionYou have the option of varying the number of attempts. As of Release 4.6,it is possible to do this directly in Transaction OMJI.In earlier releases, you have to modify the source code. Note 72440 can beused for identifying the source code points.The modification requires that you change the number '10' in the lines ineach case DO 10 TIMES.

This number specifies the number of blocking attempts which are carried outat intervals of one second.

A small number of attempts causes the error message to be displayedearlier. A large number increases the number of blocking attempts, however,it causes the end user to have to watch the hourglass for a long timebefore the system nevertheless finally generates the error message again,as it has not succeeded in accessing the block, despite the long waitingperiod.

Header Data

Release Status: Released for CustomerReleased on: 18.10.2000 22:00:00Master Language: GermanPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: MM-IM-GF-LOCK Material Block