Ah, that does look familiar. You would hope they tested the utility pretty well if their E10 upgrade support team is recommending it.
Ah, that does look familiar. You would hope they tested the utility pretty well if their E10 upgrade support team is recommending it.
I just learned a few interesting things from Epicor Support about their Data Scrub Utility. We are on Epicor 9.05.701. When we ran the Data Scrub Utility, one of the problems it showed in its log was:
"Failed","50BB5FC6-3B01-4252-9F25-774D81AB3C31","rcvdtl","Update rcvdtl where receiptdate <> rcvhead.receiptdate set ReceiptDate to rcvhead.receiptdate","SS_70X_rcvhead.r"
They then sent us a fix program to change all of our RcvDtl (Receipt Line) records to have the same Receipt Date as their RcvHead header. It seemed to me that there would be a valid business case for a Receipt Line to have a different Receipt Date than its RcvHead header record. For example, if one receipt line was received on 3/4/2015 11:55 PM and a second receipt line received on 3/5/2015 12:01 AM, wouldn't that be valid? When I asked Epicor Support about it, here is the response I got:
-- Snip 8<----------------------------------------------
You are correct, there can be instances where there is a valid business case for a receipt line having a different Receipt Date than the RcvHead header record.
In your case this sounds valid and you should not run this fix program.
In some other customer instances we have had this data was not correct.
You should not run this data fix. It is up to the customer to review what the scrub is doing and determine whether the fix should be run.
-- Snip 8<----------------------------------------------
Moral of the story: Don't blindly go run all of the Data Scrub fixes they send you. Try to understand what each fix does and decide if you think it needs to be run.
It would be nice if they could rate the issues that the Data Scrub Utility finds as Critical vs. Potiential Issue.
I also learned that the Data Scrub Utility itself does not correct any records, it only logs what fails, then Support sends you the fixes that actually fix the [potential] issues.
Take care,
Greg Bakker
Kooima Company
Note: Remember that this change has NOT gone through QA and regression testing. While every effort has been made to ensure that it will operate properly, it is the customer’s responsibility to ensure that it is operating correctly in their specific situation prior to placing it in a live environment.
Miguel A. Santillan
Compass Manufacturing Systems
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, March 10, 2015 12:18 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Data Scrub Utility Info
I just learned a few interesting things from Epicor Support about their Data Scrub Utility. We are on Epicor 9.05.701. When we ran the Data Scrub Utility, one of the problems it showed in its log was:
"Failed","50BB5FC6-3B01-4252-9F25-774D81AB3C31","rcvdtl","Update rcvdtl where receiptdate <> rcvhead.receiptdate set ReceiptDate to rcvhead.receiptdate","SS_70X_rcvhead.r"
They then sent us a fix program to change all of our RcvDtl (Receipt Line) records to have the same Receipt Date as their RcvHead header. It seemed to me that there would be a valid business case for a Receipt Line to have a different Receipt Date than its RcvHead header record. For example, if one receipt line was received on 3/4/2015 11:55 PM and a second receipt line received on 3/5/2015 12:01 AM, wouldn't that be valid? When I asked Epicor Support about it, here is the response I got:
-- Snip 8<----------------------------------------------
You are correct, there can be instances where there is a valid business case for a receipt line having a different Receipt Date than the RcvHead header record.
In your case this sounds valid and you should not run this fix program.
In some other customer instances we have had this data was not correct.
You should not run this data fix. It is up to the customer to review what the scrub is doing and determine whether the fix should be run.
-- Snip 8<----------------------------------------------
Moral of the story: Don't blindly go run all of the Data Scrub fixes they send you. Try to understand what each fix does and decide if you think it needs to be run.
It would be nice if they could rate the issues that the Data Scrub Utility finds as Critical vs. Potiential Issue.
I also learned that the Data Scrub Utility itself does not correct any records, it only logs what fails, then Support sends you the fixes that actually fix the [potential] issues.
Take care,
Greg Bakker
Kooima Company