Orphaned Job Material Records

Kinetic ERP
1

Has anyone else come across a situation where there exists JobMtl / PoSugg records referencing Assemblies that no longer exist?

We recently had an issue reported where a set of sub-assemblies had disappeared from a Job, did some digging and found the JobAsmbl records no longer existed however we still have JobMtl, PartTran (PO Receipts), PO Detail and PO Suggestion records that reference these missing Assemblies on that Job.

Under normal circumstances the system will not allow you to delete an assembly with materials that have transactions recorded against them so it’s a bit of an odd one and unsure how we’ve ended up here in the first place.

Unsure on the best approach to resolve this, have reached out to our support provider and Epicor for assistance but curious if anyone else has come across this scenario and might know of a reason that caused it or have some ideas on a solution.

2

Yes. I’ve had this happen recently.

I had to enter a ticket with support and they provided a data fix.

Reference KB0051429

3

Here’s the post where I was taking down the similar issue.

Make sure in your request for a data fix, you detail what records are sticking around. I later found others tied to the same deleted assemblies and had to make a second request.

Initially i was worried about orphaned operations, the first fix deleted those… but then we found orphaned material requirements like you’re seeing (triggering suggestions) and i had to get a second fix to delete those.

4

Cheers for the response, this is probably a similar issue, assemblies were there one week and gone the next, trouble is we have PO’s, suggestions and receipts that refer to the missing assemblies, did you have any LaborDtl transactions against the operations that were referencing the missing assemblies?

1 Like
5

No, for us, luckily, i think the assemblies got whacked before we transacted against them.

There were no issues materials, nor labor transactions against them.

I have no clue what broke down to orphan the records. For us it was operations and material requirements.

6

Epicor support working on the issue, I ended up restoring a backup copy of our database from a week ago where the Assemblies existed in our Pilot system and provided Epicor support with a copy of what the data was and they are providing us with a data fix to load the missing assemblies back into the system.

1 Like
7

I’d be interested to hear if they can discern a root cause for them being deleted. When this happened to us, I just assumed a user had deleted the assemblies but the system failed to delete the child components. But in your case it sounds like the system deleted your assemblies. This is a pretty alarming thing if it happens for no known reason.

8

Yeah, I doubt a user managed this as we restored a backup from before they went missing and attempting to delete the assemblies from the front end and DMT, they both end up with an error message stating there are transactions on this assembly or a sub-assembly as you’d expect.

I also doubt I’ll get any further assistance from Epicor support after they provide the data fix to load the missing assemblies back in, I’d like to nail down a reason why this happened, but I doubt I’ll be able to find that reason.

1 Like