on 08-10-2010 6:34 AM
Dear all,
I have a question about the MRP run and creation of proposals
When I run MD01, and even if there are requirements, no proposals (PRs,Planned Orders) are created.
However, when I run MD02 (FG specific), proposals (PRs, Planned Orders) are now created.
This is an issue in our implementation, because MRP run is done via background and users will no have time to run MD02 for each FG.
The parameters i use for both tcodes are:
NETCH
1
3
1
2
2
Dear Bear,
Check this,Use T Code MDAB and MDRE and schedule a job for both these T Codes for setting up the planning file entries and
checking the planning file consistency and when MRP is run at plant levelfor the first time ,its advisable to run with NEUPL and
then with NETPL.
Also refer this thread,
Check once with this and revert
Regards
S Mangalraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the answer!
I read the link and they were very helpful.
A few questions:
1.Should I schedule MDAB and MDRE once, or shoudl I schedule it periodically?
2. For my background job for the MRP (everday run), should key be NEUPL or NETCH?
>
> Dear Bear,
>
> Check this,Use T Code MDAB and MDRE and schedule a job for both these T Codes for setting up the planning file entries and
>
> checking the planning file consistency and when MRP is run at plant levelfor the first time ,its advisable to run with NEUPL and
>
> then with NETPL.
>
> Also refer this thread,
>
>
> Check once with this and revert
>
> Regards
> S Mangalraj
Dear ,
Find below the answer of your question :
1.Should I schedule MDAB and MDRE once, or shoudl I schedule it periodically? : As you are running on Daily basis , it will be better if you Schedule the job periodically .Goto MDRE-Hit Schjedule Job -Hit Periodically -Select Day
2.For my background job for the MRP (everday run), should key be NEUPL or NETCH? : It should be NETCH .NETCH-If you choose this only mateirals which have undergone changes from last MRP will be considered for MRP.
NEUPL: all the materials will be considered for MRP. Wull be generally used when running mrp for first time
Hope this is clear now
Regards
JH
So are my assumptions correct:
1. for MDAB - schedule ONCE?
for MDRE - schedule PERIODICALLY, everyday?
2. NEUPL for first time run, NETCH for everyday run?
>
> Dear ,
>
> Find below the answer of your question :
>
> 1.Should I schedule MDAB and MDRE once, or shoudl I schedule it periodically? : As you are running on Daily basis , it will be better if you Schedule the job periodically .Goto MDRE-Hit Schjedule Job -Hit Periodically -Select Day
>
> 2.For my background job for the MRP (everday run), should key be NEUPL or NETCH? : It should be NETCH .NETCH-If you choose this only mateirals which have undergone changes from last MRP will be considered for MRP.
>
> NEUPL: all the materials will be considered for MRP. Wull be generally used when running mrp for first time
>
> Hope this is clear now
>
> Regards
> JH
Bear,
There are no "right" answers. You do this as often as you need.
MDAB and MDRE should be run 'periodically'. I run them every night, they go very quickly.
MRP should be run as often as necessary. When you run MRP, you should run one of the NetChange selections at a minimum. I run Regenerative every night because I have enough machine to support it. NetChange to me is just a compromise to accommodate systems that don't have enough capacity to support regular Regenerative planning.
Rgds,
DB49
Try use MDRE (consistent check of planning file entries) and let us know whether it solve your problem.
I once have the same issue but mine is related to recursive BOM. The system couldn't find the right number of low level code when run in MD01.
Rgds,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
103 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
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.