SAP Note 24948 - Separate period closing for each company code

Symptom:

When you start the period closing program, this locks all materials at plant level or valuation area level. As a result, it is not possible to run the period closing program for several company codes in parallel or, during period closing for certain company codes, to maintain materials for other company codes.
In addition, if there are many company codes at your company, you can improve the runtime required for period closing by implementing this note. You should then start several background jobs at the same time and distribute the company codes among these jobs. The jobs will run in parallel and reduce the total runtime required for period closing.

However, if your main concern is performance problems, you should first read Note 25024.
For all database systems except ORACLE, you must not implement the two Notes 24948 and 25024 at the same time.

If, for organizational reasons, you need to implement Note 24948 at your company and if, for technical reasons, it is not possible to implement Note 25024 as well, you can improve the runtime by defining the following additional indexes:

• Index for table MBEW with fields MANDT and BWKEY

• Index for table MARD with fields MANDT and WERKS

• Index for table MCHB with fields MANDT and WERKS

• Index for table MSSA with fields MANDT and WERKS

• Index for table MSKA with fields MANDT and WERKS
  

For R/3 Releases before Release 4.0 (3.0, 3.1), you must add MATNR to the three indexes:

• Index for table MBEW with fields MANDT, BWKEY, MATNR

• Index for table MARD with fields MANDT, WERKS, MATNR

• Index for table MCHB with fields MANDT, WERKS, MATNR

SAP also recommends that you archive materials and, in particular, batches that you no longer need.

Cause and prerequisites

See above.

Solution
You can solve the problem by modifying the source code as follows

Additional key words

Transaction: MMPV; program: RMMMPERI