SAP Note 27153 - Planning file entries from Inventory Management

Symptom:

In the net change mode, the only materials that are included in the planning run at plant level (MD01), are those which have been given the appropriate entry in the planning file MDVM. This technique aims to reduce the runtime of the planning run. The system only flags those materials that have undergone a change relevant to the planning run and that are active for the planning run.

These flags can also be created in inventory management. However, in the standard system, not every stock change triggers a flag.
This logic differentiates materials that are planned using reorder point procedures from the rest.

For materials that are not planned using reorder point procedures, a flag is always created if no reference to a reservation (purchase order, and so on) exists. If a reference does exist, then a flag is only created for this material if

a) more than the remaining open 'rest' quantity is received or issued

b) less than the remaining open 'rest' quantity is received or issued and the final delivery indicator is set.

c) the requirements date of the reservation lies in the future (not valid for purchase orders)

From Release 3.0C, you can pre-define tolerance values (as a percentage) for points a) and b). Then the system will only flag the material if a quantity deviation exceeds this tolerance value. You make the necessary Customizing settings in Table 440C and you can make the settings plant-specific.

A reorder point material is only flagged if, for a goods receipt, the reorder point was fallen short of before the receipt and if the goods receipt occurs without reference (e.g. to the purchase order).
On the other hand, the system only creates a flag during goods issue, if the reorder point was fallen short of after the issue.

However, some customers want the system to create an entry in the planning file after every stock change. That is, they want the system to create more flags.
You can also make this setting in Customizing in Table T440C in the standard system from Release 3.0C (Transaction OMIY).

Here, note that the following errors still exist when creating planning file entries from inventory management:

1. Goods movements for make-to-stock and project stocks do not lead to planning file entries.

2. For goods movements with reference to reservations, a planning file entry is always created. The system reacts as if NO reference to the reservation exists.

Other terms

Planning file entry, planning file, MRP record, inventory management, documentation, special stock, make-to-order

Reason and Prerequisites

1. This is not programmed.

2. This is caused by an incorrect naming.

Solution

For Release 2.2, by implementing a modification, you can instruct the system to create a planning file entry for every goods movement.
In Release 3.0, (from Release 3.0C) you will be able to activate the version mentioned above via Customizing (Transaction OMIY).

1. Correction, see below. Standard from 2.2G and in another form from 3.0C.

2. Correction, see below. Standard from 2.2G and in another form from 3.0B.

For this correction, note that errors in the central function pool for the creation of planning file entries (SAPLDISP) can cripple the entire SAP logistics system! Therefore, the correction should ideally be implemented outside of the main hours of business.