PO Suggestions for Parts not in Part Master Stopped Working

We recently upgraded from Epicor 10 to Kinetic. Since making the update, “Generate PO Suggestions” has not been pulling in any new suggestions for On the Fly job materials.

We are completely custom manufacturing so every item we make is different. Because of that, most of the materials on our jobs are not in Part Master. Any of these parts that need to be bought are marked as “Purchased Direct” on the job. Before the update, it had no problems being pulled into PO Suggestions. Since the update I cannot get these to appear.

The initial response I have gotten from Epicor Support is that in order for a part to be pulled in by Po Suggestions, it has to exist in Part Master, is that correct? If so, is that something that changed with Kinetic?

Yeah, that is not correct. At my old job we were on Kinetic and POTF would show up in PO Suggestions.

Are you sure that the parts are being marked as Purchase Direct? Also, what is your setting for when Material Dates get calculated in Site Settings? It might be set to Released and changing it to Engineered or Un-Engineered might be the issue.

We’re on 2023.1.9 and we get suggestions for on the fly parts.

Can you check with a BAQ on the SugPoDTL table and see if they are there but you just aren’t seeing them from something messed up with permissions?

You can see, this is a POTF part, not in the part master
image

1 Like

Then there is something I am missing. Here is an example I just walked through:

(1) Found a job where there is a POTF marked as buy it, and not in SugPoDtl

(2) Checked the JobHead settings to make sure it is released and scheduled

(3) Checked JobMtl to make sure the part was set to “Purchase Direct”

(4) Checked the Site settings, it is set to Engineered for Material Dates

(5) I ran “Generate Suggestions” with these settings

Unfortunately it still does not show up in suggestions. Anything jumping out that I am missing?

I did notice this Purchase Scheduling field was blank in company config for us, would that be related at all?

Also, you can look at time phase, even for a POTF. Make sure there is a date on the line for the job. No date == No suggestion.

Here is the POTF from the above example in time phase, looks alright to me?

Yup, that looks right. I don’t see anything sticking out there.

Did you try the logging on the generate suggestion?

See if that sheds some light on it.

Dumb question, but where does that log get dumped to?

It’s on your server on the epicor data folder.

I don’t know if that exactly right, I didn’t test it, but it somewhere in the data folder.

Yeah, that’s right.

I don’t recognize this checkbox (It’s not in classic, so I’m guessing it might be a new feature). Have you tried running with this unchecked?

Yeah I have tried toggling that off, running regenerative, net change, etc. The only thing that jumps out is the “Part Run MRP = false”, not sure if that is actually something or not.

image

Are these the same thing?(Are you multi site?)

They are the same, MfgSys is our Denver site.

Nothing else in the log file? Did you change the logging level?

Also, are there any other POTF parts in suggestions at all? (just trying to see if it’s systemic, or specific)

I attached the full log file. There are a couple POTF , but they are all from before the update. Nothing has been pulled in since we swapped to Kinetic.

Epicor Log File.txt (9.0 KB)

So, I see an exception for net.tcp not supported. If you make a change to a non POTF part, and generate suggestions, does that get updated?

Is your task agent connected correctly? Are you load balanced? Or a single app server?

Just got some more info on that:

  1. Task agent is setup for HTTPS since we are on 2023.2
  2. No load balance, single app server.

Well, something is mis-configured then. Because you shouldn’t be getting that error. I suspect that your suggestions are all leftover from before you upgraded.

Yup, that is making complete sense. Let me do some digging and hopefully reply back with the answer here soon :slight_smile: