I’ve encountered a situation where processes lose their filters when they are saved to a process set. For instance: a Site filter on MRP, a Product Group filter on Production Planning, or a Part Class filter on PO Suggestions–you define them when setting up the process in question, but they don’t persist when you go back to the process set itself and double-click the items in the Process Set Tasks grid. I’ve seen a few mentions of similar quandaries on the board, but did not find any resolutions or explanations. Does anyone know if this is expected functionality, an undocumented feature, or simply a user error?
Hi Brad!
I was told by Epicor support never to run MRP (which would include PO Suggestions) in a process set, so I can’t speak to those specifically. We do run several processes and reports in process sets that include parameters. We haven’t had a problem in our 10.1.600 or 10.2.500 environments. What version is it being reported on to you?
Jenn
Hi Jenn,
Can you expound on the part about “I was told by Epicor Support never to run MRP in a process set” ? Does this have some specific context or configuration or was this essentially a flat out “Thou shalt Not Run MRP in a process set” ?
… cue the thunder and lightning behind the bearded support person, tiredly hefting the stone tablets with the heading “The 10 Epicor Commandments”
If the latter, I must have fallen asleep in Epicor Insights Sunday School, it is new news to me.
Thanks!
Henry,
Your depiction is exactly how it went, even the thunder 
. Our issue turned out to be a specific bug that was later patched, but I never did go back to using a process set.
Jenn
1 Like
I remember that. And ditto, I gave up on MRP in process sets at the same time and never went back.
@bergamot there is a table where the subtask settings are stored, if you wanted to really dig in with a BAQ. I think you can DMT changes as well. It’s ugly, though.