We upgraded to 2025.1.6 on 11/1.
We are now getting erroneous unfirm jobs for purchased parts. Here is an example in timephase. Is anyone else seeing this behavior?
I have noticed that if I delete the revision on the part (we like to have revs for P parts too, no method just a revision, always have had this) or unapprove the revision on the part it then does not make the erroneous unfirm job.
This is a problem, we like to have revisions on our purchased parts, obviously in case a revision is made to the p part.
So the job prefix, you are sure what it’s tied to? I mean, is it also used on kanban jobs or transfers, and honestly I am drawing a blank on all the places.
Yeah, we use UPA for our unfirm PA jobs, UOH for unfirm Ohio, then on firming become FPA and FOH. Our transfers just prefix with the PA, OH, TX. These are unfirm jobs for sure, I can open it and see empty job (no bom no boo) for the purchased part.
Unrelated (this is 2024.2) I saw this week where sales orders were marked make direct, but no jobs were made by MRP… Looked in Time Phase and the lines did NOT say “Direct.”
So I unchecked “make direct” on the sales order, then checked it again, and then Time Phase was right (orders said “Direct”) and MRP made the unfirm jobs like it was supposed to.
Why? Not wanting a real answer; just an ephemeral WHYYYY?
Are they maybe all in a “horizon window” of the next 30 days or something?
Sorry, I am still in that mindset - @jkane probably knows why…
But if so, it almost sounds intentional.
"We’d prefer to buy this because our burn table makes some ugly cuts, but if we need it yesterday we can make it in house. But it will not be pretty.
ALSO… check the make buy code in both the front page on the part, as well as at the site level. because you can have the default value in the Part record set to purchased, but the site level can say Manufactured
One other thing that I can think of to check is whether the part was ever checked out to the Engineering Workbench.
This sounds like Epicor made a change to something in the release since it always worked before. I’m just trying to think of things now that might affect the results.
if the answer to this is found, i would be interested… I have a set of parts that are doing this for every SO entered for them but there is nothing different that i can see in their part set up then other parts that are working
But real quick, I have not hardly looked into it. The flag is mostly set by a uBAQ (run on a schedule), so it could be related to that - though it had been fine since February (on 2023.2), so a lot is in play for me there.
Thanks for this and the thoughts on the front page Purchased vs Part Plant Purchased Tim. They are all set for Purchase and then that Urgent Planning override.. I don’t think my version has that, it looks like this in base. I’m befuddled.
I have noticed that it is not happening to all of my P parts thankfully. It seems to be only my P parts that have zero in the warehouse where the Job is located but QOH in another warehouse in the plant.
There isn’t some place other than urgent area to setup another way to provide supply of a part over a horizon window is there? If we have anything like that somewhere it’s by mistake.
I don’t (in 2024.2) but you do seem to have that. Tim’s screenshot looks different - he has those fields in a separate group-box - but you do have the fields. You have 8 fields on the rightmost column and I have 6.
Now, why are yours grayed out? (AMM?) And they are blank in your screenshot, so if that’s one of the naughty part numbers, then it still does not explain it.
