These questions aren’t directly related to Epicor, but I thought someone her might have run into this (or something like it) before.
“Serial Numbers” are technically character strings. So do you include leading zeros? Most systems would see
01234 as different “serial numbers”.
If the supplier of a part is to determine the S/N of the part, there is a chance (however slim) that different suppliers of the same part could provide overlapping S/N’s.
My main issue…
We have PCB’s made for us, and want to add labeling with barcodes to aid in data capture during manufacturing. We want two pieces of info to reside in barcodes - the part number, and the serial number.
Normally we could just put two labels on the PCB, sufficiently spaced to prevent accidental scanning of the wrong one. But on some PCB’s were are severely limited on space.
The P/N format is ##-#### ex:
The SN format would be number determined by the PCB assembler. Ex:
A couple of solutions would be:
Have two labels close to each other and have the program that receives the scan result check if it is the format expected before accepting it. When scanning the P/N it must find a
-, else reject it. And the SN must not contain a
-. This requires customization of the program expecting the data entry from the scanner.
Have a single barcode that contains both the P/N and SN in a single scan and parse it in the receiving program. This would require deciding if the fixed field lengths or a delimiter would be used.
Ex: Part 01-2345 with SN 54321
- Delimiter like
- Fixed width with chars 1-7 being the PN, and any remaining being the S/N, like"
Again this requires customization of the program that receives the scan.
- Delimiter like
Is it a crazy idea to have a single barcode that needs post processing to break it into seperate values?