on 10-06-2015 8:01 PM
All,
Got this question recently .,
We have this common scenario ,where we have certain component of assembly gets deleted after sales order creation(configurable header ,IPPE)
Parts pegged earlier to these sales order ,lose the link upon deletion in IPPE structure ,however sales order requirement for down line part remains open with exception "26"
In order to clear this sales order requirement for part deleted from IPPE ,if in case we run MRP for individual material ,it clear these exception ,while we are checking with MRP batch job ,its not clearing these exception
MRP parameter's for MD01 are NETCH, with 1,3,1,2,1
Thanks,
Srini
Hello
Which kind of requirement is that? If it is a reservation from a production or process order, it will not be changed or deleted by MRP. If it is a dependent requirement, it can only be deleted if the parent planned order is not firmed.
If it is a requirement from a planned order which is not firmed, you should check if this material was actually planned by MRP. You can check that on transaction MD05.
If the material was not planned by MRP, you should check if the planning file flags NETCH or NETPL are marked for this material on transaction MD21.
BR
Caetano
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Closing this defect ,thank you all
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Caetano, Ameya and Shailesh,
Thanks for valid inputs
Yes this seems to be issue with planning file entry for the said part
Part is dependent part of requirement type "SB", which is removed from IPPE "BOM", post planned order creation .
Their are situations with firmed planned order and unfirmed planned orders .upon deletion these infant dependent requirement ,triggered exception "26"
These exception were not getting cleared by itself post MRP run .
Possible reason : As referred by you all
We currently run MRP NEUPL, with mode 2(re explode bom and routing),we are told by SAP earlier not to use mode "3" due to performance issue's and current custom environment
Observation : Part upon deletion from IPPE ,shows 2 entry in planning file with LLC "000" and "003" ,which is consistent ,since it need to have only one LLC "000"
Findings: Due to recent batch job changes ,we skipped MRP daily consistency check and added it as monthly activity ,due to which their seems to be issues with planning file entry's
We ran consistency check ,MRP reset incorrect LLC "003" ,updated right entry's for planning file
Appreciate all your expert advice
Regards,
Srini
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Check if the material has the NETCH flag active in the planning file before MRP using MD21.
Try running MRP with planning mode 3, which is delete and re create planning data.
As a long run solution, you can setup MRP in your plant weekly or bi weekly with processing key NEUPL and planning mode 3. This will take care of avoiding such problems.
Best Regards,
Ameya B.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Srini,
This case generally arises when Mrp is run in by MD02. There is big difference between MRP running with MD01 and MD02. T code MD01 first looks for Planning file entry and plans only those materials which have undergone a NETCH or NETPL change in MD21 whereas MD02 doesnt behave like this.
In order to remove this inconsistency, you need to run background job for planning file entry. Create the variant and schedule the job. The job can be scheduled once in a month not necessarily to be run regularly.
Best regards
Shailesh Mishra
User | Count |
---|---|
104 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.