E10 equivalent for 6920 - Delete PartDtl with Invalid Job References?

Epicor ERP 10
1

Wondering if anyone knows how to refresh PartDtl records in E10
Or if there is an equivalent to the E9 conversion - 6920 “Delete PartDtl with Invalid Job References”?

I’m seeing occasional stale PartDtl records that result in PO Suggestions.
So far haven’t tracked down the cause for the PartDtl records, or how to clear them.

2

I don’t see any KB articles regarding PartDtl and orphans–not to say that it isn’t a known behavior to those that work in this area.

I know that Refresh part Quantities and Allocations is one of those processes (used to be a conversion) to check for issues with inventory. Run it in Report Only and see what it says… if there are a lot of results in report mode, it would be best to review them with application support if you have questions.

image
image.png1356×673 189 KB

3

Just out of curiosity, how many is a lot? I just ran a report here (for the first time ever I think) and got 62 pages worth. Is this something that we should be running on a regular basis?

4

I think 62 pages qualifies as a lot. Best practice is to run this process in report mode on a monthly basis around month end from what I understand.

5

So, I ran the process with update in Pilot to see what it would do. (I didn’t feel comfortable calling service and saying “I’m not sure why I’m calling, but Nathan says this is too many pages…”, while I don’t doubt that you are correct, in my experience, calling them without very specific questions does not go well). Anyways, it ran, I get the report. I then ran a preview to see what was left, and it errored out with the error saying that there was no data to show. Which, to me should mean that everything processed and adjusted correctly (Yay!). Is that a correct assumption?

So now if I run this in production (during off time of course) and run the preview every month like you suggest, I may be able to pinpoint specific problems and have more specific questions for service if a lot of things keep popping up.

Does that sound like a smart plan? Or am I totally misunderstanding things?

Keep in mind, I am not seeing the problems that Bruce is seeing with any of the parts that are on this list. (I am seeing problems related to duplicate suggestions with planning contract parts, and this didn’t fix that)

6

It would be fair to assume that it processed and adjusted “stuff” without error–I struggle with the word “correctly” not because I doubt the process or the coding or the logic, but, this isn’t my area so I don’t personally know what “correctly” looks like.

Here is what I would do in your position based on your comment about being hesitant about opening a Support case:

  • Run this process in Report mode in production.
  • Take the topmost item from the 1st, 17th, and 64th pages (nothing special about those pages, just, three random spots)
  • Open a Support case, provide the output of the entire report, in the body of the case provide the three example items you found above, and ask the following five questions about these three items:
  1. Describe what is the report telling me about these three items?
  2. What could have caused these three items to be out of sync and what can we do to avoid items not being in sync?
  3. What is the best practice when running the “Refresh part quantities and allocations”–as in, how frequently would it be recommended for most customers to run this in report mode?
  4. Is it generally considered safe to run “Refresh part quantities and allocations” in Report and Update mode without reviewing every item before updating? If not, why?
  5. How can I submit the Report only option of “Refresh part quantities and allocations” to run on a scheduled basis without manually running it each time? <--NOTE: this is a passion project for me personally, so, anything our customers can do to express interest in this would be helpful towards this goal.

Those are five-ish very specific questions that all require something beyond a yes/no response–none of which I know, but, someone who works in this area would definitely be able to answer.

Based on the answer to questions 1 and 4, you may want to check other items in the report or just run this in report and update mode blindly if it is really safe to do. I don’t think that running in update mode blindly is something that my counterparts on the application side would recommend though (but, I defer to them) because if it was 100% safe to do for 100% of customers 100% of the time, we’d only have a “report and update” option and not include a separate “report only” option.

Hope that helps.

1 Like
7

Alright. I’ll give it a shot.

If I may be so bold to make a prediction, worst case I get “we can connect you with a consultant to explain how this works” (I’ve gotten that before, hence my hesitation).

But honestly I hope they prove you right and me wrong.

Thanks for your help and your willingness to go the extra mile for everyone on the forum. Your humor and honesty go a long way in making difficulties more bearable.

8

There is a fix program you can request from Epicor - CR37784MPS…essentially deletes PartDtl records if a JobHead does not exist. Nt only does it do this but also cleans up JobMtl, JobOpDtl, JobAsmbl, JobOper, JobPart, JobAudit and JobProd. Run under Data Fix Workbench (System Mangement --> Upgrade/Mass Regeneration).

The fix pgm name is FX_Del_PartDtl_No_JobHead