Hi Chokkalingam,
Please check transaction SM66 to see how many programs are running
related to MM tables (MARC, MBEW, etc).
Please check transaction SM21 to see if there are errors related to
lock entries.
If you are facing MM tables in SM66 and lock entries related to MM
in SM21, please check/read the questions 1, 2 and 3 from the following
SAP note: 552289 - FAQ: R/3 Lock management
Please follow the answers of each question.
I hope it helps you.
If it doesn't help you, we should check the application side.
Please have a look at the information contained under the SAP Note:
70865 - Material block during goods movements
As explained in the note, to ensure data integrity, it is necessary to
block the material against updates by other users during good movements.
This is achieved by blocking the material plant (lock object MARC) and
the material valuation area (lock object MBEW) exclusively against other
transactions which update the material master.
What you can do, as advised in the note, is to activate the late block
via transaction OMJI. As a result of this change, several users will be
able to carry out good movements to the same material and plant
simultaneously. The problem is that you will experience a disadvantage
of performance loss after this change.
After activating the late block in transaction OMJI, please, check if
you then can post without enqueue problems.
Notice that you can alter the number of tries for posting when a block
exists by choosing different waiting times in OMJI. Please, have a look
at the below notes in this regard:
322989 Late block: Number of blocking attempts
613242 Locking problems at posting via MB_CREATE_GOODS_MOV
521945 FAQ: Material block
> OMJI:
EXCLUSIVE BLOCK DURING GOODS MOVEMENTS
When material master data is read for the first time during a goods
movement, this indicator specifies that tables MARC (plant data) and
MBEW (accounting data) are locked exclusively until the goods mvt
has been fully posted. Another user cannot maintain the material
during this time. The disadvantage is the long period of time for
which the lock is set (from the time the material master data is
first read when the goods movement is entered through to completion
completion of the update posting).
LATE BLOCK FOR GOODS MOVEMENTS
Specifies that a material:
1- is not always blocked exclusively, but only if data is actually
to be saved.
2- is blocked exclusively as late as possible to keep the lock time
to a minimum
The advantage is that several users can enter goods movements at the
same time because only one shared lock is set for the material when
the movement is entered.
The disadvantage is that the material master record is read several
times and, in the case of an outward stock movement, that the lock
entries of other users on the ATP server also have to be considered.
These additional accesses have a negative effect on performance.
The late blocking works on the material level; if the material is
being updated, all in relation to that material will be blocked until
the posting is complete. The block works for any type of goods movement.
........................................................................
You could also try a different alternative.
If note 552289 and OMJI doesn't help you, please go to OMT0 and set
'shared lock' indicator.
If this indicator is set, plant data and valuation data (tables MARC and
MBEW) are no longer locked exclusively in material master maintenance,
but a shared lock is set. This has the advantage that goods movements
can be carried out at the same time as material master maintenance if no
valuation-relevant fields or inventory-management-relevant fields (such
as the base unit of measure, batch management requirement indicator,
valuation category, or price unit) are changed in material master
maintenance.
........................................................................
I hope all this information helps you.
BR,
Enrique
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.