Page Comparison

...

Info
Requirement: Tasklet Mobile WMS version 1.10.2

Problem

In Mobile WMS we have up until now been using Application Identifier "00" for Bin Code.

Now, we also want aim to support the scanning of the official Application Identifier for SSCC according to the GS1 standard format https://ref.gs1.org/ai/

Because the official Application Identifier for SSCC is "00", we must change the existing Application Identifier for Bin Code in Mobile WMS.

...

Example of the standard Workflow defined in all existing Application.cfg.

<workflowid="standard"itemNumberAI="01,02,91">

<configurationscanBehaviourWhenRegisteringQuantity="ScanNextItem"cancelBehaviour="Close"autoSave="false"fastForwardMode="InputAndScanValues">

<steps>

<fromBinid="10"header="@{RegistrationCollectorFromBinHeader}"label="{FromBin}"defaultValue="{FromBin}"helpLabel="@{RegistrationCollectorFromBinHelpLabel}" eanAi="00"/>

<toBinid="20"header="@{RegistrationCollectorToBinHeader}"label="{ToBin}"defaultValue="{ToBin}"helpLabel="@{RegistrationCollectorToBinHelpLabel}" eanAi="00"/>

<expirationDateid="31"header="@{RegistrationCollectorExpirationDateHeader}"label=""defaultValue="{ExpirationDate}"helpLabel="@{RegistrationCollectorExpirationDateHelpLabel}"eanAi="15,17,12"/>

<lotNumberid="32"header="@{RegistrationCollectorLotNumberHeader}"defaultValue="{LotNumber}"helpLabel="@{RegistrationCollectorLotNumberHelpLabel}"eanAi="10"/>

<toteid="35"header="@{RegistrationCollectorToteHeader}"helpLabel="@{RegistrationCollectorToteHelpLabel}"eanAi="98"/>

<serialNumberid="40"header="@{RegistrationCollectorSerialNumberHeader}"defaultValue="{SerialNumber}"helpLabel="@{RegistrationCollectorSerialNumberHelpLabel}"eanAi="21"/>

<quantityid="50"header="@{RegistrationCollectorQuantityHeader}"helpLabel="@{RegistrationCollectorQuantityHelpLabel}"eanAi="310,30,37"minValue="0.0000000001"/>

<quantityByScanid="51"header="@{RegistrationCollectorQuantityByScanHeader}"helpLabel="@{RegistrationCollectorQuantityByScanHelpLabel}"minValue="0.0000000001"/>

</steps>

</configuration>

</workflow>

Solution

From Mobile WMS version X1.Y.Z we have changed 10.2, the Application Identifier has been changed for Bin Code from "00" to "".

This is required because a specific Application Identifier can´t cannot be used for different purposes and values.

The Application Identifier "00" is now added to the existing <tote id> element instead, changed changing it from "98" to "00,98".

Example of the new standard Workflow defined in Aplication.cfg

Note that all occurrences of eanAI for <fromBin>, <toBin> and <tote id> are changed in the Application.cfg.

<workflowid="standard"itemNumberAI="01,02,91">

<configurationscanBehaviourWhenRegisteringQuantity="ScanNextItem"cancelBehaviour="Close"autoSave="false"fastForwardMode="InputAndScanValues">

<steps>

<fromBinid="10"header="@{RegistrationCollectorFromBinHeader}"label="{FromBin}"defaultValue="{FromBin}"helpLabel="@{RegistrationCollectorFromBinHelpLabel}"eanAi=""/>

<toBinid="20"header="@{RegistrationCollectorToBinHeader}"label="{ToBin}"defaultValue="{ToBin}"helpLabel="@{RegistrationCollectorToBinHelpLabel}"eanAi=""/>

<expirationDateid="31"header="@{RegistrationCollectorExpirationDateHeader}"label=""defaultValue="{ExpirationDate}"helpLabel="@{RegistrationCollectorExpirationDateHelpLabel}"eanAi="15,17,12"/>

<lotNumberid="32"header="@{RegistrationCollectorLotNumberHeader}"defaultValue="{LotNumber}"helpLabel="@{RegistrationCollectorLotNumberHelpLabel}"eanAi="10"/>

<toteid="35"header="@{RegistrationCollectorToteHeader}"helpLabel="@{RegistrationCollectorToteHelpLabel}"eanAi="00,98"/>

<serialNumberid="40"header="@{RegistrationCollectorSerialNumberHeader}"defaultValue="{SerialNumber}"helpLabel="@{RegistrationCollectorSerialNumberHelpLabel}"eanAi="21"/>

<quantityid="50"header="@{RegistrationCollectorQuantityHeader}"helpLabel="@{RegistrationCollectorQuantityHelpLabel}"eanAi="310,30,37"minValue="0.0000000001"/>

<quantityByScanid="51"header="@{RegistrationCollectorQuantityByScanHeader}"helpLabel="@{RegistrationCollectorQuantityByScanHelpLabel}"minValue="0.0000000001"/>

</steps>

</configuration>

</workflow>

Who is affected by this change?

This You will only affect you be affected if you have created and used your own custom GS1 Encoded barcodes for your Bin Codes in the warehouse.

If you are using You will not be affected if you use simple barcodes for your Bin Codes, you will not be affected.

What to do if you are affected by this change

You can change your existing barcode from a GS1 encoded barcode to a simple barcode format for your Bin Codes in the Warehouse.
If you don´t do not need support for scanning SSCC barcodes, you can change back to the old standard with the below steps:
- Ask Tasklet to change your Application.cfg back to the old standard format.
- Implement this small customization OnAfterGetBinGS1Ai to overwrite the Application Identifier Value sent out from the backend.

Versions Compared

Old Version 6

New Version Current

Key

Problem

Solution

Who is affected by this change?

What to do if you are affected by this change

See also