We are seeing invalid data points in the Time Phase, “orphan records”
I’ve contact Epicor support they gave us a data fix to remove “everything” in the partdtl table.
We did this in a our test database, which did clear out the records in the time phase / partdtl for the active transactions in the system.
I’ve tried MRP regen and no success on rebuilding the partdtl table.
Does anyone know how to resync the partdtl table correct?
I’ve seen these “orphan” records in PartDtl and gotten fixes from Epicor for it but it never removed “everything”. It was always targeted at the offending records.
did they give you a query to find out easy what orphan records were or do you have a query of some sort?
we are getting several orphan records. Epicor support does provide a fix per instance, but this is getting really old. i run a query on partdtl to get the sysrowid, but i am hoping someone either figured out why this happens or found a faster solution than contacting epicor support everytime.
Could you please elaborate more? Could you share a screen perhaps?
Thanks!
Just wondering what version you are on?
And if you’ve already run built in conversions, which ones?
I’ve seen orphans in various places in past, hard to nail down the source.
I tend to assume users have performed some unusual entry sequences or switching values back & forth while save rapidly.
Forms that are updating a lot of related tables seemed to be the most susceptible
e.g. Order, Quote and Part entry.
Hi Bruce. The version is 10.2.100.6. we have run some built-ins but none recently, It seems that this just started happening. We are checking the parameters of our MRP process. Epicor support said we shouldn’t be seeing these orphans and it must be a process. You are correct that it is hard to nail down the source. Also checking when backup occurs, in case that interferes momentary;y with the process. If i find something definitive, i will post back. Thank you for your response!