Skip to main content

Barcode tokenizer

Many of the operations that can be performed in Fluentis WMS can be facilitated and accelerated by using the Input code field, which, if properly configured, intelligently reprocesses the data acquired through barcode reading and autonomously inserts the values into the corresponding fields. This provides a significant advantage to the operator both in terms of input speed and efficiency, as they will only need to read the data in the same Barcode Code field without the issue of having to change focus.

In the header table, the fields to be entered are:

Code: indicates the prefix of the barcode tokenizer;
Description: indicates the description of the barcode tokenizer;
Separator: indicates the separator character of the barcode tokenizer.

In the detail table, the objects and properties that we will read from the barcode must be defined.

The barcode must be created using BarcodeCode + Separator + BusinessObject.Property [+ Separator + BusinessObject.Property]

The last part BusinessObject.Property can be repeated multiple times; the Length or the Separator defined in the table will allow for identifying the correct values.

Typically, in a barcode tokenizer, there is only one Main object, which can be composed of multiple Business Objects.
These Business Objects can be direct properties of the Main object (in which case the Business Object will be the same as the Main object) or they can be properties belonging to other Business Objects, but still referenced in the Main object.
We can say that the Main object that is returned from the barcode reading is constituted by the composition of all the properties of the inserted Business Objects.

Note

Of course, depending on the data set being used, one must ensure that the configuration identifies a unique result.

Below are some examples of constructing the Barcode tokenizer:

Example: Item-MOB-ART

CodeDescriptionSeparatorBusiness ObjectPropertyLengthSeparatorSequenceMain Object
ItemItem Barcode-FSItemClassCode3-10FSItem
ItemItem Barcode-FSItemCode50-20FSItem

Example: Loc-01-L1

CodeDescriptionSeparatorBusiness ObjectPropertyLengthSeparatorSequenceMain Object
LocLocation Barcode-FSWarehouseCode10-10FSLocation
LocLocation Barcode-FSLocationCodeLocation100-20FSLocation

Example: UDC-2023-5-21

CodeDescriptionSeparatorBusiness ObjectPropertyLengthSeparatorSequenceMain Object
UDCUDC Barcode-FSLoadingUnitYear4-10FSLoadingUnit
UDCUDC Barcode-FSLoadingUnitGroup4-20FSLoadingUnit
UDCUDC Barcode-FSLoadingUnitNumber4-30FSLoadingUnit

Example: Lot-MOB-ART-123

CodeDescriptionSeparatorBusiness ObjectPropertyLengthSeparatorSequenceMain Object
LotLot-FSItemClassCode3-10FSBatchRegister
LotLot-FSItemCode50-20FSBatchRegister
LotLot-FSLotRegisterCode05-30FSBatchRegister

Example: MesPop-10824

CodeDescriptionSeparatorBusiness ObjectPropertyLengthSeparatorSequenceMain Object
MesPopProduction Order Phase-FSProductionOrderPhaseId-10FSProductionOrderPhase

Example: Qty-50

CodeDescriptionSeparatorBusiness ObjectPropertyLengthSeparatorSequenceMain Object
QtyQuantity-100-10

Example: ItemQty-MOB-ART-35

CodeDescriptionSeparatorBusiness ObjectPropertyLengthSeparatorSequenceMain Object
ItemQtyItem Quantity-FSItemClassCode3-10FSItem
ItemQtyItem Quantity-FSItemCode50-20FSItem
ItemQtyItem Quantity-100-30

The last examples do not fit into the logic described for the barcode tokenizer; this is because we wanted a way to map in the barcode also the quantity, which, however, cannot be attributed to any Object/Property at the moment of reading. Of course, this logic needs to be implemented in the individual forms.