The GS1-128 standard is an application within the Code 128 barcode. It identifies data with Application Identifiers (AI). You can find more information about GS1 General Specifications at the url below:
https://www.gs1.org/docs/barcodes/GS1_General_Specifications.pdf
AIM Code
The AIM Code ID is a 3 character ISO/IEC identifier that gives information about the symbology of the barcode which was scanned. Produmex Scan doesn’t support the AIM codes, so the Code ID type must be configured to ‘None’. Sending the AIM code on the device must be disabled as well.
Produmex Scan Settings > Produmex Scan Scanning tab
AI codes
Not all AI codes are supported in Produmex Scan. In case the barcode contains an unsupported AI code, then the application won't be able to interpret the barcode.
You can find the supported AI codes on the url below:
http://wiki.produmex.name/doku.php?id=implementation:scan:supportguide:ai
Difference between GS1-128 and not GS1-128 codes
Since Produmex Scan does not support the AIM code, the application makes difference between the codes using prefix and suffix.
You can configure a prefix and suffix characters in Produmex Scan Settings. Prefix and suffix characters can be configured on your device for each AIM code on your device. You must configure the same prefix and suffix character for the GS1-128 code that you have in Produmex Scan Settings.
If the application receives a code from the device that have the same prefix and suffix that is configured in the add-on settings, then the application will split the data based on the supported AI codes, and it won't change the data in any other cases. I will use the default bracket settings in my further examples.
Produmex Scan Settings > Produmex Scan Scanning tab
Scanning the barcode with the device
The brackets are only used in the human readable text under the barcode. The purpose is to differentiate the separate data elements. When you scan a GS1-128 code then the scanned data won’t contain the brackets.
Data after scanning the barcode will be: 01993100950003581725123110BTN001
The device will add the configured suffix and prefix to this data, so Produmex Scan will receive the following text:
(01993100950003581725123110BTN001)TAB
TAB suffix is mandatory configuration on the device!
In case you would like to emulate the scanning event during your tests using the application for Windows computers then you must use this text without the TAB part, and press the TAB manually.
Group Separator
There are AI codes where the data length of the value is variable. In this case the standard GS1-128 code uses a group separator character after the value. This character is the invisible [FNC1]
For example, the length of the batch number is variable. In case there is another code after the batch number, then an FNC1 is required before the next code.
10 BTN001 [FNC1] 37 10
This group separator must be replaced on the device by the character that is configured in Produmex Scan
Produmex Scan Settings > Produmex Scan Scanning tab
This device configuration is not necessary on Android devices. However if you do test on the Windows version, and you emulate a scanning event, then you will have to use this group separator during your test, even if you will use Android device later.
human readable text under the barcode:
(01)99310095000358 (10)BTN001(17)251231
Text for the test:
(0199310095000358 10BTN001$17251231)
The group separator is not supported in barcode scanning with camera function.
GS1-128 data in Produmex Scan
Produmex Scan splits the information automatically. The data from the barcode is stored in the memory and it can be seen on the Customization Assist window.
Customizing Batch/Serial details
It is possible to add a custom field to the Batch and Serial quantity screens to set batch detail values. The corresponding data from the barcode won’t appear in the field automatically. However, if you add these fields to the screen, then you must fill the field or else the data will be lost. You can find more information about this customization on the url below:
http://wiki.produmex.name/doku.php?id=implementation:scan:customizationtechnology#field_name
The custom filed must be configured on the quantity screen and the validate after query of the input field can be used to put the value into the custom field:
The date format of the custom field is the same that is configured in SAP. It is possible that you have to
add some SQL logic to convert the date value into the correct format.
Comments
0 comments
Please sign in to leave a comment.