Planning File Entry
Following is the table which clearly shows various planning file entries against a transaction/activity.
| S.no | Activity/Transaction | NChge plng | NChgePHor | ResetProps | Explode BOM | Plng date | No entry (No impact) | Remarks |
|---|
| 1 | Material master created with only basic data views | | | | | | X | |
| 2 | Material master extended with purchasing view (No MRP views) | | | | | | X | |
| 3 | Material master extended with sales view (No MRP views) | | | | | | X | |
| 4 | Material master extended with work scheduling view (No MRP views) | | | | | | X | |
| 5 | Material master extended with Plant storage location data 1/2 view (No MRP views) | | | | | | X | |
| 6 | Material master extended with MRP views | X | X | X | | | | |
| 7 | New BOM created for material | X | X | X | X | | | |
| 8 | After MRP run | | | | | | X (Entries are reset) | |
| 9 | Modify BOM (Not just accessing BOM via CS02, we need to modify some elements of BOM).Example: If I access CS02 and modify component usage from 1 EA to again 1 EA,no impact on planning file entry. This must be changed from 1 EA to 2 EA or something else. This means modification must be a real modification not just accessing CS02).Modification includes following: 1. Item quantity,2.Item change,3.BOM status,4.Fixed qty, Net scrap indicators, Following modifications are not part of planning file entry: 1.Item number (POSNR) would not have any impact on planning file entry 2.BOM header and Alt texts | X | X | | X | | | No Impact on component planning file which is changed in BOM |
| 10 | Planning file entry would be reset Even if I run MD03 as BOM anyway exploded here in MD03. | | | | | | X (Entries are reset) | |
| 11 | Now,Planned order created manually;So, firm indicator set as it is created manually | X | X | | X | | | |
| 12 | Run MD03 | | | | | | X (Entries are reset) | |
| 13 | Planning file entry is updated for component as dependent requirement generated from header item while running MD03 | X | X | | | | | |
| 14 | Modify BOM, component usage quantity from 1 EA to 2 EA | X | X | | X | | | |
| 15 | Run MD03 | | | | | | X (Entries are reset) | |
| 16 | Despite firm indicator, planned order component usage changed from 1 EA to 2 EA | | | | | | | |
| 17 | Run MD03 for component | | | | | | X (Entries are reset) | |
| 18 | Modify PR quantity of component from 1 EA to 2 EA | X | X | | | | | |
| 19 | Run MD03 for component | | | | | | X (Entries are reset) | |
| 20 | Following MRP data changed at Material master would have impact: 1. Lead time | X | X | X | | | | |
| 21 | Following MRP data changed at Material master would have impact: 1.MRP controller,2.Prod.Stor.Location,3.Strategy group,4.Indiv/Coll indicator,5.Batch management activation | X | X | | | | | |
| 22 | Following MRP data changed at Material master would have impact: 1.Selection method in MRP4 view,2.Create/Change of Production version in MRP4 view | X | X | | X | | | |
| 23 | Following MRP data would not have impact: 1. Backflush indicator,2.REM profile/Indicator,3.Serial number profile addition,4.Change of Prod.Version text alone in MRP4 view | | | | | | | |
| 24 | Run MD03 for component;This would not change lead time updated in PR as it is firmed.This change in lead time would not even be updated while converting PR to PO | | | | | | X (Entries are reset) | |
| 25 | Conversion from PR to PO | | | | | | X | |
| 26 | Change of quantity in PO | X | X | | | | | |
| 27 | Change in delivery days in PO | | | | | | X | |
| 28 | Change in delivery date in PO | X | X | | | | | |
Planning Mode 1
Planning mode 1 is set only if net change planning indicator and net change planning horizon indicator are set in the planning file for a material (see Planning Run Type).
In the planning run in planning mode 1, system reactivates the existing planning data, that is, procurement proposals that are not firmed remain on the database and are only then adapted,if the dates and quantities do not suit the new planning situation. The system only re-explodes the BOM for adjusted procurement proposals. System performance is thus improved.
Example of changes that cause planning mode 1 to be set:
Changes in date and quantity, Requirement changes, Changes in the lot-sizing procedure or MRP type
Planning Mode 2
Planning mode 2 is set if Re-explode BOM indicator is also set in the planning file along with planning mode 1 pre-requisites.
In the planning run in planning mode 2, system re-explodes the BOMs for all existing procurement proposals that are not firmed and also for which the dates and quantities do not have to be adjusted.
Example of changes that cause planning mode 2 to be set:
Changes to the material BOM, Changes to the sales order BOM, Changes to the phantom assembly BOM, Changes to references assigned within BOM, Changes to material classification, Change of production version in material master or planned order, Change or conversion of BOM explosion number.
Planning Mode 3
Planning mode 3 is set if a material has Reset order proposal indicator along with planning mode 1 pre-requisites in the planning file.
In planning mode 3, existing procurement proposals that are not firmed are completely deleted from the database and recreated. The system then re-explodes the BOMs.In this case, all unfirm MRP elements would get a new document number.
Example of changes that cause planning mode 3 to be set:
In-house production time, Planned delivery time, Scheduling margin key, MRP controller
Thanks and Regards
Sudhakar N
