Runaway records being created in PPS170 (Planned Purchase Order) from Manufactured Items

Good Evening!

We have Items whose Make/buy Code is set as a “1-Manufactured” (MMS001/E) with an Item Category of “03-Subcontracted” (MMS001/G).

All of the sudden PPS170 is getting inundated with the planning records to meet all the forecasts out to the planning time fence for these Items.

And not just the initial set of demand (which we would expect)...but over and over and over again.

More than 120,000 records and growing…

Has anyone seen that behavior before?

Thanks,

Steve

Find more posts tagged with

Accepted answers

All comments

ganganath-kaluarachchi

It is difficult to answer without fully checking the configuration you have. I believe this third party manufactured product you are selling out and thus having Customer Orders as well as Forecasts ?

And it seems you have added Forecast values far in to the future, have you considered using Forecast consumption ? So that when there are Customer Orders, your Forecasts will be consumed and will not be considered in Planning.

However, not sure if this has been working fine before and something just happened ? Some more information would be helpful. Such as what drives these POPs ? Is it just the Forecasts and COs or are there any other demands, such as demands from other warehouses.

magnus-tallqvist

Please note that the Make/Buy code in MMS001 has no bearing on the MRP. It uses the make/buy code in MMS002. A quite common reason for getting a massive amount of planned orders for an item is that someone has set the max quantity in MMS002.

ganganath-kaluarachchi

Hi Magnus, interesting. I think you mean following field in Panel F.

Even if this is setup, it can only generate Supplies against whatever the Demands right. Say, we have a demand of 1000 pcs, having a Max Order Qty of 500 will generate 2 supply orders right ?

magnus-tallqvist

That is the basic concept on a MRP yes. However in reality it becomes much more complex since there can be many origins for a demand. You also have a batch quantity setting o the product structure that can mess up things. As a second thing to look at is to make sure you have a system calendar for the future. We have seen some odd behavior's when a calendar is missing. A third thing can be that the low level codes are wrong which can create sort of a loop if the supply is calculated before the demand (especially if you have continuous MRP on it). There is quite a lot of info in the MRP best practice that can be worth reading https://support.infor.com/espublic/EN/AnswerLinkDotNet/SoHo/Solutions/SoHoViewSolution.aspx?SolutionID=2033035&kb_is_archived=1&kb_accessed_from=KBSearchResult

Legacy Contributor

Your comment about the Calendar has peaked my interest...

When you are talking about the System Calendar, do you mean CRS900? That calendar goes out to 2040.

Are there any other Calendars we should be looking at?

Copyright © 2025 Infor. All rights reserved.