SAP Note 28582 - MD02,MD03,.. cannot be called via CALL TRANSACTION

Symptom:

The MRP transactions (MD02, MD03, ..) cannot be called via CALL TRANSACTION USING ... or batch input. The planning is not saved in the database.

Cause and prerequisites

Transactions that repeatedly call 'COMMIT WORK' internally, for example, to cancel a block or to write results in the database cannot be called via CALL TRANSACTION or batch input.
A change is possible to replace the 'COMMIT WORK' by the function module DB_COMMIT.
Therefore, you can also call multi-level single-item MRP using the CALL TRANSACTION, however, within this transaction, a DB_COMMIT per function module has to be set after each planned material.
This is necessary for an up-to-date database status when planning the dependent materials.
During single-level single-item MRP, COMMIT WORKs are set to minimize the blocking periods for the number ranges.
This is no longer required if the corresponding number ranges are buffered.

Solution
In Release 2.2G and 3.0, the single-level single-item MRP can be called via CALL TRANSACTION or batch input. In Releases 2.2G and 3.1G, the multi-level planning (MD02,MD50,MD51) can be called via CALL TRANSACTION.
An advance correction is possible.
Note: In Release 3.0G, the function modules MRP_KD_AUFTRAG_RFC (like Transaction MD50) und MRP_MATERIAL_RFC (like Transactions MD03 or MD02) are also available.

Additional key words

MRP, single-item, single-level; MRP, single-item, multi-level