Missing Application Identifiers for Bin Code

Owned by Dennis Vibæk
Last updated: Nov 11, 2024 by Maria Jose Avila
3 min read
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 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.


In the Application.cfg file, the Application Identifiers are defined as attributes named 'eanAi'.

See also Register with Encoded Barcode (GS1).


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

      <workflow id="standard" itemNumberAI="01,02,91">

        <configuration scanBehaviourWhenRegisteringQuantity="ScanNextItem" cancelBehaviour="Close" autoSave="false" fastForwardMode="InputAndScanValues">
          <steps>
            <fromBin id="10" header="@{RegistrationCollectorFromBinHeader}" label="{FromBin}" defaultValue="{FromBin}" helpLabel="@{RegistrationCollectorFromBinHelpLabel}" eanAi="00"/>
            <toBin id="20" header="@{RegistrationCollectorToBinHeader}" label="{ToBin}" defaultValue="{ToBin}" helpLabel="@{RegistrationCollectorToBinHelpLabel}" eanAi="00"/>
            <expirationDate id="31" header="@{RegistrationCollectorExpirationDateHeader}" label="" defaultValue="{ExpirationDate}" helpLabel="@{RegistrationCollectorExpirationDateHelpLabel}" eanAi="15,17,12"/>
            <lotNumber id="32" header="@{RegistrationCollectorLotNumberHeader}" defaultValue="{LotNumber}" helpLabel="@{RegistrationCollectorLotNumberHelpLabel}" eanAi="10"/>
            <tote id="35" header="@{RegistrationCollectorToteHeader}" helpLabel="@{RegistrationCollectorToteHelpLabel}" eanAi="98"/>
            <!-- id="37" reserved for PackageNumber -->
            <serialNumber id="40" header="@{RegistrationCollectorSerialNumberHeader}" defaultValue="{SerialNumber}" helpLabel="@{RegistrationCollectorSerialNumberHelpLabel}" eanAi="21"/>
            <quantity id="50" header="@{RegistrationCollectorQuantityHeader}" helpLabel="@{RegistrationCollectorQuantityHelpLabel}" eanAi="310,30,37" minValue="0.0000000001"/>
            <quantityByScan id="51" header="@{RegistrationCollectorQuantityByScanHeader}" helpLabel="@{RegistrationCollectorQuantityByScanHelpLabel}" minValue="0.0000000001"/>
          </steps>
        </configuration>
      </workflow>

Solution

From Mobile WMS version 1.10.2,  the Application Identifier has been changed for Bin Code from "00" to "".

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


The Application Identifier "00" is now added to the existing <tote id> element instead, 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.

      <workflow id="standard" itemNumberAI="01,02,91">

        <configuration scanBehaviourWhenRegisteringQuantity="ScanNextItem" cancelBehaviour="Close" autoSave="false" fastForwardMode="InputAndScanValues">
          <steps>
            <fromBin id="10" header="@{RegistrationCollectorFromBinHeader}" label="{FromBin}" defaultValue="{FromBin}" helpLabel="@{RegistrationCollectorFromBinHelpLabel}" eanAi=""/>
            <toBin id="20" header="@{RegistrationCollectorToBinHeader}" label="{ToBin}" defaultValue="{ToBin}" helpLabel="@{RegistrationCollectorToBinHelpLabel}" eanAi=""/>
            <expirationDate id="31" header="@{RegistrationCollectorExpirationDateHeader}" label="" defaultValue="{ExpirationDate}" helpLabel="@{RegistrationCollectorExpirationDateHelpLabel}" eanAi="15,17,12"/>
            <lotNumber id="32" header="@{RegistrationCollectorLotNumberHeader}" defaultValue="{LotNumber}" helpLabel="@{RegistrationCollectorLotNumberHelpLabel}" eanAi="10"/>
            <tote id="35" header="@{RegistrationCollectorToteHeader}" helpLabel="@{RegistrationCollectorToteHelpLabel}" eanAi="00,98"/>
            <!-- id="37" reserved for PackageNumber -->
            <serialNumber id="40" header="@{RegistrationCollectorSerialNumberHeader}" defaultValue="{SerialNumber}" helpLabel="@{RegistrationCollectorSerialNumberHelpLabel}" eanAi="21"/>
            <quantity id="50" header="@{RegistrationCollectorQuantityHeader}" helpLabel="@{RegistrationCollectorQuantityHelpLabel}" eanAi="310,30,37" minValue="0.0000000001"/>
            <quantityByScan id="51" header="@{RegistrationCollectorQuantityByScanHeader}" helpLabel="@{RegistrationCollectorQuantityByScanHelpLabel}" minValue="0.0000000001"/>
          </steps>
        </configuration>
      </workflow>

Who is affected by this change?

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

You will not be affected if you use simple barcodes for your Bin Codes.


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 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 to the old standard format.
    • Implement this small customization OnAfterGetBinGS1Ai to overwrite the Application Identifier Value sent out from the backend.

See also