System is ignoring a existing PR in MRP

[Former Member]

Hi all,

I'm facing a problem here when executing MRP.

System is ignoring a existing PR for a material and generating a new planned order... When checking the status in MD04 I can see the old PR with exception 07...

My problem is that this PR is old but it is being processed, therefore i want the system to consider it and not to create new planned order...

I've tried to change configuration of Plan.Horizon and Rescheduling it, but without success...

Can anyone please help me?

[dipak_kumar3 · Accepted solution]

Hi,

Can you try executing MRP with planning mode as 3 in MD03 and see the result?

Check and revert back if it solves your problem.

Thank you,

Dipak

[Former Member · Accepted solution]

Hi Dipak, thanks for reply...

I've tried to do your suggestion but the result was the same...

System created new planned order and didn't deleted the old PR (wich can't happen to solve my problem).

[Former Member · Accepted solution]

Diogo,

You didn't mention any details. However, if the existing PR is fixed, then this issue can arise if your rescheduling horizon is too small. Rescheduling horizon will cause the MRP run to assume reschedule of the existing fixed elements, instead of creating a new planned order. You can review your resched horizon in either OPPQ or OPPR. If this is the culprit, you can alleviate the problem by making the Rescheduling horizon larger.

http://help.sap.com/erp2005_ehp_04/helpdata/EN/f4/7d2c9744af11d182b40000e829fbfe/frameset.htm

Best Regards,

DB49

[Former Member · Accepted solution]

DB49, thanks for you reply.

I've already changed my rescheduling for a long period and it is still not working...

I guess that my PR is not fixed... Can you please explain me what will determine if a PR is fixed or not and how to fix?

Thanks

[former_member581212 · Accepted solution]

hi,

sorry i misunderstood..

while running MRP...check horizon set...check which key are you settings up ie. NETCH/NETPL/NEUPL...

If this is first time you are running MRP, then use NEUPL...else can go for NETCH...

Regards

Priyanka.P

Edited by: Priyanka Paltanwale on Sep 15, 2010 5:02 PM

[Former Member · Accepted solution]

DB49, thanks for you reply.

I've checked the flag to fix te item in the PR and customized my rescheduling period for a long time and it is still not working...

MRP type is VB and lot size is replenish to maximum stock level...

My rescheduling horizon is set for 365 with tolerance values 2...

My PR is from jul/06/2010.

Any suggestion?

Thanks

[Former Member · Accepted solution]

Hi Priyanka,

I've tried and neither NEUPL nor NETCH worked for me...

Any other suggestion?

Thanks,

[Former Member · Accepted solution]

Diogo,

Easiest way to see if a PR is fixed is to review in MD04 or MD05. Fixed PRs or Planned orders will have an asterisk next to them.

What is the date/qty of the existing PR?

You ran MRP with parameter "delete and recreate", and it did not delete the PR? That is strange.... What is the doc type of the PR? Item category? Account assignment category? Is it assigned to a source?

What is the date/qty of the new planned order?

What is the Planned delivery time? What is the GR processing time? What is the Purchase Processing time (OMEW)?

Best Regards,

DB49

[Former Member · Accepted solution]

Hi DB49,

For this material, my reoder point is set to 10 and maximum stock level to 20.

I checked at MD04 and the PR is fixed.

Existing PR date is jul.06/2010 and qty is 300.

I've ran the MRP with Planning Mode 1 because I don't want to delete this PR, I just don't want to create one new Planned order. But just to test it, I've ran with planning mode 3 and the result was the same... Doc type is NB and item category is standard (blank). Account assignment is K (cost center) and it is not assigned to a source.

Date and qty of new planned order is sep.15/2010 and 20...

Both planning delivery time , GR processing time and proc time are set to 1 day.

Thanks.

[JL23 · Accepted solution]

Account assignment is K

MRP is creating requisition to fill up the stock in your warehouse up to maximum stock level.

Your account assigned purchase requisition does not fill up your warehouse, it is immediatly consumed to a cost center when it arrives, hence MRP has to create a new requisition.

[Former Member · Accepted solution]

Hi Jürgen L.,

thanks for your reply.

This PR was created manually so I didn't realized this detail.

I've changed the account assignment to blank and it worked.

Thanks for everyone who helped me...