Link to GS1 AI listing


GS1 decode is done by using a standard (hard coded) mapping of AI's to M3 fields

01 - POPN

02 - POPN

11 - MFDT

13 - MFDT

15 - EXPI

17 - EXPI

31xx-CAWE if CW item or TRQT if Basic UoM is KG, Kg, kg, kG

30 - TRQT

37 - TRQT

10 - BANO 

21 - BANT (Sublot)


We then have a possibility to override this standard by linking an item to a storage requirement in MMS001/X and map to this in Mobile Action settings: this can be done so we can use part of a AI 21 barcode to be linked to BANO instead of having a AI 10 barcode for BANO, Or pushing in a UBD or PACK date as the LOT no instead of letting M3 generate it etc.


 



Example Storage Req configuration

{
   "BANO":[
      {
         "AI":"10",
         "MASK":"YYYYYYYYYYYYYYYYYYYY"
      },
      {
         "AI":"21",
         "MASK":"NNNNNNNNNNYYYYYYYYYY"
      },
      {
         "AI":"11",
         "MASK":"YYYYYY"
      }
   ],
   "BANT":[
      {
         "AI":"21",
         "MASK":"YYYYYYYYYYYYYYYYYYYY"
      }
   ]
}


Explanation of above configuration:

Storage Requirement “JL“ is configured to use GS1 decode. 

It include Lot Number rule “BANO” and Serial number rule “BANT“

For BANO, it will look for AI code 10 first, if found, use all up to 20 characters. 

If AI 10 not found in GS1, second option is use AI “21“, if found, use first 10 characters as Lot number and ignore the rest. 

If AI 10 and 21 both not in GS1, their option is use date AI 11 as Lot. 

For BANT, it will look for AI code 21 first, if found, use all characters as serials number.