I have a bug report open with Epicor on DMT (PRB0212569) due to the fact that DMT re-numbers order releases on import. For example, we may have 12 releases on an order and deleted number 2 a long time ago. Rather than DMT importing them as numbered, it changes 3-12 to be 2-11. Since nearly everything in Epicor links back to Order Releases, I view this as a very serious data corruption bug.
But this is where things get fishy. The Epicor tech said and I quote “I got informed that there is an Add on called Historical DMT that should allow you to do what you need. I am requesting the mentioned Add on today; my plan is to install it in our lab for testing and share the outcome with you.”
In a subsequent message he said:
“I had my specialist to install it and tested it. We found that it works for what you are looking for. Not all the templates that are available at DMT are available at Historical DMT, fortunately the entry you are working on is. Historical DMT is not included with DMT, so I am adding your CAM as the application might have an additional cost.”"
Then when contacting my CAM and her manager, neither have ever heard of “Historical DMT” and said there is only 1 DMT license. Obviously I don’t feel I should need to purchase a 2nd license to migrate data without corruption.
Does anyone out there know what this mythical “Historical DMT” is that imports data without corrupting it?
It seems so backwards to offer a “data migration tool” that doesn’t do historical data. If one isn’t migrating historical data, what are they migrating? Data in real time? Shouldn’t need a separate license to migrate historical data when “migration” is part of its name.
I ran into this when migrating from V8 to E10 (via DMT). My solution was to create those missing lines and releases with a “filler” line or release, and then go back and delete them after being uploaded.
I also found out that the MtlSeq in a DMT file was not honored either.
I get that Calvin. But doesn’t irk you a bit that they have a second license to do it correctly, without you putting in all that extra effort? The DMT should handle this out of the box, not require a separate license just so it doesn’t corrupt your data.
Ohh… I was more than irked. Especially since we migrated select V8 data to E10, instead of Updating V8 to E10. And this is the first time I’m hearing that this “special” version exists.
Probably mostly peeved that DMT failed to mention not honoring things( like OrderNum, OrderRelNum, etc…) in the DMT file being imported.
Historical Data
Historical DMT (licensed separately) offers additional capabilities to import historical data, such as closed and shipped sales orders, closed and received purchase orders, historical job transactions, posted AR invoices with detail, posted AP invoices with detail, and posted GL journals.
I ran into this too when we “RE-implemented” from 10.0 to 10.1 back in the day. I got around this by creating “OrderRel.VoidRelease” lines and setting that bit to true. I had no idea there was such a thing as Historical DMT would of made life so much easier!
I have been doing historical loads of data for the past few years without a special license.
Last upload I did two years of data. After loading the data, go back and close the releases, etc.
To load the tables I take the files and update them with dummy lines - (which I close).
The tables that I have done this on are
Quote Lines
Sales Order Lines
Sales Order Releases
PO Lines
PO Releases
Job Assemblies
I create a excel formula to look for gaps in the data. There are also someways to do this by coding or downloading a program.
Bruce I understand that, I knew that before starting this thread. This thread is about the fact that they have a 2nd license to do it correctly the first time around without all of your extra work. Yet none of us have ever seen it or been told about it, not even our CAM. I am trying to figure out how to get this extra license so I don’t have to waste a bunch of time correcting errors created by DMT itself. Yes, I can write code to work around it but the point is we purchased this tool which is advertised and sold as (see website)
Import, add, update and delete application data safely and efficiently.
Application logic ensures security, data integrity and optimal performance.
DMT alone absolutely does not meet those criteria. Only “Historical DMT” will ensure data integrity, while DMT alone actually corrupts data. Re-numbering order releases breaks everything. It shouldn’t be this way.
Sounds like a tool that is designed to circumvent business objects. Just load a bunch of historical junk that doesn’t need to be processed but will show up in transaction histories, etc.
The manager of our CAM region did some digging for me and found out “Historical DMT” is a tool developed by the UK custom solutions group. He’s still claiming we need to purchase it for around $2000 but I call B.S. We purchased the DMT tool which is advertised and sold as (see website )
Import, add, update and delete application data safely and efficiently.
Application logic ensures security, data integrity and optimal performance.
DMT alone absolutely does not meet those criteria. Only “Historical DMT” will ensure data integrity, while DMT alone actually corrupts data. Re-numbering order releases breaks everything. It shouldn’t be this way. This essentially amounts to false advertising and can be reported to the FTC. Hopefully Epicor will make things right for us, still working on that.
I’m still confused as to the business need. If you deleted a release, in which system would it have been deleted and why would it need to be imported again as a new release?
Where was it deleted? We’re on Vantage 5.2, migrating data to Epicor 10.2. Over the last 20 years there have been many releases that have been deleted, perhaps because the customer asked us to or because we had some other business issue. Deleting a release is a normal part of how both Vantage and Epicor operate.
A deleted release would not need to be imported again as a new release. We don’t want dummy releases in there.
The business issue is that DMT re-numbers the releases on import when there is one that has been deleted – it will only number sequentially. But everything references back to the release number, so when I import other data that references a release number there will be no data integrity. The re-numbering by DMT makes the data unusable.
This is different from how DMT operates in other scenarios. For example, we also delete quotes from time-to-time. DMT imports non-sequential quotes just fine, but it corrupts non-sequential order releases.
