Data Corruption bug on Cash Head

Epicor ERP 10
, ,
1

Just ran across this issue and I thought I’d throw it up here in case others have the problem too. We found that when you create a Zero Dollar invoice in a batch, the Customer ID of the wrong Customer is sometimes assigned to the Cash Head Record.

The following query can confirm

SELECT CH.CustID,CH.CustNum, C.CustID
 FROM Erp.CashHead as CH JOIN Erp.Customer C on CH.Company = C.Company AND CH.CustNum = C.CustNum
 WHERE CH.CustID <> C.CustID
 Order by TranDate DESC

I’ve opened a detailed ticket with Epicor and I’m expecting a fix at some point, but may be worth checking.

Case: CS0001924171

It looks like this only applies to zero dollar invoices we have more than 4K records with this issue in our system.

2 Likes
2

I find it odd that the CustID field is being stored on some of these tables if the CustID can be changed at the Customer level…

2 Likes
3

I agree, but alas they have it…not only that but that’s the field that is used to display in Cash Receipt Tracker, which means when you pull up the record in Epicor it shows the wrong customer.

4

Thanks for the heads up. Obviously easy to put the bandaid on, but not a happy bug.

Jason Woods
http://LinkedIn.com/in/jasoncwoods

1 Like
5

WOW thanks Jose I ran your query and found over 1000 records!

can’t wait for the fix…:wink:

6

Only 60 records here – over a span of 5 years……

7

Yeah it’s only a problem for Zero dollar invoices which most companies don’t use a lot. Unfortunately we do a LOT of samples so we have over 4K records.

8

We have the same issue but we can’t be added to your case…

Can you post the Problem Number once you get that?

9

Why can’t you reference my case? Weird, yeah if / when I get a problem number I’ll post it

10

I can reference your case but then I have to reduplicate all of your steps and they are saying they may want a copy of our db…

11

A copy of the Db? It is trivial to replicate… Jesus!
Stand by I’m sure they’ll get a problem number for me.

1 Like
12

No worries, it’s standard tier 1 support. There just doesn’t seem a lot of benefit to have multiple support reps working on the same problem separately

13

Yeah I’m struggling with support at the moment cause I put in a detailed ticket with steps to replicate and the response I got was…
Can you please provide steps to replicate…

2 Likes
14

“Please Provide Steps to Replicate”
AKA:
“It’s so close to the weekend that I am throwing every delay at you so I don’t have to do any real work myself”

2 Likes
15

Just curious… could you make a BPM that updates the CustID field based on the CustNum field, every time the record is created?

And are you 100% sure that the CustID is wrong, and it’s not the CustNum? :wink:

16

CustNum is correct (because they pull it from Invoice instead of the Customer (lookup)

And No, BPM won’t fix it because this happens on Post (there’s on BPM for Post since its an asynchronous call)
Also they create the record directly from the posting engine without hitting the Data Directive Engine, so not even a DD will work.

You could write a Batch Script or an Epicor Function to go clean up this once a day I supose.

I also looked at the code further they also pull BillingDay and BIllingFrequency from the wrong record

      this.tmpBillFreq = this.Customer.BillFrequency;
      this.tmpBillDay = this.Customer.BillDay;

And that doesn’t only affect Zero day invoices (though its hard to determine without much more analysis)

Hoping when this fix this problem they go back and double check anything else affected.

2 Likes
17

Replying to tag myself on this case, we have 1108 records that are wrong…

1 Like
18

I already submitted a duplicate for this too. They are getting hit all at once with it. I’m sure they will sort through it and it will get handled :slight_smile:

19

1177 Rows for Us

20

Epicor has verified this bug, and they are working with development

Problem Number: PRB0221409

They were able to replicate… on pretty much all 10.X versions

1 Like