Well....this is a weird one Part Exists in SQL But Not Found

Epicor ERP 10
1

Hey Everyone!

I’ve never stumbled upon this issue before…we have a part in the part table but Epicor cant find it.
image

image
image.png611×526 7.28 KB

Any idea why?

GetByID Method:
image

2

Space at the end or beginning? In the Db?

3

Does the Company matter? I notice the BO looks in the current company

Also as a general observation, I see that the GetByID, calls InnerGetByID, which actually uses a stored proc for the query

1 Like
4

You are for sure looking at the same DB right? (had to ask)

5

I don’t believe it is company/site related as we really only use one company.

Support is saying there could be a bad record in the plantwhse or partplant tables. We shall see.

Now what makes the bad record happen to begin with? Thats the million dollar question.

I am looking at the same DB hahaa. The weird thing is we dont have this issue in test , only in live. We refreshed test about a month ago.

6

Just curious … What is the little arrow next to the Part field?

Something new since 10.1.400? Or is this a customization?

image

7

@ckrusen BAQ Zone

2 Likes
8

You can make BAQ’s run when you hover over it. I have one for part where used. (and other things)

image
image.png762×334 17.7 KB

2 Likes
9

We get the bad plantwhse record thing pretty often. I run a DataFix Workbench to fix them, at least once a month. But they never give the problem you show.

10

looks like it is because we have a bad warehouse / site combo in the plant whse table

How did that happen? hmmmm

11

We recently had the exact same issue but I was unable to determine what caused the records to be created. I have not been able to replicate the issue in our Test system either so if you can determine a cause I would love to hear it.

1 Like
12

I tried creating a DD to catch when these warehouse to site mismatches occurred. But they never fired, even when the issue happened. :frowning:

13

I’d love to try and catch these automagically.

I would have fixed this myself, but because I can’t even get the part dataset to update via get by ID in the bl tester I have to wait for a data fix from support.

14

One thing that we found is that we only got the Add New Error on a single app server. That made me think that it was a Client DLL mismatch.

You can try to load the Part Record from the client on the Epicor server and see if it lets you there. If it does you can just delete the bad PartPlant records.

15

I have seen something similar in the past… it was one of the following reasons:

  1. Space before or after the part# when it was created.
  2. Company case (upper or lower) different than the rest of the parts
  3. PartPlant, PartWhse, or PartCost bad or missing.
    You can create for each of these 4 tables and look at all the data.
16

Not the OP’s issue, but we’ve run into people copying from a website, and the “dash” is really an “en dash” or “em dash”.

- regular dash (U+2012, ASCII 2D)
‒ fig dash (U+2012)
– en dash (U+2013)
— em dash (U+2014)
― hor bar (U+2015)

And a space being represented by CHR(160), instead of CHR(32).

17

Thanks for the feedback everyone!