Job used to change material Batch data - affecting entire system

[Former Member]

Hi ,

We have a Job which updates Material- batch characteristics (plant specific).

But it is causing many strange issues.

1. Tcodes like va02, msc2n gets locked by the same user id trying to access the order/batch, even though plant used in orders are different

2.System performance gets slowed down while loading some tcode qe51n (loading infinitely)

Thanks in advance

[henk_verdaasdonk4]

Hi Pradeep,

There is no easy straight forward answer. You should consider the following:

• Which locks are set is depending on the functionality you use in your job to perform the update. If you transaction code for example, then probably everything possible is locked although your update is only on Material/Bach/Plant level. You should use SM12 to check which locks are set for each material and/or batch.
• It looks like locks are set till the end of the batch job. Is your requirement all materials/batces should be updated or none? If not required to commit all at once, you could consider to redesign the job program that is commits and releases locks after each material/batch update.

Cheers,

Henk.