Auto Serial Number Assignment via DMT Based on Job, AssemblySeq, and Quantity

Kinetic ERP
, , , , , , , , ,
1

Hello Everyone,

I am facing an issue related to Serial Number Assignment in Epicor, and I am looking for a more efficient solution.

When we assign serial numbers manually inside Epicor, the system automatically creates new serial numbers based on the quantity.
However, when we try to do the same using DMT, we must explicitly specify each serial number, which becomes a challenge.

image
image750Ă—505 18.5 KB

image
image647Ă—435 13.9 KB

DMT
image
image526Ă—439 23.1 KB

Business Scenario:

  • In our company, the same part numbers are used in repeated job releases based on requirements.
  • For a single order, we may create 10–15 jobs, and each job can have 150–200 sub-assemblies.
  • We have to manually go into each assembly and assign serial numbers one by one.
  • This process is very time-consuming and error-prone.

Problem with DMT:

  • DMT requires us to specify exact serial numbers.
  • To do that, we must first manually find:
    • The last serial number used for each part.
  • This again becomes a manual and time-consuming process, so DMT does not really help in this scenario.

Requirement / Question:

Is there any way (standard Epicor functionality, BPM, customization, or DMT enhancement) where:

  • I can provide only:
    • JobNum
    • AssemblySeq
    • Quantity
  • And Epicor should automatically assign the next available serial numbers, similar to how it works during manual serial assignment?

Any suggestions, best practices, or examples would be highly appreciated.

Thanks in advance.

1 Like
2

Serial Number BOs are kind of a pain to work with as there are a lot of parameters and variables. But sure you can do this, I would do it with a function, that you can then call from a dashboard and supply the relevant inputs/monitor outputs.

You need to use Browser F12 Debug Tools on Kinetic to Trace what happens in the payload and response/preview for network calls when you perform the actions manually. This tells you how your web browser is “talking” to the Epicor Server.

Then, work back from that “conversation” to decipher the logic (get a blank record, add 5 to the quantity, send the updated record to the server with RowMod = “U”, etc.) to build into a function, calling the same business objects and performing the same actions.

There are numerous posts on the details for that here, but that is the high level overview.

3 Likes