We have a system outside Epicor that defines our top level serial numbers for finished goods products. The system is developed in-house and I would like to be able to assign the serial numbers to the job via REST instead of having to go through the tedious amount of mouse clicks to get the number added the the job. It would also reduce the chance of error manually recording the serial number.
Has anyone tried this before and if so, I would be grateful to see how you did it to get me headed in the right direction.
Personally, I would code the work in an Epicor Function that accepts the job, assembly, Part Number, and the list of serial numbers and call that function via REST.
Coincidentally I just went through this process myself, assigning serial numbers based on outside SN generation. Our process is that each job is only qty 1, so I probably make a few assumptions that you’ll need to correct for. I’m happy to share what I have to get you started though.
Due to conflicting tablesets (ex. SelectedSerialNumberDataSet) between multiple services, I had to create two libraries and call from one to the other.
As mentioned, all my jobs are qty 1; the expected serial number is stored in a UD field JobHead.SerialNumber_c rather than being passed in.
Chris,
Thanks for the reply.
In my situation, there could be more than one on the job and I just want to assign the serial number to the job. I still want the production folks to select the serial numbers at the Operation as they are completed. I’ll have a look at the attachments and see what I can see.
Knowing nothing more than what you’ve said here, I’ll speak a possible heresy… is there any way that the serial number generation process itself could be coded in C# or SQL, and bring that calculation into Epicor?
Thanks Ernie, for the reply. I have thought about having Epicor do this but there is still the idea of having to “create” the serial numbers before you actually select them which I suppose could be automated. The other issues is that the serial number is required early in the process and sometime we are out ahead of Epicor. Meaning we are sometime building stuff before the Epicor job gets created. Also, the external software does way more than generate serial numbers which would likely never be able to live inside the Epicor framework.