8/11/2019 Nota 0000205681

1/3

SAP Note

Header Data

Symptom

In the environment of material requirements planning, problems frequently occur which are related tothe planning file entry.These problems can be comprehension problems or technical problems.In this note, the attempt is made to address the most frequent questions that relate to this topic.

Other Terms

Planning file entry, file entry, planning file, MDVM, MDVL, MRP, MD01, MDBT, dispsatz_erstellen,LDISPU01, MRP record, DBVM, KDVM, KBVM ...

Reason and Prerequisites

Preliminary remarks:

l As of Release 4.5, there are the MRP areas within material requirements planning.If the MRP areas have been activated and the planning file entry has been converted, table DBVMwill be used instead of table MDVM in the following explanations.Here, you must also refer to the corresponding documentation.

l As of Release 4.5, there is also the customer individual planning file entry.For a change in the sales order, a planning file entry is set here for this special individualcustomer segment and not for the entire material anymore;Here, you must also refer to the documentation and to the release notes.

Troubleshooting

Some typical questions or problems which occur in the environment of material requirements planningand which are related to the planning file entry:

1. What information does the planning file entry or the corresponding entry in respective table

MDVM make available?

2. Material XYZ has a material shortage.Why did the last MRP run, nevertheless, create no receipt elements?(General background:

3. The MRP did not plan the material at all because no planning file entry was set) Why is noplanning file entry set for a certain action?

4. (Example, conversion of purchase requisition into purchase order, goods issue to sales orderand so on)

Why does a planning file entry still exist for a material after an MRP run although a planningfile entry was already set before the MRP run and the material has already been plannedaccording to the spool list?

SolutionFirst some notes on the planning file entry and its technical background:

The planning file entry is a kind of 'flag' for the material requirements planning, indicating whatthe planning file entry should do with a material during the next total planning run:Do you want to plan the material?Which low-level code has the material?Do you want to explode the bill of material?

205681 - MRP: Planning file entry for material requirements planning

Version 6 Validity:11.09.2002 - active Language English

Released On 11.09.2002 13:14:13

Release Status Released for Customer

Component PP-MRP Material Requirements Planning

PP-MP-LTP Long-Term Planning (Simulation)PP-MP-MPS Master Production Scheduling

PP-MRP-BD Basic Data

PP-MRP-PE Planning Evaluation

PP-MRP-PP Procurement Proposal

PP-MRP-PR Planning Execution

Priority Recommendations / Additional Info

Category Consulting

Other Components

8/11/2019 Nota 0000205681

2/3

For a planning file entry existing or being updated at all, it is essential that the materialrequirements planning is active in the corresponding plant (Transaction OMDU).If you want to set upthe planning file later, you can execute this via Transaction OMDO.You can execute a consistency check of the planning file entry using Transaction MDRE.From a technical point of view, the planning file entry is an entry in table MDVM. Here, the totalkey (MDKEY) consists of the low-level code (three characters long), the material number (18characters long) and the plant (four characters long).New: As of Release 4.5A, there are two time stamps in MDVM:The date at which the material has been planned the last time (DSTMP) and the date at which aplanning file entry has been set the last time (USTMP).

Answers to the above questions:

1. From the planning file entry, I can see: (Transaction MD21)

l whether a MDVM entry exists for the material at all

l which low-level code the material has

l whether the material in the next planning run should be planned with the corresponding parameter(NETCH/NETPL)

l whether the bill of material should be exploded again

l whether the existing procurement proposals should be reset

2. If a material shortage or a surplus situation exists for a material which should actually becleared by the material requirements planning (for example, recognizable through the fact thatTransaction MD03 would be able to correct the situation) and this situation still exists afteranother total planning run, then the material was presumably not planned within the MRP run atall. (Also refer to related Note 371016.)

If the parameter 'Display list' is set in the variant for the MRP run, you can check this by thespool list of the corresponding job not containing the material.

In this case, the planning file entry is very probably not set or has not been set for thismaterial (this can be seen in Transaction MD21).This can either be due to a missing MDVM entry (Is material requirements planning activated forthe plant?If so, the material was created in this case before the activation of materialrequirements planning in this plant or it was imported from an external system or a customer-specific report deleted the MDVM record again) or due to the fact that the last transactionwhich lead to the changed situation for the material requirements planning has no planning fileentry set.For this, there are some notes you should be able to find with key words 'Planningfile entry' or 'MDVM' and the corresponding transaction.

3. A planning file entry should be basically set if an MRP-relevant change was made to amaterial.An exception, for which no planning file entry is set for 'Explode BOM' although a changerelevant for scheduling has been made, is the change to a routing (see Note 88669).Here, it

might be explicitly necessary to start a planning run with planning mode '2' (instead of '1' asin normal cases).

If the situation did not change from the material requirements planning point of view, thematerial must also not be planned during the next MRP run and no planning file entry is set.A typical example for this is the conversion of a purchase requisition into a purchase orderwithout any additional data change.(For the related subject of the conversion of planned orders into production orders, see Note77573.)

4. If the planning run terminates for a material with planning file entry on account of an errormessage, the planning file entry is not deleted if this is not explicitly set in Customizing.In Transaction OMDY, you can set for which errors (message number) you want the planning fileentry being deleted.

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (3)

1049311 Time-phased planning: No entry in planning file

371016 MRP: Material is not planned for MD01 / MDBT

371016 MRP: Material is not planned for MD01 / MDBT

1049311 Time-phased planning: No entry in planning file

550568 FAQ: MRP run (MD01, MD02, MD03, MDBT,...)

8/11/2019 Nota 0000205681

3/3