Answer
The most common reason a planning file entry is not created is that the material was created before MRP was turned on for that plant.
Another reason is that Materials created by certain batch SAP programs do not trigger the creation of a planning file entry automatically, the way a MM01 normally does when you create a material interactively.
Regardless of the cause, SAP supplies a transaction that will automatically create all required planning file entries.
Transaction is MDAB. This will create rows in the planning file, where none existed previously. MDAB searches for Materials that are MRP relevant (all MRP configuration settings are in place, and the material has an MRP type that indicates that MRP is to be utilized). If it finds such a material, and the planning file entry does not already exist, it will create an entry. In many companies, this transaction is run regularly, in batch.
Now, once the planning file entry exists, it must still be tagged for an MRP run or Netch MRP runs will ignore them. The normal way that a material's planning file is tagged for the next MRP run is that the system detects an MRP relevant change. The system then automatically tag the planning file for the next MRP run. There are many events that can trigger the system to do this: Most material movements, and also any changes in supply or demand elements. If no changes have been made, the planning file will not be updated. If you are running one of the Net Change MRPs, it will completely bypass these materials. You can force an MRP run in background against a material (providing there is a planning file entry) by running NETUPL.
When someone tells me background MRP doesn't work, but
interactive MRP DOES work, then I normally assume that the planning file
entry does not exist, and I run MDAB. It really doesn't matter why
it came to be missing. It is also a good idea to run MDRE periodically.
These steps are cheap insurance.
After MRP Run Planning File
After the MRP run, planning file entry should be deleted. if not deleted what will be the reasons for that?
Answer
The planning file controls which materials are to be planned for the different types of planning run. The planning file contains all materials that should be included in the planning run.
The system enters materials automatically into the planning file and marks them with a total change indicator if a change is carried out which is relevant to the material, for example, changes to active purchase orders. If a change concerning the planning horizon occurs (for example, creating a purchase order within the planning horizon), the material is automatically given another indicator, that is, the net change planning indicator.
During the planning run, the system now checks every entry for a material in the planning file: Once the planning run has been carried out, the appropriate indicator is automatically deleted in the planning file. If a termination occurs when planning a material, the indicators for this material are left in the planning file so that the material is taken into account again in the next net change planning run.
Notes:
Planning File Entry for Termination
The purpose of this activity is to set up error handling in the planning run.
Procedure
1. Access the activity choosing one of the following
navigation options:
IMG Menu - Production -> Material Requirement Planning -> Planning -> MRP Calculation -> Define Error Processing in the Planning Run (Transaction Code: OMDY)
2. On the Change View “Error Handling in the Planning Run”: Overview screen, make the following entries:
Plant Plant Name Max.Pur.Ord.Prc MPRG
BP01 Best Practice Mfg Plant 50 001
BP0X Best Practice Inter-company Plant 00
3. Save your entries.
Result
Error handling in the planning run is set up.
