Logic of Planning File Entries (PP-MRP)
The purpose of this page is to clarify and explain the logic of Planning File Entries.
Screenshots, FAQ-s and useful short descriptions about Planning File Entries.
Planning File Entries
The planning file entry is a kind of ‘flag’ for the material requirements planning, indicating what the 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?
From SAP Menu:
SAP Menu >> Logistics >> Production >> MRP >> Planning >> Planning File Entry
Important Planning File Entry transactions code:
- MD20: Create Planning File
- MD21: Display Planning File
MD20 – Create Planning File:
- Net change planning (NETCH): Determines that the material is taken into account in the net change planning run.
- Plng file entry NETPL: Means that the material is taken into account in the short-term planning horizon during the next net change planning run.
- Reset ord. proposals: Controls that existing procurement proposals (planned orders, purchase order requisitions and schedule lines) from the last planning run are deleted and recreated.
- Re-explode BOM: Controls the re-explosion of BOMs for existing procurement proposals (planned orders, purchase requisitions, delivery schedules) that came from the last planning run.
- Planning date: Date for planning.
MD21 – Display Planning File
After Execute you can see the planning file entries to the Material what you are selected.
Important tables in Planning File Entry:
- MDVM – Entry in MRP file: This table is used, if the MRP areas has not been activated.
- DBVM – Planning File Entry, MRP Area: If the MRP areas have been activated and the planning file entry has been converted, table DBVM will be used.