I do not understand how the Data Management Tool is organized. I will always know the table I want to DMT into, but I frequently find that what it is called in DMT doesn’t match my expectations, and as a result I waste time trying to figure out where the right menu item is.
For instance, I need to DMT into PLPartBrk and PriceLstParts. I see “Management / Sales / Price List Part” which requires Company, ListCode, PartNum, UOMCode, and PLPartBrk#Quantity (optional). I see all these fields in the PLPartBrk table, although I question if this is the real menu item why it explicitly names the table for the quantity if they are all the same table anyway. But when I look for PriceLstParts I have gone through some different possibilities, but every one I have looked at so far listed required fields which are not in the PriceLstParts table.
Specifically I would like to ask which menu item specifically corresponds to PLPartBrk and PriceLstParts. But more generally, how can I help myself next time to figure these out so I don’t have to go get help every time I encounter a new table I haven’t DMTed into before?
(I already tried what I thought would be the most obvious way, by putting the actual table names into the search bar, but this returns nothing!)
I have solved part of the problem - I discovered that if I click on the “Template Builder” button in the lower right corner it brings up a table of all the fields available. From this I can see that “Management / Sales / Price List Part” DMT actually covers both the PLPartBrk and PriceLstParts tables.
I don’t know the solution to the more general case though.
You’re probably not going to like the answer… but the DMT is actually based around the Epicor Business Objects (hence also the User Interface). To find out what fields are required, the best way I’ve found is to open up Epicor and follow the out-of-the-box process for entering that data manually.
And typically, the DMT follows the BO’s rules and would prevent you from doing things in DMT that you can’t do via the UI.
For example, If deleting an order first requires deleting the order’s lines, then a DMT to delete an order, via just the Order Header, won’t succeed. You’d need to use DMT to delete the Order Lines first - which would probably fail because you’d probably need to delete the Order releases before that.
Now some DMT “objects”(??), will process on multiple aspects. These typical include “Combined” in their name.
Here’s part of the Sales menu
You see that you could use DMT on just the “Sales Order Header”, or “Sales Order Combined” In the combined DMT “object”, you’ll usually see fields with a # in them. This is used when you need to specify the table you’re trying to affect.
The Sales Order Header object has a field OrderNum. So do each of the Sales Order Line and Sales Order Release objects. But the Sales Order Combined needs to specify the OrederNum for each of those tables, so you end up with fields:
OrderNum
OrderDtl#OrderNum
OrderRel#OrderNum
Some objects are inherently related, so multiple tables will always be updated together. I’m guessing this is what you’re seeing on PLPartBrk and PriceLstParts
