DMT Error on Quantity Adjustments

Kinetic ERP
,
1

Getting ‘Different’ DMT errors from the same data set using the same DMT script!

This is the first set of errors

image
image856×943 73.7 KB

As you can see the Lot Number is in the Script.

I then moved the columns around based on a few suggestions from posts on here and i get the below!

image
image1601×1038 148 KB

Same data!

The odd thing is that i did an initial test to make sure the layout worked in the first place with the first item on the list of errors and i added it and removed it fine using the same script!

image
image1872×652 52.2 KB

I have raised a ticket with Support, this is the second DMT related ticket i have raised in a few days as we are trying to migrate data into a Kinetic Test environment for one of our sites.

2

If you go in site maintenance is that really your plant id (not all upper case)?

1 Like
3

Yep that is the site id.

4

Are all of the parts in the file lot tracked?

5

Yes they are

6

here are the headers from a file I ran successfully:

image

Maybe try that order (minus the serial num) if you haven’t already?

1 Like
7

OK Will give that order a go :+1:

8

That works, thank you so much Alisa.

1 Like
9

Out of interest, was that a recent file, the reason i ask is that the script i am using worked when we migrated our first site to Kinetic, albeit the beginning of 2025, i was just wondering if it is something EPICOR has changed.

10

It was from a couple of months ago (25.1), I don’t know if anything specifically has changed, its always been super finicky in my memory.

11

image

That’s the one I used at the beginning of last year to migrate the first site to Kinetic.

Super Finicky is an understatement :rofl:

1 Like
12

Glad @aosemwengie1 chimed in first; I had a thought but was not certain.

I was going to suggest moving the LotNum column after the bin.

IMHO, lot numbers are sub-bins.

I am aware this is not true at all, but I find it useful to operate as if it were.

Odd that Plant did not need to come before PartNum. I also assume that in my mental hierarchy.

Kind of curious what was the single smoking gun that did it.

13

When in doubt, perform the transaction manually and then put your dmt fields in the order that matches the UI.

1 Like
14

I am kind of curious as to why my previously used script did not work :thinking:

15

When ANY DMT gets persnikity, I’ll look to the actual program in the UI to see what the field order is. In the Quantity Adjustment program in the Kinetic UI, the top portion of the screen wants the Part Number and Warehouse Code… so put those first. The Plant value is taken from the current plant you are logged into, so to cause the LEAST grief I’d put it last. The other fields are all in the lower part of the screen, and in this case the working DMT field sequence is NOT the UI field sequence, so it may or may not matter… but that’s where I’d start.

The DMT certainly has its quirks.

1 Like
16

Certainly does, i just loaded another script which i have always used for Cost Adjustments and it was throwing another wobbly. It didnt like the fact that part number column was set as text cells. Again i have never come across that issue before and i am using the exact same set of scripts that we used to migrate our live site to Kinetic.

17

I’m GUESSING that the Adjustment Business Objects (both Cost and Quantity Adjustments) were changed slightly beneath the hood recently… I don’t recall either of these DMTs giving me grief in past implementations.

To test, open Quantity Adjustment. Enter a Part Number. Hit the TAB key. Fill out the fields in the TAB order, and NOTICE when it “thinks” between fields. That means some BO is running… and to me that indicates a “break” in the sequence. Fields grouped between “breaks” can (probably) be in any sequence, but the the groups themselves need to be in the correct sequence.

Doesn’t always work, but it’s a start.

1 Like