Problem
In Mobile WMS we have until now been using Application Identifier "00" for Bin Code.
...
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"/>
<!-- id="37" reserved for PackageNumber -->
<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 X.Y.Z we have changed the Application Identifier for Bin Code from "00" to "".
...
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"/>
<!-- id="37" reserved for PackageNumber -->
<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 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.
...